Software Engineering Chapter 15 Construction Leads to Initial Operational Capability Fall 2001.

Slides:



Advertisements
Similar presentations
September 2008Mike Woodard Rational Unified Process Key Concepts Mike Woodard.
Advertisements

Testing Workflow Purpose
Ninth Lecture Hour 8:30 – 9:20 pm, Thursday, September 13
1 Requirements and the Software Lifecycle The traditional software process models Waterfall model Spiral model The iterative approach Chapter 3.
CS487 Software Engineering Omar Aldawud
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.
Sixth Hour Lecture 10:30 – 11:20 am, September 9 Framework for a Software Management Process – Artifacts of the Process (Part II, Chapter 6 of Royce’ book)
® IBM Software Group © 2006 IBM Corporation PRJ480 Mastering the Management of Iterative Development v2 Module 4: Phase Management - Elaboration.
GAI Proprietary Information
Rational Unified Process
The Unified Software Development Process - Workflows Ivar Jacobson, Grady Booch, James Rumbaugh Addison Wesley, 1999.
NJIT From Inception to Elaboration Chapter 8 Applying UML and Patterns Craig Larman.
OO Development Process. UML and Process UML standardizes notation, not process –Increase likelihood of widespread acceptance There is significant variability.
Software Project Transition Planning
Copyright  Larry Dribin, Ph.D. SE470_ProjMgmt_v1.ppt SE470 - ProjMgmt - 1 Excellence in Software Engineering Repeatable Level Defined Level Manage.
Lifecycle Phases time InceptionElaborationConstruction Transition  Define the scope of the project and develop business case  Inception Define the scope.
SE 555 Software Requirements & Specification Beyond Requirements Based on Weigers Chapter17.
1 Software Testing and Quality Assurance Lecture 15 - Planning for Testing (Chapter 3, A Practical Guide to Testing Object- Oriented Software)
NGAO Team Meeting Management Peter Wizinowich May 26, 2009.
Iterative development and The Unified process
Page 1 R Risk-Driven and Iterative Development. Page 2 R Copyright © 1997 by Rational Software Corporation What the Iterative Life Cycle Is Not It is.
The Software Product Life Cycle. Views of the Software Product Life Cycle  Management  Software engineering  Engineering design  Architectural design.
UML - Development Process 1 Software Development Process Using UML (2)
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.
Unified Software Development Process (UP) Also known as software engineering process SEP describes how requirements are turned into software Defines who,
RUP Fundamentals - Instructor Notes
Software Development *Life-Cycle Phases* Compiled by: Dharya Dharya Daisy Daisy
Software Engineering Chapter 12 The Generic Iteration Workflow Fall 2000.
-Nikhil Bhatia 28 th October What is RUP? Central Elements of RUP Project Lifecycle Phases Six Engineering Disciplines Three Supporting Disciplines.
Rational Unified Process (Part 1) CS3300 Fall 2015.
RUP Implementation and Testing
Software Engineering Chapter 8 Fall Analysis Extension of use cases, use cases are converted into a more formal description of the system.Extension.
CS 360 Lecture 3.  The software process is a structured set of activities required to develop a software system.  Fundamental Assumption:  Good software.
Software Engineering Management Lecture 1 The Software Process.
Object Oriented Design and Analysis Rational Unified Process.
Chapter – 9 Checkpoints of the process
Testing Workflow In the Unified Process and Agile/Scrum processes.
® IBM Software Group © 2006 IBM Corporation PRJ480 Mastering the Management of Iterative Development v2 Module 6: Phase Management -Transition.
Eighth Hour Lecture 7:30 – 8:20 pm, Thursday, September 13 Workflows of the Process (from Chapter 8 of Royce’ book)
CHECKPOINTS OF THE PROCESS Three sequences of project checkpoints are used to synchronize stakeholder expectations throughout the lifecycle: 1)Major milestones,
Notes of Rational Related cyt. 2 Outline 3 Capturing business requirements using use cases Practical principles  Find the right boundaries for your.
Fifth Lecture Hour 9:30 – 10:20 am, September 9, 2001 Framework for a Software Management Process – Life Cycle Phases (Part II, Chapter 5 of Royce’ book)
Software Engineering COSC 4460 Class 4 Cherry Owen.
Requirements Management with Use Cases Module 10: Requirements Across the Product Lifecycle Requirements Management with Use Cases Module 10: Requirements.
J. Scott Hawker p. 1Some material © Rational Corp. Rational Unified Process Overview See and use the RUP Browser on lab machines.
Chapter 8 Workflows of the Process Taken from Walker Royce’s textbook – Software Project Management plus a number of Personal Comments.
Team Skill 6: Building the Right System Assessing Requirements Quality (29)
The principles of an object oriented software development process Week 04 1.
CSPC 464 Fall 2014 Son Nguyen. 1. The Process of Software Architecting, Peter Eeles, Peter Cripss 2. Software Architecture for Developers, Simon Brown.
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.
Intelligence and Information Systems 1 3/17/2004 © 2004 Raytheon Company USC/CSE Executive Workshop on Agile Experiences March 17, 2004 A Raytheon Agile.
Software Development Process CS 360 Lecture 3. Software Process The software process is a structured set of activities required to develop a software.
Software Architecture Architecture represents different things from use cases –Use cases deal primarily with functional properties –Architecture deals.
RUP RATIONAL UNIFIED PROCESS Behnam Akbari 06 Oct
Scrum Overview. Agenda What is scrum…and what it isn’t Scrum’s Characteristics The Scrum Process Scrum Phases Measurements Key Practices Backlogs Sprint.
Object oriented analysis and design 1 Software Development Life Cycle (SDLC)
Review of Definitions Software life cycle: –Set of activities and their relationships to each other to support the development of a software system Software.
Iterative development and The Unified process
TK2023 Object-Oriented Software Engineering
Project life span.
Iterative, Evolutionary, and Agile Rational Unified Process
UNIFIED PROCESS.
Rational Unified Process
CSCI 577b Tasks and Activities
Software engineering -1
The Unified/Rational Unified Process (UP/RUP) Defined
Presentation transcript:

Software Engineering Chapter 15 Construction Leads to Initial Operational Capability Fall 2001

The Construction Phase in Brief The emphasis shifts from the accumulation of the knowledge base needed to build the project to the actual construction of a system or product within parameters of cost, effort, and shchedule. The emphasis shifts from the accumulation of the knowledge base needed to build the project to the actual construction of a system or product within parameters of cost, effort, and shchedule.

Add to the Baseline The details are filled in on the baseline architecture. The details are filled in on the baseline architecture. The remaining use cases are prioritized and divided into builds and iterations. The remaining use cases are prioritized and divided into builds and iterations.

Revise Project Plan Time may elapse between the end of the elaboration phase and the beginning of the construction phase. Time may elapse between the end of the elaboration phase and the beginning of the construction phase. People may have been reassigned and new people, possibly even a new project manager, may be on the project. People may have been reassigned and new people, possibly even a new project manager, may be on the project. The budget approved may be different from that in the plan from elaboration. The budget approved may be different from that in the plan from elaboration. Therefore, the project plan could change considerably. Therefore, the project plan could change considerably.

Staffing The majority of the work is done in the construction phase. Therefore additional staff will likely be required. The majority of the work is done in the construction phase. Therefore additional staff will likely be required.

Evaluation Criteria Criteria are needed to judge when the construction is complete, and when each iteration is complete. Criteria are needed to judge when the construction is complete, and when each iteration is complete. The use cases included in an iteration are a good start for the criteria. The criteria will be different for each project. The use cases included in an iteration are a good start for the criteria. The criteria will be different for each project.

User Material A first cut of user guides, help text, release notes, user manuals, and operator manuals are prepared in the construction phase. A first cut of user guides, help text, release notes, user manuals, and operator manuals are prepared in the construction phase. They should be sufficient to support the transition phase They should be sufficient to support the transition phase

Course Products A first draft of training materials is done. A first draft of training materials is done. They should be sufficient to support the users in the transition phase. They should be sufficient to support the users in the transition phase.

Building the System Requirements and architecture should be stable before entering the construction phase. Requirements and architecture should be stable before entering the construction phase. Complete the use-case realization for all use cases. (some in each iteration) Complete the use-case realization for all use cases. (some in each iteration) Design the required subsystems and classes. Design the required subsystems and classes. Implement them as components. Implement them as components. Test them individually. Test them individually. Test them in builds. Test them in builds. Add a set of use cases in each increment, so as to have a working product at the end of each build. Add a set of use cases in each increment, so as to have a working product at the end of each build.

Architect The architect is concerned with anything added to the system that would change the integrity of the baseline architecture already in place. The architect is concerned with anything added to the system that would change the integrity of the baseline architecture already in place. If there is a change to the baseline architecture, all the workflows must be considered to make sure the architecture is still consistent. If there is a change to the baseline architecture, all the workflows must be considered to make sure the architecture is still consistent.

Testing Unit testing Unit testing Integration testing Integration testing Black box testing Black box testing

Controlling the Business Case The business bid was prepared at the end of the elaboration phase. The business bid was prepared at the end of the elaboration phase. At the end of each iteration in the construction phase, the project manager checks the actual progress against the schedule and budget. At the end of each iteration in the construction phase, the project manager checks the actual progress against the schedule and budget.

Assess the Iterations and the Construction Phase Review what was accomplished in an iteration against what was planned. Review what was accomplished in an iteration against what was planned. Plan in which of the following iterations work not completed is to be accomplished. Plan in which of the following iterations work not completed is to be accomplished. Determine that the build is ready to advance to the next iteration. Determine that the build is ready to advance to the next iteration. Update the risk list. Update the risk list. Fill in the plan for the next iteration. Fill in the plan for the next iteration. Update the plan for iterations beyond the next one. Update the plan for iterations beyond the next one. At the end of the final iteration of this phase, determine that the product has passed system test and has reached initial operational capability. At the end of the final iteration of this phase, determine that the product has passed system test and has reached initial operational capability. Authorize entry into the transition phase. Authorize entry into the transition phase. Update the project plan. Update the project plan.

Planning the Transition Phase Select beta testers, and how application and training will be provided. Select beta testers, and how application and training will be provided. Get feedback Get feedback What to do after receiving feedback cannot always be planned in advance, since it depends on the specific feedback received. What to do after receiving feedback cannot always be planned in advance, since it depends on the specific feedback received.

The Key Deliverables Project plan for the transition phase. Project plan for the transition phase. The executable software itself--the initial- operational-capability release. This is the final build from construction. The executable software itself--the initial- operational-capability release. This is the final build from construction. All artifacts, including models of the system. All artifacts, including models of the system. Maintained and minimally updated architecture description. Maintained and minimally updated architecture description. Preliminary user manual in enough detail to guide beta users. Preliminary user manual in enough detail to guide beta users. Business case, reflecting situation at end of phase. Business case, reflecting situation at end of phase.