Agilefebrian | erlien | beny | ragnar | billy

SLDC Methodologies

WaterfallHybrid

WaterfallIncremental

IterativeAgile

Agile• A collection of methodologies that’s derived from both

Iterative and Incremental approaches to development to provide customer value• Has no set phases, but proceeds iteratively instead with short

cycles• Requirements are planned for, implemented, tested, and

evaluated repeatedly in a matter of weeks, not months• The customer is always involved.

Agile : Philosophy and Values

• Responding to change over following a plan• Individuals and interactions over processes and tools• Working software over comprehensive documentation• Customer Collaboration over contract negotiation

Agile Modelling Principles• Develop software as primary goal• Enable the next effort as secondary goal• Minimize modeling activity-few and

simple• Embrace change and change

incrementally• Model with a purpose• Build multiple models

Agile Modelling Principles (Cont’d)• Build high-quality models and get feedback

rapidly• Focus on content rather than

representation• Learn from each other with open

communication• Know the models and how to use them• Adapt to specific project needs

Agile Project Character

Iterative Modular

Parsimony Incremental

Time Boxing

Agile Project Character

Adaptive Convergent

People OrientedCollaborative

Agile Modelling Practices• Iterative and incremental modelling• Teamwork• Simplicity• Validation• Documentation• Motivation

Advantages

• Adaptive to changing Environment• Ensures Customer’s Satisfaction• Least Documentation• Reduce Risks of Errors

Disadvantages

• Customer interaction as the key factor• Least Documentation• Time consuming, Wasted resource of change

management• More helpful for management than developer

Agile and Rapid (Pros)

• the system development is focused for the customer’s need and divided into modules so that the system can be developed by focusing a single module until it completely meets the customer’s requirements.

Agile

• process promotes strong collaborative atmosphere that can help to improve productivity in the system development, and gives dynamic requirements gathering. The focus of the development is the requirements to be achieved set by the business owner, where business owner actively participate during the development by involved in the prototyping, writing test cases, and performing unit testing.

RAD

Agile and Rapid (Cons)

Agile• Each of the short iterations might

only add too little functionality, which will delay the final iteration where the system is completed.

• Problematic to integrate the system developed into one complete system if the modules are distributed into several development team

• Produce very little documentation

RAD• Requires strong cohesive

teams and commitments in its personnel in order to realize the system development and to meet the business owner’s goal

• Requires participation from the business owner, analysts, developers, and others who are involved for the system function development.

Q & A

Thank You