bpm best practices

8/6/2019 BPM Best Practices

1/20

HP Application Lifecycle Management

Software Version: 11.00

Business Process Models Best Practices Guide

Document Release Date: October 2010

Software Release Date: October 2010


2/20

2

Legal Notices

Warranty

TheonlywarrantiesforHPproductsandservicesaresetforthintheexpresswarrantystatementsaccompanying

suchproductsandservices.Nothinghereinshouldbeconstruedasconstitutinganadditionalwarranty.HPshall

not

be

liable

for

technical

or

editorial

errors

or

omissions

contained

herein.

Theinformationcontainedhereinissubjecttochangewithoutnotice.

Restricted Rights Legend

Confidentialcomputersoftware.ValidlicensefromHPrequiredforpossession,useorcopying.Consistentwith

FAR12.211and12.212,CommercialComputerSoftware,ComputerSoftwareDocumentation,andTechnical

DataforCommercialItemsarelicensedtotheU.S.Governmentundervendor'sstandardcommerciallicense.

Copyright Notices

Copyright1992 2010HewlettPackardDevelopmentCompany,L.P.

Trademark Notices

Microsoft and Windows are U.S. registered trademarks of Microsoft Corporation.


3/20

3

Documentation Updates

Thetitlepageofthisdocumentcontainsthefollowingidentifyinginformation:

Software Version number, which indicates the software version. The number before the period identifies the major release number. The first number after the period identifies the minor release number. The second number after the period represents the minor-minor release number.

Document Release Date, which changes each time the document is updated. Software Release Date, which indicates the release date of this version of the software.Tocheckforrecentupdatesortoverifythatyouareusingthemostrecentedition,visitthefollowingURL:

http://h20230.www2.hp.com/selfsolve/manuals

ThissiterequiresthatyouregisterforanHPPassportandsignin.ToregisterforanHPPassportID,goto:

http://h20229.www2.hp.com/passportregistration.html

OrclicktheNewusers pleaseregisterlinkontheHPPassportloginpage.

Youwillalsoreceiveupdatedorneweditionsifyousubscribetotheappropriateproductsupportservice.

ContactyourHPsalesrepresentativefordetails.


4/20

4

Support

YoucanvisittheHPSoftwaresupportwebsiteat:

www.hp.com/go/hpsoftwaresupport

This

web

site

provides

contact

information

and

details

about

the

products,

services,

and

support

that

HP

Softwareoffers.

HPSoftwareonlinesoftwaresupportprovidescustomerselfsolvecapabilities.Itprovidesafastandefficient

waytoaccessinteractivetechnicalsupporttoolsneededtomanageyourbusiness.Asavaluedsupport

customer,youcanbenefitbyusingthesupportsiteto:

Search for knowledge documents of interest Submit and track support cases and enhancement requests Download software patches Manage support contracts Look up HP support contacts Review information about available services Enter into discussions with other software customers Research and register for software trainingMostofthesupportareasrequirethatyouregisterasanHPPassportuserandsignin.Manyalsorequirean

activesupportcontract.Tofindmoreinformationaboutsupportaccesslevels,gotothefollowingURL:

http://h20230.www2.hp.com/new_access_levels.jsp

ToregisterforanHPPassportID,gotothefollowingURL:

http://h20229.www2.hp.com/passportregistration.html


5/20

5

Contents

Preface ................................................................................................................... 6

Analyzing the model information ............................................................................... 7

Model entities as requirements in the ALM Requirements module ................................... 8

Creating coverage for models various use cases ....................................................... 9

Re-Import Models How does it work? ..................................................................... 15

Status view display presenting accurate results ....................................................... 19

Frequently asked questions ...................................................................................... 20

Glossary ............................................................................................................... 20


6/20

6

Preface

ThepurposeofthisguideistohelpyoubuildrelationshipsbetweenALMtestrequirementsand

businessprocessmodelentities.

Examinethefollowingexampleofabusinessprocessmodel.ItwascreatedusingMetaStormProvision:

Figure 1: Sample business process model. The diagram was captured from the Provision tool.

Thisdocumentwillusethisexampletoexplaintherecommendedrelationshipstoapplywhenimporting

modelsintoHPApplicationLifecycleManagement(ALM)andconnectingthemtorequirements,which

willlaterformthebasisfordevelopmentandtestplanning.


7/20

7

Analyzing the model information

Theprovidedmodelincludesadditionalinformationthatextendsbeyondtesting.Whenfocusingon

testing,thefollowinginformationisuseful:

1. ActivityOncethisentityisimportedintoALM,itcanserveasthebaseuponwhichadditionalfunctionalspecificationsareaddedandthefunctionaltestisbuilt.

2. Paththisentityisnotaformalentityinthemodelingtool,butisintroducedinALM. ALMautomaticallyanalyzesthemodelandoffersallthepossibleendtoendpaths. Thesepathscan

thenserveashighlevellogicalbusinessprocesseswhichneedtobetestedendtoend.

3. Modelthiscanserveasabaseforadditionalfunctionalrequirements,nonfunctionalrequirementsandgeneraltestrequirements(suchasperformance,security,usability,

scalability)

Inthissamplethereare7activities,and5possiblepaths.Usershouldaddonlythepathswhichare

relevantfortestingorhavehighbusinesscriticality.

Figure 2: Screenshot from ALM Business Models module. The left pane displays the business process model

tree and the entities structure under the model tree entity.


8/20

Modemodu

Eachimp

Forclaritentity.

TheBusi

represen

Howisth

T

Ain

Thisshar

tofunctio

different

model,cu

Figure 3:

system fol

l entitiele

rtedmodel

wewillnam

essModelsativerequire

etreestruct

hefoldercon

o Belowentity.

ctivitiesare

threediffer

dactivityre

naltestrequ

modelsinwh

stomersare

Screenshot o

der, which c

as req

automaticall

etheserequ

folderinthe

ments.Thes

red?

tainsarequi

eachmodel

ddedunder

ntimported

resentation

irements,wh

ichtheactivi

advisedtou

ALM Require

ntains all the

iremen

createsmat

irementsrep

requiremen

requiremen

ementfore

isasystemg

heActivitiemodels,itw

approachsu

ichinmostc

tyisinclude

ethepath

ments modul

newly create

s in the

chingrequir

resentativetstreecontai

tshaveasp

chmodel(F

oupnodew

folderandaillbereprese

portstheco

asesaresha

.Tospecify

ntity.

. The requir

d representat

ALM R

mentsinth

equirements

nsbydefaul

cialtypean

rexample,

ichholdsre

rereusable.Intedonlyon

nceptthata

edbytheac

niquetestr

ments tree in

ive requireme

quirem

ALMRequir

astheyrepr

allthenewl

icon.

fillOrder_1).

uirementsf

Ifthesameaceinthereq

activitysho

tivityregardl

quirements

cludes the B

nts.

8

nts

ementsmod

esentamod

created

reachpath

ctivityisinclirementstr

ldbeassoci

ssofthe

foraspecific

siness Mo

le.

l

ded

e.

ated

els


9/20

9

Creating coverage for models various use cases

Therepresentativerequirementissimplyaplaceholder(ananchor)formodelentitycoverage.Themain

workintheRequirementsmoduleistolinkotherrequirementsandteststocreatecoverage.

Thissectiondescribesfourpossibleusecasesforconnectingthemodeltorequirementsandtests.As

differentcustomersengagewithALMusingdifferentmethodologiesandconstructtherequirements

hierarchydifferently,thebestpracticesforcreatingtestcoveragevary:

Use Case #1:

CustomerdoesnotusetheALMRequirementsmoduleatall.OnlytheTestPlanmoduleisused.

Bestpracticeforcreatingcoverage:

IntheBusinessModelsmodule,createlinkagebetweentestsandmodelentities(activity,path).

Manuallylinkrelevantteststoactivity,path,andmodelentities.Inthebackgroundthetestsareactually

linkedtotherepresentativerequirementofthemodelentity.ThisguaranteesasingleflowintheALM

system:Model>Requirement>Test.Thisoperationhastheidenticalresulttotheuseraddingtest

coveragetotheentitysrepresentativerequirementintheRequirementsmodule.

Advantages:

Requirementscreationandusageistransparenttothesecustomers.Noadditionalmaintenanceisrequiredofthemontherequirementssideinordertoviewcoveragestatusandcreatetest

setsbasedonthemodelscope.

EnablescustomerstosmoothlyadopttheRequirementsmoduleoncetheirorganizationbecomesmorematureandstartsusingrequirementstocreateapowerfulALMprocess.


10/20

10

Figure 4: Screenshot from ALM Business Process Model. An activity entity is selected. In the bottom-right

pane, the Linkage > Tests tab enables linking tests directly to model entities.


11/20

11

Use Case #2:

Customerhasanexistingrequirementtreestructure,andtestsarealreadylinkedtothe

requirements.Forthepurposeofthisusecasewecanassumethattherequirementstree

consistsoftwofolders:onecontainstheE2EBusinessProcesses,andanotherdetailsthe

functionalrequirementsandspecificationsandassociatedtestrequirements.Duetothispre

definedrequirementsstructuretheuserwouldnotwanttousetheautomaticallygenerated

representativerequirementsstructureprovidedbytheintegration,buthewouldliketokeep

workingwithonlytheexistingtree.Instead,hecreateslinksbetweentheexistingrequirements

andthemodelentities.

Figure 5: General example of an existing requirements structure that the customer would like to maintain.


IntheBusinessModelsmodule,createthelinkbetweenexistingrequirementsandthecorresponding

modelentities.Manuallylinkrelevantrequirementstoactivity,path,andmodelentities.Bylinkingthe

model

entities

to

requirements,

ALM

automatically

identifies

the

tests

linked

to

those

requirements

and

usesthemtodefinethecoverageandqualityanalysisofthemodelentities.

Limitation:

TheModelRequirementssystemfolderandtheautocreatedrepresentativerequirementsplayan

importantbehindthescenesroleinmaintainingtheconnectionsdescribedabove.Thismeansthat

deletingthissystemfolderandrequirements(i.e.therepresentativerequirements)willremovethe

coverage.Thisfoldermustremainuntouchedinthetree,evenifitisnotbeingused.

Advantages:

Useruseshisexistingrequirementstreestructureandbenefitsfromtheexistingcoveragelinksbetweenrequirementsandtests.Therefore,thereisnoneedtocreatespecificlinkagebetween

testsandmodelentities.

Therequirementstreecanmaintainaveryflexiblestructure(freestheuserfromtheparentchildrelationstosupportcoverageanalysis)andALMwillstillbeabletoprovideaggregated

qualityandcoveragestatusforeachmodelactivityandpath,byscanningthelinked

requirementsintherequirementstreetocollectthepass/failstatuses.Thisprovidesforamuch


12/20

12

moreflexibleanalysisthanthechildparentrelationshipthattheRequirementsmoduleenforces

inordertoviewstandardrequirementscoverageandqualityanalysis.

Figure 6: Screenshot from ALM Business Model Module. An activity entity is selected. In the bottom-rightpane, the Linkage > Requirements tab enables linking existing requirements of other types to model entities.

In this use-case the Business Models folder will be added to the customer tree but it is a minor addition

that should not affect the process.


13/20

Use Cas

Custome

therequ

structur

require

Bestprac

IntheRe

locations

Asforad

requirem

directlyt

module)

thisresul

Advantag

Tq

t

Figure 7:

location i

#3:

rhasanexi

irements.T

.Inadditio

entsasahi

ticeforcreat

uirements

intherequir

itionaltests

entsofother

activity,pat

illautomati

sincreating

es:

hefastestwa

ualitystatus

erepresent

Screenshot fr

the require

stingrequir

ecustomer

,thecusto

ghlevelstr

ingcoverage:

odule,physi

mentstree,

whichareno

types(asth

h,andmode

callyconnect

testcoverag

ytocreatec

iew,theBus

tiverequire

m ALM Requ

ents tree und

mentstree

wantsthes

erwouldli

ctureofbu

callydragan

tounderthe

tlinkedtore

customerdi

lentities.Th

thetesttot

fortherepr

veragefor

inessModel

entsinord

irements Mo

er the high le

structure,a

erequirem

ketouseth

sinessrequi

dropexisti

designatedr

quirements:

dinthepast

secondmet

ehighlevel

esentativer

odelentitie

modulewill

rtocreatea

ule. Existing

vel represent

ndonlyso

ntstreeto

eautomati

rements.

grequireme

epresentativ

thesecaneit

)orlinkedin

hod(ofdirec

representati

quirement.

.Whenaske

automaticall

nalysisonco

requirements

tive require

eofthetes

representt

allycreated

ntsfromthei

erequireme

herbelinked

theBusiness

tlinkageint

erequireme

dtogenerat

ydrilldown

erageandq

were moved

ent.

13

tsarelinke

emodel

representa

rcurrent

t.

toexisting

Modelsmod

ebusiness

nt.Inpractic

acoverage

othechildre

uality.

to their new

to

tive

ule

odel

e,

and

nof


14/20

14

Use Case #4:

Customerwantstopartiallyadopttheautomaticrepresentativerequirementsstructureoffered

bytheintegration.Thecustomerseesgreatvalueintherequirementsthatrepresentthe

modelspaths,astheseconstituteendtoendbusinessprocessesintheorganizationthat

requiretesting.Inaddition,sincethisinformationissynchronizedwiththemodelingtool,the

QAmanagerreceivesanupdatedlistofprocesseswhichisbasedonasinglebookofrecords.

Ontheotherhand,regardingfunctionalrequirementsthecustomerwouldliketokeepthe

existingrequirementstreeintact.Thetreewasbuiltcarefullyaccordingtotheapplication

structure.

Customersareadvisedtoadapttheirrequirementstreestructureinaccordancewiththisuse

case.


Useacombinationoftherecommendationsfromusecases2and3.

Activityentities:IntheBusinessModelsmodule,dragrelevantrequirementstotheactivitiesfrom

anywhereintherequirementstree.

Pathentities:IntheRequirementsmodule,eithercreatedesignatedrequirementsofvarioustypesas

childrenofthepathsrepresentativerequirement; ordrag existingrequirementswhich,untilnow,

representedbusinessprocessrequirements,tobechildrequirementsofthepathsrepresentative

requirement.TeststhatarecreatedlatercanbelinkeddirectlytothepathentityintheBusinessModels

module(thisissubjecttothespecificdevelopmentofchildrequirementsunderthehighlevelpath

node,sincetheusermightwanttolinkthetesttooneofthechildren).

Advantages:

Thismethodgetsthebestofbothworlds:Afastconnectiontocreatecoverageforpaths;andtheabilitytomaintainaflexiblerequirementstreestructureforfunctionalrequirementsbased

onapplicationfoldersstructure,andnotrequirementsperlogicalactivityinthebusiness

processmodel.


15/20

Re-Im

WhenRe

Thischap

themode

Figure 7:

Themod

willconta

model,a

entry.

Itisreco

import,c

ort Mo

importinga

terexplainst

l.Assumethi

Sample busin

lhas7activi

in7represe

d3represen

mendedth

angescanb

els H

odeltoAL

hedifferent

sistheorigi

ess process d

tiesand3pa

tativerequir

tativerequir

tyoucreate

ecompared

ow doe

,thefollowi

secasesaro

almodeltha

iagram

ths.Asdiscu

ementsfort

ementsfort

abaselineof

singtheco

s it wor

ngconfirmat

undreimpo

twasimport

sedinthea

eactivities,

e3pathsth

themodelp

parecompo

?

ionmessage

rtandtheco

edtoALM:

oveusecas

onereprese

twillbesto

riortothere

nentofALM

appears:

nsequences

s,theRequir

tativerequir

edunderth

importingm

slibrariesba

15

feachchan

ementsmod

ementforth

modeltree

odels.Afterr

selinefeatur

ein

ule

e

e

.


16/20

Conside

An activ

Scenario:

Modelw

Figure 8:

Effect:

1. 2.

a

3. At

u

a

t

e

the possi

ity was ad

sreimporte

Sample busin

alidateOrd

odule.

alidateOrd

ctivitywasn

a. Iftheassoci

autom

b. Ifthisandth

reim

llthepaths

isactivityin

pdatingand

ctivityinthe

viewpathc

xtended.

le change

ed

dandanew

ess process d

rCreditCard

rCreditCard

talreadyim

ctivitywasa

atedautoma

aticallygains

activityisne

ecoverage

ortprocessi

illbeaffecte

theendtoe

hepathdesc

pathcontent

overage,att

:

activitywas

iagram with

activitywa

nodewa

ortedtoAL

lreadyimpor

ticallywitht

allthecove

inALM,an

illbeblank.

scomplete

dbythischa

ndflow.Ani

riptionwillb

.Directpath

elevelofin

ddedtothe

change

saddedtoth

addedtoth

fromadiff

tedtoALM

eexistingac

agedefined

ewrepresen

Itistheuser

nge:theywil

ternalalgori

emodifiedt

coveragewil

ludedactivit

diagram

emodeltre

eRequireme

erentmodel:

yadifferent

tivityrepres

forthisactivi

tativerequir

sresponsibili

lallbeauto

thmwillide

includethe

lnotbeaffec

ies,thecove

intheBusin

ntsmodule,

model,thea

ntativerequ

ty.

mentwillbe

tytoaddcov

aticallyupd

tifythateac

ValidateOr

ted,butwhe

ragewillaut

16

essModels

NLYIFthis

ctivityis

irementan

createdfori

erageaftert

tedtoinclud

pathneeds

erCreditCa

nyoudrilld

maticallybe

d

t,

he

e

rd

wn


17/20

An activ

Scenario:

Modelw

Figure 9:

Effect:

1. 2.

T

If

n

Nd

3. R

ity was re

sreimporte

Sample busin

uildCompo

uildCompo

heconnectio

theBuildC

orontheco

OTE:iftheeletionwill

Thererequir

Requi

Comp

repre

Comp

oftes

emovingacti

a. Noimb. Recov

andth

c. Irrecocanno

oved

dandanacti

ess process d

entsactivit

entsrequ

nbetweenth

mponents

erageoftho

uildCompoeanpartialc

presentative

ementswhic

ementssub

nentsactiv

entativereq

nents_1wi

sandchildr

vitiesmayaf

pactasthe

erablechang

eautorecov

erablechan

tberestored

vitywasrem

iagram with

ywasremov

irementnod

eactivityan

ctivityisstil

eactivities.

entsactivitoverageloss:

requiremen

hweredragg

tabwillbelo

ity. ALMwill

irement.Ins

llbegenerat

quirements

ectpathsin

removedact

etheremo

eryalgorith

etherem

.Inthiscase,

ovedfromth

change

edfromthe

wasNOTd

thereprese

lvalidinoth

doesnota

ofBuildCo

edanddrop

stuntilafut

notbeable

tead,anew

ed.Userwill

fromBuild

differentw

ivityisnotp

edactivityd

canamend

vedactivity

thepathwil

ediagram.

odeltreein

letedfromt

ntativerequ

rmodelst

pearinany

mponents

edtocreate

reimportw

torestoreal

epresentati

thenneedto

omponents

ays:

rtofthepat

oesnothar

thepathflo

harmsthee

lbedeleted.

thebusines

erequireme

irementwas

erewillben

therimport

illremain,b

coveragein

ichwillcont

inktoanorp

erequireme

manuallydi

toBuildCo

h.

theunique

automatica

istingpathin

Co

Act

r

17

modelsmo

ntsmodule!

removed.

oaffectont

dmodels,th

tany

theLinkage>

aintheBuil

an

tnamedB

ertthecove

mponents_1

essofthep

lly.

awaythat

Build

ponents

ivitywas

moved

ule.

em

e

ild

rage

.

th


18/20

18

Lookingatourexampleabove,onecanseethattheremovalofBuildComponentscausesan

irrecoverablechangeforthethirdpath.Afterthechange,thepathsimplynolongerexistsand

thenewlyimportedmodelcontainsonly2paths.ThismeansthatthepathentityintheBusiness

Modelsmodulewillbedeletedalongwithitsdirectrequirementcoverage.Similarlytodeleted

activities,therepresentativerequirementofthepathwillremain,butwillbeorphaned.

Activity was modified

Scenario:

Modelwasreimportedandactivitywasmodified(Name,properties,additionallinks)

Effect:

NoeffectinALM.Thecoverageandlinkageremainintact.Thepropertiesoftheentitywillbemodified.

(Iftheentityischeckedoutbyanotheruser,analertwillbeaddedtothemodelentity.)


19/20

19

Status view display presenting accurate results

TheStatusviewprovidesfullflexibilityinpresentingdifferentcrosssectionsofcoverage.

Includerequirementchildrencheckbox

Dependingontheusecasethecustomerselectedtoconstructhisrepresentativerequirements,

aggregatedresultsfromrequirementschildrencanbeaddedtothestatuscalculation.For

example:ifacustomeraddedchildrequirementstotherepresentativerequirementsandthose

arecoveredbyteststhenthechildrequirementdoesnotneedtobemanuallylinkedtothe

modelentity.Selectthischeckboxfortheanalysistoaggregatealsotestscomingfromchildren

ofassociatedrequirements.

IncludeRepresentativerequirementscheckbox

Forcustomerswhodonotwanttousetheautomaticallygeneratedrepresentative

requirementsstructure,thischeckboxshouldnotbeselected.Thus,thecoveragefromthe

representativerequirementswillbeignored.

Figure 10: Status View


20/20

Frequently asked questions

Q:WhathappensifIdeletearepresentativerequirementfromtheRequirementsmodule? A: Thecoverageofthisentitywillbelost.Anyoperationthatcreatescoveragefortherelated

modelentitywillautomaticallyrecreateanewrepresentativerequirementandlinkthenew

assetstoit.ThenewrequirementwillbelocatedunderthedefaultlocationoftheBusiness

Modelsnode.

Q:HowcanIextractchangeimpacttestinginformationfromreimportedmodels? A: Forthisfirstrelease,thiscapabilityisnotimplemented.Theuserwillhavetomanuallytrace

changesafterreimportandcreatethetestsetfromit.Forthenextreleaseabuiltinfeature

willbedevelopedtoeasilyextractthisinformation.

Glossary

BPM BusinessProcessModel

Representative

requirement

EntryintheALMRequirementsmodule.Representativerequirementsare

generatedautomaticallyforeachimportedbusinessmodelentity.Theyserve

astheconnectorbetweenabusinessprocessmodelentityandotherALM

entities(requirementsandtests).

Orphanrepresentative

requirement

Ifanentitywasremovedfromabusinessprocessmodel,reimportingthe

modeldoesnotdeletetherepresentativerequirementoftheremovedentity,

asitmayholdcriticalinformation.Itisuptotheusertodeletethosenodes

afteranynecessaryinformationwasmovedtootherplacesinthe

requirementstree.

bpm best practices

Documents