Download Statistic Monitor of SPMS

Survey
yes no Was this document useful for you?
   Thank you for your participation!

* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project

Document related concepts

SQL wikipedia , lookup

Semantic Web wikipedia , lookup

Clusterpoint wikipedia , lookup

Business intelligence wikipedia , lookup

Web analytics wikipedia , lookup

Transcript
Statistics Monitor of SPMSII
-High level and detailed design
Warrior Team
Pu Su
Heng Tan
Kening Zhang
Overview
• High level design
– High level architecture
– Design issues
• Detailed design
– Design issues
– Detailed design description
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
Three-tier Client-server Architecture
First Tier
Client
(browser, part of
application logic layers)
Second Tier
Application server
(application logic,
connection layers)
Third Tier
Database server
(DBMS layer)
Tasks:
• User interface
Tasks:
• Application logic
• Data processing logic
• connection
Tasks:
• DBMS functions
High level Architecture
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.
Detailed Design Diagrams
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
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
Details Descriptions (contd)
Overall statistics
Separate statistics
Questions ?