The System Engineering Hierarchy

Regardless of its domain of focus system engineering encompasses a group of bottom- up and top-down techniques to navigate the hierarchy description in Figure 12.2. The system engineering procedure usually a start with a world view which is the entire business of product domain is examined to ensure that the proper technology or business context develop. The world view is refined to focus more entire on specific domain of interest. In a specific domain the requirement for targeted system elements example for software, data, hardware, and people is analyzed. In the final stage the construction and analysis design of a targeted system element is initiated. On the top of the hierarchy a very wide context is developed and at the bottom detailed technical activities performed through the relevant engineering discipline example for software or hardware engineering are conducted.

Beginning in a slightly more formal manner the world view (WV) is composed of a group of systems in its own right.

WV={D1,D2,D3....Dn}

Every domain is composed of exact elements (Ej) every of that serves some role in accomplishing the target and objective of the domain:

Di={E1,E2,E3....Em}

at last each  element  is  implemented  through  specifying  the  technical  components(Ck)  which  achieve  the necessary function for an element.

Ej={C1,C2,C3....Ck}

In the software circumstance a component could be a computer program a module a reusable program component and class or object or even a programming language statement.

It is important to note in which the system engineer narrows the focus of work as she or he moves downward in the hierarchy define above. Moreover the world view portrays a clear definition of overall functionality which will enable the engineer to understand the ultimately and domain the product or system in the proper circumstance.