1. Introduction Iterative Development & the Unified Process.

Slides:



Advertisements
Similar presentations
Kyle Hartmann. RAD was created in response to long lead times and low flexibility Focuses on communication Quicker and better requirements interpretation.
Advertisements

Iterative, Evolutionary, and Agile You should use iterative developmen only on projects that you want to succeed. - Martin Fowler.
The System and Software Development Process Instructor: Dr. Hany H. Ammar Dept. of Computer Science and Electrical Engineering, WVU.
Diane Pozefsky. Interactions  There is no “right answer”  Typically people and product are fixed  … can adapt process  (which is where we will start)
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.
Chapter 05: Evolutionary Requirements Definition : Requirements  “Requirements are capabilities and conditions to which the system, and more broadly.
Chapter 2. Iteration The most import aspect of OOA/D An agile practice vs waterfall – early and repeated programming, feedback, adaptation waterfall is.
Arlow and Neustadt ch.21 What is the unified process? People are more important than any process. Good people with a good process will outperform good.
29 September Interactions  There is no “right answer”  Typically people and product are fixed  … can adapt process  (which is where we will.
Unit 1, Lesson 4 Software Development Cycle AOIT Introduction to Programming Copyright © 2009–2012 National Academy Foundation. All rights reserved.
Sharif University of Technology Session # 3.  Contents  Systems Analysis and Design Sharif University of Technology MIS (Management Information System),
Copyright © The OWASP Foundation Permission is granted to copy, distribute and/or modify this document under the terms of the OWASP License. The OWASP.
CS 325: Software Engineering January 15, 2015 Software Process & Methodology Prototyping Process Model Evolutionary Process Model Spiral Process Model.
Object-Oriented Analysis and Design
PRJ270: Essentials of Rational Unified Process
OO Development Process. UML and Process UML standardizes notation, not process –Increase likelihood of widespread acceptance There is significant variability.
Object-oriented Analysis and Design
COMP 350: Object Oriented Analysis and Design Lecture 2
Chapter 6 View Alignment Techniques and Method Customization (Part I) Object-Oriented Technology From Diagram to Code with Visual Paradigm for UML Curtis.
Software Development Process
CPSC 871 John D. McGregor Processes – a first iteration Module 1 Session 1.
Object-Oriented Analysis and Design Iterative Development and the Unified Process.
Introduction to RUP Spring Sharif Univ. of Tech.2 Outlines What is RUP? RUP Phases –Inception –Elaboration –Construction –Transition.
Current Trends in Systems Develpment
CS 360 Lecture 3.  The software process is a structured set of activities required to develop a software system.  Fundamental Assumption:  Good software.
Unified Process versus Extreme Programming. Outline Compare and contrast UP and XP  Processes / Disciplines  Management  Artefacts Risk management.
©Ian Sommerville 2000, Mejia-Alvarez 2009 Slide 1 Software Processes l Coherent sets of activities for specifying, designing, implementing and testing.
Introduction to Software Development 1. Outline The code-compile-debug process for writing a program The software development process 2.
CS CS 5150 Software Engineering Lecture 3 Software Processes 2.
University of Palestine software engineering department Testing of Software Systems Testing throughout the software life cycle instructor: Tasneem Darwish.
 CS 5380 Software Engineering Chapter 2 – Software Processes Chapter 2 Software Processes1.
AGILE SOFTWARE DEVELOPMENT PROCESSES Cheruku Smitha.
Iterative development and The Unified process Chapter 2 Applying UML and Patterns -Craig Larman.
Object-oriented Analysis and Design Stages in a Software Project Requirements Writing Analysis Design Implementation System Integration and Testing Maintenance.
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 Fundamentals Module 5: Implementing RUP.
1 COMP 350: Object Oriented Analysis and Design Lecture 1Introduction References: Craig Larman Chapter 1.
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,
CS 5150 Software Engineering Lecture 3 Software Processes 2.
UI Panel: Agile User Interface Design Colin Clark.
The Confounding World of Process Methodologies By Thelma Hataria.
The Rational Unified Process 1 EECS810: Software Engineering.
#AgileEd. Using Agile in the Classroom Cindy Royal, Associate Professor Texas State University slideshare.net/cindyroyal #AgileEd.
Ivar Jacobson, Grady Booch, and James Rumbaugh The Unified Software Development Process Addison Wesley, : James Rumbaugh's OOMD 1992: Ivar Jacobson's.
Rational Unified Process Fundamentals Best Practices of Software Engineering Rational Unified Process Fundamentals Best Practices of Software Engineering.
It’s Agile …. like! A Corkman’s introduction to Agile software delivery.
Software Development Process CS 360 Lecture 3. Software Process The software process is a structured set of activities required to develop a software.
Introduction Requirements and the Software Lifecycle (3)
Unified Software Practices v 5.0 Copyright  1998 Rational Software, all rights reserved 1 R Rational Unified Process  “de facto standard”, framework.
Software Design & Documentation Anita Kuchera John Sturman UP Introduced.
The Unified Process and the Inception Phase James W. Benham CMPT 371 Fall 2004.
10 September Interactions  There is no “right answer”  Typically people and product are fixed  … can adapt process  (which is where we will.
RATIONAL UNIFIED PROCESS PROCESS FRAMEWORK OVERVIEW.
4.2 SOFTWARE DEVELOPMENT METHODOLOGGY PRESENTED BY : AZURA IBRAHIM SYARIFAH SYAZA BTE SEYD ZULKAFLY CS230(5A)
SOFTWARE DEVELOPMENT Presented By : Emporiumtech This presentation is brought you by
TK2023 Object-Oriented Software Engineering
Object-oriented Analysis and Design
Unit 6 Application Design KLB Assignment.
CSC 355 – Newer Approaches to System Development Life Cycles & Processes, Spring 2017 March 2017 Dr. Dale Parson.
System Development Process
Systems Analysis and Design in a Changing World, 6th Edition
Introduction to Software Engineering
COMP 350: Object Oriented Analysis and Design Lecture 2
How to Successfully Implement an Agile Project
Software Development Process
Chapt 2 Iterative Evolutionary Agile.
Introduction to Software Process Models
The Unified/Rational Unified Process (UP/RUP) Defined
CSCI 360: Software Architecture & Design
Presentation transcript:

1. Introduction Iterative Development & the Unified Process

2 Objectives Define: –an iterative process –an adaptive process. Define fundamental concepts of Unified Process.

3 Introduction A software development process is a recipe for –building –deploying –upgrading software. The Unified Process (UP) is based on competing formerly processes: Unifying their processes got them a bigger market share.

4 Iterative Development Iterative development is central to UP. System development comprises iterations, each of which yields a functional system. –Requirements analysis –Design –Implementation –Deployment

5 Iterative Development While ( ! isSystemComplete() ) { Select an increment of requirements; Analyze requirements; Modify design; Modify implementation; // unit test Integrate; Deploy; }

6 Iterative Development Embrace change! Do not try to design the ultimate system before writing the 1 st line of code. The Waterfall design process is iterative development with only 1 iteration. Presumes process is a science. It is not.

7 Iterative Development Benefits Early confrontation of high-risk requirements. Early, frequent satisfaction working system. Higher quality feedback to client. Higher quality feedback to developer. Adaptive: early experiences influence subsequent: –Requirements –Processes.

8 UP Best Practices & Concepts Use short time boxes for each iteration Confront high-risk requirements early Get user feedback early & often Maintain high quality at all times: –Unit & system test every change. Model system visually. Use configuration/version management for all artifacts.

9 Predictive versus Adaptive 2 terms in common usage are: Predictive process A meticulous heavy weight process, E.g., the Waterfall process. Adaptive process A light weight process. It is agile; embraces change. Small set of artifacts.