By: David Hoang Martin Hoffman

Slides:



Advertisements
Similar presentations
MIS 2000 Class 20 System Development Process Updated 2014.
Advertisements

ITIL: Service Transition
ATTENTION This presentation breaks down the purchasing process into 6 steps, which are then detailed in the subsequent slides. While responding from either.
TALOS Total ATM Life-cycle operational Solution. The Cost equation Life cycle costs are high Life cycle costs are complex Life cycle costs involve all.
© 2013 Cengage Learning. All Rights Reserved. May not be scanned, copied, duplicated, or posted to a publicly accessible website, in whole or in part.
Software Design & Production Methodologies STRUCTURED & OBJECT-ORIENTED METHODS for SYSTEMS ANALYSIS & DESIGN Vassilka Kirova Computer & Information Science.
Building Competitive Advantage Through Functional-Level Strategy
Shalagh Rigney, Tara Nolan, Kristen Sibilia March 26, 2008.
©2015 Cengage Learning. All Rights Reserved. May not be scanned, copied or duplicated, or posted to a publicly accessible website, in whole or in part.
Building Competitive Advantage Through Functional-Level Strategy
Operations Management
3. Software product quality metrics The quality of a product: -the “totality of characteristics that bear on its ability to satisfy stated or implied needs”.
OHT 22.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 Software Quality assurance (SQA) SWE 333 Dr Khalid Alnafjan
Quality of Information systems. Quality Quality is the degree on which a product satifies the requirements Quality management requires that : that requirements.
Commercial Database Applications Testing. Test Plan Testing Strategy Testing Planning Testing Design (covered in other modules) Unit Testing (covered.
 The software systems must do what they are supposed to do. “do the right things”  They must perform these specific tasks correctly or satisfactorily.
ICS321 – Management Information Systems Dr. Ken Cosh.
Software testing basic. Main contents  Why is testing necessary?  What is testing?  Test Design techniques  Test level  Test type  How to write.
Topic (1)Software Engineering (601321)1 Introduction Complex and large SW. SW crises Expensive HW. Custom SW. Batch execution.
2  Mission Statement.  Company’s overall purpose and direction, products, services and values.  Goals.  That accomplish the mission. E.g. 5 year plan.
Principles of Information Systems, Sixth Edition Systems Design, Implementation, Maintenance, and Review Chapter 13.
Indirect Sourcing Communications Set for Nokia Internal Use
CS551 - Lecture 5 1 CS551 Lecture 5: Quality Attributes Yugi Lee FH #555 (816)
1 Chapter 13 (Week 13) SYSTEMS MAINTENANCE AND EVALUATION Chapter 13: SYSTEMS MAINTENANCE AND EVALUATION Throughout its life, a system should operate effectively.
1 Object-Oriented Analysis and Design with the Unified Process Figure 13-1 Implementation discipline activities.
Building Competitive Advantage Through Functional-Level Strategies
Enterprise Resource Planning (ERP) The need for integrated information in business.
LINKAGE OF QUALITY IMPROVEMENT AND PROFITS The Cost of Quality.
Enterprise Resources Planning (ERP) Definition 1 Enterprise Resource Planning A method for the effective planning and controlling of ALL these sources.
CECE FICCI Quality Costs & Profit Chapter no.2 CECE FICCI Many people think that quality costs money and adversely effects profits. But these costs are.
BUSINESS INFORMATION SYSTEMS
Information Systems Development
ITIL: Service Transition
Balanced Scorecard: Quality, Time, and the Theory of Constraints
BLOCKCHAIN APPLICATION IN CORE BANKING
Chapter 3: Cost Estimation Techniques
Why Open Source Works Jim Herbsleb School of Computer Science
BUSINESS CONTINUITY BY HUI ZHENG.
Chapter 18 Maintaining Information Systems
McCall’s Quality Factors
Introduction SOFTWARE ENGINEERING.
APPLICATION RISK AND CONTROLS
Initiating systems development
Software Engineering Rekayasa Perangkat Lunak
Software engineering.
Quality Management Systems – Requirements
Information Systems Development
Operations Management
Dynamics 365 for Wholesale Ditribution Readiness Assessment
Software engineering Lecturer: Nareena.
Software Test Termination
Software Quality Engineering
Engineering Economic Decisions
Building Competitive advantage through functional level strategies
Construction and Materials Management System
Overview of Business Processes
Chapter 9 – Software Evolution and Maintenance
Operations Management
Software Engineering Rekayasa Perangkat Lunak
Software Engineering (CSI 321)
Building Competitive advantage through functional level strategies
Chapter 8 Software Evolution.
Lecture 06:Software Maintenance
Demand Management, Order Management, and Customer Service
Operations Management
The Cost of Inadequate S/W Testing
CEM 515 Done by: Abdulkarim Sulais
Software Engineering Rekayasa Perangkat Lunak
Software Design & Production Methodologies
Building Competitive Advantage Through Functional-Level Strategies
Presentation transcript:

By: David Hoang Martin Hoffman Measuring the Economic Impacts of an Inadequate Infrastructure for Software Testing By: David Hoang Martin Hoffman

Improved infrastructure can… Remove more bugs Detect bugs earlier Locate bugs faster 2

The longer it takes the more is costs… 3

What does this mean for the User? Fewer bugs in software operations stage Lower maintenance costs Change in avoidance activities 9

Custom vs. Commercial Software Products Custom Products: no formal release more resources needed for implementation (developer) post-purchase service (developer) 3rd party integrators To quantify the cost associated with an inadequate infrastructure for software testing we look at the costs of custom and commercial products. This is to prevent double counting. Release is different from deliverable

Estimating Software Developer Costs Data collected: Company’s total pre-release testing and post-release service costs. Surveyed developers. Additional resources required due to an Inadequate infrastructure for software testing: Labor costs Software costs Hardware costs After-sales service cost Delay costs Reputation costs Labor costs – additional employee and contract labor for pre-purchase testing and error correction, installation, and post-purchase repair - accounts for the majority of the impact Software – additional or redundant testing software purchases Hardware – equipment, computers needed in testing process After-sales – non-testing and debugging activities: servicing additional service calls and distribution of patches Delay costs – lost profits and delayed adoption du to delays and high bug counts in early versions Reputation – lost sales or market share

Estimating Software User Costs Software purchase decision Evaluation of products Lack of information on the quality of products Unable to compare across products based on price and quality uncertainty of bugs and interoperability increases Installation and Integration Higher for custom products Business operations System failures Installation and integration of custom products require more frequent integration with legacy systems. Bug or problems in either the new or legacy system can delay the system, require additional patches or drivers Potential for additional cost is very high here. Can involve both the user and developer. Most commercial SW products are typically less then custom sw. Business operations cost of loss of production, loss of data, customer information, lost sales, production delays, lost reputation, market share

Software User Cost Categories labor costs failure costs performance cost redundant systems delayed profits sales forfeited Labor – additional employees, contract labor. Testing installation, repair of software, testing sw before purchaing Failure – cost catastrophic failure of system/sw Performance – inpact on user, cost of work-arounds, loss of productivity when sw does not perform as expected Redundant – need for additional hw or sw to maintain support or back-up data in case of sw failture Common to maintain parallel system for 1+ year as a security measure. Delayed – delays in production and transactions Sales – lost transactions, discounted value.

Estimating Software Bug Costs Cost of bugs still remaining with improved sw testing infrastructure. Estimate the total cost of bugs to the user Determine linearly related costs and nonlinearly related costs User inputs: total costs associated with bugs general change in total costs in a 75% reduction in bugs Cost of product failure or installation is linear with the number of bugs Redundant system costs is not linear. Difference in cost reduction is industry dependant. Redundant systems costs – HW costs do not decrease linearly. Need for backup systems is not significantly reduced.

Estimating Software Bug Costs

Industry-specific User Costs Industries encounter different types of costs Two industries were selected: Financial services – FEDI/clearinghouse software users Transportation equipment manufacturing Quality Categories: Functionality Reliability Usability Efficiency Maintainability Portability FEDI - Financial Electronic Data Interchange

Questions?