11
The Transition from Business Modeling to Requirements Specification Svatopluk Štolfa Monday, August 29, 2022 VŠB - Technical University of Technical University of Ostrava Ostrava FEEI, Dept. of Computer Science

The Transition from Business Modeling to Requirements Specification Svatopluk Štolfa Tuesday, August 18, 2015 VŠB - Technical University of Ostrava FEEI,

Embed Size (px)

Citation preview

Page 1: The Transition from Business Modeling to Requirements Specification Svatopluk Štolfa Tuesday, August 18, 2015 VŠB - Technical University of Ostrava FEEI,

The Transition from Business Modeling to Requirements Specification

Svatopluk Štolfa

Wednesday, April 19, 2023VVŠŠBB -- Technical University of OstravaTechnical University of Ostrava

FEEI, Dept. of Computer Science

Page 2: The Transition from Business Modeling to Requirements Specification Svatopluk Štolfa Tuesday, August 18, 2015 VŠB - Technical University of Ostrava FEEI,

Business Process and Use Case ModelBusiness Process and Use Case Model

BP is a set of one or more linked procedures or BP is a set of one or more linked procedures or activities which collectively realize a business objective activities which collectively realize a business objective or policy goalor policy goal

UC model - examines the system functionality from the UC model - examines the system functionality from the perspective of actors and use casesperspective of actors and use cases– Actor:Actor: someone (user) or something (other system) that must

interact with the system being developed– Use case:Use case: a pattern of behavior the system exhibits. Each use

case is a sequence of related transactions performed by an actor and the system in a dialog

Page 3: The Transition from Business Modeling to Requirements Specification Svatopluk Štolfa Tuesday, August 18, 2015 VŠB - Technical University of Ostrava FEEI,

Activity and Use Case Diagram NotationActivity and Use Case Diagram Notation

Activity1

[condition2]

[condition1]

Activity2 Activity3

Activity4

Ref.: Activity diagram for Activity2

Initial StateEnd State

DecisionBlock

Note

SplittingTransitions

JoiningTransitions

Action State(Activity)

ControlFlow

Actor1

UseCase1

UseCase2

UseCase3

«extends»

<<include>>

Use Case

ExtendRelation

IncludeRelation

Actor

Page 4: The Transition from Business Modeling to Requirements Specification Svatopluk Štolfa Tuesday, August 18, 2015 VŠB - Technical University of Ostrava FEEI,

Business Process Definition

Define business processDefine business process– Example:Example:

Returning processReturning process Lending Process Lending Process

Modify BPModify BP– Exclude activities that will not be provided by Exclude activities that will not be provided by

systemsystem

Page 5: The Transition from Business Modeling to Requirements Specification Svatopluk Štolfa Tuesday, August 18, 2015 VŠB - Technical University of Ostrava FEEI,

Business Process Definition - exampleBusiness Process Definition - example

check items

[something was returned]

[customer has selected something]

register customer

[customer is not registered]

find customer

[customer has not selected anything]

[customer is registered]

fine

[not on time or damaged]

[wants return]

[nothing to return]

[on time and not damaged]

[nothing to pay]

[something to pay]

bill

customer enters return items

selecting

lend items

payment customer exits

Page 6: The Transition from Business Modeling to Requirements Specification Svatopluk Štolfa Tuesday, August 18, 2015 VŠB - Technical University of Ostrava FEEI,

Mapping several activities to one use caseMapping several activities to one use case

check items

[something was returned]

[customer has selected something]

register customer

[customer is not registered]

find customer

[customer has not selected anything]

[customer is registered]

fine

[not on time or damaged]

[wants return]

[nothing to return]

[on time and not damaged]

[nothing to pay]

[something to pay]

bill

customer enters return items

selecting

lend items

payment customer exitsLending

Returning

Page 7: The Transition from Business Modeling to Requirements Specification Svatopluk Štolfa Tuesday, August 18, 2015 VŠB - Technical University of Ostrava FEEI,

Mapping one atomic activity to one use caseMapping one atomic activity to one use case

check items

[something was returned]

[customer has selected something]

register customer

[customer is not registered]

find customer

[customer has not selected anything]

[customer is registered]

fine

[not on time or damaged]

[wants return]

[nothing to return]

[on time and not damaged]

[nothing to pay]

[something to pay]

bill

customer enters return items

selecting

lend items

payment customer exitsBill

Fine

Check Items

Find

Register

Page 8: The Transition from Business Modeling to Requirements Specification Svatopluk Štolfa Tuesday, August 18, 2015 VŠB - Technical University of Ostrava FEEI,

Sequential PatternSequential Pattern

Organize use cases derived from sequential activities by Organize use cases derived from sequential activities by “include” relationships.“include” relationships.

Activity2

Activity3

UseCase1

UseCase Activity2<<include>>

UseCase Activity3

<<include>>

Page 9: The Transition from Business Modeling to Requirements Specification Svatopluk Štolfa Tuesday, August 18, 2015 VŠB - Technical University of Ostrava FEEI,

Optional PatternOptional Pattern

Organize use cases derived from optional activities by “extends” Organize use cases derived from optional activities by “extends” relationships.relationships.

[Cond1]

UseCase1

UseCase Activity2

Activity2«extends»

[Cond2]

Page 10: The Transition from Business Modeling to Requirements Specification Svatopluk Štolfa Tuesday, August 18, 2015 VŠB - Technical University of Ostrava FEEI,

Applying Patterns to ExampleApplying Patterns to Example

Operating Personel

Lending

Find

<<include>>

Register«extends»

Bill

<<include>>

Returning

Check Item<<include>>

Fine

«extends»

Page 11: The Transition from Business Modeling to Requirements Specification Svatopluk Štolfa Tuesday, August 18, 2015 VŠB - Technical University of Ostrava FEEI,

ConclusionsConclusions

Analysts may use this method for support their Analysts may use this method for support their intuitionintuition

Future research is focused on improvement, Future research is focused on improvement, extension and formalization of this methodextension and formalization of this method

Method for semi-automatized use case Method for semi-automatized use case creationcreation