System Requirements Specifications
Input
The input for this process is the requirements issues as gathered from the client and other stakeholders.
Process
At this stage, the engineering has to learn from competitors, how they do it, why they failed, and how they succeed. Most of the time a single focal person is writing the document but he has to review the document with all the development teams and marketing as well.
When everybody in the firm has signed and the document got final approval, the customer has to get this Statement Of Work (SOW) and approve it.
Output
The System Requirements Specifications document should contain at least the following section:
PROJECT DRIVERS
1. The Purpose of the Project
2. Client, Customer, and Other Stakeholders
3. Users of the Product
PROJECT CONSTRAINTS
4. Mandated Constraints
5. Naming Conventions and Definitions
6. Relevant Facts and Assumptions
FUNCTIONAL REQUIREMENTS
7. The Scope of the Work
8. The Scope of the Product
9. Functional and Data Requirements
NON-FUNCTIONAL REQUIREMENTS
10. Look and Feel Requirements
12. Performance Requirements
11. Usability, MMI, and Operational Requirements
14. Installation, Maintainability, and Support Requirements
15. Security and Safety Requirements
17. Legal and Regulatory
18. Logistics Issues
TEST LIST
19. Functional
20. Data
21. Constrains
22. Edge Capability testing
23. System Functions
RISK ASSESSMENT
24. Scheduling of the deliverables
25. Fulfilling the defined Content
26. Cost of the project
27. Required functionality
28. User Verification - goals of the system