tailieunhanh - Lecture Software requirements engineering - Lecture­ 27: Requirements management

After this chapter the student should have acquired the following knowledge and skills: Structural cohesion metrics, internal cohesion or syntactic cohesion, external cohesion or semantic cohesion. | Requirements Management Lecture-27 Recap 2 Requirements traceability Types of traceability information Types of traceability Traceability lists and tables Traceability policies Cost analysis 3 What do we want here? Time Cost Using traceability information 4 Requirements requirements Requirements design Requirements code Project schedule 5 Gant chart Identify activities Rework policy Delay in activities delay in cost 6 7 Requirements Management Validation Inception Elicitation Elaboration Negotiation Specification Requirements Engineering for Agile Methods 8 Introduction The principle of lean production is the constant identification and removal of waste (muda in Japanese), that is, anything that does not add value for the customer to the final product. Being rooted on lean production, AMs focus on: Delivering value for the customer Ensuring that the customer understand such value and be satisfied by the project 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 Summary 11 How traceability information is used in change impact analysis? Impact on time Impact on cost Requirement engineering in agile methods | Requirements Management Lecture-27 Recap 2 Requirements traceability Types of traceability information Types of traceability Traceability lists and tables Traceability policies Cost analysis 3 What do we want here? Time Cost Using traceability information 4 Requirements requirements Requirements design Requirements code Project schedule 5 Gant chart Identify activities Rework policy Delay in activities delay in cost 6 7 Requirements Management Validation Inception Elicitation Elaboration Negotiation Specification Requirements Engineering for Agile Methods 8 Introduction The principle of lean production is the constant identification and removal of waste (muda in Japanese), that is, anything that does not add value for the customer to the final product. Being rooted on lean production, AMs focus on: Delivering value for the customer Ensuring that the customer understand such value and be satisfied by the project 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 Summary 11 How traceability information is used in change impact analysis? Impact on time Impact on cost Requirement engineering in agile methods