Christian Mager 58 <strong>FHWS</strong> <strong>Science</strong> <strong>Journal</strong>, Vol. 1, No. 1, 2013
Flow-Design and Event-Based Components: A New Approach in Designing Software Compared to Established Procedures TOBIAS GEGNER University of Applied <strong>Science</strong>s Wuerzburg-Schweinfurt Flow-Design is a new approach in developing software architectures. Flow-Design focuses on data processing function units and the communication among them. Event-Based Components represent a programming language independent methodology for implementing Flow-Design and can also be considered as a resulting software architecture. The Event- Based Components software architecture is structured by components that communicate via events. Therefore it is compared to the concept of service-oriented architecture and event-driven architecture which aim to create independent components as well. In conclusion Flow-Design and Event-Based Components provide a platform and programming language independent concept to develop software components. The resulting components are reusable, maintainable and testable. Although it can lead to a more complex coding. Kategorie <strong>und</strong> Themenbeschreibung: Software Engineering Object oriented programming, Software architecture, Software design, Software reusability, Software engineering. 1 INTRODUCTION Software development has ever since strived for re-usability and maintainability. Manufacturing industry with standards across companies and national borders has reached a high level in reusing and composing parts built by different suppliers. Serving as a role model, manufacturing industry motivated computer scientists explore ways of mapping industry procedures to software development. Therefore in the past years different approaches arisen to develop software components of a high level of reusability. Within this evolution several approaches evolved using events to couple components and arrange communication among them. These event-based architectures are widely discussed and find appliance in distributed software systems as well as within sole software systems or components e.g. [Cugola et al., 2001, Eugster et al., 2003, Carzaniga et al., 1998, Fiadeiro and Lopes, 2006, Kowalewski et al., 2008]. Following the idea of using events to make software components more independent of their environment Ralf Westphal invented Flow-Design and Event-Based Components. By using design patterns and best practices he evolved the way of designing and implementing software. In the following this paper will introduce Event-Based Components to the reader. By examining a running example, the f<strong>und</strong>amental concepts of Flow-Design will be discussed, as well as differences to object-oriented analysis and design. Further the implementation of Flow-Design with Event-Based Components will be described. Subsequently a comparison of Flow-Design and Event-Based Components to established design processes and software architectures will be given. In the end a conclusion is given as well as a future outlook. 10 Author's address: Tobias Gegner, University of Applied <strong>Science</strong>s Wuerzburg-Schweinfurt, Faculty of Computer <strong>Science</strong> and Business Information Systems, Sanderheinrichsleitenweg 20, 97074 Würzburg, Germany, www.fhws.de Permission to make digital or hard copies of part or all of this work for personal or classroom use is granted without fee provided that copies are not made or distributed for profit or commercial advantage and that copies show this notice on the first page or initial screen of a display along with the full citation. Copyrights for components of this work owned by others than <strong>FHWS</strong> must be honored. Abstracting with credit is permitted. To copy otherwise, to republish, to post on servers, to redistribute to lists, or to use any component of this work in other works requires prior specific permission. <strong>FHWS</strong> SCIENCE JOURNAL, Vol. 1, No. 1, 2013 59
- Page 1 and 2:
FHWS Science Journal Jahrgang 1 (20
- Page 3 and 4:
Neue wissenschaftliche Schriftenrei
- Page 5 and 6:
Artificial Communication - Can Comp
- Page 7 and 8: Eberhard Grötsch, Alfredo Pina, Mi
- Page 9 and 10: Eberhard Grötsch, Alfredo Pina, Mi
- Page 11 and 12: Eberhard Grötsch, Alfredo Pina, Mi
- Page 13 and 14: Eberhard Grötsch, Alfredo Pina, Mi
- Page 15 and 16: Präsentationssteuerung mit berühr
- Page 17 and 18: Melanie Saul Transferleistung, die
- Page 19 and 20: Melanie Saul der Systemsteuerung un
- Page 21 and 22: Melanie Saul Zur besseren Übersich
- Page 23 and 24: Native versus HTML5 - where’s mob
- Page 25 and 26: Patrick Mennig Figure 1 illustrates
- Page 27 and 28: Patrick Mennig an experience is the
- Page 29 and 30: Patrick Mennig Platform Feature B
- Page 31 and 32: Patrick Mennig In the future, the s
- Page 33 and 34: Mobile Enterprise Application Devel
- Page 35 and 36: Florian Wolf, Karsten Huffstadt The
- Page 37 and 38: Florian Wolf, Karsten Huffstadt exp
- Page 39 and 40: Florian Wolf, Karsten Huffstadt REF
- Page 41 and 42: Branded Financial Apps - Was erwart
- Page 43 and 44: Sebastian Sprenger Mobiles Marketin
- Page 45 and 46: Sebastian Sprenger und Apple App St
- Page 47 and 48: Sebastian Sprenger Auf dem Gebiet n
- Page 49 and 50: Analysis of Service Level Agreement
- Page 51 and 52: Christian Mager information about a
- Page 53 and 54: Christian Mager 4 PROCESS MINING AP
- Page 55 and 56: Christian Mager Fig. 2. Dotted char
- Page 57: Christian Mager REFERENCES AMELLER,
- Page 61 and 62: Tobias Gegner analyzed for substant
- Page 63 and 64: Tobias Gegner reformat text represe
- Page 65 and 66: Tobias Gegner approach leads to Boa
- Page 67 and 68: Tobias Gegner strict with the FD de
- Page 69 and 70: Tobias Gegner 2.3.5 Tooling EBC are
- Page 71 and 72: Tobias Gegner Components, software
- Page 73: Tobias Gegner WESTPHAL, R. 2010E. Z
Change language