Software Quality Assurance Plan



Software Quality Assurance Plan

For Hotel Reservation System (HRS)

Version 1.0

Submitted in partial fulfillment of the requirements of the degree of MSE

Cem Oguzhan

CIS 895 – MSE Project

Kansas State University

1. Purpose 3

2. References 3

3. Management 3

3.1. Organization 3

3.2. Responsibilities 3

3.3. Tasks 4

4. Documentation 4

5. Standards, Practices, Conventions, and Metrics 4

6. Reviews and Audits 4

7. Test and Problem Reporting 4

8. Tools, Techniques, and Methodologies 4

9. Deliverables 4

Purpose

The purpose of this document is to define Software Quality Assurance (SQA) plan for the MSE project .The SQL plan will be implemented throughout the project, until the release of the final product.

References

• Vision Document

• Project Plan Document

• IEEE Guide for Software Quality Assurance Planning

• IEEE Standard for Software Quality Assurance Planning

• Lecture notes, CIS 726 Advanced Tech., Dr. Daniel Andresen, Spring 2004

• Morrison Mike, Morrison Joline, “Database-Driven Web Sites”. Second Edition, Thomson Course Technology, 2003

Management

5 Organization

Supervisory Committee:

Dr. Daniel Andresen

Dr. William J. Hankley

Dr. Mitchell L. Neilsen

Major Professor:

Dr. Daniel Andresen

Developer:

Cem Oguzhan

Formal Technical Inspectors:

Esteban Guillen

Kevin Sung

1 Responsibilities

Supervisory Committee:

The committee will be responsible for attending the presentations and reviews at the end of each phase. Also, the committee members will provide feedback and suggestions about the Hotel Reservation System to the developer.

Major Professor:

The major professor will be responsible for supervisory committee responsibilities. Also, the major professor will be responsible for supervising and evaluate of work and progress done by the developer on every 2-3 weeks.

Developer:

The developer will be responsible for all documentation and software implementation of the Hotel Reservation System project. The project plan will describe all the tasks, which will be completed by the developer under the major professor supervising. Also, the developer will meet with the major professor on every 2-3 weeks.

Formal Technical Inspectors:

The formal technical inspectors will be responsible for inspection of the architecture design artifacts and then submit a formal report.

2 Tasks

All tasks that will be performed are documented in the project plan. The project plan includes a Gantt chart, which provides a schedule for each task.

Documentation

All official documentation requirements for MSE project are outlined in the MSE portfolio handbook for the MSE students at . These documents would include a vision document, project plan, software quality assurance plan, action items, formal requirements specification, architecture design, test plan, formal technical inspection, executable architecture prototype, user manual, component design, source code, assessment evaluation, project evaluation, references, and formal technical inspection letters. The committee members will evaluate all the documents.

The all documents will be posted on the web site at .

Standards, Practices, Conventions, and Metrics

Documentation Standard – IEEE standards will be used for all documentation of the project.

Coding Standard –Source code and comments will follow the guidelines in the C# coding standards and style guide.

Metrics – COCOMO model are used to predict project effort.

Reviews and Audits

Three formal presentations will be given by the developer. The committee members will be review and evaluate all the documentation of the each phase. After the each presentation, the committee members will provide feedback on the documents and the prototype demonstration.

Two technical inspectors will inspects the architecture design artifacts and submit a formal report.

Test and Problem Reporting

The developer will develop a test plan, which will outline all test activities. The result of testing will be evaluated and documented. All problems will be reported to the major professor, Dr. Dan Andresen.

Tools, Techniques, and Methodologies

The following tools will be used for Hotel Reservation System project.

• Microsoft Visual Studio .NET IDE – for coding

• C# -for coding

• JavaScript – for coding

• IIS – for web server

• – for web forms

• MS SQL – for database server

• MS Visio – for documentation

• USE 2.0.1 – for formal specification and verification

Deliverables

The following deliverables will be submitted at the end of each phase.

Phase I:

• Vision Document

• Project Plan

• Demonstration

• Software Quality Assurance Plan

Phase II:

• Action Items

• Vision Document

• Project Plan

• Formal Requirements Specification

• Architecture Design

• Test Plan

• Formal Technical Inspection

• Executable Architecture Prototype

Phase III:

• Action Items

• User Manual

• Component Design

• Source Code

• Assessment Evaluation

• Project Evaluation

• References

• Formal Technical Inspection Letters

................
................

In order to avoid copyright disputes, this page is only a partial summary.

Google Online Preview   Download