The Confounding World of Process Methodologies By Thelma Hataria.

Slides:



Advertisements
Similar presentations
Software Development Practices and Methodologies Svetlin Nakov Telerik Corporation
Advertisements

Agile Software Development کاری از : مهدی هوشان استاد راهنما : استاد آدابی.
SDLC – Beyond the Waterfall
Software Development Life-Cycle Models
Software development process improvement Ville Wettenhovi Master thesis presentation Supervisor:Professor Jukka Manner Instructor:M.Sc. Markus Aalto Date:23th.
COPYRIGHT © 2012 ALCATEL-LUCENT. ALL RIGHTS RESERVED. 1 Agile documentation development methodology Giby Panicker and Judith Benjamin 1-Dec-2012.
PROC-1 3. Software Process. PROC-2 What’s a process? Set of activities in creating software It involves creativity –hard to automate –Requires human judgment.
INFO415 Approaches to System Development: Part 1
Sharif University of Technology Session # 3.  Contents  Systems Analysis and Design Sharif University of Technology MIS (Management Information System),
Agile development By Sam Chamberlain. First a bit of history..
Software Life Cycles ECE 417/617: Elements of Software Engineering
Agile
Gu & Maher University of Sydney, October 2004 DECO2005 Monitoring Team Process.
Extreme Programming Collaboration in Software Development Process.
Computer Engineering 203 R Smith Agile Development 1/ Agile Methods What are Agile Methods? – Extreme Programming is the best known example – SCRUM.
CHAPTER 9: LEARNING OUTCOMES
Objectives Explain the purpose and various phases of the traditional systems development life cycle (SDLC) Explain when to use an adaptive approach to.
Software Development Overview CPSC 315 – Programming Studio Spring 2008.
Agile software development is a group of software development methodologies based on iterative and incremental development, where requirements and solutions.
Introduction to Agile Methodologies and Concepts Roy Osherove Principal, Team Agile Blog : ISerializable.com.
Introduction to Agile.
Software Development Life Cycle (SDLC)
Software Development Process
Solar Tech Chuck Hess, CEO Jamie Tofte, CFO Christina Cruz, CTO.
Chapter 5 Software Process Models. Problems with “Traditional” Processes 1.Focused on and oriented towards “large projects” and lengthy development time.
Current Trends in Systems Develpment
By Saravanan Bala. General Report 31 % of Software projects are cancelled 75 % of the software projects are considered failures by the people who initiated.
CS 360 Lecture 3.  The software process is a structured set of activities required to develop a software system.  Fundamental Assumption:  Good software.
CS CS 5150 Software Engineering Lecture 3 Software Processes 2.
Agile Methodologies: Comparative Study and Future Direction 林佳蓁 資工 4B.
Object-oriented Analysis and Design Stages in a Software Project Requirements Writing Analysis Design Implementation System Integration and Testing Maintenance.
Agile
Chapter 2 Iterative, Evolutionary, and Agile You should use iterative development only on projects that you want to succeed. - Martin Fowler 1CS
Rational Unified Process Mr Hisham AlKhawar. Iterative versus Waterfall  We need to use a life cycle model in order to approach developing a system easily,
Software Engineering process models
Chapter 2 Software processes. Topics covered Software process models Process activities Coping with change.
CS CS 5150 Software Engineering Lecture 2 Software Processes 1.
Basic Approach Development driven by time boxing May sacrifice requirements in order to keep schedule (time boxed) Steer project as you go based on user.
Solar Tech Chuck Hess, CEO Jamie Tofte, CFO Christina Cruz, CTO.
WATERFALL DEVELOPMENT MODEL. Waterfall model is LINEAR development lifecycle. This means each phase must be completed before moving onto the next!!! WHAT.
Copyright © 2009 Pearson Education, Inc. Publishing as Prentice Hall Appendix B Agile Methodologies B.1.
1/2/12 Chapt 2 Iterative Evolutionary Agile. 1/2/12 (Rational) Unified Process A software development process – Flexible and open Other processes – XP.
Agenda: Overview of Agile testing Difference between Agile and traditional Methodology Agile Development Methodologies Extreme Programming Test Driven.
Intelligence and Information Systems 1 3/17/2004 © 2004 Raytheon Company USC/CSE Executive Workshop on Agile Experiences March 17, 2004 A Raytheon Agile.
It’s Agile …. like! A Corkman’s introduction to Agile software delivery.
Meghe Group of Institutions Department for Technology Enhanced Learning 1.
Software Development Process CS 360 Lecture 3. Software Process The software process is a structured set of activities required to develop a software.
Agile Development Chapter 10 - part 2. Agile Philosophy  A guiding philosophy and set of guidelines for : developing information systems in an unknown,
Copyright 2015, Robert W. Hasker. Classic Model Gathering Requirements Specification Scenarios Sequences Design Architecture Class, state models Implementation.
Industrial Software Development Process Bashar Ahmad RISC Software GmbH.
AGILE SOFTWARE DEVELOPMENT. Agile software development : Agile software development refers to a group of software development methodologies that promotes.
Software Development. The Software Life Cycle Encompasses all activities from initial analysis until obsolescence Analysis of problem or request Analysis.
Introduction to Agile Development Advanced Software Engineering Dr. Nuha El-Khalili.
Group 6 : - Yesika Kristina Dea Pradana D Sukianti Merianti Meshiya Caterlee
Agile Gintarė Bernotaitytė © 2013.
Software Development.
AGILE SCRUM METHODOLOGY
Methodologies and Algorithms
CSC 355 – Newer Approaches to System Development Life Cycles & Processes, Spring 2017 March 2017 Dr. Dale Parson.
Appendix B Agile Methodologies
Valuable Project Management Tools and Techniques
Agile Software Development
Agile Software Development Brian Moseley.
Lecture Software Process Definition and Management Chapter 2: Prescriptive Process Models Dr. Jürgen Münch Fall
Approaches to Systems Development
روش‌های سريع الانتقال (چابک) توسعه نرم افزار
Chapt 2 Iterative Evolutionary Agile.
Appendix B Agile Methodologies
Chapter 5: New and Emerging Process Methodologies
Presentation transcript:

The Confounding World of Process Methodologies By Thelma Hataria

2 Overview Importance of Methodologies Characteristics of Heavyweight Methodologies Heavyweight Methodologies Advantages and Disadvantages Characteristics of Lightweight methodologies Agile (Lightweight) Methodologies Advantages and Disadvantages Conclusion

3 Definition-Methodology “A methodology is a codified set of practices (sometimes accompanied by training materials, formal educational programs, worksheets, and diagramming tools) that may be repeatedly carried out to produce software”-Wikipedia

4 Importance of Methodologies Earlier method “Code and Fix” Methodologies impose a disciplined process upon software development An inappropriate choice of methodology can lead to delayed delivery, project failure and customer dissatisfaction Making an informed choice will lead to high quality software

5 Types of Methodologies Methodologies Heavyweight Methodologies Lightweight Methodologies

6 Characteristics of Heavyweight Methodologies Plan-Oriented Detailed Documentation Predictive Approach Process Oriented Tool Oriented

7 Heavyweight Methodologies “Waterfall Model” Real heavyweight methodology Phase oriented Changes in requirements are not readily acceptable Minimum customer involvement

8 Heavyweight Methodologies “Spiral Model” Not so heavy Iterative & incremental approach Focuses on risk resolution Plan oriented

9 Heavyweight Methodologies “Rational Unified Process” Lightest heavyweight methodology Focuses on process improvement Iterative approach Changes can be accommodated readily Tool oriented

10 Advantages of Heavyweight Methodologies Safe Approach -“Tried and Tested” Reliable Work towards customer satisfaction High Quality of Software

11 Disadvantages of Heavyweight Methodologies Bureaucratic by nature Detailed activities slow process development

12 Characteristics of Lightweight Methodologies People-Oriented Conformance to Outcomes Adaptive Approach Balancing Flexibility and Planning Decentralized Approach Limited Team Size

13 Lightweight Methodologies “Extreme Programming (XP)” Short iteration cycles (2-3 weeks) Communication and Feedback Concentrates on Productivity Pair Programming Approach Complete customer involvement Frequent Integration

14 Lightweight Methodologies “Scrum” Very short iteration cycles(30 days) Sprint meetings held for each iteration Demonstration of updates Close monitoring through scrum meetings More importance to working software

15 Lightweight Methodologies “Crystal Family” Heavy Lightweight methodology Heaviness of methodology can vary depending on the criticality and size of the project Group of approaches for different team sizes Each team have different set of talent and skills Dependent on advice of experts

16 Advantages of Lightweight Methodologies Flexible approach Accommodate changes Faster delivery Customer satisfaction

17 Disadvantages of Lightweight Methodologies Experts not always on hand Progress cannot be always tracked

18 Conclusion Both classes of methodologies have one goal- ”Software Quality” Project characteristics and organizations goals need to be matched to objectives of the methodology Heavyweight methodologies is the best option when reliability is the issue Lightweight methodologies are needed where customer requirements change constantly

19 Thank you Any questions?