Day 3 meet shilpa measuring software quality and business impact session 3

www.xbosoft.com

1

Webinar March 20 2014 11.00 AM EST

You are at the right place, it’s almost time….10 minute

countdown

WELCOME

XBOSOFT Software Quality Knowledge Center is proud to partner with and

introduce

Shilpa DadhwalCEO and Founder

SQE Labs, Inc.

On the callShilpa Dadhwal, Philip Lew and Jan Princen

Moderator: Carolyn Choh

Shilpa Dadhwal,Founder and CEO,SQE Labs Inc

Philip LewCEO, XBOSoft

Jan PrincenManaging Director, XBOSoft

Agenda

• Introduction XBOsoft• Software Quality – Quick recap of Day 1 and 2• Software quality models • Advantages and impact of using them• Moving on to Day 3

– Barriers and issues to business of software quality– Implications for Senior Management for setting

guidelines– Implications for Project Management for best practices

• Q and A• Today’s meeting March 20th

https://www3.gotomeeting.com/register/886356774


• Specialize in: Software Quality Improvement

• Quality Process Improvement & Testing

• American Company• Located in: San Francisco, Amsterdam &

Beijing• Over 100 Software Quality Experts

XBOSoft Introduction

7

“Proven Results”

“Our products are very complex. We expected a one year ramp up time, but XBO was able to contribute to our release cycles in just 6 months. ."

- Development Vice President, Hyperion-Oracle

“

"The results are very encouraging. Thanks a lot for all the effort put into this project. We really appreciate your work."

- Manager, Quality Assurance, Autodesk

"Everything you've done is impressive and we are quite pleased with the quality of the test cases, well done!So keep up the good work."

- QA Director, CA

Welcome to the Session 3 on ‘Measuring Software Quality –

Its Economic Value’

Shilpa DadhwalFounder & DirectorSQE Labs Inc.

Skype ID : shilpa2dEmail ID : [email protected]

Presentated By:

SQE Labs offers an independent Software Testing and Quality

Assurance services and is committed to improving quality by

providing superior QA solutions to customers

About USA Specialist Independent Software Testing Solutions Provider

Team of Software Quality Engineering professionals having strong

Techno-functional knowledge

Provides services in the areas of Outsourced Software Testing,

Software Testing Consultancy and Software Testing Trainings

Having Offices in Texas (US) and Chandigarh (India)

What is Software Quality?

What is its Economic Value?

How to mange Software Quality?

What are its Attributes?

Why do we need to measure it?

How do we measure it?

Issues while measuring it?

Guidelines for measuring it?

A Specialist Independent Software Testing Solution Provider Questions in Mind

Session 1

Session 2

Session 3

1. QUALITY MODELS for defining Software Quality Attributes

2. ADVANTAGES of measuring Software Quality

3. IMPACT of ‘Software Quality’ on Business

4. BARRIERS to achieve ‘High’ Software Quality

5. ISSUES in measuring Software Quality

6. GUIDELINES for measuring Software Quality

7. PRACTICES to be followed

A Specialist Independent Software Testing Solution Provider Agenda

“Quality is never an accident; it is always the result of intelligent effort.”

– John Ruskin

RemarkA Specialist Independent Software Testing Solutions Provider

QuestionsA Specialist Independent Software Testing Solutions Provider

Do you know the most critical Software Quality Attribute for your product/service?

Do you know how to measure the identified Software Quality Attribute?

Are you able to make right decisions, after measuring the critical Software Quality Attribute?

If any of the above answer is ‘No’, then …….

A quality model is a specification of the required characteristics that a software system must exhibit

A quality model that defines quality attributes precisely improves communications between acquirers, architects, and developers.

A quality model that specifies usable and practical metrics can improve the quality of design models.

Effective application of a quality model adds more quality control earlier in the project’s life cycle

Validate the completeness of a requirements definition

Identifies user acceptance criteria for a completed software product

Identifies software requirements

Identifies software design objectives

Identifies software testing objectives

Quality ModelsA Specialist Independent Software Testing Solutions Provider

Several quality models have been developed over the years.

McCall/GE Quality Model• Organizes quality around three uses of software: product revision,

product operations, and product transition Boehm Quality Model

• Shares a common subset with the McCall model and identifies additional quality attributes

ISO/IEC 9126-1:2001 Quality Standard• Identifies six quality characteristics – functionality, reliability,

usability, efficiency, maintainability, and portability. These are further divided into several sub-characteristics

Quality ModelsA Specialist Independent Software Testing Solutions Provider

McCall’s Traingle for Quality

An Independent Software Testing Solution Provider

PRODUCT REVISIONPRODUCT REVISION PRODUCT TRANSITIONPRODUCT TRANSITION

PRODUCT OPERATIONPRODUCT OPERATION

• Maintainability• Flexibility• Testability

• Portability• Reusability• Interoperability

• Correctness

• Usability• Reliability

• Efficiency• Integrity

Ability to change Adaptability to new environments

Basic operational characteristic

Factors (characteristics) describe the external view of the software as viewed by users of the application

McCall’s Traingle for Quality

The model details three types of quality characteristics (major perspectives) in a hierarchy of factors, criteria and metrics:

11 Factors (To specify): They describe the external view of the software, as viewed by the users.

23 quality criteria (To build): They describe the internal view of the software, as seen by the developer.

Metrics (To control): They are defined and used to provide a scale and method for measurement

A Specialist Independent Software Testing Solutions Provider

Factors (characteristics) describe the external view of the software as viewed by users of the application

Boehm Quality Model


The high-level characteristics represent basic high-level requirements of actual use to which evaluation of software quality could be put – the general utility of software

The intermediate level characteristic represents Boehm’s 7 quality factors that together represent the qualities expected from a software system

The primitive characteristics provide the foundation for defining qualities metrics

Boehm Quality Model


ISO 9126 identifies the internal characteristics and external quality characteristics of a software product and contains various characters.

ISO/IEC 9126-1:2001 Quality Standard


Advantages of Measuring Software Quality

High levels of defect removal efficiency

Happier customers

Better team morale

Shorter development schedules

Lower development costs

Lower maintenance costs and

Total cost of ownership (TCO) that will be less than 50% of the same kinds of projects that botch up quality.


Issues in Measuring Software Quality

Cost of Collecting Metrics• Automation is less costly than manual method• CASE tool may not be free

• Development cost of the tool• Extra execution time for collecting metrics

• Interpretation of metrics consumes resources

Validity of the metrics• Does the metric really measure what it should?• What exactly should be measured?

Selection of metrics for measurement• Hundreds are available and with the same cost


Impact of ‘Software Quality’ on Business

Software Quality Income Expense

'High' Software Quality

• More Customers• Repeat Business• Competitive Advantage

• Lower Production Cost through reduced inventory

• Lower Inspection Cost• Lower Working Capital

'Low' Software Quality

• Loss of Business• Penalties for late delivery or

service• Partial or late payments due

to customer dissatisfaction

• Scrap and rework cost• Warranty Cost• Sorting Cosy• Express shipping cost

Profit = Income - Expense


Barriers in Achieving ‘High’ Software Quality

Specifying Quality Requirements• There has been little work in the field of formal specification for non-

functional requirementsModeling Methods Don’t Address Quality Attributes

• Design methodologies are weak in representing nonfunctional requirements

Designing for Quality Attributes• Quality attributes are interdependent and cannot be achieved in

isolationSolution Catalogues and Quality Attributes

• Design patterns can be used to address some quality attributes, but mapping them to a design pattern’s context and problem statements is not easy.

• It may be worthwhile to begin cataloguing patterns with respect to standardized quality attributes

Quality Control is an Afterthought• Putting testing off until the end of the project is effectively a statement

that quality is not important enough to be assessed early


Guidelines

Use common sense and organizational sensitivity when interpreting metrics data

Provide regular feedback to the individuals and teams who have worked to collect measures and metrics.

Don’t use metrics to appraise individuals

Work with practitioners and teams to set clear goals and metrics that will be used to achieve them

Never use metrics to threaten individuals or teams

Metrics data that indicate a problem area should not be considered “negative.” These data are merely an indicator for process improvement

Don’t obsess on a single metric to the exclusion of other important metrics


Practices to improve Software Quality


Sl. No

Practice Impact on Quality

Benefit Relevant Roles

1 Define Quality Attribute to match your needs

• Meet business Requirements

• Achieve a satisfying user experience

Development team is chartered with a definition of quality that fits the given time, resource and budget constraints

• Business Stakeholders

• Development Team

2. Broadcast simple quality metrics

Reduce defects Highly visible quality metrics keeps quality on the top of the mind for the entire team and exposes when the effort falls short

Development Team

3. Fine tune team and individual goals to include quality

• Meet business RequirementsAchieve a satisfying user experienceReduce defects

Team members perform according to their incentives; thus making quality improvement part of their goals reinforces desirable behaviour

Management

Practices to improve Software Quality


Sl. No

Practice Impact on Quality

Benefit Relevant Roles

4. Get requirements right

• Meet business Requirement

• Achieve a satisfying user experience

Less rework means less retesting and fewer cycles, which greatly reduces overall effort

• Managers• Business

Analysts• User Experience

designers• Architects

5. Test smarter to test less

Reduce defects • Focussing testing on the most important and most riskiest areas ensures that the bugs that slip through are likely to be confined to the least important features

• Use Testing tools

• Quality Assurance

• Managers

6. Design applications to lessen bug risks

Reduce defects Simple, cleaner designs results in code that is simpler, cleaner and easier to test and rework- which means that the code will have fewer bugs and those bugs found will be easier to diagnose and repair

• Architects• Developers

Step 1: IDENTIFY the key ‘Software Quality’ attribute(s) for your product/service

Step 2: Identify the METRIC which can be used to measure the identified

‘Software Quality’ attribute(s)

Step 3: Devise PLAN to measure the Metric for each key ‘Software Quality’

attribute

Step 4: IMPLEMENT the plan to measure the metric during the course of the

software development lifecycle

Step 5: MONITOR the Metric and publish the results to all the affected

stakeholders

Step 6: If the results are not within acceptable limits, devise an action plan to

further IMPROVE it and go back to Step 4 till the Software Quality

Attribute measured is acceptable

Next Step…A Specialist Independent Software Testing Solutions Provider

What is Software Quality?

What is its Economic Value?

How to mange Software Quality?

What are its Attributes?

Why do we need to measure it?

How do we measure it?

Issues while measuring it?

Guidelines for measuring it?

A Specialist Independent Software Testing Solution Provider Questions Answered

Session 1

Session 2

Session 3

A Specialist Independent Software Testing Solution Provider Remember…

Commitment to QUALITY always pays off

Thank YouA Specialist Independent Software Testing Solutions Provider

India OfficeSQE Labs Inc.

116/8, Mohali (Chandigarh)India – 160062

www.sqelabs.com

US OfficeSQE Labs LLC,

6533, Preston Rd, Plano,TX - 75024

Contact me : [email protected]

http://www.sqelabs.com/



mailto:[email protected]

Follow: @XBOSoft

Questions: [email protected] 408-350-0508

mailto:[email protected]

Thank You!

See you tomorrowTomorrow’s meeting March 20th


Shilpa Dadhwal,Founder and CEO,SQE Labs Inc

Philip LewCEO, XBOSoft

Jan PrincenManaging Director, XBOSoft


Day 3 meet shilpa measuring software quality and business impact session 3

Business

Transcript of Day 3 meet shilpa measuring software quality and business impact session 3