Content deleted Content added
No edit summary |
|||
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.
When an integrated software system needs to be developed and implemented normally a number of tasks and corresponding responsibilities can be divided:
##Strategic management and business consultants set objectives in relation to a more efficient/ effective business process.
##Enterprise engineers come up with a design of a more efficient business process and a request for a certain information system in the form of an Enterprise Architecture.
##Software engineers come up with the design of this information system, which describes the components and structural features of the system by use of a certain Architecture Description Language (ADL).
##Computer programmers code the different modules and actually implement the system.
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.
| |||