Software Engineering Compiled By: Roshani Ghimire Page 1

Size: px
Start display at page:

Download "Software Engineering Compiled By: Roshani Ghimire Page 1"

Transcription

1 Unit 7: Metric for Process and Product 7.1 Software Measurement Measurement is the process by which numbers or symbols are assigned to the attributes of entities in the real world in such a way as to define them according to clearly defined rules. The ability to measure attributes of software and the software development process are essential to improvements in the practice of software engineering. In software development, measurements are performed by using metrics, which are experimental designations of a value to an object aiming to characterize a definite quality of this object. Measurement is the act of determining a measure. The IEEE Standard Glossary of Software Engineering Terms [IEE93] defines metric as a quantitative measure of the degree to which a system, component, or process possesses a given attribute. Why do we do software measure? o Measurement is fundamental to any engineering discipline o To get an insight into the software process o To do process improvement o To make the quality of the product better o To express the qualitative factor by a number o To make a better estimate of the cost, schedule, complexity, effort requirements etc of the software development process o Measurement is important for prediction. o Measurement is necessary for quality control and assurance Measure is a quantitative indication of the extent, size, amount, and dimension, capacity of some attributes of a product or a process. Measurement is the act of determining a measure. Types of Software Measurements 1. Direct measures Easy to collect E.g. Cost, Effort, Lines of codes (LOC), Execution Speed, Memory size, Defects etc. 2. Indirect measures More difficult to assess & can be measured indirectly only. Quality, Functionality, Complexity, Reliability, Efficiency, Maintainability etc. An example Software Engineering Compiled By: Roshani Ghimire Page 1

2 o 2 different project teams are working to record errors in a software process o Team A Finds 342 errors during software process before release o Team B- Finds 184 errors o Which team do you think is more effective in finding errors? An example of Measures, Measurements, Metrics, Indicators All test engineers of a certain project started collecting the following measure The errors found in the test cycle. But this measure is not enough to compute a suitable metric. You need two more measurements, which are number of test engineer and the number of months spent on the testing process. Suppose there were 5 test engineers and they spent about 6 months to do the necessary testing of the product. So, the total engineer-month is 30. And let s assume, all together they found about 60 errors. So, using all those measures mentioned above we can compute a Metric, which could be Errors found per Engineer-Month ; and the value of that metric here is 2. This metric can be used here as an indicator regarding how efficient the test teams are or how good the product is. For example, after introducing an automated testing tool, the above metric may reach a value of 5 ; which indicates the effectiveness of the automated testing tool used by the test team. So, this Metric can be used as an indicator of the efficiency of a project team 7.2 Metric for software quality Metric is a quantitative measure of the degree to which a system, component, or a process possesses a given attribute. An indicator is a metric or a combination of metrics that provide insight into the s/w process, a s/w project or the s/w product itself. Types of Metrics o Process Metrics Software Engineering Compiled By: Roshani Ghimire Page 2

3 Process Metrics: Project Metrics: Product Metrics: o Product Metrics o Project Metrics o Those metrics that are used to improve the process efficiency of the Software Development Life Cycle (SDLC) are called process metrics. For example, the process metric Defect Rate the amount of defects reaching the customer can be used to improve the efficiency of the Development and the Testing team. If Defect rate is less, we know that the efficiency of the Development and the Testing team is improving. o Process metrics concentrate on the process of software development and measure process structures with the aim of either distinguishing problems or pushing forward effective practices. o Process metrics are measures of the software development process, such as Overall development time Type of methodology used o Process metrics are collected across all projects and over long periods of time. o Their intent is to provide indicators that lead to long-term software process improvement. o The project metrics are those metrics which are more relevant to a project team. They can be used to measure the efficiency of a project team or any other tools being used by the team members. One example of a project metric is Errors found per engineer- month. This is a relevant project metric for a test team. o Project Metrics are the measures of Software Project and are used to monitor and control the project. They enable a software project manager to: Minimize the development time by making the adjustments necessary to avoid delays and potential problems and risks. Assess product quality on an ongoing basis & modify the technical approach to improve quality. o The product metrics are those metrics which has more meaning in the perspective of the software product being developed. One of the examples is quality of the developed product. Considering the fact that quality is a subjective attribute, one needs a very good understanding of the measures based on which the quality metrics are computed. Software Engineering Compiled By: Roshani Ghimire Page 3

4 Software Metrics: o Product metrics are also referred to as software metrics. They are directly associated with the product itself and attempt to measure product quality or characteristics of the product that can be connected with product quality. o Product metrics are measures of the software product at any stage of its development, from requirements to installed system. o Product metrics may measure: The complexity of the software design The size of the final program The number of pages of documentation produced o Software metric is a measure of some property of a piece of software or its specifications. Since quantitative measurements are essential in all sciences, there is a continuous effort by computer science practitioners and theoreticians to bring similar approaches to software development. The goal is obtaining objective, reproducible and quantifiable measurements, which may have numerous valuable applications in schedule and budget planning, cost estimation, quality assurance testing, software debugging, software performance optimization, and optimal personnel task assignments. o Software metrics can be private and public metrics o The Private metrics are those metrics which are collected by individual software professionals. They are mostly used by any software professional to get an insight regarding how his productivity or any other parameter of interests to him is. For example, a test engineer may keep errors found in a week as a private metric. Similarly, for a development engineer, lines of code written in a week could be a private metric of interests to him. Also, an IT professional may keep Number of new technology studied in a month as a private metric. o The public metrics has more meaning on an overall team basis. The public metrics can be computed depending upon the private metrics made public by the individual software professional. They are more concerned with the project team rather than any individual software professional. The examples are, Errors found per engineer-month, Lines of code written per engineermonth, etc It may happen that some of the product metrics are private metrics maintained by the individual engineer. When these metrics are shared by the entire engineer on the team basis, those metrics can be combined to develop a set of project metrics on a project level. In addition to that, these project metrics can be consolidated to create a set of process metrics. So, at the end these process metrics become the public metrics for the whole organization. Size Oriented Metrics: Software Engineering Compiled By: Roshani Ghimire Page 4

5 o The size oriented metrics are those metrics, which are computed keeping size of the software as main consideration. The sizes of the software are usually expressed in terms of KLOC (Kilo Line of Code). General Uses of Metrics Software metrics are used to obtain objective reproducible measurements that can be useful for quality assurance, performance, debugging, management, and estimating costs. Finding defects in code (post release and prior to release), predicting defective code, predicting project success, and predicting project risk. There is still some debate around which metrics matter and what they mean, the utility of metrics is limited to quantifying one of the following goals: Schedule of a software project, Size/complexity of development involved, cost of project, quality of software Types of metrics 1. Requirements metrics Size of requirements Traceability Completeness Volatility 2. Product Metrics Code metrics Lines of code LOC 3. Design metrics computed from requirements or design documents before the system has been implemented 4. Object oriented metrics- help identify faults, and allow developers to see directly how to make their classes and objects simpler. 5. Test metrics 6. Communication metrics looking at artifacts i.e. , and meetings. 7. Process metrics Measure the process of software development Commonly used by management to check the budget and office procedures for efficiency Evaluate and track aspects of the software design process like: o Human resources o Time o Schedule o Methodology Software Engineering Compiled By: Roshani Ghimire Page 5

6 The standard identifies six key quality attributes: 1. Functionality: The degree to which the software satisfies stated needs as indicated by the following sub attributes: suitability, accuracy, interoperability, compliance, and security. 2. Reliability: The amount of time that the software is available for use as indicated by the following sub attributes: maturity, fault tolerance, recoverability. 3. Usability: The degree to which the software is easy to use as indicated by the following sub attributes: understandability, learn ability, operability. 4. Efficiency: The degree to which the software makes optimal use of system resources as indicated by the following sub attributes: time behavior, resource behavior. 5. Maintainability: The ease with which repair may be made to the software as indicated by the following sub attributes: analyzability, changeability, stability, testability. 6. Portability: The ease with which the software can be transposed from one environment to another as indicated by the following sub attributes: adaptability, install ability, conformance, and replace ability. Why Software Metrics To characterize. To evaluate To predict. To improve. Attributes of Software Metrics o Practical support is expected. o Measurement demands should be simple. o Less esoteric and easy to understand for real world professionals. o Should specify the basic intuitive notion of high-quality software. o Derived metrics and measures should lead to simple and computable conclusions o Easy to derive the metrics and should not demand inordinate effort or time 7.3 Software quality assurance Software quality is the conformance to explicitly stated functional and performance requirements, explicitly documented development standards and implicit characteristics that are expected of all professionally developed software Software requirements are reference from which quality is measured; lack of conformance is lack of quality. Specified standards define a set of development criteria that guide the manner in which software is engineered There are some implied requirements which are must with specified criteria The six standard attributes that are involved are: Software Engineering Compiled By: Roshani Ghimire Page 6

7 o Functionality o Usability o Maintainability o Portability o Reliability o Efficiency Software quality assurance (SQA) is the concern of every software engineer to reduce costs and improve product time-to-market. A Software Quality Assurance Plan is not merely another name for a test plan, though test plans are included in an SQA plan. SQA activities are performed on every software project. Use of metrics is an important part of developing a strategy to improve the quality of both software processes and work products. Software Quality Assurance is o An Umbrella activity applied throughout the software process o Planned and systematic pattern of actions required to ensure high quality in software o Responsibility of many stakeholders (software engineers, project managers, customers, salespeople, SQA group) SQA Questions are: o Does the software adequately meet its quality factors? o Has software development been conducted according to pre-established standards? o Have technical disciplines performed their SQA roles properly? Quality Assurance Elements are: o Standards ensure that standards are adopted and followed o Reviews and audits audits are reviews performed by SQA personnel to ensure that quality guidelines are followed for all software engineering work o Testing ensure that testing id properly planned and conducted o Error/defect collection and analysis collects and analyses error and defect data to better understand how errors are introduced and can be eliminated o Changes management ensures that adequate change management practices have been instituted o Education takes lead in software process improvement and educational program o Vendor management suggests specific quality practices vendor should follow and incorporates quality mandates in vendor contracts o Security management ensures use of appropriate process and technology to achieve desired security level o Safety responsible for assessing impact of software failure and initiating steps to reduce risk Software Engineering Compiled By: Roshani Ghimire Page 7

8 o Risk management ensures risk management activities are properly conducted and that contingency plans have been established SQA Tasks are: o Prepare SQA plan for the project. o Participate in the development of the project's software process description. o Review software engineering activities to verify compliance with the defined software process. o Audit designated software work products to verify compliance with those defined as part of the software process. o Ensure that any deviations in software or work products are documented and handled according to a documented procedure. o Record any evidence of noncompliance and reports them to management. SQA Goals are: Requirements quality o Ambiguity o Completeness o Volatility o Traceability o Model clarity Design quality o Architectural integrity o Component completeness o Interface complexity o Patterns Code quality o Complexity o Maintainability o Understandability o Reusability o Documentation Quality control effectiveness o Resource allocation o Completion rate o Review effectiveness o Testing effectiveness Six Sigma Software Engineering Software Engineering Compiled By: Roshani Ghimire Page 8

9 o Define customer requirements, deliverables, and project goals via well-defined methods of customer communication. o Measure each existing process and its output to determine current quality performance (e.g. compute defect metrics) o Analyze defect metrics and determine viral few causes. o For an existing process that needs improvement Improve process by eliminating the root causes for defects Control future work to ensure that future work does not reintroduce causes of defects o If new processes are being developed Design each new process to avoid root causes of defects and to meet customer requirements Verify that the process model will avoid defects and meet customer requirements What is a Software Quality Assurance Engineer? Software QA (quality assurance) engineers are individuals who monitor every phase of the software development process so as to ensure design quality, making sure that the software adheres to the standards set by the development company. Sometimes software QA engineers are confused with software testers, which is a mistake. Software testers test parts of the software at different stages of development, whereas a software QA engineer oversees the entire development process, which includes software testing, from start to finish. The monetary success of the software product is largely due in part to the quality of the product as well as the product s ability to hit the market on time. Both are the responsibility of the software QA engineer. Software Quality Attribute 1. Functionality: o Functionality represents all the system-wide functional. o These functional requirements represent the main product features and answer the question: o What the product does for us rather than how does it do it. o The easiest way to think of functional requirements is to ask the question why this piece of software exists. o This question of reason for being is distinct from security, look and feel and reliability concerns which are important but are not the concerned with the main function (or value add) of the software. 2. Usability Software Engineering Compiled By: Roshani Ghimire Page 9

10 3. Reliability o Usability includes looking at, capturing, and stating requirements based around user interface issues, e.g. issues such as accessibility, interface aesthetics, and consistency within the user interface. o Reliability includes aspects such as availability, accuracy, and recoverability, for example recoverability of the system from shut-down failure. 4. Performance o Performance involves issues such as throughput of information, system response time (which also relates to usability), recovery time, and startup time. 5. Supportability o This is a general bucket of requirements that address supporting the software: for example testability, adaptability, maintainability, compatibility, configurability, installs ability, scalability, localizability, and so on. 7.4 Software reliability Defined as the probability of failure free operation of a computer program in a specified environment for a specified time period Can be measured directly and estimated using historical and developmental data (unlike many other software quality factors) Software reliability problems can usually be traced back to errors in design or implementation. Measures of Reliability Mean time between failure (MTBF) = MTTF + MTTR MTTF = mean time to failure MTTR = mean time to repair Availability = [MTTF / (MTTF + MTTR)] x 100% Software Reliability is the probability of failure-free software operation for a specified period of time in a specified environment. Software Reliability is also an important factor affecting system reliability. It differs from hardware reliability in that it reflects the design perfection, rather than manufacturing perfection. The high complexity of software is the major contributing factor of Software Reliability problems. Software Reliability is not a function of time - although researchers have come up with models relating the two. The modeling technique for Software Reliability is reaching its prosperity, but before using the technique, we must carefully select the appropriate model that can best suit our case. Measurement in software is still in its infancy. No good quantitative methods have been developed to represent Software Reliability without Software Engineering Compiled By: Roshani Ghimire Page 10

11 excessive limitations. Various approaches can be used to improve the reliability of software, however, it is hard to balance development time and budget with software reliability. 7.5 The ISO 9000 quality standard Quality assurance systems are defined as the organizational structure, responsibilities, procedures, processes, and resources for implementing quality management. ISO 9000 describes the quality elements that must be present for a quality assurance system to be compliant with the standard, but it does not describe how an organization should implement these elements. ISO 9001:2000 is the quality standard that contains 20 requirements that must be present in an effective software quality assurance system. ISO 9000 certification ISO (International Standards Organization) is a consortium of 63 countries established to formulate and foster standardization. ISO published its 9000 series of standards in ISO certification serves as a reference for contract between independent parties. The ISO 9000 standard specifies the guidelines for maintaining a quality system. We have already seen that the quality system of an organization applies to all activities related to its product or service. The ISO standard mainly addresses operational aspects and organizational aspects such as responsibilities, reporting, etc. In a nutshell, ISO 9000 specifies a set of guidelines for repeatable and high quality product development. It is important to realize that ISO 9000 standard is a set of guidelines for the production process and is not directly concerned about the product itself. Types of ISO 9000 quality standards ISO 9000 is a series of three standards: o ISO 9001, ISO 9002, and ISO The ISO 9000 series of standards is based on the premise that if a proper process is followed for production, then good quality products are bound to follow automatically. The types of industries to which the different ISO standards apply are as follows. ISO 9001 applies to the organizations engaged in design, development, production, and servicing of goods. This is the standard that is applicable to most software development organizations. ISO 9002 applies to those organizations which do not design products but are only involved in production. Examples of these category industries include steel and car Software Engineering Compiled By: Roshani Ghimire Page 11

12 manufacturing industries that buy the product and plant designs from external sources and are involved in only manufacturing those products. Therefore, ISO 9002 is not applicable to software development organizations. ISO 9003 applies to organizations that are involved only in installation and testing of the products. Software products vs. other products There are mainly two differences between software products and any other type of products. Software is intangible in nature and therefore difficult to control. It is very difficult to control and manage anything that is not seen. In contrast, any other industries such as car manufacturing industries where one can see a product being developed through various stages such as fitting engine, fitting doors, etc. Therefore, it is easy to accurately determine how much work has been completed and to estimate how much more time will it take. During software development, the only raw material consumed is data. In contrast, large quantities of raw materials are consumed during the development of any other product. Need for obtaining ISO 9000 certification There is a mad scramble among software development organizations for obtaining ISO certification due to the benefits it offers. Some benefits that can be acquired to organizations by obtaining ISO certification are as follows: o Confidence of customers in an organization increases when organization qualifies for ISO certification. This is especially true in the international market. In fact, many organizations awarding international software development contracts insist that the development organization have ISO 9000 certification. For this reason, it is vital for software organizations involved in software export to obtain ISO 9000 certification. o ISO 9000 requires a well-documented software production process to be in place. o A well-documented software production process contributes to repeatable and higher quality of the developed software. o ISO 9000 makes the development process focused, efficient, and cost-effective. o ISO 9000 certification points out the weak points of an organization and recommends remedial action. o ISO 9000 sets the basic framework for the development of an optimal process and Total Quality Management (TQM). Software Engineering Compiled By: Roshani Ghimire Page 12

Module 13. Software Reliability and Quality Management. Version 2 CSE IIT, Kharagpur

Module 13. Software Reliability and Quality Management. Version 2 CSE IIT, Kharagpur Module 13 Software Reliability and Quality Management Lesson 34 ISO 9000 Specific Instructional Objectives At the end of this lesson the student would be able to: State what is meant by ISO 9000 certification.

More information

Software Quality Assurance. Software Engineering: A Practitionerʼs Approach, 7/e by Roger S. Pressman

Software Quality Assurance. Software Engineering: A Practitionerʼs Approach, 7/e by Roger S. Pressman Chapter 16 Software Quality Assurance Slide Set to accompany Software Engineering: A Practitionerʼs Approach, 7/e by Roger S. Pressman Slides copyright 1996, 2001, 2005, 2009 by Roger S. Pressman For non-profit

More information

Darshan Institute of Engineering & Technology Unit : 7

Darshan Institute of Engineering & Technology Unit : 7 1) Explain quality control and also explain cost of quality. Quality Control Quality control involves the series of inspections, reviews, and tests used throughout the software process to ensure each work

More information

Software Quality. Software Quality Assurance and Software Reuse. Three Important Points. Quality Factors

Software Quality. Software Quality Assurance and Software Reuse. Three Important Points. Quality Factors Software Quality Software Quality Assurance and Software Reuse Peter Lo Conformance to explicitly-stated functional and performance requirements, explicitly-documented development standards, and implicit

More information

Service Delivery Module

Service Delivery Module Service Delivery Module Software Development Methodology -India follows international industry standards and has adopted the standard methodology in our Software Development Life Cycle (SDLC). It is a

More information

Chap 1. Software Quality Management

Chap 1. Software Quality Management Chap 1. Software Quality Management Part 1.1 Quality Assurance and Standards Part 1.2 Software Review and Inspection Part 1.3 Software Measurement and Metrics 1 Part 1.1 Quality Assurance and Standards

More information

copyright 1996, 2001, 2005 R.S. Pressman & Associates, Inc.

copyright 1996, 2001, 2005 R.S. Pressman & Associates, Inc. Software Engineering: A Practitioner s Approach, 6/e Chapter 26 Quality Management copyright 1996, 2001, 2005 R.S. Pressman & Associates, Inc. For University Use Only May be reproduced ONLY for student

More information

The Role of Information Technology Studies in Software Product Quality Improvement

The Role of Information Technology Studies in Software Product Quality Improvement The Role of Information Technology Studies in Software Product Quality Improvement RUDITE CEVERE, Dr.sc.comp., Professor Faculty of Information Technologies SANDRA SPROGE, Dr.sc.ing., Head of Department

More information

Software Engineering: Analysis and Design - CSE3308

Software Engineering: Analysis and Design - CSE3308 CSE3308/DMS/2004/25 Monash University - School of Computer Science and Software Engineering Software Engineering: Analysis and Design - CSE3308 Software Quality CSE3308 - Software Engineering: Analysis

More information

SOFTWARE ENGINEERING

SOFTWARE ENGINEERING SOFTWARE ENGINEERING Chapter 26 Quality Management ETAM MEMBERS RN N 3521010116 Murali T 3521010117 Muralitharan S 3521010118 Narasimhan K 3521010119 Navaneethakrishnan D Areas Covered What is software

More information

SOFTWARE QUALITY MODELS: A COMPARATIVE STUDY

SOFTWARE QUALITY MODELS: A COMPARATIVE STUDY SOFTWARE QUALITY MODELS: A COMPARATIVE STUDY Mrs. Manisha L. Waghmode Assistant Professor Bharati Vidyapeeth Deemed University, Institute of Management and Rural Development Administration, Sangli Dr.

More information

What do you think? Definitions of Quality

What do you think? Definitions of Quality What do you think? What is your definition of Quality? Would you recognise good quality bad quality Does quality simple apply to a products or does it apply to services as well? Does any company epitomise

More information

A Study on Software Metrics and Phase based Defect Removal Pattern Technique for Project Management

A Study on Software Metrics and Phase based Defect Removal Pattern Technique for Project Management International Journal of Soft Computing and Engineering (IJSCE) A Study on Software Metrics and Phase based Defect Removal Pattern Technique for Project Management Jayanthi.R, M Lilly Florence Abstract:

More information

Software Test Specification

Software Test Specification Software Test Specification 1. Introduction This section provides an overview of the entire test document. This document describes both the test plan and the test procedure. 1.1 Goals and objectives Overall

More information

Fundamentals of Measurements

Fundamentals of Measurements Objective Software Project Measurements Slide 1 Fundamentals of Measurements Educational Objective: To review the fundamentals of software measurement, to illustrate that measurement plays a central role

More information

Lecture 8 About Quality and Quality Management Systems

Lecture 8 About Quality and Quality Management Systems Lecture 8 About Quality and Quality Management Systems Kari Systä 10.03.2014 10.03.2014 TIE-21100/21106; K.Systä 1 Content of today s lecture Two weeks ago we discussed about testing and inspections, that

More information

SOFTWARE QUALITY & SYSTEMS ENGINEERING PROGRAM. Quality Assurance Checklist

SOFTWARE QUALITY & SYSTEMS ENGINEERING PROGRAM. Quality Assurance Checklist SOFTWARE QUALITY & SYSTEMS ENGINEERING PROGRAM Quality Assurance Checklist The following checklist is intended to provide system owners, project managers, and other information systems development and

More information

Introduction to Software Engineering. 8. Software Quality

Introduction to Software Engineering. 8. Software Quality Introduction to Software Engineering 8. Software Quality Roadmap > What is quality? > Quality Attributes > Quality Assurance: Planning and Reviewing > Quality System and Standards 2 Sources > Software

More information

Testing Metrics. Introduction

Testing Metrics. Introduction Introduction Why Measure? What to Measure? It is often said that if something cannot be measured, it cannot be managed or improved. There is immense value in measurement, but you should always make sure

More information

Quality Management. Lecture 12 Software quality management

Quality Management. Lecture 12 Software quality management Quality Management Lecture 12 Software quality management doc.dr.sc. Marko Jurčević prof.dr.sc. Roman Malarić University of Zagreb Faculty of Electrical Engineering and Computing Department of Fundamentals

More information

CSC 408F/CSC2105F Lecture Notes

CSC 408F/CSC2105F Lecture Notes CSC 408F/CSC2105F Lecture Notes These lecture notes are provided for the personal use of students taking CSC 408H/CSC 2105H in the Fall term 2004/2005 at the University of Toronto. Copying for purposes

More information

Software Test Plan (STP) Template

Software Test Plan (STP) Template (STP) Template Items that are intended to stay in as part of your document are in bold; explanatory comments are in italic text. Plain text is used where you might insert wording about your project. This

More information

Managing Software Quality

Managing Software Quality Managing Software Quality Main Issues Quality cannot be added as an afterthought Metrics for measuring quality are necessary Quality can mean different things Quality needs to be implemented both in the

More information

Software Quality Management

Software Quality Management Software Lecture 9 Software Engineering CUGS Spring 2011 Kristian Sandahl Department of Computer and Information Science Linköping University, Sweden A Software Life-cycle Model Which part will we talk

More information

The purpose of Capacity and Availability Management (CAM) is to plan and monitor the effective provision of resources to support service requirements.

The purpose of Capacity and Availability Management (CAM) is to plan and monitor the effective provision of resources to support service requirements. CAPACITY AND AVAILABILITY MANAGEMENT A Project Management Process Area at Maturity Level 3 Purpose The purpose of Capacity and Availability Management (CAM) is to plan and monitor the effective provision

More information

V&V and QA throughout the M&S Life Cycle

V&V and QA throughout the M&S Life Cycle Introduction to Modeling and Simulation and throughout the M&S Life Cycle Osman Balci Professor Department of Computer Science Virginia Polytechnic Institute and State University (Virginia Tech) Blacksburg,

More information

1. Introduction. Annex 7 Software Project Audit Process

1. Introduction. Annex 7 Software Project Audit Process Annex 7 Software Project Audit Process 1. Introduction 1.1 Purpose Purpose of this document is to describe the Software Project Audit Process which capable of capturing different different activities take

More information

Evaluation of the Iceland State Financial and Human Resource System REPORT OF THE INDIVIDUAL EVALUATOR. Annex 2 SYSTEM AND SOFTWARE QUALITY

Evaluation of the Iceland State Financial and Human Resource System REPORT OF THE INDIVIDUAL EVALUATOR. Annex 2 SYSTEM AND SOFTWARE QUALITY Evaluation of the Iceland State Financial and Human Resource System REPORT OF THE INDIVIDUAL EVALUATOR Annex 2 SYSTEM AND SOFTWARE QUALITY This paper lists the properties used in the two main models in

More information

1.1 The Nature of Software... Object-Oriented Software Engineering Practical Software Development using UML and Java. The Nature of Software...

1.1 The Nature of Software... Object-Oriented Software Engineering Practical Software Development using UML and Java. The Nature of Software... 1.1 The Nature of Software... Object-Oriented Software Engineering Practical Software Development using UML and Java Chapter 1: Software and Software Engineering Software is intangible Hard to understand

More information

NEOXEN MODUS METHODOLOGY

NEOXEN MODUS METHODOLOGY NEOXEN MODUS METHODOLOGY RELEASE 5.0.0.1 INTRODUCTION TO QA & SOFTWARE TESTING GUIDE D O C U M E N T A T I O N L I C E N S E This documentation, as well as the software described in it, is furnished under

More information

Software Metrics & Software Metrology. Alain Abran. Chapter 4 Quantification and Measurement are Not the Same!

Software Metrics & Software Metrology. Alain Abran. Chapter 4 Quantification and Measurement are Not the Same! Software Metrics & Software Metrology Alain Abran Chapter 4 Quantification and Measurement are Not the Same! 1 Agenda This chapter covers: The difference between a number & an analysis model. The Measurement

More information

Software Project Audit Process

Software Project Audit Process Software Project Audit Process Version 1.2 Information and Communication Technology Agency of Sri Lanka July 2013 Copyright 2011 ICTA Software Project Audit Process-v-1.2 Revision History Date Version

More information

Your Software Quality is Our Business. INDEPENDENT VERIFICATION AND VALIDATION (IV&V) WHITE PAPER Prepared by Adnet, Inc.

Your Software Quality is Our Business. INDEPENDENT VERIFICATION AND VALIDATION (IV&V) WHITE PAPER Prepared by Adnet, Inc. INDEPENDENT VERIFICATION AND VALIDATION (IV&V) WHITE PAPER Prepared by Adnet, Inc. February 2013 1 Executive Summary Adnet is pleased to provide this white paper, describing our approach to performing

More information

The Configuration Management process area involves the following:

The Configuration Management process area involves the following: CONFIGURATION MANAGEMENT A Support Process Area at Maturity Level 2 Purpose The purpose of is to establish and maintain the integrity of work products using configuration identification, configuration

More information

Multi-view Architecting

Multi-view Architecting by Gerrit Muller, JürgenMüller, Jan Gerben Wijnstra College, Philips Research e-mail: gaudisite@gmail.com www.gaudisite.nl Buskerud University Abstract The development of large SW-intensive products needs

More information

CHAPTER 7 Software Configuration Management

CHAPTER 7 Software Configuration Management CHAPTER 7 Software Configuration Management ACRONYMS CCB CM FCA MTBF PCA SCCB SCI SCM SCMP SCR SCSA SEI/CMMI SQA SRS USNRC INTRODUCTION Configuration Control Board Configuration Management Functional Configuration

More information

Key Factors for Developing a Successful E-commerce Website

Key Factors for Developing a Successful E-commerce Website IBIMA Publishing Communications of the IBIMA http://www.ibimapublishing.com/journals/cibima/cibima.html Vol. 2010 (2010), Article ID 763461, 9 pages Key Factors for Developing a Successful E-commerce Website

More information

Kunal Jamsutkar 1, Viki Patil 2, P. M. Chawan 3 (Department of Computer Science, VJTI, MUMBAI, INDIA)

Kunal Jamsutkar 1, Viki Patil 2, P. M. Chawan 3 (Department of Computer Science, VJTI, MUMBAI, INDIA) Software Project Quality Management Kunal Jamsutkar 1, Viki Patil 2, P. M. Chawan 3 (Department of Computer Science, VJTI, MUMBAI, INDIA) ABSTRACT Quality Management is very important in Software Projects.

More information

Software Project Management Matrics. Complied by Heng Sovannarith heng_sovannarith@yahoo.com

Software Project Management Matrics. Complied by Heng Sovannarith heng_sovannarith@yahoo.com Software Project Management Matrics Complied by Heng Sovannarith heng_sovannarith@yahoo.com Introduction Hardware is declining while software is increasing. Software Crisis: Schedule and cost estimates

More information

SECURITY METRICS: MEASUREMENTS TO SUPPORT THE CONTINUED DEVELOPMENT OF INFORMATION SECURITY TECHNOLOGY

SECURITY METRICS: MEASUREMENTS TO SUPPORT THE CONTINUED DEVELOPMENT OF INFORMATION SECURITY TECHNOLOGY SECURITY METRICS: MEASUREMENTS TO SUPPORT THE CONTINUED DEVELOPMENT OF INFORMATION SECURITY TECHNOLOGY Shirley Radack, Editor Computer Security Division Information Technology Laboratory National Institute

More information

How to Write a Software Process Procedures and Policy Manual for YOUR COMPANY

How to Write a Software Process Procedures and Policy Manual for YOUR COMPANY How to Write a Software Process for YOUR COMPANY 1. Introduction MicroTools is proposing to assist YOUR COMPANY in improving the existing software process. The purpose of this project is to both improve

More information

Basic Testing Concepts and Terminology

Basic Testing Concepts and Terminology T-76.5613 Software Testing and Quality Assurance Lecture 2, 13.9.2006 Basic Testing Concepts and Terminology Juha Itkonen SoberIT Contents Realities and principles of Testing terminology and basic concepts

More information

Software Engineering Prof. N.L. Sarda Computer Science & Engineering Indian Institute of Technology, Bombay Lecture-4 Overview of Phases (Part - II)

Software Engineering Prof. N.L. Sarda Computer Science & Engineering Indian Institute of Technology, Bombay Lecture-4 Overview of Phases (Part - II) Software Engineering Prof. N.L. Sarda Computer Science & Engineering Indian Institute of Technology, Bombay Lecture-4 Overview of Phases (Part - II) We studied the problem definition phase, with which

More information

Role of Software Quality Assurance in Capability Maturity Model Integration

Role of Software Quality Assurance in Capability Maturity Model Integration Role of Software Quality Assurance in Capability Maturity Model Integration Rekha Chouhan 1 Dr.Rajeev Mathur 2 1 Research Scholar, Jodhpur National University, JODHPUR 2 Director, CS, Lachoo Memorial College

More information

QUALITY ASSURANCE IN EXTREME PROGRAMMING Plamen Balkanski

QUALITY ASSURANCE IN EXTREME PROGRAMMING Plamen Balkanski International Journal "Information Theories & Applications" Vol.10 113 QUALITY ASSURANCE IN EXTREME PROGRAMMING Plamen Balkanski Abstract: Our previous research about possible quality improvements in Extreme

More information

Automated Office Systems Support Quality Assurance Plan. A Model DRAFT. December 1996

Automated Office Systems Support Quality Assurance Plan. A Model DRAFT. December 1996 Quality Assurance Plan A Model DRAFT United States Department of Energy Office of Nonproliferation and National Security Title Page Document Name: Publication Date: Draft, ontract Number: Project Number:

More information

V. Phani Krishna et al, / (IJCSIT) International Journal of Computer Science and Information Technologies, Vol. 2 (6), 2011, 2915-2919

V. Phani Krishna et al, / (IJCSIT) International Journal of Computer Science and Information Technologies, Vol. 2 (6), 2011, 2915-2919 Software Quality Assurance in CMM and XP- A Comparative Study CH.V. Phani Krishna and Dr. K.Rajasekhara Rao CSE Department, KL University, Guntur dt., India. Abstract Software Quality Assurance is a planned

More information

Software Testing. Knowledge Base. Rajat Kumar Bal. Introduction

Software Testing. Knowledge Base. Rajat Kumar Bal. Introduction Software Testing Rajat Kumar Bal Introduction In India itself, Software industry growth has been phenomenal. IT field has enormously grown in the past 50 years. IT industry in India is expected to touch

More information

International Journal of Advance Research in Computer Science and Management Studies

International Journal of Advance Research in Computer Science and Management Studies Volume 2, Issue 12, December 2014 ISSN: 2321 7782 (Online) International Journal of Advance Research in Computer Science and Management Studies Research Article / Survey Paper / Case Study Available online

More information

Levels of Software Testing. Functional Testing

Levels of Software Testing. Functional Testing Levels of Software Testing There are different levels during the process of Testing. In this chapter a brief description is provided about these levels. Levels of testing include the different methodologies

More information

Non-Functional Requirements

Non-Functional Requirements IBM Software Group Non-Functional Requirements Peter Eeles peter.eeles@uk.ibm.com Agenda IBM Software Group Rational software Definitions Types of requirement Classifying requirements Capturing NFRs Summary

More information

What is a life cycle model?

What is a life cycle model? What is a life cycle model? Framework under which a software product is going to be developed. Defines the phases that the product under development will go through. Identifies activities involved in each

More information

A Comparative Study of Software Quality Models

A Comparative Study of Software Quality Models A Comparative Study of Software Quality Models Suman 1, Manoj Wadhwa 2 CSE Department, M.D.U. Rohtak 1 M.Tech, 2 Professor &HOD of CSE Department Echelon Institute of Technology, Faridabad 121004,India

More information

Definitions. Software Metrics. Why Measure Software? Example Metrics. Software Engineering. Determine quality of the current product or process

Definitions. Software Metrics. Why Measure Software? Example Metrics. Software Engineering. Determine quality of the current product or process Definitions Software Metrics Software Engineering Measure - quantitative indication of extent, amount, dimension, capacity, or size of some attribute of a product or process. Number of errors Metric -

More information

Great Lakes National Program Office and Office of Water Quality Management Training Modules

Great Lakes National Program Office and Office of Water Quality Management Training Modules GLOSSARY Assessment - the evaluation process used to measure the performance or effectiveness of a system and its elements. As used here, assessment is an all-inclusive term used to denote any of the following:

More information

FSW QA Testing Levels Definitions

FSW QA Testing Levels Definitions FSW QA Testing Levels Definitions 1. Overview This document is used to help determine the amount and quality of testing (or its scope) that is planned for or has been performed on a project. This analysis

More information

ISSA Guidelines on Master Data Management in Social Security

ISSA Guidelines on Master Data Management in Social Security ISSA GUIDELINES ON INFORMATION AND COMMUNICATION TECHNOLOGY ISSA Guidelines on Master Data Management in Social Security Dr af t ve rsi on v1 Draft version v1 The ISSA Guidelines for Social Security Administration

More information

Medical Device Software - Software Life Cycle Processes

Medical Device Software - Software Life Cycle Processes 1 Medical Device Software - Software Life Cycle Processes IEC 62304 2 Credits John F. Murray Software Compliance Expert U.S. Food and Drug Administration Marcie R. Williams Medical Device Fellow Ph.D.

More information

TEST METRICS AND KPI S

TEST METRICS AND KPI S WHITE PAPER TEST METRICS AND KPI S Abstract This document serves as a guideline for understanding metrics and the Key performance indicators for a testing project. Metrics are parameters or measures of

More information

Reaching CMM Levels 2 and 3 with the Rational Unified Process

Reaching CMM Levels 2 and 3 with the Rational Unified Process Reaching CMM Levels 2 and 3 with the Rational Unified Process Rational Software White Paper TP174 Table of Contents INTRODUCTION... 1 LEVEL-2, REPEATABLE... 3 Requirements Management... 3 Software Project

More information

Quality Management. Abstract

Quality Management. Abstract Quality Management Abstract Dr. Raman Chadda 1 Arzoo Gupta 2 Bhupinder Singh 3 Yatin Chadha 4 With the advancements in the technology, software has become a crucial part. The future cannot be even imagined

More information

Project Risk Management: Independent Software QA Ensures Success

Project Risk Management: Independent Software QA Ensures Success Project Risk Management: Independent Software QA Ensures Success Introduction We hear the stories time after time: A group of talented, hard-working, motivated software engineers has once again produced

More information

Lecture 1: Introduction to Software Quality Assurance

Lecture 1: Introduction to Software Quality Assurance Lecture 1: Introduction to Software Quality Assurance Software Quality Assurance (INSE 6260/4-UU) Winter 2009 Thanks to Rachida Dssouli for some slides Course Outline Software Quality Overview Software

More information

Software Quality Assurance Plan

Software Quality Assurance Plan For Database Applications Document ID: Version: 2.1a Planning Installation & Acceptance Integration & Test Requirements Definition Design Development 1 / 54 Copyright 2000-2006 Digital Publications LLC.

More information

Software Engineering 9.1. Quality Control

Software Engineering 9.1. Quality Control Software Engineering 9.1. 9. Introduction When, Why and What? Product & Process Attributes Internal & External Attributes Typical Quality Attributes Overview Definitions Quality Assurance Assumption Quality

More information

Manufacturing View. User View. Product View. User View Models. Product View Models

Manufacturing View. User View. Product View. User View Models. Product View Models Why SQA Activities Pay Off? Software Quality & Metrics Sources: 1. Roger S. Pressman, Software Engineering A Practitioner s Approach, 5 th Edition, ISBN 0-07- 365578-3, McGraw-Hill, 2001 (Chapters 8 &

More information

CDC UNIFIED PROCESS JOB AID

CDC UNIFIED PROCESS JOB AID CDC UNIFIED PROCESS JOB AID Independent Verification & Validation Activities Document Purpose This Job Aid is a brief document listing the items to be noted, checked, remembered, and delivered when completing

More information

Requirements engineering

Requirements engineering Learning Unit 2 Requirements engineering Contents Introduction............................................... 21 2.1 Important concepts........................................ 21 2.1.1 Stakeholders and

More information

An Introduction to. Metrics. used during. Software Development

An Introduction to. Metrics. used during. Software Development An Introduction to Metrics used during Software Development Life Cycle www.softwaretestinggenius.com Page 1 of 10 Define the Metric Objectives You can t control what you can t measure. This is a quote

More information

Building a Data Quality Scorecard for Operational Data Governance

Building a Data Quality Scorecard for Operational Data Governance Building a Data Quality Scorecard for Operational Data Governance A White Paper by David Loshin WHITE PAPER Table of Contents Introduction.... 1 Establishing Business Objectives.... 1 Business Drivers...

More information

GUIDELINE ON RISK MANAGEMENT AND INTERNAL CONTROL PRINCIPLES AS WELL AS INTERNAL AUDIT FUNCTION OF INVESTMENT FIRMS

GUIDELINE ON RISK MANAGEMENT AND INTERNAL CONTROL PRINCIPLES AS WELL AS INTERNAL AUDIT FUNCTION OF INVESTMENT FIRMS until further notice 1 (10) Applicable to investment firms GUIDELINE ON RISK MANAGEMENT AND INTERNAL CONTROL PRINCIPLES AS WELL AS INTERNAL AUDIT FUNCTION OF INVESTMENT FIRMS By virtue of section 4, point

More information

ájoƒ ùdg á«hô dg áµلªÿg Yesser Overall SDLC Process Definition

ájoƒ ùdg á«hô dg áµلªÿg Yesser Overall SDLC Process Definition ájoƒ ùdg á«hô dg áµلªÿg Yesser Overall SDLC Process Definition Version 0.6 - Page 3 / 43 Table of Contents 1. Process Introduction... 5 1.1. Process Scope... 5 1.2. Process Objectives and Benefits... 5

More information

Quality Assurance - Karthik

Quality Assurance - Karthik Prevention is better than cure Quality Assurance - Karthik This maxim perfectly explains the difference between quality assurance and quality control. Quality Assurance is a set of processes that needs

More information

By Ramon Smitherman, Dream Catchers, Inc. Executive Summary Many companies today are in the mode of buying technology and then figuring out how to adopt their operations to fit its processing requirements.

More information

SOFTWARE REQUIREMENTS

SOFTWARE REQUIREMENTS SOFTWARE REQUIREMENTS http://www.tutorialspoint.com/software_engineering/software_requirements.htm Copyright tutorialspoint.com The software requirements are description of features and functionalities

More information

Using Rational Software Solutions to Achieve CMMI Level 2

Using Rational Software Solutions to Achieve CMMI Level 2 Copyright Rational Software 2003 http://www.therationaledge.com/content/jan_03/f_cmmi_rr.jsp Using Rational Software Solutions to Achieve CMMI Level 2 by Rolf W. Reitzig Founder, Cognence, Inc. Over the

More information

IBM Rational systems and software solutions for the medical device industry

IBM Rational systems and software solutions for the medical device industry IBM Software August 2011 IBM Rational systems and software solutions for the medical device industry Improve processes, manage IEC 61508 and IEC 62304 standards, develop quality products Highlights Manage

More information

SOFTWARE PERFORMANCE EVALUATION ALGORITHM EXPERIMENT FOR IN-HOUSE SOFTWARE USING INTER-FAILURE DATA

SOFTWARE PERFORMANCE EVALUATION ALGORITHM EXPERIMENT FOR IN-HOUSE SOFTWARE USING INTER-FAILURE DATA I.J.E.M.S., VOL.3(2) 2012: 99-104 ISSN 2229-6425 SOFTWARE PERFORMANCE EVALUATION ALGORITHM EXPERIMENT FOR IN-HOUSE SOFTWARE USING INTER-FAILURE DATA *Jimoh, R. G. & Abikoye, O. C. Computer Science Department,

More information

Process Models and Metrics

Process Models and Metrics Process Models and Metrics PROCESS MODELS AND METRICS These models and metrics capture information about the processes being performed We can model and measure the definition of the process process performers

More information

PHASE 9: OPERATIONS AND MAINTENANCE PHASE

PHASE 9: OPERATIONS AND MAINTENANCE PHASE PHASE 9: OPERATIONS AND MAINTENANCE PHASE During the Operations and Maintenance Phase, the information system s availability and performance in executing the work for which it was designed is maintained.

More information

Software Testing Interview Questions

Software Testing Interview Questions Software Testing Interview Questions 1. What s the Software Testing? A set of activities conducted with the intent of finding errors in software. 2.What is Acceptance Testing? Testing conducted to enable

More information

ITL BULLETIN FOR JUNE 2012 CLOUD COMPUTING: A REVIEW OF FEATURES, BENEFITS, AND RISKS, AND RECOMMENDATIONS FOR SECURE, EFFICIENT IMPLEMENTATIONS

ITL BULLETIN FOR JUNE 2012 CLOUD COMPUTING: A REVIEW OF FEATURES, BENEFITS, AND RISKS, AND RECOMMENDATIONS FOR SECURE, EFFICIENT IMPLEMENTATIONS ITL BULLETIN FOR JUNE 2012 CLOUD COMPUTING: A REVIEW OF FEATURES, BENEFITS, AND RISKS, AND RECOMMENDATIONS FOR SECURE, EFFICIENT IMPLEMENTATIONS Shirley Radack, Editor Computer Security Division Information

More information

Smarter Balanced Assessment Consortium. Recommendation

Smarter Balanced Assessment Consortium. Recommendation Smarter Balanced Assessment Consortium Recommendation Smarter Balanced Quality Assurance Approach Recommendation for the Smarter Balanced Assessment Consortium 20 July 2012 Summary When this document was

More information

An Enterprise Framework for Evaluating and Improving Software Quality

An Enterprise Framework for Evaluating and Improving Software Quality An Enterprise Framework for Evaluating and Improving Software Quality Abstract Philip Lew philip.lew@xbosoft.com With the world s economy increasingly driven by software products, there has been a relentless

More information

TITLE: Control of Software

TITLE: Control of Software Page 1 of 8 TITLE: Control of Software WARNING This document is the property of United Technologies Corporation (UTC). You may not possess, use, copy or disclose this document or any information in it,

More information

International Association of Scientific Innovation and Research (IASIR) (An Association Unifying the Sciences, Engineering, and Applied Research)

International Association of Scientific Innovation and Research (IASIR) (An Association Unifying the Sciences, Engineering, and Applied Research) International Association of Scientific Innovation and Research (IASIR) (An Association Unifying the Sciences, Engineering, and Applied Research) International Journal of Engineering, Business and Enterprise

More information

Comparative Analysis of Different Software Quality Models

Comparative Analysis of Different Software Quality Models Comparative Analysis of Different Software Quality Models Ranbireshwar S. Jamwal, Deepshikha Jamwal & Devanand Padha Jamwal.grandee@gmail.com, Jamwal.shivani@gmail.com,dpadha@rediffmail.com Lecturer, Research

More information

DATA QUALITY DATA BASE QUALITY INFORMATION SYSTEM QUALITY

DATA QUALITY DATA BASE QUALITY INFORMATION SYSTEM QUALITY DATA QUALITY DATA BASE QUALITY INFORMATION SYSTEM QUALITY The content of those documents are the exclusive property of REVER. The aim of those documents is to provide information and should, in no case,

More information

Description of Services for A Quality Assurance Engineer for SQA Assignment for eservices Development Projects ICTA/CON/IC/P5/411B

Description of Services for A Quality Assurance Engineer for SQA Assignment for eservices Development Projects ICTA/CON/IC/P5/411B Description of Services for A Quality Assurance Engineer for SQA Assignment for eservices Development Projects ICTA/CON/IC/P5/411B 1. Introduction The Information and Communication Technology Agency of

More information

074-8432-552 Page 1 of 7 Effective Date: 12/18/03 Software Supplier Process Requirements

074-8432-552 Page 1 of 7 Effective Date: 12/18/03 Software Supplier Process Requirements Page 1 of 7 Software Supplier Process Requirements 1.0 QUALITY SYSTEM FRAMEWORK 1.1 QUALITY POLICY The Seller shall document and implement a quality program in the form of Quality manual or detailed Quality

More information

CMMI for Development Quick Reference

CMMI for Development Quick Reference CAUSAL ANALYSIS AND RESOLUTION SUPPORT (ML5) The purpose of Causal Analysis and Resolution (CAR) is to identify causes of selected outcomes and take action to improve process performance. SG 1 Root causes

More information

Software Configuration Management Plan

Software Configuration Management Plan For Database Applications Document ID: Version: 2.0c Planning Installation & Acceptance Integration & Test Requirements Definition Design Development 1 / 22 Copyright 2000-2005 Digital Publications LLC.

More information

Software Engineering Question Bank

Software Engineering Question Bank Software Engineering Question Bank 1) What is Software Development Life Cycle? (SDLC) System Development Life Cycle (SDLC) is the overall process of developing information systems through a multi-step

More information

http://www.test-institute.org International Software Test Institute

http://www.test-institute.org International Software Test Institute THE ONLY BOOK CAN SIMPLY LEARN SOFTWARE TESTING! Page 1 Contents ABOUT THE AUTHOR... 3 1. Introduction To Software Testing... 4 2. What is Software Quality Assurance?... 7 3. What Is Software Testing?...

More information

The document you download is the copyright of ISO, and may not be stored, reproduced, transferred or resold by any means, except as follows.

The document you download is the copyright of ISO, and may not be stored, reproduced, transferred or resold by any means, except as follows. Licence Agreement You are about to download material which is subject to strict copyright conditions. Please read these terms and conditions carefully. By accepting them, you are entering into a binding

More information

Requirements engineering and quality attributes

Requirements engineering and quality attributes Open Learning Universiteit Unit 2 Learning Unit 2 Requirements engineering and quality attributes Contents Introduction............................................... 21 2.1 Important concepts........................................

More information

CS 1632 SOFTWARE QUALITY ASSURANCE. 2 Marks. Sample Questions and Answers

CS 1632 SOFTWARE QUALITY ASSURANCE. 2 Marks. Sample Questions and Answers CS 1632 SOFTWARE QUALITY ASSURANCE 2 Marks Sample Questions and Answers 1. Define quality. Quality is the degree of goodness of a product or service or perceived by the customer. Quality concept is the

More information

Project Risk Management: IV&V as Insurance for Project Success

Project Risk Management: IV&V as Insurance for Project Success Project Risk Management: IV&V as Insurance for Project Success Introduction Software development projects can be expensive and risky: Ever more complex mission-critical requirements lead to increasingly

More information

Software Engineering. Introduction. Software Costs. Software is Expensive [Boehm] ... Columbus set sail for India. He ended up in the Bahamas...

Software Engineering. Introduction. Software Costs. Software is Expensive [Boehm] ... Columbus set sail for India. He ended up in the Bahamas... Software Engineering Introduction... Columbus set sail for India. He ended up in the Bahamas... The economies of ALL developed nations are dependent on software More and more systems are software controlled

More information

Chapter 24 - Quality Management. Lecture 1. Chapter 24 Quality management

Chapter 24 - Quality Management. Lecture 1. Chapter 24 Quality management Chapter 24 - Quality Management Lecture 1 1 Topics covered Software quality Software standards Reviews and inspections Software measurement and metrics 2 Software quality management Concerned with ensuring

More information