Australian Standard. Standard metamodel for software development methodologies AS 4651 2004 AS 4651 2004



Similar documents
Australian/New Zealand Standard

Australian Standard. Quality management systems Guidelines for configuration management AS ISO ISO 10007:2003 AS ISO 10007

Australian/New Zealand Standard

Australian Standard. Emergency control organization and procedures for buildings, structures and workplaces AS

Australian Standard. Guidelines for quality management system documentation AS ISO ISO/TR 10013:2001 AS ISO 10013

This is a free 9 page sample. Access the full version online. AS/NZS ISO 31000:2009 Risk management Principles and guidelines

Australian Standard. Bridge design. Part 1: Scope and general principles AS AP-G15.1/04 AS

AS/NZS 4801:2001. Occupational health and safety management systems. Specification with guidance for use. Australian/New Zealand Standard

Australian/New Zealand Standard

This is a free 9 page sample. Access the full version online. AS/NZS ISO 31000:2009 Risk management Principles and guidelines

AS AS Australian Standard. Emergency eyewash and shower equipment. This is a free 6 page sample. Access the full version online.

AS/NZS ISO 9001:2008 Quality management systems Requirements (Incorporating Amendment No. 1)

Australian Standard. Guidance on statistical techniques for ISO 9001:2000 (ISO/TR 10017, Ed. 2.0 (2003) MOD) AS ISO AS ISO

Australian Standard. Information technology Service management. Part 2: Guidance on the application of service management systems

Software configuration management plans

Australian Standard. Interactive voice response systems user interface Speech recognition AS AS

Australian/New Zealand Standard

Best Practice Board Reporting

Australian Standard. Customer satisfaction Guidelines for complaints handling in organizations (ISO 10002:2004, MOD) AS ISO

Australian/New Zealand Standard

Australian Standard. Intruder alarm systems. Part 1: Systems installed in client s premises AS

Australian/New Zealand Standard

AS AS Australian Standard. Health Care Client Identification. This is a free 8 page sample. Access the full version online.

Australian/New Zealand Standard

Australian/New Zealand Standard

Australian/New Zealand Standard

Australian Standard. General conditions of contract for design and construct. AS (Incorporating Amendment No. 1)

Australian/New Zealand Standard

Australian Standard. Intruder alarm systems. Part 4: Wire-free systems installed in client s premises AS

HB A Practitioners Guide to Business Continuity Management

Australian/New Zealand Standard

This is a free 15 page sample. Access the full version online.

Australian Standard. Guide to lead paint management. Part 2: Residential and commercial buildings AS

Fraud and Corruption Control

BUSINESS CONTINUITY MANAGEMENT

The Development of Statements of Accounting Concepts and Accounting Standards

Asset Plus user guide and FAQs

Reporting Service Performance Information

Quality Assurance. Policy P7

august09 tpp Internal Audit and Risk Management Policy for the NSW Public Sector OFFICE OF FINANCIAL MANAGEMENT Policy & Guidelines Paper

Memorandum of Understanding between the NSW Ministry of Health and Sydney Water Corporation

STANDARDS AUSTRALIA/STANDARDS NEW ZEALAND. Committee CE-001 Parking Facilities DRAFT. Australian/New Zealand Standard

FSDF SPATIAL INFORMATION MANAGEMENT POLICIES - CUSTODIANSHIP

You should distribute the completed learning plan to the team and forward a copy to the human resources team. Name: Section: Location:

AUSTAR turns static data into actionable business intelligence fast

Employability Skills in Information and Digital Technology. based on the Information and Communication Technology Training Package (ICA11) version 1

SAMPLE. Not for training purposes. Student Workbook. BSBHRM403 Support performance management process. 1 st Edition 2015

NSW Data & Information Custodianship Policy. June 2013 v1.0

Australian Standard. Amended from AS

NATIONAL INFORMATICS STANDARDS for NURSES AND MIDWIVES

NSW Payroll Tax Information for Contractors and Employment Agents

SAMPLE. Not for training purposes. Student Workbook. BSBHRM505 Manage remuneration and employee benefits. 1 st Edition 2015

English (ESL) Course. Stage 6 Year 12. Unit: Module A Dialogue Strictly Ballroom UNIT OVERVIEW

What is Australia's Communications Alliance?

COAG National Legal Profession Reform Discussion Paper: Professional Indemnity Insurance

IFRS 9 Financial Instruments

New South Wales State and Regional Population Projections Release TRANSPORT AND POPULATION DATA CENTRE

Counting Infrastructure Software

Effective consultation The ACMA s guide to making a submission NOVEMBER 2015

Design Specification for IEEE Std 1471 Recommended Practice for Architectural Description IEEE Architecture Working Group 0 Motivation

Engineering Procedure

Beacon Financial Group - Privacy Policy

Manage your pay-roll tax obligations online

Mr Timothy Pilgrim The Privacy Commissioner Office of the Australian Information Commissioner GPO Box 5218 SYDNEY NSW 2001

Statements of Learning for Information and Communication Technologies (ICT)

Understanding the New ISO Management System Requirements

ISBN X E-COMMERCE. Option 3 COMMERCE YEARS 7 10 TEXTBOOK. Ann Howard

How To Understand The Differences Between The 2005 And 2011 Editions Of Itil 20000

Small business guide to trade practices compliance programs. April 2006

Electricity retail businesses performance against customer service indicators in NSW

Regulatory Burdens Social & Economic Infrastructure Services

TOTAL ASSET MANAGEMENT. Life Cycle Costing Guideline

APES 325 Risk Management for Firms

INFORMATION MANAGEMENT STRATEGIC FRAMEWORK GENERAL NAT OVERVIEW

Position Description

Energy Markets and Programs Division GPO Box 1264 Adelaide SA 5001

BCPay. Alternative payment process when Online Banking is experiencing Operational Disruptions. Product Disclosure Statement

Australian Transport Council. National Standard for the Administration of Marine Safety SECTION 4 SURVEYS OF VESSELS

Records Disposal Schedule Anti-Discrimination Services Northern Territory Anti-Discrimination Commission

4 April Also via Dear Ms Arblaster

INTERNET VPN SETUP GUIDE

2015 Retail Competition Review

Rating Consultancy RICS/IRRV/RSA Code of Practice. 3rd edition

The Auditor-General Audit Report No Assurance and Control Assessment Audit. Payroll Management. Australian National Audit Office

9. GOVERNANCE. Policy 9.8 RECORDS MANAGEMENT POLICY. Version 4

Strategies for the implementation of a Public Key Authentication Framework (PKAF) in Australia

High Visibility Clothing

Introduction to the ISO/IEC Series

Developing and Reporting Supplementary Financial Measures Definition, Principles, and Disclosures

Application for Renewal or Extension of Certification

Obtaining a Copy of this Interpretation

Managing Online Content

Marketing and Communications Manager Heslerton Road, Dunsandel, Canterbury

National VET E-learning Strategy

Standard 1. Governance for Safety and Quality in Health Service Organisations. Safety and Quality Improvement Guide

EP SP RAILCORP NETWORK MANAGEMENT PLAN CHAPTER 2 - CUSTOMER INSTALLATION SAFETY. Authorised by: Neal Hook Chief Engineer Electrical

Metallic products Types of inspection documents

Tourism, Travel and Events. Consultation Feedback Report

IT Security Management

Transcription:

AS 4651 2004 AS 4651 2004 Australian Standard Standard metamodel for software development methodologies

This Australian Standard was prepared by Committee IT-015, Software and Systems Engineering. It was approved on behalf of the Council of Standards Australia on 31 May 2004. This Standard was published on 23 August 2004. The following are represented on Committee IT-015: Australian Computer Society Australian Information Industry Association Australian Society for Technical Communication (NSW) Australian Software Metrics Association Griffith University New Zealand Organization for Quality Software Quality Association (ACT) Software Quality Association (NSW) Sydney SPIN Group (Software Process Improvement Network) Systems Engineering Society of Australia The University of New South Wales University of South Australia University of Technology, Sydney 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 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 Web Shop 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. Australian Standards TM and other products and services developed by Standards Australia are published and distributed under contract by SAI Global, which operates the Standards Web Shop. We also welcome suggestions for improvement in our Standards, and especially encourage readers to notify us immediately of any apparent inaccuracies or ambiguities. Contact us via email at mail@standards.org.au, or write to the Chief Executive, Standards Australia International Ltd, GPO Box 5420, Sydney, NSW 2001. This Standard was issued in draft form for comment as DR 04154.

AS 4651 2004 Australian Standard Standard metamodel for software development methodologies First published as AS 4651 2004. COPYRIGHT Standards Australia International All rights are reserved. No part of this work may be reproduced or copied in any form or by any means, electronic or mechanical, including photocopying, without the written permission of the publisher. Published by Standards Australia International Ltd GPO Box 5420, Sydney, NSW 2001, Australia ISBN 0 7337 6195 X

AS 4651 2004 2 PREFACE This Standard was prepared by the Australian members of the Joint Standards Australia/Standards New Zealand Committee IT-015, Software and Systems Engineering. After consultation with stakeholders in both countries, Standards Australia and Standards New Zealand decided to develop this Standard as an Australian Standard rather than an Australian/New Zealand Standard. The objective of this Standard is to define a metamodel that establishes a formal framework for the definition and extension of software development methodologies, including their major three aspects: the process to follow, the products to use and generate, and the people involved. This metamodel can serve as a formal basis for the definition and extension of any software development methodology, and will be typically used by methodologists, method engineers or process engineers while undertaking such tasks. The terms normative and informative have been used in this Standard to define the application of the appendix to which they apply. A normative appendix is an integral part of a Standard, whereas an informative appendix is only for information and guidance.

3 AS 4651 2004 CONTENTS Page INTRODUCTION... 4 SECTION 1 SCOPE AND GENERAL 1.1 SCOPE... 5 1.2 APPLICATION... 5 1.3 CONFORMANCE... 5 1.4 NORMATIVE REFERENCES... 5 1.5 TERMS AND DEFINITIONS... 5 SECTION 2 INTRODUCTION TO THE SMSDM 2.1 HIGHLY ABSTRACT VIEW... 8 2.2 ABSTRACT VIEW AND CORE CLASSES... 8 2.3 PROCESS CLASSES... 9 2.4 PRODUCER CLASSES... 10 2.5 PRODUCT CLASSES... 11 2.6 CONNECTION BETWEEN PROCESS AND PRODUCT... 12 2.7 SUPPORT CLASSES... 13 SECTION 3 ELEMENTS OF SMSDM 3.1 CLASSES IN THE SMSDM... 15 3.2 ENUMERATORS IN THE SMSDM... 49 SECTION 4 USAGE OF SMSDM 4.1 USAGE RULES AND GUIDELINES... 50 APPENDICES A PHILOSOPHY... 52 B WORKED EXAMPLE... 56 C MAPPINGS TO OTHER METAMODELLING APPROACHES... 62 D BIBLIOGRAPHY... 67

AS 4651 2004 4 INTRODUCTION Software development methodologies may be described in the context of an underpinning metamodel, but the precise mechanisms that permit them to be defined in terms of their metamodels are usually difficult to explain and do not cover all needs. For example, it is difficult to devise a practice that allows the definition of properties of the elements that compose the methodology and, at the same time, of the entities (such as work products) created when the methodology is applied. This Standard introduces the Standard Metamodel for Software Development Methodologies (SMSDM henceforth), a comprehensive metamodel that makes use of a new approach to defining methodologies based on the concept of powertype. The SMSDM combines key advantages of other metamodelling approaches with none of their drawbacks, allowing the seamless integration of process, modelling and documentational aspects of methodologies. Various methodologies are defined, used, or implied by a growing number of standards and it is desirable that the concepts used by each methodology be harmonised. The vehicle for harmonization is SMSDM. Conformance to this metamodel will ensure a consistent approach to defining each methodology with consistent concepts and terminology.

5 AS 4651 2004 STANDARDS AUSTRALIA Australian Standard Standard metamodel for software development methodologies SECTION 1 SCOPE AND GENERAL 1.1 SCOPE This Standard defines a metamodel that establishes a formal framework for the definition and extension of software development methodologies, including their major three aspects: the process to follow, the products to use and generate, and the people involved. 1.2 APPLICATION This metamodel can serve as a formal basis for the definition and extension of any software development methodology, and will be typically used by methodologists, method engineers or process engineers while undertaking such tasks. 1.3 CONFORMANCE A software development methodology is conformant to this Standard if it has been generated from the metamodel defined in Section 3 Elements of SMSDM by using the rules described in Section 4. 1.4 NORMATIVE REFERENCES This Standard does not call up any normative references. 1.5 TERMS AND DEFINITIONS 1.5.1 Terms The following terms are used throughout this Standard. 1.5.1.1 Methodology Specification of the process to follow and the work products to be used and generated, plus consideration of the people and tools involved, during a software development effort. A methodology specifies the process to be executed, usually as a set of related activities, tasks and/or techniques, together with what work products must be manipulated at each moment, possibly including models, documents and other outputs. In turn, specifying the models that must be developed implies defining the basic building blocks that should be used. 1.5.1.2 Metamodel Specification of the concepts, rules and relationships used to define a methodology. 1.5.1.3 Project Software development effort aimed at the construction of a software system through the application of a methodology. Sometimes, the terms project-level or project layer are used to reference the conceptual entities that exist at the level of projects, as opposed to the entities that exist at the level of a method or a metamodel. www.standards.com.au Standards Australia

The remainder of this document is available for purchase online at www.saiglobal.com/shop SAI Global also carries a wide range of publications from a wide variety of Standards Publishers: Click on the logos to search the database online.