[PDF] ISO standards ISO 12207 ISO 15504 & ISO 9126

View - Download ISO standards ISO 12207 ISO 15504 & ISO 9126

Previous PDF

Next PDF

1

ISO standardsISO standards

ISO 12207, ISO 15504 & ISO 9126

ISO 12207, ISO 15504 & ISO 9126

ISACA - CETIC Meeting

23 May 2007

2

IntroductionIntroduction

ISO 12207 = common framework for

the lifecycle of the software

Architecture of the software lifecycle

processes (processes, activities, tasks)

ISO 15504 also known as SPICE

(Software Process Improvement and

Capability Determination) = "framework

for the assessment of software processes"

Derived from 12207 and CMMI

ProcessProcessstandardsstandards

3

Introduction (2)Introduction (2)

ISO 9126 = set of characteristics to

describe software product quality

Internal, external and use-related features

Each characteristic = subcharacteristics +

metric to assess conformance with requirements

ProductProductstandardstandard

4

ISO 12207ISO 12207

Software

Software lifecyclelifecycleprocessesprocesses

5

AgendaAgenda

1.Context and Purpose

2.Scope

3.History

4.Basic concepts

ISO 12207

6

1. 1. ContextContextandandPurposePurpose

Domain : software engineeringFocus : software lifecycle processesPurpose : to establish a common framework

for the life cycle of software to foster mutual understanding among business parties to acquire, supply, develop, operate and maintain software

ISO 12207

7

2. Scope2. Scope

Stakeholders: acquirers, suppliers, users etcApplication: corporate processes related to project products and project servicesISO 12207 covers process definitions and descriptions

ISO 12207

8

3. 3. HistoryHistory

ISO 12207

9

3. 3. HistoryHistory(2)(2)

ISO/IEC 12207 Sponsor:

• Joint Technical Committe 1 (JTC1) (Information Technology) of International Organization for Standardization (ISO) and International Electrotechnical Commission 7 (IEC). • Developer: Subcommittee 7 (SC7) (Software Engineering)

Proposed in June 1988Published 1 August 1995Participants: Australia, Canada, Denmark, Finland, France,

Germany, Ireland, Italy, Japan, Korea, Netherlands, Spain,

Sweden, UK, USA

ISO 12207

10

4. Basic Concepts 4. Basic Concepts --LifeLifecycle cycle andand

architecture architecture

ISO 12207

11

Modularity

Cohesion (Functional): Tasks in a process must be functionally relatedCoupling (Internal): Links between processes must be minimal

Association

If a function is used by more than one process, then the

function becomes a process in itselfIf Process X is invoked by Process A and Process A only, then Process X belongs to Process A

Responsibility

Each process is under a responsibilityA function with parts under different responsibilities shall notbe a process

4. Basic Concepts 4. Basic Concepts --RulesRulesfor for

partitioning partitioningthethelifelifecyclecycle

ISO 12207

12

4. Basic Concepts 4. Basic Concepts --TheTheProcessProcess

Tree Tree

ISO 12207

13 A process is partitioned into PDCA activities based on the PDCA- cycle principles

4. Basic Concepts 4. Basic Concepts --RulesRulesfor for

partitioning partitioninga a processprocess

ISO 12207

14 An activity is divided into tasks, which are grouped into similar actionsBased on TQM Principles Each party/participant has appropriate responsibility

4. Basic Concepts 4. Basic Concepts --ActivityActivityandand

Tasks Tasks

ISO 12207

15 Not certifyingNot prescriptive, no how-tosNot a standard for methods, techniques & models does not prescribe management and engineering methodsdoes not prescribe computer languagesEtc

Not a standard for metrics

many tasks need metrics and indicatorsbut prescribes no specific metrics/indicatorsreferences ISO/IEC 9126 for guidance

4. Basic Concepts 4. Basic Concepts --WhatWhat12207 12207 isis

not not 16

ISO 15504 (SPICE)ISO 15504 (SPICE)

Software

Software QualityQuality

17

AgendaAgenda

1.Context and Purpose

2.History

3.Basic concepts

4.CETIC products derived from ISO

15504

ISO 15504

18

1. 1. ContextContextandandPurposePurpose

Normalized structure devoted to managing

requirements related to a software development processModel for process management + set ofrequirements/guidelines to assess/improve those processes

ISO 15504

19

2. 2. HistoryHistory

Early 1990's: process improvement and

capability determination methods developed in several countries

International consensus on the urgent need for

a public domain standar for software process assessment

June 1991 in London, Joint Technical

Committee 1/Sub-Committee 7 of the

ISO/IEC: resolution to develop an

international standard on software process assessment

ISO 15504

20

3. Basic concepts 3. Basic concepts --ProcessProcess

5 process categories

Customer-Provider

• Acquisition process (process for selectiong provider) • Process for support to customer

Engineering

• Process for analyzing requirements and designing the system

Support

• Documentation process

Management

• Risk management process

Organization

• Process for managing human resources

ISO 15504

21

3. Basic concepts 3. Basic concepts --ProcessProcess

6 maturity levels for assessing the processes

5 : optimizing4 : quantitatively managed3 : defined2 : managed1 : initial0 : incomplete

To assess a process, we define it as follows:

Purpose/goalResults/attributes that should be met to reach a successful implementation of the process

ISO 15504

22

3. Basic concepts 3. Basic concepts --ProcessProcessandandmaturitymaturity

levels levels(2)(2)

6 niveaux de maturité

5 : en optimisation4 : prévisible3 : établi2 : géré1 : réalisé0 : incomplet

Example

: process for software testing(1/2) Purpose: to test the integrated software Result of a successful implementation of the process Acceptance criteria are developed in order to verify compliance with requirementsThe integrated software is verified using the defined acceptance

criteriaThe testing results are taken inA non-regression strategy is established in order to test theintegrated software again if software is modifiedThe regression testing is performed when necessary

ISO 15504

23

3. Basic concepts 3. Basic concepts --AssessingAssessingeacheachprocessprocess

For each attribute:

N = not implementedP = partly implementedL = largely implementedF = fully implemented

A level is achieved if

The attribute(s) of this level = or FAttributes of lower levels = F

0% 15 %

16 % 50 %

51 % 85 %

86 % 100 %

LF

ISO 15504

24

3. Basic concepts 3. Basic concepts --ExampleExampleofofprocessprocess

assessment assessment

Requirements analysis

design building testing

Quality assurance

configuration management level 3 PA3.2 P P N P L P

PA3.1PPNPPP

level 2 PA2.2 LLPLLP

PA2.1 LLLPPN

level 1 PA1.1LFLPPL =>achieved level

121001

ISO 15504

25

3. Basic concepts 3. Basic concepts --ConclusionConclusion

SPICE is very interesting to prepare an improvement plan Can be applied to the way a team worksGives the opportunity to deployprogressivelythe action plan: By targeting first and foremost the most criticalprocessesBy targeting the levels in ascending order • On a mid-term: target = level 2 • On a long term: target = level 3

ISO 15504

26

4. CETIC 4. CETIC productsproducts--OWPL OWPL

(Observatoire Wallon des Pratiques Logicielles)(Observatoire Wallon des Pratiques Logicielles)

Model based on CMM and SPICE (ISO

15504)Adapted to SMO'sgoal:improve software production

processes

ISO 15504

27

4. CETIC 4. CETIC productsproducts--OWPL (2)OWPL (2)

model structure:

10 processes (each split up in practices):

requirements management, project planification, project follow-up, development, documentation, test, configuration management, outsourcing management, quality managemenet, process for capitalizing knowledge

Success factors organized in 4 categories:

organization within the processes take place, the management policy, the human resources the " used » technical tools

ISO 15504

28

4. CETIC 4. CETIC productsproducts--OWPL (3)OWPL (3)

Success story: PEPITe

CETIC has assessed the PEPITo software with

OWPLGoal: inform PEPITe about their software development practices to improve them

Improve their products and services

CETIC has provided a complete assessment

report + recommendations to improve their development practices

ISO 15504

29

4. CETIC 4. CETIC productsproducts--NOEMINOEMI

based on existing standards such as ISO/IEC15504The NOEMI assessment method has been developed by Centre HENRI TUDOR (Luxemburg).Two goals: improve the perception of computer maturity in SMO's or VSMO'smethodological tool for improving those companies' SI

ISO 15504

30

4. CETIC 4. CETIC productsproducts--NOEMI (2)NOEMI (2)

Assessment according to an exhaustive list of the

typical computer activities in SMO's/VSMO's divided in 5 fields:

ISO 15504

31

4. CETIC 4. CETIC productsproducts--NOEMI (3)NOEMI (3)

Success Story: GREISCH (Liège), Architects office

Interviews conducted with 3 types of users:

• One responsible within the computer department • The director of the computer department • 3 end-users (architects) CETIC has provided GREISCH with an assessment report on their practices within the computer department and the quality of the services/products delivered to the end-

users (the architects) by the computer scientistsCETIC has also provided recommendations to improvetheir products and services

32

ISO 9126ISO 9126

Software

Software ProductProductQualityQuality

33

AgendaAgenda

1.Scope

2.History

3.Basic concepts

4.CETIC products derived from ISO 9126

ISO 9126

34

ISO 9126is an international standard

for the evaluation of software

It will be overseen by the project SQuaRE

ISO 25000:2005

, which follows the same general concepts four parts: quality model; external metrics; internal metrics; and quality in use metrics.

1. Scope1. Scope

ISO 9126

35

Late 1980's: need for a framework assessing

the quality of a software product1991: Joint Technical Committee of the ISO/IEC develops ISO 9126Standard revised in 2001Will be overseen by SQuaRE (ISO 25000:2005)

2. 2. HistoryHistory

ISO 9126

36

3. Basic concepts 3. Basic concepts --FirstFirstpartpart

The quality model established in the first part

of the standard, ISO 9126-1, classifies software quality in a structured set of characteristics and sub-characteristics as follows:

ISO 9126

37
quotesdbs_dbs14.pdfusesText_20

[PDF] iso 9126 pdf

[PDF] iso abréviation

[PDF] iso budget définition

[PDF] iso dis 9001 2015

[PDF] iso square

[PDF] iso/cei 14598

[PDF] iso/dis 22000

[PDF] iso/iec 25010:2011 pdf

[PDF] iso/tc 176 pdf

[PDF] iso/tc 176/sc 2 pdf

[PDF] iso26000

[PDF] isobarycentre quadrilatere

[PDF] isocout

[PDF] isocout définition

[PDF] isolationnisme