Đang chuẩn bị liên kết để tải về tài liệu:
Lecture Requirement engineering - Chapter 3: Software elicitation

Lecture Requirement engineering - Chapter 3: Software elicitation. This chapter presents the following content: What is requirement elicitation? Participants in elicitation, risks of requirements elicitation, requirements elicitation techniques. | What is Requirement Elicitation? Participants in elicitation Risks of requirements elicitation Requirements elicitation techniques The most common causes of poor quality, cost overruns and late delivery of software: Incorrect, incomplete, or misunderstood requirement Requirements elicitation is “the process of discovering the requirements for a system by communicating with customers, system users and others who have a stake in the system development” Gather requirement from various sources: identify requirement providers: stakeholders Analyse the gathered information, looking for implications, inconsistencies or unresolved issues Confirm understanding of the requirements with the users Synthesize appropriate statements of the requirements Requirement elicitation involves many people. Customer/Client: Person who pays for the software development. Ultimately, has the final word on what will be the product Software engineer: Expert who knows the technology and process -> produce the requirements specifications The potential users: of the current system or future systems indicate which functions to maintain .