Difference between revisions of "Capability Engineering"
Wikiexpert (talk | contribs) |
|||
| Line 1: | Line 1: | ||
==Capability Engineering Perspectives== | ==Capability Engineering Perspectives== | ||
| − | The term [[Capability (glossary)]] is widely used across many industrial sectors and has begun to take on various specific meanings across, and even within, those sectors. | + | The term [[Capability (glossary)]] is widely used across many industrial sectors and has begun to take on various specific meanings across, and even within, those sectors. Terms such as capability-based acquisition, capability [[Engineering (glossary)]] and management, Through Life Capability Management, capability sponsor, etc. are now ubiquitous in defense and elsewhere. Henshaw et. al. (2011) have identified at least eight worldviews of capability and capability engineering and concluded that the task of capability engineering is not consistently defined across different communities. |
| − | + | Whilst most practitioners recognise that there is a strong relationship between capability and System of Systems, there is no agreed position. There are two widely held views: | |
| − | + | *A capability comprises a range of systems, processes, people, information and organisations. (i.e. a system at levels 3-5 in Hitchin's 5 layer model such as a Carrier-Strike capability) | |
| − | + | *The capability is an emergent property of system of systems. (i.e. the capability of Carrier-Strike to engage targets within 300 miles of the Sea) | |
| − | |||
| − | |||
| − | |||
| − | The | ||
==Services view of SoSE== | ==Services view of SoSE== | ||
Revision as of 23:15, 29 July 2012
Capability Engineering Perspectives
The term capability is widely used across many industrial sectors and has begun to take on various specific meanings across, and even within, those sectors. Terms such as capability-based acquisition, capability engineering and management, Through Life Capability Management, capability sponsor, etc. are now ubiquitous in defense and elsewhere. Henshaw et. al. (2011) have identified at least eight worldviews of capability and capability engineering and concluded that the task of capability engineering is not consistently defined across different communities.
Whilst most practitioners recognise that there is a strong relationship between capability and System of Systems, there is no agreed position. There are two widely held views:
- A capability comprises a range of systems, processes, people, information and organisations. (i.e. a system at levels 3-5 in Hitchin's 5 layer model such as a Carrier-Strike capability)
- The capability is an emergent property of system of systems. (i.e. the capability of Carrier-Strike to engage targets within 300 miles of the Sea)
Services view of SoSE
As has been discussed throughout the Systems of Systems (SoS) knowledge area, ‘system of systems’ is typically viewed from the viewpoint of bringing together multiple systems to provide broader capability. As is discussed in Architecting Approaches for Systems of Systems, the networking of the constituent systems in a SoS is often a key part of an SoS. In some circumstances, the entire content of an SoS is information and the SoS brings together multiple information systems to support the information needs of a broader community. These ‘information technology (IT) based’ SoSs have the same set of characteristics of other SoSs and face many of the same challenges. Current IT has adopted a ‘services’ view of this type of SoS, and increasingly apply a ‘service oriented architecture ’ approach to design and management (Erl 2008). This approach decouples the architectural approach from the implementation, defining the functions to be provided across the SoS in terms of ‘services’. This approach allows for evolution of the underlying technical approaches in the supporting systems while maintaining continuity in supporting the needs of users across the SoS. While most commonly applied to IT based SoS, this services conceptualization of SoS can be applied to SoS of all types.
References
Works Cited
Erl, T. 2008. "SOA Principles of Service Design." Boston, MA, USA: Prentice Hall Pearson Education. ISBN 978-0-13234-482-1.
Primary References
Henshaw, M., D. Kemp, P. Lister, A. Daw, A. Harding, A. Farncombe, and M. Touchin. 2011. "Capability Engineering - An Analysis of Perspectives." Presented at International Council on Systems Engineering (INCOSE) 21st International Symposium, 20-23 June 2011. Denver, US.
- Output of the INCOSE UK Capability Working Group includes an in-depth analysis of capability engineering and its relationship to systems engineering.
Additional References
No additional references have been identified for version 0.75. Please provide any recommendations on additional references in your review.
SEBoK Discussion
Please provide your comments and feedback on the SEBoK below. You will need to log in to DISQUS using an existing account (e.g. Yahoo, Google, Facebook, Twitter, etc.) or create a DISQUS account. Simply type your comment in the text field below and DISQUS will guide you through the login or registration steps. Feedback will be archived and used for future updates to the SEBoK. If you provided a comment that is no longer listed, that comment has been adjudicated. You can view adjudication for comments submitted prior to SEBoK v. 1.0 at SEBoK Review and Adjudication. Later comments are addressed and changes are summarized in the Letter from the Editor and Acknowledgements and Release History.
If you would like to provide edits on this article, recommend new content, or make comments on the SEBoK as a whole, please see the SEBoK Sandbox.
blog comments powered by Disqus