Spec Template V5 - West Virginia



State of West VirginiaOffice of Technology216217562230Requirements Specification ContentsProject Drivers1. The Purpose of the Project Project Constraints3. Mandated Constraints4. Naming Conventions and Definitions5. Relevant Facts and AssumptionsFunctional Requirements6. The Scope of the Work7. Business Data Model8. The Scope of the Product9. Functional Requirements Nonfunctional Requirements10. Look and Feel Requirements 11. Usability and Humanity Requirements12. Performance Requirements13. Operational and Environmental Requirements14. Maintainability and Support Requirements15. Security Requirements16. Cultural and Political Requirements17. Legal RequirementsProject Issues18. Open Issues 19. Off-the-Shelf Solutions20. New Problems 21. Tasks 22. Migration to the New Product23. Risks24. Costs25. User Documentation and Training26. Waiting Room27. Ideas for Solutions1. The Purpose of the Project1a. The User Business or Background of the Project Effort 1b. Goals of the Project 2. Mandated Constraints2b. Implementation Environment of the Current System2c. Partner or Collaborative Applications2d. Off-the-Shelf Software2e. Anticipated Workplace Environment2f. Schedule Constraints 2g. Budget Constraints3. Naming Conventions and Definitions3a. Definitions of All Terms, Including Acronyms, Used in the Project4. Relevant Facts and Assumptions4a. Relevant Facts4b. Business Rules4c. Assumptions 5. The Scope of the Work5a. The Current Situation5b. The Context of the Work5c. Work Partitioning5d. Specifying a Business Use Case6. Business Data Model6a. Data Model6b. Data Dictionary7. The Scope of the Product7a. Product Boundary7b. Product Use Case List7c. Individual Product Use Cases8. Functional and Data Requirements 8a. Functional Requirements9. Look and Feel Requirements 9a. Appearance Requirements 9b. Style Requirements 10. Usability and Humanity Requirements10a. Ease of Use Requirements 10b. Personalization and Internationalization Requirements10c. Learning Requirements 10d. Understandability and Politeness Requirements10e. Accessibility Requirements11. Performance Requirements11a. Speed and Latency Requirements11b. Safety-Critical Requirements11c. Precision or Accuracy Requirements11d. Reliability and Availability Requirements11e. Robustness or Fault-Tolerance Requirements11f. Capacity Requirements11g. Scalability or Extensibility Requirements11h. Longevity Requirements12. Operational and Environmental Requirements12a. Expected Physical Environment12b. Requirements for Interfacing with Adjacent Systems12c. Productization Requirements12d. Release Requirements 13. Maintainability and Support Requirements13a. Maintenance Requirements13b. Supportability Requirements13c. Adaptability Requirements14. Security Requirements14a. Access Requirements14b. Integrity Requirements14c. Privacy Requirements14d. Audit Requirements14e. Immunity Requirements15. Cultural and Political Requirements15a. Cultural Requirements15b. Political Requirements16. Legal Requirements 16a. Compliance Requirements16b. Standards Requirements17. Open Issues 18. Off-the-Shelf Solutions18a. Ready-Made Products18b. Reusable Components18c. Products That Can Be Copied 19. New Problems19a. Effects on the Current Environment19b. Effects on the Installed Systems 19c. Potential User Problems19d. Limitations in the Anticipated Implementation Environment That May Inhibit the New Product19e. Follow-Up Problems 20. Tasks20a. Project Planning 20b. Planning of the Development Phases 21. Migration to the New Product21a. Requirements for Migration to the New Product21b. Data That Has to Be Modified or Translated for the New System 22. Risks 23. Costs24. User Documentation and Training24a. User Documentation Requirements 24b. Training Requirements 25. Waiting Room 26. Ideas for Solutions ................
................

In order to avoid copyright disputes, this page is only a partial summary.

Google Online Preview   Download