Process Metamodels-Software Development Methodologies- Lecture 16 Slides-Computer Engineering, Slides of Software Development Methodologies

Process Metamodels, Software Process Engineering Metamodel, SPEM, Core Structure, Detailed Structure, Conceptual Usage Framework, Method Content, Process Components, Modeling Enactable Processes, Raman Ramsin, Lecture Slides, Software Development Methodologies, Department of Computer Engineering, Sharif University of Technology, Iran.

Typology: Slides

2011/2012

Uploaded on 02/20/2012

hester
hester šŸ‡®šŸ‡·

4.5

(13)

84 documents

1 / 21

Toggle sidebar

This page cannot be seen from the preview

Don't miss anything!

bg1
Software Development
Methodologies
Lecturer: Raman Ramsin
Lecture 16
Process Metamodels
Department of Computer Engineering 1Sharif University of Technology
pf3
pf4
pf5
pf8
pf9
pfa
pfd
pfe
pff
pf12
pf13
pf14
pf15

Partial preview of the text

Download Process Metamodels-Software Development Methodologies- Lecture 16 Slides-Computer Engineering and more Slides Software Development Methodologies in PDF only on Docsity!

Software Development Methodologies Lecturer:

Raman Ramsin

Lecture 16 Process Metamodels

1

Sharif University of Technology

Software Development Methodologies – Lecture 16

Process MetamodelsProcess

Metamodels

l^

f

l^

b

f

d

l

Ā„

Results of applying abstraction to software development processes

Ā„

Highlight the high-level features of a process or family of processes

Ā„

Can be instantiated in order to produce concrete processes

Ā„

The two most well-known object-oriented process metamodels:

OPEN Consortium’s

OPEN Process Framework (OPF)

OMG’s

Software and Systems Process Engineering Metamodel (SPEM 2.0)

2

Sharif University of Technology

Software Development Methodologies – Lecture 16

SPEM 1.0:

Core Structure

SPEM

Core Structure

Ā„

Regards the core structure of a software development process asconsisting of:consisting of:

process roles

k

d

t

work products

activities

Ā„

Regards a software development process as

a collaboration of active entities (

process roles)

a collaboration of active entities (

process roles)

Ā„

aimed at performing specific operations (

activities)

f

d

t^

f t

ibl

t f

t

(

k

d

t

)

performed on a set of tangible artefacts (

work products

)

continued until the artefacts are brought to a well-defined state,and declared as complete.

4

Sharif University of Technology

p

Software Development Methodologies – Lecture 16

SPEM 1.0:

Core Structure

SPEM

Core Structure

5

Sharif University of Technology

[OMG 2002]

Software Development Methodologies – Lecture 16

SPEM 1.0:

Lifecycle Definition

SPEM

Lifecycle Definition

SPEM incorporates definitions for

Ā„

SPEM

incorporates definitions for

Iteration

Phase

Lifecycle

Ā„

Intended

to

constrain

the

order

in

which

the

activities

are

performed, and to define the lifecycle structure of the process

l

h

d

d f

Ā„

Very similar to their corresponding definitions in RUP

7

Sharif University of Technology

Software Development Methodologies – Lecture 16

SPEM 1.0:

Strengths and Weaknesses

Ā„

Strengths

SPEM

Strengths and Weaknesses

Flexibility and configurability due to the generality of the

d l ( lb i

li

i

d

b

f d

d

metamodel (albeit limited, because of dependence onRUP as a metamodel basis)

Well-defined general framework

Provision of well formedness rules to be observed when

Provision of well-formedness rules to be observed wheninstantiating processes

8

Sharif University of Technology

Software Development Methodologies – Lecture 16

SPEM 1.0:

Strengths and Weaknesses

Ā„

Weaknesses (Contd.)

SPEM

Strengths and Weaknesses

Lack of subtyping for important process components (let

l^

lib

hi h

k

h

d l

alone a component library), which makes the metamodelof very little practical use. Consequently: Ā„

Poor coverage of lifecycle activities

Ā„

Lack of explicit support for umbrella activities

Ā„

Lack of explicit support for umbrella activities

Ā„

Modeling and artefact production issues not explicitlyaddressedaddressed

10

Sharif University of Technology

Software Development Methodologies – Lecture 16

Software and Systems Process Engineering Metamodel
(SPEM 2.0)
y
g
g

Ā„

Adopted by OMG in December 2006

p

y

Ā„

Addresses the weaknesses of SPEM 1.

Ā„

Provides necessary concepts for modeling

documenting

presenting

Ā„

Provides necessary concepts for modeling, documenting, presenting,managing, interchanging, and enacting development methods andprocesses^

Provides standardized representation and managed libraries of reusablemethod content

Supports

systematic

development

management

and

growth

of

Supports

systematic

development,

management,

and

growth

of

development processes

Supports

deployment

of

method

content

and

process

needed

by

pp

p

y

p

y

defining configurations of processes and method content

Supports enactment of process for development projects

11

Sharif University of Technology

Software Development Methodologies – Lecture 16

SPEM 2.0:

Separation of Method Content from Development Process (1)

p

p

( )

13

Sharif University of Technology

[OMG 2007]

Software Development Methodologies – Lecture 16

SPEM 2.0:

Separation of Method Content from Development Process (2)

p

p

( )

14

Sharif University of Technology

[OMG 2007]

Software Development Methodologies – Lecture 16

SPEM 2.0:

Method Content

  • Elements

SPEM 2.0:

Method Content

Elements

l^

bl

f

k

Ā„

Roles are responsible for workproducts

Each work product is the

Each work product is theresponsibility of a single role

Ā„

Process roles perform tasks

E

h

k i

l^

f

d b

E

ach task is only performed by a single role

Ā„

Work products used as inputs to

p

p

tasks and outputs from tasks

Ā„

ā€œSomebody does something thatchanges somethingā€changes something

16

Sharif University of Technology

Software Development Methodologies – Lecture 16

SPEM 2.0:

Method Content

  • Guidance

SPEM 2.0:

Method Content

Guidance

Ā„

Can be associated with any process model element to provide more

y p

p

detailed information about the element to the practitioner

Ā„

Can standalone – does not have to be associated

Ā„

Most often associated with activities and work products

Ā„

SPEM comes with a set of built-in guidance types:

Ā„

SPEM comes with a set of built in guidance types:^

Checklist

Template

Template

ExampleT

l^

t

T

ool mentor

Guideline

17

Sharif University of Technology

Software Development Methodologies – Lecture 16

SPEM 2.0:

Process Patterns

SPEM

Process Patterns

19

Sharif University of Technology

[OMG 2007]

Software Development Methodologies – Lecture 16

SPEM 2.0:

Modeling Enactable Processes

SPEM

Modeling Enactable Processes

20

Sharif University of Technology

[OMG 2007]