You are on page 1of 17

HND :: SAD 1. Different Life Cycle Models 2. Agile Life Cycle Models 2 . Heavy Weight vs.

HND :: SAD Recall: Which Life Cycle models do you remember? 3 .

HND :: SAD Software Life Cycle (Waterfall) Spiral V-Model RAD DSDM XP RUP Iterative Incremental Evolutionary Formal Systems Development Cleanroom Ad hoc/Code and Fix and more… 4 .

HND :: SAD Discuss: What are the special features about each of the Life Cycle Models listed? 5 .

HND :: SAD Discuss: Why do we need so many different Life Cycle Models? 6 .

7 .HND :: SAD Heavy Weight or Plan Driven Life Cycle Models focus on documenting and creating a plan before each part of the process[HV]. They can often incur extra costs because of the emphasis on following strict guidelines in the process[HV].

Formal change control with Change Control Boards Project stage gates requiring formal approval in order to proceed Well defined project roles with separation of duties Development iterations tend to be few and long (measured in months. formal project reviews. quarters. or greater) 8 . documented status reports with great deal of details.HND :: SAD Heavy-Weight or Plan-driven methodologies are often/have: Milestone driven Documentation is formal and structured Planning cycle is formal and ongoing Team meetings.

9 .HND :: SAD Agile or Lightweight Life Cycle Models spend less time on planning and design early in the process to deliver something of value to the client early as soon as possible[HV].

”[Agile] 10 .HND :: SAD “Agile Software Development is: an iterative and incremental (evolutionary) approach to software development which is performed in a highly collaborative manner by self-organizing teams with "just enough" ceremony that produces high quality software in a cost effective and timely manner which meets the changing needs of its stakeholders.

HND :: SAD  Code-based deliverable driven (vs. brief project reviews. documents in plandriven)  People oriented with informal but constant communications  Initial planning cycle is formal but on-going planning is “as needed”  Limited team meetings. documented status reports with low details  Limited or no formal change control within iterations  Limited project stage gates requiring formal approval in order to proceed  Development iterations tend to be frequent and many (measured in days or weeks) 11 .

HND :: SAD Discuss: Why/When do/can Heavy Weight Life Cycle Models fail? 12 .

13 . describe and discuss different techniques that attempt to tackle problems with Heavy Weight Life Cycle Models.HND :: SAD Discuss: From the items discussed above.

HND :: SAD Discuss: Which of the Life Cycle Models list are Heavy Weight and Agile Models? Why? 14 .

HND :: SAD Discuss: When are Agile Methods better suited than Heavy Weight Methods? When are Heavy Weight Methods better suited than Agile Methods? 15 .

2005. [SOM] Ian Sommerville. Prentice Hall. “Software Engineering”. [SAD] Donald Yeates and Tony Wakefield. Pearson. 9th Edition. “Systems Analysis and Design”. “BTEC Higher National in Computing”. System Analysis Notes (2009/2010) 16 .HND :: SAD [HND] edexcel. Pearson Educational Limited.

[Agile] “The Art of Agile Development” by James Shore & Shane Warden. Martin Gaedke Notes available from Faculty Connection 17 .-Ing. Ltd. John Wiley and Sons. 2008. 3rd Edition. “ Software Engineering Principles and Practice”. O’Reilly 2007. [Ing] Dr.HND :: SAD [HV] Hans Van Vliet.