Bridging the requirements–implementation modeling gap with object–process methodology
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.
KeywordsModel-driven development Transition from specification to design
Unable to display preview. Download preview PDF.
- 2.Brooks F (1995) The mythical man-month. Addison-Wesley Longman, ReadingGoogle Scholar
- 4.Dori D (2002) Object-process methodology—a holistic systems paradigm. Springer, BerlinGoogle 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–572Google Scholar
- 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–54Google Scholar
- 7.Gibbs W (1994) Software’s Chronic Crisis, Scientific American, Sep. 1994, p 86Google Scholar