1. Introduction1 Agenda for Introduction q1. Course details q2. Basic approach q3. Products q4....
57
. Introduction 1 Agenda for Introduction 1. Course details 2. Basic approach 3. Products 4. Cycles, phases, and activities 5. Control 6. System engineering 7. Homework
-
Upload
leslie-king -
Category
Documents
-
view
215 -
download
0
Transcript of 1. Introduction1 Agenda for Introduction q1. Course details q2. Basic approach q3. Products q4....
1. Introduction 1
Agenda for Introduction
1. Course details 2. Basic approach 3. Products 4. Cycles, phases, and activities 5. Control 6. System engineering 7. Homework
1. Introduction 2
1. Course Details
Course and instructor Course description Textbook and time Schedule Grading Formats
1. Course details
1. Introduction 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 -- [email protected]
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
1. Introduction 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
1. Introduction 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
1. Introduction 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
1. Introduction 7
Grading
Homework 35% Project
30% Final 35%
1. Course details
1. Introduction 8
Formats
Non-electronic: Pencil and paper Electronic: Office 97 Word, Excel, PowerPoint PC and not Macintosh
1. Course details
1. Introduction 9
2. Basic Approach
System engineering Guideline Activities Application
2. Basic approach
1. Introduction 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
1. Introduction 11
Guidelines
Wisdom Simplicity
2. Basic approach
1. Introduction 12
Activities
Determine what customer wants
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
Make it happen
2. Basic approach
1. Introduction 13
Application
Apply same set of activities to each task
2. Basic approach
1. Introduction 14
3. Products
Product definition Products composed of products Examples Need for lower-level products
3. Products
1. Introduction 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
1. Introduction 16
Products Composed of Products
Level 1 Product
Level 2 Product 1
Level 2 Product 2
Level 3 Product 1
Level 3 Product 2
Level 4 Product 2
Higher-level products
Lower-level products
Level 4 Product 1
Level 4 Product 3
3. Products
1. Introduction 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
1. Introduction 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
1. Introduction 19
House
Kitchen Bathroom Bedroom 1 Bedroom 2 Garage
Bad example -- We wouldn’t use the lower-level products to make the higher-level product
Example 2 -- House
3. Products
1. Introduction 20
Example 3 -- House
House
Plumbing Framing Roof Electrical
Good example -- We can use the lower-level products to make the higher-level product
Foundation Dry wall
3. Products
1. Introduction 21
4. Cycles, Phases, and Activities
Definitions of cycles, phases and activities Product life cycle Example Notes on activities
4. Cycles, phases, and activities
1. Introduction 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
1. Introduction 23
Product Life Cycle
Phases
Time
Pre-develop
Post-develop
Develop
4. Cycles, phases, and activities
1. Introduction 24
Develop Phase Activities (1 of 2)
Determine what customer wants
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
Make it happen
Manage
Understand requirements
Design
Acquire products
Build
Verify
Sell-off
4. Cycles, phases, and activities
1. Introduction 25
Develop Phase Activities (2 of 2)
Sub phases
Time
Understand requirements
Design
Acquire products
Build
Verify
Sell off
Sub phases overlap
Manage
4. Cycles, phases, and activities
1. Introduction 26
Post-Develop Activities
Sub-phases
Time
Train
Produce
Upgrade
Maintain
Operate
Dispose
Sub phases overlapField test and validate
Support
4. Cycles, phases, and activities
1. Introduction 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
1. Introduction 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
1. Introduction 29
Example -- Build a House
Activities
Time
Learn what buyer wants
Have architect make blueprint
Get land and lumber
Build
See if the house is OK
Close
Supervise
4. Cycles, phases, and activities
1. Introduction 30
5. Control
Classes of products Product-based activities Product-based context Control by use of management objects
5. Control
1. Introduction 31
Classes of Products (1 of 2)
Level N Product
DeliverableProducts
EnvironmentProducts
EngineeringProducts
5. Control
1. Introduction 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
1. Introduction 33
Control Using Engineering Products
Development and environment
products
Engineering products
Activities
Activities and engineering
products are used to develop development
and environment products
5. Control
1. Introduction 34
Alternate View of Control by Products
Activities and engineering
products
Development products
Environment products
Product
Level N+1 Level N
Note: EIA 632 refers to environment and engineering products as enabling products
5. Control
1. Introduction 35
Product-Based Development ActivitiesExternal: Higher Product Team
External: Lower Product Teams
2. Understand requirements
3. Design
4. Acquire
1. Manage
5. Build
6. Verify
7. Sell off
specinterfaces
lower specsinterfaces
SOWsspecsinterfaces
productstest results
test spec test results
lower test results product
lower products
SOW
SOWspecinterfaces
deliverablesagreement
producttest results
test spec
design
plansched & budget
reviews, risks, TPPsissues, prob, AIsconfig, changes
deliverablesagreements
plansscheds & budgets
reviews, risks, TPPsissues, probs, AIsconfigs, changes
facilitiestools, capital
communicationslibrary people
control & status
build proc
test proc
legal
FCA/PCA
TRR VR
PDR CDR
RR
MR
CR
5. Control
1. Introduction 36
Product-Based Context
HigherProduct
LowerProduct 1
LowerProduct 2
LowerProduct N
Productof Interest
Product-based activities are applied to each product separately
5. Control
1. Introduction 37
Example (1 of 2)
System
Subsystem Subsystem
HWCI HWCI Unit
CSCI
HWCI Unit
CSCI
5. Control
1. Introduction 38
Example (2 of 2)
Developing the system employs 10 instantiations of the product-based development approach
1
2 3
6 7 8
9 10
5
1. Introduction 39
Optimizing Activities & Management Objects
Some management objects can be shared between levels
Not all management objects are needed at each level.
5. Control
1. Introduction 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
1. Introduction 41
Usefulness of Product Concept (2 of 2)
Makes explaining system engineering easier Allows these disciplines to be parallel rather
than randomly aligned
system engineering
software
supportability electrical engineering
maintainabilityconfiguration management
5. Control
1. Introduction 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
1. Introduction 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
1. Introduction 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
1. Introduction 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
1. Introduction 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
1. Introduction 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
1. Introduction 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
1. Introduction 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
1. Introduction 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
1. Introduction 51
Perception of a System Engineer
Perceptions of system engineer vary from technical leader to clerk
Not technical Role not understood by management
6. System engineering
1. Introduction 52
System Engineer as a Leader (1 of 2)
System engineer should lead the parade rather than clean up behind it
A problem the system engineer must overcome is being passed by the design, product acquisition, build, and verification activities
6. System engineering
1. Introduction 53
System Engineer as a Leader (2 of 2)
Leadership involves finding the leaders and being a leader among the leaders
Leadership involves finding the most active part of a project and leading at that point
A system engineer can become absorbed in processes to the point of abdicating leadership
6. System engineering
1. Introduction 54
7. Homework
Problem System spec tree
7. Homework
1. Introduction 55
Homework Problem (1 of 3)
1. In the following spec tree, how many design activities are there? -- a. 1, b. 3, c. 7, d. 10
2. Assuming that any two units or HWCIs in the same subsystem can have one interface between them and that they can not have an interface with another subsystem, how many interfaces are there among units and HWCIs? -- a. 3, b. 5, c. 10, d. 45
3. Is an interface a delivered product? a. yes, b. no, c. can be either
4. Which of the seven activities are involved in building a new house? -- a. all 7; b. 3 & 5; c. 1, 3, 5, 7; d. 5
7. Homework
1. Introduction 56
Homework Problem (2 of 3)
5. Which of the seven activities are involved in buying a pre-owned house? -- a. 1; b. 7; c. 1, 3, 5, 6, 7; d. none
6. Which of the seven activities are involved in completing an income tax 1040 form? -- a. 1; b. 6; c. 1, 3, 4, 5, 7; d. 4, 5, 6
7. Homework
1. Introduction 57
Homework Problem (3 of 3)
System
Subsystem Subsystem
HWCI HWCI Unit
CSCI
HWCI Unit
CSCI
Spec Tree
7. Homework
![[RTF] 12QQ Q43 5 Q6Q Q Q78Q1Q2 Q Q34 Q5 Q 6Q7Q8Q1Q2 Q3 4QQ5 6QQ 7Q8 Q R100 R 0 13Q R20Q4 Q5 R30 Q6 0R4 Q R705 Q R80 607 510 R14R 5 1Q ...](https://static.fdocuments.net/doc/165x107/5b479aa77f8b9a3a058c4985/rtf-12qq-q43-5-q6q-q-q78q1q2-q-q34-q5-q-6q7q8q1q2-q3-4qq5-6qq-7q8-q-r100-r-0-13q.jpg)