现代软件工程教案_5.ppt

* * Chapter 4 Requirements Engineering Requirements Engineering Tasks Inception Elicitation Elaboration Negotiation Specification Validation Requirements Management Content * What do you think after construction? “I know you believe you understood what you think I said, but I am not sure you realise that what you heard is not what I meant……” * WHAT IS A REQUIREMENT ? SwReq_1: The item shall ... SwReq_2: ... ….. SwReq_X: ... Requirement: contractual condition and/or capability (external customer(*)) industrial constraint (system engineering group, marketing, ...) states WHAT the system/software item must do, not HOW it does it. Specification: a list of technical requirements Requirement traceability, necessary to ensure development coherence * TYPES OF SYSTEM EQUIREMENTS 1 2 3 Functional technical requirements Capabilities Dynamic behaviour Data manipulation Non-functional technical requirements Operational security Safety Availability Reliability Maintainability Ergonomics Performance Constraints Non-technical requirements Contractual milestones Required methods and techniques * Characteristics of excellent requirement Complete Correctness Feasible Necessary Implementation independence Prioritize Requirements Unambiguous Verifiable Right level of detail * Characteristics of excellent Specification Complete Consistent Concise Modifiable Traceable * Requirement engineering important Is a software process action starting communication continues into modeling activity Is a bridge to design and construction Is to understand the needs of process, project, product and people Is a key problem lead to a failed software project * Requirements Engineering Tasks Inception—ask a set of questions that establish … basic understanding of the problem the people who want a solution the nature of the solution that is desired, and the effectiveness of preliminary communication and collaboration between the customer and the developer Elicitation—elicit requirements fro