an overview of iso standards relevant to systems engineering amsenga.pdf · • iso/iec 12207,...

An overview of ISO Standards relevant to

Systems Engineering

9th INCOSE SA Conference 2012

Johann AmsengaINCOSE AmbassadorChair: SABS SC 71F (Information security)Convener: ISO/IEC JTC 1/SC 27/WG 4 (Security controls and services)INCOSE delegate to ISO/IEC JTC 1/SC 7 (Software and systems engineering)Chair: INCOSE SA Standards working group

2 of 116© ISO/IEC/INCOSE

Up front

• There are good standards, and there are less than good standards.

• There are practical standards, and there are less practical standards.

• Often people criticise a certain standard.


Up front (cont.)

If the standard in question is an ISO/IEC standard, or a SANS –

you are in a position to contribute to fixing it.


Purpose

• Awareness of systems engineering standards.

• Awareness of standardisation, and the development of standards.


Overview

• This presentation is about ISO ... and the SABS.

• Mainly three parts:– Systems engineering and related standards.

– Introduction to standards, and the development of standards.

– Introduction to the relevant committees responsible for systems engineering standards.


What is a standard?

• Various definitions.

• ISO: A standard is a document that provides requirements, specifications, guidelines or characteristics that can be used consistently to ensure that materials, products, processes and services are fit for their purpose.

• See also SABS, dictionaries.


My derived definition

• Information item that – can be used as a basis for specific requirements

for a specified item, such as a product, process, method or related results; or a specified grouping of items; or a domain;

– can be used to measure conformance to the stated requirements; and

– defines relevant terminology to facilitate communication and understanding.


My derived definition (cont.)

• The information item– is established by consensus, and approved by a

recognised body;

– contributes to the achievement of the optimum degree of order in a given context; and

– provides for common and repeated use.


Development of standards

• Standards can be developed by:– national, regional and international standards

developing organisations;

– businesses or other organisations for their own internal use;

– consortia of businesses to address a specific marketplace need;

– government departments to support regulations.

• This presentation focus on International Standards and National Standards.


The benefits of standards – personal view

• Purpose of this presentation is not to “sell” standards or standardisation.

• I believe in – the clear specification of requirements; and

– the clear specification of how to prove/claim conformance to those requirements.

• Standards contribute to make that easier.


Benefits of standards

• Improving products and services.

• Contribute to providing confidence.

• Knowledge transfer.– Often overlooked!

• Enabling trade and business.

• Supporting regulation.

• Many overlaps of the above.


Committees of interest• Standards are developed by Technical

committees, e.g.– in ISO/IEC, and

– in SABS.

• To be explained later.

• A fair amount of these committees are of interest to INCOSE.


Committees of interest (cont.)• Some ISO examples:

– JTC 1 Information technology

– TC 10 Technical product documentation

– TC 176 Quality management and quality assurance

– TC 204 Intelligent transport systems

– TC 207 Environmental management

– TC 242 Energy Management

– TC 236 Project Committee: Project Management

– TC 258 Project, programme and portfolio management


Committees of interest (cont.)• Some SABS examples:

– SC 71C ICT Systems and software engineering

– TC 175 Process models

– TC 176 Quality Assurance and Quality Management Matters


INCOSE SA Standards WG membershipRelated ISO TC/SC

JTC 1/SC 7, Software and systems engineering

JTC 1/ SC 27, IT Security techniques

TC 176, Quality management and quality assurance

SABS TC/SC Membership

SC 71C, ICT Systems and software engineering

SC 71F, Information security

TC 175, Process models

TC 176, Quality Assurance and Quality Management Matters

TC 200, Standards for standards


Products of interest

• Will focus on products/projects from– SABS TC 175 – Process models.

– ISO/IEC JTC 1/SC 7 – Software and systems engineering (as addressed via SABS SC 71C).

• Some other products mentioned.


INCOSE Handbook

• In process to be adopted.

• ISO/IEC TR 16337, Systems engineering – Systems engineering handbook (INCOSE)


Vocabulary

• ISO/IEC ISO/IEC/IEEE 24765,Systems and software engineering – Vocabulary– The purpose is to serve as a useful reference for

those in the Information Technology field, and to encourage the use of systems and software engineering standards prepared by ISO/IEC and liaison organizations IEEE and PMI (Project Management Institute).

– The goal is to provide definitions that are rigorous, uncomplicated, and which can be understood by all concerned.


Vocabulary (cont.)

• Online:– SEVOCAB

– www.computer.org/sevocab


Architecture

• ISO/IEC 42010, Architecture description– Specifies the manner in which architecture

descriptions of systems are organized and expressed.

– Specifies architecture viewpoints, architecture frameworks and architecture description languages for use in architecture descriptions.

– Provides motivations for terms and concepts used; presents guidance on specifying architecture viewpoints; and demonstrates the use of this International Standard with other standards.


Architecture (cont.)

• ISO/IEC 42030, Architecture evaluation– Specifies the practices and products for planning,

executing and documenting architecture evaluations for the purpose of • determining the quality of an architecture,• verifying that an architecture addresses

stakeholders’ concerns, or

• supporting decision making informed by the architecture of the system of interest.


Life cycle processes

• ISO/IEC 15288, Systems life cycle processes– Establishes a common process framework for

describing the life cycle of man-made systems.

– Defines a set of processes and associated terminology for the full life cycle, including conception, development, production, utilization, support and retirement.

– Supports the definition, control, assessment, and improvement of these processes. These processes can be applied concurrently, iteratively, and recursively to a system and its elements throughout the life cycle of a system.


Life cycle processes (cont.)

• ISO/IEC 12207, Software life cycle processes– Establishes a common framework for software life

cycle processes, with well-defined terminology, that can be referenced by the software industry.

– Applies to the acquisition of systems and software products and services, to the supply, development, operation, maintenance, and disposal of software products and the software portion of a system, whether performed internally or externally to an organization.


Life cycle management

• ISO/IEC 24748, Life cycle management – Part 1: Guide for life cycle management

– Part 2: Guide to the application of ISO/IEC 15288 (System life cycle processes)

– Part 3: Guide to the application of ISO/IEC 12207 (Software life cycle processes)

– Part 4: Systems engineering planning

– Part 5: Software development planning

– Part 6: Guide for system integration


Process assessment

• ISO/IEC 15504, Process assessment– Part 1: Concepts and vocabulary

– Part 2: Performing an assessment

– Part 3: Guidance on performing an assessment

– Part 4: Guidance on use for process improvement and process capability determination


Process assessment (cont.)

• ISO/IEC 15504 (cont.)– Part 6: An exemplar system life cycle process

assessment model

– Part 7: Assessment of organizational maturity

– Part 8: An exemplar process assessment model for IT service management

– Part 9: Target process profiles

– Part 10: Safety extensions



• ISO/IEC 330xx-series, Process assessment

• (This series will replace ISO/IEC 15504)


Process benchmarking

• NEW!

• SANS 1466, Process benchmarking framework– Part 1: Concepts and overview

– Part 2: Generic process model

– Part 3: SANS/ISO 9001 mapping to the generic process model

– Part 4: SANS/ISO/IEC 12207 mapping to the generic process model

– Part 5: CMMI mapping to the generic process model


Systems and software assurance

• ISO/IEC 15026, Systems and software assurance– Part 1: Concepts and vocabulary

– Part 2: Assurance case

– Part 3: System integrity levels

– Part 4: Assurance in the life cycle


Risk management

• ISO/IEC 16085, Life cycle processes – Risk management– Describes a process for the management of risk

during systems or software acquisition, supply, development, operations, and maintenance.

– Purpose is to provide suppliers, acquirers, developers, and managers with a single set of process requirements suitable for the management of a broad variety of risks.


Requirements engineering

• ISO/IEC 29148, Life cycle processes – Requirements engineering– Specifies the required processes that are to be

implemented for the engineering of requirements for systems and software products (including services) throughout the life cycle,

– gives guidelines for applying the requirements and requirements-related processes described in ISO/IEC 12207:2008 and ISO/IEC 15288:2008,


Requirements engineering (cont.)

• ISO/IEC 29148 (cont.)– specifies the required information items that are to

be produced through the implementation of the requirements processes,

– specifies the required contents of the required information items, and

– gives guidelines for the format of the required and related information items.


Product quality achievement

• ISO/IEC TR 30103, Life cycle Processes – Framework for Product Quality Achievement– Provides guidance on applying ISO/IEC

15288:2008 life cycle processes to systematically achieve product quality in projects that deliver systems and software products and services.

– It focuses on how the development of certain information items, the quality thereof, the inter-relationships between these information items and the maintenance and mutual consistency management of these information items contribute to achieving quality.


Product quality achievement (cont.)

• ISO/IEC TR 30103 (cont.)– Application of life cycle processes to deliver the

product involves the production of, among others, a collection of technical information items, such as requirements, design, plans, and validation information items, as well as implementations and the integrated and deployed product.

– Identifies the network of content consistency relationships that should hold among technical information items.


Configuration management

• IEEE Std. 828, IEEE Standard for Configuration Management in Systems and Software Engineering.– Establishes the minimum requirements for

Configuration Management (CM) in Systems and Software Engineering, without restriction to any form, class, or type.


Configuration management (cont.)

• IEEE Std. 828 (cont.)– Describes CM processes to be established, how

they are to be accomplished, who is responsible for doing specific activities, when they are to happen, and what specific resources are required.

– It addresses CM activities over a product's life cycle. This standard is consistent with IEEE’s Software Engineering Body of Knowledge (SWEBOK), ISO/IEC/IEEE 12207:2008 and ISO/IEC/IEEE 15288:2008.


Verification and validation

• IEEE Std. 1012, IEEE Standard for System and Software Verification and Validation– A process standard that addresses all system and

software life cycle processes including the Agreement, Organizational Project-Enabling, Project, Technical, Software Implementation, Software Support, and Software Reuse process groups.

– compatible with all life cycle models (e.g., system, software, and hardware); however, not all life cycle

– models use all of the processes listed in this standard.



• IEEE Std. 1012 (cont.)– Compatible with all life cycle models (e.g., system,

software, and hardware); however, not all life cycle models use all of the processes listed in this standard.

– V&V processes determine whether the development products of a given activity conform to the requirements of that activity and whether the product satisfies its intended use and user needs.

– This determination may include the analysis, evaluation, review, inspection, assessment, and testing of products and processes.



• IEEE Std. 1012 (cont.)– Purpose of the standard is to perform the following:

• Establish a common framework of the V&V processes, activities, and tasks in support of all system, software, and hardware life cycle processes.

• Define the V&V tasks, required inputs, and required outputs in each life cycle process.

• Identify the minimum V&V tasks corresponding to a four-level integrity scheme.

• Define the content of the Verification and Validation Plan


SQuaRE

• ISO/IEC 25000-series, Systems and software Quality Requirements and Evaluation (SQuaRE)

• General goal is to move to a logically organised, enriched and unified series covering two main processes: – software quality requirements specification and

software quality evaluation,

– supported by a software quality measurement process.


SQuaRE (cont.)

• Assist those developing and acquiring software products with the specification and evaluation of quality requirements. – Establishes criteria for specification of software

product quality requirements, their measurement, and evaluation.

– Includes a two-part quality model for aligning customer definitions of quality with attributes of the development process.

– Provides recommended measures of software product quality attributes that can be used by developers, acquirers, and evaluators.


SQuaRE (cont.)

• SQuaRE consists of five divisions: – ISO/IEC 2500n - Quality Management Division

– ISO/IEC 2501n - Quality Model Division

– ISO/IEC 2502n - Quality Measurement Division

– ISO/IEC 2503n - Quality Requirements Division

– ISO/IEC 2504n - Quality Evaluation Division


SQuaRE (cont.)

• SQuaRE provides: – Terms and definitions,

– Reference models,

– General guide,

– Individual division guides, and

– Standards for requirements specification, planning and management, measurement and evaluation purposes.


SC 7 products not addressed

• System and software documentation

• Tools and environment

• Bodies of knowledge and professionalization

• Very Small Enterprises


Quality management

• ISO 9000 family addresses various aspects of quality management.

• The standards provide guidance and tools for companies and organisations who want to ensure – that their products and services consistently meet

customer’s requirements,

– and that quality is consistently improved.


Quality management (cont.)

• ISO 9000 covers basic concepts and language.

• ISO 9001 sets out requirements of a quality management system.

• ISO 9004 focuses on how to make a quality management system more efficient and effective.

• ISO 19011 sets out guidance on internal and external audits of quality management systems.


Social Responsibility

• Organisations' relationship to the society and environment in which they operate is a critical factor in their ability to continue to operate effectively.

• ISO 26000, Guidance on social responsibility– Provides guidance on how businesses and

organisations can operate in a socially responsible way.


Risk management

• ISO 31000, Risk management – Principles and guidelines.– Provides principles, framework and a process for

managing risk.

– Can help organisations increase the likelihood of achieving objectives, improve the identification of opportunities and threats and effectively allocate and use resources for risk treatment.


Risk management (cont.)

• ISO Guide 73, Risk management vocabulary.– Complements ISO 31000 by providing a collection

of terms and definitions relating to the management of risk.

• ISO/IEC 31010, Risk Assessment Techniques.– Focuses on risk assessment concepts, processes

and the selection of risk assessment techniques.


Environmental management

• The ISO 14000 family addresses various aspects of environmental management.

• Provides practical tools for companies and organisations looking to identify and control their environmental impact and constantly improve their environmental performance.


Environmental management (cont.)

• Focus on environmental management systems.– ISO 14001, Requirements with guidance for use.

– ISO 14004, General guidelines on principles, systems and support techniques.

• Other standards in the family focus on specific environmental aspects such as life cycle analysis, communication and auditing.


Energy management

• ISO 50001, Energy Management System.

• Provides a framework of requirements for organizations to:– Develop a policy for more efficient use of energy.

– Fix targets and objectives to meet the policy.

– Use data to better understand and make decisions about energy use.

– Measure the results.

– Review how well the policy works.

– Continually improve energy management.


Business continuity

• ISO 22301, Business continuity management systems – Requirements.

• Help organizations, regardless of their size, location or activity, to be better prepared and more confident to handle disruption of any type.


International Standardisation

• Three main organisations:– ISO – International Organization for Standardization.

– IEC – International Electrotechnical Commission.

– ITU – International Telecommunication Union.

• Also take note of the IEEE.


ISO

• International Organization for Standardization

• Develops International Standards for products, services, processes, materials and systems, and for conformity assessment, managerial and organisational practice; but

• does not carry out certification of conformity to its standards.

• http://www.iso.org/


ISO (cont.)

• Produces voluntary consensus standards through its decentralised global system of standardisation.

• Network of national standards bodies, on the basis of one member per country.– 164 countries (May 2012).

• Independent.

• Non-governmental.


IEC

• International Electrotechnical Commission

• Prepares and publishes International Standards for all electrical, electronic and related technologies.

• Close relationship with ISO.

• E.g. JTC 1 – Information technology.

• http://www.iec.ch


ITU

• International Telecommunication Union

• United Nations specialised agency for information and communication technologies.

• Allocate global radio spectrum and satellite orbits, develop technical standards that ensure networks and technologies seamlessly interconnect, strive to improve access to ICTs to under served communities worldwide.

• http://www.itu.int


IEEE-SA

• IEEE Standards Association (IEEE-SA)

• Consensus building organisation that nurtures, develops and advances global technologies, through IEEE.

• Broad range of individuals and organisations from a wide range of technical and geographic points of origin to facilitate standards development and standards related collaboration.

• http://standards.ieee.org


Other standardisation organisations

• See the following for links to other standardisation organisations – http://www.ses-standards.org/

displaycommon.cfm?an=9

– http://www.wssn.net/WSSN/listings/links_international.html


National Standardisation

• South African Bureau of Standards

• The national institution for the promotion and maintenance of standardisation and quality in connection with commodities and the rendering of services.

• http://www.sabs.co.za


More on governance, members

• More information on governance: http://www.iso.org/iso/home/about/about_governance.htm

• More information on members:http://www.iso.org/iso/home/about/iso_members.htm

• See also IEC

http://www.iec.ch


Products

• ISO International Standards

• ISO/PAS Publicly Available Specifications

• ISO/TS Technical Specifications

• ISO/TR Technical Reports

• IWA International Workshop Agreements

• ISO Guides


Development of ISO standards

• Developed by the people that need them, through a consensus process.

• Experts from all over the world develop the standards that are required by their sector.

• This means they reflect a wealth of international experience and knowledge.

• Account taken of evolving technology, and evolving interests, by requiring a review of standards.


The process in short

• An ISO standard is developed by a panel of experts, within a technical committee. – Once the need for a standard has been

established, these experts meet to discuss and negotiate a draft standard.

– As soon as a draft has been developed it is shared with ISO’s members who are asked to comment and vote on it.

– If a consensus is reached the draft becomes an ISO standard, if not it goes back to the technical committee for further edits.


Experts and national representation

• Experts come from the industrial, technical and business sectors which have asked for the standards, and which subsequently put them to use.

• May be joined by others with relevant knowledge, such as representatives of government agencies, testing laboratories, consumer associations, environmentalists, academic circles and so on.


Experts and national representation (cont.)

• Participate as national delegations, chosen by the ISO national member institute for the country concerned.

• Delegations are required to represent not just the views of the organisations in which their participating experts work, but of other stakeholders too.


Experts and national representation (cont.)

• According to ISO rules, the member institute is expected to take account of the views of the range of parties interested in the standard under development and to present a consolidated, national consensus position to the technical committee.


ISO Committee structure

Technical committees

Working groups

Subcommittees Working groups



• Technical committees (TCs) are established to– serve specific industries or generic subjects,

– in order to develop International Standards or other ISO publications appropriate to the needs of that sector.

• The focus of the technical committees is necessarily specialised and specific.


Technical committees (cont.)

• Receive inputs – from a wide range of associated committees at the

national level,

– and from liaison organisations with regional or international links.



• http://www.iso.org/iso/home/standards_development/list_of_iso_technical_committees.htm

• http://www.iec.ch/dyn/www/f?p=103:6:0


Membership types

• Participating (P-Members).

• Observing (O-Members).

• Liaison (L-members).


Participating members

• ISO member bodies which wish to play an active role in the work of a technical committee or subcommittee.– Have an obligation to vote in all official ballots

related to the work of the committee.

– Have a duty to identify experts who may be able to contribute to the related working group activities.

• Work on the preparation of International Standards and provide a feed-back route to their national organisations.


Observing members

• Those who wish to follow the development of a standard, and possibly to make contributions to the work, without committing themselves to active participation.

• Open to ISO member bodies and correspondent members.


Liaison memberships

• A way for international and broadly-based regional organisations to participate in, or to be informed about, the development of standards, and

• thus to ensure wider acceptance of the final result and to ensure coordination of parallel standardisation activities in different bodies.


Liaison memberships (cont.)

• To be effective, – liaison needs to operate in both directions,

– normal to establish reciprocal arrangements,

– usually involve the exchange of basic documents, including new work item proposals and working drafts.


Liaison types and categories

• Category A liaisons

• Category B liaisons

• Category C liaisons

• Category D liaisons

• Internal liaisons


Category A liaisons

• Organisations that make an effective contribution to the work of the technical committee or subcommittee for questions dealt with by this technical committee or subcommittee.

• Such organisations are sent copies of all relevant documentation and are invited to meetings.

• May nominate experts to participate.


Meetings

• Technical Committees meet regularly.

• Committees normally once per year.

• Working groups normally twice per year.

• The national delegations of experts (and liaisons) of a technical committee meet to discuss, debate and argue until they reach consensus on a draft agreement.


Development

• An International Standard is the result of an agreement between the member bodies of ISO.

• Developed by ISO technical committees (TC) and subcommittees (SC) by a six-step process.

• The Directives are the core procedures for standards development work within ISO and IEC.


Development stages

• Proposal stage

• Preparatory stage

• Committee stage

• Enquiry stage

• Approval stage

• Publication stage


Review of International Standards

• Several factors combine to render a standard out of date, e.g.– technological evolution,

– new methods and materials,

– new quality and safety requirements.


Review of International Standards

• All International Standards are reviewed – at the least three years after publication and

– every five years after the first review by all the ISO member bodies.

– On occasion, it is necessary to revise a standard earlier.

• P-members of the TC/SC decides whether an International Standard should be– confirmed,

– revised or

– withdrawn.


Technical corrigenda and amendments

• Published International Standard may subsequently be modified by – a technical corrigendum (or a corrected reprint of

the current edition)

– an amendment.

• Published as separate documents, the edition of the International Standard affected remaining in print.


Technical corrigenda

• Issued to correct either– a technical error or ambiguity in a product,

inadvertently introduced either in drafting or in printing and which could lead to incorrect or unsafe application of the publication, or

– information that has become outdated since publication, provided that the modification has no effect on the technical normative elements of the standard.


Amendments

• An amendment alters and/or adds to previously agreed technical provisions in an existing International Standard.


SABS

• The South African Bureau of Standards is a statutory body – established in terms of the Standards Act, 1945

(Act No. 24 of 1945),

– continues to operate in terms of the latest edition of the Standards Act, 2008 (Act No. 29 of 2008)

– as the national institution for the promotion and maintenance of standardisation and quality in connection with commodities and the rendering of services.


Products

• Normative documents:– South African National Standards.

– South African Technical Specifications.

– Sectoral Technical Agreements.

• Non-normative documents:– South African Technical Reports.

• No normative document may conflict with, or undermine, the provisions of any SANS or compulsory specification.


Products (cont.)

• Products are reviewed regularly to ensure continued market relevance.

• If updating is required, a revision or an amendment can be initiated.

• Standards Division maintains a collection of more than 6000 standards.– Produces standards via more than 450 committees.

– Approximately 98% of standards are voluntary,

– May be made compulsory under certain circumstances.


International participation

• Recognises that international and regional standardisation plays an extremely important role in connecting countries and communities.

• Member body of ISO and participates actively in a number of their committees.

• Also provides financial and administrative support for South Africa's membership of IEC.


Development of standards

• Development of South African standards funded by the Department of Trade and Industry.

• The SABS acts as – a facilitator in the development and maintenance of

South African standards, and

– also as the publisher of standards.

• Provides secretarial and technical writing facilities and services for the committee responsible for this task.


Development of standards (cont.)

• To achieve market relevance, best practice in terms of the WTO/TBT agreement is followed to ensure – that valid interest groups are represented on

committees and, once the committee has reached consensus,

– draft South African standards are submitted to a public enquiry stage.


Development of standards (cont.)

• Two options are available when considering a new national standard:– Adopt without change an international or regional

standard.

– Develop a South African standard containing at least some different requirements.


Adopting standards

• Adoption (of an International Standard as a regional or national standard): – publication of a national or regional normative

document based on a relevant International Standard,

– or endorsement of an International Standard as having the same status as a national normative document,

– with any deviations from the International Standard identified.


Adopting standards (cont.)

• Has the advantage that the resulting adopted standard is produced – cheaply,

– quickly and

– easily.

• Is in line with the World Trade Organisation Agreement.

• Might not, however, represent fully the needs and requirements of the South African market.


Adopting standards (cont.)

• SABS committed, wherever possible, to encouraging committees to adopt international or regional standards, since this will ultimately result in wider standardisation, with all its benefits, on a global scale.


Local development

• Has the advantage that a more focused standard can be achieved that addresses local needs well.

• The development of such a standard is – costly and

– time consuming.

• The result may well be a re-invention of the wheel.


Technical Committees (TC)

• National standards are prepared through a consensus process in technical committees.

• Group of representatives that is concerned with standardisation, that is responsible for identifying the need for, and the preparation of, South African national standards and other normative and non-normative documents in a defined field and that reflects valid national interests within that field.



• Are constituted to be representative, as far as reasonably possible, of valid national interests in the standardisation of products or processes.

• The technical content of a standard contextualises national requirements and needs as identified by the committee.

• https://www.sabs.co.za/Standardss/standards_tech.asp


SABS Committee structure


Working groups

Subcommittees Working groups


Membership

• Preferably on the basis of organisation, association or forum representation as opposed to an individual basis.

• Organisations include government bodies, industry associations, consumer organisations or associations, non-government organisations, organised labour and professional, technical and trade organisations.


Membership (cont.)

• Committees may invite experts to serve in any capacity, advisory or otherwise.

• Membership status:– Participating member.

– Observing member.


ISO Committee structureTechnical management board (TMB)

Technical advisory groups REMCO

REMCO – Committee on reference materials


JTC 1 JTC 2 TC 1 TC 176 TC 269··· ···

Working groups Subcommittees

SC 2 SC 7 SC 27 SC 39·········


SABS Committee structure

REMCO – Committee on reference materials


TC 71 TC 176 TC 1046··· ···

Working groups Subcommittees

SC 71C SC 71F SC 71Q······

TC 21 ······


SABS TC 175

• Process models.

• New national committee– INCOSE SA a member.

• Main focus currently development of – SANS 1466, Information technology - Process

benchmarking framework.


ISO/IEC JTC 1/SC 7

• Information technology – Software and systems engineering.

• Terms of reference– Standardization of processes, supporting tools and

supporting technologies for the engineering of software products and systems.

• INCOSE Category A liaison.


ISO/IEC JTC 1/SC 7 (cont.)

• Locally addressed by SABS SC 71C – ICT Systems and software engineering.

• INCOSE SA a member.


SC 7 Structure

S C 7

S e c r e t a r i a t

S t a n d a r d s M a n a g e m e n t G r o u p

S W G 5

S y s t e m s & S o f t w a r e D o c u m e n t a t i o n

W G 2

I T G o v e r n a n c e

W G 1 A

P r o c e s sA s s e s s m e n t

W G 1 0

V o c a b u l a r yM a i n t e n a n c e

S W G 2 2

I T S e r v i c eM a n a g e m e n t

W G 2 5

W G 2 6

S o f t w a r e T e s t i n g

T o o l s a n dE n v i r o n m e n t

W G 4T e c h n i q u e s f o r

S p e c i f y i n g I T S y s t e m s

W G 1 9

S y s t e m s Q u a l i t y M a n a g e m e n t

W G 2 3

L i f e C y c l e M a n a g e m e n t

W G 7

S o f t w a r e P r o d u c tM e a s u r e m e n t a n d

E v a l u a t i o n

W G 6

A r c h i t e c t u r e

W G 4 2

C I F U s a b i l i t y

W G 2 8

S L C P r o f i l e s a n d G u i d e l i n e s f o r V S E

W G 2 4

S W G 1

B u s i n e s s P l a n n i n g G r o u p

W G 2 0S o f t w a r e E n g i n e e r i n g

B o d y o f K n o w l e d g e

W G 2 1S o f t w a r e

A s s e t M a n a g e m e n t

I T G o v e r n a n c e

W G 4 0

L i f e C y c l e P r o c e s sH a r m o n i z a t i o n A d v i s o r y

G r o u p

L C P H A G


SC 7 Standards collection


More information

• SABS: http://www.sabs.co.za

• ISO: http://www.iso.org

• IEC: http://www.iec.ch

• ITU: http://www.itu.int

• IEEE SA: http://standards.ieee.org


More information (cont.)

• ISO/IEC JTC 1/SC 7– http://www.jtc1-sc7.org/

• ISO Focus+:– http://www.iso.org/iso/home/news_index/

iso-magazines.htm

• ISO Standards in Action– http://www.iso.org/iso/home/news_index/iso-in-

action/sustainable_development.htm

– E.g. Cars



• South African IT Process Improvement Association– http://www.improveit.org.za

• The Society for Standards Professionals– http://www.ses-standards.org

• ISONET Directory– http://www.wssn.net/WSSN/RefDocs/isonetdir/

index.html



• International Federation of Standards Users– http://www.ifan.org

• NIST Global Standards Information– http://gsi.nist.gov/global/index.cfm/L1-1

an overview of iso standards relevant to systems engineering amsenga.pdf · • iso/iec 12207,...

Documents