Software Quality Management Plan

Slides:



Advertisements
Similar presentations
Understanding Food Safety Management Systems
Advertisements

1 Dr. Ashraf El-Farghly SECC. 2 Level 3 focus on the organization - Best practices are gathered across the organization. - Processes are tailored depending.
Software Quality Assurance Plan
Child Safeguarding Standards
Chapter 7: Key Process Areas for Level 2: Repeatable - Arvind Kabir Yateesh.
Internal verification and external standards moderation.
Project Scope Management
Environmental Management Systems An Overview With Practical Applications.
Project Change Management
1 Certification Chapter 14, Storey. 2 Topics  What is certification?  Various forms of certification  The process of system certification (the planning.
Software life cycle processes Purpose n A new international standard (ISO/IEC 12207:1995(E) that –establishes a common framework for software life cycle.
School of Computing, Dublin Institute of Technology.
Lesson-11 Information System Development
System Testing CS 414 – Software Engineering I Don Bagert January 21, 2003.
Examine Quality Assurance/Quality Control Documentation
Prepared by Long Island Quality Associates, Inc. ISO 9001:2000 Documentation Requirements Based on ISO/TC 176/SC 2 March 2001.
Introduction to Computer Technology
Project Management Lecture 5+6 MS Saba Sahar.
Automated Contract Administration Project PIP Level II Presentation by Lisa A. Bowden August 24, 1999.
Guide to Implementing ISO :2005 for the Food Safety Team
Session No. 3 ICAO Safety Management Standards ICAO SMS Framework
WHAT IS ISO 9000.
How To Apply Quality Management
Introduction to ISO New and modified requirements.
Introduction to Software Quality Assurance (SQA)
SMS Operation.  Internal safety (SMS) audits are used to ensure that the structure of an SMS is sound.  It is also a formal process to ensure continuous.
Understanding ISO 22000:2005 TCISys.com.
Software Configuration Management (SCM)
QA Requirements for DOE Accelerator Safety System Software K. Mahoney Group Leader, Safety Systems TJNAF Presented at the 2008 DOE Accelerator Safety Workshop.
Product Development Chapter 6. Definitions needed: Verification: The process of evaluating compliance to regulations, standards, or specifications.
University of Palestine software engineering department Testing of Software Systems Testing throughout the software life cycle instructor: Tasneem Darwish.
Web Accessibility and Higher Education Presented by: Mr. B., Assistive Technology Specialist Ms. H., Assistant Director, Compliance and Disability Services.
Product Documentation Chapter 5. Required Medical Device Documentation  Business proposal  Product specification  Design specification  Software.
Management Responsibilities. Building a Culture of Safety.
Mechanical Integrity Written Procedures. Lesson Objectives  Describe Required Written Procedures for Establishing an MI Program  List Acceptable Sources.
Copyright 2009  Describe the five project management (PM) process groups, the typical level of activity for each, and the interactions among them  Understand.
BSBPMG505A Manage Project Quality Manage Project Quality Unit Guide Diploma of Project Management Qualification Code BSB51507 Unit Code BSBPMG505A.
SMS Planning.  Safety management addresses all of the operational activities of the entire organization.  The four (4) components of an SMS are: 1)
{ Phases of Project & life cycle Prepared by: Syed ShahRukh Haider.
Program Implementation MM.DD.YY. To comply with the OHSA and regulations To demonstrate management's commitment to health and safety To show employees.
Over View of CENELC Standards for Signalling Applications
Hitting the Leadership Target Through Leadership and Accountability.
Contracts Management Governance Mona El-Chami, Senior Financial Management Specialist World Bank November 2013 Tripoli, Libya.
Student Learning Objectives 1 SCEE Summit Student Learning Objectives District Professional Development is the Key 2.
Module N° 6 – SMS regulation
Presented by: Laurie Camilien-Pietrak, AVS Date: November 4-5, 2009 Federal Aviation Administration FAA Aviation Safety (AVS) Role in V&V.
Chapter 3: The Project Management Process Groups: A Case Study Information Technology Project Management, Fourth Edition Project Execution & Closing Thursday,
P3 Business Analysis. 2 Section F: Project Management F1.The nature of projects F2. Building the Business Case F4. Planning,monitoring and controlling.
The Project Management Process Groups
Configuration Control (Aliases: change control, change management )
B U D I L U H U R U N I V E R S I T Y POST GRADUATE PROGRAM MAGISTER ILMU KOMPUTER (M.Kom) IS PROJECT MANAGEMENT.
Slide 1ICT 327 Management of IT ProjectsSemester 1, 2005 Topic 3 Executing & Controlling & Closing Projects.
An FBI Case Study: Incorporate RIM Into System Development Processes Tammy J. Strickler, CRM Records Automation Section Records Management Division, FBI.
Pipeline Safety Management Systems
Introduction for the Implementation of Software Configuration Management I thought I knew it all !
Requirements & Process Review Report
Project Quality Management
How To Apply Quality Management
Review for Final Exam SWE questions
Software and Systems Integration
Project Management Processes
Software Requirements
Verification and Validation Unit Testing
Chapter 3 Managing the Information Systems Project
AIS Manual (Doc 8126) Air Navigation Procedures for AIM Seminar
Project Management Processes
Product Stewardship ESTA Technical Standards Council 1.
Chapter 3 Managing the Information Systems Project
DRAFT ISO 10006:2017 Revision Overview Quality management systems - Guidelines for quality management in projects ISO/TC176 TG 01.
Unit IV – Chapter 2 V-Test Model.
Presentation transcript:

Software Quality Management Plan By: Coredrees Lindsey

Quality Management Plan Purpose: The quality management plan shows guidance on how quality management will be ensured on the project. It will be ensured through design reviews, documentation, and others protocols. It gives management and the customer a clear understanding of how quality will be maintained and what documentation they can expect addressing quality during the life of the project.

Quality Policy Normally defined in general terms or by referring to other documents, the quality policy expresses the project or the support organization's attitude toward quality and quality practices.

Quality Approach The quality approach often includes extensive reference documentation that supports the quality plan. This includes the documents needed to validate deliverable performance. It will also outline how specific practices such as design reviews and records management will be carried out.

Supporting Documentation For some information incorporated in the quality approach documentation, such as flow charts and external reference, copies (or direction to copies) may be embedded as appendices or in supplemental folders.

Key Approaches Quality Management Plan in a one or two-paged document. Develop and maintain the project software quality assurance plan. Identify lessons learned that could improve process for future products

Quality Control Plan Example

Control Plan A Control Plan is used to document and commutate the initial plan for process control. Also, a Control Plan describes the actions required at each step in the process to assure that all process outputs will be in a state of control.

Safety Personnel Provide system software safely expertise to the (SQ) Software safely to the SQ personnel and/or project personnel as required. Assist in the resolution of any software safety related issues, concerns, and/ or risks identified throughout the project life cycle.

Test The test management processes and products are begins implemented per software management plan and/or test plans. This includes all types of integration testing (verification) and acceptance testing (validation).

References This PowerPoint contained of info from the following websites: Google Wikipedia Yahoo

Questions ??????