DOCSLIB.ORG

Appendix A: Quality Models and Verification Methods

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Appendix A: Quality Models and Verification Methods Appendix A: Quality Models and Verification Methods As indicated in previous chapters, we have excluded discussions on the various verification methods which still exist in many publications. The following table may be useful in researching appropriate methods to deal with the different artefacts in the product lifecycle. We do not claim completeness in the methods but have provided common verification methods which we apply in our projects. Artefact type Quality model Verification methods Documentation DocQMod • Peer Review • Structured Group Review • Inspection • Walk Through • Technical Review • Informal Review Business BPQMod • Peer Review processes • Structured Group Review • Formal Inspection (on business process models, e.g. swimlanes, business and application process models) • Walk Through • GUI Prototyping • Test Modelling (based on business processes) • Early Test Case Design • Usability Testing Requirements ReqQMod • Management Review • Peer Review • Structured Group Review • Audit • Inspection • Walk Through • Technical Review • Informal review • GUI Prototyping • Test Modelling (based on requirements) • Test Case Specification (based on requirements) (continued) M. Wieczorek et al., Systems and Software Quality, 165 DOI 10.1007/978-3-642-39971-8, © Springer-Verlag Berlin Heidelberg 2014 166 Appendix A: Quality Models and Verification Methods Artefact type Quality model Verification methods Architecture ArchQMod • Peer Review • Structured Group Review • Formal Inspection • ATAM • Prototyping (including functional and non-functional testing) • FMEA Database DataQMod • Formal Inspection (on e.g. normalisation) • Peer Review (on indexing, SQL statements, stored procedures) • Structured Group Review • Functional Testing (by application) • Non-functional testing (including performance and security) Source code CodeQMod • Peer Review • Walk Through • Formal Inspection (e.g. style guides, coding standards) • Static Source Code Analysis (tool based) • Profiling (e.g. memory leaks) • Functional and Non-Functional dynamic testing • Condition Testing • Branch Testing • LCSAJ Testing (Parts of) SysQMod • Business Process Testing application or • End-to-End Testing system • Functional Testing • Non-Functional Testing (e.g. reliability, performance, security, and usability testing) • Structure-based Testing • Specification-based Testing • Testing using Decision Tables • Testing using State Transition Diagrams • Testing using Equivalence Partitioning • Boundary Value Analysis • Cause-Effect Graphing • Combinatorial Testing • Use Case Testing • User Story Testing • Domain Analysis • Explorative Testing • Crowd Testing • Manual / Automated Testing Environment EnvQMod • Peer Review • Structured Group Review • Formal Inspection • ATAM • Prototyping (including functional and non-functional testing) • FMEA • Monitoring • In-Process Reviews (continued) Appendix A: Quality Models and Verification Methods 167 Artefact type Quality model Verification methods Long-term DigPresQMod • Inspection archive • Peer Review • Recoverability Testing • Regression Testing • Inspections by Samples • Spot Test Appendix B: Relevant International Standards All standards, quasi-standards or industry-specific standards like DO 178C, AQAP or CMMI are mostly derived from national or international standards developed by various national and international standardisation bodies. In the table below we have limited our scope to the international standards that are relevant for the purposes of this book and focus on quality governance, quality management and quality engineering. If there is a standard that does not apply by country, there should be a relatively close conversion within that country. Reference number Title IEC 31010: 2009 Risk management—Risk assessment techniques IEEE STD 1028: 2008 IEEE Standard for Software Reviews and Audits ISO 9000: 2005 Quality management systems—Fundamentals and vocabulary ISO 9001: 2008 Quality management systems—Requirements ISO 9004: 2009 Managing for the sustained success of an organization—A quality man- agement approach ISO 10001: 2007 Quality management—Customer satisfaction—Guidelines for codes of conduct for organizations ISO 10002: 2009 Quality management—Customer satisfaction—Guidelines for complaints handling in organizations ISO 10003: 2007 Quality management—Customer satisfaction—Guidelines for dispute resolution external to organizations ISO 10005: 2005 Quality management systems—Guidelines for quality plans ISO 10005: 2005 Quality management systems—Guidelines for quality plans ISO 10006: 2003 Quality management systems—Guidelines for quality management in projects ISO 10007: 2003 Quality management systems—Guidelines for configuration management ISO 10012: 2003 Measurement management systems—Requirements for measurement processes and measuring equipment ISO/TR 10013: 2001 Guidelines for quality management system documentation ISO 10014: 2007 Quality management—Guidelines for realizing financial and economic benefits ISO 10014: 2006 Quality management—Guidelines for realizing financial and economic benefits (continued) M. Wieczorek et al., Systems and Software Quality, 169 DOI 10.1007/978-3-642-39971-8, © Springer-Verlag Berlin Heidelberg 2014 170 Appendix B: Relevant International Standards Reference number Title ISO 10015: 1999 Quality management—Guidelines for training ISO 10018: 2012 Quality management—Guidelines on people involvement and competence ISO 10019: 2005 Guidelines for the selection of quality management system consultants and use of their service ISO 19011: 2012 Guidelines for auditing management systems ISO 26262-1: 2011 Road vehicles—Functional safety—Vocabulary ISO 26262-2: 2011 Road vehicles—Functional safety—Management of functional safety ISO 26262-3: 2011 Road vehicles—Functional safety—Concept phase ISO 26262-4: 2011 Road vehicles—Functional safety—Product development at the system level ISO 26262-5: 2011 Road vehicles—Functional safety—Product development at the hardware level ISO 26262-6: 2011 Road vehicles—Functional safety—Product development at the software level ISO 26262-7: 2011 Road vehicles—Functional safety—Production and operation ISO 26262-8: 2011 Road vehicles—Functional safety—Supporting processes ISO 26262-9: 2011 Road vehicles—Functional safety—Automotive Safety Integrity Level (ASIL)oriented and safety-oriented analyses ISO 26262-10: 2012 Road vehicles—Functional safety—Guideline on ISO 26262 ISO 31000: 2009 Risk management—Principles and guidelines ISO/IEC 12207: 2008 Systems and software engineering—Software life cycle processes ISO/IEC 15288: 2008 Systems and software engineering—System life cycle processes ISO/IEC 15504-1: Information technology—Process assessment—Part 1: Concepts and 2004 vocabulary ISO/IEC 15504-2: Information technology—Process assessment—Part 2: Performing an 2003 assessment ISO/IEC 15504-3: Information technology—Process assessment—Part 3: Guidance on 2004 performing an assessment ISO/IEC 15504-4: Information technology—Process assessment—Part 4: Guidance on use 2004 for process improvement and process capability determination ISO/IEC 15504-5: Information technology—Process assessment—An exemplar software 2012 life cycle process assessment model ISO/IEC 15504-7: Information technology—Process assessment—Part 7: Assessment of 2008 organizational maturity ISO/IEC 15504-9: Information technology—Process assessment—Part 9: Target process 2011 profiles ISO/IEC 15504-10: Information technology—Process assessment—Part 10: Safety extension 2011 ISO/IEC 16085: 2006 Systems and software engineering—Life cycle processes—Risk management ISO/IEC 20000-1: Information technology—Service management—Part 1: Service man- 2011 agement system requirements ISO/IEC 20000-2: Information technology—Service management—Part 2: Guidance on the 2012 application of service management systems ISO/IEC 25010: 2011 Systems and Software-Engineering—Systems and software Quality Requirements and Evaluation (SQuaRE)—System and software quality models (continued) Appendix B: Relevant International Standards 171 Reference number Title ISO/IEC 25012: 2008 Software-Engineering—Software product Quality Requirements and Evaluation (SQuaRE)—Data quality model ISO/IEC 25020: 2007 Software-Engineering—Software product Quality Requirements and Evaluation (SQuaRE)—Measurement reference model and guide ISO/IEC 25021: 2012 Systems and Software-Engineering—Systems and software Quality Requirements and Evaluation (SQuaRE)—Quality measure elements ISO/IEC 25030: 2007 Software-Engineering—Software product Quality Requirements and Evaluation (SQuaRE)—Quality requirements ISO/IEC 25040: 2011 Systems and Software-Engineering—Systems and software Quality Requirements and Evaluation (SQuaRE)—Evaluation process ISO/IEC 25041: 2012 Systems and Software-Engineering—Systems and software Quality Requirements and Evaluation (SQuaRE)—Evaluation guide for developers, acquirers and independent evaluators ISO/IEC 27001: 2013 Information technology—Security techniques—Information security management systems—Requirements ISO/IEC 90003: 2004 Software engineering—Guidelines for the application of ISO 9001 to computer software ISO/IEC FDIS 25000: Systems and Software-Engineering—Systems and software Quality 2013 Requirements and Evaluation (SQuaRE)—Guide to SQuaRE ISO/IEC FDIS 25001: Systems and Software-Engineering—Systems and software Quality 2013 Requirements and Evaluation (SQuaRE)—Planning and management ISO/IEC/IEEE 29119- Software and Systems-Engineering—Software-Testing—Concepts and 1: 2013 definitions ISO/IEC/IEEE 29119-
Load more

Recommended publications
  • AS ISO 10006-2003 Quality Management Systems-Guidelines for Quality Management in Projects
    AS ISO 10006—2003 ISO 10006:2003 AS ISO 10006 Australian Standard™ Quality management systems— Guidelines for quality management in projects This is a free 7 page sample. Access the full version online. This Australian Standard was prepared by Committee QR-008, Quality Systems. It was approved on behalf of the Council of Standards Australia on 3 September 2003 and published on 10 November 2003. The following are represented on Committee QR-008: Australian Chamber of Commerce and Industry Australian Industry Group Australian Information Industry Association Australian Organisation for Quality Bureau of Steel Manufacturers of Australia Certification Bodies (Australia) Department of Agriculture, Fisheries and Forestry (Commonwealth) Department of Defence (Australia) Department of Industry Science and Resources (Commonwealth) Institution of Engineers Australia Main Roads Department, Queensland Master Builders Australia Quality Society of Australasia Royal Australian Chemical Institute Keeping Standards up-to-date Standards are living documents which reflect progress in science, technology and systems. To maintain their currency, all Standards are periodically reviewed, and This is a free 7 page sample. Access the full version online. new editions are published. Between editions, amendments may be issued. Standards may also be withdrawn. It is important that readers assure themselves they are using a current Standard, which should include any amendments which may have been published since the Standard was purchased. Detailed information about Standards can be found by visiting the Standards Australia web site at www.standards.com.au and looking up the relevant Standard in the on-line catalogue. Alternatively, the printed Catalogue provides information current at 1 January each year, and the monthly magazine, The Global Standard, has a full listing of revisions and amendments published each month.
    [Show full text]
  • Quality Management ISO Audit & Performance Systems Instructor: Jurandir Primo, PE
    PDHonline Course M482 (5 PDH) -------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Quality Management ISO Audit & Performance Systems Instructor: Jurandir Primo, PE 2012 PDH Online | PDH Center 5272 Meadow Estates Drive Fairfax, VA 22030-6658 Phone & Fax: 703-988-0088 www.PDHonline.org www.PDHcenter.com An Approved Continuing Education Provider www.PDHcenter.com PDH Course M482 www.PDHonline.org Contents: I. BASIC QUALITY CONCEPTS V. PERFORMANCE SYSTEMS 1. Total Quality Management (TQM) 1. Six Sigma 1.1. Total Quality Management Evolution 2. The Five W´s and One H 2. Quality Management System (QMS) 2.1. Five W´s and One H Applied to Six Sigma 2.1. TQM and QMS Relationship 3. Ishikawa Diagrams 2.2. Quality Gurus Main Contribution 4. The 6 M´s Used by Toyota 2.3. The Plan-Do-Study-Act Cycles (PDSA) 5. Control Charts 2.4. TQM Failures 5.1. Control Charts Definition 3. Quality Assurance (QA) 6. Failure Mode and Effect Analysis (FMEA) 3.1. Components of QA Program 6.1. Critical Analysis - FMECA 4. Quality Control in Civil Construction 6.2. FMEA Terminology 4.1. Quality in Electrical Services 7. Risk Levels 4.2. Civil, Mechanical and Electrical Relations 8. Statistical Quality Control (SQC) 8.1. The Mean II. ISO 9000 BASIC STANDARDS 9. Histograms 10. Pareto Analysis 1. ISO Quality Management Systems 11. Root Cause Analysis (RCA) 1.1. ISO 9000 Latest Revision 12. 5S – Work Area Organization 1.2. ISO 9000 Audit 13. Design of Experiments (DOE) 1.3. Non-conformance Report 14. Quality Function Deployment (QFD) 15. Production Planning and Control (PPC) III. ISO 10000 MAIN GUIDELINES SERIES 15.1.
    [Show full text]
  • International Standards, Approaches and Frameworks Relevant to Software Quality Management and Software Process Improvement
    International standards, approaches and frameworks relevant to Software Quality Management and Software Process Improvement To help organizations managing software quality and improving software processes several standards, models, approaches and frameworks have been developed during the last decades. The most widely known and recognized of them are presented in this document. • Capability Maturity Model (CMM) • CMM Integration (CMMI) • Personal Software Process (PSP) and Team Software Process (TSP) • ISO 9000 standards family • TickIT • ISO/IEC TR 15504 Information Technology - Software Process Assessment (SPICE) • ISO/IEC 12207 Information Technology - Software Life-Cycle Processes • BOOSTRAP • Rational Unified Process CMM Publication Date: Version 1.1 - February 1993 Description: The Capability Maturity Model for Software (SW-CMM or CMM) is a model used by organizations for appraising the maturity of their software processes and for identifying practices that will increase the maturity of those processes. It was developed by the Software Engineering Institute, in cooperation with industry representatives. The Software CMM has become a de facto standard for assessing and improving software processes. Through the SW-CMM, the SEI and community have put in place an effective means for modeling, defining, and measuring the maturity of the processes used by software professionals. The Capability Maturity Model for Software describes the principles and practices underlying software process maturity and is intended to help software organizations
    [Show full text]
  • A Stone Man Version
    Guide to the Software Engineering Body of Knowledge AA SSttoonnee MMaann Veerrssiioonn (Version 0.7) April 2000 A project of the Software Engineering Coordinating Committee (Joint IEEE Computer Society - ACM committee ) Corporate support by: Project managed by: Executive Editors: Alain Abran, Université du Québec à Montréal James W. Moore, The MITRE Corp. Editors: Pierre Bourque, Université du Québec à Montréal Robert Dupuis, Université du Québec à Montréal Chair of the Software Engineering Coordinating Committee Leonard L. Tripp, IEEE Computer Society Copyright © 2000, Institute of Electrical and Electronics Engineers, Inc. All rights reserved. PREFACE TO THE SWEBOK GUIDE 1. Software engineering is an emerging discipline but there are unmistakable trends indicating an 10. Purpose increasing level of maturity: 11. The purpose of this Guide is to provide a 2. w McMaster University (Canada), the consensually-validated characterization of the Rochester Institute of Technology (US), the bounds of the software engineering discipline University of Sheffield (UK), the and to provide a topical access to the Body of University of New South Wales (Australia) Knowledge supporting that discipline. The Body and other universities around the world now of Knowledge is subdivided into ten Knowledge offer undergraduate degrees in software Areas (KA) and the descriptions of the KAs are engineering. designed to discriminate among the various important concepts, permitting readers to find 3. w The Software Capability Maturity Model and ISO 9000 are used to certify their way quickly to subjects of interest. Upon organizational capability for software finding a subject, readers are referred to key engineering. papers or book chapters selected because they succinctly present the knowledge.
    [Show full text]
  • Guide to the Software Engineering Body of Knowledge
    Guide to the Software Engineering Body of Knowledge AA SSttoonnee MMaann VVeerrssiioonn (Version 0.5) October 1999 A project of the Software Engineering Coordinating Committee (Joint IEEE Computer Society - ACM committee ) Corporate support by: Project managed by: Co-Executive Editors: Alain Abran, Université du Québec à Montréal James W. Moore, The MITRE Corp. Editors: Pierre Bourque, Université du Québec à Montréal Robert Dupuis, Université du Québec à Montréal Project Champion: Leonard L. Tripp, IEEE Computer Society Table of Contents INTRODUCTORY TEXT FROM THE EDITORIAL TEAM KNOWLEDGE AREA DESCRIPTION : - Software Configuration Management - Software Construction - Software Design - Software Engineering Infrastructure - Software Engineering Management - Software Engineering Process - Software Evolution and Maintenance - Software Quality Analysis - Software Requirement Analysis - Software Testing APPENDIX A KNOWLEDGE AREA DESCRIPTION SPECIFICATIONS FOR THE STONE MAN VERSION OF THE GUIDE TO THE SOFTWARE ENGINEERING BODY OF KNOWLEDGE – VERSION 0.25 INTRODUCTORY TEXT FROM THE EDITORIAL TEAM The IEEE Computer Society and the Association for Computing Machinery are working on a joint project to develop a guide to the Software Engineering Body Of Knowledge (SWEBOK). This is the current draft (version 0.5 completed in September 1999) of the Stoneman version of the Guide1. Articulating a body of knowledge is an essential step toward developing a profession because it represents a broad consensus regarding the contents of the discipline. Without such a consensus, there is no way to validate a licensing examination, set a curriculum to prepare individuals for the examination, or formulate criteria for accrediting the curriculum. The project team is currently working on an update to this draft version of the Guide based on the results of the second review cycle.
    [Show full text]
  • Voluntary Voting System Guidelines VVSG 2.0 Recommendations for Requirements for the Voluntary Voting System Guidelines 2.0
    Voluntary Voting System Guidelines VVSG 2.0 Recommendations for Requirements for the Voluntary Voting System Guidelines 2.0 February 29, 202010, 2021 Prepared for the Election Assistance Commission At the direction of the Technical Guidelines Development Committee 1 Acknowledgements Chair of the TGDC: Dr. Walter G. Copan Director of the National Institute of Standards and Technology (NIST) Gaithersburg, MD Representing the EAC Standards Board: Robert Giles Paul Lux Director Supervisor of Elections New Jersey Division of Elections Okaloosa County Trenton, NJ Crestview, FL Representing the EAC Board of Advisors: Neal Kelley Linda Lamone Registrar of Voters Administrator of Elections Orange County Maryland State Board of Orange County, CA ElectionElections Annapolis, MD Representing the Architectural and Transportation Barrier, and Compliance Board (Access Board): Marc Guthrie Sachin Pavithran Public Board Member Public Board Member Newark, OH Logan, UT Representing the American National Standards Institute (ANSI): Mary Saunders Vice President, Government Relations & Public Policy American National Standards Institute Washington, DC Representing the Institute of Electrical and Electronics Engineers: Dan Wallach Professor, Electrical & Engineering Computer Science Rice University Houston, TX Representing the National Association of State Election Directors (NASED): Lori Augino Judd Choate Washington State Director of Elections State Elections Director Washington Secretary of State Colorado Secretary of State Olympia, WA Denver, CO 2 Requirements
    [Show full text]
  • Innovations Well Done 20 Years of Innovations
    INNOVATIONS WELL DONE 20 YEARS OF INNOVATIONS CELEBRATE CHECK OUT OUR 20TH ANNIVERSARY CAMPAIGN CONTENT 05 33 55 79 EDITORIAL INTERVIEW PORTFOLIO SOCIAL WITH CSMO RESPONSIBILITY 07 35 67 85 COMPANY PROFILE SERVICES INNOVATIONS HUMAN RESOURCES 09 37 71 87 WHY US? CUSTOM SOFTWARE INTEGRATED ENVIRONMENT SOLUTIONS MANAGEMENT SYSTEM Page Page 3 13 39 73 89 4 Page Page MANAGEMENT MOBILE AND WEB PARTNERSHIPS & FINANCE APPLICATIONS MEMBERSHIPS 25 41 75 93 TIMELINE NEARSHORE TECHNOLOGIES SECURITY OUTSOURCING 29 45 76 95 INTERVIEW REFERENCES SCIENCE AND CONTACT WITH COO RESEARCH 31 53 77 INTERVIEW CLIENTS MARKETING WITH CTO EDITORIAL “2019 WAS A VERY SUCCESSFUL YEAR FOR QBSW, THAT IS WHY WE ENTERED THE NEW YEAR 2019 was a very successful year for implementing online communication During the year, we managed to acquire QBSW. We reached record turnover, with our clients and partners. several new customers—one from Austria we had a large number of contracted Thankfully, we were already familiar with and others from the Slovak banking WITH EQUALLY projects, and our number of employees communicating online with our foreign and finance sector. We have launched was the highest in company history. clients, and we already had systems a marketing campaign aimed at foreign Page 5 OPTIMISTIC We entered the new year with equally in place for remote communication markets, and we are also communicating 6 Page Page optimistic expectations. It was a perfect within teams (as three of our teams are intensively with chambers of commerce year to celebrate QBSW’s twentieth located outside of Bratislava). and other partners while searching for EXPECTATIONS ” anniversary.
    [Show full text]
  • Comparative Analysis of the ISO 10006:2003 Against Other Standards and Guidelines Related to Software Project Management
    Comparative Analysis of the ISO 10006:2003 against other Standards and Guidelines related to Software Project Management Brenda L. Flores-Rios1, Oscar M. Rodríguez-Elias2, Martín Olguín-Espinoza1 1Universidad Autónoma de Baja California, 2Instituto Tecnológico de Hermosillo 1{bflores | molguin}@uabc.mx, [email protected] Abstract. Nowadays, the Project Management field is in a stage in which its processes and concepts are being normalized and harmonized. The standard ISO 10006:2003 is an example of it. The goal of this standard is to provide an orientation about the concepts, elements, and guidelines for the quality of Project Management practices through eleven processes. This paper presents a comparison of the processes defined in the ISO 10006 with those defined in the PMBOK of PMI, ICB of IPMA, SWEBOK and the Mexican Standard NMX-I- 059-NYCE-2005. The purpose of this work is to describe a conceptual framework to be taken into account in project management initiatives for software processes, which can be used by software project managers. 1 Introduction The need of having highly motivated and prepared personnel in software development processes has been discussed since the sixties [1]. Today, despite that the software industry considers itself as a solid industry, and although most of the software projects are developed by highly specialized people, surprisingly, this is an industry characterized by not having highly quality products and services [2]. Software quality implies the necessity of accomplishing some parameters to allow establish the minimal levels by which a product can be considered a quality product [3]. Reports and statistical analysis have been performed to determine the status of software projects, for instance the project European Software Process Improvement Training Initiative (ESPITI), and Extreme Chaos of the Standish Group.
    [Show full text]
  • Appendix G Systems General Requirements
    BROADWAY SUBWAY PROJECT Commercial in Confidence PROJECT AGREEMENT EXECUTION COPY SCHEDULE 4 Appendix G Systems General Requirements BROADWAY SUBWAY PROJECT Commercial in Confidence PROJECT AGREEMENT EXECUTION COPY SCHEDULE 4: APPENDIX G: SYSTEM GENERAL REQUIREMENTS - 2 - Table of Contents 1 APPENDIX G – Systems GENERAL REQUIREMENTS .................................................................. 7 1.1 Introduction .......................................................................................................................................... 7 1.2 Requirements Delivery ........................................................................................................................ 7 1.3 Standards .............................................................................................................................................. 8 1.4 Systems Plan ........................................................................................................................................ 8 1.5 Design Life of the Systems .................................................................................................................. 9 1.6 Systems Design Management .............................................................................................................. 9 1.6.1 Requirements Specification Overview ............................................................................................ 10 1.6.2 Requirements Analysis Overview ..................................................................................................
    [Show full text]
  • The Evolution of Software Configuration Management
    ISSN 2278-3091 Syahrul Fahmy et al., International Journal of AdvancedVolume Trends 9, No.1. in Computer3, 2020 Science and Engineering, 9(1.3), 2020, 50 - 63 International Journal of Advanced Trends in Computer Science and Engineering Available Online at http://www.warse.org/IJATCSE/static/pdf/file/ijatcse0891.32020.pdf https://doi.org/10.30534/ijatcse/2020/0891.32020 The Evolution of Software Configuration Management 1 2 3 1 1 Syahrul Fahmy , Aziz Deraman , Jamaiah Yahaya , Akhyari Nasir , Nooraida Shamsudin 1University CollegeTATI, Malaysia, [email protected] 2Universiti Malaysia Terengganu, Malaysia 3Universiti Kebangsaan Malaysia, Malaysia processing and implementation status, and verify compliance ABSTRACT with specified requirements” [3]. Software Configuration Management (SCM) is a discipline in “a management activity that applies technical and software engineering for managing changes to software administrative direction over the life cycle of a product, its products using standard processes and tools. This article configuration items, and related product configuration presents the evolution of SCM since its inception, information. It provides identification and traceability, the highlighting the components, application to other areas, status of achievement, and access to accurate information in change management and software quality. Research and all phases of the life cycle” [4]. development in SCM are highly motivated by the problems at hand in software development. SCM process and activities are This paper presents the evolution of SCM, discussing its sound, guided by international standards and industry best components, application to other areas, change management practice. Commercial and proprietary tools are aplenty, and and software quality. the underlying techniques are no longer confined to SCM.
    [Show full text]
  • Manual on the Quality Management System for Aeronautical Information Services ______
    Doc 9839 AN/xxx Manual on the Quality Management System for Aeronautical Information Services ________________________________ Approved by the Secretary General and published under his authority First Edition — XXXX International Civil Aviation Organization Published in English, .................... by the INTERNATIONAL CIVIL AVIATION ORGANIZATION 999 University Street, Montréal, Quebec, Canada H3C 5H7 For ordering information and for a complete listing of sales agents and booksellers, please go to the ICAO website at www.icao.int Doc 9839, Manual on the Quality Management System for Aeronautical Information Services Order Number: ISBN © ICAO 2010 All rights reserved. No part of this publication may be reproduced, stored in a retrieval system or transmitted in any form or by any means, without prior permission in writing from the International Civil Aviation Organization. AMENDMENTS Amendments are announced in the supplements to the Catalogue of ICAO Publications; the Catalogue and its supplements are available on the ICAO website at www.icao.int. The space below is provided to keep a record of such amendments. RECORD OF AMENDMENTS AND CORRIGENDA AMENDMENTS CORRIGENDA No. Date Entered by No. Date Entered by TABLE OF CONTENTS Page Foreword .......................................................................................................................................................... (vii) Acronyms ........................................................................................................................................................
    [Show full text]
  • Squbok Review 2020 発行にあたって
    ISSN 2432-342X(Online) ISSN 2432-3411(Print) SQuBOK S oftw a r e Qua lit y Body of Kno wle dge Review 2020 Vol.5 SQuBOK Review 2020 2020年9月10日 発行 編集：SQuBOK策定部会 発行：一般財団法人日本科学技術連盟 〒166-0003 東京都杉並区高円寺南1-2-1 TEL.03-5378-9813 FAX.03-5378-9842 https://www.juse.or.jp/sqip/ © Union of Japanese Scientists and Engineers（JUSE） 本資料からの転載及び複製を禁止いたします NPC-202010 SQuBOK 策定部会［編］ 15807907 SQuBOK Review2020_表1-4.indd 全ページ 2020/09/01 14:42 2mm ・SQuBOK®は一般財団法人日本科学技術連盟の登録商標です． ・SQuBOK®は SQuBOK®策定部会の著作物であり，SQuBOK®にかかる著作権，その他の権利は 一般財団法人日本科学技術連盟および各権利者に帰属します． ・本文中では®は明記していません． 15807865 SQuBOK 表2-3.indd すべてのページ 2020/08/31 14:39 SQuBOK Review 2020 発行にあたって ソフトウェア品質知識体系ガイド（SQuBOK）は，ソフトウェア品質に関する知識を整理・体系 化し，それらに容易にアクセスできるようにするためのガイドである．2007 年 12 月に発行した 第１版は，ソフトウェアの品質を確保するための基盤知識を整理した．2014 年 11 月に発行した 第 2 版では，要求分析，設計，実装といった開発に関する品質技術と，専門的品質特性のソフト ウェア品質技術という副カテゴリを追加した．そして今秋，普遍的な品質に対する考え方ととも にソフトウェア品質に関する最新のテーマを整理し体系化した第 3 版を発行する． SQuBOK Review は，SQuBOK のコンテンツを拡充させることを目的に発足した SQuBOK 研究チーム の成果を発信するものである．2016 年より毎年発行しており，次の内容をレポートしている． 2016 年： ・アジャイル品質保証の動向 ・日本におけるソフトウェアプロセス改善の歴史的意義と今後の展開 ・SQuBOK ガイド V2 参照規格の改廃追加の状況 2017 年： ・レビュー技術動向 ・現場におけるソフトウェアテストの取り組み ・SQuBOK ガイド V2 参照規格の改廃追加の状況 2018 年： ・AI システムの品質保証の動向 ・IoT システムの品質保証の動向 ・SQuBOK ガイド V2 参照規格の改廃追加の状況 2019 年： ・IoT システムの開発と調達における品質保証の考え方 ・SQuBOK ガイド V2 参照規格の改廃追加の状況 今回は，2018 年から継続している「IoT システム」研究シリーズの第 3 弾として，「IoT サービ スのセキュリティと安全性の確保」を掲載する．IoT 関連のガイド類は多数発行されており，ま だ増えている状況である．そこで，ガイド類がカバーしきれていないところや不十分なところが ないかを確認するために，代表的なガイド類について分類・マッピングを行った．その結果と考 察を報告するものである．毎回掲載している「参照規格の改廃追加の状況」では，世の中の動き や変化の波を，読者の皆さまと共有したい． 2020 年
    [Show full text]