Participation

Owned by Jason Jason
Last updated: Apr 26, 2006Version comment
3 min read

Opportunities to Shape uPortal Development

Many opportunities exist to become involved in shaping the direction of the uPortal Framework. The first steps are documenting our vision, requirements, understanding of problems to be addressed, and how they fit into the bigger picture of uPortal development. Several avenues are available for contributing to the direction.

Vision Statements

Institutional and individual visions for an enterprise portal framework by and for higher education. Visions address the needs individual institutions are solveing and roles we see portals playing (e.g a customizable, personalizable user platform, service delivery mechanism, etc.) Individual perspectives are then regularly discussed, and combined to come up with an overall vision for the platform.

This is the simplest way to voice your priorities and ensure they are visible for considerationg for future portal development.

To contribute an individual vision statement:

  1. Visit: http://www.ja-sig.org/wiki/display/UPR/Vision .
  2. If you have not yet created a JA-SIG wiki account, do so.
  3. Log in to the JA-SIG wiki.
  4. Click on the "Add Page" link to create a new page for your vision statement.
  5. Save your vision statement with a name like "MY_INSTITUTION_NAME Vision"
  6. Label you vision document with "vision" to have it appear in the list on the institutional page

To discuss evolving the Community Vision Statement:

  1. Document your individual vision (see above)
  2. Join the jasig-dev@lists.unm.edu mailing list
  3. Create a post with the subject line containing: Proposed Vision - SUMMARY_HERE
    In your email provide a link to the document detailing your individual vision for a portal deployment, and a brief description of how you would like to see the community vision evolve to enable this particular role.
  4. After community discussion and consensus has emerged, changes (if appropriate) should be made to the community vision document to reflect the new understanding

Requirements

High-level descriptions of essential framework functionality. They detail what capabilities the framework must possess to be able to fulfill our vision for a portal. Requirements should be more focused on needs (the what) and less focused on implementation (the how)

Requirements are a good starting point for organizing community resources to implement common needs. Once we begin documenting the requirements, they serve as a natural point for discussion and collaboration.

Contributing Requirements

  1. Review the Requirements Library for existing/similar requirements
  2. Create a new wiki page using the "Requirements" template detailing your requirements including:
    • title
    • description
    • audience
    • category
    • priority
    • resources able to contribute
  3. optional Provide use-cases (below) describing individual scenarios for utilizing the requirement
  4. Join the jasig-dev@lists.unm.edu mailing list
  5. Create a post with the subject line containing: Proposed Requirement - SUMMARY_HERE
    In your email provide a link to the document detailing your high-level requirement for a portal deployment, and a summary of the goals you would like to accomplish.
  6. As community discussion and consensus emerges, changes should be made to the requirements document (and appropriate use-cases) to reflect modifications & feedback
  7. Work with the Framework Coordinator & Release Engineers to work towards implementation in an upcoming uPortal release

Use Cases

Portal Framework use-cases are meant to be specific, detailed descriptions of how a particular aspect of a feature should work. Use cases should include a description of the flow of a user's interaction with the system & other systems. Use cases are intended to describe the to a programmer/implementor the way a feature would be used and should work.

Use cases are particularly appropriate to propose modifications or extensions to existing behavior, and to ease collaboration between multiple parties. They are also a good way to flesh out proposed features and how they would function in detail.

Contributing Use Cases

  1. Review the Requirements Library for requirements fulfilled by the use-case
  2. Create a new wiki page using the "Use-Case" template describing the use case as a child page of the appropriate requirement
  3. Include actors, states, success conditions
  4. Join the jasig-dev@lists.unm.edu mailing list
  5. Create a post with the subject line containing: Proposed Use Case - SUMMARY_HERE
    In your email provide a link to the document detailing your high-level requirement for a portal deployment, and a brief description of how you would like to see the community vision evolve to enable this particular role.
  6. As community discussion and consensus emerge, changes should be made to the use-case document to reflect modifications & feedback
  7. Work with the Framework Coordinator & Release Engineers to work towards implementation in an upcoming uPortal release