adri timp chair, nesma counting practices committee · •formulate draft version •review by fpa...

Adri TimpChair, NESMA Counting Practices Committee

Adri.Timp@nesma.nl

ISMA-3September 18, 2008

FPA applied to UML/Use CasesSIG proposal

Approach

UML and FPA

Brief explanation of the guidelines

September 18, 2008 2ISMA-3

SIG FPA applied to UML/Use CasesPeter Bink, Capgemini

Hans van den Brink, Centric Information Engineering

Robert Louwers, ABN AMRO

William Maas, Info Support

Rogier Oudshoorn, Capgemini

Richard Sweer, Finidy

Wim Visser, Capgemini

Jolijn Onvlee, Onvlee Opleidingen & Advies

September 18, 2008 3ISMA-3

ApproachGoal SIG

• Application of ISO FPA guidelines to UML/Use Cases, no Use Case Points

• Detail Level: Estimated Function Point Count

• Starting point: Acquainted with both FPA and UML

Process

• Literature study: One basic knowledge level for SIG members

• Formulate draft version

• Review by FPA and UML experts: Getronics, Pink Roccade, Sogeti, Equens, ABN AMRO, QSM, Atos Origin, and CapGemini

• Publication

September 18, 2008 4ISMA-3

UML and FPA

September 18, 2008 5ISMA-3

Detail level FPA Behaviour or structure? Diagram Describes

Indicative Behaviour High-level Use case

diagram

Actors, system and high

level functions

Structure High-level Class diagram Overall information need

Estimated Behaviour Expanded Use case

diagram

Actors, system and

functions

Use case Description Actions in a Use case

Activity diagram Actions in a Use case

Interaction Overview

diagram

Actions in a Use case

State machine diagram Actions in a Use case

System-level Sequence

diagram

Actions in a Use case

System-level Collaboration

diagram

Actions in a Use case

Structure Class diagram Information need

Detailed Behaviour Use case diagram Actors, system and

functions

Use case Description Actions in a Use case

Activity diagram Actions in a scenario

Interaction Overview

diagram

Actions in a scenario

Sequence diagram Actions in a scenario

Collaboration diagram Actions in a scenario

Structure Class diagram Detailed information need

Use CasesUse Case Diagram

September 18, 2008 6ISMA-3

Manager

Formulate credit policy

Update customers

Customer systemAnalyze risks

Price agreement

Document the agreement

Salesman

Credit score

« include »

« include »

Customer inquiry

<<extend>>

Use Cases

Actor User

Use case description

Granularity of Use Cases

Storyboards

Include – Extend

September 18, 2008 7ISMA-3

DirectivesUse Case Diagram shows system boundaries

Find the level of the elementary processes

Be aware of alternate scenarios

“Include” UC’s: count when an autonomous process

Storyboards for drop down lists, etc.

Actor is another system? Then interface

September 18, 2008 8ISMA-3

Class Model

• Association

• Aggregation

• Composition

• Generalization

Class/Object relationships

September 18, 2008 9ISMA-3

Bank account

<id> bank account nr.: Num <9>Account type: String <6>Amount: Num <15>

DepositAmount(Amount):RemitAmount(Amount):ShowBalance():Amount

Bank account

Or

GuidelinesPreparatory steps

Determine the Code Data

Key-Key without attributes: does not occur

Key-Key with attributes: include

Investigate the type and optionality of the relationship

September 18, 2008 10ISMA-3

Guidelines

• Mutually a 1 1 logical file

• Mutually a 0 2 logical files

• A 0 on one side? delete rule

Association and Aggregation:

September 18, 2008 11ISMA-3

customer

order

1

1..*

Team

Player

0..1

0..*

Guidelines

• Together always 1 logical file

Composition

• Separate “discrete” items? Then 2 Logical files

Generalization

September 18, 2008 12ISMA-3

Order

Order line

1

1..*

Motor vehicle

TruckCar

FPA applied to UML/Use Cases

Guide “FPA applied to UML/Use Cases”

Free to download:

www.nesma.nl/english

button: Downloads

September 18, 2008 ISMA-3 13