1 Lecture 2.4a: SEF SE Planning and the SEP (SEF Ch 16) Dr. John MacCarthy UMBC CMSC 615 Fall, 2006.

Slides:



Advertisements
Similar presentations
SEMP vs. PMP Conflict and Partnership
Advertisements

Roadmap for Sourcing Decision Review Board (DRB)
Software Quality Assurance Plan
1 Lecture 1.4: Life Cycle Models Dr. John MacCarthy UMBC CMSC 615 Fall, 2006.
Chapter 7: Key Process Areas for Level 2: Repeatable - Arvind Kabir Yateesh.
More CMM Part Two : Details.
Copyright © 2012 Pearson Education, Inc. Publishing as Prentice Hall 3.1.
1 Lecture 3.2: Technical Reviews and Audits (SEF Ch 11) Dr. John MacCarthy UMBC CMSC 615 Fall, 2006.
Systems Engineering in a System of Systems Context
1 Lecture 2.6: Organization Structures Dr. John MacCarthy UMBC CMSC 615 Fall, 2006.
Trade Study Training Need and Goals Need Consistent methodologies and practices performing trade studies Pros/cons, advantages/disadvantages, customer/management.
Project Management and MS Project. The project management triangle: Time Resources Scope.
Defining the Activities. Documents  Goal Statement defines why helps manage expectations  Statement of Work what gets delivered defines scope  Software.
LSU 07/24/2004Defining Project Tasks1 Defining the Project Tasks Project Management Unit, Lecture 4.
© 2008 Prentice Hall11-1 Introduction to Project Management Chapter 11 Managing Project Execution Information Systems Project Management: A Process and.
Project Execution.
1 Lecture 4.3a: Metrics Overview (SEF Ch 14) Dr. John MacCarthy UMBC CMSC 615 Fall, 2006.
Project Management Lecture 5+6 MS Saba Sahar.
® IBM Software Group © 2006 IBM Corporation PRJ480 Mastering the Management of Iterative Development v2 Module 3: Phase Management - Inception.
What is Business Analysis Planning & Monitoring?
Effective Methods for Software and Systems Integration
Lecture 3.5: Work Dependencies, Scheduling, IMP & IMS (SEF A16A)
1 Lecture 5.3: SEF Ch 4 Requirements Analysis Dr. John MacCarthy UMBC CMSC 615 Fall, 2006.
Initiating and Planning Systems Development projects
The Key Process Areas for Level 2: Repeatable Ralph Covington David Wang.
1 Lecture 3.9: RFP, SOW and CDRL (SEF Ch 19) Dr. John MacCarthy UMBC CMSC 615 Fall, 2006.
McGraw-Hill/Irwin © 2006 The McGraw-Hill Companies, Inc. All rights reserved. BUSINESS DRIVEN TECHNOLOGY Business Plug-In B10 Project Management.
Lecture 2.3: The Systems Engineering Plan (SEP)
1 Lecture 3.1: Project Planning: Work Breakdown Structure (WBS) [SEF Ch 9] Dr. John MacCarthy UMBC CMSC 615 Fall, 2006.
PPMT CE-408T Engr. Faisal ur Rehman CED N-W.F.P UET P.
BUSINESS PLUG-IN B15 Project Management.
Soft Tech Development Inc. 1 Software Project Tracking A CMM Level 2 Key Process Area Soft Tech Development Inc.
1 Lecture 5.2a: SEF Ch 8 SE Outputs Dr. John MacCarthy UMBC CMSC 615 Fall, 2006.
1 Lecture 2.5: Project Planning Overview Dr. John MacCarthy UMBC CMSC 615 Fall, 2006.
Lecture 11 Managing Project Execution. Project Execution The phase of a project in which work towards direct achievement of the project’s objectives and.
SacProNet An Overview of Project Management Techniques.
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.
Executive Session Director’s CD-3b Review of the MicroBooNE Project January 18, 2012 Dean Hoffer.
Georgia Institute of Technology CS 4320 Fall 2003.
Project Management Concepts
I n t e g r i t y - S e r v i c e - E x c e l l e n c e Business & Enterprise Systems The Integrated Master Plan (IMP) and the Integrated Master Schedule.
PLUG IT IN 6 Project Management. 1.Project Management for Information Systems Projects 2.The Project Management Process 3.The Project Management Body.
CEN5011, Fall CEN5011 Software Engineering Dr. Yi Deng ECS359, (305)
1 | 2010 Lecture 3: Project processes. Covered in this lecture Project processes Project Planning (PP) Project Assessment & Control (PAC) Risk Management.
Component 8 Installation and Maintenance of Health IT Systems Unit 4 Structured Systems Analysis and Design This material was developed by Duke University,
M ONITOR & C ONTROL Focus is on Integrated Change Control 1.
Verification and Validation — An OSD Perspective — Fred Myers Deputy Director, Test Infrastructure Test Resource Management Center November 4, 2009.
Lecture 2.1b: DoD Acquisition Process (SEF Ch 2)
1 EMS Fundamentals An Introduction to the EMS Process Roadmap AASHTO EMS Workshop.
Topic 5 Initiating a project
Software Project Management (SEWPZG622) BITS-WIPRO Collaborative Programme: MS in Software Engineering SECOND SEMESTER /1/ "The content of this.
Dr. John MacCarthy UMBC CMSC 615 Fall, 2006
Overview of RUP Lunch and Learn. Overview of RUP © 2008 Cardinal Solutions Group 2 Welcome  Introductions  What is your experience with RUP  What is.
1 Project Management C13PM Session 2 Project Initiation & Definition Russell Taylor Business Department Staff Workroom
Software Engineering (CSI 321) Software Process: A Generic View 1.
~ pertemuan 4 ~ Oleh: Ir. Abdul Hayat, MTI 20-Mar-2009 [Abdul Hayat, [4]Project Integration Management, Semester Genap 2008/2009] 1 PROJECT INTEGRATION.
Project Management Processes for a Project Chapter 3 PMBOK® Fourth Edition.
Continual Service Improvement Methods & Techniques.
The Software Engineering Process Discussion Slides.
1 Lecture 2.3: SE Process (SEF Ch 3) Dr. John MacCarthy UMBC CMSC 615 Fall, 2006.
V. 2. © Copyright and all rights reserved 4. Project Integration Management PMP Prep Course Based on the PMBOK ® Guide 3 rd Edition.
Project Management PTM721S
Project Management PTM721S
Project Management Lifecycle Phases
TechStambha PMP Certification Training
Project Management.
Defining the Activities
Mumtaz Ali Rajput +92 – SOFTWARE PROJECTMANAGMENT– WEEK 4 Mumtaz Ali Rajput +92 – 301-
DOD’S PHASED SYSTEM DEVELOPMENT PROCESS
Presentation transcript:

1 Lecture 2.4a: SEF SE Planning and the SEP (SEF Ch 16) Dr. John MacCarthy UMBC CMSC 615 Fall, 2006

2 Agenda 16.1 Why Engineering Plans 16.2 Elements of Technical Plans 16.3 Integration of Plans 16.4 Summary Points Note that A16-A (Event-Driven) Schedules is addressed in Lecture 3

Why Engineering Plans Uses of a SE Plan: Assure all technical activities (and events) are identified and managed Communicate the technical approach to the development team and other stakeholders (e.g., Management, Customer, T&E Team, etc.) Document decisions and technical implementation Establish/Document criteria to judge how well the system development effort is meeting customer and management needs. Key Questions: Who will Do What When Approaches: Develop a Systems Engineering Plan (SEP) Document SE plan as part of a Project Management Plan (PMP) The next lecture specifically addresses the DoD-recommended SEP content and format. DoD recommends the development of a SEP

4 16.2: Elements of Technical Plans (SEPs) Technical Plans (SEP) should include: Introduction Plan Scope Description of the System Focus Technical Strategy Development Phasing & associated Baselining Key Engineering Milestones Parallel developments Product improvement Strategy Considerations and Constraints Critical Technologies Cost As an Independent Variable (CAIV) Business management directed constraints/ activities that will significantly impact the technical strategy Technical Plans (con’d): SE Processes: Specific methods and techniques used to perform the SE process Steps and Loops System Analysis and Control Tools Special design considerations Organization Plan: Organizations & IPTs Roles, Authority & Responsibilities Resource Plan: People Funding Schedule

Integration of Plans Plans that need to be coordinated: Acquisition Strategy Financial Plan Test and Evaluation Master Plan (TEMP) Configuration Management Planning (CMP) Risk Management Planning (RMP) Interoperability Planning Design/Development Planning (SDP) Integrated Logistics Support (ILS) Planning & Analysis Production/Manufacturing Planning Quality Management Planning Others Well-developed Technical Management Plans (SEPs) include: Benefit of plan to the user How “total” system will be developed using the SE Process How the SEP complements and supports the Acquisition Strategy and/or Management Plan How incremental reviews will keep development on track How costs will be reduced and controlled. How technical activities relate to work accomplishment and calendar dates How the System Configuration and risk will be controlled How System Integration will be achieved

6 16.4: Summary Points The next lecture specifically addresses the DoD-recommended SEP content and format. SE Planning should establish the organizational structure that will achieve the engineering objectives Planning must include event-based scheduling and establish feedback and control methods Planning should result in Planning and Control Documents Planning should identify the estimated funding and detail schedule necessary to achieve the strategy SE Planning should establish the proper relationship between acquisition and technical processes