Themes/functional needs developed during OSP 2.6 Summit brainstorming session at IUPUI in October 2007
Themes:
- Governance / Operational Structure
- Functional Team / Process planning
- Structure, organization, responsibilities?
- Rotating functional team lead?
- How does DESIGN/review fit into functional specs/QA process?
- Permissions / Workflows / Personas
- Mapping of Roles, Personas, Actions w.r.t. Workflows
- Outline the roles/perms in terms of educationally bounded use cases
- General workflow vs. existing subsystem - build or adopt something?
- Publishing workflows!
- User opt-in groups... Groups outside of CIGs - sharing toward these groups
- Tagging / Goal Management
- Common ground in GMT dev - organizational structure
- Tagging - what does it really do? How does it help?
- Long-Term Data Structure Sustainability
- Migration of data/structures and change between versions, institutions, programs, etc.
- Deletion/Editing - long-term sustainability
- Cohort use of a matrix: permissions and data over time, evaluators, etc. Management of complexity/change -> single experience for student
- Goalset Change over time
- Reporting
- Global parameters around reporting requirements.. Are there specifications that are applicable to multiple institutions' needs or are they strictly institution-specific?
- Aggregated View????
- Anything to talk about today besides planning?
...