Software crisis and new development paradigms or how to design reliable medical software

Abstract

The extended operational paradigm (EOP) is a software development paradigm for dealing with the emerging software crisis in the field of medical software development. This crisis is a result of using the waterfall paradigm, which neglects many dimensions of system design. The EOP paradigm is based on the multidimensional, multiview, multilingual, and user-oriented (M/sup 3/UO) framework. A CASE tool called the extended operational approach (EOA), developed to support EOP, is presented. EOA is based on JSP, SML, and spreadsheet software. EOP was successfully used in the development of a medical decision and information support system. Experience with using EOA has shown that it reduces the complexity of the specification. The semantic gap between users and development groups, and the effort results in increased productivity, user satisfaction, and more reliable systems.<>