1. PBDA1 Agenda for introduction q1. Course details q2. Disclaimer q3. Reasons why systems fail q4....
-
Upload
sophie-palmer -
Category
Documents
-
view
215 -
download
1
Transcript of 1. PBDA1 Agenda for introduction q1. Course details q2. Disclaimer q3. Reasons why systems fail q4....
1. PBDA 1
Agenda for introduction1. Course details2. Disclaimer3. Reasons why systems fail4. Products5. Cycles, phases, and activities6. PBDA
1. PBDA 2
1. Course details
Course and instructorCourse contentTextbook and timeScheduleGradingFormats
1. Course details
1. PBDA 3
Course and instructorCourse -- 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 -- [email protected]
1. Course details
1. PBDA 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
1. PBDA 5
Textbook and time
Textbook -- noneClass time -- 7:15 - 9:15
1. Course details
1. PBDA 6
ScheduleMay 29 -- IntroductionJune 3, 5 -- DesignJune 10, 12 -- IdeasJune 17, 19 -- ExamplesJune 24, 26, July 1 -- MathJuly 3 -- ProjectJuly 8, 10, 15 -- MathJuly 17 -- SystemJuly 22 -- SoftwareJuly 24 -- HardwareJuly 29 -- Final
1. Course details
1. PBDA 7
Grading
Project -- 50%Final -- 50%
1. Course details
1. PBDA 8
FormatsNon-electronic: Pencil and paperElectronic: Office 97 Word, Excel, PowerPoint PC and not Macintosh
1. Course details
1. PBDA 9
2. DisclaimerDesign is more of an art than a science.Almost any approach to design will work if
someone takes ownership of successNo one approach is better than all the othersWe will use the approach used in the
Systems Engineering Process course
2. Disclaimer
1. PBDA 10
3. Reasons systems failafter
deliverybefore
delivery
lack of qualified people
unmanaged risks
wrong requirements
failure toexecute
other
didn’t meetrequirements
overlookedsomething
failed to impresscustomer
3. Reasons systems fail
1. PBDA 11
4. Products
Product definitionProducts composed of productsTypes of productsNeed for productsNeed for lower-level productsExamples
4. Products
1. PBDA 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
1. PBDA 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
1. PBDA 14
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
4. Products
1. PBDA 15
Types of products (1 of 2)
Level N Product
DeliverableProducts
EnvironmentProducts
EngineeringProducts
Products can be divided into three types of products -- delivered products, environment products, and
engineering products.
Products can be divided into three types of products -- delivered products, environment products, and
engineering products.
4. Products
1. PBDA 16
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
Types of products (2 of 2)
4. Products
1. PBDA 17
Need for products
We need products to describe what we’re controlling
Products may be developed or procured without development
4. Products
1. PBDA 18
Need for lower-level productsWe need lower-level products if we’re
going to procure something needed for doing the development
4. Products
1. PBDA 19
Good example -- We can use the lower-level products to make the higher-level product
Good example -- We can use the lower-level products to make the higher-level product
Example 1 -- model airplane
Model airplane
Fuselage Wing Stabilizer Rudder Glue
4. Products
1. PBDA 20
Bad example -- We wouldn’t use the lower-level products to make the higher-level product
Bad example -- We wouldn’t use the lower-level products to make the higher-level product
House
Kitchen Bathroom Bedroom 1 Bedroom 2 Garage
Example 2 -- house, bad example
4. Products
1. PBDA 21
Good example -- We can use the lower-level products to make the higher-level product
Good example -- We can use the lower-level products to make the higher-level product
Example 3 -- house, good example
House
Plumbing Framing Roof ElectricalFoundation Dry wall
4. Products
1. PBDA 22
5. Cycles, phases, and activities
DefinitionsProduct life cyclePre-develop-phase activitiesDevelop-phase activitiesPost-develop-phase activitiesExample
5. Cycles, phases, and activities
1. PBDA 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 tasksProcess -- steps used to accomplish an
activity
5. Cycles, phases, and activities
1. PBDA 24
Product life cycle
Phases
Time
Pre-develop
Post-develop
Develop
5. Cycles, phases, and activities
1. PBDA 25
Pre-develop-phase activities
Sub phasesor activities
Time
Meet the customer
Discuss the work
Respond to RFP
Sub phases overlap
Identify opportunity
5. Cycles, phases, and activities
1. PBDA 26
Develop-phase activitiesSub-phasesor activities
Time
Understand requirements
Design
Acquire products
Build
Verify
Sell off
Sub-phases overlap
Manage
5. Cycles, phases, and activities
1. PBDA 27
Post-develop-phase activitiesSub-phases
Time
Train
Produce
Upgrade
Maintain
Operate
Dispose
Sub-phases overlapField test and validate
Support
5. Cycles, phases, and activities
1. PBDA 28
Example -- build a houseActivities
Time
Learn what buyer wants
Have architect make blueprint
Get land and lumber
Build
See if the house is OK
Close
Supervise
5. Cycles, phases, and activities
1. PBDA 29
6. PBDAApproachPBDA block diagramApplication of PBDA to productsExampleWork products (WPs)
6. PBDA
1. PBDA 30
The approachDetermine 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
Approach consists of applying these seven activities to each product in the
system
Approach consists of applying these seven activities to each product in the
system
1. PBDA 31
PBDA block diagram
1. Manage
2. Understand req
3. Design
4. Acquire
5. Build6. Verify
7. Sell off
External: higher product teams
External: lower product teams
contracts,specs,interfaces
specs, I/Fscontracts
lower specs & I/Fs
design
lowercontracts,specs,interfaces
status
lower product,test results,
test spec agree
lower test results
lower products
build proc
product
test proc
test resultstest spec
people, facilities, tools, capital,
communications, library
schedule, budget,risks, TPPs, issues, AIs, plans, timeline, changes, problems, legal
control,status
agree
status
MR
RR
CR PDR CDR
TRR VR
FCA PCA
1. PBDA 32
Application of PBDA to products
Productof interest
Lowerproduct N
Higherproduct
Lowerproduct 1
Lowerproduct 2
PBDA is applied to each product separately
6. PBDA
1. PBDA 33
Example with 10 productsExample with 10 products
System
Subsystem Subsystem
HWCI HWCI Unit
CSCI
HWCI Unit
CSCI
Example (1 of 2)
6. PBDA
1. PBDA 34
Developing the example with 10 instantiations of PBDADeveloping the example with 10 instantiations of PBDA
1
2 3
6 7 8
9 10
5
Example (2 of 2)
6. PBDA
1. 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
6. PBDA
PBDA executed by completing WPsPBDA executed by completing WPs
1. 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. 26 WPs used for managing each product in PBDA.
6. PBDA
1. 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. 10 WPs used for developing each product in PBDA.
6. PBDA
1. 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
Inputs are monitored but aren’t WPs of the product of interest
6. PBDA
1. 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 usedNot all WPs must always be used
6. PBDA
1. PBDA 40
WPs (6 of 6)
An example pareto of WPs by likely useAn example pareto of WPs by likely use6. PBDA
decreasing likelihood of use
product (1)
lower products (1)
higher inputs (3)
budget & schedule (2)
environment (6)
design (3)
build proc (1)
problems and changes (2)
risks & TPPs (2)
verify (3)
plan and timeline (2)
lower inputs (3)
reviews and audits (9)
agreement (1)
acquire (1)
issues and AIs (2)
legal (1)
physical
paper
externalpaper