Professional Documents
Culture Documents
RE Hina Khan (CU-2938-2022) A
RE Hina Khan (CU-2938-2022) A
SUBMITTED TO:
Sir Asim
SUBMITTED BY:
HINA KHAN
CLASS ID: CU-2938-2022
CLASS & SECTION: BSSE-2022(A)
Analyzing Quality Requirement
1. Source of Requirements:
Identify the sources of quality requirements, including stakeholders, customers, regulatory
bodies, and internal project documentation.
2. Requirement Classification:
Functional vs. Non-functional Requirements:
Distinguish between functional requirements (what the system should do) and non-functional
requirements (how well the system should perform).
3. Requirement Prioritization:
Criticality: Assess the criticality of each quality requirement in relation to the overall
project goals and objectives.
Priority: Establish priorities based on the impact of not meeting each requirement.
4. Requirement Decomposition:
Breaking Down Requirements: Decompose high-level quality requirements into
more detailed and specific sub-requirements.
Granularity: Ensure that requirements are at an appropriate level of granularity for
effective implementation and testing.
5. Requirement Validation:
Review and Validation: Conduct reviews and validations of quality requirements with
stakeholders to ensure clarity, completeness, and correctness.
6. Requirement Traceability:
Traceability Matrix: Establish and maintain a traceability matrix to link quality
requirements to their source, related functional requirements, and test cases.
7. Measurable Metrics:
Quantifiable Criteria: Define measurable metrics for each quality requirement, where
possible. For example, response time, error rates, or availability percentages.
Acceptance Criteria: Clearly specify the acceptance criteria that must be met for
each quality requirement.
8. Risk Analysis:
Identify Risks: Analyze potential risks associated with meeting or not meeting each
quality requirement.
Mitigation Strategies: Develop mitigation strategies for high-impact risks that could
affect the achievement of quality goals.
10. Documentation:
Document Changes: Keep documentation up-to-date as requirements evolve or change.