Statistics Monitor of SPMSIIStatistics Monitor of SPMSII

WarriorWarrior TeamTeamPu SuPu Su

Heng TanHeng Tan

Kening ZhangKening Zhang

OverviewOverview

• Background• Proposed System• Requirement Specification• Project Management Plan• Testing• Future

BackgroundBackground

• Current System Features– Similar with Source Forge system (http://sourceforge.net/

)• Project hosting• Version control• Bug and issue tracking• Project management• Backups and archives• Communication and collaboration resources

• Current System Shortcoming– Lack of statistic information for the project progress

monitor. (http://132.170.201.217/SPMS/ )

Proposed SystemProposed System

• Based on SPMSI, monitor statistics module is added to provide function of tracing the activities of projects

• Similar with Source Forge system (http://sourceforge.net/ )– Overall Statistics– Separate Detailed Statistics

System Environment & ToolsSystem Environment & Tools

• All software components are Open Source • Apache Web Server MySQL 3.23.33 or greater • PHP4 Scripting Language • Linux Debian 3.0 • System Processor PII/233Mhz or above • System Memory 128MB or greater • Internet connection

Requirement SpecificationRequirement Specification

• Functional Requirements • Interface Requirements • Physical Environment Requirements • Users and Human Factors Requirements • Documentation Requirements • Resource Requirements • Security Requirements• Quality Assurance Requirements

Event TableEvent Table

Event Name External Stimuli External Responses Internal data and state

Overall Statistics Page Request

User types HTTP address of Overall Statistics Webpage and IP packets signal server to send user this webpage

Page sent Apache server logs user IP address, and HTTP request

Seperate Statistics Page Request

User types HTTP address of Separate Statistics Webpage and IP packets signal server to send user this webpage

Page sent Apache server logs user IP address, and HTTP request

Use Case DiagramUse Case Diagram

Use Case DescriptionsUse Case Descriptions

• Use cases from the overall projects' statistics pages and associated pages– Display the overall statistics of all projects after inquiry (Primary: Display the overall statistics of all projects after inquiry (Primary:

Display)Display) 1. Execute inquiry action

2. Display result as a ranking list with percentage (detailed activity data with forms)

3. Update the ranking list with the latest data under updating inquiry

• Alternative: Inquiry action not accepted • Display an error message page if exceptions happen during inquiry

Use Case Descriptions (contd)Use Case Descriptions (contd)

• Use cases from the each project's statistics pages and associated pages– Display the separate statistics of each project after inquiry

(Primary: Display)1. Execute inquiry action 2. Display result as a ranking list with percentage (detailed activity

data with forms) 3. Update the ranking list with the latest data under updating inquiry

• Alternative: Inquiry action not accepted – Display an error message page if exceptions happen during inquiry

Project Team OrganizationProject Team Organization

• Team will use a democratic organization to carry out development of SPMSII project. This will allow everyone to have equal input in decision making and allow the group to make decisions based on the majority rules principle. However, the team do have a team manager to accommodate all the non-technique affairs. – Pu Su, Kening Zhang, Heng Tan are in the team.– All the technique decisions will be discussed and finally made

democratically.– Communication will be handled through email and scheduled

face-to-face meetings when ideas and design need to be decided.

Deliverables TimetableDeliverables Timetable

Artifact Due Dates <some will have

multiple deliveries>

Meeting Minutes In maintenance. Update approximately once every two week

Individual Logs In maintenance. Update when necessary

Group Project

Management Reports N/A

ConOps 10/01/02

Project Plan 10/01/02

SRS 10/01/02

High-Level Design 10/22/02

Detailed Design 10/22/02

Test Plan 10/01/02

User's Manual 11/19/02

Final Test Results 11/19/02

Source, Executable, Build

Instructions 11/19/02

Project Legacy 11/19/02

Software Life Cycle Software Life Cycle

• Basically,waterfall model is used in this project• Rapid prototype may be used in requirement

phase.

Quality AssuranceQuality Assurance

• QA is group effort in the final days of each phase testing. The group will decide unanimously if the project satisfies the requirements and if it does so accurately

Risk ManagementRisk Management

• Inability to coordinate three different developers in the group due to the different schedules– Suggested solution: Utilize email and instant messaging to

overcome scheduling errors

• Inability to coordinate between the client and developers– Suggested solution: Fully used the loop back of the waterfall

model

• Limited time of developers– Suggested solution: improve our work efficiency

Technical Progress MetricsTechnical Progress Metrics

• For requirements phase, the total number of requirements, the number of requirements changes is used

• For OO analysis and design, the number of UML diagrams completed is used.

• For detailed design and code, the number of web pages, classes, and methods is used

Plan for tracking, control, and reporting Plan for tracking, control, and reporting of progressof progress

• Tracking and control will be handled by a website where all group members can keep track of the progress of the pages and upload updates to the development of the web pages.– Each team member will post the following information weekly– Each week, the project manager will: read and analyze the logs

– The project manager will issue a Project Management Report on the

schedule as indicated in the deliverables section above

Overall Objective for Software Overall Objective for Software Test ActivityTest Activity

• Using non-execute test to specification• Using execute test to the software production• Using different test cases to test

Test case ITest case I

• Test Objective: Test the over all project statistics

• Test Description: Test whether the over all project statistics is correct reflected in the monitor. Operate the all monitor operation in all projects, and see whether the monitor can get a reasonable result.

• Test Conditions: See test environment• Expected Results: the project statistics can be

recorded by the monitor correctly

Test case IITest case II

• Test Objective: Test the single project statistics• Test Description: Operate the single project in

all possible operation, and see whether the monitor can reflect the change.

• Test Conditions: See test environment• Expected Results: the change can reflect in the

monitor statistics

Test stopping criteriaTest stopping criteria

• The software qualify assurance policy • Test cases • The object of software qualify assurance

FutureFuture

• Details of Design• Implementation of Statistics Monitor• Integration with SPMSII• Maintenance