496 IAG Exec Guide to Biz n Software Req 081707

8/14/2019 496 IAG Exec Guide to Biz n Software Req 081707

1/13

!!!!


2/13

!"

"#$$$%&

$

'!"#((

$$&$()#

!"*$$$(&$

$+

#$$((

'$,

$$&$(

$',

%&'(#-$

(

$.

/(!#(0

12 3!"# $

/4%.$$0 5

'..$( 6*7)' 6

7 8

.$+.$

9

.$+.$$7$% :

;


3/13

%&!'

"

?&$("&$

9=@-$.+

/$6@-$($&8@

$$-$$(2$-&$(

$$

'-$$&$7

$&6@$$

$3

$+$%$

$&$&$%$(-$$$

"$$*=@$$(

A'-$$$%$(&-&$%$($

("

)*

+())*

+

How does business performance in defining business requirements affect otheroperational areas?

)$$&

$($(

($$(($($($

?$($$$

$

(&$($

4%$(

$$$$

3 )$$%2$$($

$($

$$

$$$-$(

$(

$($$$

$((&&

$$$$

*"B==8C

&.B==5C

3"(B==C


4/13

3

,!-

(./0+!

1+))

1+!

2+()

0)

)))

))

+34

($$$&$

$

1$(&

$($

$$$(

$$(

$

$$(&

-+

$)+$(

$($

$$+($($$ &'+$$($$$

Business Requirements:The Holistic View

(4!$

#;;B..C&

$

'$

$(

2(

($*

8%

5*$*'$(&()

."

7$$

1".7

>""

D

$

.$

.($$)

>-

$$

$)%

&'

!""#


5/13

5

%516!!7

$((-$$&

-$$($$($%6

($%%$$-$

$(BC$$$

?&$($$$(

((

(

/$$(0

'%$&

$$-$$(

'$(&$(($$-"

$$$(%%$

$?&($(($

$($$$$(E%

&$$$$$

$&$$$%$$(

3 '$-)

&$&$

&$(&$$

$($($('$$&

$$2$(

5 E%$%$$-2($

%&$""$

($$

$(*$$(F/?'G&F?>/G&

%$$%

$(&&&)

('$$)%$$$

%-$$$$$

$($)$$$(

-.-.-./0)1!

6D$4&==6+%$$(

&$$

$$($

Number of Departments/Stakeholders Effected

High

Low

Changes to asingle

departments

legacy system

Single Window

Low High

AnticipatedComplexity(Un-Familiarity of

Business Requirementsto Project Team)


6/13

6

/!

70'$$(*

$$&$$%

$'

$$$$((&$(

>)$$

"%

(7$(&$$$$(

((/(0((

$+$%$%$$+

o 4$$

o 4$($$

o 4$

o 4$$6=6(o 4$$9H5

o 4%$$($$(

o 4$%$

/$($&($$$&

$(=($$($$$

I$)-=-("

$$(A&(

$9==B$$$%$$($CJ.$(&

($&

($'&$$9&===

%(

Effective Information Format Recognizes Three Audiences

/#+$(($

$&$%$(&

$$($$($

$&$$

$($(

B14ED$($(1

.C&$($"$$$(

&$&$("$

413(+

$&*$$(K$

$($($$($

$$%>&(

(

*"234

$$$$

%&%&%&%&

''''

$$$$

%&%&%&%&

''''

((((

$$$$

)')')')'

((((

$$$$

)')')')'

((((

$&$&$&$&

****

((((

$&$&$&$&

****

))))

."

7$$

1".7

$)%


7/13

8

(

$+ *"7&$(

$+$

$0/0/

B(C$(0?

(%($0/

($0*$ 5 *$$

$$("$$(&$($$$

$$B$C3 '*$&&

-$%$

'($($"$&

$$&(-*$&-($($$'

E'==($%$

$$(-&-

$((

#"-5.#

)*(#1.14EB$$C)(

$$

)

$

$B1.C&$$$(%

$

'$($

$((

$(*&-$

B$(!$(#C$$((

$

*6

,7)"

?$$

0BI(+!4#(%&&

$C *$(

-0B4+

(%$$$(FG

(%C3 *$

-

$0B%(!$$(#&

!$$#4($(($(

$(C

."

7$$

1".

7

$)%


8/13

9

"

!7

FD>AG2-%$"

7$&/88"

$()&&$

&&$$")$$$

(2%&&"$&

$$$$$"$

F*$G&&

($$/

-L6$$L6==&===-$($

-$(0*.$$

$$$+$($&

$

+

'($

!#0$(

$(#$(

?$0

$(%&&

-

#$$

))'$&$1B1C&'DB$$C&$$&"

$$%-"$$$

$(

$/

$$

o /$$&1&1.$$M:=@

o '$$$$

$(

$

*$$-&$$B$$C

$%$%

&L$$-

L3==&===($(-

88

>""

D$

.$

$$

9$

*

((

BC

(

)%"$$$K(

BC(&"B

(C

K3 'BCB&

(0C5 /$$"

$(B&F(JGC

6 $

8 D

BC$

9 A"$

$&(K&

&


9/13

:

"(!1

$%$+

/$$($0

&;3==*-

$$($

%-$($$$$

$(%

$$($

"%)(-

$$$($-&($

($$$$)(

$$

$$

>$-$+3=@BC$-L6$$&&

&L6$$$$$(

/$+L6$$

%L3L6$$0*==&.(

-6@

($$$(=@

$

%$$(

(&6@$$(

+ E($$$

$

%$$$

$

$

($$

(&$$

3 )$$$(!

#((

$()

)

($$

5 $($$$$$(

:;


10/13

;

!7

'($%&*%+F%

$0GB$

(C>$(==

$

7)$

(*($

$($#BDE.C(&"($$

-!#&$'&

$$$)(5=

-$$()$($*$(

%$(&%$$(&

$

!!!!" .$($$)(-

$%($$(

"B

C$$(-'($(&N

D*A&)$%$

*$&(%$(

*$(($(&

%(1$(&$

$$($(()$$

$$7$+

4$

3 4--

5 .$($

6 $$(

#$%

-$$!$$(#

($(

B!$(#C*$$+

2$(+ -%$3 *-7$&$"

$

5 >2($$

6 >2&)$ +

,7'

" .

$$-

-0BI(?+

C /$(

0B4+&

)C

4>)

.($$)>-

&'


11/13

=

9(7/!

$$&&

-$%(-$($$(&$%&

$)$$(

(B%((C$

?.5##5

E%($(&$($(&

$$$(1$

&$

*#%$$'$%#%

$DE.

'$$$)-$((*L6=&===&L6==&===

3 /8"'$%8(

(

5 '$(!#(BC!G

$$B$C

6 .($$)(

8 $$$

/%$&

$

9 O*$$$(

'$!

*:=$8

(($+

89@%

3=@5=@$$9

;=@:

36=@(

*$(&*).44$$$$

.44$$.44$$3&$(

)$$(

8D$&&B;;C7#*4&

BI$BC9'7E("*DB;;;&4C&'.

*"4*

4

:P&.B;;8CFD$(G&.BI$;&A5C


12/13

:7&;'

Number of Departments/Stakeholders Effected

High

Low

Changes to asingle

departments

legacy system

Single Window

Low High

AnticipatedComplexity(Un-Familiarity of

Business Requirementsto Project Team)

Do you have a test forcompleteness?

Test projects over $5M formally. Improve the completeness of

elicitation from SMEs in sessions

++++ ,-,-,-,-

Q 76@-$8@-$$(2 $-&$($$&==5

Q $$$-7$&6@$$$"&==

Q $)$-6@RRBP;;8C6=@$%$($BD$&;;C

Q *:=$(& BD$&;;C

Q B$(C$$(($$(3=@5=@BDD&;;;C

/&$$(($$($-3=@5=@%

Q /*).44.44K.44.443&)(B89@C$$($-B?$&;;5C

.

/

Do you measure requirementsrisk on projects?

Do your trouble spots tend tobe the upper right corner?

Do you change the process,format or content expectationwhen dealing with projects inthis upper corner?

Do you utilize a structured format for requirements? Is the format designed for different users with a different purpose Does the format decompose easily from one stage of the SDLC to the next. Does a blueprint get created which enables easy comparison from one divisions results to the next.

Get an efficient way tocrystallize every project

SMEs are the scarceresource: design theprocess to optimize use

Can you estimate theamount of time andresource needed to executea requirements gathering

initiative?

Effective and efficient requirements must:Start with a Template: that clearly defines a format for content designed for use by a specific user. And also has;Complete Content: this content has specific characteristics, and is measurably complete. And;Uses an Efficient Process: a companys subject experts are its most limited asset.

4>)

."7$

$

1".7

>""D

$

.$

.($$)>-

$$

$)%

&'

)*!""#


13/13

Documents

496 IAG Exec Guide to Biz n Software Req 081707