Content deleted Content added
rm "notice of originality" - not WP:STYLE |
rm ---- lines |
||
Line 21:
Having red 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 enforces practitioners to use it as a strategic input for a [[Technical architecture]]. A formal mapping between a Functional Software Architecture and a type of ADL is thereby 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==
Line 39 ⟶ 38:
Figure 1 shows at the top-level the “Enterprise Engineering” field;
Optimizing the internal and external business processes through process reengineering is one of the main objectives an enterprise can have in times of high external pressure. A [[business process]] involves value creating activities with certain inputs and outputs, which are interconnected and thereby jointly contribute to the final outcome (product or service) of the process. Process reengineering covers a variety of perspectives of how to change the organization. It is concerned with the redesign of strategic, value adding processes, systems, policies and organizational structures to optimize the processes of an organization [2]. This paper considers process (re)engineering as part of the broader enterprise engineering field.
==Modeling the business==
Line 111 ⟶ 107:
So, maybe EFD could be used as a business front-end to a software modeling language like UML. The major resemblance with IDEF as a modeling tool indicates that it can be done. However, more research is needed to improve the EFD technique in such a way that formal mappings to UML can be made (see dashed line figure 1). Work of Kim et. al. [1] about the complementary use of IDEF and UML has contributed to the acceptance of IDEF as business-front end. A similar study should be done with EFD and UML.
==Conclusion==
Line 135 ⟶ 129:
The dotted box shows which business function is decomposed into sub-functions in order to reveal detailed information needs and come up with a software design. At this detailed level a mapping to Petri Nets or UML-diagrams should result in a rich software design. In this way a developed information system is set into a wider enterprise context. However, further research, like that of Kim et. al (2002), is needed to show this mapping can actually be done.
==References==
| |||