Requirements supplementary

topics
Requirements Problems
Requirements from the User/Customer’s
Perspective:
• User Stories: These are brief descriptions of a feature or functionality
told from the perspective of the end user. They are typically used in
agile methodologies to capture user requirements.
• Use Cases: Use cases describe the interactions between the system
and external entities (users or systems) to achieve a particular goal.
They provide a detailed view of how the system will be used.
Issues Related to System Contract
Requirements:
• Legal and Compliance Requirements: Systems often need to adhere
to certain legal and compliance standards. Identifying and
documenting these requirements is essential for ensuring that the
system complies with industry regulations.
• Service Level Agreements (SLAs): Contracts may include SLAs that
define the expected performance, availability, and other service-
related aspects of the software. These should be clearly understood
and documented during requirements engineering.
Requirements Problems:
• Ambiguity: Unclear or ambiguous requirements can lead to
misunderstandings and errors during the development process.
Resolving ambiguity is crucial to delivering a successful software
product.
• Inconsistency: Conflicting or contradictory requirements may arise
from different stakeholders. Resolving inconsistencies ensures that
the final system meets the expectations of all parties involved.
• Scope Creep: This refers to the uncontrolled expansion of project
scope without proper authorization. Managing and controlling
changes to requirements is essential to avoid scope creep.
• Traceability:
• Requirements Traceability Matrix (RTM): A matrix that links requirements to design elements, test
cases, and other related artifacts. It helps ensure that all requirements are fulfilled throughout the
development process.
• Prototyping:
• Prototyping Techniques: Building prototypes can be a valuable approach for validating and refining
requirements. Prototypes help stakeholders visualize the system early in the development process and
provide feedback.

• Validation and Verification:

• Validation: Ensuring that the system meets the user's needs and expectations. Validation activities
include reviews, inspections, walkthroughs, and user demonstrations.
• Verification: Confirming that the requirements are well-defined, complete, and consistent. Verification
activities involve techniques such as inspections and reviews.
• Change Management:
• Change Control Process: Establishing a process for handling changes to requirements. This includes
assessing the impact of changes, obtaining approval, and updating documentation accordingly.
• Communication and Collaboration:
• Stakeholder Collaboration: Involving stakeholders throughout the requirements engineering process is
essential for gathering accurate and complete requirements. Effective communication ensures that all
parties have a shared understanding of the requirements.