6. Design1 Agenda for design activity (1 of 2) r 1. Example 1: understanding customer r 2. Example 2: design r 3. Example 3: real estate product r 4. Example.

Slides:



Advertisements
Similar presentations
East Hampton High School July 2013 – July 2014 Design Phases.
Advertisements

Mahmut Ali GÖKÇEIndustrial Systems Engineering Lecture 2 System Identification ISE102 Spring 2007.
1 Homework r1. Module 2 r2. Module 4 r3. Module 7 r4. Module 8 r5. Module 9 r6. Module 11 r7. Module 12 r8. Module 14.
S Y S T E M S E N G I N E E R I N G.
1 Agenda for design activity r1. Objective r2. Disclaimer r3. Design context r4. Solutions r5. Design process r6. Other design processes.
The System and Software Development Process Instructor: Dr. Hany H. Ammar Dept. of Computer Science and Electrical Engineering, WVU.
Systems Analysis & IT Project Management Pepper. System Life Cycle BirthDeathDevelopmentProduction.
Software Modeling SWE5441 Lecture 3 Eng. Mohammed Timraz
EYYUP ORAK Material requirements planning (MRP) is a computer-based inventory management system designed to assist production managers in.
Requirements Engineering n Elicit requirements from customer  Information and control needs, product function and behavior, overall product performance,
IS 421 Information Systems Management James Nowotarski 16 September 2002.
1 Introduction to System Engineering G. Nacouzi ME 155B.
Information Systems Development and Acquisition Chapter 8 Jessup & Valacich Instructor: Ramesh Sankaranarayanan.
Trade Study Training Need and Goals Need Consistent methodologies and practices performing trade studies Pros/cons, advantages/disadvantages, customer/management.
Lead Black Slide. © 2001 Business & Information Systems 2/e2 Chapter 13 Developing and Managing Information Systems.
SDLC. Information Systems Development Terms SDLC - the development method used by most organizations today for large, complex systems Systems Analysts.
ES305: Virtual Tools in Engineering Design: The Eng. Design Process James Carroll, Associate Professor Electrical and Computer Engineering.
System Engineering Instructor: Dr. Jerry Gao. System Engineering Jerry Gao, Ph.D. Jan System Engineering Hierarchy - System Modeling - Information.
The Software Product Life Cycle. Views of the Software Product Life Cycle  Management  Software engineering  Engineering design  Architectural design.
Chapter 2 - Overview of the Systems Engineering Design Process1 Aerospace Systems Engineering Chapter 2 - Overview of the Systems Engineering Design Process.
Spring 2008, King Saud University Engineering Administration Dr. Khalid Al-Gahtani 1 What is a Project? “A Project is a one-shot, time-limited, goal- directed,
Welcome to CMPE003 Personal Computer Concepts: Hardware and Software Winter 2003 UC Santa Cruz Instructor: Guy Cox.
Introduction to Computer Technology
 Located in Murrieta Hills › Accessible via two highways  Family-oriented city › Established community › Excellent school district  Two floor plans.
QUALITY MANAGEMENT SYSTEM ACCORDING TO ISO
Systems Analysis and Design: The Big Picture
Chapter 2: Overview of Essentials ISE 443 / ETM 543 Fall 2013.
Chapter 10 Architectural Design
SUBJECT  Industrial facility design. GROUP MEMBERS H.Hammad Ali 11-IE-32 S.Hammad shah 11-IE-21 Hammad Hassan 11-IE-41.
S/W Project Management Software Process Models. Objectives To understand  Software process and process models, including the main characteristics of.
3. Design1 Agenda for Design Activity r1. Objective r2. Design concepts r3. A design process r4. Optimizing design r5. Example r6. Other design processes.
By: Brian Toomer ET-494 Senior Design Dr. Cris Koutsougeras Advisor: Mr. Rode’
An Introduction to Software Architecture
Software System Engineering: A tutorial
2.01 Housing Options Sherry Brooks David W. Butler April 28, 2009.
1 Lecture 5.2a: SEF Ch 8 SE Outputs Dr. John MacCarthy UMBC CMSC 615 Fall, 2006.
1 Systems Engineering Process Review Mark E. Sampson EMIS 8340 Systems Engineering Tool—applying tools to engineering systems.
Engineering System Design
Product Development Chapter 6. Definitions needed: Verification: The process of evaluating compliance to regulations, standards, or specifications.
Software Reviews & testing Software Reviews & testing An Overview.
Fundamentals of Information Systems, Third Edition1 Systems Design Answers the question “How will the information system do what it must do to solve a.
10 Software Architecture CSCU 411 Software Engineering.
The System and Software Development Process Instructor: Dr. Hany H. Ammar Dept. of Computer Science and Electrical Engineering, WVU.
Developed by Reneta Barneva, SUNY Fredonia The Process.
Prof Ralph V. Locurcio, PE CON 2001 CVE Sequence Single Family House - 3,000 square feet Duration 1 General Conditions 21 2 Apply for Permits.
The System and Software Development Process Instructor: Dr. Hany H. Ammar Dept. of Computer Science and Electrical Engineering, WVU.
Fall CS-EE 480 Lillevik 480f06-l1 University of Portland School of Engineering Senior Design Lecture 1 Introductions Course objectives What is design?
 CMMI  REQUIREMENT DEVELOPMENT  SPECIFIC AND GENERIC GOALS  SG1: Develop CUSTOMER Requirement  SG2: Develop Product Requirement  SG3: Analyze.
Software Development Process CS 360 Lecture 3. Software Process The software process is a structured set of activities required to develop a software.
1 Agenda for design activity r1. Tracing requirements r2. Managing requirements r3. Requirements management tools.
David M. Kroenke and David J. Auer Database Processing Fundamentals, Design, and Implementation Appendix B: Getting Started in Systems Analysis and Design.
Software Engineering Lecture 9: Configuration Management.
2. Design1 Agenda for design activity r1. Objective r2. Disclaimer r3. Solutions r4. Design process r5. Other design processes.
Systems Architectures System Integration & Architecture.
© 2009 Artisan Software Tools. All rights reserved. Testing Solutions with UML/SysML Andrew Stuart, Matthew Hause.
Develop Schedule is the Process of analyzing activity sequences, durations, resource requirements, and schedule constraints to create the project schedule.
8. Acquire products & build1 Agenda for acquire products activity r1. Objective r2. Level of products r3. Role of customer r4. Make or buy r5. Subcontractor.
Process engineering Quality controls.
Information Systems Development
Medical Device Software Development
Systems Analysis and Design
Classical Waterfall Model
Software Requirements
Life Cycle Models PPT By :Dr. R. Mall.
FIVE PROJECT PHASES 5C-3 Sun. 8:00-10:00am 21/ 2/2016.
Engineering Processes
House Construction Budget Plan
Chapter 9 Architectural Design.
PSS verification and validation
System Analysis and Design:
Presentation transcript:

6. Design1 Agenda for design activity (1 of 2) r 1. Example 1: understanding customer r 2. Example 2: design r 3. Example 3: real estate product r 4. Example 4: structure product r 5. Example 5: electrical product r 6. Example 6: plumbing product

6. Design2 Agenda for design activity (2 of 2) r 7. Optimizing design r 8. DMC design process r 9. James Martin design process r 10. EIA 632 design process r 11. Homework

6. Design3 1. Example 1: understanding customer rUnderstand customer process rCustomer wants rConverting wants to spec and contract rProduct contract rProduct spec rContractor wants rContractor requirements 1. Example 1: understanding customer

6. Design4 Understand customer process Product requirements review Assist customer in developing product requirements and interfaces initial contract, spec, & I/Fs final contract, spec, & I/Fs approval 1. Example 1: understanding customer

6. Design5 Customer wants rW1: Live in a quiet place rW2: Have low maintenance costs rW3: Raise a garden rW4: Have room for family to visit rW5: Have adequate electricity rW6: Have a garage rW7: Cool in the evenings rW8: Pay $100,000 rW9: Obtain 6/1/99 1. Example 1: understanding customer

6. Design6 Converting wants to spec & contract W1: quiet W2: low costs S01: <3yrs S04: no flood S05: low maint S12: equip works S02: miles W3:garden S03: 1/2 acre S11: water W4: family W5: electric W6: garage W7: cool W8: $100K W9: close S06: 1800 S07: 3 bdr S10: 100 amps S09: garage S08:east C2:$100K C3:close Wants SpecContract Wants flow to spec or contract directly or via studies SSSSSS C1: house & lot 1. Example 1: understanding customer

6. Design7 Product contract rC1: Provide house and lot that meet spec (ANA) rC2: Pay $100,000 (INS) rC3: Close on sale by 6/1/99 (INS) 1. Example 1: understanding customer

6. Design8 Product spec (1 of 2) rS01: <3 years old (ANA) rS02 3 miles from town of 5000 people (INS) rS03 > 1/2 acre lot (INS) rS04 Does not flood (ANA) rS05 Low maintenance construction (INS) rS06: >1800 feet in air conditioning (INS) 1. Example 1: understanding customer

6. Design9 Product spec (2 of 2) rS07: At least 3 bedrooms (INS) rS08: Master bedroom on east side (INS) rS09: Attached two-car garage (INS) rS10: >100 amperes electrical service (INS) rS11: > 11 gal/min from at least one faucet (TEST) rS12: Equipment works (DEMO) 1. Example 1: understanding customer

6. Design10 Contractor wants Customer wantsContractor wants ProfitPrideLaw 20%Happy buyerMeets code Contractor wants create pseudo requirements in addition to customer requirements. These pseudo requirements can be considered to be part of the design. In this example, they don’t flow from the customer wants. Contractor wants create pseudo requirements in addition to customer requirements. These pseudo requirements can be considered to be part of the design. In this example, they don’t flow from the customer wants. Contractor requirements 1. Example 1: understanding customer

6. Design11 Contractor requirements rWants rDs1: 20 percent profit (INS) rDs2: Make buyer happy (INS) rOther rDr1: Meets code (INS, DEMO) 1. Example 1: understanding customer

6. Design12 2. Example 2: design rDesign process rConcept rSpec tree rContractor design 2. Example 2: design

6. Design13 Design process Preliminary design review Critical design review Develop product concept Develop product design conceptdesign spec & I/Fs lower specs & I/Fs Develop lower specs & interfaces approval Concept design review approval 2. Example 2: design

6. Design14 Concept Garage StorageUtility Living Kitchen Bedroom Master Bedroom Bath N 2. Example 2: design

6. Design15 Spec tree House and lot Real estateStructureElectricalPlumbing 2. Example 2: design

6. Design16 Contractor design rDd1: Plans rFloor plan rElevations rPlumbing plan rElectrical plan rFoundation plan rLot layout rDd2: Flood analysis rDd3: Cost and schedule 2. Example 2: design

6. Design17 3. Example 3: real estate product rReal-estate flowdown rReal-estate spec rRe-estate contract 3. Example 3: real-estate product

6. Design18 Real-estate flowdown C2: $100,000 C3: close by 6/1/99 Ds1: 20% Dd3: Cost/sched study Rs2: <$15,000 Rs3: close by 1/1/99 Dd1: PlansDd2: flood analysis Rr1: miles Rr3: 1/2 acre Rr4: <3 yrs Rs1: land Rs5: survey Rr2: doesn’t flood Rs4: provide analysis S01: < 3yrs S02: miles S03: 1/2 acre S04: doesn’t flood Product spec, product contract, and contractor-wants flowdown directly and through studies to become the real estate spec and contract Product spec, product contract, and contractor-wants flowdown directly and through studies to become the real estate spec and contract 3. Example 3: real-estate product

6. Design19 Real-estate spec rRr1: 3 miles from town of 5000 people (INS) rRr2: Does not flood (ANA) rRr3: > 1/2 acre (INS) rRr3 <3 years (INS) 3. Example 3: real-estate product

6. Design20 Real-estate contract rRs1: Provide land rRs2: < $15,000 rRs3: Close by 1/1/99 rRs4: Provide flood analysis rRs5: Provide survey 3. Example 3: real-estate product

6. Design21 4. Example 4: structure product rStructure flowdown rStructure spec rStructure contract 4. Example 4: structure product

6. Design22 Structure flowdown C2: $100,000 C3: close by 6/1/99 Ds1: 20% Dd3: Cost/sched study Ss2: <$53,000 Ss3: close by 5/1/99 Ss4: coordinate Dd1: PlansDd2: flood analysis Product spec, product contract, and contractor-wants flowdown through studies to become the structure spec and contract Product spec, product contract, and contractor-wants flowdown through studies to become the structure spec and contract Ss1: structure Sr1: meets design Sr2: brick Sr3: roof Sr4: paint Sr5: carpet S05: low maintenance S12: works Dr1: meets code Ds2: buyer happy Sr6: tile Sr7: colors Sr8: tile color Sr9: meets code 4. Example 4: structure product

6. Design23 Structure spec rSr1: Meets design (INS) rSr2: Brick (INS) rSr3: 30-yr composition (INS) rSr4: Long-lasting paint (INS) rSr5: Nylon carpet except bath and kitchen (INS) rSr6: Ceramic tile on all other interior floors (INS) rSr7: White exterior paint, beige interior paint, beige carpet (INS) rSr8: White tile (INS) rSr9: Meets code (INS) 4. Example 4: structure product

6. Design24 Structure contract rSs1: Provide structure rSs2: <$53,000 rSs3: Compete by 5/1/99 rSs4: Coordinate with plumber and electrician 4. Example 4: structure product

6. Design25 5. Example 5: electrical product rElectrical flowdown rElectrical spec rElectrical contract 5. Example 5: electrical product

6. Design26 Electrical flowdown C2: $100,000 C3: close by 6/1/99 Ds1: 20% Dd3: Cost/sched study Es2: <$4,000 Es3: close by 5/1/99 Es4: coordinate Dd1: PlansDd2: flood analysis Product spec, product contract, and contractor-wants flowdown through studies to become the electrical spec and contract Product spec, product contract, and contractor-wants flowdown through studies to become the electrical spec and contract Es1: electrical Er1: meets design Pr2: electrical Pr3: meets code S10: electrical S12: works Dr1: meets code 5. Example 5: electrical product

6. Design27 Electrical spec rEr1: Meets design (INS) rEr2: >100 amperes electrical service (INS) rEr3: Meets code (INS) 5. Example 5: electrical product

6. Design28 Electrical contract rEs1: Provide electrical rEs2: <$4,000 rEs3: Complete by 5/1/99 rEs4: Coordinate with structure 5. Example 5: electrical product

6. Design29 6. Example 6: plumbing product rPlumbing flowdown rPlumbing spec rPlumbing contract 5. Example 5: electrical product

6. Design30 Plumbing flowdown C2: $100,000 C3: close by 6/1/99 Ds1: 20% Dd3: Cost/sched study Ps2: <$8,000 Ps3: close by 5/1/99 Ps4: coordinate Dd1: PlansDd2: flood analysis Product spec, product contract, and contractor-wants flowdown through studies to become the plumbing spec and contract Product spec, product contract, and contractor-wants flowdown through studies to become the plumbing spec and contract Ps1: plumbing Pr1: meets design Pr2: water Pr3: meets code S11: water S12: works Dr1: meets code 6. Example 6: plumbing product

6. Design31 Plumbing spec rPr1: Meets design (INS) rPr2: >100 gal/min from one faucet (TEST) rPr3: Meets code (INS) 6. Example 6: plumbing product

6. Design32 Plumbing contract rPs1: Provide plumbing rPs2: <$8,000 rPs3: Complete by 5/1/99 rPs4: Coordinate with structure 6. Example 6: plumbing product

6. Design33 7. Optimizing design rWaterfall process rModified waterfall process rProviding information when needed 7. Optimizing design

6. Design34 Waterfall process System design Box design Software design Software i&t Box i&t System i&t Waterfall process has classic V pattern. Steps are serial with each step finishing before the next starts 7. Optimizing design

6. Design35 Modified waterfall process System design Box design Software design Software i&t Box i&t System i&t Modified waterfall has shorter cycle time. It starts earlier & tasks develops in parallel often using multiple builds. Modified waterfall has shorter cycle time. It starts earlier & tasks develops in parallel often using multiple builds. Tasks start earlier Software and box developed in multiple builds 7. Optimizing design

6. Design36 Providing information when needed Percent of requirements complete ConceptFunctionsI/FsMechanicalTest Percent of tasks to be developed Development can start before requirements are complete 7. Optimizing design

6. Design37 8. DMC design process Requirements analysis Functional analysis and allocation Synthesis System analysis and control requirements loop design loop verification process inputs process outputs Systems Engineering Process 8. DMC design process

6. Design38 9. James Martin design process Requirements Analysis Functional Analysis and Allocation Synthesis Requirements loopDesign loop Requirements and architecture documentation Verification loop System analysis and optimization Specs, interfaces, design requirements product characteristics 9. James Martin design process

6. Design EIA 632 design process rRequirements relationship rDesign Process rLogical solution definition rPhysical solution definition rSpecified requirements generation 10. EIA design process

6. Design40 Requirements relationship User or customer requirements System technical requirements Logical solution Physical solution Derived technical requirements Design solution Specified requirements Other stakeholder requirements TRACE TO Assigned requirements TRACE TO ASSIGNED TO DRIVE SOURCE OF SPECIFIED BY BECOME The EIA 632 entity relationship is similar to the PBDA approach but is more complex. The EIA 632 entity relationship is similar to the PBDA approach but is more complex. 10. EIA design process

6. Design41 Design process Logical Solution Definition Specified Requirements Generation Physical Solution Definition Specifications, drawings, models System technical requirements The EIA 632 design process is quite similar to the PBDA, but it is more serial in description The EIA 632 design process is quite similar to the PBDA, but it is more serial in description EIA 632 Figure EIA design process

6. Design42 Logical solution definition (1 of 3) rAnalyze functions, objects, data flow, data structures rDefine subfunctions rPerform trade studies rAssign performance requirements & constraints rAnalyze behaviors 10. EIA design process

6. Design43 Logical solution definition (2 of 3) rIdentify and define interfaces, states and modes, timelines, data, & and control rAnalyze failure modes and define effects 10. EIA design process

6. Design44 Logical solution definition (3 of 3) rEstablish set of logical solutions rValidate logical solutions rRecord logical solutions rIdentify and define derive technical requirements rRecord derived technical requirements 10. EIA design process

6. Design45 Physical solution definition Perform system analysis Define I/Fs ID & analyze critical parameters ID & assess physical solution options ID and define technical requirements Group requirements & solutions Assign groups to physical solutions Generate alternative solutions Select solution The physical solution definition is more serial than PBDA. 10. EIA design process

6. Design46 Specified requirements generation rFully characterize design solution rVerify design solution rRecord design solution rGenerate and record specified requirements rInitiate development of enabling processes 10. EIA design process

6. Design Homework (1 of 2) rA customer wants to sell a line of lawn mowers that can cut Texas lawn grasses, requires partial assembly, and that costs less than $300 rDevelop a design that satisfies the customer r1. List the customer requirements (>0, <10) r2. List pseudo customer requirements (0, <20) r3. List the key items in the concept (>0, <20) r4. List the key items in the design (>0, <20) 11. Homework

6. Design Homework (2 of 2) rDevelop a design that satisfies the customer (continued) r5. List key items in documentation (>0, <20) r6. List the key items in the CDR (>0, <20) r7. List items shall be (>0, <30 words); no pictures 11. Homework