[PDF] [PDF] ISO standards ISO 12207, ISO 15504 & ISO 9126 - CETIC

[PDF] Normes dingénierie système et logiciel pour les très petites

2 mar 2012 · telles que l'ISO/IEC 12207 et l'ISO/CEI 15288, pour un projet spécifique Ces TPO ne savent pas comment ajuster le processus sélectionné, 

[PDF] Towards a Serious Game to Teach ISO/IEC 12207 Software - CORE

ISO/IEC 12207 is an international software engineering standard which defines the soft- ware engineering processes and activities, which are associated with 

[PDF] ISO/IEC 12207:2008 — IEEE Std 12208-2008

14 avr 2014 · ISO/IEC 12207 was published on 1 August 1995 and was the first International Standard to provide a comprehensive set of life cycle processes, 

[PDF] Checklist for Standard ISO/IEC/IEEE 12207:2017 - ComplianceOnline

31 mar 2018 · ISO/IEC/IEEE 12207:2017 Systems and Software Engineering – Software Life Cycle Processes The World Standard for Developing Quality

[PDF] INTERNATIONAL STANDARD ISO/IEC/ IEEE 12207

12207 Reference number ISO/IEC/IEEE 12207:2017(E) First edition 2017-11 Permission can be requested from either ISO or IEEE at the address below or 

[PDF] ISO/IEC/IEEE 12207, Systems and software engineering -- Software

3 jan 1971 · Table I 2 — Comparison of process outcomes in ISO/IEC/IEEE 12207:2017 and software-related outcomes in the previous edition

[PDF] ISO standards ISO 12207, ISO 15504 & ISO 9126 - CETIC

23 mai 2007 · ISO 12207 = common framework for the lifecycle of the software ➢ Architecture of the software lifecycle processes (processes, activities, tasks)

[PDF] Towards a Serious Game to Teach ISO/IEC 12207 - DORAS

ISO/IEC 12207 Software Lifecycle processes can be maintained by 7 main phases by any organization which have capability to support the standard's views and 

[PDF] International Standard ISO/IEC 12207 Software Life Cycle - OoCities

1 août 1995 · In June 1989, the JTC1 initiated the development of an International Standard, ISO/IEC 12207 [1], on software life cycle processes to fill a 

[PDF] iso 14000

[PDF] iso 14001

[PDF] iso 14001 2015

[PDF] iso 14001 2015 pdf

[PDF] iso 14001 2015 ppt presentation

[PDF] iso 14001 définition

[PDF] iso 14001 logo

[PDF] iso 14001 pdf

[PDF] iso 14001 pdf gratuit

[PDF] iso 14001 pour les nuls

[PDF] iso 14001 ppt français

[PDF] iso 14001 version 2015 changements

[PDF] iso 14001 version 2015 pdf gratuit

[PDF] iso 14001 version 2015 ppt

[PDF] iso 14001 wiki

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

quotesdbs_dbs4.pdfusesText_8