Agile Process Models
• Agile Modeling (AM)
• Agile Unified Process (AUP)
Agile Modelling (AM)
A practice based methodology for effective modeling and
documentation of software based systems
It’s a collection of values , principles and practices for modeling
software that can be applied on a software development project
in an effective and light weight manner
Agile Modelling (AM)
• more flexible and more effective than traditional modeling
methods, making it a better fit in a fast changing environment.
• part of the agile software development tool kit.
• a supplement to other agile development methodologies such
as Scrum, extreme programming (XP), and Rational Unified
Process (RUP).
• explicitly included as part of the disciplined agile delivery (DAD)
framework. As per 2011 stats, agile modeling accounted for 1%
of all agile software development.
Agile Modelling (AM)
AM suggests a wide range of core and supplementary modeling
principles :
• Model with a purpose
• Use multiple models
• Travel light
• Content is more important than the representation
• Know the models and tools used to create them
• Adapt locally
Agile Unified Process
• simplified version of the Rational Unified Process (RUP) developed
by Scott Ambler.
• simple, easy to understand approach to developing business
application software using agile techniques and concepts yet still
remaining true to the RUP.
• The AUP applies agile techniques including test-driven development
(TDD), agile modeling (AM), agile change management, and database
refactoring to improve productivity.
• In 2011 the AUP accounted for one percent of all the agile
methodologies used.[2] In 2012 the AUP was superseded by disciplined
agile delivery (DAD). Since then work has ceased on evolving AUP.
Agile Unified Process
• Adopts “serial in large” and “iterative in small” philosophy for
building computer based systems
• By adopting the Unified Process phased activities like : —
inception, elaboration, construction, and transition —AUP
provides a serial overlay (i.e., a linear sequence of software
engineering activities) that enables a team to visualize the
overall process flow for a software project
Agile Unified Process
Each AUP iteration addresses the following activities :
• Modeling: UML (Unified Modeling Language ) representations
of the business and problem domains are created. However, to
stay agile, these models should be “just barely good enough” to
allow the team to proceed.
• Implementation: Models are translated into source code.
• Testing: Like XP, the team designs and executes a series of
tests to uncover errors and ensure that the source code meets
its requirements.
• Deployment: focuses on the delivery of a software increment
and the acquisition of feedback from end users.
Agile Unified Process
• Configuration and project management:
▪ configuration management addresses (1) change management, (2)
risk management, and the (3) control of any persistent work products
that are produced by the team.
▪ Project management tracks and controls the progress of the team and
coordinates team activities.
• Environment management: coordinates a process
infrastructure that includes standards, tools, and other support
technology available to the team.
Thank you
