User Tag List

Thanks Thanks:  0
Likes Likes:  0
Dislikes Dislikes:  0
Results 1 to 5 of 5

Thread: Quality Plan.

  1. #1
    Points for Confirmed Friends

    Quality Plan.

    Hello, Our web based product is in a design stage and I would like to provide the customer a document to assure that the product is going to be upto the standards I have few bullets like the Security implementation will make sure that the data will be encrypted, Usability studies will be conducted to assure the Usability of the application... etc. Can you guys give me more ideas what else can I talk about in the document. You help is greatly appretiated. thanks.


  2. #2
    Senior Member
    Join Date
    Feb 2001
    Colorado Springs, CO, USA
    Post Thanks / Like
    0 Post(s)
    0 Thread(s)
    Total Downloaded

    Re: Quality Plan.

    One option, since it is the design stage, is to use this as an opportunity to involve the customer in the process. Ask them how they would like to see the software tested. This will not only show them that you care about their concerns but it may raise some issues during the design stage rather than a later stage like system test or user acceptance testing. You can also use their main concerns as a way to determine the highest risk areas to concentrate on.
    Tim Van Tongeren

  3. #3
    Senior Member
    Join Date
    Jun 2001
    United Kingdom
    Post Thanks / Like
    0 Post(s)
    1 Thread(s)
    Total Downloaded

    Re: Quality Plan.

    It does depend on your definition of a "Quality Plan". Here is my definition of what it is and what should be in it. It may or may not be of some use to you.

    The Quality Plan defines how quality will be built in. This following guidelines are to the key parts of the Quality Plan.

    Make a point of stating what phase the project is in - remember that the Quality Plan may need updating at future phases
    State related documentation - if none, query whether you are writing too early, or whether quality already going wrong.

    Quality Objectives
    Define what the quality objectives are
    Each objective must be S.M.A.R.T., i.e.

    The following are examples of types of Quality Objectives:
    * Conformance to Requirements
    * Security
    * Auditability
    * Performance
    * Operability
    * Flexibility
    * Maintainability

    Roles and Responsibilities
    Define who is in the project team, what their role is and what they own

    Define what will be produced, by whom
    Determine what roles are required, minimum of :
    * Project Board
    * Project Manager
    * Sponsor
    * Support Manager
    * Test Manager

    Need a full list of all project deliverables, who will produce them, who will signoff and the purpose of signoff. Each project will need at least:
    * Project Initiation Document
    * Requirements Specification
    * Functional Specification
    * Project Plan
    * Quality Plan
    * Test Plan
    Each deliverable will required to be signed off. It is important to document what signoff means for each role and for each document
    Following are a list of typical types of signoffs:
    * Business Signoff - "I agree that you have met my needs"
    * Managerial Signoff - "I agree with your approach and will support it"
    * Signoff to provide resources - "I agree to provide you with people/equipment when you need it"
    * Signoff to actions - "I agree to perform the actions you have requested by the dates you need"
    * Report Signoff - "I agree that you have accurately reported events"

    Project Processes
    For most projects the processes described in the process manual will be used, however, as not all projects are the same, there is a need, at the Quality Plan stage, to determine which processes are applicable to this project, which will not be used and which will be used but will need to be modified (for this project only). Therefore, the Quality Plan defines:
    * Which processes will be used for this project
    * What extra processes are required
    * Which "standard" processes will not be used, or will be modified
    * To what level will the process be used
    * Who will manage the process
    * What tools will be used

    How the project will be managed

    An important part of managing Quality is how the project as a whole will be managed, so the following needs defining:

    * Project Controls
    * Project Reporting
    * Project Meetings
    * Project Records
    * Project Assurance
    * Post Implementation Review

    The final act is for the Author to include, or ensure the inclusion of all the quality activities described in the Quality Plan on the Project Plan. These activities must be monitored as every other activity

    It is recommended that the Quality Plan be reviewed and, if necessary, updated at the end of every development phase.


  4. #4
    Join Date
    Apr 2002
    Toronto, Ontario, Canada
    Post Thanks / Like
    0 Post(s)
    0 Thread(s)
    Total Downloaded

    Re: Quality Plan.

    I agree with peternairn.
    In our development shop, QA plan includes checklists for different phases. Every project member is responsible to compliance with Checklists.
    At QA audit stage, auditor use these checklists as a QA Tool to verify compliance.


  5. #5
    Points for Confirmed Friends

    Re: Quality Plan.

    wonderful guys!!! thanks soo much for your time. Looking forward for more feedbacks please.

    thanks indeed!!
    Quality Serv



Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
Search Engine Optimisation provided by DragonByte SEO v2.0.36 (Pro) - vBulletin Mods & Addons Copyright © 2016 DragonByte Technologies Ltd.
Resources saved on this page: MySQL 10.34%
vBulletin Optimisation provided by vB Optimise v2.6.4 (Pro) - vBulletin Mods & Addons Copyright © 2016 DragonByte Technologies Ltd.
User Alert System provided by Advanced User Tagging v3.2.8 (Pro) - vBulletin Mods & Addons Copyright © 2016 DragonByte Technologies Ltd.
vBNominate (Lite) - vBulletin Mods & Addons Copyright © 2016 DragonByte Technologies Ltd.
Feedback Buttons provided by Advanced Post Thanks / Like (Pro) - vBulletin Mods & Addons Copyright © 2016 DragonByte Technologies Ltd.
Username Changing provided by Username Change (Free) - vBulletin Mods & Addons Copyright © 2016 DragonByte Technologies Ltd.
BetaSoft Inc.
Digital Point modules: Sphinx-based search
All times are GMT -8. The time now is 04:48 PM.

Copyright BetaSoft Inc.