Software evolution in componentware using requirements/assurances contracts

ABSTRACT

In practice, pure top-down and refinement-based development processes are not sufficient. Usually, an iterative and incremental approach is applied instead. Existing methodologies, however, do not support such evolutionary development processes very well. In this paper, we present the basic concepts of an overall methodology based on component ware and software evolution. The foundation of our methodology is a novel, well-founded model for component-based systems. This model is sufficiently powerful to handle the fundamental structural and behavioral aspects of component ware and object-orientation. Based on the model, we are able to provide a clear definition of a software evolution step.During development, each evolution step implies changes of an appropriate set of development documents. In order to model and track the dependencies between these documents, we introduce the concept of Requirements/Assurances Contracts. These contracts can be rechecked whenever the specification of a component evolves, enabling us to determine the impacts of the respective evolution step. Based on the proposed approach, developers are able to track and manage the software evolution process and to recognize and avoid failures due to software evolution. A short example shows the usefulness of the presented concepts and introduces a practical description technique for Requirements/Assurances Contracts.

REFERENCES

• 1: K. Bergner, A. Rausch, M. Sihling, A. Vilbig, and M. Broy. A formal model for componentware. In Formale Beschreibungstechniken f. ur verteilte Systeme FBT'99. Herbert Utz Verlag, 1999.
• 2: Don Box , Grady Booch , Charlie Kindel, Essential COM, Addison-Wesley Longman Publishing Co., Inc., Boston, MA, 1997
• 3: Bran Selic , Garth Gullekson , Paul T. Ward, Real-time object-oriented modeling, John Wiley & Sons, Inc., New York, NY, 1994
• 4: M. Broy, F. Dederichs, C. Dendorfer, M. Fuchs, T. Gritzner, and R. Weber. The design of distributed systems - an introduction to FOCUS. Technische Universit. at M. unchen, January 1992.
• 5: M. Broy, E. Denert, K. Renzel, and M. Schmidt (eds.). Software architectures and design patterns in business applications. Technische Universit. at M. unchen, 1997.
• 6: Manfred Broy , Christoph Hofmann , Ingolf Krueger , Monika Schmidt, Using Extended Event Traces to Describe Communication in Software Architectures, Proceedings of the Fourth Asia-Pacific Software Engineering and International Computer Science Conference, p.203, December 02-05, 1997
• 7: Manfred Broy , Ingolf Krüger, Interaction Interfaces - Towards a Scientific Foundation of a Methodological usage of Message Sequence Charts, Proceedings of the Second IEEE International Conference on Formal Engineering Methods, p.2, December 09-11, 1998
• 8: Martin Buchi , Wolfgang Weck, A Plea for Grey-Box Components, Turku Centre for Computer Science, 1997
• 9: Frank Buschmann , Regine Meunier , Hans Rohnert , Peter Sommerlad , Michael Stal, Pattern-oriented software architecture: a system of patterns, John Wiley & Sons, Inc., New York, NY, 1996
• 10: D. Flanagan. Java in a Nutshell. O'Reilly & Associates, Inc., 2nd edition, 1996.
• 11: Erich Gamma , Richard Helm , Ralph Johnson , John Vlissides, Design patterns: elements of reusable object-oriented software, Addison-Wesley Longman Publishing Co., Inc., Boston, MA, 1995
• 12: David Harel, On visual formalisms, Communications of the ACM, v.31 n.5, p.514-530, May 1988 [doi>10.1145/42411.42414]
• 13: Richard Helm , Ian M. Holland , Dipayan Gangopadhyay, Contracts: specifying behavioral compositions in object-oriented systems, Proceedings of the European conference on object-oriented programming on Object-oriented programming systems, languages, and applications, p.169-180, September 1990, Ottawa, Canada
• 14: Ivar Jacobson , Grady Booch , James Rumbaugh, The unified software development process, Addison-Wesley Longman Publishing Co., Inc., Boston, MA, 1999
• 15: Ivar Jacobson, Object-oriented software engineering, ACM Press, New York, NY, 1991
• 16: JavaSoft. Enterprise JavaBeans website, <http://java.sun.com/~products/~ejb/>, 1999.
• 17: Leslie Lamport, The temporal logic of actions, ACM Transactions on Programming Languages and Systems (TOPLAS), v.16 n.3, p.872-923, May 1994 [doi>10.1145/177492.177726]
• 18: G. T. Leavens, A. L. Baker, and C. Ruby. Preliminary design of JML: A behavioral interface specisification language for Java. Iowa State University, 1999.
• 19: C. Lucas, P. Steyaert, and K. Mens. Managing software evolution through reuse contracts. Vrije Universiteit Brussel Faculteit Wetenschappen, BELGIUM, 1997.
• 20: Bertrand Meyer, Object-oriented software construction (2nd ed.), Prentice-Hall, Inc., Upper Saddle River, NJ, 1997
• 21: G. Neumann. 500 Europa: Der Club der Innovatoren. Information Week, pages 10{12, Jan. 1999.
• 22: OMG. The Common Object Request Broker: Architecture and Specication. Object Management Group, February 1998.
• 23: OMG. OMG Unified Modeling Language Specification. Version 1.3, Object Management Group, 1999.
• 24: Robert Orfali , Dan Harkey, Client/server programming with Java and CORBA, John Wiley & Sons, Inc., New York, NY, 1997
• 25: Vaclav Rajlich, Software Change and Evolution, Proceedings of the 26th Conference on Current Trends in Theory and Practice of Informatics on Theory and Practice of Informatics, p.189-202, November 27-December 04, 1999
• 26: A. Rausch. Executive Summary: Software Evolution in Componentware { A Practical Approach. In Software Change and Evolution 1999 Workshop Proceedings, 1999.
• 27: James Rumbaugh , Michael Blaha , William Premerlani , Frederick Eddy , William Lorensen, Object-oriented modeling and design, Prentice-Hall, Inc., Upper Saddle River, NJ, 1991
• 28: B. Rumpe. Formale Methodik des Entwurfs verteilter objektorientierter Systeme. PhD thesis, Technische Universit. at M.unchen, 1996.
• 29: Patrick Steyaert , Carine Lucas , Kim Mens , Theo D'Hondt, Reuse contracts: managing the evolution of reusable assets, ACM SIGPLAN Notices, v.31 n.10, p.268-285, Oct. 1996

INDEX TERMS

Primary Classification:
  D. Software
  D.2 SOFTWARE ENGINEERING
      D.2.1 Requirements/Specifications
          Subjects: Methodologies (e.g., object-oriented, structured)

Additional Classification:
  D. Software
  D.1 PROGRAMMING TECHNIQUES
  D.2 SOFTWARE ENGINEERING

  K. Computing Milieux
  K.6 MANAGEMENT OF COMPUTING AND INFORMATION SYSTEMS
      K.6.3 Software Management
          Subjects: Software development

General Terms:
Design, Management, Performance, Theory

Keywords:
componentware, contracts, description techniques, formal methods, object-orientation, software architecture, software evolution