Completing the Department Application › Summary

Summary

The sample Department application is now fully developed. The steps you performed while developing the Department application throughout this manual could have been performed in a different order, depending on the preferences and requirements of the site. For example, you could have added process logic to dialogs before associating the dialogs with ADSA application functions.

In Part II of this manual, "Developing the Prototype," you began developing the Department application based on a structure diagram for the application. You created a prototype of the application by defining components for the application:

1. You defined the executable application structure in Chapter 8, "Defining an Application Structure Using ADSA". The structure consists of:
   • Functions (for example, MODDEP) that represent units of work (such as dialogs) to be performed by the application
   • Responses (for example, EXIT) that define run-time paths between functions in the application
   • A task code (XXXDEPT) that defines an entry point for the application
2. You defined a map in Chapter 9, "Defining a Screen Display Using MAPC". The map allows dialogs in the application to display department information.
3. You defined skeleton versions of dialogs in Chapter 10, "Defining Dialogs Using ADSC". At run time, these dialogs are executed when control passes to the application functions that invoke them.

Based on tests of the completed prototype, you modified the prototype to make the application easier to use. You changed flow of control and screen displays without having to alter any code.

After the prototype application was approved, you developed a fully functional application from the prototype in Part III of this manual, "Enhancing the Application Definition." You added process logic and a work record to the application's skeleton dialogs:

1. You defined process modules for dialog XXXDADD in Chapter 13, "Adding Process Logic to a Dialog" and Chapter 14, "Modifying Process Logic in a Dialog". These processes allow end users to add new departments to the database.
2. You defined a work record in Chapter 14, "Modifying Process Logic in a Dialog". The record stores a value that determines the processing performed by dialog XXXDUPD at run time.
3. You defined process modules for dialog XXXDUPD in this chapter. These processes allow end users to modify and delete departments in the database.

After completing the Department application, you executed the completed application to test its full capabilities.

Even though you have tested the Department application, you still may need to make modifications either now or in the future. For example, consider the following sources of change:

• Tests and preliminary use of the application can cause developers, end users, and managers to suggest changes.

  For example, end users of the Department application might prefer blanks to be displayed instead of zeros (0000) in fields where they enter numeric values (for example, the DEPARTMENT ID variable field).

  End users might request that execution of the application be changed from STEP to FAST mode. In FAST mode, the end user can enter values on one screen and transfer to another screen at the same time.

  End users might have difficulty remembering the ID numbers for all departments to be modified or deleted. One solution would be to add a dialog function that alphabetically lists all departments and allows the end user to select a department from the list.

• Changes in regulations, updated business functions, and other planned and unplanned developments can require developers to modify an application.

  For example, new contractors might require the collection of additional information for departments.

  Long-term plans for the sample Department application could call for you to add EMPLOYEE and OFFICE functions to the existing application structure.

CA ADS application development tools can be used at any time to modify individual application components and to add new components to the application. For example, you can add EMPLOYEE and OFFICE functions to the Department application by defining maps and process modules for EMPLOYEE and OFFICE dialogs. When the dialogs are developed, you can incorporate the dialogs into the application structure by using ADSA to add the necessary functions and responses to the application.