Functional software architecture: Difference between revisions

Revision as of 18:17, 25 May 2007

Revision as of 18:18, 25 May 2007

Line 21:

This definition emphasizes the use of the architecture as a rich strategic information source for the improvement of business processes and development of needed information systems. If defined, maintained, and implemented effectively, these institutional blueprint assist in optimizing the interdependencies and interrelationships among an organizations business operations and the underlying IT that support operations.

Having read the definition of a Functional Software Architecture at the beginning of this entry we can see a Functional Software Architecture as a type of Enterprise Architecture that can be used as a rich reference for the development of an integrated information system. Naming it a Functional Software Architecture encourages practitioners to use it as a strategic input for a [[technical architecture]]. A formal mapping between a Functional Software Architecture and a type of [[Architecture Descriptiondescription Languagelanguage|ADL]] is therefore needed. In this way the formal use and reuse of enterprise architectures as strategic input for software architectures can be realized.

==Development of a FSA==