2. โข Clarity:
โข Requirements should be clear, unambiguous, and easy to understand for all
stakeholders. Ambiguous requirements can lead to misinterpretations and
project errors.
โข Completeness:
โข Requirements must capture all necessary functionalities and constraints.
Incomplete requirements may result in gaps or oversights during the
development process.
3. โข Consistency:
โข Requirements should not conflict with each other. Consistency ensures that
all aspects of the system are aligned and can be implemented without
contradictions.
โข Relevance:
โข Each requirement should contribute directly to the project's objectives.
Irrelevant requirements can add unnecessary complexity and impede
progress.
โข Feasibility:
โข Requirements should be realistic and achievable within the constraints of the
project, considering factors such as time, budget, and technical limitations.
4. โข Verifiability:
โข Requirements should be testable, allowing for verification to ensure that the
final product meets the specified criteria.
โข Traceability:
โข A requirement should be traceable to its source and traceable forward to
design, implementation, and testing. This helps in maintaining a clear
understanding of the project scope and progress.
โข Modifiability:
โข Requirements should be adaptable to changes, as modifications may be
necessary during the development process or due to changing project needs.
