Content deleted Content added
No edit summary |
No edit summary |
||
Line 1:
'''Notice of Originality'''
I declare that this paper is my own work and that information derived from published or unpublished work of others has been acknowledged in the text and has been explicitly referred to in the list of references.
Name: Niels de Vrij
Date: 27-04-2005
Place: Utrecht, The Netherlands
==Introduction==
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.
Line 98 ⟶ 105:
EFD is a used modeling technique for the representation of enterprise functions and corresponding interactions. Different business processes can be modeled in these representations through the use of “function modules” and triggers. A starting business process delivers different inputs to different functions. A process flowing through all the functions and sub-functions creates multiple outputs. Enterprise Function Diagrams hereby give a very easy-to-use and detailed representation about a business process and corresponding functions, inputs, outputs and triggers.
In this way EFD has many similarities with IDEF0 diagrams, which also represent in a hierarchical way business processes as a combination of functions and triggers. Difference is that an EFD places the business functions in an organization hierarchical perspective, which outlines the downstream of certain processes in the organization. On the contrary, IDEF0 diagrams show responsibilities of certain business functions trough the use of arrows. Also, IDEF0 has a clear representation of inputs and outputs of every (sub)function.
Figure
**Different modules represent the different business function on multiple organizational levels, which is highlighted by the different colors. On strategic level (yellow) a certain publication project with corresponding products is determined. This is based on certain triggers like sales forecasts, product information.
Line 143 ⟶ 150:
#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
#Zakarian & Kusiak; Process analysis and reengineering: Departement of Industrial Engineering, University of Iowa, USA, Computers & Industrial Engineering 41, 135-150
#Beekman, (1989); European Committee for Standardization, ECN TC310 WG1, 1994
#U.S. Airforce (1981); ICAM architecture part 1, Ohio, Air Force Materials Laboratory, Wright-Patterson
#Peterson J.L. (1981); Petri net theory and the modelling of systems, Englewood Cliffs, N.J., Prentice Hall
#Marshall, C. (2000); Enterprise Modelling with UML, ISBN 0-201-43313-3, Addison-Wesley, MA
#Vernadat F.B.; A vision for future work of the task force (IFAC-IFIP)
#Ortiz et al. (1999); Enterprise Integration—Business Processes Integrated Management: a proposal for a methodology to develop Enterprise Integration Programs, Departamento de Organizacion de Empresas, UniÍersidad Politecnica de Valencia, Spain, Computers in Industry 40, 155-171
#Silva, M. and Valette, R. (1989); Petri nets and Flexible manufacturing. Lecture Notes on Computer Science, 424, 374±417.
#Zhu et al. (2004); Model-driven business process integration and management: A case study with the Bank SinoPac regional service platform, IBM Corporation, Res. & Dev. Vol. 48 No. 5/6
#Aguiar, M. (1995); Executing Manufacturing Models of Open Systems, Ph.D. Thesis, Loughborough University
#Eriksson & Penker (1998); UML Toolkit, Wiley, New York
| |||