Академический Документы
Профессиональный Документы
Культура Документы
concept Utilization
Support/
evolution
Development
Retirement
Production
System Life Cycle
21/2/06 Setyo U. Soekarsono 2
Traditional VS Concurrent
21/2/06 Note:
IPDT = Integrated Product Setyo U. Soekarsono
Development Team 3
Why should we use SE? The Benefits
Specific benefits:
Shorter product development cycle time (reduce by 60%)
Engineering change orders reduced by 50%
Redesign and rework effort reduced by as much as 75%
Manufacturing costs reduced by as much as 40%
Overall save 10 – 20% of the project budget
• General benefits
– Reduced non-recurring costs
– Reduced life cycle costs
– A more competitive product
– A process that is compliant with the expectations and
requirements of external customers
21/2/06 Setyo U. Soekarsono 4
James Martin, Systems Engineering Guidebook, 1997
Why should we use SE? The Benefits
URD &
OTHER
STAKESHOLDER
REQTS SEMP
SEMS
SEDS
• RFP
• CONTRACT A/B SPECS
• PROGRAM C/D/E SPECS
PLAN SSDD
• COST
OBJECTIVES ICD
• MARKETING TRS
INFO
PRODUCT CHARACTERISTICS
MGMT DIRECTION & REPORTING
Component
Component Design
Integration & Test
Component
Engineering
Procure, Fabricate, & Domain
Assemble Parts
• What needs are we trying to fill?
•• Focus
Focusof
ofSystems
Systems
Need • What is wrong with the current situation?
• Is the need clearly articulated?
Engineering
Engineering • Who are the intended users?
–– From
FromOriginal
OriginalNeed
Need • How will they use our products?
Operations Concept • How is this different from the present?
–– To
ToFinal
FinalProduct
Product
• What specific capability will we provide?
•• The
TheWhole
Whole • To what level of detail?
System
System Functional Requirements• Are element interfaces well defined?
•• The
TheFull
FullSystem
System • What is the overall plan of attack?
Life Cycle
Life Cycle
• What elements make up the overall approach?
• Are these complete, logical, and consistent?
System Architecture
• Which elements address which requirements?
• Is the allocation appropriate?
• Are there any unnecessary requirements?
Allocated Requirements
• Are the details correct?
• Do they meet the requirements?
• Are the interfaces satisfied?
••Focus Detailed Design
FocusofofComponent
Component • Will the solution be satisfactory in terms
Engineering
Engineering of cost and schedule?
• Can we reuse existing pieces?
•• On
OnDetailed
DetailedDesign
Design Implementation • What is our evidence of success?
•• And
AndImplementation
Implementation • Will the customer be happy?
• Will the users’ needs be met?
Customer Maintenance
Reqts Reqts
Context use
Reqts Reqts
System Deployment
Reqts Reqts
Development Verification
Reqts Reqts
Fabrication/ Assembly//
Procurement Integration
Reqts Reqts
Flowdown of Reqts from Stakeholders
User Stakeholders
Provide
Provide
User Stakeholder
Reqts Reqts
Flowdown to
Flowdown to
System Flowdown to
Reqts
Flowdown to Task
Reqts
Design - to Provided to
Provided to
Reqts
Flowdown to
Task
Build- to Performers
Reqts
Provided to
Product/
BUILDERS
Service