Saturday, January 28, 2012

Software project: JS feed for joomla - Quality Plan

Introduction
The introduction of Quality Assurance Plan provides an overview of the entire document. It includes the purpose, scope, definitions, acronyms, abbreviations, references, and overview of this Quality Assurance Plan.

Purpose
The purpose of this document is to provide a single point of reference on the topic of quality for “JS Feeds for Joomla” project. This document does not contain details review and evaluation techniques, criteria, metrics, etc.

Scope
This is document’s main purpose is to help in quality assurance plan of the “JS Feeds for Joomla” project

Definitions, Acronyms, and Abbreviations
  • GUI - Graphical User Interface
  • UML - Unified Modeling Language
  • Joomla - Joomla is a free and open source CMS or content management system for publishing content on the World Wide Web and intranets. It comprises a model–view–controller (MVC) Web application framework that can be used independently also.
  • API - An application-programming interface (API) is an interface implemented by a software program that enables it to interact with other software. It facilitates interaction between different software programs similar to the way the user interface facilitates interaction between humans and computers.
  • RSS Feeds - a simple XML-based system that allows users to subscribe to their favourite websites. Using RSS, webmasters can put their content into a standardized format.
  • CSM – Content management system.
References
Software Requirements Specification (SRS).

Overview
  • This document describes organization of development process from the point of achieving the highest software quality.
  • The section Quality Objectives describes product quality requirements.
  • The section Management describes the organizational structure of quality assurance department, responsibilities and communication between team members in order to facilitate quality assurance.
  • The section Documentation gives the list of documents, which are designed to check the product’s conformity to quality standards.
  • The section Standards and Guidelines describes Standards and Guidelines, which will be used in product development process.
  • The section Metrics defines the metrics that will be measured at certain control points during product development and that will allow controlling the development process.
  • The section Review and Audit Plan describes in detail schedule, resources engaged, methods and processes that will be used for project Review and Audit.
  • The section Evaluation and Test describes product evaluation plan, and covers the techniques, criteria, metrics, and procedures of evaluation, which include walkthroughs, inspections, and reviews.
  • The section Problem Resolution and Corrective Action describes the principles of reporting, analysis, and problem solving during the project.
  • The section Tools, Techniques, and Methodologies describes Tools, Techniques, and Methodologies used in the project.
  • The section Configuration Management defines all Configuration and Change Control Management (CCM) activities that need to be performed on the course of project and product lifecycle. It provides the details on the schedule of activities, responsibilities assigned, and resources required, including staff, tools, and computers.
  • The section Supplier Controls gives some background on accounting information that will be given to the client during the project.
  • The section Quality Records describes the process of quality issues tracking.
  • The section Risk Management and Risk Management Plan gives the information on how to manage risks associated with the project. This section defines risk management tasks that will be carried out, describes the responsibilities assigned and all additional resources required for the effective risk management.
Full Artical(pdf): PDF DOWNLOAD

Content

Email:

Syndicators/Readers:

FaceBook: