Requirements Capture

Page initiated by Jim Busser. Plan is to begin capturing and listing requirements that could better guide use case formulation. For now I am looking at this link as a guide. Here, it is suggested:
  1. Capture an overall view of the problem, and the desired characteristics of its solution in the vision document.
  2. Identify the use case and actors from the vision document and show their relationships on one or more use case diagrams.
  3. Give detailed use case specifications for each use case, covering normal and alternate behavior, pre- and post-conditions.
  4. Capture all non-functional requirements in a supplementary requirements specification.

Link to UseCases.

Link to ClinicalOrganizingAndWorkflows
Topic revision: 10 Mar 2007, JamesBusser
This site is powered by the TWiki collaboration platformCopyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding Foswiki? Send feedback
Powered by Olark