An Example - Requirements Development
{"Image DocumentName": "An Example - Requirements Development", "Image ImageDescription": "5.3.2 Functions. Functional requirements should define the fundamental actions that must take place in the software in accepting and processing the inputs and in processing and generating the outputs. These are generally listed as shall statements starting with The system shall These include: a) Validity checks on the inputs. b) Exact sequence of operations. c) Responses to abnormal situations, including: 1) Overflow. 2) Communication facilities. 3) Error handling and recovery. d) Effect of parameters. e) Relationship of outputs to inputs ) It may be appropriate to partition the functional requirements into subfunctions or subprocesses. This does. not imply that the software design will also be partitioned that way Performance requirements. This subsection should specify both the static and the dynamic numerical requirements placed on the soft- ware or on human interaction with the software as a whole. Static numerical requirements may include the. following: a) The number of terminals to be supported; b) The number of simultaneous users to be supported; c) Amount and type of information to be handled. SP Establish Product and Product Component Requirements. Establish and maintain, from the customer requirements, product and product component requirements essential to product and product component effectiveness and affordability. ISO/IEC 15288, System Life Cycle Processes. Clause Requirements Analysis Process. IEEE/EIA , Software Life Cycle Processes. Clause System Requirements Analysis. Clause Software requirements analysis. IEEE 1233, Guide for Developing System Requirements Specifications. IEEE 830, Software Requirements Specifications.", "Image XResolution": "37", "Image YResolution": "37", "Image ResolutionUnit": "Pixels/Centimeter", "Image Software": "SlidePlayer", "Image YCbCrPositioning": "Centered"}