Discussion of the scope for the OSP 2.4 release. Consider that the release is planned for the April 2007 timeframe and the code freeze for the release is on March 15th. List items that you believe are important to include in the upcoming release. Ultimately the scope will be determined by the folks who commit to work on the 2.4 project, the resources available, and the time constraints. Also see the /wiki/spaces/REQ/pages/13648396425
Draft High Level Scope
Each of the items below represents a high-level scope item. These are intended to frame the release and focus our efforts on elaborating requirements that fall into scope, and postponing work on requirements that fall outside the scope. Once requirements are complete, the set of agreed upon requirements will be the detailed scope for the release.
UI rework/refinement. Focus on making the user experience more integrated and cohesive. This will involve assessing current user workflow's, reducing clicks, potentially reducing tools, increasing UI consistency between tools, language consistency, etc.
Documentation. Documentation should include a map and description of how all the tools work together, simple 'start here' cookbook type docs, documentation on how to construct the various data structures such as forms, portfolio templates, etc.
Sample data structures. Include complete sample portfolios with all templates, layouts, forms, matrices for a variety of portfolios - accreditation, self presentation, integrative learning, project portfolio. With doc on how they are put together and the use case for each role's interaction.
Improve authoring flexibility. Improve ability to change data structures once created and published (Matrices, Forms, etc.). Rethink immutable design of published items such as forms, matrices, wizards etc. When does it make sense to allow changes to published data structures. (ie) Should it be possible to add on to a matrix once it's already in use? Also allow changing the state of objects (published/unpublished)
Reports. Complete the reports tool.
Integration with Goal Management Tool. Make Wizards, Matrices and Forms goal aware.
Forward compatibility. No changes that require difficult migration. The project team is making a commitment to building all migration scripts for a seamless upgrade from 2.2.x.
Create "Builders" for the hard to create xsd, xsl, css, xhtml files. Create "Builders" for the hard to create xsd, xsl, css, xhtml files. In the short term, tools that enable faculty to build their own forms and their own custom presentations are also needed to reduce the bottleneck around programming staff.