2016
DOI: 10.1002/sys.21359
|View full text |Cite
|
Sign up to set email alerts
|

Complexity in a Systems Engineering Organization: An Empirical Case Study

Abstract: General rightsThis document is made available in accordance with publisher policies. Please cite only the published version using the reference above. Full terms of use are available:

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1

Citation Types

0
2
0

Year Published

2019
2019
2024
2024

Publication Types

Select...
6

Relationship

0
6

Authors

Journals

citations
Cited by 7 publications
(2 citation statements)
references
References 20 publications
0
2
0
Order By: Relevance
“…Moreover, what counts as a reasonable approach to defining system complexity depends on what type of system of interest (SoI) is being considered; is it limited to the technical system(s) being developed and deployed , or does it also include the systems of processes and resources that are involved in developing and deploying such technical systems ? 35 Is the project that strives to realize the system under consideration? 36–39 Does it include the processes of utilizing the system once deployed or the user's perceptions of how complex the system is (e.g., how familiar users of the system are with important features of the system)? 40,41 What is the boundary of the SoI; is it the physical context of the implemented system or does it also include the more extended strategic/business context? 42–46 While several approaches purport to provide a quantitative measure of the complexity of a system, they more realistically provide a quantitative measure of the complexity of a particular representation of a system (i.e., a particular view on the architecture of a system) 25,26,47–50 . A distinction is also required between the complexity of a representation of a system (i.e., the structural complexity of a system architecture) and the qualitative perceived and observer‐dependent complexity of the system 25,26,40 .…”
Section: Literature Reviewmentioning
confidence: 99%
“…Moreover, what counts as a reasonable approach to defining system complexity depends on what type of system of interest (SoI) is being considered; is it limited to the technical system(s) being developed and deployed , or does it also include the systems of processes and resources that are involved in developing and deploying such technical systems ? 35 Is the project that strives to realize the system under consideration? 36–39 Does it include the processes of utilizing the system once deployed or the user's perceptions of how complex the system is (e.g., how familiar users of the system are with important features of the system)? 40,41 What is the boundary of the SoI; is it the physical context of the implemented system or does it also include the more extended strategic/business context? 42–46 While several approaches purport to provide a quantitative measure of the complexity of a system, they more realistically provide a quantitative measure of the complexity of a particular representation of a system (i.e., a particular view on the architecture of a system) 25,26,47–50 . A distinction is also required between the complexity of a representation of a system (i.e., the structural complexity of a system architecture) and the qualitative perceived and observer‐dependent complexity of the system 25,26,40 .…”
Section: Literature Reviewmentioning
confidence: 99%
“…Wildly divergent definitions of "complexity" have emerged; it has no singular meaning [8,9]. Applying such a broad topic as complexity to the equally common topic of Systems Engineering is extremely difficult [10].…”
Section: Complexitymentioning
confidence: 99%