Enterprise level projects tend to be delayed and to exceed budgets. Original expectations and targets are not met by these projects. Many solutions have been proposed to address this problem, one of them the application of Systems Engineering at large. In this paper we show how a compact Architecture Overview is a helpful instrument to keep enterprise level projects on track.
Practical experience shows that such an overview provides a quick insight in project progress and in potential threats. Principal customers and managers should ask the architects for this overview. Benefit for the architects of making the overview is that it helps to position their work in the enterprise context. Experience also shows that pragmatic system engineering practices, such as process orientation and project management are complementary to the proposed overview. This combination of overview and pragmatic systems engineering is very powerful.
One of the main issues in creating an architecture overview is the need for breadth, what needs to be included and for whom, and the balancing act of providing sufficient depth, what are crucial details that are part of this top-level description. Also the way of describing is discussed, from stakeholder needs to ambiguity and the level of formalism.
[1]
Derek K. Hitchins,et al.
Putting Systems to Work
,
1993
.
[2]
Jongmoon Baik,et al.
An empirical study of modifying the Fagan inspection process and the resulting main effects and interaction effects among defects found, effort required, rate of preparation and inspection, number of team members and product 1st pass quality
,
2002,
27th Annual NASA Goddard/IEEE Software Engineering Workshop, 2002. Proceedings..
[3]
Koen Arnoldus Wilhelmus Driessen,et al.
The FEI Small Dual Beam Product Family
,
2006
.
[4]
G. J. Muller,et al.
CAFCR: A Multi-view Method for Embedded Systems Architecting. Balancing Genericity and Specificity
,
2004
.
[5]
IEEE-SA Standards Board
,
2000
.