DOD’S PHASED SYSTEM DEVELOPMENT PROCESS

Slides:



Advertisements
Similar presentations
Successful Project Management Justice, E-Government, & the Internet June 28, 2000 – Dallas, Texas Lawrence P. Webster.
Advertisements

1 PROJECT MANAGEMENT ROLE OF KEY PERSONNEL Bernd Madauss International Space University Strasbourg February, 2011
S Y S T E M S E N G I N E E R I N G.
Software Process Models
Chapter 2 The Analyst As Project Manager In Managing Information Systems 2.3.
Copyright © 2012 Pearson Education, Inc. Publishing as Prentice Hall 3.1.
Project Scope Management
Modern Systems Analysis and Design Third Edition
Copyright 2002 Prentice-Hall, Inc. Chapter 3 Managing the Information Systems Project 3.1 Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer.
Pertemuan Matakuliah: A0214/Audit Sistem Informasi Tahun: 2007.
Chapter 5: Project Scope Management
Systems Engineering Management
Planning. SDLC Planning Analysis Design Implementation.
© 2008 Prentice Hall11-1 Introduction to Project Management Chapter 11 Managing Project Execution Information Systems Project Management: A Process and.
Project Execution.
© 2005 Prentice Hall14-1 Stumpf and Teague Object-Oriented Systems Analysis and Design with UML.
Initiating and Planning Systems Development projects
Copyright 2010, The World Bank Group. All Rights Reserved. Statistical Work Plan Development Section B 1.
CS 360 Lecture 3.  The software process is a structured set of activities required to develop a software system.  Fundamental Assumption:  Good software.
Certification and Accreditation CS Phase-1: Definition Atif Sultanuddin Raja Chawat Raja Chawat.
© 2006 Cisco Systems, Inc. All rights reserved.Cisco Public 1 Version 4.0 Gathering Network Requirements Designing and Supporting Computer Networks – Chapter.
BIS 360 – Lecture Two Ch. 3: Managing the IS Project.
Lecture 11 Managing Project Execution. Project Execution The phase of a project in which work towards direct achievement of the project’s objectives and.
ISM 5316 Week 3 Learning Objectives You should be able to: u Define and list issues and steps in Project Integration u List and describe the components.
CHECKPOINTS OF THE PROCESS Three sequences of project checkpoints are used to synchronize stakeholder expectations throughout the lifecycle: 1)Major milestones,
Ch 4 - Learning Objectives Scope Management You should be able to: n Discuss the relationship between scope and project failure n Describe how strategic.
Slide 1 Project Management Chapter 4. Slide 2 Objectives ■ Become familiar with estimation. ■ Be able to create a project workplan. ■ Become familiar.
University of Southern California Center for Systems and Software Engineering Barry Boehm, USC CS 510 Software Planning Guidelines.
Notes of Rational Related cyt. 2 Outline 3 Capturing business requirements using use cases Practical principles  Find the right boundaries for your.
Request for Proposal (RFP)
Copyright 2002 Prentice-Hall, Inc. Chapter 3 Managing the Information Systems Project 3.1 Modern Systems Analysis and Design.
Project Scope Management 1. 2 Learning Objectives Understand the elements that make good project scope management important. Explain the scope planning.
Software Project Management (SEWPZG622) BITS-WIPRO Collaborative Programme: MS in Software Engineering SECOND SEMESTER /1/ "The content of this.
Software Development Process CS 360 Lecture 3. Software Process The software process is a structured set of activities required to develop a software.
Team-Based Development ISYS321 Managing the Information Systems Project.
1 Project Management Software management is distinct and often more difficult from other engineering managements mainly because: – Software product is.
1 Lecture 2.4a: SEF SE Planning and the SEP (SEF Ch 16) Dr. John MacCarthy UMBC CMSC 615 Fall, 2006.
IFS310: Module 9 Systems Design - Procurement Phase - Software Design.
1 Lecture 2.3: SE Process (SEF Ch 3) Dr. John MacCarthy UMBC CMSC 615 Fall, 2006.
6/6/ SOFTWARE LIFE CYCLE OVERVIEW Professor Ron Kenett Tel Aviv University School of Engineering.
Request for Proposal (RFP) In response to the RFP – the first step is to prepare a proposal 1. Review Customer Requirements and come up with candidate.
Software Development Process includes: all major process activities all major process activities resources used, subject to set of constraints (such as.
Project Management PTM721S
Introduction to Project Management
IF 3507 Manajemen Proyek Perangkat Lunak
Project Management Systems
Systems Analysis and Design in a Changing World, 4th Edition
WORK BREAKDOWN STRUCTURE
Software Planning Guidelines
Business System Development
Project Management and Information Security
TechStambha PMP Certification Training
Planning Phase: Project Control and Deliverables
Project Management.
Introduction to Tech Communication & Project Management Arthur C.M. Chen , Rm
Defining the Activities
Request for Proposal (RFP)
Quality Management Systems – Requirements
Engineering Processes
Scope management Chapter 5 Copyright ©2016 Pearson Education, Inc.
CIS12-3 IT Project Management
EMIS 7307 Chapter 6.
Chapter 3 Managing the Information Systems Project
MANAGING THE DEVELOPMENT AND PURCHASE OF INFORMATION SYSTEMS
Modern Systems Analysis and Design Third Edition
Chapter 3 Managing the Information Systems Project
Modern Systems Analysis and Design Third Edition
The Database Development Process
Presentation transcript:

DOD’S PHASED SYSTEM DEVELOPMENT PROCESS OBJECTIVE Orderly System definition growth and avoidance of premature entry into subsequent program phase. Funds commitment based on reviews at specific points in program (determination of appropriate and effective base for next program phase.).

Design Project Process OBJECTIVE Orderly design definition growth and insurance that : Design cost effectively satisfies all requirements. Derived from an analysis of well defined needs. SUMMARY Problem / Needs definition Alternate solution strategies identified Trade off analysis to select best solution approach based on explicitly stated criteria. Baseline iteration system design evolution permits : System requirements / Design changes due to reviews and test results Configuration management Quality assurance System validations and qualifications (Thru pilot model)

DOD’s System Development Process Phases

Design Project Process Phases

Design Project Process TECHNICAL PERSPECTIVE Research Base Conceptual Base Needs (mission ) analysis Requirement definition Design Solution strategy definition Alternate approaches Comparative analysis (trade off studies)) Validation Phase Needs Review Design and approach feasibility Rapid Prototyping Design Issues Prototype Design Test plan and testing Result analysis Iterations where necessary Engrg. Phase

Design Project Process TECHNICAL PERSPECTIVE (continued) Engineering Development Phase Implementation Feasibility Pilot model Construction / production issues Pilot model design Test plan and testing (qualification) Result analysis Iterations where necessary Production Phase Final system design Acceptance test plan (verification) Implementation and testing Operation Phase Presentation and demonstration (transfer to owner)

Design Project Process DOCUMENTATION Project Definition Project plan ( preliminary submitted with proposal) The HOW, WHO, WHEN and WITH-WHAT of the project Test plans and the procedures (details of required testing operations) System Definition System requirements Design specifications Technical manual User’s manual

Design Project Process Foundation Literature and catalog search Review design lab archive Conceptual definition Need Analysis System / operation description Scenario - Performance requirements and maintenance considerations. Analysis Alternate System Approaches trade-off Risk Assessment Project plan must cover all of these .

Design Project Process Definition System requirements Design Specs Test plans Design Implementation Test results impact analysis Final documentation Technical manual User’s manual Historic record (legacy report) Loop for prototype, pilot, and final models Project plan must cover all of these

Steps to project planning As a team, brainstorm possible needs to be satisfied. Select one of those identified In some detail, describe the needs to be satisfied, and the possible system approaches. Identify the system approach selection criteria (risk included), and select one via a trade-off analysis. Identify project milestones necessary to realize the given major milestone.

Steps to project planning Assign functional responsibilities to team members who then define the associated tasks: to whom assigned, when started, when completed, required inputs (and when), provided outputs (and when). Connect the tasks into a project task network, and define the required resources (and required dates) Define the project’s management procedures (configuration management tracking and control, resource acquisition, quality assurance, etc.)

Project Planning Work Decomposition and Organization Scheduling Work Breakdown Structure (WBS) Scheduling Financial Management Cost estimating, budgeting, reporting and control. Technical Performance System performance decomposition to component level Tracking / reporting to identify development problems for appropriate action. Provides visibility as to meeting the system requirements during development process

Project Planning Work Breakdown Structure (WBS) Scheduling Top down work hierarchy definition To low levels of responsibility assignment, cost estimates/ accounting, scheduling, and performance assessment. Scheduling Gantt charts - horizontal bar charts Milestone charts Performance Evaluation and Reporting Technique (PERT) originally developed and used on the Polaris program by Lockheed.