1 / 48

Agenda for design activity (1 of 2)

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

ethel
Download Presentation

Agenda for design activity (1 of 2)

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

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

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

  3. 1. Example 1: understanding customer • Understand customer process • Customer wants • Converting wants to spec and contract • Product contract • Product spec • Contractor wants • Contractor requirements 1. Example 1: understanding customer

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

  5. Customer wants • W1: Live in a quiet place • W2: Have low maintenance costs • W3: Raise a garden • W4: Have room for family to visit • W5: Have adequate electricity • W6: Have a garage • W7: Cool in the evenings • W8: Pay $100,000 • W9: Obtain 6/1/99 1. Example 1: understanding customer

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

  7. Product contract • C1: Provide house and lot that meet spec (ANA) • C2: Pay $100,000 (INS) • C3: Close on sale by 6/1/99 (INS) 1. Example 1: understanding customer

  8. Product spec (1 of 2) • S01: <3 years old (ANA) • S02 <10 & > 3 miles from town of 5000 people (INS) • S03 > 1/2 acre lot (INS) • S04 Does not flood (ANA) • S05 Low maintenance construction (INS) • S06: >1800 feet in air conditioning (INS) 1. Example 1: understanding customer

  9. Product spec (2 of 2) • S07: At least 3 bedrooms (INS) • S08: Master bedroom on east side (INS) • S09: Attached two-car garage (INS) • S10: >100 amperes electrical service (INS) • S11: > 11 gal/min from at least one faucet (TEST) • S12: Equipment works (DEMO) 1. Example 1: understanding customer

  10. Contractor wants Customer wants Contractor wants Profit Pride Law 20% Happy buyer Meets code Contractor requirements 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. 1. Example 1: understanding customer

  11. Contractor requirements • Wants • Ds1: 20 percent profit (INS) • Ds2: Make buyer happy (INS) • Other • Dr1: Meets code (INS, DEMO) 1. Example 1: understanding customer

  12. 2. Example 2: design • Design process • Concept • Spec tree • Contractor design 2. Example 2: design

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

  14. Concept N Master Bedroom Bath Living Garage Kitchen Bedroom Bath Bedroom Storage Utility 2. Example 2: design

  15. Spec tree House and lot Real estate Structure Electrical Plumbing 2. Example 2: design

  16. Contractor design • Dd1: Plans • Floor plan • Elevations • Plumbing plan • Electrical plan • Foundation plan • Lot layout • Dd2: Flood analysis • Dd3: Cost and schedule 2. Example 2: design

  17. 3. Example 3: real estate product • Real-estate flowdown • Real-estate spec • Re-estate contract 3. Example 3: real-estate product

  18. Real-estate flowdown S01: < 3yrs S02: miles S03: 1/2 acre S04: doesn’t flood C2: $100,000 C3: close by 6/1/99 Ds1: 20% Dd1: Plans Dd2: flood analysis Dd3: Cost/sched study Rr1: miles Rr3: 1/2 acre Rr4: <3 yrs Rs1: land Rs5: survey Rr2: doesn’t flood Rs4: provide analysis Rs2: <$15,000 Rs3: close by 1/1/99 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

  19. Real-estate spec • Rr1: <10 & > 3 miles from town of 5000 people (INS) • Rr2: Does not flood (ANA) • Rr3: > 1/2 acre (INS) • Rr3 <3 years (INS) 3. Example 3: real-estate product

  20. Real-estate contract • Rs1: Provide land • Rs2: < $15,000 • Rs3: Close by 1/1/99 • Rs4: Provide flood analysis • Rs5: Provide survey 3. Example 3: real-estate product

  21. 4. Example 4: structure product • Structure flowdown • Structure spec • Structure contract 4. Example 4: structure product

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

  23. Structure spec • Sr1: Meets design (INS) • Sr2: Brick (INS) • Sr3: 30-yr composition (INS) • Sr4: Long-lasting paint (INS) • Sr5: Nylon carpet except bath and kitchen (INS) • Sr6: Ceramic tile on all other interior floors (INS) • Sr7: White exterior paint, beige interior paint, beige carpet (INS) • Sr8: White tile (INS) • Sr9: Meets code (INS) 4. Example 4: structure product

  24. Structure contract • Ss1: Provide structure • Ss2: <$53,000 • Ss3: Compete by 5/1/99 • Ss4: Coordinate with plumber and electrician 4. Example 4: structure product

  25. 5. Example 5: electrical product • Electrical flowdown • Electrical spec • Electrical contract 5. Example 5: electrical product

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

  27. Electrical spec • Er1: Meets design (INS) • Er2: >100 amperes electrical service (INS) • Er3: Meets code (INS) 5. Example 5: electrical product

  28. Electrical contract • Es1: Provide electrical • Es2: <$4,000 • Es3: Complete by 5/1/99 • Es4: Coordinate with structure 5. Example 5: electrical product

  29. 6. Example 6: plumbing product • Plumbing flowdown • Plumbing spec • Plumbing contract 5. Example 5: electrical product

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

  31. Plumbing spec • Pr1: Meets design (INS) • Pr2: >100 gal/min from one faucet (TEST) • Pr3: Meets code (INS) 6. Example 6: plumbing product

  32. Plumbing contract • Ps1: Provide plumbing • Ps2: <$8,000 • Ps3: Complete by 5/1/99 • Ps4: Coordinate with structure 6. Example 6: plumbing product

  33. 7. Optimizing design • Waterfall process • Modified waterfall process • Providing information when needed 7. Optimizing design

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

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

  36. Providing information when needed Percent of requirements complete 100 0 0 Percent of tasks to be developed 100 Concept Functions I/Fs Mechanical Test Development can start before requirements are complete 7. Optimizing design

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

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

  39. 10. EIA 632 design process • Requirements relationship • Design Process • Logical solution definition • Physical solution definition • Specified requirements generation 10. EIA design process

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

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

  42. Logical solution definition (1 of 3) • Analyze functions, objects, data flow, data structures • Define subfunctions • Perform trade studies • Assign performance requirements & constraints • Analyze behaviors 10. EIA design process

  43. Logical solution definition (2 of 3) • Identify and define interfaces, states and modes, timelines, data, & and control • Analyze failure modes and define effects 10. EIA design process

  44. Logical solution definition (3 of 3) • Establish set of logical solutions • Validate logical solutions • Record logical solutions • Identify and define derive technical requirements • Record derived technical requirements 10. EIA design process

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

  46. Specified requirements generation • Fully characterize design solution • Verify design solution • Record design solution • Generate and record specified requirements • Initiate development of enabling processes 10. EIA design process

  47. 11. Homework (1 of 2) • A customer wants to sell a line of lawn mowers that can cut Texas lawn grasses, requires partial assembly, and that costs less than $300 • Develop a design that satisfies the customer • 1. List the customer requirements (>0, <10) • 2. List pseudo customer requirements (0, <20) • 3. List the key items in the concept (>0, <20) • 4. List the key items in the design (>0, <20) 11. Homework

  48. 11. Homework (2 of 2) • Develop a design that satisfies the customer (continued) • 5. List key items in documentation (>0, <20) • 6. List the key items in the CDR (>0, <20) • 7. List items shall be (>0, <30 words); no pictures 11. Homework

More Related