0% found this document useful (0 votes)
97 views

Software Development Life Cycle & Quality Assurance SQA

The document discusses quality assurance activities throughout the software development life cycle (SDLC). It states that QA should follow each stage of the SDLC, from project planning to testing. Early QA catches issues when they are cheaper to fix, before testing. QA activities ensure quality of processes and products. The document also covers QA infrastructure, standards like ISO and CMMI, and the relationship between QA and SDLC.

Uploaded by

Aqib Asad
Copyright
© © All Rights Reserved
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
97 views

Software Development Life Cycle & Quality Assurance SQA

The document discusses quality assurance activities throughout the software development life cycle (SDLC). It states that QA should follow each stage of the SDLC, from project planning to testing. Early QA catches issues when they are cheaper to fix, before testing. QA activities ensure quality of processes and products. The document also covers QA infrastructure, standards like ISO and CMMI, and the relationship between QA and SDLC.

Uploaded by

Aqib Asad
Copyright
© © All Rights Reserved
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
You are on page 1/ 15

Software Development Life Cycle &

SQA
Quality Assurance

www.company.com
Software Development Life Cycle &
SQA
Quality Assurance
In order to be efficient, Quality Assurance activities should follow every
stage in the Software Life Cycle. Structure wise it as a concept of QA
Support Ring, as shown in the diagram.
For each activity in the Software Life Cycle, there is one or more QA
support activities focusing on ensuring the Quality of the process and of
the resulting product
Having Quality Assurance activities for all stages of the Software Life
Cycle can bring significant savings. In fact, the earlier QA is applied, the
higher is its ROI. Finding a problem in Requirements can cost ten or
more times cheaper to fix than fixing the same issues when found in
testing: fighting a paper tiger is easier than a live one..

www.company.com
Software Development Life Cycle &
SQA
Quality Assurance
Project Plan Review – before you start investing time, money and
resources in the project, it's worth checking out whether the plan has
covered all the bases, if it's feasible in terms of timeline and resources,
or even – simple – if it is complete.

Requirements Review – once the Requirements are written but before


more resources are engaged in translating them into design and code,
it's useful to review them for correctness, completeness, testability, etc. -
and fix the issues while they are still on paper. 

Pre-release Quality Status Evaluation– you've executed your tests.


Defects were logged, and now it's time to decide what to do next: to
release or not to release... An analysis of application's Quality level in
terms of the impact of the defects discovered can help to make a rational
decision based on sound data obtained through Quality metrics. 

www.company.com
SQA Infrastructure
SQA

• Procedures and work instruction.


• Quality support devices like templates an checklists.
• „Staff SQA training and certification activities.
• „Preventive and corrective actions.
• „Software configuration management, documentation and quality
records control.
• What activities have to be performed?
• How should each activity be performed?
• When should the activity be performed?
• Where should the activity be performed?
• Who should perform the activity?

www.company.com
SQA Infrastructure
SQA

www.company.com
Relationship between SDLC & SQA
SQA

• SDLC deals with Req, Design, Coding & Testing. SQA life 
cycle includes SDLC + configuration management + Audit + 
Metrics + Continual Improvement. 

It is important to understand that SQA is not Testing. Both 


are different. SQA is process oriented, Testing is product 
oriented. SQA is process oriented but QC is oriented towrds
prevention 
• SQA Life Cycle Includes SDLC+Process oriented

www.company.com
Relationship between SDLC & SQA
SQA

STLC is software test life cycle it starts with


• Preparing the test strategy.
• Preparing the test plan.
• Creating the test environment.
• Writing the test cases.
• Creating test scripts.
• Executing the test scripts.
• Analyzing the results and reporting the bugs.
• Doing regression testing.

www.company.com
Relationship between SDLC & SQA
SQA

SDLC is software or system development life cycle,


phases are...
• Project initiation.
• Requirement gathering and documenting.
• Designing.
• Coding and unit testing.
• Integration testing.
• System testing.
• Installation and acceptance testing. " Support or maintenance.

www.company.com
Software Quality Standards
SQA

• Software Quality ISO Standards


• Capability Maturity Model Integration – CMMI
• Level 1
• Level 2
• Level 3
• Level 4
• Level 5
• Other standards.

www.company.com
Software Quality ISO Standards
SQA (http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_tc_browse.htm?
commid=45086) – List of standards

• The ISO/IEC 9126 standard describes a software quality model which categorizes
software quality into six characteristics (factors) which are sub-divided into sub-
characteristics (criteria). The characteristics are manifested externally when the
software is used as a consequence of internal software attributes.
• The internal software attributes are measured by means of internal metrics (e.g.,
monitoring of software development before delivery). Examples of internal metrics
are given in ISO 9126-3. The quality characteristics are measured externally by
means of external metrics (e.g., evaluation of software products to be delivered).
Examples of external metrics are given in ISO 9126-2.
• The ISO 9126-1 software quality model identifies 6 main quality characteristics,
namely:
• Functionality
• Reliability
• Usability
• Efficiency
• Maintainability
• Portability

www.company.com
The ISO/IEC 25000 series of standards
SQA (http://iso25000.com/index.php/en/iso-25000-standards)

www.company.com
Capability Maturity Model Integration
SQA
CMMI
Capability Maturity Model Integration (CMMI) is a process improvement
training and appraisal program and service administered and marketed by
Carnegie Mellon University and required by many DOD and U.S.
Government contracts, especially in software development. Carnegie Mellon
University claims CMMI can be used to guide process improvement across
a project, division, or an entire organization.

CMMI currently addresses three areas of interest:


• Product and service development — CMMI for Development (CMMI-DEV),
• Service establishment, management, — CMMI for Services (CMMI-SVC), and
• Product and service acquisition — CMMI for Acquisition (CMMI-ACQ).

To reach a particular level, an organization satisfies all of the goals of the


process area or set of process areas that are targeted for improvement,
regardless of whether it is a capability or a maturity level.

www.company.com
Capability Maturity Model Integration
SQA
CMMI

www.company.com
Capability Maturity Model Integration
SQA
CMMI – Assignment 02
• What is CMMI level (1-5) – three to four pager.
• List of CMMI level 5 software companies in Pakistan and in the
World?
• List of CMMI level 4 software companies in Pakistan and in the
World?
• List of CMMI level 3 software companies in Pakistan and in the
World?
• List of CMMI level 2 software companies in Pakistan and in the
World?
• What is PASHA?

www.company.com
Other standards.
SQA

CISQ Standard
• Functional size standard
• Software quality standard
The initial version of the CISQ Software Quality specification was first
published in 2012. The software quality characteristics included in this
specification were selected in the CISQ Executive Workshops held in
Washington D.C.; Frankfurt, Germany; and Bangalore, India. These
quality characteristics include:
 
-        Reliability
-        Performance Efficiency
-        Security
-        Maintainability
 
The CISQ quality standard is going through the OMG(Object
Management Group) standardization process and each quality measure
is expected to become a standard in 2015

www.company.com

You might also like