System Modelling
stores process models in the same repository that the other Oracle Designer/2000 tools use. The first requirement for a computer systems implementation project is a definition of the scope. One common way to express this scope is through the definition of a function hierarchy. A process model already includes this hierarchy of process, sub-process and process step.
can view and refine the process model as a pure function hierarchy or as a set of dataflow diagrams, which additionally show the flows and stores defined in the process model. The system specification is accelerated, because scope is pre-defined and documented. The communication is improved, because the models that were originally created and agreed by business users are now re-cast as system models. The association of each process step with the organisation unit responsible for performing that step becomes the initial specification of menus for the resultant system. One menu per organisation, each with options to invoke the system facilities that support the process steps that organisation performs.
Rapid Application Development (RAD)
and
directly transform the models created by
and refined by
to create fully functional working systems. Because of the high level of automation, it is easy for developers to use prototyping and iteration to keep business users informed of the development and to seek input to improve the system in the most direct manner possible. And at any point the models can be corrected or enhanced to drive the next cycle of prototyping until a system that is 'fit for purpose' results. Of course these tools support a more formal development approach just as well, but a RAD approach has the additional benefit of maintaining a high level of user involvement and visibility that contributes to the change process.
Implementation and Enhancement
The original process models provide a clear indication of system workflow and make a sound basis for user training. This material already exists and so accelerates system implementation and hand-over. The users who have been involved in the RAD implement ation will already be very familiar with the new process and the way the new system supports it; they will have reviewed and approved it at each iteration.
Successful handover, to users familiar with the system, is the first milestone of computer systems implementation. But successful systems grow and change with the process they serve, so the implemented system must support swift and sure enhancement. The whole development from process model to implemented code was driven by a series of related models in a common repository. These models still exist and can be interrogated using the
tools. Impact analysis, enforcement of consistency standards and reuse of model components for add-on projects are automated. Dealing with the inevitable teething troubles of new processes and supporting the continued improvement of new processes are just as important as implementing those new processes. All the modelling, tion and management tools are deployed to ensure that the initial success is not eroded.
Copyright © 1996 Oracle Corporation. All Rights Reserved.