Metadata
- Source
- FLUID-1358
- Type
- Task
- Priority
- Major
- Status
- Closed
- Resolution
- Fixed
- Assignee
- N/A
- Reporter
- Daphne Ogle
- Created
2008-08-29T10:56:26.000-0400 - Updated
2013-04-11T17:53:03.765-0400 - Versions
- N/A
- Fixed Versions
- N/A
- Component
-
- Design Framework
- Uploader
Description
Abstracted use cases are good start to the requirements list. Other requirements might come from personas, functional needs in scenarios not captured as use cases, partner project priorities, etc.
These should be documented on the wiki in the component design space.