Designer/2000 is a revolutionary second-generation client/server tool for developing and protyping enterprise-wide information systems solutions. As software developers of enterprise-wide information solutions, the techniques and technologies to perform
these tasks are constantly changing. As soon as one promising solution to providing rapid development of information systems solutions appears and accumulates a following, the technology and tools seem to change almost overnight. As professional
developers, we are constantly being asked to change methods, tools, and technologies when confronted with a new solution to developing and maintaining enterprise information systems.
Although the profession of designing and deploying information systems is in a state of constant change, we are often reminded that our customers are in need of solutions. Whether our customers dwell in corner offices and have personalized parking
spaces or process payroll registers, or perform data entry for the majority of the day, all of their efforts contribute to the performance, progress, and success of the company. Strangely enough, those in corner offices often have their information system
needs put ahead of others, for whatever reason.
Designing, developing, and implementing the solutions needed by these groups or individuals is often a task not often completed by information system departments. Often, the solution is implemented too late to be effective. Internal or external changes
may have changed the flow or importance of information since the initiation of the project. Other times, what the customer needed is not exactly what was delivered. And, at other times, we as professionals fail to consider how a solution developed for one
group will impact another related group or division. All these aspects are of dire importance when developing information system solutions.
Successful information systems often share common properties. These properties can be defined as
Although successful information systems often contain common attributes, the approaches to attain the end results have been changing radically throughout the past several years. New approaches are being developed, and old tried and true approaches are
still being utilized because of their past successes. While no single approach is suitable for every situation, Designer/2000's objective is to support a wide range of approaches in delivering information systems. It is the responsibility of the developers
to match the proper approach with the need of each project. Let's discuss each approach tightly integrated into Designer/2000, and when you should use each of the four approaches.
It's the 1990s. Businesses are down sizing, integrating, merging, and expanding...all seemingly in a single step. This often leads to smaller departments, yet increased visibility and responsibility within the enterprise. At the other end of the
spectrum, small businesses can grow from two employees to several hundred within a very short amount of time.
Both of the above situations may need to investigate Business Process Reengineering, or BPR in developing an information system. BPR often starts with the notion that something is wrong with the integration of the enterprise. This could be caused by
downsizing, or rapid growth, as described above.
This approach often involves integrating multiple departments, each with complex information systems needs. Understanding the overall integration of the enterprise is often revealed when BPR is utilized. While BPR may have some resemblance with more
traditional approaches, this methodology incorporates an emphasis on redesign of processes within the enterprise, and how those processes interact with each other.
Once the diagnosis has been completed, you must act upon that diagnosis. Knowing that you have a cold based on a runny nose, coughing and congestion does nothing to help you until you actually do something, like take some medication. Once the processes
have (possibly) been redesigned, the process model is of little significance unless acted upon. To achieve a successful implementation using BPR, the redesigned processes and procedures must be implemented. New procedures may be required, or old ones
changed radically, as well as an information system to support those new procedures and processes.
BRP utilizes the following portions of Designer/200:
Figure 22.1. The Process Modeller in action, displaying the flow of information through a single department.
Business Process Reengineering takes a lot of involvement from management within each effected process. Be aware that with the involvement of numerous separate processes, you must juggle personalities, conflicts,
and differences within each department or division.
"He who controls the data controls the world." Although not entirely true, that is the concept behind information engineering. This approach to information systems development considers data as one of the most valuable resources of an
enterprise. By analysis of information, and how that information impacts the divisions within the enterprise, future plans to implement information systems can be derived. The steps and processes utilized within Designer/2000 to implement an Information
Engineering approach to an information system are as follows:
As you can derive from the name, Rapid Application Development (RAD) attempts to provide quick, useful, and effective information system. Through use of specialized tools, developers can quickly prototype and generate entire applications. In this
approach, the end user is very aware of what is needed for a successful information system. Other than verifying what the user is requesting, is what will be delivered and the impact, or lack of impact, on other divisions or departments. Delivering a
working application is not impossible. Using Designer/2000, developers can quickly prototype an information system, and deliver a working application in a relatively short amount of time. The steps and processes utilized within Designer/2000 to implement
an RAD approach to an information system are as follows:
The RAD approach to implementing an information system is best used when the end user is well aware of what is needed, and when the scope of the project is not likely to fluctuate to a great degree. Another sign to
using the RAD approach is that the information system will not greatly effect, either directly or indirectly, the operation of other divisions or departments.
In using the Legacy Led approach, an existing system is being replaced, upgraded, or added to. As the enterprise grows, expands, and possibly broadens it's business horizon, information systems already in place may outlive their usefulness. If a
previous analysis of the process is available, you are one step ahead of the process. This should allow analysis of how the new additions will impact the system, or what processes the replacement must perform. If the system was developed using the
predecessor to Designer/2000, Oracle CASE, its design will be readily available to Designer/2000.
Using the Legacy Led Development approach, existing processes are reverse engineered into Designer/2000. These definitions are stored in the Designer/2000 Repository, where they are available as the central source of redesign. The processes utilized
within Designer/2000 to implement a Legacy Led Development approach to an information system are as follows:
With Design/2000's capability to support multiple approaches to developing information systems, its common repository, entity reusability, and its consistency of application development, Designer/2000 is a tool that every professional system developer can utilize.
