Question: Briefly explain why it is desirable to categorize technical specifications using the categories in Table 3.4 or 3.5. Documenting Technical Specifications The categories listed in
Briefly explain why it is desirable to categorize technical specifications using the categories in Table 3.4 or 3.5.
Documenting Technical Specifications
The categories listed in Table 3.4 can be used to organize and document technical specifications.
TABLE 3.4 Categories of technical specifications
| Category | Description |
| Interfaces | To the environment and other subsystems |
| Functions | Stimulusresponse pairs |
| Performance | Response time; throughput |
| Behavior | Sequences of system states over time |
| Capacities | Data; communication; memory |
| Design constraints | Predetermined design decisions |
| Quality attributes | Safety; security; reliability; others |
IEEE Standard 8301998 is a Recommended Practice for Software Requirements Specifications [IEEE830]. Table 3.5 lists the specific requirements to be documented in section 3 of a Software Requirements Specification that conforms to IEEE 830.
TABLE 3.5 Specific requirements in IEEE Standard 8301998
| Specific Requirements | Description |
| External interfaces | Inputs into and outputs from the software system |
| Functions | Actions taken in accepting and processing inputs and generating outputs |
| Performance requirements | Static and dynamic quantified requirements |
| Logical database requirements | Requirements for information to be placed into a database |
| Design constraints | Constraints imposed by conformance to standards, hardware limitations, etc. |
| Software system attributes | Reliability; availability; security; maintainability; portability |
Step by Step Solution
There are 3 Steps involved in it
Get step-by-step solutions from verified subject matter experts
