Database Manganement SQA Plan

Supervisoer: Sir Farhan Rasheed

Submitted By: Abdul Wahab (Bsf1907825)

Muhammad Javed Naro (Bsf1907789)

Purpose:

The purpose of this Software Quality Assurance (SQA) Plan is to establish a framework for ensuring
the quality and reliability of the Database Management. It outlines the processes, activities, roles, and
responsibilities related to software quality assurance throughout the project lifecycle.

Scope:

This plan applies to the development, testing, and maintenance phases of the Database
Management. It encompasses all aspects of software quality assurance, including documentation,
standards, practices, reviews, testing, problem reporting, tools, training, risk management, and record
management.

Reference Documents

• Project requirements and specifications

• Design documents
• Test plans and procedures
• Software development standards and guidelines
• Relevant industry standards and best practices

Management Organization:

Project Office is responsible for overseeing the overall project management activities, including
resource allocation, scheduling, and coordination.

Assurance Management Office:

The Assurance Management Office is responsible for managing the software quality assurance
process, ensuring compliance with standards and procedures, and providing guidance and support
to the project team.

Tasks:

Product Assessments Regular assessments of the Database Managment will be conducted to

evaluate the quality and reliability of the software. This includes code reviews, inspections, and
walkthroughs to identify and address any defects or deviations from the defined standards.

Process Assessments Periodic assessments of the software development and testing processes will
be performed to identify areas for improvement and ensure adherence to established procedures.
This includes process audits, reviews of project documentation, and analysis of process metrics.

Roles and Responsibility:

Software Assurance Manager (SAM) The SAM is responsible for overseeing the software quality
assurance activities, ensuring compliance with the SQA plan, and reporting any quality-related issues
to the project management.

Software Quality Personnel:

Software quality personnel are responsible for executing quality assurance tasks such as code
reviews, inspections, and testing. They ensure that the software meets the defined quality standards
and report any defects or non-compliance.

Other OSSMA Personnel:

Other Office of Safety and Mission Assurance (OSSMA) personnel may be involved in providing
support, guidance, and expertise related to specific quality assurance activities as needed.

Software Assurance Estimated Resources:

The resources required for software quality assurance activities, including personnel, tools, and
infrastructure, will be estimated and allocated based on project needs and complexity.

Documentation:
 Purpose Documentation serves as a record of software quality assurance activities, processes, and
outcomes. It provides a reference for understanding the quality management approach and ensures
traceability throughout the project.

Minimum Documentation Requirement The minimum documentation required includes:

• SQA plan
• Test plans and procedures
• Review reports
• Problem reports and corrective action documentation
• Process audit reports
• Training records

Standards, Practices, Conventions, and Metrics:

Purpose Standards, practices, conventions, and metrics provide a framework for ensuring
consistency, reliability, and quality in software development. They define guidelines and criteria for
software design, coding, testing, and documentation.

Software Quality Program:

A comprehensive software quality program will be established, encompassing industry best practices
and tailored to the specific needs of the Tourism Management System project. It will include the
definition of quality standards, practices, conventions, and metrics.

Standard Metrics:

Standard metrics, such as defect density, code coverage, and test effectiveness, will be defined to
measure and monitor the quality of the software throughout the development lifecycle. These
metrics will be used to assess progress, identify trends, and drive continuous improvement.

Software Reviews:

Purpose Software reviews are conducted to evaluate the quality, completeness, and compliance of
the software artifacts. They provide an opportunity to identify and address defects, deviations, and
potential risks early in the development process.

Minimum Software Reviews The minimum software reviews to be conducted include:

• Requirements review
• Design review
• Code review
• Test plan review
• Test case review
• Inspection or walkthrough of key deliverables

Test Comprehensive testing will be performed to verify the functionality, performance, and reliability
of the Tourism Management System. This includes unit testing, integration testing, system testing,
and acceptance testing. Test plans, procedures, and test cases will be documented and executed.

Problem Reporting and Corrective Action:

A problem reporting and corrective action process will be established to capture and track defects,
non-compliance, and issues identified during quality assurance activities. The process will ensure that
appropriate actions are taken to address the reported problems and prevent their recurrence.

Software Quality Tools Additional:

Software quality tools may be employed to support various quality assurance tasks, such as code
analysis tools, automated testing tools, and static analysis tools. The selection and use of these tools
will be based on project requirements and industry best practices.

Project Tools:

Project-specific tools, such as project management software, collaboration platforms, and

documentation management systems, will be utilized to facilitate communication, coordination, and
documentation throughout the project.

Media Control:

Media control procedures will be established to ensure the integrity and security of software and
documentation. This includes version control, access control, backup procedures, and storage
requirements.

Supplier Control:

If external suppliers or vendors are involved in the development or delivery of components or

services related to the Tourism Management System, supplier control procedures will be
implemented to ensure their compliance with quality standards and requirements.

Record Collection:
 Maintenance, and Retention Procedures will be defined for collecting, maintaining, and retaining
records related to software quality assurance activities. This includes the storage, retrieval, and
archiving of documentation, test results, reviews, and problem reports.

Training:

Training programs will be established to ensure that personnel involved in software quality assurance
activities are equipped with the necessary knowledge and skills. Training needs will be identified, and
appropriate training resources will be provided to enhance competency and ensure adherence to
quality practices.

Risk Management:

A risk management process will be implemented to identify, assess, and mitigate risks associated
with software quality. Risk analysis and mitigation strategies will be documented and regularly
reviewed to minimize the impact of potential risks on the project.

Glossary

A glossary of relevant terms and definitions will be maintained to ensure a common understanding
of key concepts and terminology used in the SQA plan and related documents.