1 / 57

Agenda for Introduction

Agenda for Introduction. 1. Course details 2. Basic approach 3. Products 4. Cycles, phases, and activities 5. Control 6. System engineering 7. Homework. 1. Course Details. Course and instructor Course description Textbook and time Schedule Grading Formats. 1. Course details.

tanginika-morris
Download Presentation

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. Basic approach • 3. Products • 4. Cycles, phases, and activities • 5. Control • 6. System engineering • 7. Homework

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

  3. Course and Instructor Course -- 7301 Systems Engineering Process Room -- 125 Caruth Hall Instructor -- Jim Hinderer Work phone number -- (972) 344 7410 Home phone number -- (972) 596 2693 E-mail address -- j-hinderer@raytheon.com Web site -- http://www.seas.smu.edu/sys/7301/ This web site contains the syllabus and the course notes. If a student chooses to print the course notes to view during the lectures, printing the vugraphs with six per page will save a lot of paper since there are about 700 vugraphs, 1. Course details

  4. Course Content • Show how to develop a system from start to delivery • Illustrate a product-based development approach • Show applications to commercial and military systems, large and small systems, and hardware and software systems 1. Course details

  5. Textbook and Time • Textbook -- Systems Engineering Guidebook by James N. Martin • Class time -- 6:30 - 9:20 • 6:30 - 7:50 first lecture period • 7:50 - 8:00 break • 8:00 - 9:20 second lecture period 1. Course details

  6. Tentative Schedule • 8/23 Introduction • 8/30 Understanding-customer • 9/06 Labor Day No class • 9/13 Understanding-customer • 9/20, 9/27, 10/04 Design • 10/11 Acquisition and build • 10/18 Verification and sell-off • 10/25, 11/01, 11/8 Management • 11/15 Processes • 11/22 Implementation • 11/29 Project, no class • 12/06 Applications • 12/13 Final 1. Course details

  7. Grading • Homework 35% • Project 30% • Final 35% 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. Basic Approach • System engineering • Guideline • Activities • Application 2. Basic approach

  10. System Engineering • System engineering is more of an art than a science. • Almost any method of system engineering will work if someone takes ownership of success • The goal of this course is to explain one method for developing systems and to indicate how this method relates to other methods. 2. Basic approach

  11. Guidelines • Wisdom • Simplicity 2. Basic approach

  12. Activities Determine what customer wants Make it happen Decide what to do Get what it takes to do it Do it Check it out Convince customer it’s what he or she wanted 2. Basic approach

  13. Application • Apply same set of activities to each task 2. Basic approach

  14. 3. Products • Product definition • Products composed of products • Examples • Need for lower-level products 3. Products

  15. Product Definition • A product is something produced by nature or by human industry or art • A product is something we can procure -- hardware, software, data, services. • Examples -- space shuttle, house, circuit card, software program, resistor. • The concept of a product makes explaining system engineering easier. 3. Products

  16. Products Composed of Products Higher-level products Level 1 Product 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 3. Products

  17. Need for Lower-Level Products • A product that doesn’t need development or support does not need lower-level products • Whether a product needs lower-level products depends upon whether we care about it. • A stone has no lower level components • A light bulb has lower level components, but purchasers don’t care • A personal computer has lower level components, and some people may care 3. Products

  18. 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 3. Products

  19. Example 2 -- House House Kitchen Bathroom Bedroom 1 Bedroom 2 Garage Bad example -- We wouldn’t use the lower-level products to make the higher-level product 3. Products

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

  21. 4. Cycles, Phases, and Activities • Definitions of cycles, phases and activities • Product life cycle • Example • Notes on activities 4. Cycles, phases, and activities

  22. Definitions • A cycle is a complete set of events occurring in the same sequence • Product life cycle • Contract life cycle • A phase is part of a cycle • An activity is a execution of a set of tasks 4. Cycles, phases, and activities

  23. Product Life Cycle Phases Pre-develop Develop Post-develop Time 4. Cycles, phases, and activities

  24. Develop Phase Activities (1 of 2) Understand requirements Manage Determine what customer wants Make it happen Design Decide what to do Acquire products Get what it takes to do it Build Do it Check it out Verify Convince customer it’s what he or she wanted Sell-off 4. Cycles, phases, and activities

  25. Develop Phase Activities (2 of 2) Sub phases Sub phases overlap Manage Understand requirements Design Acquire products Build Verify Sell off Time 4. Cycles, phases, and activities

  26. Post-Develop Activities Sub-phases Sub phases overlap Field test and validate Train Operate Maintain Support Produce Upgrade Dispose Time 4. Cycles, phases, and activities

  27. Notes on Activities • Not every product has the same activities • Developing software may not require acquiring products • Integration or verification may be deferred to another level • Some products may be so simple that they don’t require formal management. 4. Cycles, phases, and activities

  28. Contrasting Definitions • Activity - work towards a goal • Phase -- period of time the activity takes • Process -- steps used to accomplish activity 4. Cycles, phases, and activities

  29. 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 4. Cycles, phases, and activities

  30. 5. Control • Classes of products • Product-based activities • Product-based context • Control by use of management objects 5. Control

  31. Classes of Products (1 of 2) Level N Product Deliverable Products Environment Products Engineering Products 5. Control

  32. Classes 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 5. Control

  33. Control Using Engineering Products Development and environment products Activities and engineering products are used to develop development and environment products Engineering products Activities 5. Control

  34. Alternate View of Control by Products Level N+1 Level N Development products Activities and engineering products Product Environment products Note: EIA 632 refers to environment and engineering products as enabling products 5. Control

  35. Product-Based Development Activities External: Higher Product Team plan sched & budget reviews, risks, TPPs issues, prob, AIs config, changes SOW spec interfaces facilities tools, capital communications library people legal 1. Manage MR SOW spec interfaces 2. Understand requirements control & status RR design 3. Design CR PDR CDR lower specs interfaces 4. Acquire SOWs specs interfaces lower products build proc 5. Build product test results test spec lower test results test proc plans scheds & budgets reviews, risks, TPPs issues, probs, AIs configs, changes product 6. Verify products test results test spec deliverables agreements TRR VR deliverables agreement test results External: Lower Product Teams 7. Sell off FCA/PCA 5. Control

  36. Product-Based Context Higher Product Product of Interest Lower Product 1 Lower Product 2 Lower Product N Product-based activities are applied to each product separately 5. Control

  37. Example (1 of 2) System Subsystem Subsystem HWCI HWCI Unit HWCI Unit CSCI CSCI 5. Control

  38. Example (2 of 2) 1 2 3 5 8 6 7 10 9 Developing the system employs 10 instantiations of the product-based development approach

  39. Optimizing Activities & Management Objects • Some management objects can be shared between levels • Not all management objects are needed at each level. 5. Control

  40. Usefulness of Product Concept (1 of 2) • System engineering has evolved slowly • Many disciplines could not identify where they fit within system engineering, so they defined what they needed independently • As a result, there are many overlapping concepts 5. Control

  41. Usefulness of Product Concept (2 of 2) • Makes explaining system engineering easier • Allows these disciplines to be parallel rather than randomly aligned supportability electrical engineering system engineering software maintainability configuration management 5. Control

  42. Reason for Product-Based Approach • Alternate approach • 106 activities • 966 management objects • Result of many overlapping perspectives • Product-based approach • 7 activities • 46 management objects • Result of applying same approach at all levels Product-based approach is used for simplicity 5. Control

  43. 6. System Engineering • RAA • Definition of a system • Definition of a product engineer • Definition of a project manager • Definition of a system engineer 6. System engineering

  44. RAA • R -- Responsibility: Who is supposed to do the task • A -- Authority : Who has the authority to do the task • A -- Accountability : Who gets blamed if something goes wrong 6. System engineering

  45. Goal of RAA • The goal is to • Give authority to people who are responsible and accountable • Make people with authority responsible and accountable 6. System engineering

  46. Definition of a System • Definition used here • Each product is a system • Definitions used by others • System is the highest level product • System is the highest level product within a company or an enterprise 6. System engineering

  47. Definition of a Product Engineer • The person who has RAA for the product • Performs the roles of the project manager and the system engineer 6. System engineering

  48. Definition of a Project Manager • The person who has RAA for the product • Provides the environment to develop the product • Generally has a significant level of technical depth 6. System engineering

  49. Definition of a System Engineer (1 of 2) • Definition used here • The person who has RAA for the technical part of the product and the administrative duties associated with the technical part • Reports to project manager 6. System engineering

  50. Definition of a System Engineer (2 of 2) • Definitions used by others • Customer advocate and system auditor • Technical leader • Developer of the system front end • Requirements keeper 6. System engineering

More Related