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



Similar documents
ISO/IEC JTC1/SC7 N4098

A Comparative Study of Software Quality Models

SOFTWARE QUALITY MODELS: A COMPARATIVE STUDY

Quality Management. Lecture 12 Software quality management

Lecture 8 About Quality and Quality Management Systems

Effective Test Management can help you to launch mobile payments faster, smarter and cheaper

Mike Peters Senior Test Consultant/Delivery Manager LogicaCMG All rights reserved

The Role of Information Technology Studies in Software Product Quality Improvement

Requirements engineering and quality attributes

ISO and Industry Standards for User Centred Design

Key Factors for Developing a Successful E-commerce Website

Evaluating the Quality of Software in ERP Systems Using the ISO 9126 Model

A Quality Model of e-government Services Based on the ISO/IEC 9126 Standard

Software Engineering Compiled By: Roshani Ghimire Page 1

ISO/IEC Software Product Quality Model

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

What do you think? Definitions of Quality

Multi-view Architecting

Scorecard and KPIs for monitoring software factories effectiveness in the financial sector

IEEE ComputerSociety 1 Software and Systems Engineering Vocabulary

ISO/IEC 27002:2013 WHITEPAPER. When Recognition Matters

Operational Acceptance Testing. White Paper. Business continuity assurance. December 2012

Quality in Use: Meeting User Needs for Quality

Quality in use: incorporating human factors into the software engineering lifecycle

Software Engineering: Analysis and Design - CSE3308

Defining the Quality of Business Processes

Characteristics of Computational Intelligence (Quantitative Approach)

Chapter 3 TOTAL QUALITY MANAGEMENT

Service Measurement Index Framework Version 2.1

A model for assessing the quality of e-commerce systems

International Software & Systems Engineering. Standards. Jim Moore The MITRE Corporation Chair, US TAG to ISO/IEC JTC1/SC7 James.W.Moore@ieee.

Extending Quality in Use to Provide a Framework for Usability Measurement

Darshan Institute of Engineering & Technology Unit : 7

Organizational Requirements Engineering

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

Lecture Softwareengineering-Vertiefung

SERV SER ICE DE SIGN

6 Cloud computing overview

SELECTION OF AN ORGANIZATION SPECIFIC ERP

An Approach for Enhance the Software Quality Based on Quality Model

Integrated Software Quality Evaluation: A Fuzzy Multi-Criteria Approach

QUALITY MODEL BASED ON COTS QUALITY ATTRIBUTES

Software Testing. Knowledge Base. Rajat Kumar Bal. Introduction

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

Evaluation of E-Learning Management Systems by Lecturers and Students in Ugandan Universities: A Case of Muni University

IEEE ComputerSociety 1 Software and Systems Engineering Vocabulary

Advantages of DBMS.

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

Quality Attributes in mobile Web Application Development

SECURITY INFRASTRUCTURE Standards and implementation practices for protecting the privacy and security of shared genomic and clinical data

CDC UNIFIED PROCESS JOB AID

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

Risks and Problems associated with a Telematic Approach for Log Downloads for EOBRs

Defining Quality Workbook. <Program/Project/Work Name> Quality Definition

Standard Glossary of Terms Used in Software Testing. Version 3.01

Causal Relationships between Improvements in Software Development Processes and Final Software Product Quality

Comparative Analysis of Different Software Quality Models

An Enterprise Framework for Evaluating and Improving Software Quality

CRISC Glossary. Scope Note: Risk: Can also refer to the verification of the correctness of a piece of data

Electronic business conditions of use

CHAPTER 20 TESING WEB APPLICATIONS. Overview

Preventive Approach for Web Applications Security Testing OWASP 10/30/2009. The OWASP Foundation

Software Quality Requirements and Evaluation, the ISO Series

Evaluation of the Iceland State Financial and Human Resource System

What Makes A Good Information Security Policy: A Preliminary Framework For Evaluating Security Policy Quality.

CHAPTER 11 COMPUTER SYSTEMS INFORMATION TECHNOLOGY SERVICES CONTROLS

FSW QA Testing Levels Definitions

OVERVIEW. In all, this report makes recommendations in 14 areas, such as. Page iii

Official Journal of RS, No. 86/2006 of REGULATION

HUMAN RESOURCES MANAGEMENT NETWORK (HRMN) SELF-SERVICE

CSC 408F/CSC2105F Lecture Notes

A Case Study of the Systems Engineering Process in Healthcare Informatics Quality Improvement. Systems Engineering. Ali M. Hodroj

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

Nuclear Safety Council Instruction number IS-19, of October 22 nd 2008, on the requirements of the nuclear facilities management system

Project Management Step Wise. Sunday, 4 November 12

Interim Threat / Risk Assessment. Student E- Communications Outsourcing Project

Levels of Software Testing. Functional Testing

Application of software product quality international standards through software development life cycle

UNIVERSIDAD POLITÉCNICA DE MADRID

SITA Security Requirements for Third-Party Service Providers that Access, Process, Store or Transmit Data on Behalf of SITA

ELECTRONIC SIGNATURES AND ASSOCIATED LEGISLATION

UF Risk IT Assessment Guidelines

Oracle Insurance Policy Administration System Quality Assurance Testing Methodology. An Oracle White Paper August 2008

Introduction to Software Engineering

Information Technology Engineers Examination. Network Specialist Examination. (Level 4) Syllabus. Details of Knowledge and Skills Required for

Dolby Software Maintenance and Extended Warranty Policy for Select Cinema Products Revised as of August 1, 2013

Information Security Policies and Procedures Development Framework for Government Agencies. First Edition AH

Do You Have The Right Practices In Your Cyber Supply Chain Tool Box? NDIA Systems Engineering Conference October 29, 2014

Chap 1. Software Quality Management

Evaluation of a MOODLE Based Learning Management System Applied at Berlin Institute of Technology Based on ISO-9126

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

How To Measure Quality

WEB SURVEY SYSTEM TO DISCOVER THE ACTUAL ROLE OF EXPERIENCE IN LEARNING IN HIGHER EDUCATION: A CASE STUDY

Measurement Information Model

TC Electronic Extended Warranty Policy

ARC VIEW. Stratus High-Availability Solutions Designed to Virtually Eliminate Downtime. Keywords. Summary. By Craig Resnick

Implementation of a Quality Management System for Aeronautical Information Services -1-

Success or Failure? Your Keys to Business Continuity Planning. An Ingenuity Whitepaper

Software Metrics and Measurements

SOFTWARE ASSET MANAGEMENT Continuous Monitoring. September 16, 2013

Transcription:

Evaluation of the Iceland State Financial and Human Resource System REPORT OF THE INDIVIDUAL EVALUATOR Annex 2 SYSTEM AND SOFTWARE QUALITY This paper lists the properties used in the two main models in the SQuaRE standards and their definitions. Properties marked with an * are included in the Terms of Reference (ToR) of the Evaluation. Quality in use model 1 Quality in use is the degree to which a product or system can be used by specific users to meet their needs to achieve specific goals with effectiveness, efficiency, freedom from risk and satisfaction in specific contexts of use. The properties of quality in use are categorized into five characteristics: effectiveness, efficiency, satisfaction, freedom from risk and context coverage. Effectiveness accuracy and completeness with which users achieve specified goals Efficiency resources expended in relation to the accuracy and completeness with which users achieve goals 1 ISO/IEC 25010 section 3 Rexed 130514 1(5)

Satisfaction degree to which user needs are satisfied when a product or system is used in a specified context of use - Usefulness degree to which a user is satisfied with their perceived achievement of pragmatic goals, including the results of use and the consequences of use - Trust degree to which a user or other stakeholder has confidence that a product or system will behave as intended - Pleasure degree to which a user obtains pleasure from fulfilling their personal needs - Comfort degree to which the user is satisfied with physical comfort Freedom from risk degree to which a product or system mitigates the potential risk to economic status, human life, health, or the environment - Economic risk mitigation degree to which a product or system mitigates the potential risk to financial status, efficient operation, commercial property, reputation or other resources in the intended contexts of use - Health and safety risk mitigation degree to which a product or system mitigates the potential risk to people in the intended contexts of use - Environmental risk mitigation degree to which a product or system mitigates the potential risk to property or the environment in the intended contexts of use Context coverage degree to which a product or system can be used with effectiveness, efficiency, freedom from risk and satisfaction in both specified contexts of use and in contexts beyond those initially explicitly identified - Context completeness degree to which a product or system can be used with effectiveness, efficiency, freedom from risk and satisfaction in all the specified contexts of use - Flexibility degree to which a product or system can be used with effectiveness, efficiency, freedom from risk and satisfaction in contexts beyond those initially specified in the requirements Product quality model 2 The product quality model categorizes product quality properties into eight characteristics (functional suitability, reliability, performance efficiency, usability, security, compatibility, maintainability and portability). Each characteristic is composed of a set of related subcharacteristics Functional suitability* degree to which a product or system provides functions that meet stated and implied needs when used under specified conditions - Functional completeness* degree to which the set of functions covers all the specified tasks and user objectives 2 ISO/IEC 25010 section 4 Rexed 130514 2(5)

- Functional correctness* degree to which a product or system provides the correct results with the needed degree of precision - Functional appropriateness* degree to which the functions facilitate the accomplishment of specified tasks and objectives Performance efficiency performance relative to the amount of resources used under stated conditions - Time behaviour degree to which the response and processing times and throughput rates of a product or system, when performing its functions, meet requirements - Resource utilization degree to which the amounts and types of resources used by a product or system, when performing its functions, meet requirements - Capacity degree to which the maximum limits of a product or system parameter meet requirements Compatibility Co-existence Interoperability degree to which a product, system or component can exchange information with other products, systems or components, and/or perform its required functions, while sharing the same hardware or software environment degree to which a product can perform its required functions efficiently while sharing a common environment and resources with other products, without detrimental impact on any other product degree to which two or more systems, products or components can exchange information and use the information that has been exchanged Usability* Appropriateness recognizability Learnability Operability* User error protection* User interface aesthetics Accessibility degree to which a product or system can be used by specified users to achieve specified goals with effectiveness, efficiency and satisfaction in a specified context of use degree to which users can recognize whether a product or system is appropriate for their needs cf. functional appropriateness degree to which a product or system can be used by specified users to achieve specified goals of learning to use the product or system with effectiveness, efficiency, freedom from risk and satisfaction in a specified context of use degree to which a product or system has attributes that make it easy to operate and control degree to which a system protects users against making errors degree to which a user interface enables pleasing and satisfying interaction for the user degree to which a product or system can be used by people with the widest range of characteristics and capabilities to achieve a specified goal in a specified context of use Rexed 130514 3(5)

Reliability* Maturity* Availability* Fault tolerance* Recoverability* degree to which a system, product or component performs specified functions under specified conditions for a specified period of time degree to which a system, product or component meets needs for reliability under normal operation degree to which a system, product or component is operational and accessible when required for use degree to which a system, product or component operates as intended despite the presence of hardware or software faults degree to which, in the event of an interruption or a failure, a product or system can recover the data directly affected and reestablish the desired state of the system Security* Confidentiality* Integrity* Non-repudiation* Accountability* Authenticity* degree to which a product or system protects information and data so that persons or other products or systems have the degree of data access appropriate to their types and levels of authorization Survivability (the degree to which a product or system continues to fulfil its mission by providing essential services in a timely manner in spite of the presence of attacks) is covered by recoverability Immunity (the degree to which a product or system is resistant to attack) is covered by integrity degree to which a product or system ensures that data are accessible only to those authorized to have access degree to which a system, product or component prevents unauthorized access to, or modification of computer programs or data degree to which actions or events can be proven to have taken place, so that the events or actions cannot be repudiated later degree to which the actions of an entity can be traced uniquely to the entity degree to which the identity of a subject or resource can be proved to be the one claimed Maintainability Modularity Reusability Analysability degree of effectiveness and efficiency with which a product or system can be modified by the intended maintainers Maintainability includes installation of updates and upgrades. degree to which a system or computer program is composed of discrete components such that a change to one component has minimal impact on other components degree to which an asset can be used in more than one system, or in building other assets degree of effectiveness and efficiency with which it is possible to assess the impact on a product or system of an intended change to Rexed 130514 4(5)

Modifiability Testability one or more of its parts, or to diagnose a product for deficiencies or causes of failures, or to identify parts to be modified degree to which a product or system can be effectively and efficiently modified without introducing defects or degrading existing product quality degree of effectiveness and efficiency with which test criteria can be established for a system, product or component and tests can be performed to determine whether those criteria have been met Portability Adaptability* Installability Replaceability degree of effectiveness and efficiency with which a system, product or component can be transferred from one hardware, software or other operational or usage environment to another degree to which a product or system can effectively and efficiently be adapted for different or evolving hardware, software or other operational or usage environments degree of effectiveness and efficiency with which a product or system can be successfully installed and/or uninstalled in a specified environment degree to which a product can replace another specified software product for the same purpose in the same environment Rexed 130514 5(5)