Functional software architecture: Difference between revisions

Revision as of 15:00, 31 March 2005

Revision as of 15:08, 31 March 2005

Line 1:

A '''Functional Software Architecture''' (FSA) is an architectural model that identifies [[enterprise]] functions, interactions and corresponding [[IT]] needs, which can be used as reference by different ___domain experts to develop IT-systems as part of a co-operative information-driven enterprise. In this way both [[software engineers]] and enterprise engineers are able to create an information-driven, integrated organizational environment.

As the boundary of an enterprise is extended, it becomes increasingly important that a common “big picture” of needed [[business]], people and IT system activities is developed and shared by all the parties involved [1]. A Functional Software Architecture does this by breaking down the organisation in business functions and corresponding IT needs. In this way the enterprise engineer provides a rich schematic reference that can be used by the software engineer in the development of these IT-systems.

==Development of a FSA==

The development of a Functional Software Architecture can be done by a number of (combined) methods[[method]]s and techniques. Figure 1 outlines the methods and techniques that will be discussed in this paper. Filling in the “gab” between the enterprise engineers and software engineers through the use of different combinations of methods and techniques will be the main objective of this paper. However, this objective can only be reached when combined methods result in clear and rich Functional Software Architectures that are developed and used by both parties.

[[Image:FSA-network.PNG]]