2 Analysis 4
3 Design 5
4 Conclusion 6
4.1 Usage Examples 6
5 Appendixes 7
Figure 2‑1: Global parameters object 4
Figure 4‑1: Global parameter – SetPrameter, FindParameter, ResetParameter, GetEntirePicutre 6
Table 3‑1: System parameters module's layers decomposition. 5
This essay takes as its purpose analysis and design of custom global parameters module. The meaning of custom global parameter is data that shared across all processes within the user session, in addition the information can be written to the database.
The module provides an ability of data retrieval, its appending, and its flushing.
The global parameters module must give an opportunity of shared data management among the processes within the user session, when the main purpose of such data is being a run time parameters.
The following diagram presents object diagram of needed business layer:
Figure 2‑1: Global parameters object
The module must include several elements from database, business, and graphic user interface layers:
- BC (Business Component) – contains several methods and based on custom VBC
- BS (Business Service) – contains several methods delegated by underlied business component
The analysis can be handled using a single stand alone module definition. The module will include several elements from every one of three application tiers:
* Graphic User Interface Layer
· View – System Parameters View
· Applet - System Parameters List Applet
* Business Layer
· Business Object – System Parameters
· Business Component – System Parameters with methods
§ SetParameter() – creates new entry
§ FindParameter() – makes a search across parameters in order to find out the appropriate parameter that answers on search specification
§ ResetParameter() – resets the data of given parameter
§ GetEntirePicture() – retrieves the entire picture of populated parameters as hierarchy. The hierarchy can be presented within the appropriate applet.
· Business Service – Global Parameters BS encapsulates delegated methods of Business Component
The following table demonstrates those elements per layer:
Table 3‑1: System parameters module's layers decomposition
Current essay provides a new sight over the old problem, how to store cross processes parameters and effectively use them during the session of system users. The pattern can be used in many applications like CTI phone book, XSLT etc.
4.1 Usage Examples
The following figures demonstrate proposed solution examples:
Figure 4‑1: Global parameter – SetPrameter, FindParameter, ResetParameter, GetEntirePicutre
* "Workflow usage best practices" (Roman Agaev)
* "Common VBC paradigm" (Roman Agaev)
* "Common error handling mechanism" (Roman Agaev)
 For further information please refer to "Common VBC paradigm" in Appendixes section of the document
 Cacheable business service