Đang chuẩn bị liên kết để tải về tài liệu:
Lecture Software engineering: Chapter 4 – Requirements Engineering

This lecture discusses the key concepts of project scope management. Scope is defined as work to be done to create products. Another term ‘deliverable’ is used to describe products that are further divided into product-related (e.g. software component) and process-related (e.g. minutes of meeting) deliverables. Stakeholders’ agreement is quite important for the newly developed products. | Chapter 4 – Requirements Engineering Chapter 4 Requirements Engineering 1 30/10/2014 Topics covered Functional and non-functional requirements Requirements engineering processes Requirements elicitation Requirements specification Requirements validation Requirements change Chapter 4 Requirements Engineering 2 30/10/2014 Requirements engineering The process of establishing the services that acustomer requires from a system and the constraints under which it operates and is developed. The system requirements are the descriptions of the system services and constraints that are generated during the requirements engineering process. Chapter 4 Requirements Engineering 3 30/10/2014 What is a requirement? It may range from a high-level abstract statement of a service or of a system constraint to a detailed mathematical functional specification. This is inevitable as requirements may serve a dual function May be the basis for a bid for a contract - therefore must be open to interpretation; May be the basis for the contract itself - therefore must be defined in detail; Both these statements may be called requirements. Chapter 4 Requirements Engineering 4 30/10/2014 Requirements abstraction (Davis) Chapter 4 Requirements Engineering 5 “If a company wishes to let a contract for a large software development project, it must define its needs in a sufficiently abstract way that a solution is not pre-defined. The requirements must be written so that several contractors can bid for the contract, offering, perhaps, different ways of meeting the client organization’s needs. Once a contract has been awarded, the contractor must write a system definition for the client in more detail so that the client understands and can validate what the software will do. Both of these documents may be called the requirements document for the system.” 30/10/2014 Types of requirement User requirements Statements in natural language plus diagrams of the services the system provides and its operational | Chapter 4 – Requirements Engineering Chapter 4 Requirements Engineering 1 30/10/2014 Topics covered Functional and non-functional requirements Requirements engineering processes Requirements elicitation Requirements specification Requirements validation Requirements change Chapter 4 Requirements Engineering 2 30/10/2014 Requirements engineering The process of establishing the services that acustomer requires from a system and the constraints under which it operates and is developed. The system requirements are the descriptions of the system services and constraints that are generated during the requirements engineering process. Chapter 4 Requirements Engineering 3 30/10/2014 What is a requirement? It may range from a high-level abstract statement of a service or of a system constraint to a detailed mathematical functional specification. This is inevitable as requirements may serve a dual function May be the basis for a bid for a contract - therefore must be open to interpretation; May