KS3 Phase4

Client Server Monitoring System

October 1, 2008 by Stephen, Seema, Kam, Shpetim

Software Project Management PlanPurpose

This document specifies the scope, management structure, schedule and process of the project. It serves as the overview of the process and provides context to the other documents.

SPMP OverviewManagement StructurePlanning and ControlTechnical ProcessSupporting Plans

SPMP LifecycleThe Project Management Plan is to be created in the initial phase and updated throughout all phases of the

Software Configuration Management PlanPurpose

This document is to specify how the team is to track and various versions of the project artifacts and the changes made to them.

SCMP OverviewSCM Management (Team roles, policies, procedures)SCM Activities (Identification, Control, Account, Reviews)SCM Schedule (Timeline for SCM Activities)SCM ResourcesSCM Plan Maintenance

SCMP LifecycleThe Project Management Plan is to be created in the initial phase and updated as need be.

Software Quality Assurance Plan (SQAP)Purpose

This document is to specify the manner in which quality goals can be achieved for the project, Client Server Monitoring System. It describes the Quality Organization and Responsibilities, Quality Goals and Procedure, Documents required for quality assurance and Techniques used to ensure quality.Management

Organization

Tasks Responsibilities

Documentation : SCMP, SRS, SVVP, STD, SDDStandards, Practices, Conventions and metricsReviews and Audits : periodically access the quality of the applicationTestsProblem Reporting and Corrective ActionsTools, techniques and methodologies: ChecklistsCode Control : Part of SCMPRisk Management

Software Verification and Validation Plan (SVVP)

PurposeVerification and Validation strives to ensure that the quality is built into the software

and that the software satisfies business functional requirements. Software verification and validation employs review, analysis, and testing techniques to determine whether a software product and its intermediate deliverables comply with requirements. These requirements include both business functional capabilities and quality attributes.

V & V OverviewOrganization

Master Schedule

Software Integrity

Resource summary

Responsibilities

Life Cycle of V & V

Management of V & V, Concept Phase of V & V, Requirement phase, Design phase , Implementation phase, Test phase, Installation and checkout phase, Operation and maintenance phase.

Software V & V Reporting

Data Flow Diagram (Used in SDD)

Run the Monitoring Software

Define what to be monitored

Observe the Server feedback

Customer

Alert Customer

Receive feedback from the Server

Collect Data from customer Machine

Send Data to the Server

Store Data if Server down

Connect to the Server over the Internet

Monitoring Software

Receive Data from customer

Analayse DataServer

Send Feedback to Customer

Use Case Diagram (Used in SDD)

Client

Server

Monitor

No Event

New Event...

Data Not ValidOr Server Down

Data Received and Valid

State Transition Diagram (Used in SDD)

DCA

URLDataTimeDate

Connect()getTime()getDate()Alert()ReadData()SendData()StoreData()

DAS

DataClientNameEventname2

ReceiveData()CompareData()SendFeedBack()

User

NamePasswordMachineName

GetName()GetPass()GetMachineName()SaveName()SavePasss()ObserevAlert()

1 0..*

1

1

Class Diagram (Used in SDD)

:Customer :Client :Server

RunClient()

Configure()

ConnectToServer(URL)

RegisterEvent()

SendEvent()

AnalyseEvent()

AlertClient()

ShowEvent()

Sequence Diagram (Used in SDD)

Software Test DocumentationContent:Introduction:

•Goals•Assumptions•Risks and assets•References

Features to be tested:

Features not to be tested:

Approach:•Test objectives•Types of testing

Artefacts:•Test design specification•Test case specification•Test reports

Test elements:•Staffing, roles and responsibilities, schedule, resources

User manual

Content:

•General information and installation•Environment•System requirements

•System components explanation•Data collection agent•Data analysis server

•Data interpretation

•Troubleshooting

Screenshots will be used in this document to better explain the system to users