Content deleted Content added
Line 18:
Off course the described work division is in reality much more complex and also involves more actors but it outlines the involvement of people with different backgrounds in creating a software system that enables the organization to reach business objectives. A wide variety of material produced by different actors within this system development process needs to be exchanged between and understand by multiple actors.
Especially in the field of software engineering much tools (A4 Tool, CAME, ARIS) languages (ACME, Rapide, [[UML]]) and methods ([[DSDM]], [[RUP]], [[ISPL]]) are developed and extensively used. Also, the transition between the software engineers (step 3) and computer programmers (step 4) is already highly formalized by for instance [[object-oriented]] development and corresponding [[Java programming]].
Setting strategic objectives (step 1) and the corresponding search for [[business]] opportunities and weaknesses is a subject extensively discussed and investigated for more than hundred years. Concepts like for instance [[Business process reengineering]] (Fredrick Taylor), [[Product software market analysis]], [[Requirements analysis]] are commonly known and extensively used in this context. These strategic inputs must be used for the development of a good enterprise design (step2), which can then be used for software design and implementation respectively.
Recent studies have shown that these enterprise architectures can be developed by a number of different methods and techniques. Before these methods and techniques are discussed in detail a definition of an [[Enterprise architecture]] is given:
| |||