Abstract
Office systems are typical representatives of applications with evolving requirements. The functionality of office systems must reflect, for example, organizational changes, new laws, and work flow optimizations. Since an application should not be rebuilt from scratch every time requirements change, reorganization mechanisms and tools supporting application evolution are needed.
This research is supported in part by SIEMENS Austria under grant GR 21/96106/5
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.
Similar content being viewed by others
References
M. Ahlsen, A. Björnerstedt, S. Britts, C. Hulten and L. Söderlund, “An Architecture for Object Management in OIS,” ACM TOOIS 2(3), July 1984.
E. Bertino, M. Negri, G. Pelagatti and L. Sbatella, “An Object-Oriented Data Model for Distributed Office Applications,’’ ACM/IEEE Conf. of Office Information Systems, Cambridge, MA, April 1990, pp. 216–226.
Eduardo Casais, “Managing Class Evolution in Object-Oriented Systems,” Object Management, ed. D.C. Tsichritzis, Centre Universitaire d’Informatique, University of Geneva, July 1990, pp. 133–195.
J. Hogg, O.M. Nierstrasz and D. Tsichritzis, “Office Procedures,” Office Automation: Concepts and Tools, ed. D. Tsichritzis, Springer, 1985, pp. 137–165.
G. Kappel, J. Vitek, O.M. Nierstrasz, B. Junod and M. Stadelmann, “Scripting Applications in the Public Administration Domain”, ACM SIGOIS Bulletin 10(4), December 1989, pp. 21–32.
G. Kappel and M. Schrefl, “Using an Object-Oriented Diagram Technique for the Design of Information Systems,” International Working Conference on Dynamic Modelling of Information Systems, ed. H.G. Sol, North-Holland (to appear), 1990.
G. Kappel and M. Schrefl, “Object/Behavior Diagrams,” 7th International Conference on Data Engineering, Kyoto, Japan, April 1991.
B. Meyer, Object-oriented Software Construction, Prentice-Hall, 1988.
I. Nassi and B. Shneiderman, “Flowchart Techniques for Structured Programming,” ACM SIGPLAN Notices 8(8), August 1973, pp. 12–26.
O.M. Nierstrasz, “A Survey of Object-Oriented Concepts,” Object-Oriented Concepts, Databases and Applications, eds. W. Kim and F. Lochovsky, ACM Press and Addison-Wesley, 1989, pp. 3–21.
O.M. Nierstrasz and D.C. Tsichritzis, “Integrated Office Systems,” Object-Oriented Concepts, Databases and Applications, eds. W. Kim and F. Lochovsky, ACM Press and Addison-Wesley, 1989, pp. 199–215.
T.W. Olle, “System Design Specifications for a Conference Organization System,” Computerized Assistance During the Information System’s Life Cycle, eds. T.W. Olle, A.A. Verrijn-Stuart and L. Bhabuta, North-Holland, 1988, pp. 497–539.
B. Pernici, “Objects with Roles,” ACM/IEEE Conf of Office Information Systems, Cambridge, MA, April 1990, pp. 205–215.
M. Schrefl, “Behavior Modeling by Stepwise Refining Behavior Diagrams,” 9th Int. Conf on Entity Relationship Approach, Lausanne, Oct. 1990.
D. Tsichritzis, “Object-Oriented Development for Open Systems,” Information Processing 89 — IFIP World Computer Congress, ed. G.X. Ritter, North-Holland, 1989, pp. 1033–1040.
Author information
Authors and Affiliations
Editor information
Editors and Affiliations
Rights and permissions
Copyright information
© 1991 Springer-Verlag Berlin Heidelberg
About this paper
Cite this paper
Kappel, G. (1991). Reorganizing Object Behavior by Behavior Composition — Coping with Evolving Requirements in Office Systems. In: Appelrath, HJ. (eds) Datenbanksysteme in Büro, Technik und Wissenschaft. Informatik-Fachberichte, vol 270. Springer, Berlin, Heidelberg. https://doi.org/10.1007/978-3-642-76530-8_29
Download citation
DOI: https://doi.org/10.1007/978-3-642-76530-8_29
Publisher Name: Springer, Berlin, Heidelberg
Print ISBN: 978-3-540-53861-5
Online ISBN: 978-3-642-76530-8
eBook Packages: Springer Book Archive