7. Capability Maturity Model Integration (CMMI) - tud.ttu.ee

An Example - RequirementsDevelopment SP 2.1-1 Establish Productand Product ComponentRequirements– Establish and maintain, fromthe customer requirements,product and productcomponent requirementsessential to product andproduct componenteffectiveness and affordability• ISO/IEC 15288, System Life CycleProcesses– Clause 5.5.3 - Requirements AnalysisProcess• IEEE/EIA 12207.0, Software LifeCycle Processes– Clause 5.3.2 - System RequirementsAnalysis– Clause 5.3.4 - Software requirementsanalysis• IEEE 1233, Guide for DevelopingSystem Requirements Specifications• IEEE 830, Software RequirementsSpecifications121An Example - RequirementsDevelopment5.3.2 FunctionsFunctional requirements should define the fundamental actions thatmust take place in the software in accepting and processing the inputsand in processing and generating the outputs. These are generallylisted as “shall” statements starting with “The system shall”These include:a) Validity checks on the inputsb) Exact SP sequence 2.1-1 of Establish operations Productc) Responses to abnormal situations, including:1) Overflow and Product Component2) Communication facilitiesRequirements3) Error handling and recoveryd) Effect–ofEstablishparametersand maintain, frome) Relationship of outputs to inputs . . .1) It may the be appropriate customer partition requirements,the functional requirements intosubfunctionsproductor subprocesses.and productThis doesnot imply that the software design will also be partitioned that way.5.3.3 Performance component requirements requirementsThis subsection should specify both the static and the dynamicessential to product andnumerical requirements placed on the softwareor on product human interaction component with the software as a whole. Staticnumerical requirements may include theeffectiveness and affordabilityfollowing: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.• ISO/IEC 15288, System Life CycleProcesses– Clause 5.5.3 - Requirements AnalysisProcess• IEEE/EIA 12207.0, Software LifeCycle Processes– Clause 5.3.2 - System RequirementsAnalysis– Clause 5.3.4 - Software requirementsanalysis• IEEE 1233, Guide for DevelopingSystem Requirements Specifications• IEEE 830, Software RequirementsSpecifications12261