1. Systems Engineering Management
CSUN - Prof. David Shternberg
Systems Engineering Management
MSE607B- Systems Engineering
MSE607B Chapter 5 Design Review and Evaluation
Engineering Design Methods and Tools
The purpose of this chapter is to briefly highlight some of the recent concepts in design and to discuss system engineering objectives as they relate to current design methods.

2. CSUN - Prof. David Shternberg
Learning Objectives
CSUN - Prof. David Shternberg
MSE607B- Systems Engineering
Explain the basic philosophy of design evolution
Describe the evaluation methods
Explain the informal and formal design reviews
Explain the feedback and corrective-action loop associated with these activities
Learning Objectives
The objectives of this module are to:
Explain the basic philosophy of design evolution,
Describe the evaluation methods,
Explain the informal and formal design reviews, and
Explain the feedback and corrective-action loop associated with these activities

3. Design Review and Evaluation
CSUN - Prof. David Shternberg
MSE607B- Systems Engineering
Design Review and Evaluation
Design Review and Evaluation
As shown in this figure, the design review and evaluation process includes two basic categories of activity:
1. An informal activity in which the results of design are reviewed and discussed on a day-by-day basis and
2. A structured series of formal design reviews conducted at specific times in the overall system development process.

4. Design Review and Evaluation Requirements
CSUN - Prof. David Shternberg
MSE607B- Systems Engineering
Design Review and Evaluation Requirements
Formal mechanism to ensure design will meet consumer need
Design evolves through iterations from initial definition to firm system configuration
Requirements verification process required from the beginning
Early detection of potential problems allows to incorporate necessary changes easily
An ongoing design review and evaluation effort is required
Overall review process through combination of several approaches:
Informal day-to-day review and evaluation
Formal design reviews at designated stages
Serve as a vehicle for communications
Serve as the formal approval of design data
Design Review and Evaluation Requirements
One of the objectives in establishing a formal mechanism for design review and evaluation is to ensure, on a progressive and continuing basis, that the results of design reflect a configuration that will ultimately meet the stated consumer need.
Design evolves from the initial definition of requirements for a given system, through a series of iterations following a top-down approach, to a firm system configuration ready for production and/or construction.
As one progresses through this series of steps, it is important to initiate the requirements verification process from the beginning, because the earlier that potential problems are detected, the easier it will be to incorporate changes if needed. Thus, an ongoing design review and evaluation effort is required.
The overall review process is accomplished through a combination of several approaches:
Informal day-to-day review and evaluation as design decisions are made and data developed
Formal design reviews at designated stages in the evolution of design
The review process serve as a vehicle for communications, as well as the formal approval of design data.

5. Design Review and Evaluation Procedure
CSUN - Prof. David Shternberg
MSE607B- Systems Engineering
Design Review and Evaluation Procedure
Design Review and Evaluation Procedure
This figure shows the relationship between the informal and formal design reviews. The output from the day-to-day informal activity leads into the formal design reviews.

6. Informal Day-to-day Review and Evaluation
CSUN - Prof. David Shternberg
MSE607B- Systems Engineering
Informal Day-to-day Review and Evaluation
Performed as design decisions are made and data developed
Informal activity
Results of design reviewed and discussed on a day-by-day basis
Output leads into the formal design reviews
Ensure that the results of design:
Communicated in a clear, effective, and timely manner to all members of the design team
Compatible with initially defined requirements for the system
Review procedure has to be accomplished efficiently and in timely manner
Informal Day-to-day Review and Evaluation
Informal day-to-day review and evaluation is performed as design decisions are made and data are developed.
It is an informal activity in which the results of design are reviewed and discussed on a day-by-day basis.
The output from the day-to-day informal activity leads into the formal design reviews.
As this definition process evolves, design reviews intend to ensure that the results of design must be properly communicated in a clear, effective, and timely manner to all members of the design team, and compatible with the initially defined requirements for the system.

7. CSUN - Prof. David Shternberg
MSE607B- Systems Engineering
Formal Design Reviews
Conducted at designated stages in the evolution of design
Serve as a vehicle for communications and the formal approval of design data.
Purpose
Review system requirements specification document
Ensure documented design reflect current knowledge of customer and market requirements
Identify areas where design may not be consistent with product development constraints
Put the design document under version control to serve as a stable baseline for continued new product development
Formal Design Reviews
Formal design reviews are conducted at designated stages in the evolution of design, and serve as a vehicle for communications and the formal approval of design data.
The purpose of the formal design review is to review the system requirements specification document, to ensure the documented design reflect the current knowledge of the customer and market requirements, to identify areas where the design may not be consistent with product development constraints, and to put the design document under version control to serve as a stable baseline for continued new product development.

8. Formal Design Reviews (cont.)
CSUN - Prof. David Shternberg
Formal Design Reviews (cont.)
MSE607B- Systems Engineering
Preliminary Design Review (PDR)
Ensure planned technical approach will meet the requirements
Critical Design Review (CDR)
Ensure design implementation has met the requirements
Test Readiness Review (TRR)
Review preparations and readiness for testing, including test procedures
Production Readiness Review (PRR)
Ensure design completely and accurately documented
Ensure design ready for formal release to manufacturing
Preliminary Design Review (PDR) is performed to review the conceptual design to ensure that the planned technical approach will meet the requirements.
Critical Design Review (CDR) is performed to review the detailed design to ensure that the design implementation has met the requirements.
Test Readiness Review (TRR) is performed to review preparations and readiness for testing of software configuration items, including adequate version identification of software and test procedures.
Production Readiness Review (PRR) is performed to ensure that the design is completely and accurately documented and ready for formal release to manufacturing.

9. Conceptual (Preliminary) Design Review
CSUN - Prof. David Shternberg
MSE607B- Systems Engineering
Conceptual (Preliminary) Design Review
PDR
Usually scheduled toward end of program conceptual design
Deals primarily with top system-level requirements
Results constitute basis for preliminary system design and development activity
Participation include representation from both the consumer and producer organizations
Purpose:
Review and evaluate the functional baseline of the system
Conceptual (Preliminary) Design Review
The conceptual design review, also known as preliminary design review or PDR, is usually scheduled toward the end of the conceptual design and prior to entering the preliminary system design phase of the program.
The conceptual design review deals primarily with top system-level requirements, and the results constitute the basis for follow-on preliminary system design and development activity.
Participation in this formal review include representation from both the consumer and producer organizations.
The purpose of conceptual design review is to review and evaluate the functional baseline of the system.

10. Topics Covered in Conceptual Design Review
CSUN - Prof. David Shternberg
MSE607B- Systems Engineering
Topics Covered in Conceptual Design Review
Objective
Review and evaluate functional baseline of the system
Feasibility analysis
Results of technology assessments and trade-off studies justifying the system design approach being proposed
System operational requirements
System maintenance concept
Topics Covered in Conceptual Design Review
The objective of the conceptual design review is to review and evaluate the functional baseline of the system.
The material to be covered through this review include:
Feasibility analysis – the results of technology assessments and early trade-off studies justifying the system design approach being proposed
System operational requirements
System maintenance concept

11. Topics Covered in Conceptual Design Review (cont.)
CSUN - Prof. David Shternberg
MSE607B- Systems Engineering
Topics Covered in Conceptual Design Review (cont.)
Functional analysis
Significant design criteria for the system
Effectiveness of merit and technical performance measures
System specification Type A
System engineering management plan
Test and evaluation master plan
System design documentation
Functional analysis
Significant design criteria for the system
Applicable effectiveness figures of merit and technical performance measures
System specification Type A
System engineering management plan
Test and evaluation master plan
System design documentation – layout drawings, sketches, parts lists, selected supplier components

12. Systems Design Reviews
CSUN - Prof. David Shternberg
MSE607B- Systems Engineering
Systems Design Reviews
Usually scheduled during preliminary design phase
Functional requirements & allocations are defined
Preliminary design layouts & specifications are prepared
System-level trade-off studies are conducted
Oriented to the overall system configuration
Ensure that requirements described in the system specifications are maintained as design evolves
Should include representation from
Consumer
Producer
Major suppliers
System Design Reviews
System design reviews are usually scheduled during the preliminary design phase when functional requirements and allocations are defined, preliminary design layouts and detailed specifications are prepared, system-level trade-off studies are conducted, and so on.
These reviews are oriented to the overall system configuration, rather than individual equipment items, software and other components of the system.
As design evolves, it is important to ensure that the requirements described in the system specifications are maintained.
Participation in system design reviews should include representation from both the consumer and producer organizations, as well as from major suppliers involved in the early phases of the system life cycle.

13. Topics Covered in Systems Design Reviews
CSUN - Prof. David Shternberg
MSE607B- Systems Engineering
Topics Covered in Systems Design Reviews
Functional analysis and the allocations of requirements
Development, process, product, and material specifications
Type B, C, D, and E
Design data defining the overall system
Analysis, reports, trade-off studies, and related design documentation.
Assessment of proposed system design configuration in terms of technical performance measures (TPMs)
Individual program/design plans
Topics Covered in Systems Design Reviews
System design reviews cover a variety of topics, such as:
Functional analysis and the allocations of requirements
Development, process, product, and material specifications as applicable (Type “B”, “C”, “D”, and “E”)
Design data defining the overall system
Analysis, reports, predictions, trade-off studies, and related design documentation.
Assessment of the proposed system design configuration in terms of technical performance measures (TPMs)
Individual program/design plans

14. Equipment/Software Design Reviews
CSUN - Prof. David Shternberg
MSE607B- Systems Engineering
Equipment/Software Design Reviews
Formal design reviews covering equipment, software, and other components of the system:
Scheduled during the detail design and development phase of the life cycle
Usually oriented to a particular item
Should include representation from
Consumer
Producer
Applicable supplier organizations
Equipment/Software Design Reviews
Formal design reviews covering equipment, software, and other components of the system are scheduled during the detail design and development phase of the life cycle.
These reviews are usually oriented to a particular item of the system.
Participation in these formal reviews should include representation from the consumer, producer, and applicable supplier organizations.

15. Topics Covered in Equipment/Software Design Reviews
CSUN - Prof. David Shternberg
MSE607B- Systems Engineering
Topics Covered in Equipment/Software Design Reviews
Process, product, and material specifications
Types C, D, and E
Design data defining major subsystems, equipment, software, and other elements of the system as applicable
Analyses, reports, predictions, trade-off studies, and other related design documentation
Assessment of the proposed system design configuration in terms of the applicable TPMs
Engineering breadboards, laboratory models, service test models, mock-ups, and prototype models
Supplier data covering specific components of the system
Topics Covered in Equipment/Software Design Reviews
Equipment/software design reviews include coverage of the following:
Process, product, and material specifications (Types “C”, “D”, and “E”)
Design data defining major subsystems, equipment, software, and other elements of the system as applicable
Analyses, reports, predictions, trade-off studies, and other related design documentation as required in support of the proposed design configuration and/or for assessment purposes.
Assessment of the proposed system design configuration in terms of the applicable technical performance measures (TPMs)
Engineering breadboards, laboratory models, service test models, mock-ups, and prototype models
Supplier data covering specific components of the system

16. Critical Design Review (CDR)
CSUN - Prof. David Shternberg
MSE607B- Systems Engineering
Critical Design Review (CDR)
Generally scheduled after the completion of detail design, but prior to the release for production or construction
Design is essentially “frozen” at this point
Proposed configuration evaluated for adequacy and producibility
Results describe final system/product configuration baseline prior to entering into production or construction.
Constitute the last in series of progressive evaluation efforts
Reflecting design and development from a historical perspective
Showing growth and maturity in design as the engineering project evolved
Critical Design Review (CDR)
The critical design review, also known as CDR, is generally scheduled after the completion of detail design, but prior to the release of firm design data for production of construction.
The design is essentially “frozen” at this point, and the proposed configuration is evaluated in terms of adequacy and producibility.

17. The Design Change and System Modification Process
CSUN - Prof. David Shternberg
MSE607B- Systems Engineering
The Design Change and System Modification Process
Important that any changes to the baseline be tightly controlled
All changes carefully recorded and documented
Configuration identification
Controlling the changes
Maintaining the integrity and continuity of design
Configuration management
The Design Change and System Modification Process
Once a configuration baseline for the system design has been established, it is equally important that any variations, or changes, with respect to the baseline be tightly controlled.
In evolving from one design configuration to the next, it is important that all changes be carefully recorded and documented in terms of their possible impact on the initially specified system requirements.
The process of configuration identification, the control of changes, and maintaining the integrity and continuity of design are accomplished through Configuration Management (CM).

18. The Design Change and System Modification Process (cont.)
CSUN - Prof. David Shternberg
MSE607B- Systems Engineering
The Design Change and System Modification Process (cont.)
Configuration Management (CM)
Identifies the functional and physical characteristics of an item
Controls changes to characteristics
Records and reports change processing and implementation status
Proposed design changes initiated during any phase in the life cycle
Prepared in the form of an Engineering Change Proposal (ECP)
Configuration Management, also called CM, is the process that identifies the functional and physical characteristics of an item during its life cycle, controls changes to those characteristics, and records and reports change processing and implementation status.
Proposed design changes, or proposed changes to a given baseline, may be initiated from any one of a number of sources during any phase in the overall system life cycle. Such changes, prepared in the form of an Engineering Change Proposal (ECP)

19. Engineering Change Proposal (ECP)
CSUN - Prof. David Shternberg
MSE607B- Systems Engineering
Engineering Change Proposal (ECP)
Each ECP should include:
Statement of the problem and description of proposed change
Description of alternatives considered in responding to the need
Analysis how change will impact system performance
Analysis to ensure proposed solution will not cause a new problem
Preliminary plan for incorporating the change
Engineering Change Proposal (EPC)
Each proposed change to the system design is presented in the form of an Engineering Change Proposal, or ECP, submitted for review, evaluation, and approval.
In general, each ECP should include the following:
A statement of the problem and a description of the proposed change
A brief description of alternatives that have been considered in responding to the need
An analysis showing how the change will impact system performance, effectiveness factors, packaging concepts, safety, and so on.
An analysis to ensure that the proposed solution will not cause the introduction of a new problem
A preliminary plan for incorporating the change – proposed date of incorporation, serial numbers affected, retrofit requirements, and verification test approach, as applicable.

20. Engineering Change Proposal (ECP) (cont.)
CSUN - Prof. David Shternberg
MSE607B- Systems Engineering
Engineering Change Proposal (ECP) (cont.)
Description of the resources required to implement the change
Estimate of the costs associated with implementing the change
Impact on the system if the proposed change is NOT implemented
Classified
Class 1 changes
Design changes that will affect fit, form or function
Class 2 changes
Design changes that are relatively minor in nature
Will not affect system specification requirements
May be classified as “emergency”, “urgent,” or “routine”
A description of the resources required to implement the change
An estimate of the costs associated with implementing the change
A statement covering the impact on the system if the proposed change is NOT implemented. That is, the possible risks with “do-nothing” decision.
ECPs may be classified as Class 1 changes – when design changes will affect fit, form or function, or Class 2 changes – when design changes are relatively minor in nature and that will not affect system specification requirements
Changes may be classified as “emergency”, “urgent,” or “routine,” depending on priority and on the criticality of the change.

21. CSUN - Prof. David Shternberg
MSE607B- Systems Engineering
Summary
Addressed the basic review, evaluation, and feedback process of system design
The process is critical in regard to the objectives of system engineering
Must be tailored to the specific system development effort and must be properly controlled
An ongoing measurement and evaluation activity is essential and must be initiated from the beginning
Without proper controls, the incorporation of design changes ay be costly in terms of possible modifications and system support
Summary
This module primarily addressed the basic review, evaluation, and feedback process of system design.
The process, which is critical in regard to the objectives of system engineering, must be tailored to the specific system development effort and must be properly controlled.
An ongoing measurement and evaluation activity is essential and must be initiated from the beginning.
Without the proper controls the incorporation of design changes on a continuing basis may be costly in terms of possible modifications and system support.

22. CSUN - Prof. David Shternberg
MSE607B- Systems Engineering
Interactive Workshop
Preliminary Design Review (PDR):
Ensures design implementation has met the requirements
Ensures that the planned technical approach will meet the requirements
Review preparations and readiness for testing, including test procedures
Ensures design is ready for formal release to manufacturing

23. CSUN - Prof. David Shternberg
MSE607B- Systems Engineering
Interactive Workshop
System design reviews ensure that:
Requirements described in the system specifications are maintained as design evolves
Proposed design changes initiated during any phase in the life cycle are documented
Results constitute basis for preliminary system design and development activity
None of the above

24. CSUN - Prof. David Shternberg
MSE607B- Systems Engineering
Interactive Workshop
Configuration Management (CM) is the process that:
Identifies the functional and physical characteristics of an item
Controls changes to functional and physical design characteristics
Records and reports change processing and implementation status
All of the above

25. CSUN - Prof. David Shternberg
MSE607B- Systems Engineering
Interactive Workshop
The Critical Design Review, also known as CDR, is generally scheduled:
After the completion of detail design, but prior to the release of firm design data for production
After the completion of detail design and during the release of firm design data for production
During the detail design and development phase of the life cycle
During the requirements definition phase of the life cycle

26. CSUN - Prof. David Shternberg
MSE607B- Systems Engineering
Interactive Workshop
The purpose of conceptual design review is to:
Experiment with different packaging during formal design
Convey final design approach during design review
Review and evaluate the reliability baseline of the system
Review and evaluate the functional baseline of the system

27. CSUN - Prof. David Shternberg
MSE607B- Systems Engineering
Homework Assignment
Chapter 5 – Textbook page 246
Answer questions 1, 4, 7, 11 and 13
Read Chapter 6 - Engineering Program Planning
Pages

28. Questions? Comments?