1. KS3 Phase4 Client Server Monitoring System October 1, 2008 by Stephen, Seema, Kam, Shpetim

2. Software Project Management Plan Purpose 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 Overview  Management Structure  Planning and Control  Technical Process  Supporting Plans SPMP Lifecycle  The Project Management Plan is to be created in the initial phase and updated throughout all phases of the

3. Software Configuration Management Plan Purpose 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 Overview  SCM Management (Team roles, policies, procedures)‏  SCM Activities (Identification, Control, Account, Reviews)‏  SCM Schedule (Timeline for SCM Activities)‏  SCM Resources  SCM Plan Maintenance SCMP Lifecycle  The Project Management Plan is to be created in the initial phase and updated as need be.

4. 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, SDD Standards, Practices, Conventions and metrics Reviews and Audits : periodically access the quality of the application Tests Problem Reporting and Corrective Actions Tools, techniques and methodologies: Checklists Code Control : Part of SCMP Risk Management

5. Software Verification and Validation Plan (SVVP)‏ Purpose Verification 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 Overview Organization 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

6. Data Flow Diagram (Used in SDD)‏

7. Use Case Diagram (Used in SDD)‏

8. State Transition Diagram (Used in SDD)‏

9. Class Diagram (Used in SDD)‏

10. Sequence Diagram (Used in SDD)‏

11. Software Test Documentation Content: 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

12. 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