Phases, Activities, and Work Products. Object-Oriented Software Development. Project Management. Requirements Gathering

Save this PDF as:
 WORD  PNG  TXT  JPG

Size: px
Start display at page:

Download "Phases, Activities, and Work Products. Object-Oriented Software Development. Project Management. Requirements Gathering"

Transcription

1 Object-Oriented Software Development What is Object-Oriented Development Object-Oriented vs. Traditional Development An Object-Oriented Development Framework Phases, Activities, and Work Products Phases, Activities, and Work Products A development phase is a state of product development that focuses on making progress on a particular aspect or facet. A work product is a concrete result of a planned project-related activity such as analysis or project management. Work products include items delivered to the customer and items used purely internally within a project. [OOTC 97] OOSD--fall'04 Copyright by 51 OOSD--fall'04 Copyright by 52 Project Management Requirements Gathering Project Management After initial project planning, define development activities and allocate resources to the activities. Allocate requirements to releases and manage project schedule and issues. Project Workbook Outline Resource Plan Schedule Risk/Option Management Plan Test Plan Issues Metrics An organized list of work products that are expected to comprise the project workbook. Analysis of the resources required for the successful completion of the project. A task time line showing dates, milestones, critical path, etc. Lists development options and describes the plan for minimizing project risks. Outlines the project s plan for testing the application. A list of outstanding issues, questions, and concerns that are reviewed on a regular basis. The planned and actual measurements, and statistics. Requirements Gathering Group functional requirements (into use cases) and prioritize them. Problem Statement Use Cases (functional requirements) Nonfunctional Requirements Prioritized Requirements Description of the problem to be solved in non-technical terms. An OO formalization of functional requirements describing the usage of the system by external agents. Requirements that do not belong to user function, such as performance, platform, quality. Defines the relative priorities of functional and nonfunctional system requirements. OOSD--fall'04 Copyright by 53 OOSD--fall'04 Copyright by 54

2 UI Design OOA&D UI Design Document how users will interact with the application. Guidelines Screen Flows Screen Layouts UI Prototype Describes the user interface guidelines and standards. Documents user navigation through the application s user interface. Documents details of all screens. A prototype built to show users the look and feel. Object- Oriented Analysis & Design Guidelines System Architecture Analysis: Identify objects, their attributes, behaviors, and interrelationships. Develop solutions to system usage scenarios in terms of active objects that group related tasks and communicate with other objects in order to complete them. Design: Plan a solution to the problem examined during analysis in terms of interacting objects, within the constraints specified by the nonfunctional requirements. Object Model Scenarios OIDs (Object Interaction Diagrams) State Models Classes File Structure Traceability Matrix Records the details of the analysis and design approach being followed. Description of the high-level components/ structures of the system and the design principles guiding the implementation. A consolidated model describing the classes of a system together with their responsibilities and static interrelationships. Descriptions of required systems behaviour. Scenarios refine use cases and are formalized in OIDs. A working out of a scenario, showing the interactions between objects to accomplish (the implementation of) a task. Show the life cycle of an object, i.e. its possible states and state transitions. Detailed descriptions of all classes. The files and their structure as required by the system. A cross-reference table that relates design elements to requirements. OOSD--fall'04 Copyright by 55 OOSD--fall'04 Copyright by 56 Implementation & Testing Miscellaneous Work Products Implementation Testing Systematically code the classes as specified in the class descriptions so that they can be built and installed on the target platforms. Insure that the application meets the requirements set forth in the problem statement and requirements gathering work products. Coding Guidelines Source Code User Support Materials Prototypes Test Cases A description of the coding guidelines and standards. The actual implementation of the product. Documentation, delivered in various forms, which support the customer s use of the product. Intermediate products. The testing and quality assurance work products. Miscellaneous Document miscellaneous Glossary Definitions and terminology. activities in appendices and add them to the Historical Back-level work products. project workbook. Work Products Meeting Minutes Time Logs The minutes of all project meetings. The time logs of the people allocated to the project. OOSD--fall'04 Copyright by 57 OOSD--fall'04 Copyright by 58

3 Course Related Work Products Course organization Document course specific aspects and support course organization. Team Description Subcontract Prototype Evaluation Weekly Reports Presentations Final Report A presentation of your team and the members of the team. A contract with an external team to deliver a specified piece of software. An evaluation of another team s prototype. Progress reports with up-todate project information. Materials from the team presentations. A complete document set. OOSD--fall'04 Copyright by 59 Work Product Definition Defined in detail in [OOTC 97]: Description Purpose Participants Timing Techniques Strengths Weaknesses Notation Traceability Advice & Guidance Verification Examples References Importance See homepage>/deliverables.html for a detailed description of the course s deliverables and for an example from a previous course. OOSD--fall'04 Copyright by 60 Contents Project Management Introduction Object-Oriented Software Development Project Management Requirements Gathering (G)UI Design Object-Oriented Analysis and Design Advanced Topics in OOA&D Implementation and Testing References Just do it. Think first and look what you did. Activity Planning Activity Evaluation produce to produce input to to improve Result Result OOSD--fall'04 Copyright by 61 OOSD--fall'04 Copyright by 62

4 Project Management Activities Project acquisition Initial project planning Resources assessment Risk and option analysis Cost estimation Project scheduling Project tracking and control Reporting Not required in this course Project Scheduling Define work breakdown structure Break down the project into manageable tasks Identify all activities/ tasks that a project must undertake Distribute effort Define duration and start/ end dates for all activities/ tasks Identify parallelism Assign tasks Assign resources to tasks Do not forget the project functions, lectures, meetings, etc. OOSD--fall'04 Copyright by 63 OOSD--fall'04 Copyright by 64 Example Effort Distribution Another Group 250 total time in h actual plan week35 week36 week37 week38 week39 week40 week41 week42 week43 week44 Lectures Meetings Planning Requirements GUI design Analysis Design Testing Coding Presentations Subcontract Code subc. Evaluation of prototype Manual Final report weekly reports and meeting minutes Other OOSD--fall'04 Copyright by Lectures Administration Study assignments Documentation Implementation Integration Testing OOSD--fall'04 Copyright by 66

5 Another Group (10 cr version) Another Group (10 cr version) OOSD--fall'04 Copyright by 67 OOSD--fall'04 Copyright by 68 A Project Schedule Time vs budget vs quality work overtime more time fix a problem higher costs reduce control/ documentation decreasing quality OOSD--fall'04 Copyright by 69 OOSD--fall'04 Copyright by 70

6 Project Tracking and Control Risk Management Task management Risk management Issue management Quality management Don t forget to schedule time for these activities Investigate potential risk factors Risk Likelihood of occurrence Impact Define mitigation strategies (i.e. be prepared) What can be done to avoid the problem(s) What can be done to solve the problem(s) Monitor risks Determine if predicted risk occurs Properly apply risk aversion steps Collect info for future risk analysis OOSD--fall'04 Copyright by 71 OOSD--fall'04 Copyright by 72 Example Assume Risk = High staff turnover Likelihood of occurrence = 70% Impact = Increase project time by 15%, project cost by 12% Mitigation strategy Identify high turnover causes Reduce causes before project starts Develop techniques to assure work continuity in light of turnover For example or Top Ten Project Risks Staff deficiencies Unrealistic schedules and budgets Developing the wrong functions Developing the wrong interface Over-engineering Requirements volatility Externally developed items Externally performed tasks Performance problems Assumptions on technology OOSD--fall'04 Copyright by 73 See Jalote: An Integrated Approach to Software Engineering, Springer OOSD--fall'04 Copyright by 74

7 Software s Ten Essentials A product specification A detailed user interface prototype A realistic schedule Explicit priorities Active risk management A quality assurance plan Detailed activity lists Software configuration management Software architecture An integration plan Significant Student Project Risks Personnel schortfalls Lack of Commitment Interpersonal incompatibility Lack of critical project skills (technical and management) Communication problems Unrealistic schedule, budget, and process External (COTS) components Requirements mismatch UI mismatch See IEEE Software 14(2), Mar/Apr 1997, OOSD--fall'04 Copyright by 75 See Proceedings CSEE&T 2004, OOSD--fall'04 Copyright by Critical Software Practices TM OOSD--fall'04 Copyright by 77 Weekly Reports Will help you and us to track project progress Provides information/ data to access project status Major events and/or decisions Major changes to schedule (and resources) Top-10 risk list Major changes to issues list Statistics/ data Is project on schedule? Resources spent (per person, per category, last week, accumulated) Productivity (LOC, LOD, ; last week, accumulated) Summary of issues change log (new issues, closed issues, ; last week, accumulated) (QA?) () OOSD--fall'04 Copyright by 78

8 An Example Top-10 Risk List Risk Items COTS availability Weekly Ranking Current Previous # Weeks Risk Resolution Progress Performed multilingual NLP COTS survey. Applied for academic discount. Personal shortfalls Two members are not available for this week. Other team members will put extra effort this week. OOSD--fall'04 Copyright by 79

Contents. Today Project Management. Project Management. Last Time - Software Development Processes. What is Project Management?

Contents. Today Project Management. Project Management. Last Time - Software Development Processes. What is Project Management? Contents Introduction Software Development Processes Project Management Requirements Engineering Software Construction Group processes Quality Assurance Software Management and Evolution Last Time - Software

More information

<name of project> Software Project Management Plan

<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 information

PROJECT MANAGEMENT PLAN TEMPLATE < PROJECT NAME >

PROJECT 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 information

8. Master Test Plan (MTP)

8. Master Test Plan (MTP) 8. Master Test Plan (MTP) The purpose of the Master Test Plan (MTP) is to provide an overall test planning and test management document for multiple levels of test (either within one project or across

More information

CS/SWE 321 Sections -001 & -003. Software Project Management

CS/SWE 321 Sections -001 & -003. Software Project Management CS/SWE 321 Sections -001 & -003 Software Project Management Copyright 2014 Hassan Gomaa All rights reserved. No part of this document may be reproduced in any form or by any means, without the prior written

More information

This is the software system proposal document for the <name of the project> project sponsored by <name of sponsor>.

This is the software system proposal document for the <name of the project> project sponsored by <name of sponsor>. Guide to Preparing the SOFTWARE PROJECT MANAGEMENT PLAN R. Buckley CSc 190 Senior Project Department of Computer Science - College of Engineering and Computer Science California State University, Sacramento

More information

Department of Administration Portfolio Management System 1.3 June 30, 2010

Department of Administration Portfolio Management System 1.3 June 30, 2010 E 06/ 30/ 2010 EX AM PL 1. 3 06/ 28/ 2010 06/ 24/ 2010 06/ 23/ 2010 06/ 15/ 2010 06/ 18/ 2010 Portfolio System 1.3 June 30, 2010 Contents Section 1. Project Overview... 1 1.1 Project Description... 1 1.2

More information

Essentials of the Quality Assurance Practice Principles of Testing Test Documentation Techniques. Target Audience: Prerequisites:

Essentials of the Quality Assurance Practice Principles of Testing Test Documentation Techniques. Target Audience: Prerequisites: Curriculum Certified Software Tester (CST) Common Body of Knowledge Control Procedures Problem Resolution Reports Requirements Test Builds Test Cases Test Execution Test Plans Test Planning Testing Concepts

More information

(Refer Slide Time: 01:52)

(Refer Slide Time: 01:52) Software Engineering Prof. N. L. Sarda Computer Science & Engineering Indian Institute of Technology, Bombay Lecture - 2 Introduction to Software Engineering Challenges, Process Models etc (Part 2) This

More information

SOFTWARE DEVELOPMENT PLAN

SOFTWARE DEVELOPMENT PLAN SOFTWARE DEVELOPMENT PLAN This document outline is based on the IEEE Standard 1058.1-1987 for Software Project Management Plans. This is the controlling document for managing a software project, and it

More information

Time Monitoring Tool Software Development Plan. Version <1.1>

Time Monitoring Tool Software Development Plan. Version <1.1> Time Monitoring Tool Software Development Plan Version Revision History Date Version Description Author 10/01/01 1.0 First Draft Sabrina Laflamme 12/01/01 1.1 Completion of Document John Lemon Page

More information

Partnering for Project Success: Project Manager and Business Analyst Collaboration

Partnering for Project Success: Project Manager and Business Analyst Collaboration Partnering for Project Success: Project Manager and Business Analyst Collaboration By Barbara Carkenord, CBAP, Chris Cartwright, PMP, Robin Grace, CBAP, Larry Goldsmith, PMP, Elizabeth Larson, PMP, CBAP,

More information

Develop Project Charter. Develop Project Management Plan

Develop 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 information

A Case study based Software Engineering Education using Open Source Tools

A 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 information

What is a life cycle model?

What is a life cycle model? What is a life cycle model? Framework under which a software product is going to be developed. Defines the phases that the product under development will go through. Identifies activities involved in each

More information

SEVEN KEY TACTICS FOR ENSURING QUALITY

SEVEN KEY TACTICS FOR ENSURING QUALITY SEVEN KEY TACTICS FOR ENSURING QUALITY 1 INTRODUCTION Besides avoiding disasters and fatal flaws, quality assurance (QA) delivers significant benefits for banks. Strong QA planning provides the groundwork

More information

Software Project Management Plan. Team Synergy Version: 1.0 Date: 1/27/03

Software Project Management Plan. Team Synergy Version: 1.0 Date: 1/27/03 Team Synergy Version: 1.0 Date: 1/27/03 Revision History Document Owner: Goran Momiroski Date Revision Description Author 11/26/2002 1.0 Document creation Goran Momiroski Team Synergy Page 1 1/27/2003

More information

Software Project Management Plan (SPMP)

Software Project Management Plan (SPMP) Software Project Management Plan (SPMP) The basic template to be used is derived from IEEE Std 1058-1998, IEEE Standard for Software Project Management Plans. The following is a template for the SPMP.

More information

Design Document Version 0.0

Design Document Version 0.0 Software Development Templates Design Document Version 0.0 Description of Project DOCUMENT NO: VERSION: CONTACT: EMAIL: Ivan Walsh DATE: 4/13/2004 Distribution is subject to copyright. Design Document

More information

Introduction and Overview

Introduction and Overview Introduction and Overview Definitions. The general design process. A context for design: the waterfall model; reviews and documents. Some size factors. Quality and productivity factors. Material from:

More information

BAL2-1 Professional Skills for the Business Analyst

BAL2-1 Professional Skills for the Business Analyst 1 BAL2-1 Professional Skills for the Business Analyst OVERVIEW This course trains participants to help business clients articulate their needs and wants, and to document them clearly, concisely, and completely.

More information

INFORMATION TECHNOLOGY GUIDELINE

INFORMATION TECHNOLOGY GUIDELINE COMMONWEALTH OF PENNSLVANIA DEPARTMENT OF HUMAN SERVICES INFORMATION TECHNOLOG GUIDELINE Name Of Guideline: System Development Methodology (SDM) Domain: Business Date Issued: 03/01/1999 Date Revised: 03/29/2016

More information

Requirements Engineering for Web Applications

Requirements Engineering for Web Applications Web Engineering Requirements Engineering for Web Applications Copyright 2013 Ioan Toma & Srdjan Komazec 1 What is the course structure? # Date Title 1 5 th March Web Engineering Introduction and Overview

More information

Request for Proposal for Application Development and Maintenance Services for XML Store platforms

Request for Proposal for Application Development and Maintenance Services for XML Store platforms Request for Proposal for Application Development and Maintenance s for ML Store platforms Annex 4: Application Development & Maintenance Requirements Description TABLE OF CONTENTS Page 1 1.0 s Overview...

More information

Appendix V Risk Management Plan Template

Appendix 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 information

CMMI for Development Quick Reference

CMMI for Development Quick Reference CAUSAL ANALYSIS AND RESOLUTION SUPPORT (ML5) The purpose of Causal Analysis and Resolution (CAR) is to identify causes of selected outcomes and take action to improve process performance. SG 1 Root causes

More information

How to Write a Software Process Procedures and Policy Manual for YOUR COMPANY

How to Write a Software Process Procedures and Policy Manual for YOUR COMPANY How to Write a Software Process for YOUR COMPANY 1. Introduction MicroTools is proposing to assist YOUR COMPANY in improving the existing software process. The purpose of this project is to both improve

More information

SOFTWARE DEVELOPMENT STANDARD FOR SPACECRAFT

SOFTWARE DEVELOPMENT STANDARD FOR SPACECRAFT SOFTWARE DEVELOPMENT STANDARD FOR SPACECRAFT Mar 31, 2014 Japan Aerospace Exploration Agency This is an English translation of JERG-2-610. Whenever there is anything ambiguous in this document, the original

More information

Information Technology Project Oversight Framework

Information Technology Project Oversight Framework i This Page Intentionally Left Blank i Table of Contents SECTION 1: INTRODUCTION AND OVERVIEW...1 SECTION 2: PROJECT CLASSIFICATION FOR OVERSIGHT...7 SECTION 3: DEPARTMENT PROJECT MANAGEMENT REQUIREMENTS...11

More information

Project Management Plan for

Project Management Plan for Project Management Plan for [Project ID] Prepared by: Date: [Name], Project Manager Approved by: Date: [Name], Project Sponsor Approved by: Date: [Name], Executive Manager Table of Contents Project Summary...

More information

SOFT 423: Software Requirements

SOFT 423: Software Requirements SOFT 423: Software Requirements Week 3 Class 1 Finish Elicitation & Start Analysis SOFT 423 Winter 2015 1 Last Class Questionnaires Document Inspection Requirements Stripping Use Cases Scenarios SOFT 423

More information

SOFTWARE REQUIREMENTS

SOFTWARE REQUIREMENTS SOFTWARE REQUIREMENTS http://www.tutorialspoint.com/software_engineering/software_requirements.htm Copyright tutorialspoint.com The software requirements are description of features and functionalities

More information

Introduction to the ITS Project Management Methodology

Introduction to the ITS Project Management Methodology Introduction to the ITS Project Management Methodology In September 1999 the Joint Legislative Committee on Performance Evaluation and Expenditure Review (PEER) produced a report entitled Major Computer

More information

Project Audit & Review Checklist. The following provides a detailed checklist to assist the PPO with reviewing the health of a project:

Project Audit & Review Checklist. The following provides a detailed checklist to assist the PPO with reviewing the health of a project: Project Audit & Review Checklist The following provides a detailed checklist to assist the PPO with reviewing the health of a project: Relevance (at this time) Theory & Practice (How relevant is this attribute

More information

CS 6361, SPRING 2010 Advanced Requirements Engineering Web Based Meeting Scheduler- Project Plan

CS 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 information

Frank Tsui. Orlando Karam. Barbara Bernal. State. University. Polytechnic. Ail of Southern JONES & BARTLETT LEARNING

Frank Tsui. Orlando Karam. Barbara Bernal. State. University. Polytechnic. Ail of Southern JONES & BARTLETT LEARNING Frank Tsui Orlando Karam Barbara Bernal Ail of Southern Polytechnic State JONES & BARTLETT LEARNING University Preface Hi Chapter 1 Writing a Program 1 1.1 A Simple Problem 2 1.2 Decisions, Decisions 2

More information

Business Analyst Work Plan. Presented by: Billie Johnson, CBAP CSM

Business Analyst Work Plan. Presented by: Billie Johnson, CBAP CSM Business Analyst Work Plan Presented by: Billie Johnson, CBAP CSM Agenda Topic Introduction Overview of a Business Analysis Work Plan Initiating a Business Analysis Effort Components of the Business Analysis

More information

PHASE 5: DESIGN PHASE

PHASE 5: DESIGN PHASE PHASE 5: DESIGN PHASE During the Design Phase, the system is designed to satisfy the requirements identified in the previous phases. The requirements identified in the Requirements Analysis Phase are transformed

More information

PROJECT MANAGEMENT PLAN Outline VERSION 0.0 STATUS: OUTLINE DATE:

PROJECT MANAGEMENT PLAN Outline VERSION 0.0 STATUS: OUTLINE DATE: PROJECT MANAGEMENT PLAN Outline VERSION 0.0 STATUS: OUTLINE DATE: Project Name Project Management Plan Document Information Document Title Version Author Owner Project Management Plan Amendment History

More information

CREDENTIALS & CERTIFICATIONS 2015

CREDENTIALS & CERTIFICATIONS 2015 THE COMMUNITY FOR TECHNOLOGY LEADERS www.computer.org CREDENTIALS & CERTIFICATIONS 2015 KEYS TO PROFESSIONAL SUCCESS CONTENTS SWEBOK KNOWLEDGE AREA CERTIFICATES Software Requirements 3 Software Design

More information

Custom Software Development Approach

Custom Software Development Approach Custom Software Development Approach Our approach to custom software development combines benefits from several standard development process models. We tend to have a well-defined, predictable and highly

More information

4. Software Project Management

4. Software Project Management 4. Software Subject/Topic/Focus: Management of Systems Engineering Projects Summary: Influences on projects and potential risks Software systems engineering and project management Activity network and

More information

This alignment chart was designed specifically for the use of Red River College. These alignments have not been verified or endorsed by the IIBA.

This alignment chart was designed specifically for the use of Red River College. These alignments have not been verified or endorsed by the IIBA. Red River College Course Learning Outcome Alignment with BABOK Version 2 This alignment chart was designed specifically for the use of Red River College. These alignments have not been verified or endorsed

More information

Software Engineering Reference Framework

Software Engineering Reference Framework Software Engineering Reference Framework Michel Chaudron, Jan Friso Groote, Kees van Hee, Kees Hemerik, Lou Somers, Tom Verhoeff. Department of Mathematics and Computer Science Eindhoven University of

More information

PROJECT PLAN TEMPLATE

PROJECT 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 information

Application of software product quality international standards through software development life cycle

Application of software product quality international standards through software development life cycle Central Page 284 of 296 Application of software product quality international standards through software development life cycle Mladen Hosni, Valentina Kirinić Faculty of Organization and Informatics University

More information

Requirements Engineering

Requirements Engineering Murali Chemuturi Requirements Engineering and Management for Software Development Projects Foreword by Tom Gilb ^ Springer Contents 1 Introduction to Requirements Engineering and Management... 1 1.1 What

More information

Software Development Methodologies

Software Development Methodologies Software Development Methodologies Lecturer: Raman Ramsin Lecture 5 Integrated Object-Oriented Methodologies: OPM and Catalysis 1 Object Process Methodology (OPM) Introduced by Dori in 1995 Primarily intended

More information

Your Software Quality is Our Business. INDEPENDENT VERIFICATION AND VALIDATION (IV&V) WHITE PAPER Prepared by Adnet, Inc.

Your Software Quality is Our Business. INDEPENDENT VERIFICATION AND VALIDATION (IV&V) WHITE PAPER Prepared by Adnet, Inc. INDEPENDENT VERIFICATION AND VALIDATION (IV&V) WHITE PAPER Prepared by Adnet, Inc. February 2013 1 Executive Summary Adnet is pleased to provide this white paper, describing our approach to performing

More information

System Development Life Cycle Guide

System Development Life Cycle Guide TEXAS DEPARTMENT OF INFORMATION RESOURCES System Development Life Cycle Guide Version 1.1 30 MAY 2008 Version History This and other Framework Extension tools are available on Framework Web site. Release

More information

APICS INSIGHTS AND INNOVATIONS ENHANCING PROJECT MANAGEMENT

APICS INSIGHTS AND INNOVATIONS ENHANCING PROJECT MANAGEMENT APICS INSIGHTS AND INNOVATIONS ENHANCING PROJECT MANAGEMENT APICS INSIGHTS AND INNOVATIONS ABOUT THIS REPORT Supply chain project management is a process that allows you to coordinate resources and activities

More information

Project Plan for <project name>

Project Plan for <project name> Note: Text displayed in blue italics is included to provide guidance to the author and should be deleted or hidden before publishing the document. This template can be used at it is, or to complete and

More information

Information Technology Project Oversight Framework

Information Technology Project Oversight Framework State of California California Technology Agency Information Technology Project Oversight Framework SIMM Section 45 Revised April 2011 This Page Intentionally Left Blank California Technology Agency Table

More information

Improve Your Process With Online Good Practices 1

Improve Your Process With Online Good Practices 1 Improve Your Process With Online Good Practices 1 Karl Wiegers Process Impact www.processimpact.com Most software developers are allergic to paper. As organizations improve their software development and

More information

Contents. Introduction and System Engineering 1. Introduction 2. Software Process and Methodology 16. System Engineering 53

Contents. Introduction and System Engineering 1. Introduction 2. Software Process and Methodology 16. System Engineering 53 Preface xvi Part I Introduction and System Engineering 1 Chapter 1 Introduction 2 1.1 What Is Software Engineering? 2 1.2 Why Software Engineering? 3 1.3 Software Life-Cycle Activities 4 1.3.1 Software

More information

Project Management Plan Template

Project Management Plan Template Abstract: This is the project management plan document for . This is a controlled document and should be maintained in a configuration environment. Project Management Plan Template Contents REVISION

More information

3SL. Requirements Definition and Management Using Cradle

3SL. Requirements Definition and Management Using Cradle 3SL Requirements Definition and Management Using Cradle November 2014 1 1 Introduction This white paper describes Requirements Definition and Management activities for system/product development and modification

More information

The Project Management Plan will be used to guide, communicate and coordinate project efforts.

The Project Management Plan will be used to guide, communicate and coordinate project efforts. F.1 General Implementation Contractor Deliverables include critical system planning and development components. Sufficient deliverables have been identified at key steps in the project to guide the project

More information

NUMBER: 12.PM-004 RESPONSIBILITY: Office of Project Support Services REVISION: 4 APPROVED BY: TITLE SUBJECT: Head, Office of Project Support Services

NUMBER: 12.PM-004 RESPONSIBILITY: Office of Project Support Services REVISION: 4 APPROVED BY: TITLE SUBJECT: Head, Office of Project Support Services SUBJECT: FERMI RESEARCH ALLIANCE PROCEDURES PROJECT MANAGEMENT NUMBER: 12.PM-004 RESPONSIBILITY: Office of Project Support Services REVISION: 4 APPROVED BY: TITLE Head, Office of Project Support Services

More information

Noorul Islam College of Engineering M. Sc. Software Engineering (5 yrs) IX Semester XCS592- Software Project Management

Noorul Islam College of Engineering M. Sc. Software Engineering (5 yrs) IX Semester XCS592- Software Project Management Noorul Islam College of Engineering M. Sc. Software Engineering (5 yrs) IX Semester XCS592- Software Project Management 8. What is the principle of prototype model? A prototype is built to quickly demonstrate

More information

Enterprise Test Management Standards

Enterprise Test Management Standards Enterprise Test Management Standards Version 4.0 09/28/2012 Document Number: FSA_TOADG_STDS_TEST.TMS_001 Document Version Control This section summarizes this document revision history. Each entry includes

More information

Risk Mitigation, Monitoring and Management Plan

Risk Mitigation, Monitoring and Management Plan Risk Mitigation, Monitoring and Management Plan Introduction Scope and intent of RMMM activities The goal of the risk mitigation, monitoring and management plan is to identify as many potential risks as

More information

Introduction. Architecture Re-engineering. Systems Consolidation. Data Acquisition. Data Integration. Database Technology

Introduction. Architecture Re-engineering. Systems Consolidation. Data Acquisition. Data Integration. Database Technology Introduction Data migration is necessary when an organization decides to use a new computing system or database management system that is incompatible with the current system. Architecture Re-engineering

More information

Communication Diagrams

Communication Diagrams Communication Diagrams Massimo Felici Realizing Use cases in the Design Model 1 Slide 1: Realizing Use cases in the Design Model Use-case driven design is a key theme in a variety of software processes

More information

Software Engineering. An Introduction. Fakhar Lodhi

Software Engineering. An Introduction. Fakhar Lodhi Software Engineering An Introduction Fakhar Lodhi 1 Engineering The science concerned with putting scientific knowledge to practical use. Webster s Dictionary Physics versus Electrical Engineering 2 Software

More information

Knowledge Area Inputs, Tools, and Outputs. Knowledge area Process group/process Inputs Tools Outputs

Knowledge Area Inputs, Tools, and Outputs. Knowledge area Process group/process Inputs Tools Outputs HUMAN RESOURCE MANAGEMENT Organizational planning Staff Acquisition Project interfaces such as organizational interfaces, technical interfaces and interpersonal interfaces. Staffing requirements Staffing

More information

Software Project Audit Process

Software Project Audit Process Software Project Audit Process Version 1.2 Information and Communication Technology Agency of Sri Lanka July 2013 Copyright 2011 ICTA Software Project Audit Process-v-1.2 Revision History Date Version

More information

Course Outline. Foundation of Business Analysis Course BA30: 4 days Instructor Led

Course Outline. Foundation of Business Analysis Course BA30: 4 days Instructor Led Foundation of Business Analysis Course BA30: 4 days Instructor Led Prerequisites: No prerequisites - This course is suitable for both beginner and intermediate Business Analysts who would like to increase

More information

Project Lifecycle Management (PLM)

Project Lifecycle Management (PLM) Project Lifecycle Management (PLM) Process or Tool? Why PLM? Project Definition Project Management NEW REQUEST/ INITIATIVES SUPPORT (Quick fixes) PROJECT (Start Finish) ONGOING WORK (Continuous) ENHANCEMENTS

More information

PROJECT RISK MANAGEMENT

PROJECT RISK MANAGEMENT PROJECT RISK MANAGEMENT DEFINITION OF A RISK OR RISK EVENT: A discrete occurrence that may affect the project for good or bad. DEFINITION OF A PROBLEM OR UNCERTAINTY: An uncommon state of nature, characterized

More information

STC 2015 Tutorial Part 2 Managing Technical Debt for Software and Systems Development Projects

STC 2015 Tutorial Part 2 Managing Technical Debt for Software and Systems Development Projects STC 2015 Tutorial Part 2 Managing Technical Debt for Software and Systems Development Projects IEEE Software Technology Conference Long Beach, CA October 12, 2015 Tutorial agenda Part 1: introductions

More information

ájoƒ ùdg á«hô dg áµلªÿg Yesser Overall SDLC Process Definition

ájoƒ ùdg á«hô dg áµلªÿg Yesser Overall SDLC Process Definition ájoƒ ùdg á«hô dg áµلªÿg Yesser Overall SDLC Process Definition Version 0.6 - Page 3 / 43 Table of Contents 1. Process Introduction... 5 1.1. Process Scope... 5 1.2. Process Objectives and Benefits... 5

More information

Utilizing Defect Management for Process Improvement. Kenneth Brown, CSQA, CSTE kdbqa@yahoo.com

Utilizing Defect Management for Process Improvement. Kenneth Brown, CSQA, CSTE kdbqa@yahoo.com Utilizing Defect Management for Process Improvement Kenneth Brown, CSQA, CSTE kdbqa@yahoo.com What This Presentation Will Cover How to Appropriately Classify and Measure Defects What to Measure in Defect

More information

Capacity Plan. Template. Version X.x October 11, 2012

Capacity Plan. Template. Version X.x October 11, 2012 Template Version X.x October 11, 2012 This is an integral part of infrastructure and deployment planning. It supports the goal of optimum provisioning of resources and services by aligning them to business

More information

Project Management Guidelines

Project Management Guidelines Project Management Guidelines 1. INTRODUCTION. This Appendix (Project Management Guidelines) sets forth the detailed Project Management Guidelines. 2. PROJECT MANAGEMENT PLAN POLICY AND GUIDELINES OVERVIEW.

More information

Software Development Life Cycle (SDLC)

Software Development Life Cycle (SDLC) Software Development Life Cycle (SDLC) Supriyo Bhattacharjee MOF Capability Maturity Model (CMM) A bench-mark for measuring the maturity of an organization s software process CMM defines 5 levels of process

More information

Rational Unified Process Process Description and Workflows

Rational Unified Process Process Description and Workflows Rational Unified Process Process Description and Workflows Mike Fourman Describing Processes The RUP uses four elements to describe processes: Workers describe a role, some people have many roles. Activities

More information

Process Methodology. Wegmans Deli Kiosk. for. Version 1.0. Prepared by DELI-cious Developers. Rochester Institute of Technology

Process Methodology. Wegmans Deli Kiosk. for. Version 1.0. Prepared by DELI-cious Developers. Rochester Institute of Technology Process Methodology for Wegmans Deli Kiosk Version 1.0 Prepared by DELI-cious Developers Rochester Institute of Technology September 15, 2013 1 Table of Contents 1. Process... 3 1.1 Choice... 3 1.2 Description...

More information

Expert Reference Series of White Papers. A Business Analyst s Glossary for Project Management Terminology 1-800-COURSES. www.globalknowledge.

Expert Reference Series of White Papers. A Business Analyst s Glossary for Project Management Terminology 1-800-COURSES. www.globalknowledge. Expert Reference Series of White Papers A Business Analyst s Glossary for Project Management Terminology 1-800-COURSES www.globalknowledge.com A Business Analyst s Glossary for Project Management Terminology

More information

Acknowledgement. Software Engineering. CS 3141: Team Software Project Introduction

Acknowledgement. Software Engineering. CS 3141: Team Software Project Introduction CS 3141: Team Software Project Introduction Ali Ebnenasir Department of Computer Science Michigan Technological University Acknowledgement Betty H.C. Cheng Software Engineering Systematic approach for

More information

Project Integration Management

Project Integration Management Integration Initiating ning Executing Monitoring & Controlling Closing 4.1 Develop Charter Statement Of Work Business Case 4.2 Develop 4.3 Direct and Manage Work 4.4 Monitor and Control Work 4.5 Perform

More information

Fundamentals of Measurements

Fundamentals of Measurements Objective Software Project Measurements Slide 1 Fundamentals of Measurements Educational Objective: To review the fundamentals of software measurement, to illustrate that measurement plays a central role

More information

Software Engineering/Courses Description Introduction to Software Engineering Credit Hours: 3 Prerequisite: 0306211(Computer Programming 2).

Software Engineering/Courses Description Introduction to Software Engineering Credit Hours: 3 Prerequisite: 0306211(Computer Programming 2). 0305203 0305280 0305301 0305302 Software Engineering/Courses Description Introduction to Software Engineering Prerequisite: 0306211(Computer Programming 2). This course introduces students to the problems

More information

SLCM 2003.1 Artifacts in a Nutshell ( as of 01/21/2005)

SLCM 2003.1 Artifacts in a Nutshell ( as of 01/21/2005) 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 information

Mastering Microsoft Project 2010 50413B; 3 days, Instructor-led

Mastering Microsoft Project 2010 50413B; 3 days, Instructor-led Mastering Microsoft Project 2010 50413B; 3 days, Instructor-led Course Description This three-day instructor-led course provides students with the knowledge and skills plan and manage projects using Microsoft

More information

CONTENTS. Preface. Acknowledgements. 1. Introduction and Overview 1 Introduction 1 Whatis the CMMI"? 2 What the CMMI* is Not 3 What are Standards?

CONTENTS. Preface. Acknowledgements. 1. Introduction and Overview 1 Introduction 1 Whatis the CMMI? 2 What the CMMI* is Not 3 What are Standards? Preface Acknowledgements xi xiii 1. Introduction and Overview 1 Introduction 1 Whatis the CMMI"? 2 What the CMMI* is Not 3 What are Standards? 3 2. Summaryof CMMI-SW 5 The CMM*-SW 5 CMMI--SW Continuous

More information

Appendix H Software Development Plan Template

Appendix H Software Development Plan Template Appendix H Software Development 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

More information

Lecture Objectives. Software Life Cycle. Software Engineering Layers. Software Process. Common Process Framework. Umbrella Activities

Lecture Objectives. Software Life Cycle. Software Engineering Layers. Software Process. Common Process Framework. Umbrella Activities Software Life Cycle Lecture Objectives What happens in the life of software To look at the life cycle of a software To understand the software process and its related elements To relate to the different

More information

In this Lecture you will Learn: Development Process. Unified Software Development Process. Best Practice

In 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 information

CDC UNIFIED PROCESS JOB AID

CDC UNIFIED PROCESS JOB AID CDC UNIFIED PROCESS JOB AID Independent Verification & Validation Activities Document Purpose This Job Aid is a brief document listing the items to be noted, checked, remembered, and delivered when completing

More information

Quick Reference Guide Interactive PDF Project Management Processes for a Project

Quick Reference Guide Interactive PDF Project Management Processes for a Project Project Processes for a Project Click the Knowledge Area title (below and left in blue underline) to view the details of each Process Group. Project Process Groups and Knowledge Areas Mapping Project Process

More information

11 Tips to make the requirements definition process more effective and results more usable

11 Tips to make the requirements definition process more effective and results more usable 1 11 Tips to make the s definition process more effective and results more usable This article discusses what I believe are the key techniques for making s definition process repeatable from project to

More information

Integration Mgmt / Initiating Process Group 4.1 Develop Project Charter

Integration Mgmt / Initiating Process Group 4.1 Develop Project Charter 1 Mgmt / Initiating Process Group 4.1 Develop Project Charter Project statement of work Business case Agreements Facilitation techniques Project charter 26/02/2013 18:23:36 1 2 Mgmt / Planning Process

More information

NE-50413B Mastering Microsoft Project 2010

NE-50413B Mastering Microsoft Project 2010 NE-50413B Mastering Microsoft Project 2010 Summary Duration Vendor 3 Days Microsoft Audience This course is intended for both novice and experienced Project Managers and project support personnel who need

More information

Minnesota Health Insurance Exchange (MNHIX)

Minnesota 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 information

QA Roles and Responsibilities

QA Roles and Responsibilities QA Roles and Responsibilities There are various roles on projects, some people may play more than one role. You should always check with your organizations testing methodology on what your role(s) are.

More information

Project Management Certificate (IT Professionals)

Project Management Certificate (IT Professionals) Project Management Certificate (IT Professionals) Whether your field is architecture or information technology, successful planning involves a carefully crafted set of steps to planned and measurable goals.

More information

4.1 Domain Analysis. Object-Oriented Software Engineering Practical Software Development using UML and Java

4.1 Domain Analysis. Object-Oriented Software Engineering Practical Software Development using UML and Java 4.1 Domain Analysis Object-Oriented Software Engineering Practical Software Development using UML and Java Chapter 4: Developing The process by which a software engineer learns about the domain to better

More information

Lecture Slides for Managing and Leading Software Projects. Chapter 8: Measuring and Controlling Work Processes

Lecture Slides for Managing and Leading Software Projects. Chapter 8: Measuring and Controlling Work Processes Lecture Slides for Managing and Leading Software Projects Chapter 8: Measuring and Controlling Work Processes developed by Richard E. (Dick) Fairley, Ph.D. to accompany the tet Managing and Leading Software

More information

TEST PLAN OUTLINE (IEEE 829 FORMAT)

TEST PLAN OUTLINE (IEEE 829 FORMAT) TEST PLAN OUTLINE (IEEE 829 FORMAT) 1) Test Plan Identifier 2) References 3) Introduction 4) Test Items 5) Software Risk Issues 6) Features to be Tested 7) Features not to be Tested 8) Approach 9) Item

More information