On the Load Balancing of Business Intelligence Reporting Systems

Abstract

The UML model consists of several types of diagrams representing different aspects of the modeled system. To assure the universality and flexibility, the UML involves only a few general rules about dependence among different types of diagrams. In consequence people can have the different methodologies based on the UML, but in the same time we haven't the formal tool for assure the vertical cohesion of created model. To test and reach the vertical cohesion of the model some auxiliary information about the relations among the elements belonging to different types of diagrams should be remembered. In this chapter the authors present the method of formal representation of such information in a form of the relation, called Accomplish Relation. This method is based only on the UML properties and is independent from any methodology. Additionally, they show how to use the UML timing diagrams for representing the users' requirements in association with use cases. To illustrate the usefulness of this approach we present how it can be used for load balancing of distributed system in case of a Reporting Systems based on Data Warehouse concept.

On the Modeling Timing Behavior of the System with UML(VR)

“…In [13] we consider a typical reporting systems. Every business organization during its activity generates many single reports.…”

“…Only Consultant Actor uses more that one systems function (ad hoc report generation and hypothesis verification). Thus we have to create five timing diagrams to express user behavior timing characteristics [13].…”