QPR Knowledge Base

Program Architecture

Hide Navigation Pane

Program Architecture

Previous topic Next topic No expanding text in this topic  

Program Architecture

Previous topic Next topic JavaScript is required for expanding text Mail us feedback on this topic!  

Comments (...)

QPR ScoreCard consists of three modules: Development Client, Application Server, and Web Client. The system also contains a separate reporting subsystem.

 

QPR ScoreCard, i.e. the Development Client, is the tool to be used primarily for the development of models and for QPR ScoreCard administration; however, it can be used for browsing models as well. The following functions can be performed with the Development Client: model creation and development, data input, user rights management, report management, and customization of graphics.

 

The QPR ScoreCard Server, i.e. the Application Server, manages the connections to the other two modules, and stores all model information. This permits different users to work with one model simultaneously. It also means that changes made to models are updated immediately.

 

The QPR Web Client is the web-based application for accessing QPR product information, which allows users to browse models and make updates over the web. The Web Client provides users with up-to-date, customized views and easily navigatable and searchable model information.

 

The QPR User Management System (UMS) is the user management system that is used by QPR products. This system is only for the authentication of users, whereas the administering of specific rights to the users is performed separately from within QPR ScoreCard itself. Users and groups can be managed from the QPR User Management Client. Therefore users and groups are not added from within QPR ScoreCard but within the QPR User Management Client.

 

These core QPR ScoreCard components, the Development Client and the Application Server, along with the QPR User Management System (UMS) and the QPR Web Application Server (WAS), on which the QPR ScoreCard plugin, QPR ProcessGuide plugin, and the QPR Portal plugin run, make up the entire QPR System.

pic_qpr_system_architecture

Comments (...)