Skip to main content
Log in

Bridging the requirements–implementation modeling gap with object–process methodology

  • Original Paper
  • Published:
Innovations in Systems and Software Engineering Aims and scope Submit manuscript

Abstract

A model-based system development cycle involves two semantically distinct aspects: the requirements specification and the implementation model. Due to the conceptual and semantic differences between these two major system lifecycle stages, the transition from requirements to implementation is inherently a noncoherent process. Consequently, the system requirements are not faithfully transformed into the working system. This paper introduces an effective solution via an Integrated Modeling Paradigm (IMP) that combines the requirements and implementation domain models into a unified system model that continuously represents the system as it evolves. The IMP was implemented in an Object–Process Methodology (OPM) development environment. This implementation reinforces OPM with the capability to bridge the significant conceptual gap that lies right at the heart of the development process. A user survey has shown that this OPM-based solution is easy to use and can indeed help bridge the information gap, yielding a better match between the required and implemented systems than the currently accepted practice.

This is a preview of subscription content, log in via an institution to check access.

Access this article

Price excludes VAT (USA)
Tax calculation will be finalised during checkout.

Instant access to the full article PDF.

Similar content being viewed by others

References

  1. Boehm B, Port D (1999) Escaping the software tar pit: model clashes and how to avoid them. ACM Softw Eng Notes 24(1): 36–48

    Article  Google Scholar 

  2. Brooks F (1995) The mythical man-month. Addison-Wesley Longman, Reading

    Google Scholar 

  3. Dori D (1995) Object-process analysis: maintaining the balance between structure and behavior. J Logic Comput 5(2): 227–249

    Article  Google Scholar 

  4. Dori D (2002) Object-process methodology—a holistic systems paradigm. Springer, Berlin

    Google Scholar 

  5. Dori D, Reinhartz-Berger I, Sturm A (2003) Developing complex systems with object-process methodology using OPCAT. In: Int. Conf. on conceptual modeling (ER 2003), Lecture notes in computer science, vol 2813, pp 570–572

  6. France R, Rumpe B (2007) Model-driven development of complex software: a research roadmap. In: Proceedings, future of software engineering (FOSE ’07), pp 37–54

  7. Gibbs W (1994) Software’s Chronic Crisis, Scientific American, Sep. 1994, p 86

  8. Harel D (2001) From play-in scenarios to code: an achievable dream. IEEE Comput 34(1): 53–60

    MathSciNet  Google Scholar 

Download references

Author information

Authors and Affiliations

Authors

Corresponding author

Correspondence to Avi Soffer.

Rights and permissions

Reprints and permissions

About this article

Cite this article

Soffer, A., Dori, D. Bridging the requirements–implementation modeling gap with object–process methodology. Innovations Syst Softw Eng 5, 27–34 (2009). https://doi.org/10.1007/s11334-009-0079-2

Download citation

  • Received:

  • Accepted:

  • Published:

  • Issue Date:

  • DOI: https://doi.org/10.1007/s11334-009-0079-2

Keywords

Navigation