System Requirements Specification (In greater detail)

Prof. asked to think and place a more detailed break down of what should be in our System Requirements Documentation.

System Requirements Specification (SRS) is basically an organization's understanding and agreement completed in writing about proposed client's system dependencies and requirements provided to customer prior any actual design or work.

List of what SRS document should include ( contains previously discussed items along with expansion and newly added items):

• High level goal (tree structure) - while most of implementations done in bottom-up approach
• (A) Functional requirements

A.1 User

A.1.1 User qualifications (assumed or required)

A.1.2 User interface and environment

A.2 Performance

A.2.1 Time requirements - specify at which speed system must operate

A.3 Concurrency - how multi-threading must be handled by the system

A.4 HW requirements, platform requirements

A.4.1 The hardware to be used

A.4.2 Hardware limitations (s.a. minimum memory amount required)

A.4.3 Compiler to be used (version, distributer, etc.)

A.4.4 Any SW and OS dependencies, s.a. what OS and what versions system required for operation, what other SW packages, programs, or libraries expected to be installed on PC/Mac prior to system's installation and run

A.5 Data flow diagrams, high level highlights on how the system is working and responding to certain events

A.6 Quality requirements

A.6.1 Quality assurance planning

A.6.2 Configuration management of the system

A.7 Reliability requirements - can be specified by Mean Time Between Failures and/or Mean Time to Repair.

A.8 Maintanability requirements

A.8.1 Trace and repair of defects (logs)

A.8.2 Modularity of SW

A.8.3 Readability of the code

• (B) non-functional

B.1 Documentation

B.1.1 Operational requirements - how system will be used and usage in hostile environment, prioritization of failed events (emergency planning)

B.2 Trademark, legal

B.3 Aesthetics (look & feel)

B.4 Coding Standards

• (C) Testing

C.1 Specify how and what tests will be done during development, test data.

C.2 Acceptance testing - specifies the tests will be used for the user acceptance of the system ( Integration test suite and data sets)

• (D) Security

D.1 Security requirements and concern for the system's normal operation and how security bridges will be handled by the system if any to occur