Previous | Table of Contents | Next

Page 375

Determining the Number of CASE Applications to UseA number of questions should be answered to determine the number of CASE applications to use. These include:

Several strategies can be used, and each has its pros and cons.

Centralized ConfigurationIn a centralized configuration, all the data is owned by one application and the others share this data.

The advantages to this strategy include:

The disadvantages to this strategy include:

Decentralized ConfigurationDecentralized configuration means that each application owns its own data and can grant privileges on its elements to other applications as needed.

The advantages to this strategy include:

The disadvantages to this strategy include:

Page 376

Combined ConfigurationIn combined configuration, a master application owns elements that are common to more than one application and shares these with applications that need them. There are also applications that contain application-specific data that is not shared with others.

The advantages to this strategy include:

The disadvantages to this strategy include:

Determining the Number of RepositoriesThere are several things to consider when determining the number of repositories. These include:

Using multiple instances can have its advantages and disadvantages:

The pros and cons of using the different configurations are summarized in Table 15.5.

Page 377

Table 15.5Pros and Cons of Using Different Configurations

Factor to Consider Centralized Decentralized Mixed
Time to administer access privileges low low medium
Ease of version control high low medium
Support for parallel system development low high medium
Performance on frequently versioned systems low high medium
Need to use multiple instances low high medium
Interdependency of applications high low medium

Enhancing the Performance of Designer/2000

The installation guide for Designer/2000 has a number of hardware and software requirements that should be met. The following discussion provides suggestions that can improve the performance of Designer/2000 (use them with caution because it might affect other Windows applications also).

Optimizing the Client Machine

A client/server configuration works quite well with Designer/2000. However, a network
install is not recommended because there will be performance problems. A minimum of a
386 machine is required, and there is no notable difference between using one hardware
manufacturer or another. The minimum is 16MB of memory, although 32MB is recommended. Optimize memory usage in your system with some of the following tips:

Page 378

Optimizing the Network

The network performance can affect overall system performance, and it should be carefully monitored.

Get SQL*NET trace files or put sniffers to determine the network performance and where the degradation is present. Use dead connection detection by setting sqlnet.expire_time= <time_in_minutes> in the sqlnet.ora. This will allow the listener to check after every time period specified in the above setting to make sure that there are no dead connections.

Optimizing Designer/2000

Several things can be done to optimize Designer/2000:

Optimizing the Database Server

Database optimizing is an art and has to be constantly performed on the database, due to changing conditions in the database. Tuning Oracle by Oracle Press is a very good book on different tips that can be used to optimize the database performance. The following tips can be helpful:

Previous | Table of Contents | Next