Quality is defined as the degree of goodness of a product or service as perceived by customers. Software quality refers to the totality of features and characteristics of software that bear on its ability to satisfy needs. There are various views of quality including the transcendent view, product-based view, value-based view, manufacturing view, and user-based view. Quality is measured using metrics that are linked to quality criteria and can objectively determine the level of a given criterion. Software quality measurement faces issues like quality being non-absolute and multidimensional.
The document describes the Goal Question Metric (GQM) approach for defining and interpreting operational and measurable software goals. The GQM approach defines goals at the conceptual level, then refines each goal into questions at the operational level, and finally associates metrics at the quantitative level to answer each question. An example GQM model is provided to illustrate how to structure goals, questions, and metrics in a hierarchical manner to measure a specific goal of improving the timeliness of change request processing. The GQM approach combines product, process, and resource measurement to provide a framework for defining measurable goals tailored to an organization.
This document provides course materials for the subject of Software Quality Management taught in the 8th semester of the Computer Science and Engineering department at A.V.C. College of Engineering in Mannampandal, India. It includes the syllabus, course objectives, textbook information, and an introductory section on fundamentals of software quality covering topics like hierarchical quality models, quality measurement, and metrics.
The document discusses quality standards, practices, and conventions for software testing and quality assurance. It covers topics such as software testing types, quality assurance, quality concepts, software standards organizations, basic practices like reviews and inspections, and coding conventions. Software configuration management is also introduced which involves tracking and controlling changes in software.
This document discusses definitions of software quality from Deming, Feigenbaum, and Juran. It also discusses different types of quality like external/functional quality which is compliance to requirements/specifications, and internal/structural quality like robustness and maintainability. Motivations for quality include risk and cost management. Improving quality involves choosing standards, defining metrics to measure against them, testing, analyzing, reviewing code, refactoring, and automating processes. Simplicity is important for reliability according to Dijkstra. Quality is an ongoing effort not a one-time thing.
Software quality program and establishiment coceptsGuruKrishnaTeja
Â
This document outlines the key concepts and objectives of a Software Quality Program (SQP). The SQP establishes quality requirements, defines development and maintenance processes, and uses metrics to measure productivity, quality, and documentation. It plans evaluations of software and development processes. Responsibility for the SQP is assigned and its procedures, tools, and records are documented. The SQP scope identifies deliverables and ensures the desired quality is achieved. It defines referenced documents, procedures, tools, records, and establishes tasks like data collection and quality planning to develop high quality software.
Enhancing Software Quality Using Agile TechniquesIOSR Journals
Â
This document discusses how agile techniques can enhance software quality. It begins by defining software quality factors and quality assurance. It then provides an overview of the agile development lifecycle and highlights key techniques like system metaphor, architectural spike, onsite customer feedbacks, refactoring, pair programming, stand-up meetings, and continuous integration. These techniques are described in detail and how they help improve specific quality factors like correctness, maintainability, reliability, usability, testability, flexibility and others. The document concludes by summarizing how agile techniques can be evaluated to enhance software quality based on these factors.
Syed Zaffar Iqbal, Prof. Urwa Javed and Dr. Shakeel Ahmed Roshan. Department of Computer Science, Alhamd Islamic University, Pakistan. âSoftware Quality Assurance Model for Software Excellence with Its Requirementsâ United International Journal for Research & Technology (UIJRT) 1.1 (2019): 39-43.
The document describes the Goal Question Metric (GQM) approach for defining and interpreting operational and measurable software goals. The GQM approach defines goals at the conceptual level, then refines each goal into questions at the operational level, and finally associates metrics at the quantitative level to answer each question. An example GQM model is provided to illustrate how to structure goals, questions, and metrics in a hierarchical manner to measure a specific goal of improving the timeliness of change request processing. The GQM approach combines product, process, and resource measurement to provide a framework for defining measurable goals tailored to an organization.
This document provides course materials for the subject of Software Quality Management taught in the 8th semester of the Computer Science and Engineering department at A.V.C. College of Engineering in Mannampandal, India. It includes the syllabus, course objectives, textbook information, and an introductory section on fundamentals of software quality covering topics like hierarchical quality models, quality measurement, and metrics.
The document discusses quality standards, practices, and conventions for software testing and quality assurance. It covers topics such as software testing types, quality assurance, quality concepts, software standards organizations, basic practices like reviews and inspections, and coding conventions. Software configuration management is also introduced which involves tracking and controlling changes in software.
This document discusses definitions of software quality from Deming, Feigenbaum, and Juran. It also discusses different types of quality like external/functional quality which is compliance to requirements/specifications, and internal/structural quality like robustness and maintainability. Motivations for quality include risk and cost management. Improving quality involves choosing standards, defining metrics to measure against them, testing, analyzing, reviewing code, refactoring, and automating processes. Simplicity is important for reliability according to Dijkstra. Quality is an ongoing effort not a one-time thing.
Software quality program and establishiment coceptsGuruKrishnaTeja
Â
This document outlines the key concepts and objectives of a Software Quality Program (SQP). The SQP establishes quality requirements, defines development and maintenance processes, and uses metrics to measure productivity, quality, and documentation. It plans evaluations of software and development processes. Responsibility for the SQP is assigned and its procedures, tools, and records are documented. The SQP scope identifies deliverables and ensures the desired quality is achieved. It defines referenced documents, procedures, tools, records, and establishes tasks like data collection and quality planning to develop high quality software.
Enhancing Software Quality Using Agile TechniquesIOSR Journals
Â
This document discusses how agile techniques can enhance software quality. It begins by defining software quality factors and quality assurance. It then provides an overview of the agile development lifecycle and highlights key techniques like system metaphor, architectural spike, onsite customer feedbacks, refactoring, pair programming, stand-up meetings, and continuous integration. These techniques are described in detail and how they help improve specific quality factors like correctness, maintainability, reliability, usability, testability, flexibility and others. The document concludes by summarizing how agile techniques can be evaluated to enhance software quality based on these factors.
Syed Zaffar Iqbal, Prof. Urwa Javed and Dr. Shakeel Ahmed Roshan. Department of Computer Science, Alhamd Islamic University, Pakistan. âSoftware Quality Assurance Model for Software Excellence with Its Requirementsâ United International Journal for Research & Technology (UIJRT) 1.1 (2019): 39-43.
The document discusses software quality and achieving high quality software. It notes that software companies often deliver software with known bugs and that low quality software increases risks for developers and users. It also discusses the costs of quality and how management decisions impact quality. Achieving quality involves software engineering methods, project management techniques, quality control, and quality assurance. Reviews, testing, and validation are important parts of the quality process.
This document outlines the software quality plan for an airline reservation system project. It discusses roles in quality assurance including developers writing unit tests, an on-site customer for acceptance testing, and QA ensuring quality and functionality. It also covers risk management, prioritizing use cases, infrastructure and component testing for the application server, database, OS, and hardware. User acceptance testing approaches are defined using test tools and test scenarios from user stories. Training and disaster recovery plans are also summarized.
A Novel Method for Quantitative Assessment of Software QualityCSCJournals
Â
This paper deals with quantitative quality model that needs to be practiced formally through out the software development life cycle at each phase. Proposed quality model emphasizes that various stakeholders need to be consulted for quality requirements. The quality goals are set through various measurements and metrics. Software under development is evaluated against expected value of set of metrics. The use of proposed quantitative model is illustrated through a simple case study. The unaddressed quality attribute reusability in ISO 9126 is also discussed.
The document discusses various software quality factors that should be considered when developing software. It identifies the need for comprehensive requirements documents to ensure user needs are fully met. It then describes several quality factors models proposed by researchers and groups the factors into categories like product operation, revision, and transition factors. Key factors discussed in detail include correctness, reliability, efficiency, integrity, usability, maintainability, flexibility, testability, portability, reusability and interoperability.
This document discusses software quality and its attributes. It defines software quality as conformance to functional and performance requirements, development standards, and implicit expectations. Problems in ensuring quality include incomplete specifications and tensions between different stakeholder needs. Quality is described using a hierarchical model, with attributes including reliability, efficiency, usability, maintainability, and portability. Internal attributes like correctness, verifiability and understandability contribute to external attributes like reliability, usability and maintainability. Productivity, timeliness and visibility are described as important process quality attributes.
The document discusses key concepts in software quality including:
1) The relationships between software errors, faults, and failures and their causes during development.
2) The importance of software quality and quality assurance objectives like defect prevention and removal.
3) Quality assurance techniques like verification, validation, inspections, testing and standards to evaluate conformance.
4) How quality is managed through metrics, process engineering, and cost controls.
Testability measurement model for object oriented design (tmmood)ijcsit
Â
Measuring testability early in the development life cycle especially at design phase is a criterion of crucial importance to software designers, developers, quality controllers and practitioners. However, most of the
mechanism available for testability measurement may be used in the later phases of development life cycle.
Early estimation of testability, absolutely at design phase helps designers to improve their designs before
the coding starts. Practitioners regularly advocate that testability should be planned early in design phase.
Testability measurement early in design phase is greatly emphasized in this study; hence, considered significant for the delivery of quality software. As a result, it extensively reduces rework during and after implementation, as well as facilitate for design effective test plans, better project and resource planning in a practical manner, with a focus on the design phase. An effort has been put forth in this paper to recognize the key factors contributing in testability measurement at design phase. Additionally, testability
measurement model is developed to quantify software testability at design phase. Furthermore, the relationship of Testability with these factors has been tested and justified with the help of statistical measures. The developed model has been validated using experimental tryout. Finally, it incorporates the empirical validation of the testability measurement model as the authorâs most important contribution.
The document discusses software quality management. It covers quality fundamentals like culture, costs and models. It describes quality management processes like quality assurance, verification and validation, reviews and audits. It discusses quality requirements, defect characterization and management techniques like static, people-intensive and dynamic techniques. The document provides details on quality measurement and testing to ensure software quality.
This document discusses software engineering and software quality assurance. It begins by defining software and describing a case study on the Therac-25 radiation therapy machine which suffered from a software failure disaster. It then covers classification of causes of software errors, definitions of software quality from IEEE and Pressman, and objectives of SQA activities. Key causes of errors listed include faulty requirements, client-developer communication failures, deliberate deviations from requirements, logical design errors, coding errors, non-compliance with documentation, shortcomings in testing, procedure errors, and documentation errors. The document also discusses definitions of quality assurance and quality control and the goals of SQA in software development and maintenance.
This document summarizes a survey paper on agile methods and quality assurance. The paper presents 4 sections: [1] An overview of agile methods and how they relate to quality assurance. Some key quality techniques in agile like refactoring and test-driven development are discussed. [2] How quality is handled within agile development processes, with a focus on defect discovery and refactoring. [3] How quality is addressed within agile management practices, discussing people capability models. [4] Examples of applying quality practices in real-world agile projects. The paper aims to understand how quality is incorporated into agile methods and identify areas for further improvement.
This document discusses software quality management standards. It defines software quality and explains that standards aim to manage quality and development processes. The document outlines three major standards activities: software quality assurance which establishes organizational procedures; software quality plans which select applicable procedures for a project; and software quality control which ensures procedures are followed. It provides examples of standards organizations and types of standards including quality assurance, project management, system engineering, safety, and product standards. The document also notes some problems with software quality standards.
The document provides details on the ISTQB Advanced Level Certification study guide. It discusses 20 questions and their answers related to software development processes and quality assurance. Key topics covered include software requirements, design, coding, testing, configuration audits, error reporting systems, and defect categorization.
This document discusses software quality assurance and testing. It provides definitions of key terms like software quality, errors, faults and failures. It also lists common causes of software errors and characteristics that differentiate software from other products. Software quality assurance is defined as a planned set of activities to provide confidence that software conforms to requirements, while quality control evaluates quality after development. The objectives of software quality assurance are also prevention of defects rather than finding them after development.
This document discusses software quality factors and McCall's quality factor model. It describes McCall's three main quality factor categories: product operation factors, product revision factors, and product transition factors. Under product operation factors, it outlines reliability, correctness, integrity, efficiency, and usability requirements. It then discusses product revision factors of maintainability, flexibility, and testability. Finally, it covers product transition factors including portability, reusability, and interoperability. The document provides details on the specific requirements for each quality factor.
IRJET- Factors Affecting the Delivery of Quality Software and their Relations...IRJET Journal
Â
This document discusses factors that affect the delivery of quality software and their relationship to the software development process. It identifies key factors such as the amount of testing, costs involved, time spent, and following proper software development life cycle (SDLC) phases. The document presents a literature review on how these factors influence software quality. It then defines variables, hypotheses, and a regression model to analyze the relationship between delivery of quality software and the identified factors. The results of distributing and analyzing questionnaires indicate that amount of testing, costs involved, and time spent have a statistically significant correlation with delivering quality software. Therefore, paying attention to these factors during development can help improve software quality.
The document discusses the elusive nature of software quality. It defines quality as meeting user requirements as well as usability factors. Measuring quality is challenging as it depends on perspectives. Process improvements like total quality management, six sigma and software quality function deployment can help improve quality by focusing on customer needs and continuous process enhancement. However, achieving high quality is difficult given the complex nature of software and how it depends on many interconnected factors including hardware, people, processes, and other software.
The document discusses software quality management and outlines five units: introduction to software quality; software quality assurance; quality control and reliability; quality management systems; and quality standards. It defines quality, discusses hierarchical models of quality including those proposed by Boehm and McCall, and explains techniques for improving software quality like metrics, reviews, and standards.
The document discusses configuration management for ISTQB Advanced Level Certification. It provides definitions for configuration management and discusses its importance across the software development life cycle. It also discusses key requirements for successful configuration management like management commitment and a configuration management plan. Additionally, it covers how configuration management can save costs by reducing side effects from changes. Finally, it discusses configuration items, types of discrepancies and change requests, problems like simultaneous updates, and the relationship between quality assurance and the software life cycle.
Software Engineering Past Papers (Short Questions)MuhammadTalha436
Â
1. SWOT analysis is a framework for identifying internal and external factors that can impact a project, product, place or person. It analyzes strengths, weaknesses, opportunities, and threats.
2. Software refactoring is changing software code without altering external behavior to improve internal structure.
3. An embedded system is a programmed system within a larger mechanical or electrical system, often with real-time computing constraints and a dedicated function.
A New Model for Study of Quality Attributes to Components Based Development A...Kiogyf
Â
A New Model for Study of Quality Attributes to Components Based Development Approach
by bstract :
Software development costs, time - to release and quality product are important factors affecting the construction of software. Different types of tools and techniques are suggested by researchers to improve in delivering quality software systems with lower cost and reduce time to delivery. One such practice is development of software using ased Software Development (CBSD) techniques. CBSD recommended Component Bbuilding software systems using existing reusable components, instead of writing from scratch. The main objective of CBSD is to writes once and reuse any number of time with no or modification . Some of the advantages that a company may available by adapting CBSD for the Software development are shorter development time which results in meet tight dead line, increase productivity and Quality Product. CBSD also, s paper is to develop the new model of software support reusability. The aim of thiproduct and describe the characteristics of some selected of attributes of CBSD models that are widely practiced in software industries. We proposed a complete model for or reuse. This Model will cover both Component Based Software Development fcomponent based software development as well as Component development phases for
A - Model. This Model is represent one good solution for Component Based Development with reduce cost and time to deliverable and save the quality of product . Keywords: Component Based Approach, Quality Model, Quality Attributes, , A - Model for CBD .
1. Introduction
SOFTWARE ENGINEERING & ARCHITECTURE - SHORT NOTESsuthi
Â
The document discusses various topics related to software engineering and architecture including what software engineering is, the characteristics and categories of software, software processes and models, system engineering, software testing, and analysis and design modeling. Specifically, it defines software engineering as applying theories, methods and tools to develop professional software. It also discusses fundamental software process activities like specification, design, validation and evolution. Finally, it defines analysis modeling as describing customer requirements, establishing a basis for design, and devising valid requirements for building software.
The document discusses software quality and achieving high quality software. It notes that software companies often deliver software with known bugs and that low quality software increases risks for developers and users. It also discusses the costs of quality and how management decisions impact quality. Achieving quality involves software engineering methods, project management techniques, quality control, and quality assurance. Reviews, testing, and validation are important parts of the quality process.
This document outlines the software quality plan for an airline reservation system project. It discusses roles in quality assurance including developers writing unit tests, an on-site customer for acceptance testing, and QA ensuring quality and functionality. It also covers risk management, prioritizing use cases, infrastructure and component testing for the application server, database, OS, and hardware. User acceptance testing approaches are defined using test tools and test scenarios from user stories. Training and disaster recovery plans are also summarized.
A Novel Method for Quantitative Assessment of Software QualityCSCJournals
Â
This paper deals with quantitative quality model that needs to be practiced formally through out the software development life cycle at each phase. Proposed quality model emphasizes that various stakeholders need to be consulted for quality requirements. The quality goals are set through various measurements and metrics. Software under development is evaluated against expected value of set of metrics. The use of proposed quantitative model is illustrated through a simple case study. The unaddressed quality attribute reusability in ISO 9126 is also discussed.
The document discusses various software quality factors that should be considered when developing software. It identifies the need for comprehensive requirements documents to ensure user needs are fully met. It then describes several quality factors models proposed by researchers and groups the factors into categories like product operation, revision, and transition factors. Key factors discussed in detail include correctness, reliability, efficiency, integrity, usability, maintainability, flexibility, testability, portability, reusability and interoperability.
This document discusses software quality and its attributes. It defines software quality as conformance to functional and performance requirements, development standards, and implicit expectations. Problems in ensuring quality include incomplete specifications and tensions between different stakeholder needs. Quality is described using a hierarchical model, with attributes including reliability, efficiency, usability, maintainability, and portability. Internal attributes like correctness, verifiability and understandability contribute to external attributes like reliability, usability and maintainability. Productivity, timeliness and visibility are described as important process quality attributes.
The document discusses key concepts in software quality including:
1) The relationships between software errors, faults, and failures and their causes during development.
2) The importance of software quality and quality assurance objectives like defect prevention and removal.
3) Quality assurance techniques like verification, validation, inspections, testing and standards to evaluate conformance.
4) How quality is managed through metrics, process engineering, and cost controls.
Testability measurement model for object oriented design (tmmood)ijcsit
Â
Measuring testability early in the development life cycle especially at design phase is a criterion of crucial importance to software designers, developers, quality controllers and practitioners. However, most of the
mechanism available for testability measurement may be used in the later phases of development life cycle.
Early estimation of testability, absolutely at design phase helps designers to improve their designs before
the coding starts. Practitioners regularly advocate that testability should be planned early in design phase.
Testability measurement early in design phase is greatly emphasized in this study; hence, considered significant for the delivery of quality software. As a result, it extensively reduces rework during and after implementation, as well as facilitate for design effective test plans, better project and resource planning in a practical manner, with a focus on the design phase. An effort has been put forth in this paper to recognize the key factors contributing in testability measurement at design phase. Additionally, testability
measurement model is developed to quantify software testability at design phase. Furthermore, the relationship of Testability with these factors has been tested and justified with the help of statistical measures. The developed model has been validated using experimental tryout. Finally, it incorporates the empirical validation of the testability measurement model as the authorâs most important contribution.
The document discusses software quality management. It covers quality fundamentals like culture, costs and models. It describes quality management processes like quality assurance, verification and validation, reviews and audits. It discusses quality requirements, defect characterization and management techniques like static, people-intensive and dynamic techniques. The document provides details on quality measurement and testing to ensure software quality.
This document discusses software engineering and software quality assurance. It begins by defining software and describing a case study on the Therac-25 radiation therapy machine which suffered from a software failure disaster. It then covers classification of causes of software errors, definitions of software quality from IEEE and Pressman, and objectives of SQA activities. Key causes of errors listed include faulty requirements, client-developer communication failures, deliberate deviations from requirements, logical design errors, coding errors, non-compliance with documentation, shortcomings in testing, procedure errors, and documentation errors. The document also discusses definitions of quality assurance and quality control and the goals of SQA in software development and maintenance.
This document summarizes a survey paper on agile methods and quality assurance. The paper presents 4 sections: [1] An overview of agile methods and how they relate to quality assurance. Some key quality techniques in agile like refactoring and test-driven development are discussed. [2] How quality is handled within agile development processes, with a focus on defect discovery and refactoring. [3] How quality is addressed within agile management practices, discussing people capability models. [4] Examples of applying quality practices in real-world agile projects. The paper aims to understand how quality is incorporated into agile methods and identify areas for further improvement.
This document discusses software quality management standards. It defines software quality and explains that standards aim to manage quality and development processes. The document outlines three major standards activities: software quality assurance which establishes organizational procedures; software quality plans which select applicable procedures for a project; and software quality control which ensures procedures are followed. It provides examples of standards organizations and types of standards including quality assurance, project management, system engineering, safety, and product standards. The document also notes some problems with software quality standards.
The document provides details on the ISTQB Advanced Level Certification study guide. It discusses 20 questions and their answers related to software development processes and quality assurance. Key topics covered include software requirements, design, coding, testing, configuration audits, error reporting systems, and defect categorization.
This document discusses software quality assurance and testing. It provides definitions of key terms like software quality, errors, faults and failures. It also lists common causes of software errors and characteristics that differentiate software from other products. Software quality assurance is defined as a planned set of activities to provide confidence that software conforms to requirements, while quality control evaluates quality after development. The objectives of software quality assurance are also prevention of defects rather than finding them after development.
This document discusses software quality factors and McCall's quality factor model. It describes McCall's three main quality factor categories: product operation factors, product revision factors, and product transition factors. Under product operation factors, it outlines reliability, correctness, integrity, efficiency, and usability requirements. It then discusses product revision factors of maintainability, flexibility, and testability. Finally, it covers product transition factors including portability, reusability, and interoperability. The document provides details on the specific requirements for each quality factor.
IRJET- Factors Affecting the Delivery of Quality Software and their Relations...IRJET Journal
Â
This document discusses factors that affect the delivery of quality software and their relationship to the software development process. It identifies key factors such as the amount of testing, costs involved, time spent, and following proper software development life cycle (SDLC) phases. The document presents a literature review on how these factors influence software quality. It then defines variables, hypotheses, and a regression model to analyze the relationship between delivery of quality software and the identified factors. The results of distributing and analyzing questionnaires indicate that amount of testing, costs involved, and time spent have a statistically significant correlation with delivering quality software. Therefore, paying attention to these factors during development can help improve software quality.
The document discusses the elusive nature of software quality. It defines quality as meeting user requirements as well as usability factors. Measuring quality is challenging as it depends on perspectives. Process improvements like total quality management, six sigma and software quality function deployment can help improve quality by focusing on customer needs and continuous process enhancement. However, achieving high quality is difficult given the complex nature of software and how it depends on many interconnected factors including hardware, people, processes, and other software.
The document discusses software quality management and outlines five units: introduction to software quality; software quality assurance; quality control and reliability; quality management systems; and quality standards. It defines quality, discusses hierarchical models of quality including those proposed by Boehm and McCall, and explains techniques for improving software quality like metrics, reviews, and standards.
The document discusses configuration management for ISTQB Advanced Level Certification. It provides definitions for configuration management and discusses its importance across the software development life cycle. It also discusses key requirements for successful configuration management like management commitment and a configuration management plan. Additionally, it covers how configuration management can save costs by reducing side effects from changes. Finally, it discusses configuration items, types of discrepancies and change requests, problems like simultaneous updates, and the relationship between quality assurance and the software life cycle.
Software Engineering Past Papers (Short Questions)MuhammadTalha436
Â
1. SWOT analysis is a framework for identifying internal and external factors that can impact a project, product, place or person. It analyzes strengths, weaknesses, opportunities, and threats.
2. Software refactoring is changing software code without altering external behavior to improve internal structure.
3. An embedded system is a programmed system within a larger mechanical or electrical system, often with real-time computing constraints and a dedicated function.
A New Model for Study of Quality Attributes to Components Based Development A...Kiogyf
Â
A New Model for Study of Quality Attributes to Components Based Development Approach
by bstract :
Software development costs, time - to release and quality product are important factors affecting the construction of software. Different types of tools and techniques are suggested by researchers to improve in delivering quality software systems with lower cost and reduce time to delivery. One such practice is development of software using ased Software Development (CBSD) techniques. CBSD recommended Component Bbuilding software systems using existing reusable components, instead of writing from scratch. The main objective of CBSD is to writes once and reuse any number of time with no or modification . Some of the advantages that a company may available by adapting CBSD for the Software development are shorter development time which results in meet tight dead line, increase productivity and Quality Product. CBSD also, s paper is to develop the new model of software support reusability. The aim of thiproduct and describe the characteristics of some selected of attributes of CBSD models that are widely practiced in software industries. We proposed a complete model for or reuse. This Model will cover both Component Based Software Development fcomponent based software development as well as Component development phases for
A - Model. This Model is represent one good solution for Component Based Development with reduce cost and time to deliverable and save the quality of product . Keywords: Component Based Approach, Quality Model, Quality Attributes, , A - Model for CBD .
1. Introduction
SOFTWARE ENGINEERING & ARCHITECTURE - SHORT NOTESsuthi
Â
The document discusses various topics related to software engineering and architecture including what software engineering is, the characteristics and categories of software, software processes and models, system engineering, software testing, and analysis and design modeling. Specifically, it defines software engineering as applying theories, methods and tools to develop professional software. It also discusses fundamental software process activities like specification, design, validation and evolution. Finally, it defines analysis modeling as describing customer requirements, establishing a basis for design, and devising valid requirements for building software.
The document discusses various software development methodologies and concepts. It describes methodology types like waterfall, rapid application development, spiral, incremental, V-model, and iterative V-model. It also covers the software development life cycle phases of initiation, definition, design, programming/testing, evaluation, and installation. Finally, it discusses defining requirements, methodology maturity, staff competency, configuration management, and measuring the impact of the development process.
ISOIEC 9126Software engineering â Product quality was an intern.docxpriestmanmable
Â
ISO/IEC 9126Software engineering â Product quality was an international standard for the evaluation of software quality. It has been replaced by ISO/IEC 25010:2011. The fundamental objective of the ISO/IEC 9126 standard is to address some of the well known human biases that can adversely affect the delivery and perception of a software development project. These biases include changing priorities after the start of a project or not having any clear definitions of "success." By clarifying, then agreeing on the project priorities and subsequently converting abstract priorities (compliance) to measurable values (output data can be validated against schema X with zero intervention), ISO/IEC 9126 tries to develop a common understanding of the project's objectives and goals.
Quality model
The quality model presented in the first part of the standard, ISO/IEC 9126-1, classifies software quality in a structured set of characteristics and sub-characteristics as follows:
1. Functionality - A set of attributes that bear on the existence of a set of functions and their specified properties. The functions are those that satisfy stated or implied needs.
a. Suitability
b. Accuracy
c. Interoperability
d. Security
e. Functionality Compliance
2. Reliability - A set of attributes that bear on the capability of software to maintain its level of performance under stated conditions for a stated period of time.
a. Maturity
b. Fault Tolerance
c. Recoverability
d. Reliability Compliance
3. Usability - A set of attributes that bear on the effort needed for use, and on the individual assessment of such use, by a stated or implied set of users.
a. Understandability
b. Learnability
c. Operability
d. Attractiveness
e. Usability Compliance
4. Efficiency - A set of attributes that bear on the relationship between the level of performance of the software and the amount of resources used, under stated conditions.
a. Time Behaviour
b. Resource Utilization
c. Efficiency Compliance
5. Maintainability - A set of attributes that bear on the effort needed to make specified modifications.
a. Analyzability
b. Changeability
c. Stability
d. Testability
e. Maintainability Compliance
6. Portability - A set of attributes that bear on the ability of software to be transferred from one environment to another.
a. Adaptability
b. Installability
c. Co-Existence
d. Replaceability
e. Portability Compliance
¡ Quality in use metrics.
Quality in use metrics is only available when the final product is used in real conditions.
Ideally, the internal quality determines the external quality and external quality determines quality in use.
This standard stems from the GE model for describing software quality, presented in 1977 by McCall et al., which is organized around three types of Quality Characteristics:
¡ Factors (To specify): They describe the external view of the software, as viewed by the users.
¡ Criteria (To build): They describe the internal view of the software, as seen by the develop ...
The document discusses software quality standards as defined by ISO/IEC. It introduces ISO/IEC 9126 as one of the best software quality standards, which specifies required software product quality for development and evaluation. ISO/IEC 9126 defines a quality model consisting of six main quality characteristics - functionality, reliability, usability, efficiency, maintainability, and portability - which are further divided into sub-characteristics.
The document discusses several key dimensions and definitions of quality in software development. It describes quality as meeting requirements, meeting user needs and expectations, and being developed according to sound engineering practices. The quality process involves planning, assurance, control and prevention of defects. Testing is important but has limitations - it occurs late, catches only code issues, and does not ensure other quality attributes. Quality assurance involves standards, reviews, audits and feedback to stakeholders throughout the development lifecycle.
AN IMPROVED REPOSITORY STRUCTURE TO IDENTIFY, SELECT AND INTEGRATE COMPONENTS...ijseajournal
Â
An ultimate goal of software development is to build high quality products. The customers of software
industry always demand for high-quality products quickly and cost effectively. The component-based
development (CBD) is the most suitable methodology for the software companies to meet the demands of
target market. To opt CBD, the software development teams have to customize generic components that are
available in the market and it is very difficult for the development teams to choose the suitable components
from the millions of third party and commercial off the shelf (COTS) components. On the other hand, the
development of in-house repository is tedious and time consuming. In this paper, we propose an easy and
understandable repository structure to provide helpful information about stored components like how to
identify, select, retrieve and integrate components. The proposed repository will also provide previous
assessments of developers and end-users about the selected component. The proposed repository will help
the software companies by reducing the customization effort, improving the quality of developed software
and preventing integrating unfamiliar components.
A software system continues to grow in size and complexity, it becomes increasing difficult to
understand and manage. Software metrics are units of software measurement. As improvement in coding tools
allow software developer to produce larger amount of software to meet ever expanding requirements. A method
to measure software product, process and project must be used. In this article, we first introduce the software
metrics including the definition of metrics and the history of this field. We aim at a comprehensive survey of the
metrics available for measuring attributes related to software entities. Some classical metrics such as Lines of
codes LOC, Halstead complexity metric (HCM), Function Point analysis and others are discussed and
analyzed. Then we bring up the complexity metrics methods, such as McCabe complexity metrics and object
oriented metrics(C&K method), with real world examples. The comparison and relationship of these metrics are
also presented.
A comparative studies of software quality model for the software product eval...imdurgesh
Â
Actually, software products are increasing in a fast way and are used in almost all activities of human life.
Consequently measuring and evaluating the quality of a software product has become a critical task for many companies.
Several models have been proposed to help diverse types of users with quality issues. The development of techniques for
building software has influenced the creation of models to assess the quality. Since 2000 the construction of software
started to depend on generated or manufactured components and gave rise to new challenges in assessing quality.
These components introduce new concepts such as configurability, reusability, availability, better quality and lower cost.
Consequently, the models are classified into basic models which were developed until 2000, and those based on
components called tailored quality models. The purpose of this article is to describe the main models with their strengths
and point out some deficiencies. In this work, we conclude that in the present age, aspects of communications play an
important factor in the quality of the software.
Research Inventy : International Journal of Engineering and Scienceinventy
Â
Research Inventy : International Journal of Engineering and Science is published by the group of young academic and industrial researchers with 12 Issues per year. It is an online as well as print version open access journal that provides rapid publication (monthly) of articles in all areas of the subject such as: civil, mechanical, chemical, electronic and computer engineering as well as production and information technology. The Journal welcomes the submission of manuscripts that meet the general criteria of significance and scientific excellence. Papers will be published by rapid process within 20 days after acceptance and peer review process takes only 7 days. All articles published in Research Inventy will be peer-reviewed.
This document reviews quality assurance approaches for component-based software systems. It discusses how encapsulating functional and non-functional properties into individual reusable units can help meet quality demands like predictability and reusability. The paper analyzes prior work on quality assurance metrics and methods, comparing their approaches. While component-based development aims to improve quality, fully meeting all quality requirements remains challenging. More rigorous quality assessment is still needed.
A Review on Quality Assurance of Component- Based Software Systemiosrjce
Â
IOSR Journal of Computer Engineering (IOSR-JCE) is a double blind peer reviewed International Journal that provides rapid publication (within a month) of articles in all areas of computer engineering and its applications. The journal welcomes publications of high quality papers on theoretical developments and practical applications in computer technology. Original research papers, state-of-the-art reviews, and high quality technical notes are invited for publications.
This document provides an overview of how human-computer interaction (HCI) affects the software development process. It discusses how usability engineering promotes interactive system design and the software life cycle. The software life cycle involves requirements specification, design, implementation, testing, and maintenance. Iterative design and prototyping are important to overcome the limitations of traditional software development models. Usability metrics and standards help specify and test usability requirements. While iterative design has benefits, initial design decisions and a lack of understanding problems can limit its effectiveness.
PRODUCT QUALITY EVALUATION METHOD (PQEM): TO UNDERSTAND THE EVOLUTION OF QUAL...ijseajournal
Â
Promoting quality within the context of agile software development, it is extremely important as well as
useful to improve not only the knowledge and decision-making of project managers, product owners, and
quality assurance leaders but also to support the communication between teams. In this context, quality
needs to be visible in a synthetic and intuitive way in order to facilitate the decision of accepting or
rejecting each iteration within the software life cycle. This article introduces a novel solution called
Product Quality Evaluation Method (PQEM) which can be used to evaluate a set of quality characteristics
for each iteration within a software product life cycle. PQEM is based on the Goal-Question-Metric
approach, the standard ISO/IEC 25010, and the extension made of testing coverage in order to obtain the
quality coverage of each quality characteristic. The outcome of PQEM is a unique multidimensional value,
that represents the quality level reached by each iteration of a product, as an aggregated measure. Even
though a value it is not the regular idea of measuring quality, we believe that it can be useful to use this
value to easily understand the quality level of each iteration. An illustrative example of the PQEM method
was carried out with two iterations from a web and mobile application, within the healthcare environment.
A single measure makes it possible to observe the evolution of the level of quality reached in the evolution
of the product through the iterations.
A study of various viewpoints and aspects software quality perspectiveeSAT Journals
Â
Abstract The software quality is very important research of software engineering grown from the last two decades. The software engineering paradigm adopted by many organizations to develop the high quality software at affordable cost. The high quality software is considered as one of the key factor in the rapid growth of Global Software Development. The software metrics computes and evaluates the quality characteristics and used to take quantitative and qualitative decisions for risk assessment and reduction. The multiple stakeholders can view the software quality in multiple angles with various aspects. In this paper we present multiple views of the software quality with respect to various quality aspects. Key Words : Stakeholders, Functional aspect, Structural aspect, Process aspect, Metrics etc.
This document provides an overview of software quality assurance. It begins with the course outcomes, which focus on explaining software quality standards and models, applying various project management techniques like configuration management and quality assurance practices. It then discusses the uniqueness of software quality assurance compared to other products. Key differences include software's invisibility and complex nature. The document emphasizes that software quality assurance is an ongoing challenge due to these differences. It provides definitions of software quality and outlines the goals of software quality assurance activities.
This document discusses various concepts related to software quality management including quality, quality control, quality assurance, cost of quality, software quality assurance, statistical software quality assurance (SQA), quality evaluation standards like Six Sigma and ISO 9000 for software, Capability Maturity Model Integration (CMMI), and McCall's quality factors. It provides definitions and explanations of these concepts as well as activities involved in SQA like preparing an SQA plan and auditing software work products.
This document discusses the need for a metrics ecosystem to help design quality e-commerce systems based on ISO standards. It proposes a new framework that maps metrics to ISO 25010 quality characteristics and components of user-system interaction. The framework defines six key components of user interaction with e-commerce systems: presentation, navigation, purchasing, social, interaction, and support. It then presents a set of 29 new metrics focused on the functional suitability and usability quality characteristics, which are important targets for e-commerce system design. The metrics aim to provide insights for designers and developers to help produce quality e-commerce systems.
A METRICS ECOSYSTEM FOR DESIGNING QUALITY E-COMMERCE SYSTEMSijcsit
Â
E-commerce has become a prime channel for doing commerce both globally and locally. It has gained the
trust of buyers worldwide not only because of the supporting technologies but for the ever-increasing
quality of service provided by most vendors as well. Quality is and will be a competitive advantage in ecommerce
as competition on an international scale increases. Designing quality e-commerce software is
one battle that needs to be won in this war and tools such as formal standards are key weapons. In this
paper an eco-system of software quality metrics is presented based on the ISO25010 standard. These
metrics are mapped to quality characteristics of the software and to facets of user-system interaction so as
to provide designers and developers insights and guidelines on how produce quality e-commerce systems. A
representative set of 29 new metrics for the quality characteristics of Functional Suitability and Usability is
presented.
THE SACRIFICE HOW PRO-PALESTINE PROTESTS STUDENTS ARE SACRIFICING TO CHANGE T...indexPub
Â
The recent surge in pro-Palestine student activism has prompted significant responses from universities, ranging from negotiations and divestment commitments to increased transparency about investments in companies supporting the war on Gaza. This activism has led to the cessation of student encampments but also highlighted the substantial sacrifices made by students, including academic disruptions and personal risks. The primary drivers of these protests are poor university administration, lack of transparency, and inadequate communication between officials and students. This study examines the profound emotional, psychological, and professional impacts on students engaged in pro-Palestine protests, focusing on Generation Z's (Gen-Z) activism dynamics. This paper explores the significant sacrifices made by these students and even the professors supporting the pro-Palestine movement, with a focus on recent global movements. Through an in-depth analysis of printed and electronic media, the study examines the impacts of these sacrifices on the academic and personal lives of those involved. The paper highlights examples from various universities, demonstrating student activism's long-term and short-term effects, including disciplinary actions, social backlash, and career implications. The researchers also explore the broader implications of student sacrifices. The findings reveal that these sacrifices are driven by a profound commitment to justice and human rights, and are influenced by the increasing availability of information, peer interactions, and personal convictions. The study also discusses the broader implications of this activism, comparing it to historical precedents and assessing its potential to influence policy and public opinion. The emotional and psychological toll on student activists is significant, but their sense of purpose and community support mitigates some of these challenges. However, the researchers call for acknowledging the broader Impact of these sacrifices on the future global movement of FreePalestine.
A Visual Guide to 1 Samuel | A Tale of Two HeartsSteve Thomason
Â
These slides walk through the story of 1 Samuel. Samuel is the last judge of Israel. The people reject God and want a king. Saul is anointed as the first king, but he is not a good king. David, the shepherd boy is anointed and Saul is envious of him. David shows honor while Saul continues to self destruct.
Level 3 NCEA - NZ: A Nation In the Making 1872 - 1900 SML.pptHenry Hollis
Â
The History of NZ 1870-1900.
Making of a Nation.
From the NZ Wars to Liberals,
Richard Seddon, George Grey,
Social Laboratory, New Zealand,
Confiscations, Kotahitanga, Kingitanga, Parliament, Suffrage, Repudiation, Economic Change, Agriculture, Gold Mining, Timber, Flax, Sheep, Dairying,
Elevate Your Nonprofit's Online Presence_ A Guide to Effective SEO Strategies...TechSoup
Â
Whether you're new to SEO or looking to refine your existing strategies, this webinar will provide you with actionable insights and practical tips to elevate your nonprofit's online presence.
A Free 200-Page eBook ~ Brain and Mind Exercise.pptxOH TEIK BIN
Â
(A Free eBook comprising 3 Sets of Presentation of a selection of Puzzles, Brain Teasers and Thinking Problems to exercise both the mind and the Right and Left Brain. To help keep the mind and brain fit and healthy. Good for both the young and old alike.
Answers are given for all the puzzles and problems.)
With Metta,
Bro. Oh Teik Bin đđ¤đ¤đĨ°
How to Download & Install Module From the Odoo App Store in Odoo 17Celine George
Â
Custom modules offer the flexibility to extend Odoo's capabilities, address unique requirements, and optimize workflows to align seamlessly with your organization's processes. By leveraging custom modules, businesses can unlock greater efficiency, productivity, and innovation, empowering them to stay competitive in today's dynamic market landscape. In this tutorial, we'll guide you step by step on how to easily download and install modules from the Odoo App Store.
1. UNIT-I
PART-A (2 MARKS)
1. Define quality.
Quality is the degree of goodness of a product or service or perceived by the
customer.
Quality concept is the way business organizations perform their business activities
that focuses on two things.
2. Define software quality?
Source
Definition
OED, 1990
Degree of excellence
Crosby, 1979 Zero defects
ISO, 1986
The totality of features and characteristics of a product or service that
bear on its ability to satisfy specified or implied needs.
Fruhauf
Quality is when the customer comes back, not the product.
3. Write down the different views of quality?
īˇī The transcendent view
īˇī The product based view
īˇī The value based view
īˇī The manufacturing view
īˇī The user based view
4. Write short notes on transcendent view?
īˇ Quality is excellence
īˇ It is impossible to quantity and difficult to apply in a meaningful sense to a
large software project
5. Write short notes on users-based view?
īˇ The aim is to check whether the software solution addresses the right problems
īˇ User ideas have to be converted to technical requirements
īˇ The quality match between user requirements and the design will determine
the quality of this view.
6. What are the metrics associated with reliability?
īˇ Accuracy
īˇ Consistency
īˇ Error tolerance
īˇ Simplicity
7. Mention few characteristics of functionality.
īˇ Suitability
īˇ Accurateness
8. Describe the three areas addressed by Mccals model?
2. īˇī Product operation
īˇī Product revision
īˇī Product transition
9. Define Mccallâs quality criteria.
īˇī Usability
īˇī Integrity
īˇī Efficiency
īˇī Correctness
īˇī Reliability
īˇī Maintainability
īˇī Flexibility
īˇī Testability
īˇī Portability
īˇī Reusability
īˇī Interoperability
10. How the quality criteria interrelated?
īˇī Inverse
īˇī Neutral
īˇī Direct
11. Give the conditions that quality metrics should met?
īˇī Be clearly linked to the quality criterion.
īˇī Be sensitive to the different degrees of the criterion.
īˇī Provide objective determination of criterion.
12. Define Structuredness?
Structuredness īĄī Modularity īĄī Lines of code
Number of modules
13. What are the two types of metrics?
īˇ Predictive Metrics
īˇ Descriptive Metrics
14. Give the characteristics of quality of software?
īˇ Quality is not absolute
īˇ Quality is multidimensional.
īˇ Quality is subject to constraints
īˇ ī Quality is about acceptable compromises.
īˇ ī Quality criteria are not independent.
15. Why software is considered to be problematical?
īˇ ī Software has no physical existence
īˇ ī The lack of knowledge of client needs
īˇ ī The change of client needs.
īˇ ī The rapid change in hardware and software.
īˇ ī ī High expectation of customers
16. What are the seven criteria suggested by watts for a good metric?
3. īˇī Objectivity
īˇī Reliability
īˇī Validity
īˇī Standardization
īˇī Comparability
īˇī Economy
īˇī Usefulness
17. How the metrics are classified?
īˇī Readability as a measure of usability
īˇī Error prediction as a measure of correctness
īˇī Error detection as a measure of correctness
īˇī MTTF as a measure of reliability
īˇī Complexity as a measure of reliability.
īˇī Complexity as a measure of maintainability
īˇī Readability of a code as a measure of maintainability
īˇī Modularity as a measure of maintainability.
īˇī Testability as a measure of maintainability
18. Write down the limitations of metrics?
īˇī They cannot be validated.
īˇī They are not generally objective.
īˇī Quality is relative ,not an absolute quantity.
īˇī They depend upon a small set of measurable properties.
īˇī The do not measure the complete set of quality criteria.
īˇī The metrics measure more than one criterion.
19. What are the problem areas associated with implementation of the method?
īˇī The method is different.
īˇī The need for training and retraining.
īˇī The need for effective management.
īˇī The need to measure progress.
īˇī Picking up errors earlier may cause frustration.
20. Write down the gilbâs quality attributes?
īˇī Workability
īˇī Availability
īˇī Adaptability
īˇī Usability
21. Define workability?
Workability is defined as the raw ability of the system to do work. workability
may considered in terms of
īˇī Process capacity-Itâs the ability to process transactions within a given unit of
time.
īˇī Storage capacity-Itâs the ability of the syatem to store things such as
information.
īˇī Responsiveness-Itâs the measure of the response to single event.
4. 22. Define Availability?
Availability is concerned with the proportion of elapsed time that a system is
able to be used. The sub attributes are
īˇī Reliability
īˇī Maintainability.
īˇī Integrity
23. Define Adaptability?
Adaptability may considered in terms of improvability,extendability,and
portability.
īˇī Improvability-the time taken to make minor changes to the system where the term
system is taken to include items such as documentation.
īˇī Extendability-Itâs the ease of adding new functionality to system.
īˇī Portability-Itâs the ease of moving a system from one environment to another.
24. Gilbâs approach become obselent.State reason.
īˇī ī Use of a template rather than rigid model.
īˇī ī Explicit recognition of constraints upon quality.
īˇī ī Recognition of critical resources
īˇī ī Use of locally defined measures.
īˇī ī Close links with the development process.
25. Write down the five methods suggested by waats for measuring quality?
īˇī ī Simple Scoring.
īˇī ī Weighted Scoring.
īˇī ī Phased Weighting factor method.
īˇī ī The Kepner-Tregoe method.
īˇī ī The Cologne combination method.
26. Define metric and indicator?
Quality metric: A metric is a verifiable measure that captures performance in
terms of how something is being done relative to a standard, allows and encourages
comparison, supports business strategy.
īˇ Quality indicator: An agreed-upon process or outcome measure that is used to
determine the level of quality achieved.
īˇ A measurable variable (or characteristic) that can be used to determine the
degree of adherence to a standard or achievement of quality goals.
27. List the classifications of a software metrics.
The classifications of a software metrics are
īˇ Product metrics
īˇ Process metrics
īˇ Project metrics
28. What is product metrics?
Product metrics describes the characteristics of a product such as size,
Complexity, design features, performance and quality levels (e.g defect rate etc.)
29. What is project metrics?
5. Project metrics describes the project characteristics and execution. Some of the
metrics are no. of developers in the project, cost, schedule, staffing pattern over the
SDLC.
30. What is cocomo model?
The COnstructive COst MOdel (COCOMO) is an algorithmic Software Cost
Estimation Model developed by Barry Boehm. The model uses a basic regression
formula, with parameters that are derived from historical project data and current
project characteristics.
31. What are the goals of software Quality management?
To build quality into the software from the beginning
To make sure there is quality throughout the life cycle.
32. What is a GOM model?
A goal- driven method for developing and maintaining a meaningful metrics
program that is based on three levels. Goals, Questions and Metrics. The Goal-
Question-Metric(GOM)Approach is a paradigm for developing and maintaining a
meaningful metrics program.
33. Define Quality as defined by ISO?
The totality of characteristics of an entity that bear on its ability to satisfy stated
and implied needs.
34. List any two Quality criteria.
Must explicitly attend to both functional and non-functional requirements.
Need to verify whether all customerâs requirements are met and from any stage of
the SDLC, must be traceable back to requirements.
35. What is a hierarchical model?
A Hierarchical model of software quality is based upon a set of quality criteria,
each of which has a set of measures or metrics associated with it.
36. How are quality measured?
Quality measurements are usually expressed in terms of metrics.
37. What is software metric?
Software metric is used to predict the about the software later in the life cycle.
38. What are the resources attributes given by glib?
īˇ Time
īˇ Money
īˇ People
īˇ Tools
PART-B
1. What are the views of quality? Explain in Detail the views of quality. (12)
6. 2. Explain the hierarchical model of Quality. (12)
3. a) Plain in detail the GE Model. (06)
b) Plain the Boehm model. (06)
4. Explain how the software quality can be measured and the problems associated
5. Explain the work of Gilb. (12)
6. Explain in detail GQM model. (12)
UNIT-II
PART-A (2 MARKS)
1. Define Methodology?
A methodology may be defined as a frame work for the systematic organization of a
collection of methods.
2. Write down the features of methodology?
īˇī It can be taught.
īˇī It can be scheduled.
īˇī It can be measured.
īˇī In can be compared.
īˇī It can be modified.
3. Define SSADM.Write down the principle behind SSADM.
SSADM-Structured System And Design Methodology.The aim of SSADM is to
ensure that user requirements are reflected in the design of the sysytem.The three
principle behind SSADM is
īˇī User Involvement.
īˇī Quality Assurance.
īˇī Seperation of logical and Physical design.
4. What are the stages involved in SSADM?
īˇī Analysis of current system.
īˇī Requirement specification.
īˇī Selection of technical options.
īˇī Data design.
īˇī Process design.
īˇī Physical design.
5. What are techniques used in SSADM?
SSADM make use of a number of techniques, both diagrammatic and non
diagrammatic.
Diagrammatic Techniques Non-Diagrammatic Techniques
1) Data Flow Diagram
2) Logical data structures
3) Entity life histories
7. 4) Logical dialogue outlines
1) Relational Data Analysis
2) First-cut rules.
3) Physical design control.
4) Project Estimation.
5) QA Reviews
6. Write down the seven phases involved in IEM?
īˇī Information Strategy Planning.
īˇī Business Area Analysis.
īˇī Business System Design.
īˇī Technical Design.
īˇī Construction.
īˇī Transition and Production.
7. Write down the advantages of IEM?
īˇī It links system development to business needs.
īˇī It covers the whole life cycle.
īˇī It facilitates the use of a case tool.
8. Define CASE tool?
CASE-Computer Aided Software Engineering. CASE tools are computer based tools
to assist in the software engineering process. CASE tool is made up of set of tools.
9. What are different types of CASE tools?
īˇī Front end or upper case tools.
īˇī Back end or lower case tool
īˇī Integrated case tools.
10. Define QMS?
The organisational structure,responsibilities,procedures,processes and resources for
implementing quality management.
11. Write down the SPC techniques?
īˇī Process flow chart
īˇī Tally chart.
īˇī Histogram.
īˇī Pareto Analysis.
īˇī Cause-and Effect diagram.
īˇī Scatter diagram.
īˇī Control charts.
12. Define Quality Control.
A systematic method of economically providing products or services that met the
userâs requirements.
13. Define DRE?
DRE=Errors found by an inspection * 100%
Total Errors in the product before Inspection
8. 14. Name the two metrics for DRE?
īˇī Total defect containment Effectiveness (TDCE)
īˇī Phase containment Effectiveness (PCE)
TDCE= Number of pre release defects
Number of prerelease defects + number of post release defects
PCE=Number of phase i errors
Number of phase I errors + Number of phase I defects
15. Write down the characteristics of DRE?
īˇī There are only two phases of defect removal.
īˇī The defect removal effectiveness for the two phases is same.
16. Write down the five steps involved in Fagans Inspection method?
īˇī Overview
īˇī Preparation.
īˇī Inspection.
īˇī Rework.
īˇī Follow-up.
17. Why we have to assess the reliability of a software product?
It is important for two reason
īˇī As an objective statement of the quality of the product.
īˇī For resource planning for the software maintenance phase.
18. How the reliability models are classified?
Reliability models are classified into two types.
īˇī Dynamic models
īˇī Static models
A static models uses other attributes of the project or program modules to estimate
number of defects in the software.
A dynamic models usually based on statistical distributions, uses development defect
patterns to estimate end product reliability.
19. What are five factors affecting software quality assurance?
īˇ Size of the system
īˇ Criticality of the system.
īˇ The cost of correcting errors.
īˇ Type of release.
īˇ Relationship with user.
20. Write down the guidelines for effective leadership?
īˇ Trust your subordinates.
īˇ Develop your vision.
īˇ Keep u cool.
īˇ Encourage risk
īˇ Be an expert.
īˇ Invite dissent.
īˇ Simplify.
21. Write down the five effective methods to ensure the failure of software
9. quality assurance?
Too many technical niceties.
Too much time spent stopping, rather than preventing defects.
Efforts wasted.
Management has a problem with the mathematical kid.
Always complaining about the government ,but no one does anything.
22. What is SRS?
The software requirement specification document describes capabilities, states,
functionality of all aspects of the system. This include major components,
subcomponents of the software and internal interfaces of the software and
may include databases. It also include items specifically required by the user.
23. What is SDD?
The software Design Description describes major components and sub components
of the software, including databases and internal interfaces. This process will be
carried out according to the standard procedure. This procedure may include use of a
computerized design tool.
24. What is Software Interfaces documentation?
Software interfaces documentation describes capabilities and functionality of all
interfaces between any two or more components of the system.This include major
components ,sub components and external systems.
25. Write down the principles behind the review process?
īˇī Establishing what reviews are needed by the project.
īˇī What are contents of various review.
īˇī What should be results o f the review.
26. Write down the specification for reviews?
īˇī Formal reviews occur at menaing ful points of the software schedule.
īˇī Include affected groups within organization and customer or end user
representatives as appropriate.
īˇī Review materials that the responsible software managers have reviewed and
approved.
īˇī Check the commitments, plans and status of the software activities.
īˇī Document the identification of significant issues.
īˇī Address the software project risks.
īˇī Define any refinements in the software development plan
27. Write down the objectives of Management Review Process?
īˇī Making activities progress according to plan
īˇī Changing project direction.
īˇī Identify the need for alternative palnning.
īˇī Maintaining the global control of the project.
28. What are the inputs given to the management review process?
īˇī Statement of objectives
īˇī List of issues to be addressed.
10. īˇī Current project schedule.
īˇī Report from other reviews.
īˇī Reports of resources assigned to project
īˇī Data on the software elements completed.
29. What are the procedures involved in the management review?
īˇī Planning
īˇī Overview
īˇī Preparation
īˇī Examination.
īˇī Rework
īˇī Exit criteria.
īˇī Management review output.
īˇī Auditability
30. Write down the objective of Technical review ?
īˇī Evaluation of a specific software elements.
īˇī Identification of any discrepancies from specification and standards.
īˇī Recommendations after the examination of alternatives.
31. What are inputs given to the technical review process?
īˇī Statement of objectives.
īˇī Software elements being examined.
īˇī Specifications for the software elements.
īˇī Plans,standards or guidelines against which the software elements are to be
examined.
32. Write down the procedures involved in auditing?
īˇī Planning
īˇī Overview
īˇī Preparation
īˇī Examination
īˇī Reporting
33. Write down the preparation that has to be made by the audit team?
īˇī Understand the organization
īˇī Understand the products and processes.
īˇī Understand the objective audit criteria.
īˇī Prepare for the audit report.
īˇī Detail the audit plan.
34. Write down the contents included in the Auditing plan?
īˇī Project processes to be examined.
īˇī Software required to be examined.
īˇī Reports shall be identified.
īˇī Reports distribution.
īˇī Required follow up activities.
īˇī Requirements.
īˇī Objective audit criteria.
īˇī Audit procedures and checklists.
11. īˇī Audit personnel.
īˇī Organization involved in the audit.
īˇī Date,time, place,agenda of session.
35. What are the requirements required for the document audit and verification?
īˇī Acquisition of project documentation.
īˇī Analysis of documents.
īˇī Dissemination of information.
36. When the auditing is said to be complete?
When
īˇī Each element within the scope has been examined.
īˇī Findings have been presented to the auditing organization.
īˇī Response to the draft audit have been received.
īˇī Final findings have been formally presented.
īˇī The audit report has been prepared and submitted.
īˇī All follow-up actions by the auditing organization have been performed.
37. Write down the contents of audit reports?
īˇī Audit Identification
īˇī Scope
īˇī Conclusions.
īˇī Synopsis
īˇī Follow-up.
38. What is Auditing?
An audit provides an objective compliance confirmation of products and processes
to certify adherence to standards, guidelines, specifications and procedures. Audits are
performed in accordance with documented plans and procedures .The results of the
audit are documented and are submitted to the management of the audited
organization, to the entity initiating the audit and to any external organizations
identified in the audit plan.
39. What is the purpose of performing Review and auditing?
The purpose of performing review and audits are to ensure that the products
meets all client needs and requirements and to find development anomalies as early
and as inexpensively as possible.
40) What are advantages of CASE Tools?
īˇī ī Productivity.
īˇī Consistency.
īˇī Methodology Automation.
īˇī Encourages Good Practice.
īˇī Documentation.
īˇī Maintenance
PART-B
1. Explain in detail the Quality tasks and responsibilities. (12)
12. 2. Explain in detail about the Documentation. (12)
3. Explain the Procedural description template and Action items (12)
4. Explain in detail the CMM Compatibility of Reviews and audits. (12)
5. Explain the management review process. (12)
6. Explain the technical review process. (12)
7. Explain the types of reviews. (12)
8. Explain the software inspection process. (12)
9. a) Explain walkthrough process. (6)
b) Explain the Audit process. (6)
10. a) Explain the Document verification and validation. (6)
b) Explain the factors affecting the SQA effort. (6)
UNIT-III
PART-A (2 MARKS)
1. What are Ishikawaâs seven basic tools for quality control?
īˇī Check sheet
īˇī Pareto diagram
īˇī Histogram
īˇī Scatter diagram
īˇī Run chart
īˇī Control chart
īˇī Cause and effect diagram.
2. What is the purpose of using check sheet?
A check sheet is a paper form with printed items to be checked. Its main purpose is
to facilitate gathering data and to arrange data while collecting it so the data can be
easily used later.
3. What is the use of pareto diagram?
A pareto diagram is a frequency chart of bars in descending order. A pareto
diagram can identify the few causes that account for the majority of defects. It
indicates which problem can be solved first in eliminating defects and improving the
operation. Pareto analysis can be referred to as 80-20% principle.
4. What is the purpose of using Histogram?
The histogram is a graphic representation of frequency counts of a sample or a
population. The purpose of histogram is to show the distribution characteristics of a
parameter.
13. 5. What is the use of scatter diagram?
A scatter diagram vividly portrays the relationship of two interval variables.
6. Define process capability?
Cp= (USL-LSL)/6īŗī
ī
7. Define process capability index?
Cp = (USL-u)/3īŗī
ī
8. Write down the assumptions made in the phases of defect removal activities?
īˇī Those activities handled directly by the development team for large software
projects .
īˇī The formal machine tests after code integration.
9. How will u calculate the total defects for the life of the software?
TD=MP+PTR+Q
TD=Total defects for the life of software.
MP=Major problems found during review.
Q =Number of defects in the released software.
10. What are the two types of inspector phase defined by knight and Myers?
īˇī Single Inspector Phase.
īˇī Multi Inspector phase.
11. What is single inspector phase?
Itâs a rigidly formatted process driven by a list of unambiguous checks, for
eg, internal documentation, source code layout, source code readability.
12. What is multi inspector phase?
Itâs designed to check for those properties of the software that cannot be captured
in a precise yes or no statement is called the multi inspector phase.
13. What is the use of software reliability models?
Software reliability models are used to assess a software products reliability or to
estimate the number of latent defects when it is available to the customers.
14. What is the need of assessing the software reliability?
An estimate is important for two reasons
īˇī As an objective statement of the quality of the product
īˇī Resource planning for software maintenance phase.
15. Write down the classification of reliability models?
The reliability models can be broadly classified into two categories. They are
īˇī Static models
īˇī Dynamic models
16. What are the assumptions made in the rayleigh model curve to model the
software development activity?
14. īˇī Defect rate observed during development process is positively correlated with the
defect rate.
īˇī Same error injection rate
17. Define component?
A component is a group of modules that perform specific functions such as
spooling, printing, message handling, file handling, and so on.
18. What is DUD?
DUD is a derivative free algorithm for non linear least squares.It competes favorably
with even the best derivative based algorithm when evaluated on number of standard
test problems. One of the advantage behind this DUD method is its simplicity and its
efficiency.
19. Define Predictive validity?
Predictive validity refers to the accuracy of model estimates. To achieve the
predictive validity is to make sure that the input data are accurate and reliable.
20. What is fish-bone diagram?
The cause and effect diagram is sometimes called an Ishikawa diagram after its
inventor. It is also known as a fish bone diagram because of its shape. A cause and
effect diagram describes a relationship between variables.
21. What is the use of a Z-chart?
The Z-chart is a combination chart that shows three perspectives in a single
picture . A run chart is called as Z-chart.
22. What is the use of CASE tools?
Computer-aided software engineering(CASE) is the use of software tools to assist
in the development and maintenance of software. Tools used to assist in this way are
known as CASE Tools.
23. Write a short note on UML?
Unified Modeling Language (UML) is a standardized specification language for
object modeling. UML is a general-purpose modeling language that includes a
graphical notation used to create an abstract model of a system, referred to as a UML
model.
24. What is QVT?
In the model-driven architecture, QVT (Queries/Views/Transformations) is a
standard for model transformation defined by the Object Management Group
25. What are the advantages of CASE tools?
īˇ Productivity
īˇ Consistency ,
īˇ Methodology automation,
īˇ Encourage and good practice,
īˇ Documentation.
15. 26. Give the types of CASE tools.
īˇ Front end or upper case tools
īˇ Back end or Lower case tools
īˇ Integrated case tools
27. Why is Rayleigh model used?
The Rayleigh model is a parametric model in the sense that it is based on a
specific statistical distribution. Rayleigh model encompasses both defect prevention
and early defect removal. Another strength of Rayleigh model is that it provides an
excellent framework for quality management.
28. Define Errors, Bugs, and Defects
Error: It is the Deviation from actual and the expected value.
Bug: It is found in the development environment before the product is shipped to the
respective customer.
Defect: It is found in the product itself after it is shipped to the respective customer.
29. Name any two tools for quality.
There are many tools used for quality.
They are:
1. Check list or check sheet.
2. Pareto Diagram.
30)What is the use of cause and effect diagram?
The cause and effect diagram is also known as fish bone diagram. It shows the
relationship between the quality characteristics and factors that affect the
characteristics. It identifies all casual factors of a quality characteristic in one chart.
PART-B
1. Explain in Detail about the Ishikawaâs basic tools in software development (12)
2. a) Explain in detail about the CASE tools. (6)
b) Explain the Defect Prevention Process. (6)
3. Explain the Defect removal Effectiveness. (12)
4. Explain the Reliability models. (12)
5. Explain in detail about the Rayleigh model. (12)
6. Explain Reliability growth model for quality assessment (12)
UNIT-IV
PART-A (2 MARKS)
1. What are the strengths of Rayleigh model?
Compared to phase defect removal model, the rayleigh model is a formal parametric
16. work that can be used for projecting latent software defects when the development
work is complete .another strength of Rayleigh model is it provides an excellent
framework for quality management.
2. How the Reliability growth models are classified?
Reliability growth models are classified into two major classes depending on the
dependent variable of the model. They are
īˇī Time between failure models.
īˇī Fault count models.
3. Write down the equation for Goel generalized non homogenous poisson
process model?
M(t) = a(1-e-btc)
4. What are different types of Reliability growth models?
īˇī J-M Model.
īˇī Littlewood Model
īˇī Goel-Okumoto Imperfect Debugging Model.
īˇī Goel-Okumoto Non Homogenous Poisson Process Model.
īˇī The Delayed and Inflection S Model.
5. What are assumptions made in J-M model?
īˇī There are N unknown software faults at the start of testing.
īˇī Failures occur randomly-times between failures are independent.
īˇī All faults contribute equally to cause a failure.
īˇī Fix time is negligible.
īˇī Fix is perfect for each failure.
6. What are the assumptions made in fault count model?
īˇī Testing intervals are independent of each other.
īˇī Testing during intervals is reasonably homogenous.
īˇī Number of defects detected during non overlapping intervals are independent of
each other.
7. Write down the criteriaâs involved in reliability models?
īˇī Predictive validity
īˇī Capability
īˇī Quality of assumptions.
8. Write down the procedures involved in modeling software reliability?
īˇī Examine the data.
īˇī Select a model or several models to fit the data.
īˇī Estimate the parameters of the model.
īˇī Obtain the fitted model by substituting the estimates of parameters into the
chosen model
īˇī Perform a goodness âof-fit test and assess the reasonableness of the model.
īˇī Make reliability predictions based on the fitted model.
9. Define test compression factor?
17. The difference between testing defect density and field defect density is called
compression factor.
10. Write down the principles behind the quality management?
īˇī The best scenario is to prevent errors being injected into the development process.
īˇī When errors are introduced, improve the front end of the development process to
remove as many of them as early as possible.
īˇī If the project is beyond the design and code phases, unit tests and any additional
tests by the developers serve as gate keepers for defects to escape the front end
process before the code is integrated into the configuration management system.
11. What are the four types of scenarios?
īˇī Best case scenario
īˇī Good scenario.
īˇī Unsure scenario
īˇī Worst case scenario.
12. What are the five activities involved in QIP?
īˇī Blitz testing
īˇī Customer evaluation
īˇī Code inspections.
īˇī Design reviews
īˇī Extension of system tests.
13. Write down the advantages of using reliability growth model?
īˇī Comparisons can be made when the first data points become available. If
unfavaorable signs are detected timely action s can be taken.
īˇī To determine end date of testing.
14. Write down the general formula to calculate the cyclomatic complexity?
M=V(G)=e-n+2p
Where V(G)=cyclomatic number of G
E=number of edges.
N=number of nodes.
P=number of unconnected parts of the grap
15. Define Fan-in and Fan-out?
īˇī Fan-in : A count of the modules that call a given module.
īˇī Fan-out: A count of modules that are called by a given module.
16. Define Structure complexity?
Henry and Kafuraâs structure complexity is defined as
Cp=(fan-in *fan-out)2
17. Define Complexity metrics and models?
Complexity metrics and models are by small team metrics.They measure the
internal dynamics of design and code of the software,and the unit of analysis is
usually at
the program module level.
18. 18. Write down the methods to gather data?
īˇī Face to face interviews
īˇī Telephone interviews
īˇī Mailed questionaries
19. Define sampling methods?
When the customer base is large ,its to costly to survey all customers.Estimating the
satisfaction level of the entire customer population through a representative sample is
more efficient.To obtain representative samples ,scientific probability sampling must
be used.
20. Write down the different types of sampling methods?
īˇī Random sampling.
īˇī Systematic sampling.
īˇī Stratified sampling.
īˇī Cluster sampling.
21. Write down the product quality attributes?
īˇī Technical solution.
īˇī Support and service.
īˇī Marketing
īˇī Administration.
īˇī Delivery
īˇī Company image.
22. What is Quality Management?
Quality Management includes all the activities that managers carry out in
an effort to implement their quality policy. These activities include quality planning,
quality control, quality assurance and quality improvement.
23. Give the ISO definition on Quality management.
ISO defines âQuality Management â as â what the organization does to
ensure that its products or services satisfy the customerâs quality requirements and
comply with any regulations applicable to those products or services.â
24. What are the elements of Quality Management.
1. Organizational Structure.
2. Responsibilities.
3. Procedures.
4. Processes.
5. Resources.
25. Give the procedures in Quality Management.
Contract view, Design control, Document control, purchasing, customer
supplies, Traceability, Process control, Checking. Inspecting . Measuring and testing,
Non conforming Product or services, Corrective action, Training, Protection of
quality, Statistical process control, Quality system audit.
26. What is Iceberg analogy?
19. Iceberg analogy describes the relationship between testing and field defect rates, the
tip of the iceberg is the testing defect rate and the submerged part is the field defect
rate. The size of the iceberg is equivalent to the amount of error injection.
27. What is Blitz testing?
Blitz is a generic tool whose purpose is to maintain and execute test cases of
arbitrary complexity. Blitz can be used either as a command-line tool or as a full-
featured graphical user interface. Artistic testing in stressful environments.
28. List the common metrics for software.
īˇ Order of growth
īˇ Source lines of code
īˇ Cyclomatic complexity
īˇ Function per analysis
īˇ Bugs per line of code
īˇ Code coverage
īˇ Number of lines of customer requirements
īˇ Number of classes and interfaces
īˇ Cohesion
īˇ Robert Cecil Martinâs software package metrics
īˇ Coupling
29. What are the coverage criteria?
Function coverage: Has each function in the program been executed?
Statement coverage: Has each line of the source code been executed?
Condition coverage: Has each evaluation point (such as a true/false decision) been
executed?
Path coverage: Has every possible route through a given part of the code been
executed?
Entry/exit coverage: Has every possible call and return of the function been
executed?
30. What is cohesion?
Cohesion is a measure of how strongly-related and focused the various
responsibilities of a software module are. Cohesion is an ordinal type of measurement
and is usually expressed as âhigh cohesionâ or âlow cohesionâ when being discussed.
Modules with high cohesion tend to be preferable because high cohesion is
associated with several desirable traits of software including robustness, reliability,
reusability, and understandability whereas low cohesion is associated with
undesirable traits such as being difficult to maintain, difficult to test, difficult to reuse,
and even difficult to understand.
31. What are the drawbacks of Halstead science metric?
īˇ It depends on completed code.
īˇ It has little or no use as a predictive estimating model. But McCabeâs model is
more suited to application at the design level.
32. What is Cyclomatic complexity?
20. Cyclomatic complexity is computed using a graph that describes the control flow
of the program. The nodes of the graph correspond to the commands of a program. A
directed edge connects two nodes if the second command might be executed
immediately after the first command.
33. What are the five components of QMS as listed by ISO?
The main five components of QMS are.
īˇ Organizational structure
Responsibilities
īˇ Procedures
Processes
īˇ Resources
34. What is QMS?
QMS according to ISO is the organizational structure, responsibilities, procedures,
processes and resources for implementing Quality management.
35. Define Lines of code.
Source lines of code (SLOC) are software metric used to measure the size of a
software program by counting the number of lines in the text of the programâs source
code.
36. Define Halsteadâs software science.
The software science developed by M.H, Halstead principally attempts to estimate
the programming effort.
37. Define Cyclomatic Complexity.
Cyclomatic complexity is software metric (measurement). It was developed by
Thomas McCabe and is used to measure the complexity of a program and indicate the
programâs testability and understandability.
38. What are the three ways to gather survey data for customer satisfaction
analysis?
īˇ Face-to-face interviews
īˇ Telephone interviews
īˇ Mailed Questionnaires
PART- B
1. Explain in detail the elements of QMS. (12)
2. Explain the Rayleigh model framework. (12)
3. Explain the Reliability Growth models. (12)
4. Explain the complexity metrics and its models (12)
5. Explain Lines of Code and Halsteadâs Software Science. (12)
6. Explain in detail the Cyclomatic Complexity (12)
21. 7. a)Explain Syntactic constructs (6)
b) Briefly explain structure metrics. (6)
8. Explain in detail the Customer satisfaction surveys / analysis. (12)
UNIT-V
PART-A (2 MARKS)
1. What are the management responsibilities regarding ISO 9001 requirements?
Management commitment, Customer focus, Quality policy, Planning, Responsibility,
Authority, Communication, and Management review.
2. Define SPICE.
SPICE (Software Process Improvement and Capability dEvelopement) standard
defines a set of requirements for software process assessment. The intent of the
standard is to assist organizations in developing an objective evaluation of the
efficacy of any defined software process.
3. What is MALCOLM BALDRGE award?
MALCOLM BALDRIGE award is the most prestigious quality award in the United
States. The award is given annually to recognize U.S companies that exceed in quality
management and quality achievement.
4. What are the ISO 9000 series of quality management standards?
ISO 9000, ISO9001, ISO9002, ISO9003, ISO9003, ISO9004
5. Define CMM.
The capability maturity model (CMM) for s/w is a widely accepted set of guidelines
for developing high performance s/w organizations.
6. What are the capability levels defined in SPICE?
Level0: Not performed, 1: Performed informally, 2: Planned and tracked, 3: Well
defined, 4: Quantitatively controlled, 5: Continuously improving.
7. What are the types of accreditation?
First party, Second party, Third party.
8. What are the components of the ISO 9000 series to which SPICE is related?
ISO 9001, ISO 9000-3, ISO 9004-4., ISO DIS.
9. What is and assessment instrument?
An assessment instrument is a tool, or set of tools, used during the performance of an
assessment to assist the assessor in obtaining reliable, consistent and repeatable
results.
10. What are the goals of SPICE project?
1. developing a working draft for a standard for software process assessment
2. conducting industry trials of the emerging standards.
3. promoting the technology transfer of software process assessment into the software
22. industry world wide.
11. What are the benefits that an international standard will provide to
industry?
1. Software suppliers will submit to just one process assessment scheme.
2. Software development organizations will have a tool to initiate and sustain a
continuous process improvement
3. Programme managers will have a means to ensure that their software development
is aligned with, and supports, the business needs of the organization.
12. What are the benefits of ISO 9000 verification?
1. Provides know-how for establishing a quality management system.
2. Certification has become the minimum requirement of quality for any tender.
3. It is a status symbol for the organizations.
4. Improves products and services.
5. Improves employee morale.
13. What are the events associated with quality management?
Establishing, Documenting, Implementing, Maintaining, Continuously improving its
effectiveness.
14. What are the documents required to implement quality management system
in an organization?
1. Quality policy and quality objectives
2. Quality manual
3. Document to ensure the effective planning, operation and control of its processes
4. Records.
15. What are the pre-requisites for employees?
Education, training, skill, experience
16. What are the requirements of internal auditing?
1. Set up an internal audit program
2. Develop an internal audit procedure
3. Plan internal audit procedure.
4. Perform regular internal audits
5. Take corrective action.
17. What are the different organizations to which the Malcolm Balridge award is
given?
1. Manufacturing
2. Service
3. Small businesses
18. What are the different process maturity levels?
1. Initial
2. Repeatable
3. Defined
4. Managed
5. Optimizing
23. 19. Who are the steps organizations has to take to improve their software
capabilities?
1. Understand the current status
2. Develop a vision of the desired process
3. Establish a list of process improvement actions.
4. Produce a plan to accomplish the required actions.
5. Commit the resources to execute the plans.
20. What are the requirements of ISO 9001: 2000 standard?
1. Demonstrate ability to consistently provide product that meets customer and
applicable regulatory requirements.
2. Enhance customer satisfaction.
21. What is the need for quality standards?
It is important for a software product to asses its quality. Project the defects and
the mean time to next failure. It is also important for a software product to manage the
quality when it its in the development state. This purpose is done by the quality
standards available for softwareâs such as ISO. Six sigma etc.
22. What are the levels of accreditation?
There are three levels of accreditation encountered,
īˇ First party-Internal monitoring
īˇ Second party-External monitoring
īˇ Third party-External Monitoring
23. Give the requirements of ISO 9000.
The document control of ISO 9000 has some requirements.
īˇ Must be adequate for purpose
īˇ Owner must be identified
īˇ Properly approved before issue
īˇ Version qualified
īˇ Pages numbered and total pages indicated
īˇ Properly destroyed when obsolete
24. What are the advantages of the ISO standard?
ISO often gives the following advantages
īˇ Create a more efficient, effective operation
īˇ Increase customer satisfaction and retention
īˇ Reduce audits
īˇ Enhance marketing
īˇ Improve employee motivation, awareness, and morale
īˇ Promote international trade
īˇ Increases profit
īˇ Reduce waste and increases productivity.
25. What is CMM?
The Capability Maturity Model (CMM), also known as the software CMM (SW-
CMM. The CMM is a process model based on software best practices effective in
large-scale, multi-person projects. CMM was developed by the Software Engineering
24. Institute (SEI) at Carnegie Mellon University in Pittsburgh.
The Capability Maturity Model (CMM) is a way to develop and refine an
organizationâs processes. The first CMM was for the purpose of developing and
refining software development professes. This model is questionnaire based. The
questions are divided into
īˇ Essential
īˇ Highly desireable
36. What is six sigma?
Six sigma is a rigorous and disciplined methodology that uses data and statistical
analysis to measure and improve a companyâs operational performance by identifying
and eliminating âdefectsâ in manufacturing and service-related processes.
37. What are the level improvements of CMMI?
CMMI Level 1to2: Pre-packaged methodology methodology documentation and
active mentoring
CMMI Level 2to3: Process documentation, configuration& accelerated project
management
CMMI Level 3to4:Managed process through Metrics Capture in an XML process
repository
CMMI Level 4to5:Process feedback loop.
38. What is ISO 9000 and ISO 9001?
ISO 9000 is a family of standards for quality management systems. ISO 9000 is
maintained by ISO, the International Organization for Standardization and is
administered by accreditation and certification bodies.
ISO 9001 is the internationally recognized standard for the quality management of
businesses. It applies to the processes that create and control the products and services
an organization supplies.
39. What are capability level?
A capability level is a well-defined evolutionary plateau describing the
organizationâs capability relative to a process area. A capability level consists of
related specific and generic practices for a process area that can improve the
organizationâs processes associated with that process area. Each level is a layer in the
foundation for continuous process improvement. Thus, capability levels are
cumulative, i.e.. a higher capability level includes the attributed of the lower levels.
40. Define quality standards.
Quality standards were developed to assist companies control quality and
maintain a high standard of customer satisfaction. Quality standards can assist a
company with good management practices, reduce risk and increase profit margins.
41. What are the types of metrics used in six sigma?
The two major types of six sigma metrics are
īˇ Classical measures of six sigma metrics
īˇ Typical six sigma measures.
25. 1. Discuss in detail about the needs for standards (12)
2. Explain the ISO9000 series standard (12)
3. Explain the ISO9000-3 standard for software development. (12)
4. Explain in detail the CMM Model (12)
5. Explain the CMMI Model (12)
6. Explain the Six Sigma Concepts. (12)