Software Requirements Engineering (SENG109) PDF
Document Details
Uploaded by UnderstandableCornet
AYBU
Yenal Arslan
Tags
Related
- Introduction to Software Engineering (Lecture 4) 2024f PDF
- Software Engineering 1 Lecture 5 PDF
- CSE241/CMM341 Foundations of Software Engineering Requirements Engineering 2023 PDF
- Software Requirements Engineering (SENG109)
- Software Engineering: Requirements Engineering Process PDF
- SRE Validation PDF
Summary
This document is about software requirements engineering, specifically covering topics like requirements elicitation, analysis, validation, management, prototypes, and verification methods. It also includes examples and diagrams related to these ideas.
Full Transcript
Software Requirements Engineering (SENG109) Assos. Prof. Dr. Yenal ARSLAN @yenalarslan1 https://www.linkedin.com/in/yenalarslan [email protected] Requirements engineering 1. Requirements elicitation; What services do the end-users require...
Software Requirements Engineering (SENG109) Assos. Prof. Dr. Yenal ARSLAN @yenalarslan1 https://www.linkedin.com/in/yenalarslan [email protected] Requirements engineering 1. Requirements elicitation; What services do the end-users require of the system? 2. Requirements analysis; How do we classify, prioritise and negotiate requirements? 3. Requirements validation; Does the proposed system do what the users require? 4. Requirements management; How do we manage the (sometimes inevitable) changes to the requirements document? Requirement Validation According to a survey, around 56% of the problems that arises during software development are the direct results of the errors from the requirement phase. To detect and rectify these errors, developers use requirement validation techniques. It plays an important role in ensuring that the product meets the customer’s expectations Requirement Validation Requirement Validation Requirement Validation Requirement Validation Developing Checklists Developing Checklists These checks are performed during requirements validation phase to ensure the following things: The requirements should be consistent with other requirements, which means no two requirements should conflict or oppose each other. The requirements should be practically achievable. The requirements should be complete in every sense. The requirements must contain all relevant information. The requirements must address the actual needs of the system The requirements must be understandable by the stakeholders Every requirement must be described in a way that precludes different interpretation Peer Review Peer Review Prototype Prototype Prototype Prototype Prototype Prototype Requirement Validation Requirement Verification Requirement verification is the activity of checking that the implementation, building of a component, and the system itself has been done correctly in accordance with the specified requirements. It consists of few confirmation checks performed throughout the product life cycle to ensure that the design, iterations, and the finished system fully meets the requirements. Those checks are: Inspection Analysis Demonstration Test Expert review Requirement Verification Requirement Verification ISO 29119