Summary
With so many different types of diagrams out there, you might think there is no room for improvement. UML certainly dominates the landscape of software diagrams, but many people are starting to feel that UML has gotten too complex—that it is trying to solve too many problems at once. Is it a modeling language, a set of diagramming conventions, or a high-level programming language? Depending on how you use it, it can be all three. When dealing with event-based designs, a circuit-oriented diagram is often a good choice. Event notifications travel around the system like signals in an electrical circuit, so it makes sense to depict the system using the same kinds of concepts adopted in hardware diagrams. The next chapter is dedicated to a new kind of diagram developed specifically for event-based systems.
This is a preview of subscription content, log in via an institution to check access.
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
Preview
Unable to display preview. Download preview PDF.
References
David Harel, “Statecharts: A Visual Formalism for Complex Systems,” Science of Computer Programming, June 1987.
James Martin and James J. Odell, Object-Oriented Methods: A Foundation-UML Edition (Upper Saddle River, NJ: Prentice Hall, 1995).
Tadao Murata, “Petri Nets: Properties, Analysis and Applications,” Proceedings of the IEEE, April 1989.
John C. Grundy, John G. Hosking, and Warwick B. Mugridge, “Supporting Flexible Consistency Management via Discrete Change Description Propagation, Software,” Practice and Experience, September 1996.
Nenad Medvidovic and Richard N. Taylor, “A Classification and Comparison Framework for Software Architecture Description Languages,” IEEE Transactions on Software Engineering, January 2000.
David C. Luckham, John J. Kenney, Larry M. Augustin, James Vera, Doug Bryan, and Walter Mann, “Specification and Analysis of System Architecture Using Rapide,” IEEE Transactions on Software Engineering, April 1995.
W.M.P. van der Aalst, “Formalization and Verification of Event-Driven Process Chains,” Information and Software Technology, July 1999.
Don Box, Essential COM (Boston: Addison-Wesley Professional, 1997).
Clemens Szyperski, Component Software: Beyond Object-Oriented Programming (Boston: Addison-Wesley Professional, 2000).
Jan Ellsberger, Dieter Hogrefe, and Amardeo Sarma, SDL: Formal Object-Oriented Language for Communicating Systems (Upper Saddle River, NJ: Prentice Hall, 1997).
Ted Faison, “Interactive Component-Based Software Development with Espresso” (proceedings of the International Conference on Automated Software Engineering, Lake Tahoe, NV, November 1997).
Desmond Francis D’Souza and Alan Cameron Wills, Objects, Components, and Frameworks with UML: The Catalysis Approach (Boston: Addison-Wesley Professional, 1998).
George T. Heineman and William T. Councill, Component-Based Software Engineering: Putting the Pieces Together (Boston: Addison-Wesley Professional, 2001, p. 308).
Rights and permissions
Copyright information
© 2006 Ted Faison
About this chapter
Cite this chapter
(2006). Diagrams for Event-Based Systems. In: Event-Based Programming. Apress. https://doi.org/10.1007/978-1-4302-0156-4_6
Download citation
DOI: https://doi.org/10.1007/978-1-4302-0156-4_6
Publisher Name: Apress
Print ISBN: 978-1-59059-643-2
Online ISBN: 978-1-4302-0156-4
eBook Packages: Professional and Applied ComputingApress Access BooksProfessional and Applied Computing (R0)