Requirement Engineering(BS COMPUTER SCIENCE).pptx

Software Engineering

1. REQUIREMENT ENGINEERING Presented By: Ajoc , Prince Carl Baker , Jerette Jean Comandante Karen

2. INTRODUCTION Requirement engineering is a fundamental process in software development. It involves gathering, analyzing, documenting, and managing the needs and expectations of stakeholders for a software system.

3. Importance of Requirement Engineering Effective requirement engineering ensures that the software system meets the needs of its users. It reduces the risk of costly rework and delays, leading to a successful software development process. Clear Communication Reduces miscommunication and misunderstandings between stakeholders, developers, and users. Reduced Costs Early identification and resolution of issues minimize rework and delays, ultimately saving time and money. Improved Quality Well-defined requirements lead to software that meets user expectations and performs as intended. Increased Success Rate A robust requirement engineering process increases the likelihood of successful software projects, meeting deadlines and delivering value.

4. Stakeholder Identification and Analysis Identifying and understanding stakeholders is crucial. This involves mapping out all individuals or groups with an interest in the software system and analyzing their roles, needs, and expectations. Internal Stakeholders Employees within the organization, including developers, project managers, and business analysts. External Stakeholders Individuals or organizations outside the organization, such as customers, users, regulatory bodies, and partners. Analysis Techniques Stakeholder analysis methods include interviews, surveys, workshops, and document review.

5. Requirement Elicitation Techniques Elicitation techniques are employed to extract requirements from stakeholders. The process involves gathering detailed information and understanding their needs and expectations. Interviews Structured conversations with stakeholders to gather detailed information about their needs and expectations. Surveys Questionnaires used to gather feedback and data from a large group of stakeholders. Workshops Collaborative sessions involving stakeholders, developers, and other team members to brainstorm ideas and reach consensus on requirements. Document Review Examining existing documentation, such as business requirements, user stories, and use cases, to identify requirements.

6. Requirement Documentation and Specification Clearly documenting requirements is essential. This involves creating a comprehensive document that captures all aspects of the software system, serving as a reference for development and testing. Type Description Functional Requirements Describe the specific functions the system must perform. Non-Functional Requirements Define the quality attributes and constraints of the system, such as performance, security, and usability. User Stories Short, user-centric descriptions of a feature from the perspective of a user. Use Cases Detailed descriptions of how users interact with the system to accomplish specific tasks.

7. Requirement Validation and Verification Validation ensures that the requirements meet the needs of stakeholders. Verification checks that the requirements are consistent, complete, and unambiguous. Validation Does the software system meet the needs of its intended users? Verification Are the requirements clear, consistent, complete, and unambiguous? Testing Testing activities confirm that the software system meets the defined requirements.

8. Requirement Management and Traceability Requirement management involves controlling the evolution of requirements throughout the development lifecycle. Traceability ensures that each requirement can be linked to its source and its impact on other requirements. Requirement Tracking Maintain a record of changes and modifications to requirements. Version Control Track different versions of requirements and manage their evolution. Documentation Maintain a comprehensive record of all requirements and their associated documentation. Traceability Link requirements to other related artifacts, such as design documents, test cases, and code.

9. Conclusion and Best Practices Effective requirement engineering is essential for successful software development. By following best practices, organizations can ensure that their software systems meet the needs of their stakeholders and deliver value. Early Involvement Engage stakeholders early in the process to ensure that their needs are fully understood. Clear Communication Use clear and concise language to document requirements. Continuous Feedback Solicit feedback from stakeholders throughout the process. Prioritization Focus on the most critical requirements and address them first. Testing and Validation Validate and verify requirements throughout the process to ensure accuracy. Traceability Maintain traceability between requirements and other related artifacts.