1 sqa13b IEEE Standard for SQAP u IEEE Std 730-1989 –Standard for Software Quality Assurance Plans –12 pages u IEEE Guide for Software Quality Assurance.

Slides:



Advertisements
Similar presentations
1 09/10/02 WG12 Software Primer For RTVIS Committee September 10, 2002.
Advertisements

Configuration Management
Software Quality Assurance Plan
Software Quality Assurance Plan
More CMM Part Two : Details.
How to Document A Business Management System
Configuration Management Managing Change. Points to Ponder Which is more important?  stability  progress Why is change potentially dangerous?
Stepan Potiyenko ISS Sr.SW Developer.
Overview Lesson 10,11 - Software Quality Assurance
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.
Copyright © 2006 Software Quality Research Laboratory DANSE Software Quality Assurance Tom Swain Software Quality Research Laboratory University of Tennessee.
DITSCAP Phase 2 - Verification Pramod Jampala Christopher Swenson.
Software Quality Management
Difference between project and other assignments real customer before programming: negotiations with client to clarify requirements often changes.
S R S S ystem R equirements S pecification Specifying the Specifications.
Development plan and quality plan for your Project
Software Verification and Validation (V&V) By Roger U. Fujii Presented by Donovan Faustino.
Software Configuration Management
CSSE 375 Software Construction and Evolution: Configuration Management
Configuration Management Avoiding Costly Confusion mostly stolen from Chapter 27 of Pressman.
OHT 2.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 Software Quality assurance (SQA) SWE 333 Dr Khalid Alnafjan
CEN 4935 Senior Software Engineering Project Joe Voelmle.
S/W Project Management
CHAPTER 5 Infrastructure Components PART I. 2 ESGD5125 SEM II 2009/2010 Dr. Samy Abu Naser 2 Learning Objectives: To discuss: The need for SQA procedures.
UNIT-II Chapter : Software Quality Assurance(SQA)
Introduction to Software Quality Assurance (SQA)
INFORMATION SYSTEM APPLICATIONS System Development Life Cycle.
Software Engineering Term Paper
S OFTWARE Q UALITY QA: Quality Assurance By: MSMZ.
Chapter 8 : Software Quality Assurance Juthawut Chantharamalee Curriculum of Computer Science Faculty of Science and Technology, Suan Dusit University.
Software Quality Assurance
Software Quality Assurance Activities
Michael Dermody September 2010  Capability Maturity Model Integration ◦ Is a Trademark owned by the Software Engineering Institute (SEI) of Carnegie.
Software System Engineering: A tutorial
程建群 博士 (Dr. Jason Cheng) 年 03 月 Software Engineering Part 06.
Lecture #9 Project Quality Management Quality Processes- Quality Assurance and Quality Control Ghazala Amin.
Software Quality Assurance Lecture #2 By: Faraz Ahmed.
Plan project Integrate & test system Analyze requirements Design Maintain Test unitsImplement Software Engineering Roadmap: Chapter 1 Focus Identify corpor-
S Q A.
“Software Life Cycle Processes”
1.  Describe an overall framework for project integration management ◦ RelatIion to the other project management knowledge areas and the project life.
Quality Activity Matrix Presented by Sandra Toalston President, SanSeek 1.
Steven Kolenda, Jacob Brown, Johnpaul Barrieau, Jen Bilotta, Felix Rohrer CS673 Software Engineering
KS3 Phase4 Client Server Monitoring System October 1, 2008 by Stephen, Seema, Kam, Shpetim.
CSSE 375 Software Construction and Evolution: More SCM, and a loop back to Feathers! Shawn and Steve Left – On big systems, SCM is a well-defined process.
CSC 480 Software Engineering
SE513 Software Quality Assurance Lecture12: Software Reliability and Quality Management Standards.
1 Definition Introduction and key stages Steps and standards used Plan Team Characteristics Implementation documentation Reviews & Audit Software Quality.
6/6/ SOFTWARE LIFE CYCLE OVERVIEW Professor Ron Kenett Tel Aviv University School of Engineering.
Project Management Methodology Project Closing. Project closing stage Must be performed for all projects, successfully completed or shut off by management.
by: Er. Manu Bansal Deptt of IT Software Quality Assurance.
Introduction for the Implementation of Software Configuration Management I thought I knew it all !
SQA project process standards IEEE software engineering standards
Chapter 11: Software Configuration Management
Software Quality Assurance (SQA)
SQA project process standards IEEE software engineering standards
IEEE Std 1074: Standard for Software Lifecycle
12207.
د. حنان الداقيز خريف /28/2016 Software Quality Assurance ضمان جودة البرمجيات ITSE421 5 – The components of the SQA.
Software and System Delivery
System Requirements Specification
CMMI – Staged Representation
ارائه كننده: شاهين انتصاري
Software Quality Assurance Plans
Standards.
Chapter 11: Software Configuration Management
Mumtaz Ali Rajput +92 – SOFTWARE PROJECTMANAGMENT– WEEK 4 Mumtaz Ali Rajput +92 – 301-
HHS Child Welfare National IT Managers' Meeting
Software Reviews.
Presentation transcript:

1 sqa13b IEEE Standard for SQAP u IEEE Std –Standard for Software Quality Assurance Plans –12 pages u IEEE Guide for Software Quality Assurance Planning –87 pages

2 sqa13b Contents of SQA Plan (sect 1&2) u 1. Purpose –list software covered –state portion of software life cycle covered –(draft) u 2. Reference Documents –complete list of documents referenced elsewhere

3 sqa13b Sect 3 - Management u organization - depict structure of org. –responsibilities u tasks –tasks to be performed –relationship between tasks and checkpoints –sequence of tasks u responsibilities –organizational elements responsible for each task

4 sqa13b Sect 4 - Documentation u identify required documents u state how documents will be evaluated u minimum documents –SRS - Software Requirements Specification –SDD - Software Design Description –SVVP - S Verification and Validation Plan –SVVR - S Verification and Validation Report –User documentation - manual, guide –SCMP - S Configuration Management Plan

5 sqa13b Sect 5- Standards, Practices, Conventions and Metrics u Identify S,P,C,and M to be applied u How compliance is to be monitored and assured u Minimum –documentation standards, logic structure standards, coding standards, testing standards –selected sqa product and process metrics »e,g, branch, decision points

6 sqa13b Sect 6 - Reviews and Audits u purpose –define what reviews/audits will be done –how they will be accomplished –what further actions are required u Minimum –Software Requirements Reviews –Preliminary Design Review »evaluate technical adequacy of top-level design

7 sqa13b Min Set of Reviews/Audits (cont) –Critical Design Review »acceptability of detailed designs –Software Verification and Validation Plan Review »adequacy of planned verification and validation –Functional Audit »all requirements in SRS have been met –Physical Audit »software and documents are consistent and ready –In-Process Audit –Managerial Reviews

8 sqa13b Sect 7 - Test u All tests not included in SVVP

9 sqa13b Sect 8 - Problem Reporting u Practices and Procedures for reporting, tracking, and resolving problems u Organizational responsibilities

10 sqa13b Sect 9 - Tools, Techniques and Methodologies u identify the special software tools, techniques and methodologies –purpose –describe use

11 sqa13b The rest u 10 - Code Control u 11 - Media Control u 12 - Supplier Control (for outsourcing) u 13 - Records - collection, maint and retention u 14 - Training u 15 - Risk Management

12 sqa13b L13bS12 - Individual Task u Write an SQA Plan for an organization which has 100 software engineers, 20 team leaders, 2 levels of managers above the teams and 10 engineers in the QA department. u Turn/fax in