Project Management in the Rational Unified Process
|
|
- Roy Williams
- 8 years ago
- Views:
Transcription
1 CS2 Software Engineering note 3 Project Management in the Rational Unified Process In the last two Software Engineering lectures we have considered the outline description of the Rational Unified Process and in Lecture 2 we considered the Requirements workflow as an example of a typical workflow. In this and the next lecture we consider some of the the workflows of the RUP in a little more detail. This lecture considers the project management workflow. The Project Management Workflow The RUP is an essentially iterative process. The iterative approach has been chosen to limit exposure to project risk. This lecture introduces two key concepts in project management: Risk: this is used to assess the potential of a project to fail to deliver the required product. Metrics: these are the measurements we make of a development process in an attempt to assess and control risk through the planning process. The purpose of the Project Management workflow is threefold: 1. To provide a framework for managing project risk, through 2. The provision of practical guidance on how to plan, execute and monitor projects within, 3. A framework of planning structured around the coordination of the RUP workflows and phases oriented to generating a flexible plan exploiting the strengths of the iterative approach. Planning an iterative project Using an iterative approach in planning the development of software projects has many benefits mainly because it is easier to keep the project aligned to the requirements which are usually undergoing rapid evolution driven by a variety of factors, involving many different stakeholders. However, in some respects, taking an iterative approach raises additional questions: 1
2 How many iterations should be planned? How long should each iteration last? What are the aims, objectives and deliverables of each iteration? How should an iteration be monitored? The project plan encapsulates the process the project should follow. In particular it: Expresses: The decomposition of the overall task into sub-tasks. The allocation of tasks to people/teams The setting of timescales for the task Evolves through the lifetime of the project: To reflect changes in the desired outcome of the project. To take account of earlier deviations from the plan. In response to monitoring and measurement of the process and product. Two level plans: In many Project Planning environments because many similar projects have been undertaken previously it is possible to identify the deliverables that are required and the phasing of sub-tasks to achieve the goal of the project. Unfortunately this is rarely the case in software projects. The usual approach is to take a two level approach with a coarse-grained phase plan that looks at the project across the four main phases of the RUP and then consider detailed iteration plans for each iteration undertaken on the project. The phase plan is very rough and consists of the outline for the whole project. It should include at least: Dates of the major milestones, i.e. the move from one phase to another. Staffing estimates for each phase (this is usually based on historical evidence). An idea of the number of iterations included in each phase and rough dates for the end of each iteration. The number of iterations for each phase is reasonably closely related to the size of the system. Larger systems require more iterations. 2
3 The iteration plans usually include the current plan that is being used to manage the current iteration. This provides a framework against which progress can be measured. Each iteration includes: Requirements, analysis and design, implementation, deployment, test, and evaluation so milestones for each activity should be established and decomposition of larger tasks into sub-tasks should ensure the milestones are achievable. In addition, there should be at least a plan under development for the next iteration and possibly some scheduling of particular tasks into later iterations. In complex systems, the early iterations may exclude much of the functionality and the iteration plans may capture the road map of when particular features are scheduled to be introduced. The approach to generating the iteration plans is entirely conventional. We identify subtasks, their interdependence, and make effort estimates for each task. From this we establish start and end dates for each task that respects the resource requirements we have and the dependency between tasks. This plan is usually captured by a Gantt chart showing when each task starts and ends. Project Risk A risk comprises three elements: an undesirable event, an estimate of the severity of the consequences of the event, and a liklihood that the event will occur. The amount of risk a project is exposed to is a good measure of the viability of the project. If a project carries too much liklihood of high consequence events it should probably be cancelled because the chances of delivering an acceptable product are too low. Risk is often classified into Direct risk that the manager can control to some extent and Indirect risk that the manager cannot influence. In managing a project the aim is to control risk. Risk control involves three strategies: Risk avoidance involves reorganizing the project so you are not exposed to the risk. E.g. Change the supplier of some key component from a supplier who is promising a high quality product but has yet to deliver to a supplier who has a tried-and-tested product in the area. Risk transfer involves finding other stakeholders to share the risk with. E.g. if you are producing the product for a particular customer but hope to market it to other customers it might be possible to share get the custome to accept more of the development costs in return for a stake in future sales to other customers. Risk acceptance involves deciding to live with the risk and to take the occurrence of of the risk as a possible contingency to be taken account of in the planning process. Accepting a risk involves: Risk mitigation where we try to reduce the liklihood or the impact of a risk. E.g. if we decide to choose a particular supplier for a component 3
4 we can identify an alternative supplier with a similar product that could be used if the original supplier fails to deliver. Contingency planning construct what if plans on the basis of the risk occurring. Metrics A metric is some measurement we can make of a product or process in the overall development process. Usually metrics are split into two broad categories: Knowledge oriented metrics: these are oriented to tracking the process to evaluate, predict or monitor some part of the process. E.g. Goals of this kind of measurement include: Are we progressing according to plan? Is the workload to high for the team? How much reuse is the team achieving? Achievement oriented metrics: these are often oriented to measuring some product aspect, often related to some overall measure of quality of the product. E.g. goals of this kind of measurement include: Have we achieved the usability target? Metrics have a number of issues we need to consider. Without gathering some metrics we cannot expect adequately to control a process. However: It can be very expensive to gather metric data we should only gather the necessary data and no more. What we need to measure may change through the different process phases. We should be modest about what metrics we can measure E.g. measuring attributes like usability can only be very crude. Artifacts Generated by the Project Management workflow The Project management workflow aims to create a number of key artifacts for the management of the project. These are: The software development plan that comprises: Product acceptance plan Risk list and risk management plan Problem resolution plan Metric list and measurement plan Business case Detailed plan for each iteration 4
5 Assessment of each iteration Periodic status assessment Work schedule Project measurement database. Project Management Workflow In this final section we briefly outline the nine workflow items comprising this workflow. This is sufficient to understand the overall process but more detail is required if we are to apply this successfully. At project inception on the first iteration we require to carry out three workflow items: Conceive new project: This provides a preliminary business case and identifies some of the risks and begins assessment. Evaluate project scope and risk: This carries out more detailed development of the business case and the associated risks. Develop software development plan: This develops much of the detailed plan by developing the: measurement plan risk management plan product acceptance plan problem resolution plan project organisation and staffing monitoring and control processes plan phases and iterations During each iteration, we have three further workflow items: Monitor and Control Project: This work item continually checks the project is on plan by monitoring the process and checking the monitoring results against the plan. Deviations from plan may result in replanning. Plan for next iteration: This workitem develops the plan for the next iteration, taking into account progress on the current iteration and the overall plan. Manage iteration: This work items monitors progress and next iterations planning to inform decision making on whether to transfer to the next iteration or abandon the project because risks or cost estimates have become unacceptable. In addition there are further workflow items than manage phase transitions and bringing projects to an end. 5
6 Summary This note has provided a brief overview of the project management workflow of the RUP. In particular we have: Seen how planning uses two levels of plan Considered how the planning process is risk driven Measurement and metrics are used to assess progress and modify plans 6
Supporting Workflow Overview. CSC532 Fall06
Supporting Workflow Overview CSC532 Fall06 Objectives: Supporting Workflows Define the supporting workflows Understand how to apply the supporting workflows Understand the activities necessary to configure
More informationManaging Small Software Projects - An Integrated Guide Based on PMBOK, RUP, and CMMI
Managing Small Software Projects - An Integrated Guide Based on PMBOK, RUP, and CMMI César Cid Contreras M.Sc. Prof. Dr. Henrik Janzen Published at the South Westphalia University of Applied Sciences,
More informationIntroduction to Software Engineering. 9. Project Management
Introduction to Software Engineering 9. Project Management Roadmap > Risk management > Scoping and estimation > Planning and scheduling > Dealing with delays > Staffing, directing, teamwork 2 Literature
More information<name of project> Software Project Management Plan
The document in this file is adapted from the IEEE standards for Software Project Management Plans, 1058-1998, which conforms to the requirements of ISO standard 12207 Software Life Cycle Processes. Tailor
More informationCS 389 Software Engineering. Lecture 2 Chapter 2 Software Processes. Adapted from: Chap 1. Sommerville 9 th ed. Chap 1. Pressman 6 th ed.
CS 389 Software Engineering Lecture 2 Chapter 2 Software Processes Adapted from: Chap 1. Sommerville 9 th ed. Chap 1. Pressman 6 th ed. Topics covered Software process models Process activities Coping
More informationPlanning a Project with the Rational Unified Process Author: David West
Planning a Project with the Rational Unified Process Author: David West Rational Software White paper TP 151, 08/02 Table of Contents INTRODUCTION... 1 ABOUT THE PROJECT PLAN... 1 CHARACTERISTICS OF A
More information<Company Name> <Project Name> Software Development Plan. Version <1.0>
Version [Note: The following template is provided for use with the Rational Unified Process. Text enclosed in square brackets and displayed in blue italics (style=infoblue)
More informationSoftware Development Methodologies
Software Development Methodologies Lecturer: Raman Ramsin Lecture 15 Agile Methodologies: AUP 1 Agile Unified Process (AUP) Proposed by Ambler as a simplified version of the Rational Unified Process (RUP).
More informationSRM UNIVERSITY FACULTY OF ENGINEERING AND TECHNOLOGY
SRM UNIVERSITY FACULTY OF ENGINEERING AND TECHNOLOGY SCHOOL OF COMPUTING DEPARTMENT OF SWE COURSE PLAN Course Code : CS0351 Course Title : SOFTWARE PROJECT MANAGEMENT Semester : VII Course Time : July
More information1. Background and business case
1. Background and business case This section explains the context and why the project is being undertaken. It provides the justification for investing the time and resources in the project. 1.1 Reasons
More informationModellistica Medica. Maria Grazia Pia, INFN Genova. Scuola di Specializzazione in Fisica Sanitaria Genova Anno Accademico 2002-2003
Modellistica Medica Maria Grazia Pia INFN Genova Scuola di Specializzazione in Fisica Sanitaria Genova Anno Accademico 2002-2003 Lezione 20-21 The Unified Process Dynamic dimension Two dimensions Content
More informationIn this Lecture you will Learn: Development Process. Unified Software Development Process. Best Practice
In this Lecture you will Learn: Development Chapter 5C About the Unified Software Development How phases relate to workflows in an iterative life cycle An approach to system development Major activities
More informationPROJECT MANAGEMENT PLAN TEMPLATE < PROJECT NAME >
PROJECT MANAGEMENT PLAN TEMPLATE < PROJECT NAME > Date of Issue: < date > Document Revision #: < version # > Project Manager: < name > Project Management Plan < Insert Project Name > Revision History Name
More informationWeb Application Development Process
Web Engineering Web Application Development Process Copyright 2013 Ioan Toma & Srdjan Komazec 1 Where we are? # Date Title 1 5 th March Web Engineering Introduction and Overview 2 12 th March Requirements
More informationMNLARS Project Audit Checklist
Audit Checklist The following provides a detailed checklist to assist the audit team in reviewing the health of a project. Relevance (at this time) How relevant is this attribute to this project or audit?
More informationRUP for Software Development Projects
RUP for Software Development Projects George Merguerian www.bmc-online.com 1 Specialists in Global Project Management Brussels Frankfurt Houston Istanbul Milan Ottawa Shanghai Singapore Warsaw Washington
More informationStrategy for Application Modernization A Summa White Paper
Strategy for Application Modernization A Summa White Paper Summa 925 Liberty Avenue, 6 th Floor Pittsburgh, PA 15222 (p) 412.258.3300 (f) 412.258.3299 www.summa tech.com Why Modernize? My customers want
More informationDescription of Program Management Processes (Initiating, Planning) 2011 PROGstudy.com. All rights reserved
Description of Program Management Processes (Initiating, Planning) Topics Covered Program Management Process Groups salient features Description of all processes in Initiating Process Group: Initiate Program
More informationSoftware Process and Project Plan
Software Process and Project Plan for Trillium Health - Grant Management Version: 1.2 Prepared by: Akshay Karnawat Date: November 26, 2014 (updated) Team Members: Shannon Trudeau (smtofny@gmail.com) Matt
More informationDigital Asset Manager, Digital Curator. Cultural Informatics, Cultural/ Art ICT Manager
Role title Digital Cultural Asset Manager Also known as Relevant professions Summary statement Mission Digital Asset Manager, Digital Curator Cultural Informatics, Cultural/ Art ICT Manager Deals with
More informationObjectives. Project Management Overview. Successful Project Fundamentals. Additional Training Resources
Project Management for Small Business Moderator: Maria Mancha Frontline Systems, Inc. Objectives Project Management Overview Successful Project Fundamentals Additional Training Resources Project Management
More informationCS 6361, SPRING 2010 Advanced Requirements Engineering Web Based Meeting Scheduler- Project Plan
1 W E B B A S E D M E E T I N G S C H E D U L E R S Y S T E M Project Plan Version 4.0 CS 6361 ADVANCED REQUIREMENTS ENGINEERING, SPRING 2010 UNIVERSITY OF TEXAS AT DALLAS R E Q U I R E M E N T S E N G
More informationIterative Project Management 1
Iterative Project Management Module 2 Objectives Understand issues for Project Managers (PM) who use iterative development by: Learning how the PM monitors and steers an iterative project towards success.
More informationSoftware Project Management using an Iterative Lifecycle Model
Software Corporation Software Project Management using an Iterative Lifecycle Model 1 Objectives of this Presentation To understand what the Unified Process is To understand the iterative lifecycle approach
More informationProject Management Planning
Develop Project Tasks One of the most important parts of a project planning process is the definition of activities that will be undertaken as part of the project. Activity sequencing involves dividing
More informationOPERATIONAL PROJECT MANAGEMENT (USING MS PROJECT)
OPERATIONAL PROJECT MANAGEMENT (USING MS PROJECT) 3 DAY COURSE INTRODUCTION The principles of project management are generic and therefore can be applied to all projects regardless of business sector.
More informationIntroduction to Software Engineering
CS1Ah Lecture Note 7 Introduction to Software Engineering In this note we provide an overview of Software Engineering. The presentation in this lecture is intended to map out much of what we will study
More informationSoftware Development Process and Activities. CS 490MT/5555, Fall 2015, Yongjie Zheng
Software Development Process and Activities CS 490MT/5555, Fall 2015, Yongjie Zheng Software Process } A set of activities that leads to the production of a software product } What product we should work
More information2.1 Initiation Phase Overview
2.1 Initiation Phase Overview The is the conceptualization of the project. This section describes the basic processes that must be performed to get a project started. Accordingly, the purpose of the is
More informationManaging Successful Software Development Projects Mike Thibado 12/28/05
Managing Successful Software Development Projects Mike Thibado 12/28/05 Copyright 2006, Ambient Consulting Table of Contents EXECUTIVE OVERVIEW...3 STATEMENT OF WORK DOCUMENT...4 REQUIREMENTS CHANGE PROCEDURE...5
More informationAppendix 2-A. Application and System Development Requirements
Appendix 2-A. Application and System Development Requirements Introduction AHRQ has set up a Distributed Systems Engineering Lab (DSEL) to support all internal development efforts and provide a facility
More informationITIL. Lifecycle. www.alctraining.com.my. ITIL Intermediate: Continual Service Improvement. Service Strategy. Service Design. Service Transition
Take your ITIL skills to the next level ITIL Lifecycle ITIL Intermediate: Part of the complete ITIL Education Program Advance your career Add value to your organisation Gain credits towards ITIL Expert
More informationRequirement Management with the Rational Unified Process RUP practices to support Business Analyst s activities and links with BABoK
IBM Software Group Requirement Management with the Rational Unified Process RUP practices to support Business Analyst s activities and links with BABoK Jean-Louis Maréchaux Software IT Specialist IBM Rational
More informationClassical Software Life Cycle Models
Classical Software Life Cycle Models SWEN 301 Trimester 1, 2015 Lecturer: Dr Hui Ma Engineering and Computer Science Lecture slides make use of material provided on the textbook's companion website Motivation
More information02 General Information. 03 Features. 06 Benefits.
invgate 02 General Information. 03 Features. 06 Benefits. Index. 02 General Information. Improve your IT department Managing Service Support just got easier Despite growing connectivity, data accessibility
More informationChap 1. Introduction to Software Architecture
Chap 1. Introduction to Software Architecture 1. Introduction 2. IEEE Recommended Practice for Architecture Modeling 3. Architecture Description Language: the UML 4. The Rational Unified Process (RUP)
More informationMitigating Service-Orientation Risks with RUP
by Filippos Santas, IT Architect, Credit Suisse Private Banking in Switzerland and Certified SOA Trainer SERVICE TECHNOLOGY MAGAZINE Issue LIV September 2011 Abstract - In this article, we examine the
More informationPORTFOLIO, PROGRAMME & PROJECT MANAGEMENT MATURITY MODEL (P3M3)
PORTFOLIO, PROGRAMME & PROJECT MANAGEMENT MATURITY MODEL (P3M3) 1st February 2006 Version 1.0 1 P3M3 Version 1.0 The OGC logo is a Registered Trade Mark of the Office of Government Commerce This is a Value
More informationMinnesota Health Insurance Exchange (MNHIX)
Minnesota Health Insurance Exchange (MNHIX) 1.2 Plan September 21st, 2012 Version: FINAL v.1.0 11/9/2012 2:58 PM Page 1 of 87 T A B L E O F C O N T E N T S 1 Introduction to the Plan... 12 2 Integration
More informationProgram Lifecycle Methodology Version 1.7
Version 1.7 March 30, 2011 REVISION HISTORY VERSION NO. DATE DESCRIPTION AUTHOR 1.0 Initial Draft Hkelley 1.2 10/22/08 Updated with feedback Hkelley 1.3 1/7/2009 Copy edited Kevans 1.4 4/22/2010 Updated
More informationThe Software Process. The Unified Process (Cont.) The Unified Process (Cont.)
The Software Process Xiaojun Qi 1 The Unified Process Until recently, three of the most successful object-oriented methodologies were Booch smethod Jacobson s Objectory Rumbaugh s OMT (Object Modeling
More informationProject Management Step Wise. Sunday, 4 November 12
Project Management Step Wise An Overview of Project Planning you might have noticed already that it is difficult to track progress with a software project it gets worse as scale and distribution increase
More informationImplementation of ANSI/AAMI/IEC 62304 Medical Device Software Lifecycle Processes.
Implementation of ANSI/AAMI/IEC 62304 Medical Device Software Lifecycle Processes.. www.pharmout.net Page 1 of 15 Version-02 1. Scope 1.1. Purpose This paper reviews the implementation of the ANSI/AAMI/IEC
More informationDevelopment models. 1 Introduction. 2 Analyzing development models. R. Kuiper and E.J. Luit
Development models R. Kuiper and E.J. Luit 1 Introduction We reconsider the classical development models: the Waterfall Model [Bo76], the V-Model [Ro86], the Spiral Model [Bo88], together with the further
More informationPRINCE2:2009 Glossary of Terms (English)
accept (risk response) acceptance acceptance criteria activity agile methods approval approver assumption assurance A risk response to a threat where a conscious and deliberate decision is taken to retain
More informationProject Management. What is Project Management?
Project Management Project Management enables your business to proceed with new initiatives in a way that allows: Costs to be controlled Agreed outcomes to be measured and confirmed Timescales to be met
More informationProject Execution, Monitoring and Control (IS PM 8. Lecture; 2012 Spring)
Project Execution, Monitoring and Control Topics of the lecture as follows: PDCA cycle Project execution processes by PMBOK Project monitoring and controlling processes by PMBOK Project monitoring and
More informationCHAPTER_3 SOFTWARE ENGINEERING (PROCESS MODELS)
CHAPTER_3 SOFTWARE ENGINEERING (PROCESS MODELS) Prescriptive Process Model Defines a distinct set of activities, actions, tasks, milestones, and work products that are required to engineer high quality
More informationIT Project Management
IT Project Management IT Project Management provides a structured approach to making things happen and in doing so, enables initiatives (projects) to be delivered to time, quality and budget. www.business.wales.gov.uk/superfastbusinesswales
More informationATTACHMENTS: 1. CUSTOMER EXPERIENCE PROGRAM CHART
INFORMATION REPORT REPORT TITLE: ITEM NUMBER: 1176 DATE OF MEETING: 14 JULY 2014 AUTHOR: JOB TITLE: RESPONSIBLE OFFICER: JOB TITLE: COMMUNITY GOAL: CUSTOMER EXPERIENCE PROGRAM ANNABEL SHINKFIELD MANAGER
More informationLeveraging RUP, OpenUP, and the PMBOK. Arthur English, GreenLine Systems
Software Project Management Leveraging RUP, OpenUP, and the PMBOK Arthur English, GreenLine Systems GreenLine Systems Inc. 2003 2013 My Background 30+ years of IT project management experience with both
More informationHow To Understand The Software Process
Ingegneria del Software Corso di Laurea in Informatica per il Management Software process model Davide Rossi Dipartimento di Informatica Università di Bologna The task of the software development team
More informationNFSA Project Management Guidelines
NFSA Project Management Guidelines Project Management Guide Purpose of this Guide This Guide outlines the NFSA Project Management Guidelines, and includes: NFSA Project Life Cycle Governance Roles and
More informationEstablishing your Automation Development Lifecycle
Establishing your Automation Development Lifecycle Frequently I engage clients in assessing and improving their automation efforts. The discussion normally starts from a position of frustration We ve invested
More informationGénie Logiciel et Gestion de Projets. Project Management
Génie Logiciel et Gestion de Projets Project Management 1 Roadmap Project Management: Why and what? Risk management Scoping and estimation, planning and scheduling Dealing with delays Staffing, directing,
More informationDeveloping SOA solutions using IBM SOA Foundation
Developing SOA solutions using IBM SOA Foundation Course materials may not be reproduced in whole or in part without the prior written permission of IBM. 4.0.3 4.0.3 Unit objectives After completing this
More informationProject Management Office (PMO)
Contents I. Overview of Project Management...4 1. Project Management Guide (PMG)...4 1.1 Introduction...4 1.2 Scope...6 1.3 Project Types...6 2. Document Overview, Tailoring, and Guidance...7 3. The Project
More informationEMC PERSPECTIVE. Adopting an Agile Approach to OSS/BSS Development
EMC PERSPECTIVE Adopting an Agile Approach to OSS/BSS Development Reader ROI The agile software methodology is different from the traditional approach in that requirements gathering and analysis, design,
More informationJ O B S P E C I F I C A T I O N
J O B S P E C I F I C A T I O N DIRECTORATE: Corporate Services DIVISION/SECTION/UNIT: Information and Business Change / ICT Services / Solutions Software UNIT MANAGER: POST TITLE: JOB FAMILY & ROLE PROFILE:
More informationPositive Train Control (PTC) Program Management Plan
Positive Train Control (PTC) Program Management Plan Proposed Framework This document is considered an uncontrolled copy unless it is viewed online in the organization s Program Management Information
More informationHow To Write An Slcm Project Plan
SLCM 2003.1 Artifacts in a Nutshell ( as of 01/21/2005) Project Development Phases Pension Benefit Guaranty Corporation s (PBGC) System Life Cycle Methodology (SLCM) is comprised of five project development
More informationA Case study based Software Engineering Education using Open Source Tools
A Case study based Software Engineering Education using Open Source Tools Sowmya B J Dept. of CSE M. S. Ramaiah Institute of Technology sowmyabj@msrit.edu Srinidhi Hiriyannaiah Dept. of CSE M.S. Ramaiah
More informationThe Data Integration Strategy
White Paper The Data Integration Strategy Take Aim Before You Shoot Introduction Much has been written about the need to align business and technology, but that alignment has to begin up front. In fact,
More informationSurveying and evaluating tools for managing processes for software intensive systems
Master Thesis in Software Engineering 30 Credits, Advanced Level Surveying and evaluating tools for managing processes for software intensive systems Anuradha Suryadevara IDT Mälardalen University, ABB
More informationRUP Design. Purpose of Analysis & Design. Analysis & Design Workflow. Define Candidate Architecture. Create Initial Architecture Sketch
RUP Design RUP Artifacts and Deliverables RUP Purpose of Analysis & Design To transform the requirements into a design of the system to-be. To evolve a robust architecture for the system. To adapt the
More informationREVIEW ON THE EFFECTIVENESS OF AGILE UNIFIED PROCESS IN SOFTWARE DEVELOPMENT WITH VAGUE SYSTEM REQUIREMENTS
REVIEW ON THE EFFECTIVENESS OF AGILE UNIFIED PROCESS IN SOFTWARE DEVELOPMENT WITH VAGUE SYSTEM REQUIREMENTS Lisana Universitas Surabaya (UBAYA), Raya Kalirungkut, Surabaya, Indonesia E-Mail: lisana@ubaya.ac.id
More informationProject Scorecard Template
Project Scorecard Template 1. Identify criteria for success: Review the objectives and deliverables in the Project Definition, as well as any other existing information that is relevant to the project.
More informationPlan-Driven Methodologies
Plan-Driven Methodologies The traditional way to develop software Based on system engineering and quality disciplines (process improvement) Standards developed from DoD & industry to make process fit a
More informationUnit 1 Learning Objectives
Fundamentals: Software Engineering Dr. Rami Bahsoon School of Computer Science The University Of Birmingham r.bahsoon@cs.bham.ac.uk www.cs.bham.ac.uk/~rzb Office 112 Y9- Computer Science Unit 1. Introduction
More informationHow To Adopt Rup In Your Project
08Bergstrom.C08 Page 127 Thursday, December 4, 2003 12:06 PM 8 How to Adopt RUP in Your Project Support Projects with Mentoring Make a High-Level Adoption Plan and Develop a Communication Plan Project
More informationORACLE PROJECT MANAGEMENT
ORACLE PROJECT MANAGEMENT KEY FEATURES Oracle Project Management provides project managers the WORK MANAGEMENT Define the workplan and associated resources; publish and maintain versions View your schedule,
More informationDriving Your Business Forward with Application Life-cycle Management (ALM)
Driving Your Business Forward with Application Life-cycle Management (ALM) Published: August 2007 Executive Summary Business and technology executives, including CTOs, CIOs, and IT managers, are being
More informationTDWI strives to provide course books that are content-rich and that serve as useful reference documents after a class has ended.
Previews of TDWI course books are provided as an opportunity to see the quality of our material and help you to select the courses that best fit your needs. The previews can not be printed. TDWI strives
More informationProject Management Process
Project Management Process Description... 1 STAGE/STEP/TASK SUMMARY LIST... 2 Project Initiation 2 Project Control 4 Project Closure 5 Project Initiation... 7 Step 01: Project Kick Off 10 Step 02: Project
More information3C05: Unified Software Development Process
3C05: Unified Software Development Process 1 Unit 5: Unified Software Development Process Objectives: Introduce the main concepts of iterative and incremental development Discuss the main USDP phases 2
More informationExample IEEE software project management plan (SPMP)
Example IEEE software project management plan (SPMP) Source: Object Oriented & Classical Software Engineering, 7 th edition, Stephen R. Schach, pg. 590 594 This plan is for development of the MSG product
More informationSelf Assessment Risk Management Toolkit Summary
Self Assessment Risk Management Toolkit Summary Objectives of Toolkit Self Assessment Risk Management The objectives of the Risk Toolkit are: Helps Risk Managers identify and mitigate the risks in their
More informationThe most suitable system methodology for the proposed system is drawn out.
3.0 Methodology 3.1 Introduction In this chapter, five software development life cycle models are compared and discussed briefly. The most suitable system methodology for the proposed system is drawn out.
More informationProject Management. Software Projects vs. Engineering Projects
Read Chapters (a) Project Management, (b) Project Scheduling and (c) Risk Management from Pressman for this lecture. Project Management Rahul Premraj + Andreas Zeller reliability of data questioned! Software
More information1.20 Appendix A Generic Risk Management Process and Tasks
1.20 Appendix A Generic Risk Management Process and Tasks The Project Manager shall undertake the following generic tasks during each stage of Project Development: A. Define the project context B. Identify
More informationThe Unified Software Development Process
The Unified Software Development Process Technieche Universal Darmstadt FACHBEREICH IN-FORMAHK BLIOTHEK Ivar Jacobson Grady Booch James Rumbaugh Rational Software Corporation tnventar-nsr.: Sachgebiete:
More informationAppendix V Risk Management Plan Template
Appendix V Risk Management Plan Template Version 2 March 7, 2005 This page is intentionally left blank. Version 2 March 7, 2005 Title Page Document Control Panel Table of Contents List of Acronyms Definitions
More informationWork Breakdown Structure (WBS)
Work Breakdown Structure (WBS) The building blocks of a schedule start with a Work Breakdown Structure (WBS). The WBS is a hierarchical reflection of all the work in the project in terms of deliverables.
More informationLecture Notes #27: Software Risk Management
EECS816: Object-Oriented Software Development Slide 2 Lecture Notes #27: Software Risk Management Software risks: What can go wrong? What is the likelihood? What will be the damage? What can be done about
More information10 Critical Steps to Create a Project Plan
10 Critical Steps to Create a Project Plan Elizabeth Larson, PMP, CBAP and Richard Larson, PMP, CBAP Principals, Watermark Learning, Inc. Industry Article Watermark Learning 7300 Metro Blvd, Suite 207
More informationITRM Guideline CPM 110-01 Date: January 23, 2006 SECTION 4 - PROJECT EXECUTION AND CONTROL PHASE
PROJECT MANAGEMENT GUIDELINE SECTION 4 - PROJECT EXECUTION AND CONTROL PHASE Table of Contents Introduction... 3 Project Execution and Control Phase Overview... 3 Activities and Documents in the Execution
More informationRISK MANAGEMENT OVERVIEW - APM Project Pathway (Draft) RISK MANAGEMENT JUST A PART OF PROJECT MANAGEMENT
RISK MANAGEMENT OVERVIEW - APM Project Pathway (Draft) Risk should be defined as An uncertain event that, should it occur, would have an effect (positive or negative) on the project or business objectives.
More informationPHASE 3: PLANNING PHASE
PHASE 3: PLANNING PHASE The ning Phase focuses principally on required project planning work. Proper comprehensive project planning is essential to a successful IT project, and incomplete project planning
More informationAgile Unified Process
INTERNATIONAL JOURNAL OF COMPUTER SCIENCE AND MOBILE APPLICATIONS - IJCSMA Agile Unified Process Charles Edeki Ph.D, American Intercontinental University, Department of Information Technology, 160 Parkside
More informationReaching CMM Levels 2 and 3 with the Rational Unified Process
Reaching CMM Levels 2 and 3 with the Rational Unified Process Rational Software White Paper TP174 Table of Contents INTRODUCTION... 1 LEVEL-2, REPEATABLE... 3 Requirements Management... 3 Software Project
More informationDevelop Project Charter. Develop Project Management Plan
Develop Charter Develop Charter is the process of developing documentation that formally authorizes a project or a phase. The documentation includes initial requirements that satisfy stakeholder needs
More informationWelcome to the Data Analytic Toolkit PowerPoint presentation an introduction to project management. In this presentation, we will take a brief look
Welcome to the Data Analytic Toolkit PowerPoint presentation an introduction to project management. In this presentation, we will take a brief look at project management to understand the process and some
More informatione-tourism Marketing Specialist
! Role Profile for e-tourism Marketing Specialist e-jobs-observatory.eu European Profiles in e-tourism Functions e-tourism Marketing Specialist 1 e-tourism Marketing Specialist 1. Role Profile Role title
More informationAn Introduction to the PRINCE2 project methodology by Ruth Court from FTC Kaplan
An Introduction to the PRINCE2 project methodology by Ruth Court from FTC Kaplan Of interest to students of Paper P5 Integrated Management. Increasingly, there seems to be a greater recognition of the
More informationBasic Unified Process: A Process for Small and Agile Projects
Basic Unified Process: A Process for Small and Agile Projects Ricardo Balduino - Rational Unified Process Content Developer, IBM Introduction Small projects have different process needs than larger projects.
More informationSoftware Engineering Graduate Project Effort Analysis Report
Software Engineering Graduate Project Effort Analysis Report Zhihao Chen Center for Software Engineering, University of Southern California, Los Angeles 90089 California, USA {zhihaoch}@cse.usc.edu Abstract:
More informationProject management: an SE Perspective
Project management: an SE Perspective Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 5 Slide 1 Objectives To explain the main tasks undertaken by project managers To introduce software
More informationPROJECT PLAN TEMPLATE
Treasury Board of Canada Secretariat Secrétariat du Conseil du Trésor du Canada Enhanced Management Framework for Information Management/Information Technology PROJECT PLAN TEMPLATE Document Revision Draft
More informationESKISP6055.01 Manage security testing
Overview This standard covers the competencies concerning with managing security testing activities. Including managing resources activities and deliverables. This includes planning, conducting and reporting
More information<Project Name> Quality Assurance Plan
Version [Note: The following template is provided for use with the Rational Unified Process. Text enclosed in square brackets and displayed in blue italics (style=infoblue) is included
More information