Advertisement

Rhapsody: A Complete Life-Cycle Model-Based Development System

  • Eran Gery
  • David Harel
  • Eldad Palachi
Conference paper
Part of the Lecture Notes in Computer Science book series (LNCS, volume 2335)

Abstract

We discuss Rhapsody, a UML based software development tool, designed to support complete model-based iterative life-cycle. First, we identify several key inhibiting factors that prevent model-based approaches from being adopted as a mainstream practice. We then examine the requirements for allowing complete life-cycle model-based development and discuss how they are met by Rhapsody through its key enabling technologies, which include:
  • model-code associativity

  • automated implementation generation

  • implementation framework

  • model execution

  • model-based testing

We explain why each of these features is instrumental to an effective development of production systems, based on a key observation that the modeling language does not replace the implementation platform, but should be integrated with it in a synergistic manner. This allows the use of modeling for expressing requirements and design abstractions, along with the use of the full power of an implementation language and its supporting platform to specify implementation details. While allowing this flexibility, Rhapsody facilitates full consistency of the modeling and implementation artifacts throughout the life-cycle, and it also supports a high level of automation in the implementation and validation of the developed system.

Keywords

Sequence Diagram Model Execution Implementation Framework Iterative Development Implementation Language 
These keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.

Preview

Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

References

  1. 1.
    B.P. Douglass Doing Hard Time. Addison-Wesley Object Technology Series, 1999.Google Scholar
  2. 2.
    W. Damm and D. Harel. LSCs: Breathing Life into Message Sequence Charts. Formal Methods in System Design, 19(1), 2001. (Preliminary version in Proc. 3rd IFIP Int. Conf. on Formal Methods for Open Object-Based Distributed Systems (FMOODS’99), (P. Ciancarini, A. Fantechi and R. Gorrieri, eds.), Kluwer Academic Publishers, 1999, pages 293–312.)Google Scholar
  3. 3.
    D. Harel and E. Gery. Executable Object Modeling with Statecharts. IEEE Computer, pages 31–42, July 1997. Also, Proc. 18th Int. Conf. on Software Engineering, Berlin, IEEE Press, March, 1996, pp. 246–257.)Google Scholar
  4. 4.
    Rhapsody’s user guide. http://www.ilogix.com
  5. 5.
    I. Jacobson, G. Booch, J. Rumbaugh. The Unified Software Development Process. Addison-Wesley Object Technology Series, 1998.Google Scholar
  6. 6.
    E. Gery, R. Rinat, J. Ziegler. Octopus Concurrency Design with Rhapsody. http://www.ilogix.com
  7. 7.
    OMG Unified Modeling Language Specification, Version 1.4. OMG Document formal/01-09-67Google Scholar
  8. 8.
    OMG Architecture Board MDA Drafting Team. ”Model Driven Architecture-A Technical Perspective”. OMG Document ormsc/01-07-01Google Scholar
  9. 9.
    UML 1.4 with Action Semantics. OMG Document ptc/02-01-09, p. 2-209–2-349Google Scholar
  10. 10.

Copyright information

© Springer-Verlag Berlin Heidelberg 2002

Authors and Affiliations

  • Eran Gery
    • 1
  • David Harel
    • 1
  • Eldad Palachi
    • 1
  1. 1.I-Logix, Inc.Sweden

Personalised recommendations