Content deleted Content added
Ketiltrout (talk | contribs) m dab |
|||
Line 25:
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 description language|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
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.<ref name="Kim">Kim & Weston & Hodgson & Lee (2002); The complementary use of IDEF and UML. Information system engineering, Deajon University South Korea, Computers & Industrial Engineering 50, 35–56.</ref> A functional software architecture does this by breaking down the organization 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.
| |||