tailieunhanh - Lecture Software requirements engineering - Lecture­ 29: Requirements engineering in agile methods

After this chapter the student should have acquired the following knowledge and skills: Why measure software, fundamentals of measurement theory, use case points, problem domain modeling, recombining problem frames. | Requirements Engineering in Agile Methods Lecture-29 Recap 2 Requirement engineering in AMs Today’s lecture 3 Requirement engineering in AMs Requirement methods XP and agile principles Incremental development is supported through small, frequent system releases. Customer involvement means full-time customer engagement with the team. People not process through pair programming, collective ownership and a process that avoids long working hours. Change supported through regular system releases. Maintaining simplicity through constant refactoring of code. Customer involvement Customer involvement is a key part of XP where the customer is part of the development team. The role of the customer is: To help develop stories that define the requirements To help prioritize the features to be implemented in each release To help develop acceptance tests which assess whether or not the system meets its requirements. Requirements scenarios In XP, user requirements are expressed as scenarios or user | Requirements Engineering in Agile Methods Lecture-29 Recap 2 Requirement engineering in AMs Today’s lecture 3 Requirement engineering in AMs Requirement methods XP and agile principles Incremental development is supported through small, frequent system releases. Customer involvement means full-time customer engagement with the team. People not process through pair programming, collective ownership and a process that avoids long working hours. Change supported through regular system releases. Maintaining simplicity through constant refactoring of code. Customer involvement Customer involvement is a key part of XP where the customer is part of the development team. The role of the customer is: To help develop stories that define the requirements To help prioritize the features to be implemented in each release To help develop acceptance tests which assess whether or not the system meets its requirements. Requirements scenarios In XP, user requirements are expressed as scenarios or user stories. These are written on cards and the development team break them down into implementation tasks. These tasks are the basis of schedule and cost estimates. The customer chooses the stories for inclusion in the next release based on their priorities and the schedule estimates. Story card for document downloading 7 XP and change Conventional wisdom in software engineering is to design for change. It is worth spending time and effort anticipating changes as this reduces costs later in the life cycle. XP, however, maintains that this is not worthwhile as changes cannot be reliably anticipated. Rather, it proposes constant code improvement (refactoring) to make changes easier when they have to be implemented. Refactoring Refactoring is the process of code improvement where code is reorganised and rewritten to make it more efficient, easier to understand, etc. Refactoring is required because frequent releases mean that code is developed incrementally and therefore tends to become .