在軟體開發流程中，需求分析是初期了解系統範圍(Scope)的一個步驟。在進行設計之前，每個專案成員都要先審閱軟體需求是否已經完備。在實務上，我們可以透過Checklist來化簡審閱的過程，確保軟體需求已考慮周全。
Requirement Peer Review Checklist
- Compliance with standards
Does the requirements specification comply with ISD or tailored Branch/project-level standards and naming conventions? - Completeness of Specifications
Does the requirements specification document address all known requirements? Have ‘TBD’ requirements been kept to a minimum, or eliminated entirely? - Clarity
Are the requirements clear enough to be turned over to an independent group for implementation? - Consistency
Are the specifications consistent in notation, terminology, and level of functionality? Are any required algorithms mutually compatible? - External Interfaces
Have external interfaces been adequately defined? - Testability
Are the requirements testable? Will the testers be able to determine whether each requirement has been satisfied? - Design-Neutrality
Does the requirements specification state what actions are to be performed, rather than how these actions will be performed? - Readability
Does the requirements specification use the language of the intended testers and users of the system, not software jargon? - Level of Detail
Are the requirements at a fairly consistent level of detail? Should any particular requirement be specified in more detail? In less detail? - Requirements Singularity
Does each requirement address a single concept, topic, element, or value? - Definition of Inputs and Outputs
Have the internal interfaces, i.e., the required inputs to and outputs from the software system, been fully defined? Have the required data transformations been adequately specified? - Scope
Does the requirements specification adequately define boundaries for the scope of the target software system? Are any essential requirements missing? - Design Constraints
Are all stated design and performance constraints realistic and justifiable?
參考資料：
No comments:
Post a Comment