Essay: Project proposal: Fashion Shop website project

Summary :
Special Web project displays clothes, shoes, bags, etc., the user can login to the site and buy what suits him, showing the price of each piece, it is also allowing the user to put information about it, such as: the place where the lives and email address to be connected to the piece chosen as site aims to make it easier for the user and provide comfort to him
1.0 Purpose
The purpose of this Software Quality Assurance (SQA) Plan is to establish the goals, processes, and responsibilities required to implement effective quality assurance functions for the Fashion shop project.
The fashion shop Software Quality Assurance Plan provides the framework necessary to ensure a consistent approach to software quality assurance throughout the project life cycle. It defines the approach that will be used by the SAM and Software Quality (SQ) personnel to monitor and assess software development processes and products to provide objective insight into the maturity and quality of the software. The systematic monitoring of <Project Name> products, processes, and services will be evaluated to ensure they meet requirements and comply with National Aeronautics and Space Administration (NASA), Goddard Space Flight Center (GSFC), and fashionshop policies, standards, and procedures, as well as applicable Institute of Electrical and Electronic Engineers (IEEE) standards.
1.1 Scope
This plan covers SQA activities throughout the phases of this project e.g.’ Objectives, Architecture, Implementation’
The site is selling online to save time and convenience to the user, the site has been the work of a language PHP
2.0 Reference Documents
The following documents were used or referenced in the development of this plan:
‘ NASA-STD-8719.13, NASA Software Safety Standard
‘ NASA-STD-8739.8, NASA Software Assurance Standard
‘ Fashion shop System Implementation Plan (SIP)
‘ Fashion shop Software Management Plan (or Product Plan)
‘ Fashion shop Statement of Work (SOW)
3.0 Management
This section describes the management organizational structure, its roles and responsibilities, and the software quality tasks to be performed.
3.1 Management Organization
Fashion shop website efforts are supported by numerous entities, organizations and personnel.
The organization consists of
‘ QA Manager: V. Domenico from DOE Software Mgmt.
‘ SQA Team: M. Leijten, S.C.H. Bego and I. Van from DOE Software Mgmt.
‘ System Owner: M. Raffaello from HR-XXX Company
‘ QA Consultant: G. Garibaldi from DOE Software Mgmt.
‘ Project Manager: A. Michelangelo from DOE Software Mgmt.
3.2 Tasks
The responsibilities of the developer are as follows:
‘ Develop the requirement specification and cost estimation for the project
‘ Develop the design plan and test plan for testing the tool
‘ Implement and test the application and deliver the application along with the necessary documentation
‘ Give a formal presentation to the committee on completion of the analysis, design and testing phases. The committee reviews the developer’s work and provides feedback/suggestions.
‘ Planning, coordinating, testing and assessing all aspects of quality issues.
The responsibilities of the committee members are to:
‘ Review the work performed by the developer
‘ Provide feedback and advice
4.0 Documentation
In addition to this document, the essential documentation will include:
The Software Requirements Specification (SRS), which
‘ Prescribes each of the essential requirements (functions, performances, design constraints and attributes) of the software and external interfaces
‘ Objectively verifies achievement of each requirement by a prescribed method (e.g. Inspection, analysis, demonstration or test)
‘ Facilitates traceability of requirements specification to product delivery.
‘ Gives estimates of the cost/effort for developing the product including a project plan
4.1 Standards
‘ Document standards ‘ MSE Portfolio
‘ Coding standards ‘ php,css
‘ Coding Documents standards ‘ php Documentation
‘ Test Standards ‘ IEEE Standard for software test documentation
4.1.1 Metrics
‘ LOC – lines of code is used to measure the size of the softwar.
4.1.2 Project Reviews
The Committee will perform a review at the 3 stages of the project . This review will determine whether the requirements have been met for the deliverable, check that the product meets the requirements, ensure that the SQA plan has been adhered to, verify the performance of the software and ensure that acceptance testing is carried out. In addition the developer will conduct a Formal Technical Review after the design phase. A design checklist will be used and the developer will check to see whether his/her design meets the checklist criteria.