IT 518 Systems Engineering & Integration Chapter 5: Detail Design and Development Dr. Jim Dept. of Computer Science & Information Technology Detail Design and Development Configuration/Allocated Baseline - overall system and major subsystems Realization of specific system components Detail Design and Development (Activities) 1. Detail Design Requirements 2. Integrating System Elements 3. Design Engineering Activities 4. Detail Design Aids 5. Detail Design Documentation 6. System Prototype Development 7. Detail Design Review 1. Detail Design Requirements ⚫ Derived from ⚫ System Requirements Analysis and Allocation (Conceptual & Preliminary Design) ⚫ Procurement of System Components ⚫ Integration, Test, and Evaluation of Prototype Selection of Resources SYSTEM Function A Function B Function C Functional Analysis And Tradeoff-Studies OR Non-Development Items Modified COTS Development Items COTS Technology (Off the Shelf) Modified for Compatibility Unique Design Non-development Items Interface Items COTS Technology Unique Design Alternative Approaches in the Selection of Resources (From ANSI/AIAA R-100 with approval from authors) 2. Integrating System Elements Functional Analysis and Allocation ◼ ◼ identified various elements of the system, e.g. hardware, software, people, facilities, data, etc. ◼ Tradeoff Analysis has selected elements ◼ Detail Design ensures the proper coordination and timely integration of all system elements! How? 2. Integrating System Elements It's Not a Motorcycle, It's a Mobile Barbecue Pit. (Lesson: just because you can, it does not mean you should!) Integrating System Elements ◼ Good Definition of Requirements ◼ Well-written Specifications ◼ Structured and Disciplined Design Approach ◼ Design Reviews! 3. Design Engineering Activities ⚫ Engineering Technical Expertise ⚫ Engineering Technical Support ⚫ Non-Technical Expertise and Support Establishing The Design Team Manufacturing Engineering Mechanical Engineering Software Engineering Electrical Engineering Civil Engineering SYSTEM ENGINEERING INTEGRATION Maintainability Engineering Reliability Engineering Human Factors Engineering Process Engineering Components Engineering Other Engineering Logistics Engineering The Integration of Engineering Disciplines Concurrent Design THE SYSTEM/PRODUCT LIFE CYCLE--SERIAL APPROACH System/Product Design and Development Production and/or Construction System/Product Utilization Maintenance and Support THE SYSTEM/PRODUCT LIFE CYCLE-CONCURRENT APPROACH System/Product Design and Development Production/Construction Process System/Product Utilization Development Operations Maintenance and Support Capability Development Operations Retirement and Material Disposal Feedback and Corrective-Action Sequential Versus Concurrent Approaches in System Design Evolution Of Detail Design Preliminary System Design System and Subordinate Specification and System Functional Analysis Design and Definition Of Subsystems NO YES Design and Definition Of Units, Assemblies, Software Subassemblies, and the Specification of Components and Parts Feedback Are Results Acceptable? Are Results Acceptable? NO YES Complete Set of Design Documentation (Database) NO Feedback Design Documentation Review and Approval? YES Engineering Model, Service Test Model, and/or Prototype Model Development, Test, and Evaluation Are Results Acceptable? NO YES Release of Documentation for System Production/Construction Recommendations For System/Equipment Modification(s) 4. Detail Design Aids ⚫ CAE,CAD,CAM,CALS ⚫ Computer Simulation ⚫ Models or Mockups ⚫ Rapid Prototyping 5. Detail Design Documentation Detail design documentation: • Design drawings • Material and part lists • Analyses and reports – documentation supporting design decisions Design Data Review Cycle Design Documentation Is Released for Formal Design Review Release of Engineering Design Data For Review Review for Compliance With Established System Requirements And Design Criteria: Functional Capability, Reliability, Maintainability Human Factors, Safety, Producibility, Disposability, And Others Are Requirements Satisfied? NO YES Design Changes are Initiated And Documentation is Revised Accomplish Formal Design Review Approval Design Documentation is Released for System Production or Construction YES NO Prepare, Submit, and Coordinate Recommendations For Product Improvement Recommendations Approval? Disapproval Special Review Meeting(s) To Discuss Alternatives YES Agreement On a Feasible Solution? NO No Feasible Solution is Attained; Document Trade-Off Study Results for Design Justification, And Determine Impact on System Requirements Revise System Specification as Required to Reflect Results 6. System Prototype Development Engineering Model ⚫ Service Test Model ⚫ Prototype Model ⚫ Engineering Model ◼ Represents a working system (or an element of the system) Exhibits functional characteristics defined in the specification ◼ OBJECTIVE: verify technical feasibility of an item ◼ ◼ does not represent the system in terms of physical dimensions, i.e., form or fit Service Model ◼ Represents a working system (or an element of the system) ◼ Component substitution allowed as long as the system functions properly OBJECTIVE: to verify functional performance – physical configuration interface ◼ ◼ reflects the end product in terms of functional performance and physical dimensions Prototype Model ◼ Represents production configuration of a system all aspects of form, fit, and function Not yet fully qualified ◼ ◼ ◼ No operational testing No environmental testing Evolution: ◼ ◼ ◼ directly from a mock-up OBJECTIVE: final evaluation before entering the production and/or construction phase ◼ ◼ series of working configurations Classification of Models ◼ Physical Models – geometric equivalents, either as miniatures, enlargements, or duplicates ◼ Analogue Models – focus on similarity in relations ◼ Schematic Models – charts and diagrams ◼ Mathematical Models - Higher degree of abstraction, but very useful! ◼ Descriptive vs. Prescriptive Models ◼ Descriptive – predict (explain) an outcome. ◼ Prescriptive – control (optimize) an outcome. Models and Indirect Experimentation ◼ Direct vs. Indirect Experimentation Direct – the object, state, or event is subject to manipulation and the results are observed. Indirect – uses a model (or simulation) for decision making Indirect Experimentation through Simulation ◼ Economic Feasibility of Testing ◼ Explores the effects of alternative system characteristics on system performance without actually producing and testing each candidate. ◼ May be physical, analogue, schematic or mathematical 7. Design Review Conceptual Design Preliminary Detail System Design And Advance System Design And Development Planning Phase Phase Phase Production and/or Construction Phase Operational Use and System Support Phase System Feasibility Analysis, Operational Requirements, Maintenance Concept, Advance Planning Functional Analysis, Requirements Allocation, Synthesis, Trade-Offs, Preliminary Design, Test and Evaluation Of Design Concepts, Detail Planning Detail Design of Subsystem and Components, Trade-offs, Development Of Prototype Models, Test and System Requirements, Evaluation, Evaluation, Production Planning and Review Process Production and/or Construction of the Informal Day-to-Day Design Review and System and its components, Supplier Evaluation Activity Production Activities, Distribution, System Operational Use Maintenance and Support, Data Collection and Analysis Conceptual Design Review (System Requirement Review) System Operational Use, System Design Views Sustaining Maintenance, Equipment/Software And Support, Data Collection Design Reviews And analysis, System Modification (as Required) Critical Design Review Homework 4 Writing Type B and C Specifications (Hardware and Software) Homework 4 Consider a Microwave Oven System, which senses and controls several I/O devices through sensors and actuators respectively. The oven is composed of five input devices: a door sensor which senses when the door is opened and closed by the user, a weight sensor to weigh food, temperature sensor to figure out if the food is hot or cold, a steam/cook level sensor to sense if the food is over/under cooked, and a keypad for entering commands. There are two output devices: a heating element for cooking food and a display for displaying information and prompts to the user. There is also a timer component, namely the real-time clock. System Engineering Objectives: 1. Pop a cup of corn 2. Thaw frozen chicken 3. Reheat a plate of food Note: One common theme in all these objectives is to get food to the right temperature and taste. Your task: Develop Type B and C specifications (hardware and software) for the previously developed list of Type A system specs [on Blackboard] for the microwave oven system. Objectives: 1) Pop a cup of corn. 2) Thaw frozen chicken. 3) Reheat a plate of food. Type A Type B Hardware 1A) System shall sense weight of food. 2A) System shall sense if food is hot or cold. 3A) System shall sense if food is over/under cooked. 4A) System shall sense when door is opened or closed. 5A) System shall have keypad control. 6A) System shall have real time clock/timer component. 7A) System shall have heat element with highest cook power. 8A) System shall contain radiation while in cooking operation. 9A) System shall have appropriate messages including warning messages for output. Type B Software Type C Hardware Component Type C Software Component
Purchase answer to see full attachment