McCall Software Quality Model in Software Quality Assurance
•Download as PPTX, PDF•
8 likes•10,099 views
McCall Software Quality Model in Software Quality Assurance subscribe my youtube channel do like and share video https://youtu.be/sab1Fwybrkc
Report
Share
Report
Share
Recommended
Software quality
The document discusses software quality and defines key aspects:
- It explains the importance of software quality for users and developers.
- Qualities like correctness, reliability, efficiency are defined.
- Methods for measuring qualities like ISO 9126 standard are presented.
- Quality is important throughout the software development process.
- Both product quality and process quality need to be managed.
Hierarchical models of software quality
This document discusses hierarchical models of software quality, including the McCall and Boehm models. The McCall model addresses three areas of software quality: product operation, product revision, and product transition. Product operation focuses on usability, integrity, efficiency, and correctness. Product revision examines testability and maintainability. Product transition considers portability, reusability, and interoperability. The Boehm model defines three levels of quality attributes: primary uses, intermediate constructs, and primitive constructs. Primary uses include as-is utility and maintainability. Intermediate constructs are flexibility, reliability, portability, efficiency, testability, understandability, and usability. Primitive constructs result in measurable properties.
Constructive Cost Model - II (COCOMO-II)
This presentation was made by me in my pre-final year and would be beneficial to anyone learning and studying Software Engineering in their college
Software Quality Attributes
The quality of software systems may be expressed as a collection of Software Quality Attributes. When the system requirements are defined, it is essential also to define what is expected regarding these quality attributes, since these expectations will guide the planning of the system architecture and design.
Software quality attributes may be classified into two main categories: static and dynamic. Static quality attributes are the ones that reflect the system’s structure and organization. Examples of static attributes are coupling, cohesion, complexity, maintainability and extensibility. Dynamic attributes are the ones that reflect the behavior of the system during its execution. Examples of dynamic attributes are memory usage, latency, throughput, scalability, robustness and fault-tolerance.
Following the definitions of expectations regarding the quality attributes, it is essential to devise ways to measure them and verify that the implemented system satisfies the requirements. Some static attributes may be measured through static code analysis tools, while others require effective design and code reviews. The measuring and verification of dynamic attributes requires the usage of special non-functional testing tools such as profilers and simulators.
In this talk I will discuss the main Software Quality attributes, both static and dynamic, examples of requirements, and practical guidelines on how to measure and verify these attributes.
Software engineering Questions and Answers
1. Risk management is the process of identifying, addressing, and eliminating potential problems that could threaten the success of a project before they cause damage. This includes issues that could impact cost, schedule, technical success, product quality, or team morale.
2. HIPO (Hierarchical Input Process Output) diagrams were developed at IBM as a design representation and documentation aid. They contain a visual table of contents, overview diagrams, and detailed diagrams.
3. Software maintenance is any work done to modify software after it is operational, such as fixing errors, adding capabilities, removing obsolete code, or optimizing performance. It aims to preserve the software's value over time as requirements, users, and technology change. M
Mc call's software quality model
The earliest software model encompassing quality of a software with both users and developers approach is presented.
McCall's Quality Factors
This document discusses software quality factors and McCall's model of quality factors. It describes McCall's model which categorizes quality factors into three categories: product operation factors related to how well the software runs, product revision factors related to how easily the software can be changed and tested, and product transition factors related to moving the software to different environments. Under each category it provides examples of specific quality factors like correctness, reliability, maintainability, and portability. It also mentions some alternative models that suggest additional quality factors.
Software Quality Metrics
What is Quality ||
Software Quality Metrics ||
Types of Software Quality Metrics ||
Three groups of Software Quality Metrics ||
Customer Satisfaction Metrics ||
Tools used for Quality Metrics/Measurements ||
PERT and CPM ||
Recommended
Software quality
The document discusses software quality and defines key aspects:
- It explains the importance of software quality for users and developers.
- Qualities like correctness, reliability, efficiency are defined.
- Methods for measuring qualities like ISO 9126 standard are presented.
- Quality is important throughout the software development process.
- Both product quality and process quality need to be managed.
Hierarchical models of software quality
This document discusses hierarchical models of software quality, including the McCall and Boehm models. The McCall model addresses three areas of software quality: product operation, product revision, and product transition. Product operation focuses on usability, integrity, efficiency, and correctness. Product revision examines testability and maintainability. Product transition considers portability, reusability, and interoperability. The Boehm model defines three levels of quality attributes: primary uses, intermediate constructs, and primitive constructs. Primary uses include as-is utility and maintainability. Intermediate constructs are flexibility, reliability, portability, efficiency, testability, understandability, and usability. Primitive constructs result in measurable properties.
Constructive Cost Model - II (COCOMO-II)
This presentation was made by me in my pre-final year and would be beneficial to anyone learning and studying Software Engineering in their college
Software Quality Attributes
The quality of software systems may be expressed as a collection of Software Quality Attributes. When the system requirements are defined, it is essential also to define what is expected regarding these quality attributes, since these expectations will guide the planning of the system architecture and design.
Software quality attributes may be classified into two main categories: static and dynamic. Static quality attributes are the ones that reflect the system’s structure and organization. Examples of static attributes are coupling, cohesion, complexity, maintainability and extensibility. Dynamic attributes are the ones that reflect the behavior of the system during its execution. Examples of dynamic attributes are memory usage, latency, throughput, scalability, robustness and fault-tolerance.
Following the definitions of expectations regarding the quality attributes, it is essential to devise ways to measure them and verify that the implemented system satisfies the requirements. Some static attributes may be measured through static code analysis tools, while others require effective design and code reviews. The measuring and verification of dynamic attributes requires the usage of special non-functional testing tools such as profilers and simulators.
In this talk I will discuss the main Software Quality attributes, both static and dynamic, examples of requirements, and practical guidelines on how to measure and verify these attributes.
Software engineering Questions and Answers
1. Risk management is the process of identifying, addressing, and eliminating potential problems that could threaten the success of a project before they cause damage. This includes issues that could impact cost, schedule, technical success, product quality, or team morale.
2. HIPO (Hierarchical Input Process Output) diagrams were developed at IBM as a design representation and documentation aid. They contain a visual table of contents, overview diagrams, and detailed diagrams.
3. Software maintenance is any work done to modify software after it is operational, such as fixing errors, adding capabilities, removing obsolete code, or optimizing performance. It aims to preserve the software's value over time as requirements, users, and technology change. M
Mc call's software quality model
The earliest software model encompassing quality of a software with both users and developers approach is presented.
McCall's Quality Factors
This document discusses software quality factors and McCall's model of quality factors. It describes McCall's model which categorizes quality factors into three categories: product operation factors related to how well the software runs, product revision factors related to how easily the software can be changed and tested, and product transition factors related to moving the software to different environments. Under each category it provides examples of specific quality factors like correctness, reliability, maintainability, and portability. It also mentions some alternative models that suggest additional quality factors.
Software Quality Metrics
What is Quality ||
Software Quality Metrics ||
Types of Software Quality Metrics ||
Three groups of Software Quality Metrics ||
Customer Satisfaction Metrics ||
Tools used for Quality Metrics/Measurements ||
PERT and CPM ||
Human computer interaction -Input output channel with Scenario
This document discusses input and output channels in human-computer interaction. It describes the five human senses - sight, hearing, touch, taste and smell - and how they provide input. It then discusses the major effectors like limbs, fingers and vocal systems that provide human output. The document focuses on how vision, hearing and touch are used as input channels in interacting with computers, primarily through the eyes, fingers and voice. It provides details on the physiological mechanisms and processing involved in each sense.
Cocomo model
The COCOMO model is a widely used software cost estimation model that predicts development effort and schedule based on project attributes. It includes basic, intermediate, and detailed models of increasing complexity. The intermediate model estimates effort as a function of source lines of code and cost drivers. The detailed model further incorporates the impact of cost drivers on development phases. COCOMO 2 expands on this with application composition, early design, reuse, and post-architecture models for different project stages.
Publish subscribe model overview
The document provides an overview of the publish-subscribe model from the perspective of a database. It discusses key aspects of the publish-subscribe model including decoupling of publishers and subscribers, subscription models, and quality measures. It also examines applying publish-subscribe concepts in databases through expressions, continuous queries, and using XML with XFilters and SQL queries.
WEB INTERFACE DESIGN
The document discusses principles and patterns for designing web interfaces, including making interactions direct, lightweight, and keeping users on the page. It covers various techniques for inline and overlay editing, direct selection of objects, drag and drop interactions, and using contextual tools near content to improve usability. The document provides examples and guidelines for implementing these patterns and principles in web design.
Software project management Software economics
This document discusses software project management and cost estimation. It outlines five basic factors that influence software project costs: size, process, personnel, environment, and required quality. An equation is provided that estimates effort based on these five factors. The document also discusses the importance of cost estimation for feasibility analysis and return on investment calculations. It describes different techniques for software cost estimation including algorithmic modeling, expert judgment, top-down, bottom-up, and estimation by analogy.
Boehm Software Quality Model
Boehm Software Quality Model is an important Software Quality Model. Introduced in 1978, it helps define the usability, maintainability, and portability of the product. Learn more: www.professionalqa.com/boehm-software-quality-model
Software maintenance and configuration management, software engineering
Types of Software Maintenance, Re-Engineering, Reverse Engineering, Forward Engineering, The SCM Process, Identification of Objects in the Software Configuration, Version
Control and Change Control
Software Engineering (Software Quality Assurance)
The document discusses software quality assurance (SQA) and quality control (QC). It defines SQA as a planned set of activities to evaluate the development process and ensure software meets requirements. QC focuses on reviews, inspections, and tests to find and remove defects before product release. Formal technical reviews (FTRs) are important QC activities that involve evaluation of work products by other engineers to uncover errors early. The goal is to improve quality and catch the majority of defects in a cost-effective manner.
Software Quality Models: A Comparative Study paper
Software Quality Models: A Comparative Study paper
McCall, Boehm, FURPS, Dromey, and ISO - Moutasm Tamimi
Iterative model
The iterative model breaks a project into small modules that can be delivered incrementally. A working version is produced in the first module, with each subsequent release adding additional functionality until the full system is complete. It allows for quick releases during development and makes it easier to develop and test in smaller iterations while incorporating customer feedback at each stage. However, it requires more resources than traditional models and skilled management to avoid increased costs over time.
Improving of software processes
This document discusses software project management. It outlines software processes, common problems, and methods for improving processes. Software processes involve many elements and sub-processes. Common problems include cost overruns, schedule delays, low productivity, and poor quality. There are three methods for improving processes: meta processes focus on organizational strategies and profitability, macro processes produce software within constraints for a project, and micro processes focus on iterations and risk resolution for a project team. The objective of process improvement is to maximize resources for productive activities and minimize overhead impacts on resources like personnel and schedule to ultimately enhance product quality.
Software Engineering Diversity
It's about software engineering diversity. To build a software at first we fixed our requirements and according to our requirements we have to choose perfect software design and implementation techniques. For different software we have to select different kinds of techniques.
Software maintenance Unit5
This document provides an overview of software maintenance. It discusses that software maintenance is an important phase of the software life cycle that accounts for 40-70% of total costs. Maintenance includes error correction, enhancements, deletions of obsolete capabilities, and optimizations. The document categorizes maintenance into corrective, adaptive, perfective and preventive types. It also discusses the need for maintenance to adapt to changing user requirements and environments. The document describes approaches to software maintenance including program understanding, generating maintenance proposals, accounting for ripple effects, and modified program testing. It discusses challenges like lack of documentation and high staff turnover. The document also introduces concepts of reengineering and reverse engineering to make legacy systems more maintainable.
comparative study software quality models
The ppt is base on a paper: comparative study software quality models. know different types of software quality and their characteristics. The goal of the study is to provide a reference to software developers when they are measuring the quality of their software.
HCI 3e - Ch 13: Socio-organizational issues and stakeholder requirements
Chapter 13: Socio-organizational issues and stakeholder requirements
from
Dix, Finlay, Abowd and Beale (2004).
Human-Computer Interaction, third edition.
Prentice Hall. ISBN 0-13-239864-8.
http://www.hcibook.com/e3/
Chapter 13 software testing strategies
This ppt covers the following
A strategic approach to testing
Test strategies for conventional software
Test strategies for object-oriented software
Validation testing
System testing
The art of debugging
Software reuse ppt.
Software reuse is the process of implementing or updating software systems using existing software components.
Software quality assurance lecture 1
This document discusses software quality assurance. It defines software as computer programs, procedures, and documentation related to operating a computer system. Software quality is defined as meeting requirements and user needs/expectations. Quality factors include correctness, reliability, efficiency, integrity, usability, maintainability, flexibility, testability, portability, reusability, and interoperability. Software quality assurance is a planned set of actions to provide confidence that software development/maintenance conforms to requirements and schedules/budgets. The objectives of SQA are to assure acceptable confidence in conforming to functional/managerial requirements during development and maintenance. Three principles of QA are to know what is being done, know what should be done, and know how to
Usability Engineering Presentation Slides
Usability: the extent to which a product can be used by specified users to achieve specified goals with effectiveness, efficiency and satisfaction in a specified context of use.“
For instance:
• Appropriate for a purpose
• Comprehensible, usable, (learnable), …
• Ergonomic, high-performance, ...
• Reliable, robust, …
Software testing
The objective of software testing is to find greatest possible number of errors with a manageable amount of effort applied over a realistic time span
Design principles & quality factors
The document discusses McCall's quality factors model for classifying software quality requirements. It describes the three categories in McCall's model - product operation factors, product revision factors, and product transition factors. Under each category, it lists and describes the specific quality factors, including correctness, reliability, efficiency, integrity, usability, maintainability, flexibility, testability, portability, reusability, and interoperability. It also discusses some alternative models that other researchers have proposed and eight design principles for structuring high-quality software designs.
Software quality
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.
More Related Content
What's hot
Human computer interaction -Input output channel with Scenario
This document discusses input and output channels in human-computer interaction. It describes the five human senses - sight, hearing, touch, taste and smell - and how they provide input. It then discusses the major effectors like limbs, fingers and vocal systems that provide human output. The document focuses on how vision, hearing and touch are used as input channels in interacting with computers, primarily through the eyes, fingers and voice. It provides details on the physiological mechanisms and processing involved in each sense.
Cocomo model
The COCOMO model is a widely used software cost estimation model that predicts development effort and schedule based on project attributes. It includes basic, intermediate, and detailed models of increasing complexity. The intermediate model estimates effort as a function of source lines of code and cost drivers. The detailed model further incorporates the impact of cost drivers on development phases. COCOMO 2 expands on this with application composition, early design, reuse, and post-architecture models for different project stages.
Publish subscribe model overview
The document provides an overview of the publish-subscribe model from the perspective of a database. It discusses key aspects of the publish-subscribe model including decoupling of publishers and subscribers, subscription models, and quality measures. It also examines applying publish-subscribe concepts in databases through expressions, continuous queries, and using XML with XFilters and SQL queries.
WEB INTERFACE DESIGN
The document discusses principles and patterns for designing web interfaces, including making interactions direct, lightweight, and keeping users on the page. It covers various techniques for inline and overlay editing, direct selection of objects, drag and drop interactions, and using contextual tools near content to improve usability. The document provides examples and guidelines for implementing these patterns and principles in web design.
Software project management Software economics
This document discusses software project management and cost estimation. It outlines five basic factors that influence software project costs: size, process, personnel, environment, and required quality. An equation is provided that estimates effort based on these five factors. The document also discusses the importance of cost estimation for feasibility analysis and return on investment calculations. It describes different techniques for software cost estimation including algorithmic modeling, expert judgment, top-down, bottom-up, and estimation by analogy.
Boehm Software Quality Model
Boehm Software Quality Model is an important Software Quality Model. Introduced in 1978, it helps define the usability, maintainability, and portability of the product. Learn more: www.professionalqa.com/boehm-software-quality-model
Software maintenance and configuration management, software engineering
Types of Software Maintenance, Re-Engineering, Reverse Engineering, Forward Engineering, The SCM Process, Identification of Objects in the Software Configuration, Version
Control and Change Control
Software Engineering (Software Quality Assurance)
The document discusses software quality assurance (SQA) and quality control (QC). It defines SQA as a planned set of activities to evaluate the development process and ensure software meets requirements. QC focuses on reviews, inspections, and tests to find and remove defects before product release. Formal technical reviews (FTRs) are important QC activities that involve evaluation of work products by other engineers to uncover errors early. The goal is to improve quality and catch the majority of defects in a cost-effective manner.
Software Quality Models: A Comparative Study paper
Software Quality Models: A Comparative Study paper
McCall, Boehm, FURPS, Dromey, and ISO - Moutasm Tamimi
Iterative model
The iterative model breaks a project into small modules that can be delivered incrementally. A working version is produced in the first module, with each subsequent release adding additional functionality until the full system is complete. It allows for quick releases during development and makes it easier to develop and test in smaller iterations while incorporating customer feedback at each stage. However, it requires more resources than traditional models and skilled management to avoid increased costs over time.
Improving of software processes
This document discusses software project management. It outlines software processes, common problems, and methods for improving processes. Software processes involve many elements and sub-processes. Common problems include cost overruns, schedule delays, low productivity, and poor quality. There are three methods for improving processes: meta processes focus on organizational strategies and profitability, macro processes produce software within constraints for a project, and micro processes focus on iterations and risk resolution for a project team. The objective of process improvement is to maximize resources for productive activities and minimize overhead impacts on resources like personnel and schedule to ultimately enhance product quality.
Software Engineering Diversity
It's about software engineering diversity. To build a software at first we fixed our requirements and according to our requirements we have to choose perfect software design and implementation techniques. For different software we have to select different kinds of techniques.
Software maintenance Unit5
This document provides an overview of software maintenance. It discusses that software maintenance is an important phase of the software life cycle that accounts for 40-70% of total costs. Maintenance includes error correction, enhancements, deletions of obsolete capabilities, and optimizations. The document categorizes maintenance into corrective, adaptive, perfective and preventive types. It also discusses the need for maintenance to adapt to changing user requirements and environments. The document describes approaches to software maintenance including program understanding, generating maintenance proposals, accounting for ripple effects, and modified program testing. It discusses challenges like lack of documentation and high staff turnover. The document also introduces concepts of reengineering and reverse engineering to make legacy systems more maintainable.
comparative study software quality models
The ppt is base on a paper: comparative study software quality models. know different types of software quality and their characteristics. The goal of the study is to provide a reference to software developers when they are measuring the quality of their software.
HCI 3e - Ch 13: Socio-organizational issues and stakeholder requirements
Chapter 13: Socio-organizational issues and stakeholder requirements
from
Dix, Finlay, Abowd and Beale (2004).
Human-Computer Interaction, third edition.
Prentice Hall. ISBN 0-13-239864-8.
http://www.hcibook.com/e3/
Chapter 13 software testing strategies
This ppt covers the following
A strategic approach to testing
Test strategies for conventional software
Test strategies for object-oriented software
Validation testing
System testing
The art of debugging
Software reuse ppt.
Software reuse is the process of implementing or updating software systems using existing software components.
Software quality assurance lecture 1
This document discusses software quality assurance. It defines software as computer programs, procedures, and documentation related to operating a computer system. Software quality is defined as meeting requirements and user needs/expectations. Quality factors include correctness, reliability, efficiency, integrity, usability, maintainability, flexibility, testability, portability, reusability, and interoperability. Software quality assurance is a planned set of actions to provide confidence that software development/maintenance conforms to requirements and schedules/budgets. The objectives of SQA are to assure acceptable confidence in conforming to functional/managerial requirements during development and maintenance. Three principles of QA are to know what is being done, know what should be done, and know how to
Usability Engineering Presentation Slides
Usability: the extent to which a product can be used by specified users to achieve specified goals with effectiveness, efficiency and satisfaction in a specified context of use.“
For instance:
• Appropriate for a purpose
• Comprehensible, usable, (learnable), …
• Ergonomic, high-performance, ...
• Reliable, robust, …
Software testing
The objective of software testing is to find greatest possible number of errors with a manageable amount of effort applied over a realistic time span
What's hot (20)
Human computer interaction -Input output channel with Scenario
Human computer interaction -Input output channel with Scenario
Software maintenance and configuration management, software engineering
Software maintenance and configuration management, software engineering
Software Quality Models: A Comparative Study paper
Software Quality Models: A Comparative Study paper
HCI 3e - Ch 13: Socio-organizational issues and stakeholder requirements
HCI 3e - Ch 13: Socio-organizational issues and stakeholder requirements
Similar to McCall Software Quality Model in Software Quality Assurance
Design principles & quality factors
The document discusses McCall's quality factors model for classifying software quality requirements. It describes the three categories in McCall's model - product operation factors, product revision factors, and product transition factors. Under each category, it lists and describes the specific quality factors, including correctness, reliability, efficiency, integrity, usability, maintainability, flexibility, testability, portability, reusability, and interoperability. It also discusses some alternative models that other researchers have proposed and eight design principles for structuring high-quality software designs.
Software quality
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.
Software Quality Factors-Non Functional Rq.pptx
The document discusses McCall's model of software quality factors. It identifies three categories of quality factors: product operation factors, product revision factors, and product transition factors. Product operation factors include correctness, reliability, efficiency, integrity, and usability which relate to how well the software runs. Product revision factors include maintainability, flexibility, and testability which relate to how easily the software can be changed, tested, and redeployed. Product transition factors include portability, reusability, and interoperability which relate to moving the software between platforms and interfacing with other systems. The document provides examples of how each quality factor can be specified as a requirement.
Software Quality Assurance
The document discusses software quality factors and McCall's quality factors model. McCall's model classifies software quality requirements into 11 factors across 3 categories: product operation, product revision, and product transition. Product operation factors include correctness, reliability, efficiency, integrity, and usability. Product revision factors are maintainability, flexibility, and testability. Product transition factors are portability, reusability, and interoperability. The document provides examples to illustrate each quality factor. Alternative models from other authors that expand on McCall's 11 factors are also mentioned.
6. McCall's Model.pptx
McCall's model defines quality factors for software products across three categories: product operation, product revision, and product transition. For product operation, the key factors are correctness, reliability, efficiency, integrity, and usability. Product revision factors include maintainability, flexibility, and testability. Finally, for product transition the important factors are portability, reusability, and interoperability. The model provides examples of how each factor could be specified as a requirement in a software project.
Attributes of 'well - engineered' software product
The document discusses the attributes of well-engineered software, including dependability, maintainability, efficiency, usability, portability, and documentation. Dependability means the software reliably performs as designed and accounts for reliability, security, and safety. Maintainability ensures the software can receive updates to fix errors or add features based on feedback. Portability means the software can run on different platforms without issues. Documentation outlines system requirements and specifications for optimal performance. Usability ensures users can easily interact with and manipulate the software through consistent design and a small learning curve. Efficiency evaluates how software utilizes computer resources without slowing down systems or using too many resources.
SE Lecture 1.ppt
The document provides an overview of software engineering concepts including definitions of software, characteristics of good software, and the software engineering process. It discusses that software engineering aims to apply systematic and disciplined approaches to software development and maintenance to economically produce reliable and efficient software. The document also outlines key activities in a generic software process framework including communication, planning, modeling, construction, and deployment.
SE Lecture 1.ppt
The document provides an overview of software engineering concepts. It defines software and its key characteristics, such as being developed rather than manufactured. It discusses different types of software applications and attributes of good software like maintainability and dependability. The document also outlines the activities in a generic software process, including communication, planning, modeling, construction, and deployment. It emphasizes that the process should be adapted to each project's specific needs.
Software engineering
software engineering , its characteristic ,changing nature of software,evolving nature of software,legacy software,generic view of software,process flow ,umbrella activity,CMMI,PROCESS ASSESSMENT ,team and personal software process
Quality attributes in software architecture
This document discusses various quality attributes in software architecture including responsiveness, scalability, usability, security, accessibility, serviceability, extensibility, distributability, maintainability, portability, reliability, testability, and compatibility. For each attribute, it provides definitions and considerations for how to achieve that attribute in architecture and design. It also discusses relationships between attributes and references quality models for evaluating software.
Chapter 01
This document provides an overview of software and software engineering. It defines software, discusses why software is important to modern economies, and outlines some key characteristics of software such as its non-physical nature and tendency to deteriorate over time rather than wear out. The document also introduces common software applications, categories, and costs. Finally, it discusses the importance of software engineering in developing reliable, high-quality software economically.
Chapter 01
This document provides an overview of software and software engineering. It defines software, discusses why software is important, and explores key software engineering concepts like the software development process, process models, case studies, and requirements. Specifically, it defines software, explains that software engineering aims to produce reliable software economically, and discusses the importance of processes and methods in software development.
Quality Concept
This document defines key concepts related to quality in software engineering, including definitions of quality, software quality, and several quality factor frameworks. It discusses Garvin's quality dimensions, McCall's quality factors, ISO 9126 quality factors, and targeted quality factors. The document also covers concepts like good enough software and the cost of quality.
Week_01-Intro to Software Engineering-1.ppt
This document provides an overview of software engineering concepts including definitions of software and software engineering. It discusses the importance of software and different types of software applications. The document also introduces a generic software engineering process framework consisting of communication, planning, modeling, construction, and deployment activities. Finally, it provides examples of an embedded insulin pump control system and a patient information system for mental health care to illustrate software engineering concepts and processes.
1_Software Quality Control.pptx
This document discusses software quality control. It aims to help students understand why quality control is important, how it works in projects, and how to set and follow standards. It defines quality as meeting customer requirements now and in the future. It also discusses that around 63% of software projects exceed costs mainly due to frequent changes and unclear requirements. Quality assurance ensures production meets pre-established requirements and standards through activities like reviews, testing, and audits. The software quality assurance team is responsible for many quality control tasks throughout the development process.
Identification & analysis of parameters for program quality improvement a ree...
This document discusses parameters for improving program quality from a reengineering perspective. It begins with an introduction stating that software development is complex and dynamic, so programs must be flexible, reusable and scalable. It then reviews literature on various software quality models proposed over decades to identify quality parameters. These parameters affect program design, functionality, performance and other attributes. The document emphasizes that considering quality parameters at each development stage can help produce programs that meet requirements and are suitable for reengineering.
Evolving role of Software,Legacy software,CASE tools,Process Models,CMMI
The Evolving role of Software – Software – The changing Nature of Software – Legacy software, Introduction to CASE tools, A generic view of process– A layered Technology – A Process Framework – The Capability Maturity Model Integration (CMMI) – Process Assessment – Personal and Team Process Models. Product and Process. Process Models – The Waterfall Model – Incremental Process Models – Incremental Model – The RAD Model – Evolutionary Process Models – Prototyping – The Spiral Model – The Concurrent Development Model – Specialized Process Models – the Unified Process.
Software Testing - Software Quality
The document discusses software quality assurance and testing. It defines software quality as having two aspects - quality of design which includes requirements and specifications, and quality of conformance which focuses on implementation. Software Quality Assurance (SQA) includes quality management, effective engineering processes, formal techniques, testing strategies, documentation control, and measurement/reporting. SQA aims to ensure requirements quality, design quality, code quality, and effective quality control. Non-functional attributes like reliability, usability, and performance largely determine a software's subjective quality from a user's perspective.
Software qualityfactors
This document discusses software quality factors and different models for categorizing them. It summarizes McCall's quality factors model, which groups factors into three categories: product operation, product revision, and product transition. Under each category it lists the specific factors, like correctness, reliability, and maintainability, and provides examples. It also discusses some alternative models that suggest additional quality factors like verifiability, expandability, safety, and manageability. The document emphasizes that both developers and clients should care about software quality factors and they may prioritize different factors for different types of applications.
Similar to McCall Software Quality Model in Software Quality Assurance (20)
Attributes of 'well - engineered' software product
Attributes of 'well - engineered' software product
Identification & analysis of parameters for program quality improvement a ree...
Identification & analysis of parameters for program quality improvement a ree...
Evolving role of Software,Legacy software,CASE tools,Process Models,CMMI
Evolving role of Software,Legacy software,CASE tools,Process Models,CMMI
More from sundas Shabbir
History of windows and Windows servers
The document provides a history of Microsoft operating systems from 1985 to present day, including:
- MS-DOS (Microsoft Disk Operating System), the precursor to Windows operating systems
- Early Windows versions 1.0 through 3.1 that introduced graphical user interfaces
- Major Windows releases such as Windows 95, 98, ME, NT, 2000, XP, 7, 8, and 10
- Related Microsoft operating systems including Windows Server, Windows Home Server, Windows CE, Windows Mobile, and Windows Phone.
History of Windows Server
This document provides a history of Microsoft Windows Server operating systems from 1993 to 2016. It describes the key releases including Windows NT 3.1 Advanced Server in 1993, Windows 2000 in 2000 which introduced Active Directory, Windows Server 2003 in 2003 with improved security and server roles, Windows Server 2008 in 2008 with new features like Hyper-V virtualization, Windows Server 2012 in 2012 with cloud-oriented features and a default Server Core installation, and Windows Server 2016 in 2016 with additional container and software-defined networking support and a new Nano Server deployment option. Each new release brought performance improvements and additional capabilities for managing networks, storage, security and workloads.
Introduction to Operating System and its Types
The document provides an introduction to operating systems, including what they are, their types, and the services they provide. It discusses operating system I/O software, file systems, and gives examples of different operating systems like Windows, Linux, Mac OS, and Unix. It then focuses on Windows, covering its evolution from Windows 3.1 to the current Windows 10, and the system requirements and steps for installing Windows 8/8.1.
Sensors and its type by ss
what is sensor and its type.
Subscribe my channel like and comment on video
https://youtu.be/sab1Fwybrkc
Linux file commands
This document summarizes common Linux file commands including file, rm, mv, cat, cp, uname, echo, which, cal, wc, who, whoami, more, man, date and commands to shut down or reboot the system. It provides the syntax and options for each command to view, create, copy, move and delete files, view system information, print output, and manage the system date and time.
Linux Commands
This document provides descriptions and examples of various Linux commands, including commands for listing files and directories (ls), creating directories (mkdir), viewing file contents (cat, tac), copying and moving files (cp, mv), checking the current working directory (pwd), finding command locations (whereis, which), getting command documentation (man, info), viewing user and system information (whoami, uname), and more. 35 commands are described in total, with the syntax and examples provided for each.
RHDB Release History Database Model
This document discusses the Release History Database (RHDB) model, which integrates versioning system information from CVS with bug report data from Bugzilla. The RHDB stores extracted version and bug report data linked together. It was the first to link CVS artifacts and Bugzilla problem reports. The RHDB offers benefits for software evolution analysis by providing qualified links between changes and bugs and identifying files coupled through changes and bugs.
Software Project Management Lab Manual Lab 1
This document provides an introduction and instructions for a lab on using Microsoft Project. The lab includes 5 activities to familiarize students with starting MS Project, creating a project plan from a template, switching between views, viewing built-in reports, and creating a visual report. The lab aims to help students understand basic functions of MS Project for tracking project goals, costs, deadlines and assigned resources.
More from sundas Shabbir (8)
Recently uploaded
🏎️Tech Transformation: DevOps Insights from the Experts 👩💻
Connect with fellow Trailblazers, learn from industry experts Glenda Thomson (Salesforce, Principal Technical Architect) and Will Dinn (Judo Bank, Salesforce Development Lead), and discover how to harness DevOps tools with Salesforce.
一比一原版(USF毕业证)旧金山大学毕业证如何办理
USF硕士毕业证成绩单【微信95270640】一比一伪造旧金山大学文凭@假冒USF毕业证成绩单+Q微信95270640办理USF学位证书@仿造USF毕业文凭证书@购买旧金山大学毕业证成绩单USF真实使馆认证/真实留信认证回国人员证明
#一整套旧金山大学文凭证件办理#—包含旧金山大学旧金山大学本科毕业证成绩单学历认证|使馆认证|归国人员证明|教育部认证|留信网认证永远存档教育部学历学位认证查询办理国外文凭国外学历学位认证#我们提供全套办理服务。
一整套留学文凭证件服务：
一：旧金山大学旧金山大学本科毕业证成绩单毕业证 #成绩单等全套材料从防伪到印刷水印底纹到钢印烫金
二：真实使馆认证（留学人员回国证明）使馆存档
三：真实教育部认证教育部存档教育部留服网站永久可查
四：留信认证留学生信息网站永久可查
国外毕业证学位证成绩单办理方法：
1客户提供办理旧金山大学旧金山大学本科毕业证成绩单信息：姓名生日专业学位毕业时间等（如信息不确定可以咨询顾问：我们有专业老师帮你查询）；
2开始安排制作毕业证成绩单电子图；
3毕业证成绩单电子版做好以后发送给您确认；
4毕业证成绩单电子版您确认信息无误之后安排制作成品；
5成品做好拍照或者视频给您确认；
6快递给客户（国内顺丰国外DHLUPS等快读邮寄）。
教育部文凭学历认证认证的用途：
如果您计划在国内发展那么办理国内教育部认证是必不可少的。事业性用人单位如银行国企公务员在您应聘时都会需要您提供这个认证。其他私营 #外企企业无需提供！办理教育部认证所需资料众多且烦琐所有材料您都必须提供原件我们凭借丰富的经验帮您快速整合材料让您少走弯路。
实体公司专业为您服务如有需要请联系我: 微信95270640奈一次次令他失望山娃今年岁上五年级识得很多字从走出小屋开始山娃就知道父亲的家和工地共有一个很动听的名字——天河工地的底层空空荡荡很宽阔很凉爽在地上铺上报纸和水泥袋父亲和工人们中午全睡在地上地面坑坑洼洼山娃曾多次绊倒过也曾有长铁钉穿透凉鞋刺在脚板上但山娃不怕工地上也常有五六个从乡下来的小学生他们的父母亲也是高楼上的建筑工人小伙伴来自不同省份都操着带有浓重口音的普通话可不知为啥山娃不仅很快与他们熟识了
Enums On Steroids - let's look at sealed classes !
These are slides for my session"Enums On Steroids - let's look at sealed classes !" - delivered among others, on Devoxx UK 2024 conference
一比一原版(UMN毕业证)明尼苏达大学毕业证如何办理
UMN硕士毕业证成绩单【微信95270640】购买（明尼苏达大学毕业证成绩单硕士学历）Q微信95270640代办UMN学历认证留信网伪造明尼苏达大学学位证书精仿明尼苏达大学本科/硕士文凭证书补办明尼苏达大学 diplomaoffer,Transcript购买明尼苏达大学毕业证成绩单购买UMN假毕业证学位证书购买伪造明尼苏达大学文凭证书学位证书,专业办理雅思、托福成绩单，学生ID卡，在读证明，海外各大学offer录取通知书，毕业证书，成绩单，文凭等材料:1:1完美还原毕业证、offer录取通知书、学生卡等各种在读或毕业材料的防伪工艺（包括 烫金、烫银、钢印、底纹、凹凸版、水印、防伪光标、热敏防伪、文字图案浮雕，激光镭射，紫外荧光，温感光标）学校原版上有的工艺我们一样不会少，不论是老版本还是最新版本，都能保证最高程度还原，力争完美以求让所有同学都能享受到完美的品质服务。
#毕业证成绩单 #毕业証 #成绩单 #學生卡 #OFFER录取通知书 #雅思#托福等……
国外大学明尼苏达大学明尼苏达大学毕业证offer制作方法（一对一专业服务）
1客户提供办理信息：姓名生日专业学位毕业时间等（如信息不确定可以咨询顾问：我们有专业老师帮你查询）；
2开始安排制作毕业证成绩单电子图；
3毕业证成绩单电子版做好以后发送给您确认；
4毕业证成绩单电子版您确认信息无误之后安排制作成品；
5成品做好拍照或者视频给您确认；
6快递给客户（国内顺丰国外DHLUPS等快读邮寄）
— — 制作工艺 【高仿真】— —
凭借多年的制作经验本公司制作明尼苏达大学明尼苏达大学毕业证offer《激光》《水印》《钢印》《烫金》《紫外线》凹凸版uv版等防伪技术一流高精仿度几乎跟学校100%相同！让您绝对满意。
— — -公司理念 【诚信为主】— — —
我們以質量求生存.以服务求发展有雄厚的实力专业的团队咨询顾问为您细心解答可详谈是真是假眼见为实让您真正放心平凡人生,尽我所能助您一臂之力让我們携手圆您梦想!
此贴长年有效【贴心专线/微-信: 95270640】敬请保留此联系方式以备用！如有不在线请给我们留言！我们将在第一时间给您回复!上散发着一抹抹的光晕而这每处自然形成的细节融合在一起浑然天成的美实在令人心生愉悦小道的周边无秩序的生长着几株艳丽的野花红的粉的紫的虽混乱无章却给这幅美景更增添一份性感夹杂着一份纯洁的妖娆毫无违和感实在给人带来一份悠然幸福的心情如果说现在的审美已经断然拒绝了无声的话那么在树林间飞掠而过的小鸟叽叽咋咋的叫声是否就是这最后的点睛之笔悠然走在林间的小路上宁静与清香一丝丝的盛夏气息吸入身体昔日生活里的繁忙多
WWDC 2024 Keynote Review: For CocoaCoders Austin
Overview of WWDC 2024 Keynote Address.
Covers: Apple Intelligence, iOS18, macOS Sequoia, iPadOS, watchOS, visionOS, and Apple TV+.
Understandable dialogue on Apple TV+
On-device app controlling AI.
Access to ChatGPT with a guest appearance by Chief Data Thief Sam Altman!
App Locking! iPhone Mirroring! And a Calculator!!
Upturn India Technologies - Web development company in Nashik
Nashik's top web development company, Upturn India Technologies, crafts innovative digital solutions for your success. Partner with us and achieve your goals
8 Best Automated Android App Testing Tool and Framework in 2024.pdf
Regarding mobile operating systems, two major players dominate our thoughts: Android and iPhone. With Android leading the market, software development companies are focused on delivering apps compatible with this OS. Ensuring an app's functionality across various Android devices, OS versions, and hardware specifications is critical, making Android app testing essential.
Kubernetes at Scale: Going Multi-Cluster with Istio
Divine Odazie and Jubril Oyetunji share tips on Going Multi-Cluster with Istio Service Mesh at DevOpsDays Houston.
Operational ease MuleSoft and Salesforce Service Cloud Solution v1.0.pptx
Operational ease MuleSoft and Salesforce Service Cloud Solution v1.0
14 th Edition of International conference on computer vision
About the event
14th Edition of International conference on computer vision
Computer conferences organized by ScienceFather group. ScienceFather takes the privilege to invite speakers participants students delegates and exhibitors from across the globe to its International Conference on computer conferences to be held in the Various Beautiful cites of the world. computer conferences are a discussion of common Inventions-related issues and additionally trade information share proof thoughts and insight into advanced developments in the science inventions service system. New technology may create many materials and devices with a vast range of applications such as in Science medicine electronics biomaterials energy production and consumer products.
Nomination are Open!! Don't Miss it
Visit: computer.scifat.com
Award Nomination: https://x-i.me/ishnom
Conference Submission: https://x-i.me/anicon
For Enquiry: Computer@scifat.com
ppt on the brain chip neuralink.pptx
A neural network is a machine learning program, or model, that makes decisions in a manner similar to the human brain, by using processes that mimic the way biological neurons work together to identify phenomena, weigh options and arrive at conclusions.
Mobile App Development Company In Noida | Drona Infotech
React.js, a JavaScript library developed by Facebook, has gained immense popularity for building user interfaces, especially for single-page applications. Over the years, React has evolved and expanded its capabilities, becoming a preferred choice for mobile app development. This article will explore why React.js is an excellent choice for the Best Mobile App development company in Noida.
Visit Us For Information: https://www.linkedin.com/pulse/what-makes-reactjs-stand-out-mobile-app-development-rajesh-rai-pihvf/
TMU毕业证书精仿办理
多伦多都会大学毕业证成绩单(留信网认证)【176555708微信】不能毕业办理假文凭回国找工作
【多伦多都会大学毕业证成绩单仿制】（176555708微信☀️）伪造研究生学位证书TMU毕业证文凭,多伦多都会大学文凭证书学籍信息入库,多伦多都会大学学位证书留学高校学位证书补办
【TMU毕业证【微信176555708】多伦多都会大学文凭学历】【微信176555708】【多伦多都会大学文凭学历证书】【多伦多都会大学毕业证书与成绩单样本图片】毕业证书补办 Fake Degree做学费单【毕业证明信-推荐信】成绩单，录取通知书，Offer，在读证明，雅思托福成绩单，真实大使馆教育部认证，回国人员证明，留信网认证。网上存档永久可查！
What’s New in Odoo 17 – A Complete Roadmap
Odoo releases a new update every year. The latest version, Odoo 17, came out in October 2023. It brought many improvements to the user interface and user experience, along with new features in modules like accounting, marketing, manufacturing, websites, and more.
The Odoo 17 update has been a hot topic among startups, mid-sized businesses, large enterprises, and Odoo developers aiming to grow their businesses. Since it is now already the first quarter of 2024, you must have a clear idea of what Odoo 17 entails and what it can offer your business if you are still not aware of it.
This blog covers the features and functionalities. Explore the entire blog and get in touch with expert Odoo ERP consultants to leverage Odoo 17 and its features for your business too.
An Overview of Odoo ERP
Odoo ERP was first released as OpenERP software in February 2005. It is a suite of business applications used for ERP, CRM, eCommerce, websites, and project management. Ten years ago, the Odoo Enterprise edition was launched to help fund the Odoo Community version.
When you compare Odoo Community and Enterprise, the Enterprise edition offers exclusive features like mobile app access, Odoo Studio customisation, Odoo hosting, and unlimited functional support.
Today, Odoo is a well-known name used by companies of all sizes across various industries, including manufacturing, retail, accounting, marketing, healthcare, IT consulting, and R&D.
The latest version, Odoo 17, has been available since October 2023. Key highlights of this update include:
Enhanced user experience with improvements to the command bar, faster backend page loading, and multiple dashboard views.
Instant report generation, credit limit alerts for sales and invoices, separate OCR settings for invoice creation, and an auto-complete feature for forms in the accounting module.
Improved image handling and global attribute changes for mailing lists in email marketing.
A default auto-signature option and a refuse-to-sign option in HR modules.
Options to divide and merge manufacturing orders, track the status of manufacturing orders, and more in the MRP module.
Dark mode in Odoo 17.
Now that the Odoo 17 announcement is official, let’s look at what’s new in Odoo 17!
What is Odoo ERP 17?
Odoo 17 is the latest version of one of the world’s leading open-source enterprise ERPs. This version has come up with significant improvements explained here in this blog. Also, this new version aims to introduce features that enhance time-saving, efficiency, and productivity for users across various organisations.
Odoo 17, released at the Odoo Experience 2023, brought notable improvements to the user interface and added new functionalities with enhancements in performance, accessibility, data analysis, and management, further expanding its reach in the market.
Safelyio Toolbox Talk Softwate & App (How To Digitize Safety Meetings)
Consistent toolbox talks are critical for maintaining workplace safety, as they provide regular opportunities to address specific hazards and reinforce safe practices.
These brief, focused sessions ensure that safety is a continual conversation rather than a one-time event, which helps keep safety protocols fresh in employees' minds. Studies have shown that shorter, more frequent training sessions are more effective for retention and behavior change compared to longer, infrequent sessions.
Engaging workers regularly, toolbox talks promote a culture of safety, empower employees to voice concerns, and ultimately reduce the likelihood of accidents and injuries on site.
The traditional method of conducting safety talks with paper documents and lengthy meetings is not only time-consuming but also less effective. Manual tracking of attendance and compliance is prone to errors and inconsistencies, leading to gaps in safety communication and potential non-compliance with OSHA regulations. Switching to a digital solution like Safelyio offers significant advantages.
Safelyio automates the delivery and documentation of safety talks, ensuring consistency and accessibility. The microlearning approach breaks down complex safety protocols into manageable, bite-sized pieces, making it easier for employees to absorb and retain information.
This method minimizes disruptions to work schedules, eliminates the hassle of paperwork, and ensures that all safety communications are tracked and recorded accurately. Ultimately, using a digital platform like Safelyio enhances engagement, compliance, and overall safety performance on site. https://safelyio.com/
The Rising Future of CPaaS in the Middle East 2024
Explore "The Rising Future of CPaaS in the Middle East in 2024" with this comprehensive PPT presentation. Discover how Communication Platforms as a Service (CPaaS) is transforming communication across various sectors in the Middle East.
DevOps Consulting Company | Hire DevOps Services
Spiral Mantra excels in providing comprehensive DevOps services, including Azure and AWS DevOps solutions. As a top DevOps consulting company, we offer controlled services, cloud DevOps, and expert consulting nationwide, including Houston and New York. Our skilled DevOps engineers ensure seamless integration and optimized operations for your business. Choose Spiral Mantra for superior DevOps services.
https://www.spiralmantra.com/devops/
Measures in SQL (SIGMOD 2024, Santiago, Chile)
SQL has attained widespread adoption, but Business Intelligence tools still use their own higher level languages based upon a multidimensional paradigm. Composable calculations are what is missing from SQL, and we propose a new kind of column, called a measure, that attaches a calculation to a table. Like regular tables, tables with measures are composable and closed when used in queries.
SQL-with-measures has the power, conciseness and reusability of multidimensional languages but retains SQL semantics. Measure invocations can be expanded in place to simple, clear SQL.
To define the evaluation semantics for measures, we introduce context-sensitive expressions (a way to evaluate multidimensional expressions that is consistent with existing SQL semantics), a concept called evaluation context, and several operations for setting and modifying the evaluation context.
A talk at SIGMOD, June 9–15, 2024, Santiago, Chile
Authors: Julian Hyde (Google) and John Fremlin (Google)
https://doi.org/10.1145/3626246.3653374
Transforming Product Development using OnePlan To Boost Efficiency and Innova...
Ready to overcome challenges and drive innovation in your organization? Join us in our upcoming webinar where we discuss how to combat resource limitations, scope creep, and the difficulties of aligning your projects with strategic goals. Discover how OnePlan can revolutionize your product development processes, helping your team to innovate faster, manage resources more effectively, and deliver exceptional results.
ACE - Team 24 Wrapup event at ahmedabad.
Atlassian Team 24 event wrap-up Ahmedabad. Recap of Atlassian team24 event.
Recently uploaded (20)
🏎️Tech Transformation: DevOps Insights from the Experts 👩💻
🏎️Tech Transformation: DevOps Insights from the Experts 👩💻
Enums On Steroids - let's look at sealed classes !
Enums On Steroids - let's look at sealed classes !
Upturn India Technologies - Web development company in Nashik
Upturn India Technologies - Web development company in Nashik
8 Best Automated Android App Testing Tool and Framework in 2024.pdf
8 Best Automated Android App Testing Tool and Framework in 2024.pdf
Kubernetes at Scale: Going Multi-Cluster with Istio
Kubernetes at Scale: Going Multi-Cluster with Istio
Operational ease MuleSoft and Salesforce Service Cloud Solution v1.0.pptx
Operational ease MuleSoft and Salesforce Service Cloud Solution v1.0.pptx
14 th Edition of International conference on computer vision
14 th Edition of International conference on computer vision
Mobile App Development Company In Noida | Drona Infotech
Mobile App Development Company In Noida | Drona Infotech
Safelyio Toolbox Talk Softwate & App (How To Digitize Safety Meetings)
Safelyio Toolbox Talk Softwate & App (How To Digitize Safety Meetings)
The Rising Future of CPaaS in the Middle East 2024
The Rising Future of CPaaS in the Middle East 2024
Transforming Product Development using OnePlan To Boost Efficiency and Innova...
Transforming Product Development using OnePlan To Boost Efficiency and Innova...
McCall Software Quality Model in Software Quality Assurance
- 1. BY: SUNDAS SHABBIR Ahmed Kaim Khani 1
- 2. Software Quality: •Conformance to the users Requirements. Quality Models: •Software Quality is described by specific quality models. Software Quality Models are: McCall’s Model •Boehm Model •FURPS/FURPS+ •Dromey quality Model •ISO quality Model FURPS BY: SUNDAS SHABBIR Ahmed Kaim Khani 2
- 3. Introduction: Jim McCall produced this model for the US Air Force and the intention was to bridge the gap between users and developers. McCall Model Developed in 1967-7, •One of the first , Oldest software quality model. •Started with volume of 55 quality characteristics ,called them “factors” •Quality Factors was compressed into 11 main factors. •McCall Tried to map user view developer’s priorities. BY: SUNDAS SHABBIR Ahmed Kaim Khani 3
- 4. McCall Quality Model: Three 3 major perspectives. 1. Product Revision (ability to under go Changes) Maintainability, Flexibility, Testability. 2.Product Transition (adaptability to new environments). Portability, Reusability, Interoperability. 3.Product Operations( basic Operational characteristic). Correctness, Reliability, Efficiency, Integrity, Usability BY: SUNDAS SHABBIR Ahmed Kaim Khani 4
- 5. McCall’s Quality Model Tree BY: SUNDAS SHABBIR Ahmed Kaim Khani 5
- 6. Also known as McCall’s Quality Model Triangle BY: SUNDAS SHABBIR Ahmed Kaim Khani 6
- 7. McCall’s Quality Model: Based on 3 types of Characteristics with hierarchical dependency: 1. Factors(to specify): external software view for users. 2. Criteria(to build): internal software view for developers. 3. Measures/metrics (to control): are used for software measurement. BY: SUNDAS SHABBIR Ahmed Kaim Khani 7
- 8. 1.Product Operations •Correctness, the functionality matches the specification. or Does it do what customer wants?(meeting specification) •Reliability, the extent to which the system fails. or Does it do it accurately all of the time. (successful performance) BY: SUNDAS SHABBIR Ahmed Kaim Khani 8
- 9. 1.Product Operations conti.. •Efficiency, system resource (including cpu, disk, memory, network) usage. or Does it quickly solve the intended problem?(enough computing resources) •Integrity, protection from unauthorized access. or is it Secure? (access limitation to people) •Usability, ease of use Or Can I run it? (efforts in learning/operating) BY: SUNDAS SHABBIR Ahmed Kaim Khani 9
- 10. 2.Product revision •Maintainability, the ability to find and fix a defect. Or Can it be fixed?(fixing bugs and errors) •Flexibility, the ability to make changes required as dictated by the business. Or Can it be changed?(modifying an operational program) •Testability, the ability to Validate the software requirements. Or Can it be tested? (ensuring performance) BY: SUNDAS SHABBIR Ahmed Kaim Khani 10
- 11. 3. Product transition •Portability, the ability to transfer the software from one environment to another. Or Can it be used on another machine?(Platform dependence). •Reusability, the ease of using existing software components in a different context. Or Can part of it be reused? (generic coding). •Interoperability, the extent, or ease, to which software components work together. Or Can it interface with other system (coupling system) BY: SUNDAS SHABBIR Ahmed Kaim Khani 11
- 12. Relationship between Quality Factors and Quality Criteria •Each quality factor is positively influenced by the set of quality criteria, And the same quality criterion impacts a number of quality factors. Some quality factors positively impact others. •An effort to improve the correctness of a system will increase its reliability. BY: SUNDAS SHABBIR Ahmed Kaim Khani 12
- 13. BY: SUNDAS SHABBIR Ahmed Kaim Khani 13
- 14. BY: SUNDAS SHABBIR Ahmed Kaim Khani 14
- 15. BY: SUNDAS SHABBIR Ahmed Kaim Khani 15