Ninth Lecture Hour 8:30 – 9:20 pm, Thursday, September 13

Slides:



Advertisements
Similar presentations
Chapter 7: Software production process Refers to the activities that are used for building, delivering, deploying, and evolving a software product, from.
Advertisements

1 Requirements and the Software Lifecycle The traditional software process models Waterfall model Spiral model The iterative approach Chapter 3.
Software Project Management Peking University Fall Semester, 2001.
Software Process Models
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)
GAI Proprietary Information
Using UML, Patterns, and Java Object-Oriented Software Engineering Royce’s Methodology Chapter 16, Royce’ Methodology.
SYSC System Analysis and Design
Iterative Process Planning
Rational Unified Process
NJIT From Inception to Elaboration Chapter 8 Applying UML and Patterns Craig Larman.
Object-oriented Analysis and Design
Copyright  Larry Dribin, Ph.D. SE470_ProjMgmt_v1.ppt SE470 - ProjMgmt - 1 Excellence in Software Engineering Repeatable Level Defined Level Manage.
EMIS Chapter 6. EMIS Chapter 6 EMIS Chapter 6 Fig 6.2 shows where the SEMP fits into the earliest program stages. Fig 6.5 has an.
Iterative development and The Unified process
COMP 350: Object Oriented Analysis and Design Lecture 2
Systems Engineering Management
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.
Unified Software Practices v 5.0-D Copyright  1998 Rational Software, all rights reserved 1 /26 RUP Architecture.
Chapter 6– Artifacts of the process
® IBM Software Group © 2006 IBM Corporation PRJ480 Mastering the Management of Iterative Development v2 Module 3: Phase Management - Inception.
Sixteenth Meeting 6:30 – 9:20 pm, Thursday, September 20, 2001 Review - Looking Forward (from Part IV, Chapter 15 of Royce’ book) Final Examination.
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,
Software Engineering Chapter 15 Construction Leads to Initial Operational Capability Fall 2001.
RUP Fundamentals - Instructor Notes
Software Development *Life-Cycle Phases* Compiled by: Dharya Dharya Daisy Daisy
Fifteenth Lecture Hour 10:30 – 11:20 am, Sunday, September 16 Tailoring the Process (from Chapter 14 of Royce’ book)
Twelfth Lecture Hour 10:30 – 11:20 am, Saturday, September 15 Software Management Disciplines Project Organization and Responsibilities (from Part III,
Thirteenth Lecture Hour 8:30 – 9:20 am, Sunday, September 16 Software Management Disciplines Process Automation (from Part III, Chapter 12 of Royce’ book)
Fourteenth Lecture Hour 9:30 – 10:20 am, Sunday, September 16 Software Management Disciplines Project Control and Process Automation (from Part III, Chapter.
Chapter – 9 Checkpoints of the process
Yazd University, Electrical and Computer Engineering Department Course Title: Advanced Software Engineering By: Mohammad Ali Zare Chahooki The Project.
Eleventh Lecture Hour 9:30 – 10:20 am, Saturday, September 16 Software Management Disciplines Iterative Process Planning (from Part III, Chapter 10 of.
Eighth Hour Lecture 7:30 – 8:20 pm, Thursday, September 13 Workflows of the Process (from Chapter 8 of Royce’ book)
Object-oriented Analysis and Design Stages in a Software Project Requirements Writing Analysis Design Implementation System Integration and Testing Maintenance.
CHECKPOINTS OF THE PROCESS Three sequences of project checkpoints are used to synchronize stakeholder expectations throughout the lifecycle: 1)Major milestones,
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)
CEN5011, Fall CEN5011 Software Engineering Dr. Yi Deng ECS359, (305)
Rational Unified Process (RUP) Process Meta-model Inception Phase These notes adopted and slightly modified from “RUP Made Easy”, provided by the IBM Academic.
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.
The Rational Unified Process 1 EECS810: Software Engineering.
Software Project Management (SEWPZG622) BITS-WIPRO Collaborative Programme: MS in Software Engineering SECOND SEMESTER /1/ "The content of this.
CSPC 464 Fall 2014 Son Nguyen. 1. The Process of Software Architecting, Peter Eeles, Peter Cripss 2. Software Architecture for Developers, Simon Brown.
Yazd University, Electrical and Computer Engineering Department Course Title: Advanced Software Engineering By: Mohammad Ali Zare Chahooki The Rational.
Overview of RUP Lunch and Learn. Overview of RUP © 2008 Cardinal Solutions Group 2 Welcome  Introductions  What is your experience with RUP  What is.
An organizational structure is a mostly hierarchical concept of subordination of entities that collaborate and contribute to serve one common aim... Organizational.
Rational Unified Process (RUP)
Rational Unified Process Fundamentals Best Practices of Software Engineering Rational Unified Process Fundamentals Best Practices of Software Engineering.
Unified Software Practices v 5.0-D Copyright  1998 Rational Software, all rights reserved 1 /26 Rational Unified Process – Part 2 Original slides modified.
RUP RATIONAL UNIFIED PROCESS Behnam Akbari 06 Oct
RATIONAL UNIFIED PROCESS PROCESS FRAMEWORK OVERVIEW.
Review of Definitions Software life cycle: –Set of activities and their relationships to each other to support the development of a software system Software.
Adaptive Software Development Process Framework. Version / 21 / 2001Page Project Initiation 2.0 Adaptive Cycle Planning 5.0 Final Q/A and.
Iterative development and The Unified process
TK2023 Object-Oriented Software Engineering
Process 4 Hours.
Software Project Management
The Web Application Development Process Models
Requirements and the Software Lifecycle
COMP 350: Object Oriented Analysis and Design Lecture 2
Rational Unified Process
EMIS 7307 Chapter 6.
Presentation transcript:

Ninth Lecture Hour 8:30 – 9:20 pm, Thursday, September 13 Checkpoints of the Process (from Chapter 9 of Royce’ book)

Topics for Today Major Milestones Minor Milestones Periodic Status Assessments

Review - Seven Software Process Workflows Management Controlling the process. Environment Automating the process. Requirements Analysis and evolving requirements artifacts. Design Modeling and evolving the architectures and design artifacts. Implementation Programming and evolving the implementation and deployment artifacts. Assessment Assessing trends in process and product quality. Deployment Transitioning the end products to the use.

Review - Artifacts Associated with Workflows

Review - Iteration Workflow Design Evolving the architecture and baseline design, design and test models, updating design set artifacts. Implementation Developing and acquiring new components, integration and testing. Assessment Evaluating the results of the iteration: compliance, quality, performance. Change decisions. Deployment Transitioning the release to users, IV&V contractor, customer, regulators. Management element Planning for the release, use case selection, detail assignments. Environment Evolving the change order database for new baselines for product, test and environment components. Requirements Analyzing the requirements artifact set, elaborate use cases and evaluation criteria.

Review - Typical Build Sequence

Management Reviews Major milestones Minor milestones System-wide reviews at end of each of the four phases. Minor milestones Iteration-focused events to review iterations. Includes a release specification (release plan and evaluation criteria), and release description (results of the evaluation of the release.) Status assessments Periodic events to assess progress.

Checkpoints

Major Milestones Reviewers Customers Schedules, budgets, feasibility, risk assessment, requirements, progress, compatibility. Users Requirements, usage scenarios, growth, quality. Architects Requirements changes, tradeoffs, completeness, balance. Developers Requirements details, consistency, resolution of risks, environment. Maintainers Sufficiency of product and documentation artifacts, understandibility, interoperability, environment. Others Regulators, IV&V contractor, subcontractors, associate contractors, sales, marketing.

Status Across Major Milestones

Life-Cycle Objectives Milestone Occurs at end of Inception Phase. Includes: Plan, estimated cost and schedule, expected benefits, vision statement andcritical issues, operational concept. Contains draft architecture document. Contains a prototype architecture demonstration. Goal: Authorization to proceed to Elaboration Phase.

Life-Cycle Architecture Milestone Goal: Demonstrate an executable architecture. Authorization to Proceed with the construction phase. Includes: Detailed plan for the construction phase, critical issues regarding requirements and the operational concept, baseline architecture, baseline vision, baseline software development plan, evaluation criteria for the initial operational capability milestone.

Readiness for Architecture Milestone Critical use cases defined and scenarios prepared for evaluating architecture Stable architecture baselined and demonstrated. Risk profile is well understood. Common understanding of outstanding risks, and mitigation plans fully elaborated. Development plans for remaining phases are defined.

Architecture Milestone Contents Presentation and Overview of the current state of the software project. A configuration-controlled set of all engineering data for the engineering artifacts. An executable demonstration of capability.

Architecture Milestone Artifacts

Architecture Milestone Agenda

Initial Operational Capability Milestone Goals Assess readiness to begin transition into customer and user sites. Authorize beginning of acceptance tests. Items for Milestone Installation instructions and issues, software version descriptions, user and operator manuals, support for user sites, test environment, and test software.

Product Release Milestone Goal Assess the completion of software and its transition. Milestone contents Results of acceptance testing, open issues, installation issues, support issues.

Minor Milestones Primarily, iteration readiness reviews and iteration assessment reviews. Early iteration focus Design and analysis, discovery, experimentations, risk assessment. Later iteration focus Completeness, consistency, usage, and change management. Other minor milestones. Test readiness reviews, test results, special issues.

Typical Minor Milestones

Periodic Status Assessments Assessments are crucial for focusing management attention on the health of the project. Generally status assessments are held each month or each quarter during the project. Preparations ideally should include no more than one day’s effort by the software project manager. (Use day-to-day material to prepare the presentation.) Assessments also can be used for project-to-project comparisons, and dissemination of best practices within the organization.

Status Assessment Reviews

Summary for Checkpoints of the Process Checkpoints provide for control of the development process. Major Milestones are the Objectives, Architecture, Initial Operational Capability, and the Product Release Milestones. Minor Milestones are for iteration readiness and iteration results reviews. Periodic Assessment Reviews are for focusing management attention on the health of the project.

Reading Assignment for Next Class Read Chapters 9 of Royce’ book, on process checkpoints. Learn the four major milestones. Learn the primary purpose of each of the four major milestones. Learn the six topics of periodic status assessment reviews.

Assignment for Next Class Meeting In class Mid-Term Exam

Sample Mid-Term Exam 1. List all 7 steps of the waterfall model. 2. List keywords for all 5 improvements needed for the waterfall model approach to work. 3. List keywords for 4 of Barry Boehm’s “Top Ten List” for the state of software development. 4. List all 5 major parameters in the software effort estimation formula. 5. List keywords for 2 of the five attributes of a good software estimate. 6. List keywords for 4 of the five good staffing principles. 7. List keywords for all 3 major problem area failures of peer inspections. 8. List keywords for the top 5 of Royce’ top 10 principles for modern software management. 9. List all 2 stages for economic software development processes. 10. List keywords for the major emphasis for each of the 2 stages. 11. List all 4 phases of a modern life-cycle development process. 12. List the names of 2 of the 5 artifact sets for modern management. 13. List keywords for the major elements of the 2 artifacts sets in question #12. 14. List 3 of the five views of an architecture description. 15. List the 3 of the four sets which comprise an architectural baseline. 16. List the 7 basic workflows for a modern software development process.

Sample Mid-Term Exam 1. List all 7 steps of the waterfall model. 2. List keywords for all 5 improvements needed for the waterfall model approach to work. 3. List keywords for 4 of Barry Boehm’s “Top Ten List” for the state of software development. 4. List all 5 major parameters in the software effort estimation formula. 5. List keywords for 2 of the five attributes of a good software estimate. 6. List keywords for 4 of the five good staffing principles. 7. List keywords for all 3 major problem area failures of peer inspections. 8. List keywords for the top 5 of Royce’ top 10 principles for modern software management. 9. List all 2 stages for economic software development processes. 10. List keywords for the major emphasis for each of the 2 stages. 11. List all 4 phases of a modern life-cycle development process. 12. List the names of 2 of the 5 artifact sets for modern management. 13. List keywords for the major elements of the 2 artifacts sets in question #12. 14. List 3 of the five views of an architecture description. 15. List the 3 of the four sets which comprise an architectural baseline. 16. List the 7 basic workflows for a modern software development process.