ν Software product usage dictates that Software product Strategic Considerations ν Software product development dictates that Software product

Similar documents
Software quality Texts and Readings

User Centered Design (UCD)

Usable Software and its Attributes:A synthesis of Software Quality, European Community Law and Human-Computer Interaction Ronan Fitzpatrick

2/18/2009. Introducing Interactive Systems Design and Evaluation: Usability and Users First. Outlines. What is an interactive system

Concepts of Usability. Usability Testing. Usability concept ISO/IS What is context? What is context? What is usability? How to measure it?

Software Quality Assurance Text and Readings

10. Software Testing Fundamental Concepts

Software quality revisited

Quality in Use: Achieving Stakeholder Needs for Quality

Transactions on Information and Communications Technologies vol 11, 1995 WIT Press, ISSN

Software Requirements Specification (SRS) Software Requirements Specification for <Name of Project>

A Quality Model for Design Patterns

CIS 890: Safety Critical Systems

Requirements Validation and Negotiation

Usability Evaluation of Software Testing Based on Analytic Hierarchy Process Dandan HE1, a, Can WANG2

INFORMATION SECURITY PRINCIPLES OF THE UNIVERSITY OF JYVÄSKYLÄ

Unit 1 Introduction to Software Engineering

Comparative Study of Software Quality Attributes in Perspective of Usability with Generalized Classification

Harmonization of usability measurements in ISO9126 software engineering standards

A Literature Survey on standards for software product quality

Software Requirements Specification. <Project> for. Version 1.0 approved. Prepared by <author> <organization> <date created>

DISABILITY LAW SERVICE BEST PRACTICES FOR AN ACCESSIBLE AND USABLE WEBSITE

Software Requirements Specification

A Literature Survey on standards for software product quality

QUIM: A Framework for Quantifying Usability Metrics in Software Quality Models

Manchester Metropolitan University Information Security Strategy

Metadata Framework for Resource Discovery

EXAM PREPARATION GUIDE

Quality and usability: A new framework

Applying ISO/IEC Quality Model to Quality Requirements Engineering on Critical Software

In this Lecture you will Learn: Design Patterns. Patterns vs. Frameworks. Patterns vs. Frameworks

Introduction to Architecture. Introduction to Architecture 1

Policy Title; Business Continuity Management Policy. Date Published/Reviewed; February 2018

Software engineering Product quality Part 1: Quality model

Ingegneria del Software Corso di Laurea in Informatica per il Management. Software quality and Object Oriented Principles

Software Requirements Specification. <Project> for. Version 1.0 approved. Prepared by <author(s)> <Organization> <Date created>

Advanced Software Engineering: Software Testing

Regulations for Compulsory Product Certification

PROTERRA CERTIFICATION PROTOCOL V2.2

CS 307: Software Engineering. Lecture 10: Software Design and Architecture

PDF/UA and Section 508. Karen McCall Karlen Communications Copyright 2015

Overview of the course. User-Centred Design. Group. Practical issue. Writting the report. Project work. Fang Chen

QUESTIONS AND CONTACTS

EUROPEAN ICT PROFESSIONAL ROLE PROFILES VERSION 2 CWA 16458:2018 LOGFILE

Architecture and Standards Development Lifecycle

Guidelines for Interface Publication Issue 3

QUALITY METRICS IMPLEMENTATION IN COMPONENT BASED SOFTWARE ENGINEERING USING AI BACK PROPAGATION ALGORITHM SOFTWARE COMPONENT

A Study on Website Quality Models

4.2.2 Usability. 4 Medical software from the idea to the finished product. Figure 4.3 Verification/validation of the usability, SW = software

ISO/IEC JTC1/SC7 N2228

A System Software Quality Model using DeLone & McLean Model and

Standard Glossary of Terms used in Software Testing. Version 3.2. Foundation Extension - Usability Terms

The «SQALE» Models for assessing the Quality of Software Source Code

What is ISO/IEC 20000?

Requirements Engineering: Specification & Validation. Software Requirements and Design CITS 4401 Lecture 18

GDPR AMC SAAS AND HOSTED MODULES. UK version. AMC Consult A/S June 26, 2018 Version 1.10

Seven Requirements for Successfully Implementing Information Security Policies and Standards

Standards: Implementation, Certification and Testing Work group Friday, May 8, :00 Pm-1:30 Pm ET.

ICS 52: Introduction to Software Engineering

We may change the privacy notice from time to time by amending this page.

SAMPLE REPORT. Business Continuity Gap Analysis Report. Prepared for XYZ Business by CSC Business Continuity Services Date: xx/xx/xxxx

Wonde may collect personal information directly from You when You:

ANALYTICAL STUDY OF MAINTAINABILITY MODELS FOR QUALITY EVALUATION

Software processes, quality, and standards Non-functional testing

Lecture 13 Introduction to Software Architecture

Object Oriented Programming

Non Functional Product Requirements (illeties)


TESTING SOFTWARE QUALITY CHARACTERISTICS

Mei Nagappan. How the programmer wrote it. How the project leader understood it. How the customer explained it. How the project leader understood it

TEL2813/IS2820 Security Management

Virginia State University Policies Manual. Title: Information Security Program Policy: 6110

IT Accessibility

Requirements Specifications & Standards

Traditional Classification of Requirements

Strategic Action Plan. for Web Accessibility at Brown University

EU Data Protection Agreement

FORENSIC LABORATORY DEVELOPMENT AND MANAGEMENT: INTERNATIONAL BEST PRACTICES BY AGWEYE, BENEDICT HEAD OF FORENSICS, EFCC

DOMAIN ENGINEERING OF COMPONENTS

Presenter: Ian Musweu FCCA, FZICA, CRA. Head of Risk and Assurance Professional Insurance

Lecture 16: (Architecture IV)

Data Processing Agreement

A Hierarchical Model for Object- Oriented Design Quality Assessment

ISO INTERNATIONAL STANDARD. Ergonomics General approach, principles and concepts. Ergonomie Approche générale, principes et concepts

M403 ehealth Interoperability Overview

Introduction to software architecture Revision : 732

XIV. The Requirements Specification Document (RSD)

ORDINANCE ON EMPLOYMENT PROMOTION (AZAV) INFORMATION SECURITY MANAGEMENT SYSTEMS ACCORDING TO DIN ISO/IEC (INCL. IT SECURITY CATALOGUE)

The descriptions of the elements and measures are based on Annex D of ISO/DIS Geographic information Data quality.

SOFTWARE ARCHITECTURE & DESIGN INTRODUCTION

S1000D International Specification for Technical Publications

Requirements. CxOne Standard

Cybersecurity. Quality. security LED-Modul. basis. Comments by the electrical industry on the EU Cybersecurity Act. manufacturer s declaration

Modeling Issues Modeling Enterprises. Modeling

What is Usability? What is the Current State? Role and Activities of NIST in Usability Reactions from Stakeholders What s Next?

ISO Gap Analysis Excerpt from sample report

Information for your Certification

Reasons for data modelling

IOAS Operating Manual information and requirements specific to assessment against ISO/IEC 17065

The Role of Standards in Ensuring Toy Safety

Transcription:

Software Texts and Readings Building into software products Content overview Software Quality:Definitions and strategic issues - in library for reference. Ince, D. (1994) ISO 9001 and Software assurance. Lecture handouts. 1 Quality defined Quality models Quality characteristics Interrelationships between characteristics Measuring Grouping characteristics Prioritising characteristics 2 Software Quality defined IEEE std 729-1983 Software Quality defined The totality of features and characteristics of a software product that bear on its ability to satisfy given needs, for example, conform to specification. The degree to which software possesses a desired combination of attributes The degree to which a customer or user perceives that software meets his or her composite expectations. The composite characteristics of software that determine the degree to which the software in use will meet the Software is the extent to which a set of desirable features (attributes or characteristics) are incorporated into a software product in order to enhance its lifetime performance. expectations of the customer. 3 4 MIS Triad Brookes et al. USER BOARD IS Brookes, Grouse, Jeffery and Lawrence (1982) Information system design, Prentice Hall usage Quality Perspective Strategic Considerations development 5 usage dictates that the product possesses a desired combination of attributes or characteristics development dictates that attributes or characteristics are built into the product during the development life-cycle an appropriate model is used for assurance during design, development, production, installation and servicing, (i.e. ISO 9001:1994 and IOS/DIS 9000-3 6 Guidelines) 1

Models of Quality Attributes Quality Factors McCall et al. McCall, Richards and Walters (1976-77) Boëhm (1978) International Standards ISO, IEEE, DIN and military standards Correctness Integrity Usability Maintainability Testability Flexibility Portability Reusability Aspects of maintainability (Transferability) 7 8 Quality characteristics Since 1977 three important developments have influenced the set of characteristics. 1 European Council directive (1990) Minimum safety and health requirements for work with display screen equipment. 2 ISO 9001:1994 Quality systems - Model for assurance in design, development, production, installation and servicing. 9 10 Quality characteristics Extended to comply with European Council directive (1990) relating to display screen equipment and ISO/DIS 9000-3 (1996) 3 ISO/DIS 9000-3 (1996) Guidelines for the application of ISO 9001:1994 to the design, development, installation and maintenance of computer software. Safety Security is the new name for integrity Statutory obligations are introduced Safety Security Correctness Portability Testability Maintainability Re-usability 11 12 2

Quality characteristics See handout re: The external characteristics of a software product. See handout re: The internal characteristics of a software product. - The extent to which a program complies with the user community ethos, culture and/or mode of use. - The effort required to install a program and configure it to the user s requirements. 13 14 - The extent to which the feature set and the capabilities of a program satisfy the user s requirements. - The effort required to adapt the user interface to suit the user s preferences and mode of working. - The amount of human effort required to operate a program. - The ease with which new users can begin effective interaction and achieve maximal performance. 15 16 - The effort required to couple one system with another. - The extent to which a program can be expected to perform its intended function with required precision. Safety - The extent to which the software s safety-critical requirements are satisfied. Security (Integrity) - The extent to which access to software or data by unauthorised persons can be controlled. 17 18 3

Correctness - The extent to which a program satisfies its specifications and fulfils the user s mission objectives. - The amount of computing resources and code requited by a program to perform a function. Portability - The effort required to transfer a program from one hardware configuration and/or software system environment to another. Testability - The effort required to test a program to ensure it performs its intended function. 19 20 Interrelationships between characteristics Maintainability - The effort required to locate and fix an error in an operational program. (Adaptive, perfective & corrective) Re-usability - The extent to which a program can be used in another application - related to the packaging and scope of the applications that programs perform. Although all software characteristics are desirable there can be conflict between some of them. For example, Portability conflicts with efficiency. Portability and re-usability are concerned with solving problems that might not be directly related to the original requirements. 21 22 Interrelationships between characteristics - after Perry using McCall Examples to approaches to measuring.» Mean Time Between Failure (MTBF)» Mean Time To Recover» Mean Time To Rerepair (MTTR) Usability» Effectiveness, efficiency & satisfaction» Algorithm checking Correctness C _ R E Integrity I Usability _ U Maintainability _ M Testability T Flexibility _ F Portability P Re-usability R _ I 23 = Inverse blank = Neutral _ = Direct 24 4

% weighting assigned by user/evaluator. User/evaluator s subjective rating of this factor. e.g. 1-10 Measuring Weighting and Rating Grouping characteristics Safety Security Correctness Portability Testability Maintainability Re-usability Total 100% 25 External characteristics H-CI which impacts the end user. Internal characteristics Technical of interest to developers and maintenance staff. 26 Grouping characteristics MIS Triad Quality Perspective H-CI Safety Security Correctness Portability Testability Maintainability Re-usability Technical USER External BOARD Strategic Considerations IS Internal 27 28 Prioritising characteristics Conclusion There is a view that if you cannot install and launch a program then evaluation of all of the other characteristics are irrelevant. This gives rise to the concept of a priority scale among characteristics. 29 Building into software products Definition Models Characteristics Interrelationships Measuring Grouping Prioritising. 30 5