It is critical to define object-oriented (OO) technology within a framework of a powerful solution to particular, existing programmer/user needs. One attractive option is the Rapid Application Prototyping, Integration and Deployment (RAPID) architecture. Using a tool that utilizes a RAPID-like strategy gives programmers and users a practical framework in which OO can address business problems quickly. The RAPID approach results in OO applications that can be created more rapidly and remain more useful than applications created with conventional tools. A RAPID/OO prototyping method also provides for programmers to build program objects once and use them in various combinations to develop distinct programs.
Computing Canada. June 22, 1994, Vol. 20 Issue 13, p27, 1 p.
Object-oriented programming, Management of EDP, Programming Management, Training, Guidelines, and Object-oriented programming -- Usage
Corporate MIS officials should consider a number of factors when moving from traditional programming towards object-oriented (OO) approaches. The OOP field is still in a transitional mode and there are a variety of programming languages, program development tools, databases and OO analysis/design (OOA/OOD) methodologies available. MIS officials should consult with experts and not limit themselves to one vendor's development tools. They should also decide at the outset whether their goal is to use outside experts to train in-house staff on OOP technology or to deliver new systems quickly and efficiently. A suggested approach is to combine Use Cases with Class-Responsibility-Collaboration (CRC) cards, a diagramming scheme such as Rumbaugh's OMT and a prototyping notation to maximize code reusability. Under such an approach, design data is captured via a combination of word processing and diagramming tools.