Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Wiki Markup
h1. High level requirements

- Time Driven
- Goal Driven
- Iterative
- Intuitive central location 
- Guided
- Supports integrationCross -Site spansintegration sites
- Supports Artifact Persistence over Time - spans terms, years, etc
- Includes Notification

h2. Institution



h2. Department/Program



h2. Faculty


h3. Create Assessments that speak to course goals/learning outcomes

h2. Student


h3. Create a Portfolio/Presentation

# Give Title
# Select Template (free form or layout)
# Select Content
# Preview
# Choose Audience
# Share

h3. Keep Track of What I Need to Do/Know (RSS feed wizard)

* Deadlines (Assignment, Matrix, Wizards)
* Tasks (Forum, Matrix, Wizard)
* Feedback and Evaluations
* Portfolios/Presentations (that have been shared with Me)

h2. [New Use Cases]



----
h2. Past Work

h2. [Use Cases] - Old Use Cases
Dashboard design proposal from Ann Arbor Planning meeting (May 2007): [UMichigan - OSP Dashboard]
[OSP2x Prototypes (2005 mock-ups) | ^OSP2xprototypes2.pdf]


{gliffy:name=Educational Roadmap|space=OSP|page=Workflow Breakout Group|pageid=4064170|align=center|size=L}