1 / 11

SPMSII High-Level and Detailed Design Monitoring

This document provides an overview of the high-level and detailed design of the Statistics Monitor of SPMSII. It covers design issues, architecture, and detailed design descriptions.

williamsong
Download Presentation

SPMSII High-Level and Detailed Design Monitoring

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Statistics Monitor of SPMSII-High level and detailed design WarriorTeam Pu Su Heng Tan Kening Zhang

  2. Overview • High level design • High level architecture • Design issues • Detailed design • Design issues • Detailed design description

  3. High Level Design • Reuse current components efficiently as much as possible (Including the web pages and database operations ), since our system is developed under an existing one. • Keep the same coding style to the current system, with code comment and description in more detail to get the better maintainability • Verify the evaluation algorithm by prototype, since in previous phase it is very ambiguous • Web browser/ Web Server/ DB Server

  4. Three-tier Client-server Architecture • Tasks: • User interface First Tier Client (browser, part of application logic layers) • Tasks: • Application logic • Data processing logic • connection Second Tier Application server (application logic, connection layers) • Tasks: • DBMS functions Third Tier Database server (DBMS layer)

  5. High level Architecture

  6. Detailed Design Issues • Store every project as an object and construct extra two counters for it. One counter is to tag the total number of the same activities, the other counter is just to sum up all the previous counters and get the total number of its all different activities for this project. • To use SQL query to compare and select all the data. • To pass the statistical data to the target web page.

  7. Detailed Design Diagrams

  8. Details Descriptions • Update the proper counter for every project’s activities • If onsite Hits == some activity of a certain project, use SQL query to query the project. • Set the $counter (single for every activity) increasing by 1 for this project. • Set the $total_counter (overall activities for this project ) increasing by 1 for this • Analyze data from database • If onsite Hits ==overall statistics • Use SQL query to get the all the projects’ $total_counter, then by comparing these counters sort all the projects. • Create percentage data for every project according to all the projects’ overall statistics • Add the percentage data as an attribute to the corresponding project • If onsite Hits ==separate statistics for certain project • Use SQL query to get this projects’ $counter for every activity

  9. Details Descriptions (contd) • Display the data • If onsite Hits ==overall statistics • Pass the every project’s percentage data and the project name to the target web page. • Display the project by rank according to their percentage data. • If onsite Hits ==separate statistics for certain project • Pass this project’s every activity name and its corresponding counter to the target web page. • Display the project’s all activities statistics

  10. Details Descriptions (contd) Overall statistics Separate statistics

  11. Questions ?

More Related