Bild 1 - bkcase

advertisement
SEBoK Part 3 Status, Structure
and Issues
Bud Lawson
Dave Olwell
Garry Roedler
12 April 2011
1
General Status
• Comments for all Knowledge Areas adjudicated
• Authors identified for KAs
– Some shortfalls – discussed in following charts
– Some additional authors identified, but need to be
reviewed and approved by Core Team
• Key terms and primary references for Part 3 have
been identified
– May need to prioritize further
– Challenge is getting to a concise set, but still being
meaningful considering size of Part 3
• Ready to move forward
– Writing for Version 0.5 has started for some KAs
12 April 2011
2
General Issues
•
How to take account of systems engineering practices with respect to the range of
applications; product, service, enterprise, and system-of-systems?
– Note: If the result of systems engineering is an instantiated product, service or
enterprise, what should we call the result of its application to a system-of-systems? –
Perhaps conglomerate, amalgamation (any ideas!!!)
•
•
•
•
•
•
How to deal with classifications of readiness: TRL (Technical Readiness Levels) and
SRL (System Readiness Levels)? Can SRL’s be used for soft systems like services
and enterprises or even SoS? (Stress tests for Nuclear Reactors and their
operation is certainly actual now). Perhaps this can be used in SRL evaluation.
Can we identify a set of patterns of systems engineering practice and how should
this be discussed in the various KAs.
Improvement of the discussion of Change Management and its affects upon Life
Cycle Management and the other KAs.
Discussion of product line SE and Management. Should a discussion on service
line also be considered?
Many comments address software-specific issues.
Requests to expand the text
– The challenge is to keep the discussion concise while expanding the scope
– Clarification needed in some cases
•
Structure, prescription, level of detail, survey of industry practices for each topic
12 April 2011
3
Structure
• Content within Knowledge Areas/Topics for consistency
– Items to be included in each Knowledge Areas (aka chapters)
(Required unless approved by Part Leaders)
•
•
•
•
•
•
•
Introduction
Fundamentals (if applicable)
SE Topics
Practical Considerations
Primary References
Additional References and Readings
Glossary
– Items to be included in each SE topic
applicable – please discuss any changes with Part Leaders)
•
•
•
•
•
•
•
12 April 2011
(Follow as
Introduction
Process Overview
Application to Product Systems
Application to Service Systems
Application to Enterprises
Linkages to other topics
Practical Considerations (Pitfalls, Good Practice, etc.)
Note: Team realizes that the application to Products, Services, and Enterprises
4
may vary by topic
1. ENTERPRISE KNOWLEDGE AREA
(James, Hillary) Formerly Part of Chapter 6
1. ENTERPRISE KNOWLEDGE AREA
1.1 Introduction/Overview
1.2 Enterprise Systems Engineering
1.3 ESE Process Activities
1.4 Enterprise Capability Management
1.5 Practical Considerations
1.6 Primary References
1.7 Additional References and
Readings
1.8 Glossary
12 April 2011
Comments/Issues:
• No specific issues
identified
5
2. LIFE CYCLE MODELS KNOWLEDGE AREA
(Kevin, Barry, Alain, Bud) Formerly Chapter 4
2. LIFE CYCLE MODELS KNOWLEDGE
AREA
2.1 Introduction/Overview
2.2 Life Cycle Characteristics
2.3 System Life Cycle Process Drivers
and Choices
2.4 Representative System Life Cycle
Process Models
2.5 Practical Considerations
2.6 Primary References
2.7 Additional References and Readings
2.8 Glossary
12 April 2011
Comments/Issues:
• Deploy Products,
Transition Services – UK
•
•
• Is there a single term
we could use?
Requests to expand the text
• The challenge is to
keep the discussion
concise while
expanding the scope
• Clarification needed in
some cases
The need for the SEBOK to
provide effective guidance
on handling “brown field”
systems engineering
6
challenges
3. SYSTEM DEFINITION KNOWLEDGE AREA
(Alain, Garry) Formerly Chapter 9
3. SYSTEM DEFINITION KNOWLEDGE
AREA
3.1 Introduction/Overview
3.2 Fundamentals
3.3 Stakeholders Requirements
3.4 System Requirements
3.5 Architectural Design
3.6 System Analysis
3.7 Practical Considerations
3.8 Primary References
3.9 Additional References and Readings
3.10
Glossary
Comments/Issues:
•
•
•
•
•
•
Any other BKCASE
authors?
Add an architecture
subject matter expert?
No mention of ISO/IEC
42010
•
•
12 April 2011
Additional authors needed
Should consider getting
someone from WG42,
maybe Johan Bendz
Some comments are very
SW engineering oriented
Some topics should be
added and may need help
Need expanded set of
references
7
4. REALIZATION KNOWLEDGE AREA
(John, Alain, Jean-Claude) Formerly Chapter 10
4. REALIZATION KNOWLEDGE AREA
4.1 Introduction/Overview
4.2 Fundamentals
4.3 Implementation
4.4 System Integration
4.5 System Verification
4.6 System Validation
4.7 Practical Considerations
4.8 Primary References
4.9 Additional References and Readings
4.10
Glossary
12 April 2011
Comments/Issues:
• Need author from a nondefense/aero sector
• Should consider an
author from ISO/IEC SI
and/or V&V studies
• Several technical issues
to resolve – see details
in Word file
• Use of “should”
• Reuse of subsystems
• Implementation
• System Integration
scope and definition
8
5. DEPLOYMENT AND USE KNOWLEDGE AREA
(Brian Gallagher) Formerly Chapter 11
5. DEPLOYMENT AND USE
KNOWLEDGE AREA
5.1 Introduction/Overview
5.2 Fundamentals
5.3 System Deployment
5.4 Operation of the System
5.5 System Maintenance
5.6 Logistics
5.7 Practical Considerations
5.8 Primary References
5.9 Additional References and Readings
5.10
Glossary
12 April 2011
Comments/Issues:
• Any authors from the
following areas?
• Operations and
Maintenance
• Logistics and Support
• Ensure single coverage
of Maintenance vs.
Upgrade (KA 3.7?)
9
6. SYSTEMS ENGINEERING MANAGEMENT KA
(Ray, Garry, Barry, Kevin, Ed, Ken) Formerly Chapter 8
6. SYSTEMS ENGINEERING MANAGEMENT
KNOWLEDGE AREA
6.1 Introduction/Overview
6.2 Planning
6.3 Assessment and Control
6.4 Risk Management
6.5 Measurement
6.6 Decision Management
6.7 Configuration Management
6.8 Information Management
6.9 Quality Management (from old chapter 14)
6.10
Primary References
6.11Additional References and Readings
6.12
Glossary
12 April 2011
Comments/Issues:
• Need Quality Mgt subject
matter expert
• Resolution of comments
regarding “Opportunity
Management”
• Need to reduce
prescription and tutorial
level content
10
7. PRODUCT AND SERVICE LIFE MGT KA
(Brian, Raytheon people) Formerly Chapter 12
7. PRODUCT AND SERVICE LIFE
MANAGEMENT KNOWLEDGE
AREA
7.1 Introduction/Overview
7.2 Fundamentals
7.3 Service Life Extension
7.4 Capability Updates, Upgrades, and
Modernization
7.5 Disposal and Retirement
7.6 Practical Considerations
7.7 Primary References
7.8 Additional References and Readings
7.9 Glossary
12 April 2011
Comments/Issues:
• Need author(s) from nondefense/aero sectors
•
•
•
Planning for system life
management during the
requirement phase
Managing service life
extension using the
Engineering Change
Management process with
an understanding of design
life constraints
Performing Legacy system
upgrades with attention to
legacy requirements and
key system interfaces
11
8. SPECIALTY ENGINEERING KNOWLEDGE AREA
(Cihan, ??) Formerly Chapter 14
8. SPECIALTY ENGINEERING KNOWLEDGE AREA (NEED TO PRIORITIZE AREAS)
•
8.1
Introduction/Overview
•
8.2
Integration of Specialty Engineering
•
(Affordability/Design to Cost - ( MOVE TO SYSTEMS ANALYSIS????))
•
8.3
Human System Integration – (SHOULD THIS BE HUMAN FACTORS??)
•
8.4
Dependability
–
–
–
–
•
•
8.5
8.6
–
–
–
•
8.7
–
•
•
•
•
•
•
Safety (PERHAPS A CATEGORY OF DEPENDABILITY – WITH SUBTOPICS)
Reliability and Maintainability
Availability (NEW)
Reslliance
Security
Aspects of Physical Products
Spectrum Management
Electro-Magnetic Interference/ TEMPEST
Radiation Hardness
Manufacturing and Production
(Quality – MMOVE TO CHAPTER 6 SYSTEMS ENGINEERING MANAGEMENT)
(Logistics/Supportability –ADDRESS IN CHAPTER 5)
8.8
Occupational Health/ Work Environment
(Disposal–ADDRESS IN CHAPTER 5)
8.9
Practical Considerations
8.10 Primary References
8.11 Additional References and Readings
8.12 Glossary
12 April 2011
Comments/Issues:
• Need more discussion
on structure and
content for this KA
• Need more diverse
set of authors
• Relationship to
Product, Service and
Enterprise systems?
12
9. SYSTEM OF SYSTEMS KNOWLEDGE AREA
(Mike Henshaw) New Knowledge Area
9. SYSTEM OF SYSTEMS
KNOWLEDGE AREA
9.1 Introduction//Overview
9.2 xxx
…
9.w Practical Considerations
9.x Primary References
9.y Additional References and Readings
9.z Glossary
Comments/Issues:
•
•
•
•
•
•
•
•
12 April 2011
Need more diverse set of
authors – the following have
confirmed interest and
commitment:
Mo Jamshidi
Dan DeLaurentis
Judith Dahmann
Charles Dickerson
Types of SoS – virtual,
collaborative,
acknowledged, directed
Emergence – definition,
prediction
SoS Evolution –
asynchronous lifecycles,
safety qualification,
13
capability concepts
Download