Agile Software Development: Practices and Techniques, Slides of Software Engineering

Download Agile Software Development: Practices and Techniques and more Slides Software Engineering in PDF only on Docsity!

Agile Software Development

Lecture 6

Recap

■ Agile Values ■ Agile Principles

i. Active Stakeholder Participation

■ It describes the need to have on-site access to people, typically users or their representatives, who have the authority and ability to provide information pertaining to the system being built and to make pertinent and timely decisions regarding the requirements, and prioritization thereof.

ii. Apply the Right Artifact(s)

■ Each artifact in development process has its own specific applications. ■ For example, a UML activity diagram is useful for describing a business process. ■ If a picture is worth a thousand words, then a model is often worth 1024 lines of code when applied in the right circumstances.

iv. Several Models

■ Because each type of model has its strengths and weaknesses no single model is sufficient for your modeling needs. You should know how to use different models in different scenarios.

v. Create Simple Content

■ You should keep the actual content of your models -- your requirements, your analysis, your architecture, or your design -- as simple as you possibly can while still fulfilling the needs of your project stakeholders.

vii. Display Models Publicly

■ You should display your models publicly, often on something called a "modeling wall" or a "wall of wonder." This supports open and honest communication on your team because all of the current models are quickly accessible to them, as well as with your project stakeholders because you aren't hiding anything from them. ■ Your modeling wall is where you post your models for everyone to see. It may be physical such as a whiteboard or it may be virtual such as a website.

viii. Iterate to Another Artifact

■ When you are working on a development artifact -- such as a use case, sequence diagram, or even source code -- and find that you are stuck then you should consider working on another artifact for the time being.

x. Model With Others

■ Modeling is a group activity, one in which you want the input of several people working together effectively. You will often find that your development team needs to work together to create the core set of models critical to your project. ■ For example, to develop the architecture for your system, you will often need to model with a group of people to develop a solution everyone agrees on as well as one that is as simple as possible. ■ Most of the time the best way to do this is to talk the issue through with one or more people.

xi. Prove it With Code

■ A model is an abstraction, one that should accurately reflect an aspect of whatever you are building. But will it work? To determine so, you should prove your model with code. ■ You have developed a sketch of an HTML page for accepting billing address information? Code it and show the resulting user interface to your users for feedback.