Functional software architecture: Difference between revisions

Revision as of 12:27, 27 April 2005

Revision as of 12:32, 27 April 2005

Line 19:

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 Processprocess Reengineeringreengineering]] (Fredrick Taylor), [[MarketProduct Analysissoftware market analysis]], [[Requirements Analysisanalysis]] 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: