Anda di halaman 1dari 7

ISLAMIA CHARTED UNIVERSITY PESHAWER

TOPIC
AGILE DEVELOPMENT MODEL
SUBJECT
SOFTWARE ENGINEERING 01

SUBMITTED BY:
MUSSAWIR IQBAL
CLASS NO:
BS - 655
SUBMITTED TO:
Mr. SAJJAD KTK
SUBMITTED DATE:
19/10/2014

COMPUTER SCIENCE DEPARTMENT
AGILE DEVELOPMNET MODEL

1: Definition
Agile development model is also a type of Incremental model. Software is developed in
incremental, rapid cycles. This results in small incremental releases with each release building on
previous functionality. Each release is thoroughly tested to ensure software quality is maintained.
It is used for time critical applications. Extreme Programming (XP) is currently one of the most
well known agile development life cycle model.
Diagram of Agile Model:


2: Elements of Agile Modeling
Agile Modeling consists of three components which are related in the following way:
AM practices are based on several values and proven software engineering principles [Source:
Agile Modeling]. To understand Agile Modeling, rst we must understand the purpose of these
components and how they can be applied in Software Engineering.
2.1 Values
A value is dened by The American Heritage Dictionary as a principle, standard, or
quality considered worthwhile or desirable [Source: dictionary.com]. In Agile Modeling, there
are ve principal values. These are communication, simplicity, feedback, courage, and humility
[Source: An Introduction to Agile Modeling]. The rst three values pertain to the role of models
within a project, and the remaining values describe desirable personality traits of software
designers.
Models facilitate communication between the designers and the customer, and between
the designers and developers. Models promote simplicity both by clarifying design problems and
representing programming concepts in a more understandable or generalized manner. Models
help designers to obtain feedback quickly, allowing them to act on the advice they receive.
Designers require courage to make decisions, and also to admit mistakes and change
direction if necessary. Designers require humility to recognize the abilities of other team
members and value their contributions.

2.2 Principles
Next, lets see how these values lead to principles. WordNet 2.01 denes a principle as a
basic generalization that is accepted as true and that can be used as a basis for reasoning or
conduct [Source: dictionary.com]. Agile Modeling contains two kinds of principles: core
principles and supplementary principles [Source: Agile Modeling Principles]. Core principles of
Agile Modeling include:
Assume Simplicity The simplest solution is the best solution.
Embrace Change Requirements and available technologies change over time. An approach
to development can only be successful if it embraces the reality of change.
Enabling the Next Eort is Your Secondary Goal Ensure robustness of the current system
before you even think about the next version.
Incremental Change Dont insist that a model be perfect the rst time. Start with an
incomplete or generalized model and rene it over time.
Maximize Stakeholder Investment Customers deserve nal say in determining the
distribution of resources.
Model With a Purpose This requires knowing your audience. Before creating a model,
determine its purpose and its audience, and then develop the model just until it is suciently
detailed and accurate to serve its purpose, and not more.
Multiple Models Be aware of the types of models available: UML Class & Activity
Diagrams, Change Cases & Use Cases, CRC Models, Communication Diagrams, Constraint
denitions, UML Deployment Diagrams, Flowcharts, etc. Just as a particular repair job at home
is best completed using more than one tool from your toolbox, a particular project generally
requires multiple modeling techniques.
Quality Work Do quality work.
Rapid Feedback Obtained by working closely with the customer.
Software Is Your Primary Goal Remember that documentation, models, etc. are a means to
an end, and not the end itself. The nal product is the software.
Travel Light Keep the number & complexity of models within your project to a minimum, to
reduce the cost of updating and maintaining models. Supplementary principles of Agile
Modeling include:
Content is More Important Than Representation Consider whiteboards or post-it notes as
an alternative to CASE tools. These allow you to take advantage of the benets of modeling
without incurring the costs of creating and maintaining documentation. [Source: Agile
Modeling Principles]
Open and Honest Communication Enables people to share ideas or even admit
shortcomings, which in turn enables the team to make decisions based upon more accurate
information. Previously, there were more principles in Agile Modeling, which were deprecated
in favour of simplication in January, 2005. These included: Everyone Can Learn From
Everyone Else, Know Your Models, Know Your Tools, Local Adaptation, and Work With
Peoples Instincts.
2.3 Practices
Finally, lets examine how the values and principles discussed above lead to the practices
of Agile Modeling. Well start with the denition of practices given by The American Heritage
Dictionary 1WordNet R 2.0, c 2003 Princeton University 4[Source: dictionary.com]: practice is
the process of doing something such as a performance or action. Again, Agile Modeling
subdivides practices into two groups: core and supplementary practices. Core practices of Agile
Modeling include:
Active Stakeholder Participation This is analogous to XPs On-Site Customer. The idea is
to have the customer and end user participate in requirements elicitation and prioritization of
requirements.
Apply the Right Artifact(s) Know the types of models available, and choose one that
concisely conveys information while allowing exibility to change the design.
Collective Ownership Applies to all models and all artifacts.
Create Several Models in Parallel This technique helps to create a fuller understanding of
the system or subsystem, while helping to determine which model represents the system most
simply, fully and accurately.
Create Simple Content Analogous to XPs practice of Simple Design.
Depict Models Simply Models should basically highlight key features.
Display Models Publicly Preferably create a modeling wall.
Iterate to Another Artifact If one modeling tool is insucient, try another.
Model in Small Increments Incremental development allows more rapid prototyping.
Model With Others Use modeling to develop a common vision on a project.
Prove it With Code Prove the ecacy of nished models by implementing them.
Single Source Information Minimize the redundancy between models.
Use the Simplest Tools Consider Whiteboards or paper as an alternative to modeling tools.















Figure 1: How AM Practices Fit Together [Source: AM Practices]
Supplementary practices include:
Apply Modeling Standards No explanation necessary.
Apply Patterns Gently When applying a pattern, create the minimal infrastructure necessary
for the pattern while structuring the code in such a way that it would be easy to refactor and
apply the full-edged pattern later, if that turns out to be the easiest solution.
Discard Temporary Models Do not update or keep models that have outlived their
usefulness.
Formalize Contract Models Create a contract model whenever an external group controls an
information resource that the system requires, such as a database, legacy application or
information service.
Update Only When It Hurts or only when you absolutely have to. Deprecated practices
include: Consider testability, model to communicate, model to understand, and reuse existing
resources. Finally, not included as practices are the following complementary strategies,
generally grouped as Really Good Ideas: Refactor, and practice Test-First Design.

3: When to use Agile Model:
When new changes are needed to be implemented. The freedom agile gives to change is
very important. New changes can be implemented at very little cost because of the
frequency of new increments that are produced.
To implement a new feature the developers need to lose only the work of a few days, or
even only hours, to roll back and implement it.
Unlike the waterfall model in agile model very limited planning is required to get started
with the project. Agile assumes that the end users needs are ever changing in a dynamic
business and IT world. Changes can be discussed and features can be newly effected or
removed based on feedback. This effectively gives the customer the finished system they
want or need.
Both system developers and stakeholders alike, find they also get more freedom of time and
options than if the software was developed in a more rigid sequential way. Having options
gives them the ability to leave important decisions until more or better data or even entire
hosting programs are available; meaning the project can continue to move forward without
fear of reaching a sudden standstill.
4: When not to use Agile Model:
Agile Modeling does not work well in organizations that have a prescriptive culture or for
teams that are very large and/or distributed [Source: Modeling and Documentation Rethunk].
5: Advantages of Agile Model:
Customer satisfaction by rapid, continuous delivery of useful software.
People and interactions are emphasized rather than process and tools. Customers, developers
and testers constantly interact with each other.
Working software is delivered frequently (weeks rather than months).
Face-to-face conversation is the best form of communication.
Close daily cooperation between business people and developers.
Continuous attention to technical excellence and good design.
Regular adaptation to changing circumstances.
Even late changes in requirements are welcomed
6: Disadvantages of Agile Model:
In case of some software deliverables, especially the large ones, it is difficult to assess the
effort required at the beginning of the software development life cycle.
There is lack of emphasis on necessary designing and documentation.
The project can easily get taken off track if the customer representative is not clear what
final outcome that they want.
Only senior programmers are capable of taking the kind of decisions required during the
development process. Hence it has no place for newbie programmers, unless combined with
experienced resources.

Anda mungkin juga menyukai