Editing Systems engineering (section)

===Managing complexity===
The need for systems engineering arose with the increase in complexity of systems and projects, in turn exponentially increasing the possibility of component friction, and therefore the unreliability of the design. When speaking in this context, complexity incorporates not only engineering systems but also the logical human organization of data. At the same time, a system can become more complex due to an increase in size as well as with an increase in the amount of data, variables, or the number of fields that are involved in the design. The [[International Space Station]] is an example of such a system.

[[File:STS-134 International Space Station after undocking.jpg|thumb|The [[International Space Station]] is an example of a very complex system requiring systems engineering.]]

The development of smarter control [[algorithms]], [[microprocessor design]], and [[Environmental systems analysis|analysis of environmental systems]] also come within the purview of systems engineering. Systems engineering encourages the use of tools and methods to better comprehend and manage complexity in systems. Some examples of these tools can be seen here:<ref>{{cite web|url=http://systemseng.cornell.edu/CourseList.html|title=Core Courses, Systems Analysis&nbsp;– Architecture, Behavior and Optimization|publisher=Cornell University|access-date=25 May 2007}}</ref>
* ''[[System architecture]]''
* ''[[System model]], [[Scientific modelling|modeling]], and [[simulation]]''
* ''[[Mathematical optimization]]''
* ''[[System dynamics]]''
* ''[[Systems analysis]]''
* ''[[Statistical analysis]]''
* ''[[Reliability engineering]]''
* ''[[Decision making]]''

Taking an [[interdisciplinary]] approach to engineering systems is inherently complex since the [[behavior]] of and interaction among system components is not always immediately [[well defined]] or understood. Defining and characterizing such [[system]]s and subsystems and the interactions among them is one of the goals of systems engineering. In doing so, the gap that exists between informal requirements from users, [[Sysop|operator]]s, [[marketing]] organizations, and [[technical specifications]] is successfully bridged.