...
- User Requirements - things users would like to be able to do, subdivided by user category (e.g., student, instructor, librarian)
- Functional Requirements - should flow from and reference user requirements; things the software system needs to be able to do
- Technical Requirements - requirements about how things need to be implemented; these should support user requirements, but they sometimes derive from other sources, such as the Sakai community's decision to use a particular technology
Values for the Priority column are high, medium, low, and outplan. High priority items must be achieved for the project to be successful. Ideally, there is time to accomplish all high priority items as well as a make-sense assortment of medium and low priority items. Outplan requirements are those which we decide we will not attempt to address.
User Requirements
Note: Where user categories are not specifically identified (i.e., where this says "users can..." instead of "instructors can..." or "librarians can..."), the implication is that the task is broadly useful to most or all categories of user.
...