Challenge Overview
The client of this company is one of the world largest software and hardware manufacturer. Order Status Online (OSOL) application allows large enterprise companies, small/medium businesses, public clients and business partners who directly placed orders to IBM or Lenovo to track these orders. OSOL application keeps all the information related to the placed orders, manufacturing data and distribution cycles in the special repository.
The repository is a backend OSOL, but it is not directly accessible by users. User can access GUI screens of OSOL application’s front-end to access information about placed orders. The status information about customers’ orders will be providing starting from the start of the order processing. That data will describe manufacturing events related to the customers’ orders, and all the information about distribution and invoices for those orders.
The main features of the OSOL are:
- Basic Search,
- Guest Search,
- Standard/Custom Reports.
The performance of those features (i.e. how fast they are executed for the users) is regularly monitored at the client’s company. The client’s staff creates reports on those three OSOL functions’ performance every day. Performance reports were previously created manually, through usage of SQL scripts, Brio, MS Excel and PowerPoint applications.
The main goal of the Application Performance Report Generator is to deliver an efficient tool for automatically generating performance reports on OSOL usage. That tool can retrieve performance data from the reporting database and generate resulted performance reports to the output MS Excel file. So, it can eliminate most of the manual actions, performed previously.
This component provides the infrastructure services, which includes the basic services managing user, configuration data, sending emails, performing authentication, resetting password, and managing pertinent dates. It also defines the model classes that are shared between layers and modules. The services interfaces are under Ibm.PerformanceReport.InfrastructureServices namespace, the services implementations are under Ibm.PerformanceReport.InfrastructureServices.Impl namespace, and the models are under Ibm.PerformanceReport.Models.
Final Submission Guidelines
N/A