Đang chuẩn bị liên kết để tải về tài liệu:
Lecture Software requirements engineering - Lecture­ 28: Requirements engineering in agile methods

After this chapter the student should have acquired the following knowledge and skills: Measuring software complexity, desirable properties of complexity metrics, cyclomatic complexity, converting code to graph, unit testing: path coverage,. | Requirements Engineering in Agile Methods Lecture-28 Recap 2 How traceability information is used in change impact analysis? Impact on time Impact on cost Requirement engineering in agile methods Today’s lecture 3 Requirement engineering for agile methods The Agile Manifesto Manifesto includes following points: Individuals and Interactions over Process and Tools Customer Collaboration over Contracts Working Software over Documentation Responding to Change over Planning From such values, a set of common practices and behaviors are identifies. Adaptability Incremental Development Frequent Releases Requirements Prioritization Before Every Iteration High Customer Involvement Team Size in Agile Methods Read more: http://www.devx.com/architect/Article/32836/0/page/2 Agile Approaches to Requirements Engineering The Customer In AMs, the customer assumes a vital role. Usually, the term “customer” identifies a set of stakeholders that belongs to the organization that is paying for the . | Requirements Engineering in Agile Methods Lecture-28 Recap 2 How traceability information is used in change impact analysis? Impact on time Impact on cost Requirement engineering in agile methods Today’s lecture 3 Requirement engineering for agile methods The Agile Manifesto Manifesto includes following points: Individuals and Interactions over Process and Tools Customer Collaboration over Contracts Working Software over Documentation Responding to Change over Planning From such values, a set of common practices and behaviors are identifies. Adaptability Incremental Development Frequent Releases Requirements Prioritization Before Every Iteration High Customer Involvement Team Size in Agile Methods Read more: http://www.devx.com/architect/Article/32836/0/page/2 Agile Approaches to Requirements Engineering The Customer In AMs, the customer assumes a vital role. Usually, the term “customer” identifies a set of stakeholders that belongs to the organization that is paying for the development of a software product. In the case of mass-products for which there are no organizations paying directly for the product, the development team has to identify an expert in the area (e.g., a marketing expert) that is able to act as the customer and participate in the development of the product. This approach is feasible only if the size of the problem is limited and a single person can act as customer, representing all the stakeholders. Agile Approaches to Requirements Engineering The customer-on-site practice defines some specific requirements for the customer: Availability: The customer has to be always available to answer questions coming from the development team. Any delay in the answer delays the development of the product. Complete Knowledge: The customer is the representative for all the stakeholders. Therefore, he is able to answer all questions, since he is the domain expert and knows how the application should work and the input/output data required. Again, this is .