SQA Role during Software Requirements Phase Schulmeyer, G.,’Handbook of Software Quality Assurance’, Chapter 16.6, Prentice Hall, 1999.

Documents Produced Two major outputs of this phase An SRS for each Configuration Item (CI) An Interface Requirement Specification (IRS) for all CIs If more than one CI have to be developed Both documents have to conform to a defined format and content e.g. IEEE Standard, NASA Standard, Military Standard 9/20/2018

Role of SQA Any deviations or additions to the SRS or IRS must be discussed and agreed to by stakeholders e.g. SQA Before and During internal technical reviews Verify that all of the agreed contents are included in draft SRS-IRS Verify that all requirements are included in document Verify traceability (e.g. check for ‘no apparent predecessor’, invalid, missing requirement): Upward, i.e. from SRS to System requirements Downward from System requirements to SRS-IRS 9/20/2018

Role of SQA Before and During internal technical reviews 4. Verify that each SRS is consistent with other SRS and the IRS for that system Evaluate the adequacy of quality factors requirements e.g. maintainability, portability 6. Verify SRS-IRS for completeness and correctness, explicit, non ambiguous and testable. e.g. Is testable criteria well defined (pass-fail) ? 7. Evaluate if verification method described in Software Development Plan (SDP) is adequate e.g. test, demonstration, analysis, inspection 9/20/2018

Role of SQA Before and During internal technical reviews 8. Prepare a list of discussion items for internal draft SRS-IRS reviews Record and track action items Prepare report of reviews Validate actions Verify updated SRS-IRS 3 . Attend Technical Reviews with Customer Customer may request changes to documents SQA will review changes before document is released to customer SRS-IRS, once released, becomes part of a baseline i.e. allocated baseline 9/20/2018