1 / 40

Agenda for introduction

Agenda for introduction. 1. Course details 2. Disclaimer 3. Reasons why systems fail 4. Products 5. Cycles, phases, and activities 6. PBDA. 1. Course details. Course and instructor Course content Textbook and time Schedule Grading Formats. 1. Course details. Course and instructor.

dooley
Télécharger la présentation

Agenda for introduction

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 introduction • 1. Course details • 2. Disclaimer • 3. Reasons why systems fail • 4. Products • 5. Cycles, phases, and activities • 6. PBDA

  2. 1. Course details • Course and instructor • Course content • Textbook and time • Schedule • Grading • Formats 1. Course details

  3. Course and instructor Course -- 7310 Systems Engineering Design Room -- 218 Caruth Hall Instructor -- Jim Hinderer Work phone number -- (972) 344 7410 Home phone number -- (972) 359 1557 E-mail address -- j-hinderer@raytheon.com 1. Course details

  4. Course content • Show how to design a system from start to delivery • Show applications to commercial and military systems, large and small systems, hardware and software systems, and people systems 1. Course details

  5. Textbook and time • Textbook -- none • Class time -- 7:15 - 9:15 1. Course details

  6. Schedule • May 29 -- Introduction • June 3, 5 -- Design • June 10, 12 -- Ideas • June 17, 19 -- Examples • June 24, 26, July 1 -- Math • July 3 -- Project • July 8, 10, 15 -- Math • July 17 -- System • July 22 -- Software • July 24 -- Hardware • July 29 -- Final 1. Course details

  7. Grading • Project -- 50% • Final -- 50% 1. Course details

  8. Formats • Non-electronic: Pencil and paper • Electronic: Office 97 Word, Excel, PowerPoint • PC and not Macintosh 1. Course details

  9. 2. Disclaimer • Design is more of an art than a science. • Almost any approach to design will work if someone takes ownership of success • No one approach is better than all the others • We will use the approach used in the Systems Engineering Process course 2. Disclaimer

  10. 3. Reasons systems fail before delivery after delivery lack of qualified people unmanaged risks didn’t meet requirements wrong requirements overlooked something failure to execute failed to impress customer other 3. Reasons systems fail

  11. 4. Products • Product definition • Products composed of products • Types of products • Need for products • Need for lower-level products • Examples 4. Products

  12. Product definition (1 of 2) • A product is something produced by nature or by human industry or art • A product is something we can procure -- hardware, software, data, services. 4. Products

  13. Product definition (2 of 2) • Examples • Hardware -- space shuttle, house, circuit card, resistor • Software -- program, firmware • Data -- documents, management objects • Services -- activities • The concept of a product makes explaining system engineering easier. 4. Products

  14. Products composed of products Level 1 Product Higher-level products Level 2 Product 1 Level 2 Product 2 Level 3 Product 1 Level 3 Product 2 Level 4 Product 1 Level 4 Product 2 Level 4 Product 3 Lower-level products 4. Products

  15. Types of products (1 of 2) Level N Product Deliverable Products Environment Products Engineering Products Products can be divided into three types of products -- delivered products, environment products, and engineering products. 4. Products

  16. Types of products (2 of 2) • Deliverable products -- part of level-N product • Environment products -- physical products that interact physically with the level-N product throughout its life, such as manufacturing, test, and maintenance equipment • Engineering products -- other products that enable development of the level-N product, such as specifications 4. Products

  17. Need for products • We need products to describe what we’re controlling • Products may be developed or procured without development 4. Products

  18. Need for lower-level products • We need lower-level products if we’re going to procure something needed for doing the development 4. Products

  19. Example 1 -- model airplane Model airplane Fuselage Wing Stabilizer Rudder Glue Good example -- We can use the lower-level products to make the higher-level product 4. Products

  20. Example 2 -- house, bad example House Kitchen Bathroom Bedroom 1 Bedroom 2 Garage Bad example -- We wouldn’t use the lower-level products to make the higher-level product 4. Products

  21. Example 3 -- house, good example House Plumbing Foundation Framing Roof Electrical Dry wall Good example -- We can use the lower-level products to make the higher-level product 4. Products

  22. 5. Cycles, phases, and activities • Definitions • Product life cycle • Pre-develop-phase activities • Develop-phase activities • Post-develop-phase activities • Example 5. Cycles, phases, and activities

  23. Definitions • Cycle -- a complete set of events occurring in the same sequence • Product life cycle • Contract life cycle • Phase -- part of a cycle; the period of time the activities take • Activity -- execution of a set of tasks • Process -- steps used to accomplish an activity 5. Cycles, phases, and activities

  24. Product life cycle Phases Pre-develop Develop Post-develop Time 5. Cycles, phases, and activities

  25. Pre-develop-phase activities Sub phases or activities Sub phases overlap Identify opportunity Meet the customer Discuss the work Respond to RFP Time 5. Cycles, phases, and activities

  26. Develop-phase activities Sub-phases or activities Manage Understand requirements Sub-phases overlap Design Acquire products Build Verify Sell off Time 5. Cycles, phases, and activities

  27. Post-develop-phase activities Sub-phases Field test and validate Sub-phases overlap Train Operate Maintain Support Produce Upgrade Dispose Time 5. Cycles, phases, and activities

  28. Example -- build a house Activities Supervise Learn what buyer wants Have architect make blueprint Get land and lumber Build See if the house is OK Close Time 5. Cycles, phases, and activities

  29. 6. PBDA • Approach • PBDA block diagram • Application of PBDA to products • Example • Work products (WPs) 6. PBDA

  30. The approach Determine what customer wants Make it happen Decide what to do Get what it takes to do it Do it Approach consists of applying these seven activities to each product in the system Check it out Convince customer it’s what he or she wanted 2. Basic approach

  31. External: higher product teams contracts, specs, interfaces people, facilities, tools, capital, communications, library schedule, budget, risks, TPPs, issues, AIs, plans, timeline, changes, problems, legal status 1. Manage MR contracts specs, I/Fs RR control, status design 3. Design CR PDR CDR lower specs & I/Fs build proc 4. Acquire lower contracts, specs, interfaces lower products product 5. Build test results test spec lower test results lower product, test results, test spec 6. Verify status agree agree TRR VR test proc External: lower product teams 7. Sell off FCA PCA PBDA block diagram 2. Understand req

  32. Application of PBDA to products Higher product Product of interest Lower product 1 Lower product 2 Lower product N PBDA is applied to each product separately 6. PBDA

  33. Example (1 of 2) System Subsystem Subsystem HWCI HWCI Unit HWCI Unit CSCI CSCI Example with 10 products 6. PBDA

  34. Example (2 of 2) 1 2 3 5 8 6 7 10 9 Developing the example with 10 instantiations of PBDA 6. PBDA

  35. Management objects (WPs) (1 of 6) • Definition • A WP is a tangible object that is used to control the PBDA • Execution of the PBDA can be thought of as completing the associated WPs PBDA executed by completing WPs 6. PBDA

  36. WPs (2 of 6) • WPs for management • Environment (6) -- people, facilities, tools, capital, communications, library • Control (11) -- schedule, budget, risks, TPPs, issues, AIs, timeline, plans, changes, problems, legal • Reviews and audits (9) --MR, RR, CD, PDR, CDR, TRR, VR, PCA, FCA 26 WPs used for managing each product in PBDA. 6. PBDA

  37. WPs (3 of 6) • WP accounting • Understand (0) -- • Design (3) -- design, lower specs, lower interfaces • Acquire (1) -- lower contracts • Build (2) -- build procedure, product • Verify (3) -- test spec, test procedure, test results • Sell off (1) -- agreement 10 WPs used for developing each product in PBDA. 6. PBDA

  38. WPs (4 of 6) • WPs vs inputs • Higher inputs (3) -- contracts, specs, interfaces • Lower inputs (4) -- lower product, lower test results, lower test spec, status Inputs are monitored but aren’t WPs of the product of interest 6. PBDA

  39. WPs (5 of 6) • Optimizing WPs • Some management objects can be shared between levels • Not all management objects are needed at each level. Not all WPs must always be used 6. PBDA

  40. WPs (6 of 6) product (1) problems and changes (2) lower products (1) verify (3) higher inputs (3) legal (1) design (3) reviews and audits (9) plan and timeline (2) issues and AIs (2) budget & schedule (2) lower inputs (3) physical environment (6) acquire (1) paper risks & TPPs (2) agreement (1) external paper build proc (1) decreasing likelihood of use An example pareto of WPs by likely use 6. PBDA

More Related