Application in a Systems Design Environment. EE 498/499 Capstone Design Classes Klipsch School of Electrical & Computer Engineering

Transcription

1 Application in a Systems Design Environment EE 498/499 Capstone Design Classes Klipsch School of Electrical & Computer Engineering

2 Purpose The formal design process in the other notes can be applied to systems design in a systems engineering environment. One of the approaches in the systems engineering design is to apply top-down structured techniques to go from the whole system to manageable system elements that fit together as a whole. Spring 2007 Nanosat Realization 2

3 Purpose In this set of notes, we will look at the same process applied on several levels Spring 2007 Nanosat Realization 3

4 Design Process Whether we are working at the system level or the individual component level, we will use the same process. Step #1: Formulation Establish the design problem to be solved. The statement of the problem should be appropriate for the level. System-level statements are at a higher level and with fewer specifics than component-level problem statements. Spring 2007 Nanosat Realization 4

5 Design Process Step #1 Formulation (cont.) Generate the requirements for the design level. At the system level, these are the system-level requirements and the process flows down to the component level with component-level requirements. Determine the performance requirements for the level as well. This will include acceptance criteria. At this stage, all formulations are at the functional level and not the specific design level. Spring 2007 Nanosat Realization 5

6 Design Process Step #2 Conceptual Design For each level, develop the physical principles that are considered to be the best ones to solve the problem and realize the requirements for that level. Include the Conceptual Design diagram. Use the Functional Decomposition and I/O Analysis to detail what functions are to be included at each level. Verify all requirements are tracked to a design element. Spring 2007 Nanosat Realization 6

7 Design Process Step #2 Conceptual Design (cont.) Use the activity analysis to generate an Operations Concept Note: there should be backup design support to show the concepts considered and why the non-optimal concepts were not accepted. Keep performance analysis that supports design decisions. This should include the appropriate evaluation matrices. Spring 2007 Nanosat Realization 7

8 Design Process Step #3 Configuration Design For each level, develop the architecture and configuration that are considered to be the best ones realize the requirements for that level. For each level, develop the relevant design parameters for each architecture element. Verify all requirements are tracked to a design element. Provide any necessary analysis to show design will work. Spring 2007 Nanosat Realization 8

9 Design Process Step #4 Detailed Design This is the final stage producing the design as a real item in hardware & software. All configuration diagrams and parameters are updated to the as built configuration. Full design is tested from end-to-end to ensure that all requirements are met and performance specifications are met. Spring 2007 Nanosat Realization 9

10 Data Products Step #1 Formulation Functional Requirements Document Requirements Verification Matrix Spring 2007 Nanosat Realization 10

11 Data Products Step #2 Conceptual Design Conceptual Design diagram Functional Analysis and I/O Analysis for each level Preliminary draft of the Operations Concept Document Preliminary draft of the Interface Control Document Preliminary draft of the Integration and Test Plan Preliminary draft of budgets: power, mass, size, communications links, etc. Update Requirements Document and Requirements Verification Matrix to capture changes and to indicate which design elements will track to specific requirements. Spring 2007 Nanosat Realization 11

12 Data Products Step #3 Configuration Design Architecture diagram for the level Configuration diagram for the level Preliminary draft of Parts List and Materials List. Updated draft of the Operations Concept Document Updated draft of the Interface Control Document Updated draft of the Integration and Test Plan Updated draft of budgets: power, mass, size, communications links, etc. Updated Requirements Matrix. Spring 2007 Nanosat Realization 12

13 Data Products Step #4 Detailed Design Finalized architecture diagram for the level Finalized configuration diagram for the level Finalized Parts List and Materials List. Finalized Operations Concept Document Finalized Interface Control Document Finalized Integration and Test Plan Finalized budgets: power, mass, size, communications links, etc. Finalized Requirements Matrix with all requirements showing having been met. Spring 2007 Nanosat Realization 13

14 Reviews The System Concept Review presentation can be developed from Steps #1 and #2 The Preliminary Design Review can be developed by updating Steps #1 and #2 for any changes or refinements that have developed as the design has evolved. Then, the design details from Step #3 are added. Spring 2007 Nanosat Realization 14

15 Reviews The Critical Design Review can be developed by updating Steps #1, #2 and #3 for any changes or refinements that have developed as the design has evolved. Then, the design details from Step #4 are added. The Final Review is based on the production of the finalized working design. The acceptance criteria are shown as having being met. Spring 2007 Nanosat Realization 15

16 Reviews What is needed for the review? The appropriate review template should be completed for the presentations. The indicated documents should be ready by the review date. The review will consist of the presentation to summarize the design to that point. The documents are to be ready for inspection at those times. Spring 2007 Nanosat Realization 16