60 likes | 219 Vues
Lecture 2.4a: SEF SE Planning and the SEP (SEF Ch 16). Dr. John MacCarthy UMBC CMSC 615 Fall, 2006. 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.
E N D
Lecture 2.4a: SEF SE Planning and the SEP (SEF Ch 16) Dr. John MacCarthy UMBC CMSC 615 Fall, 2006
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
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) 16.1 Why Engineering Plans DoD recommends the development of a SEP The next lecture specifically addresses the DoD-recommended SEP content and format.
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 16.2: Elements of Technical Plans (SEPs)
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 16.3 Integration of Plans
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 16.4: Summary Points The next lecture specifically addresses the DoD-recommended SEP content and format.