Information Technology Reference
In-Depth Information
5.1 Description for Software Behavior
5.1.1 Events
5.1.2 States
5.2 State Transition Diagrams
5.3 Control Specification (CSPEC)
6. Restrictions, Limitations, and Constraints
Special issues which impact the specification, design, or implementation of the
software are noted here.
7. Validation Criteria
The approach to software validation is described.
7.1 Classes of Tests
7.2 Expected Software Response
7.3 Performance Bounds
8. Appendices
Presents information that supplements the Requirements Specification.
8.1 System Traceability Matrix
8.2 Product Strategies
8.3 Analysis Metrics to be Used
8.4 Supplementary Information (as required)
5.8 Chapter Summary and Conclusions
Requirements for a system are the descriptions of the services provided by the
system and its operational constraints. Functional requirements are associated with
specific functions, tasks or behaviors the system must support. Non-functional
requirements are constraints on various attributes of these functions or tasks.
Domain requirements include specialized domain terminology or references to
domain concepts. Since these are specialized, software engineers often find it
difficult to understand how they are related to other system requirements.
Requirement elicitation is distinguished into two categories as traditional and
modern methods.
Communicating with the client involves the developers and customers devel-
oping a shared understanding of problems and of technical solutions. Effective
requirements definition requires mutual control of process by all players. In tra-
ditional methods of requirement elicitation, interviews and questionnaires were the
primary technique of fact finding and information gathering. This chapter explains
the way to identify the functional and non-functional requirements, as well as
