CH02_Software_development_life_cycle (1).pptx
- 1. Systems Analysis and Design Slides in this presentation contain hyperlinks. JAWS users should be able to get a list of links by using INSERT+F7 Chapter 2: Software development life cycle
- 2. Learning Objectives 1.1 Choose the right SDLC 1.2 Describe the RUP methodologies 1.3 Describe the Agile methodologies 1.4 The great methodologies debate
- 3. 68% of all Software Projects fail – ZDNET 1.1 Choose the right SDLC • McKinsey – 17% of large IT Projects fail miserably • Geneca - Large IT Projects run 45% over budget, 7% over time, delivering 56% less value • 75% Project participants lack confidence in their project
- 4. Software Projects fail from around 5 to 47 factors – Alexandria University 1.1 Choose the right SDLC • Organizational Structure • Badly Defined Requirements • Unrealistic or Unarticulated goals • Inability to handle project complexity • Sloppy development practices • Inaccurate estimates
- 5. Project failures can be controlled 1.1 Choose the right SDLC • Delivery dates impact project delivery • Projects estimations can be made as close as possible • Risks can be re-assessed, controlled and managed • Staff can be awarded for long work hours
- 6. Unified Software Development Process 1.1 Choose the right SDLC • Rational Unified Process • Agile Unified Process • Basic Unified Process • Enterprise Unified Process • Essential Unified Process • Open Unified Process • Oracle Unified Method • RUP-Systems Engineering
- 7. Agile methodology 1.1 Choose the right SDLC • Kanban • Scrum • XP • Feature-driven development (FDD) • Dynamic Systems Development Method (DSDM) • Crystal • Lean
- 8. What is Rational Unified Process ? 1.2 Describe the RUP methodologies A software engineering process based on best practices in modern software development A disciplined approach to assigning and managing tasks and responsibilities in a development organization Focus on high quality software that meets the needs of its end users within a predictable schedule and budget A process framework that can be tailored to specific organization or project needs RUP is a methodology for delivering projects in a maximum performance manner ?
- 9. RUP uses an integration of approaches & initiatives 1.2 Describe the RUP methodologies Team-Unifying Approach The RUP unifies a software team by providing a common view of the development process and a shared vision of a common goal Increased Team Productivity knowledge base of all processes view of how to develop software modeling language Rational provides many tools Designer / Developer Analyst Tester Architect Tool Specialist Release Engineer Project Management
- 10. Key Aspects of RUP 1.2 Describe the RUP methodologies Risk-driven process Risk management integrated into the development process Iterations are planned based on high priority risks Use-Case driven development Use cases express requirements on the system’s functionality and model the business as context for the system Use cases are defined for the intended system and are used as the basis of the entire development process Architecture-centric design Architecture is the primary artefact to conceptualize, construct, manage, and evolve the system Consists of multiple, coordinated views (or models) of the architecture
- 11. Rational Unified Process – Snapshot 1.2 Describe the RUP methodologies Project Management Environment Supporting Workflows Configuration & Change Mgmt Business Modeling Implementation Test Analysis & Design Process Workflows Deployment Requirements Preliminary Iteration(s) Iter. #1 Phases Iterations Iter. #2 Iter. #n Iter. #n+1 Iter. #n+2 Iter. #m Iter. #m+1 Elaboration Transition Inception Construction time content
- 12. Dynamic Elements Phases and Milestones 1.2 Describe the RUP methodologies time Inception Define scope of project Lifecycle Objectives … Elaboration Plan project, specify features, baseline architecture Lifecycle Architecture … Initial Operational Capability Construction Build product … Major Milestones Transition Transition product to end user community … Product Release
- 13. Inception Phase 1.2 Describe the RUP methodologies Objective: Understand what to build. A vision document: Optional business model An initial project glossary Identify key system functionality. A initial use-case model (10% -20%) complete. Determine at least one possible solution. One or several prototypes. Understand the costs, schedule, and risks associated with the project. An initial risk assessment. Business case Decide what process to follow and what tools to use. A project plan Inception is the first of four RUP phase its all about getting familiar with Project goal and Scope .this phase help you determine the project feasibility , what customer want and how will you get into more resource consumable phase.
- 14. Elaboration phase 1.2 Describe the RUP methodologies Deeper Requirement understanding At least 80% complete use-case model Supplementary requirements capturing non functional requirements None Use case requirement Architect consideration. A Software Architecture Description. An executable architectural prototype. Risk mitigation and Accurate Cost/Scapulae A revised risk list and a revised business case. Development Case refinement A development plan for the overall project coarse-grained project plan showing iterations evaluation criteria for each iteration. Objectives: Elaboration is the second of the four phases in the RUP approach. The goal of the Elaboration phase is to define and baseline the architecture of the system in order to provide a stable basis for the bulk of the design and implementation effort in the Construction phase. The architecture evolves out of a consideration of the most significant requirements (those that have a great impact on the architecture of the system) and an assessment of risks.
- 15. Construction Phase 1.2 Describe the RUP methodologies Minimize development costs and achieve some degree of parallelism Iteratively develop a complete product that is ready to transition to its user community The software product integrated on the adequate platforms. The user manuals. A description of the current release. Construction is really about cost-efficient development of a complete product—an operational version of your system—that can be deployed in the user community Objectives:
- 16. Transition Phase 1.2 Describe the RUP methodologies “beta testing” to validate the new system against user expectations parallel operation with a legacy system that it is replacing conversion of operational databases training of users and maintainers roll-out the product to the marketing, distribution, and sales teams Improve future project performance through lessons learned The purpose of the transition phase is to transition the software product to the user community. Once the product has been given to the end user, issues usually arise that require you to develop new releases, correct some problems, or finish the features that were postponed. Objectives:
- 17. RUP Disciplines 1.2 Describe the RUP methodologies In RUP, the process is described at two levels: the discipline level and the workflow detail level. A Workflow is a grouping of activities that are often performed "together" to produce a specific result. In particular, workflow details describe groups of activities performed together in a discipline. The workflows for the RUP disciplines and workflow details are described using Unified Modeling Language (UML) activity diagrams. Discipline diagrams contain the workflow details of the discipline.
- 18. Each major workflow describes how to create and maintain a particular model. Models and Workflows Business Modeling Business Model implemented by Implementation Model Implementation Workflow Test Model Test Workflow verified by Use-Case Model Requirements Workflow Build upon realized by Design Model Analysis Design Workflow Deployment Workflows Used by Deployment model
- 19. Workflow Detail: Prepare Environment for Project
- 20. Bringing It All Together... Project Management Environment Business Modeling Implementation Test Analysis & Design Preliminary Iteration(s) Iter. #1 Phases Process Workflows Iterations Supporting Workflows Iter. #2 Iter. #n Iter. #n+1 Iter. #n+2 Iter. #m Iter. #m+1 Deployment Configuration & Change Mgmt Requirements Elaboration Transition Inception Construction In an iteration, you walk through all workflows
- 21. What is Agile? 1.3 Describe the Agile methodologies • Agile is a time boxed, iterative approach to software delivery that builds software incrementally from the start of the project, instead of trying to deliver it all at once near the end.
- 22. Agile History Timeline 1.3 Describe the Agile methodologies On February of 2001, seventeen people met to talk about Agile. What emerged was the Agile 'Software Development' Manifesto Dynamic Systems Development Method (Agile delivery Framework) Feature Driven Development (Agile Modeling) Hirotaka Takeuchi 1986 1993 Jeff Sutherland, Jeff McKenna, John Scumniotales 2
- 23. AGILE Quality- driven Cooperative Iterative Adaptable Rapid Not a process, it's a philosophy or set of values What is Agile? 1.3 Describe the Agile methodologies
- 24. • It works by breaking projects down into little bits of user functionality called user stories, prioritizing them, and then continuously delivering them in short two week cycles called sprints. What is Agile? 1.3 Describe the Agile methodologies
- 25. Modern Agile 1.3 Describe the Agile methodologies • The industry has become overloaded with techniques, processes, methodologies and tools that have fallen under the Agile umbrella • Modern Agile aims to move Agile to the next level, not by adding complexity, but by simplifying— stressing only adherence to four principles
- 26. Modern Agile guiding principles 1.3 Describe the Agile methodologies Experiment & Learn Rapidly Is a guiding principle of Modern Agile because it protects us from wasting time and helps us discover success faster Make Safety a Prerequisite Means establishing safety before engaging in potentially hazardous work “Make People Awesome” If you make customers awesome, they tend to be natural promoters of your products or services Deliver Value Continuously Anything valuable that hasn’t been delivered isn’t helping anyone. How might we deliver the right outcomes faster
- 27. Agile Umbrella 1.4 The great methodologies debate Agile Scrum Crystal Kanban XP DSDM FDD RUP And few more… RUP (120+) XP (13) Scrum (9) Kanban (3) Do Whatever!! (0) More Prescriptive more rules to follow More Adaptive fewer rules to follow * Check wikipedia for list of all Agile methods RUP has over 30 roles, over 20 activities, and over 70 artifacts
- 28. How is Agile different? 1.4 The great methodologies debate You are never done A&D, coding and testing on Agile project. So long as there are features to build, these activities continue for the duration of the project The RUP has determined a project life- cycle consisting of four phases. These phases can break down into small iterations if needed
- 29. RUP model Agile model RUP vs Agile: another view
- 30. Large Companies that use Agile…and lots of local guys, too
- 32. RUP: Heavyweight, Is a Framework • Use-case driven from inception to deployment, small team size • Architecture-centric, model visually, well-documented, lots of artifact • Iterative and incremental, where large projects are divided into smaller projects • Long-term detailed planning Agile: Lightweight, Like a Philosophy • Small cross-functional teams are used • Daily status meetings are held, less artifact can be better • Short timeframe increments for each change, short-term planning • A working project is completed at end of each iteration and demonstrated to stakeholders Main characteristics comparison: RUP vs Agile 1.4 The great methodologies debate
- 33. RUP: • It mostly relies on the ability of experts and professionals to assign the activities to individuals • It is a rather complex method which makes its implementation challenging, particularly for smaller businesses, teams or projects • A long time is spent doing requirements or design work before programming starts • Too many roles, artifacts required • High cost in managing, following RUP project • Tool-set are useful but expensive Agile: • It can be difficult to keep the interest of customers / users who are involved in the process. • Team members may be unsuited to the intense involvement that characterizes agile methods. • Prioritizing changes can be difficult where there are multiple stakeholders. • Maintaining simplicity requires extra work. • Contracts may be a problem as with other approaches to iterative development. • Because of their focus on small, tightly- integrated teams, there are problems in scaling agile methods to large systems. • Less emphasis on documentation - harder to maintain when you get a new team for maintenance Main problems comparison: RUP vs Agile 1.4 The great methodologies debate
- 34. Experts review (1) 1.4 The great methodologies debate
- 35. Experts review (2) 1.4 The great methodologies debate
- 36. Experts review (3) 1.4 The great methodologies debate
- 37. Conclusion • RUP will be main methodology in this course due to the following reasons: – It is a framework – Well documented, having templates, tools, well explanation – Model visually – Easy to learn, do not required much experience as Agile – Good method to learn OOP, OOD – Can be customized into small version with less artifacts