DOORS ChangeManagement

8/17/2019 DOORS ChangeManagement

1/28

© Telelogic AB

Managing ChangeFrom Customer Request to Implementation

Jean-Louis Vignaud & Dominic Tavassoli


2/28

© Telelogic AB

Change is inevitale

• All Projects are subject to change… a high risk challenge – Increasing number of contributors & stakeholders

– Agility needs reactiity

– !sability is key

• "hange may im#act the agreed baseline of $e%uirements – eed a formal organi'ation(tuned #rocess)

– Assess) decide) communicate

• "hange traceability

– $elate #roject *eelo#ment actiities to $e%uirements and"hange +anagement decisions

– ,stablish a full audit trail

– eed to record and manage change im#acting all #roject artifacts


3/28

© Telelogic AB

D!!R"#Change empo$ers %our

Requirements Change Request rocess

• Predefined) customi'able -ifecycles) allo.ing assignment)multi#le reie.ers) electronic signatures

– /eb(based submission) transitions) analysis history) re#orting

– /ork on the $e%uirements is carried out inside *00$1

"hanges are

#ro#osed

against

re%uirements

Pro#osed

"hanges

are assessed

and a##roed

Pro#osed

"hanges

are a##lied


4/28

© Telelogic AB

'or(ing against a Requirement Change

Request

• 1etting the default $"$ indicates that all changes are to betracked against this conte2t

– *00$13"hange builds the traceability re#ort automatically

– ,nforced #rocess control can be actiated


5/28

© Telelogic AB

)nrivalled usailit%

• *00$13"hange brings critical enter#rise functionality .ith noadditional learning cure

• !sers .ork as they normally .ould in *00$1 – "hanges are automatically tracked

• ,ffortless) intuitie change control of4 – $e%uirements edition) creation) remoal

– -ink creation and deletion

– *ocument restructuring

•o constraints ( multi#le #eo#le may #ro#ose changes against

a same *00$1 module

– *00$1 1hareable edit & ,2clusie edit modes


6/28

© Telelogic AB

"treamlining the Revie$ & *pproval

process

• otifications) re#orts andin(tool lists of changes

im#roe communication

• Automatically createdchange(focused ie.s for

easier reie. in *00$1

• /eb ie.s #roide#o.erful) intuitie

enter#rise(.ide reie.

• *esignated reie.ers caneach indicate a##roal and

feedback


7/28© Telelogic AB

*ppl%ing a Requirements Change Request

• 0nce a##roed) $e%uirement "hange $e%uests can bea##lied

• The changes then a##ear in *00$1 for all users


8/28© Telelogic AB

Li+ec%cle Change Management

• *00$13"hange #roides organi'ations .ith much more thana re%uirement change #rocess

• It #roides you .ith a best(in(class) #roen) ,nter#rise(.ide

-ifecycle "hange +anagement solution5 – Po.erful

– 6le2ible

– 1calable

– ,asy(to(!se

• Po.ered by a.ard(.inning Telelogic 17,$87


9/28© Telelogic AB

roviding a gloal vie$ o+ change

"%stem Change Request rocess

"%stem

Change Request

Requirements Change Request

rocess

Changes

Requirement

Change Request The -ifecycle "hange +anagement Audit trail

#roides isibility into the com#lete change

across the ,nter#rise


10/28© Telelogic AB

"%stem Change Management

• Telelogic9s -ifecycle "hange +anagement solution allo.s youto im#lement a central) high(leel) system change #rocess

across engineering & business

– $ecord and manage "hange $e%uests that .ill #otentially im#act

all #roject artifacts

– 1oft.are) hard.are) documentation) !+- models) test cases…

– +ay lead to a change of re%uirements

– +ay lead to im#lementation actiities




"umitting a "%stem Change Request

• 6orms and attributes are ada#table to your needs

"ontrolled)

mandatory fields in

$ed

-ist bo2

selection for

ease of use



,igh level change process

• Im#lement your cor#orate #rocess – "a#ture critical information from key team members across the

globe

Informationca#tured during the

#rocess

Authori'ed

transition ste#s



o$er+ul arent-Child hierarch%

• $e%uirement "hange $e%uests can be children of a 1ystem"$ :or submitted stand(alone;



Integrated Requirements athering

• *00$13"hange also #roides a best(in(class /eb interface forthe re%uest ca#ture and reie. #rocess

– Personali'ed /eb forms

– Trace and document decisions

– $e%uirements organi'ed in *00$1 and allocated to s#ecific releases

– "a#tures the original =oice> of the customer

roduct Revie$ .oard rocess

Customer/eeds0

)ser /eedsRequirements


15/28



Driving and Trac(ing Implementation


"%stem

Change Request

Tas(s &

changes

Implementation

Requests

Implementation rocess

Im#lementation carried out under "+ control4

17,$873"+) "lear"ase…



Requirements Implementation rocess

• "reate im#lementation re%uestsand engineering tasks directly

from the re%uirements

• "om#lete traceability from needsto code

– Im#act analysis

– "ommunication

• Better #roject control – ,nsure you?re doing the right

thing

– $eal(time $e#orting on

#rogress) coerage

– Building your kno.ledgebase



Complete traceailit% and visiilit%

$e#orting aailable .hen deelo#ment

is under 17,$873"+ control



D!!R"#Change implements process

improvement est practices

• *00$13"hange hel#s you stay in control5• $e%uirements "hange "ontrol

– 1calable) enforceable "++I change #rocess :com#any(.ide

change control board…;

– Im#act analysis and traceability of a 1ystem "hange $e%uest• $e%uirements 8athering

– Im#lement a o#en to all) formal) re#eatable but easy to use

#rocess

• $e%uirements *rien *eelo#ment – 0ffshore deelo#ment #rocess control

– @uality initiaties certification :"++I…;

– $egulatory certification :*0CB) 1arbanes(02ley…;



I n t e g r a t e d

$ e % u i r e

m e n t s

8 a t h e r i n g

$a. Information

12tending Li+ec%cle Change Management

$ e % u

i r e m e n t s *

r i e n

* e

e l o # m e n

t I n t e

g r a t e d

* e f e c t

+ a n

a g e m

e n t

$e%uirements *rien Testing

!ser $e%uirements

1#ecification

6unctional

1#ecification

*esign

1ystem Build

Integration

testing

1ystem testing

Acce#tance

testing

"hange



D!!R"#Change 3e% .ene+its

• Reduce pro4ect ris(s and increase customer con+idence

– "lear im#act assessment and understanding

• Improve productivit% .ith focused deelo#ment teams and reducedre.ork risk

– "learly defined and communicated re%uirements changes

• Improve process control

– Trusted re#eatable "++I #rocess and automatic traceability bet.een

re%uirements and related deelo#ment actiities

– Information is aailable for s#eciali'ed) distributed teams

• Reduce scope creep and streamline deelo#ment – $eal(time isibility of the relationshi#s bet.een re%uirements and deelo#ment

actiities

– Track 1ystem "hange $e%uests all the .ay to the im#act to $e%uirements

base and im#lementation information



3e% .ene+its % Role

• +anagement – ,2tended "hange +anagement coers the full lifecycle)

#reenting loss or miscommunication of fundamental re%uirements

changes

• Analyst & *00$1 user

– Intuitie change control .ithout the #roductiity hit or learning ga#

– ,arly im#act analysis of re%uirements changes inoling all

releant stakeholders

– $eliable re%uirement change #ro#agation after a##roal

• *eelo#er – $eleant information aailable fast

– A##roed re%uirements changes are clearly and efficiently

communicated) reducing risk of re.ork



3e% .ene+its % Role

• @A3Tester – A##roed re%uirements changes are clearly and timely

communicated to the Test team) im#roing efficiency

• Administrator

– "om#any(.ide access for submission) discussion) reie. andre#orting

– 1tate(of(the(art features such as electronic signature) user(tuned

interfaces and multi#le reie.er system) as .ell as the security

and #rocess control leels) out of the bo2


25/28

© Telelogic AB

• 6ull /eb(based interface

• "om#lete .ith #redefined re#orts &

#rocess tem#lates

• "ustomi'able .orkflo.) submission)

and transition forms

• A##roal management

• Attachment su##ort

•


26/28

© Telelogic AB

1nterprise "calailit%

• o $estriction for #latform su##ort :!IF or /indo.s;• ,erything on one serer class machine

• 1erer Tuning to ensure good #erformance oer a large userbase :GHHH total users) DHH simultaneous actie users;

• o de#endency on .eb technologies :A1P or II1; to limit#erformance) iral infection) or security breaches

• 1u##orts


27/28

© Telelogic AB

• Predefine #rocess tem#late that is both e2tendible & customi'ablethrough the .eb(based interface – Add 3 modify 3 delete attributes

– Add 3 modify 3 delete lifecycle state

– "reate multi#le lifecycles based on the re%uest ty#e

– Add 3 modify 3 delete forms

rocess Fle2iilit%

• 17,$873"hange API – Integrations

– *ata +igration

– otification

• Built(in Process "ontrol and+anagement to ease

administration


28/28

.uilt-In Reporting6 7uer%ing6 and Charting

•Pre(defined or user(defined re#orting consistency on eery

#latform

– $e#ort and @uery =builder> allo. each user to easily create and

share re#orts and %ueries

– o de#endency on Grd #arty re#ort tool :ie "rystal $e#orts;

• $e#orting and @uery into "+ database• Proides built(in 6ull Te2t 1earch ca#ability that can be used

across multi#le databases

• 1u##ort to allo. charting of grou#s of states – :0#en s "losed trend;

• Promote #redefined charts for re#orts :matri2) #ie;

• "harts and $e#orts are #latform inde#endent

DOORS ChangeManagement

Documents