Mc Lc

CHNG I. TNG QUAN V YU CU PHN MM V QUY TRNH .........................................5

1.1

1.2

Hy nu bn cht ca yu c u ph n m m .......................................................................................5

1.3

Nu

1.4

Hy nu cc thi quen tt v thi quen khng tt trong cng ngh hc yu c u ph n m m ..........6

u ph n m m nhn t pha khch hng .........................................................5

1.5

1.6
1.7

.6
........7

M t Quy trnh cng ngh hc yu c u ph n m m (Requirement Engineering Process)..............8

1.8

................................................................................................10

CHNG II. PHT HIN, TNG HP V PHN TCH CC YU CU PHN MM ..............11

1.9

1.10
1.11

Trnh by cc yu c

...........11

........................................................12

nh nhim v v ph m vi ca ph n m m ....................................13

1.12 Trnh by quy trnh thc hi (

b ),
m v nh ng k thu
x
nh yu
c u ph n m m Phng vn (interview).......................................................................................................14
1.13 Trnh by quy trnh thc hi (
b ),
m v nh ng k thu
x
nh yu
c u ph n m m H i tho ............................................................................................................................15
1.14 Trnh by quy trnh thc hi (
b ),
m v nh ng k thu
x
nh yu
c u ph n m m Brainstorming ...................................................................................................................16
1.15 Trnh by quy trnh thc hi (
b ),
m v nh ng k thu
x
nh yu
c u ph n m m Storyboarding ...................................................................................................................17
1.16 Trnh by quy trnh thc hi (
b ),
m v nh ng k thu
x
nh yu
c u ph n m m p dng Usecase ..............................................................................................................17

1.17 Trnh by quy trnh thc hi (

b ),
m v nh ng k thu
x
nh yu
c u ph n m m Prototyping .......................................................................................................................19
1.18

.........................................................................................................................................20

1.19

(
b

..................................................................................20

)
1.20
1.21

b c (quy trnh) Phn tch cc yu c u ph n m m ................................................20

Nu cc k thu t p dng trong Phn tch cc yu c u ph n m m ...............................................23

1.22
tiu ch

.............................................................23

1.23

trong BTL .................................................................................................................................................24

H G

C T CC YU CU PHN MM .............................................................................25
c t cc yu c u ph n m m .....................................................................25

1.24

Nu cc yu c u c

1.25

Nu khi nim v thnh ph n c

1.26

Nu tn cc bi u mu c

1.27
R

Trong cu trc c
c hi

1.28

Nu cc k thu t vi

c t yu c u ph n m m ........................................................25

c t yu c u ph n m m (theo IEEE v CMU) .................................26

c t yu c u ph n m m (SRS) System Requirement v Software

c t v tr no trong ti liu SRS. ...............28
c t yu c u ph n m m ...........................................................................28

1.29

1.30

.................................................33

1.32

.........................31
.......................................................33

1.31

1.33
1.34

..............................40

..............................41

x x
(
)

..................................................................................................................................................42

1.35

trong BTL .................................................................................................................................................43

1.36

trong BTL .................................................................................................................................................50

CHNG IV. DUYT V KIM SOT CC YU CU PHN MM ...........................................52
1.37

u ph n m m .......................................52

Phn bit cc khi nim Ki m th

1.38 T i sao c n ki m th
u ph n m m. Nu tn m t s
m th
yu c u ph n m m thng dng m em bi t. ..............................................................................................53
x x
x x
...............................................................................................................................54

1.39

1.40

...................................................54

1.41
1.42
1.43

....................55

.......................................................................................................................................55

.......................56

1.44
b

1.45

....................56

.....................................................................................................58

Kim ton: .....................................................................................................................................................58

S dng ng c s:...................................................................................................................................60
Thay i yu cu v cc vn v yu cu ngoi .........................................................................................61
b)S dng cc yu t bo tr cho Thay i v cc vn .........................................................................62
1.46

Ki m th (testing) yu c u ph n m m ..........................................................................................63

CHNG V. CC K THUT NNG CAO CHT LNG YU CU PHN MM ..................64

1.47

1.48

..........................................................................................................65

1.49

K thu t qu

1.50

t ca yu c u ph n m m. .........................................................64

i yu c u ph n m m ...............................................................................66
u ph n m m theo cc thu c tnh ch

1.51

u ph n m

ng ph n m m ................................67

m bo cc yu c u ph n m m ..............68

u ph n m m .................................................................68

1.52
1.53

1.54

..............................................69

.................................71

C UH I

N TP

N H C IT

PH N TCH CC YU CU PHN

CHNG I. TNG QUAN V YU CU PHN

V QUY TRNH

1.1 C

.
I EE.

(1993) :
)

(1994) :

(1)

(2)

(1997): Y

(1)

x
x

1.3 N

b b
(3)
(2)

1.2 H

1.4 H

.Q

K
D

1.5 N

TBD( Tobe determined).
D
b
x

(1)

chnh xc

b
1.6 N

.P

(note)

:
a) Phn lo i theo yu c u ch

.
- Cc yu c u ch
nh ng ch
n m m s thc
hin. V d
bn hay thu tn hiu.
- Cc yu c u phi ch
rng bu c ca
gii php thc hin. C th gi yu c u phi ch
u
v tnh rng bu c v v ch
ng ph n m m.
b) Phn lo i cc yu c u ph n m m theo ngun gc t m t hay nhi u
yu c u c
c cc thu c tnh ni bt (emergent
property), ho
ch u
ng ca ph n m m b

i din
s dng (stake holder) ho c m t s ngun khc:
emergent property: C m t s yu c u ph n m m s c
u khng th x
nh cho m t
thnh ph
, m cn ty thu
p
cc thnh ph n trong h thng. V d
u ca m t trung tm
g n tho i (t
) ph thu c vo s k t h p ca h thng
telephone, h th
u kin khc. Cc emergent
c bit ph thu c vo ki n trc h thng.
c) Phn lo i theo cc yu c
t ra cho sn ph m ho c l trn tng tin
trnh. Cc yu c u trn cc qu trnh pht tri n khc nhau s c th
nh ng rng bu c b i la chn ca nh
i ti tr (contractor), ho c
l nh ng chu
t ra.
d) Phn lo
n m m:
ng, cc yu c
n l nh ng yu c u quan tr
c xy
dng da trn m t s y u t
y nhi ,
mong mun, ho c tnh
c hay khng bt bu c.

e) Phn theo ph m vi yu c u ph n m m: Ph m vi yu c u ph n m m

ng ca yu c u ln ph n m m v cc
thnh ph n ca ph n m m.
f) Phn lo
d bi
ng/ tnh
nh (volatility/ stability): M t
s yu c u ph n m m s
i ca ph n m m, v th m
ch ngay c trong qu trnh pht tri n ca yu c u ph n m m. Chng ta c
th phn lo i cc yu c u bng cch thng k nh
i m yu c u
c th pht sinh.
,

,
b

: Guide to the Software Engineering Body of Knowledges 2004

39 202

,
b
b

1.7 Q
Process)

(R

HNH 1-2


K
-

sau.
X
D

1995)

(R

HNH 1-3. Bin phn chia gia pht trin yu cu v qun l yu cu.

,
) K

,
,

(
b

Requrireme
(
b

b
10

1 0)
,b
b

,x

b 1 1
b 1 1

By

1.8 N

i s dng:

Cung cp yu cu cng vic(Business Requirement): th hin cc mc tiu

yu c u m c cao ca t ch c hay khch hng v kh
,
m vi ng
dng v gii h n ca ph n m m; cung cp cc thng tin v tng nhim v c
th m h s lm vic vi ph n m m
Yu cu ngi s dng (user requirement): th hin cc nhim v c th m
NSD c n ph
,
c vi ph n m m.

ng,tha th n v
i pht tri n cc yu c u ph n m m.
- N i pht tri n:
Pht hin cc yu c u
Phn tch cc yu c u

c t cc yu c u
Ki m th cc yu c u

:
- N i s dng: c
ng ti

ph n m

i qu cao ho c ch
t cod

n qu trnh pht tri n

ng yu c

ngh rt kh chp nh

PTV
Cc yu c u ph n m
nh p nhng
a cc nh phn tch: lm l i yu c u ph n m
ng
chi m khang 40% qu trnh xy d
70, 80%
c tnh xy dng
l i c th d
n cc l i

D
ng yu c u qu ngn gn m khng miu t k

chng l g
- N i pht tri n:c
ng ti

:
Phn tch
c cc v
Hi u bi t v nhu c u s dng
Hi
c h thng
Hi u ph m vi qun tr
Tinh chnh cc tnh
h thng
CHNG II. PHT HIN, TNG HP V PH N TCH CC YU CU PHN

1.9 N

1.

2. Ngu

x
nh yu c u ph n m m
K
t phng vn
K
t h i tho
K
t BrainStorming
K
t storyBoarding
K
t thu t Use Case
K
t Protopyting
n gc yu c u ph n m m

1997

2b

1
1
b

1
,1

1.10

(1)

(2)

(1)

(2)

Phng vn
T ch c h i tho
Brainstorming v Idea Reduction
Storyboarding
p dng cc Use-case
Prototyping

i tng
tham gia
Loi yu
cu
Ni dung
chun b
nh gi
phng
php

Khch hng,

b
lin quan

Brainstorming
b
quan

,
qu trnh
b
cng phu

Use case
K

Prototyping
,
khch hng

Storyboarding
,

b
, b

,
,

xc

M hnh
Use case

b b

case chnh
xc, l

chnh xc

1.11

Trong pht

,
w

,

b
b

b
b

,
,

Ch
ng th b gii h n b i th i gian (c
)
c nh), v th ph m vi kh thi chnh l hnh ch nh t mu trng.

N u hi
i phi b
c tnh ca h thng bng vi ti nguyn
trn th i gian sn c th d n c ph m vi kh thi.
ng trong cng nghip, cc d
T

1.12

b
x

b ),
P

u l d

t ph m vi.

w)

b
:

?
- Khch hng l ai?
c khc nhau khng?

(
)

:
b

- G

(K

thng tin trong lc ny).

1.13

b
x

b ),
H
o

1. Quy trnh thc hin

b H

o
b
o
b
b

o
b

o K
(w
):

2
w
-up materials:

b
b

,
, b

,b
x
,

,b

,
,

b

b
f
(

):
o
b
,
x

o

o
Ch
ck
x
ng s ng lng hay xy dng
nhm v ng chc.

c c cc thnh vin trong nhm v ngoi nhm tn

trng.

v
i m t vi nh ng thch th c trong h i tho.
H

o Brainstorming
o
b
cc

2.

:
,f

,f

- H i tho yu c u c l l k thu t m nh m nh
g i ra cc yu c u
- N t p h p cc bn lin quan l i vi nhau trong th i gian ng
p
tru
- Vic s dng m
u khi n bn ngoi c kinh nghim trong qun l
yu c u c th m bo s thnh cng ca h i tho.
- Brainstorming l ph n quan trng nht ca m t h i tho.
3. K thu t

1.14

b
x

b ),
B

K thu t ny c nh ng l i ch chnh sau:

Khuy
c mi thnh vin tham gia.
Cho php cc thnh vin tranh lu n vi nhau v cc ki
u phi ho

c h i tho khng b
Din ra nhanh chng.
i php kh thi cho v
.
Khuy

,
,
nh:

K
c php tranh ci, ph bnh gay gt.
T do sng t ,
ng.

ng cng tt
Nghin c u t ng h p l
ng hay.

xut.
n.

1.15

b
x

b ),
b

:
3

b
:G

:
:

:
b

:
K

b
K

1.16

u ny.
b

b
x

b ),
d

U -case.
U

,
b

U
,

(
U
)
U

b
U
U
U

U -case:

U H
):

U

,b
b

b
b

- Tm ra cc tc nhn(Actor) v cc use-case
o

b
)
o
U

U
U

b b

U -case

U -case
- K
:

),
(

)b

(X

1.17

b
x

b ),
P

:
x

fw

13

b
b

w w ,

1.18 N
.

:
??????

1.19 N
b

V )

D liu v ki m sot lu ng (data and control Flows)

Cc m hnh tr ng thi (state models)
D v t s kin (Event tracing)

i dng (user interaction)

ng (object models)
Cc m hnh d liu (data models)

M hnh ha use case

M hnh ha nghip v

M hnh ha d liu

N
-

d
M hnh ha use case
M hnh ha nghip v
M hnh ha d liu
T

1.20

b (

)P

Phn lo i cc yu c u ph n m m:

.T
.

BTL (V

C
C

M hnh ha khi nim:

,
,

:
-

hng

- Ph b

2000

1.21

1.
2.
3.
4.
5.
6.
7.
8.
9.
10.

)
(F

(D

)
(G

)
(f w
))
( ntity relationship models)

(Obj -oriented analysis)

(
)
(D f w D
)
(

1.22

Mt thut ng khc c s dng cho ch ny l conflict resolution .

iu quan tm ny gii quyt vn vi cc yu cu m s xung t
xy ra gia hai yu cu ca cc bn lin quan cng cc tnh nng khng
tng thch , gia cc yu cu v ngun lc hoc gia yu cu chc
nng v yu cu phi chc nng.
Trong tt c cc trng hp , n khng thn trng cho cc k s phn mm
lm cc quyt nh n phng v do n cn thit tham kho t cc
bn lin quan t c mt s ng thun trn s tha hip thch
hp.
S dng Use Cases
h tr cc hot ng thit k v m ha, cc Use Case pht
trin trong cc hot ng suy lun hn l xy dng y .
Cc Use Cases thch hp nht khi h thng giu chc nng v
phi h tr cc loi ngi dng khc nhau.

 Cc Use Case khng c hiu qu khi p dng n h thng vi

mt vi hoc khng c giao din ngi dng ti thiu, ch yu l
nhng yu cu phi chc nng v nhng hn ch khi thit k.
thm

1.23 C
d

A
BTL

:
1. Xem xt c

t ca yu c u ph n m m
S dng c a s Hierachy. Khi la chn 1 Requirement, ta s x
c cc thng tin v :
Quan h phn cp ca Requirement: cho bi t n l con ca cc Requirement
no, cha ca cc Reqiurement no, quan h thu c lo i no (s h u hay k t t p)

Quan h v
t ca R
:
t b i cc Element no. N u
Requirement c cc Requirement con, EA c th chi ti t vi
t ca tng
R

2. Phn tch s ph th c ca yu c u
S dng ma tr n quan h (Relationship Matrix): thng qua c a s Relationship Matrix.
Cho bi t quan h gi

ng trong 2 package

3. Qu
i
S dng c a s Audit View: ghi chp l
Kch ho t Audit View:
M c a s Audit View
Chn Audit Settings
Enable Auditing

4. Lp bo co
S dng menu Project | Documentation

c hin.

L
R

ng : thng tin v Requirement v cc

ng. C nhi
nh d
bn khc nhau
:R
x F
,H
,
Bo co quan h
t
Bo co quan h ph thu c

H G

YU U H

1.24

c t

Khng ph thuc vo cc yu cu c tm c ra hay xy dng nh th

no
Trong c t phi nu c c business requirement , phm vi ng dng ,
gii hn ca ng dng.
Trong c t phi nu c y cc user requirement, s dng mu
(template) ca cc trng hp s dng ca tng yu cu.
Tha mn cc tiu thc nh gi mt c t: tnh nht qun, tnh thn thin,
tnh d s dng.

1.25

Khi nim:
L hi u bi t h thng ca khch hng vo th
m thi t k v pht tri n ph n
m
m bo v c khch hng v s hi u bi t h thng,cc nhu
c
c khi
nh th
m.

- Khng ph thu c cc yu c u ph n m
,
c xy dng
no? Cui cng bao gi ch

c t cc yu c u
ny.
1 c t: tnh nht qun, tnh thn thin v tnh
d s dng.
c t yu c u ph n m m ph
c c yu c
i,
ph m vi ng dng, gii h n ca ng dng.
c t ph

c cc yu c
i s dng, s dng
cc mu(template) c
ng h p s dng ca tng yu c u
Thnh phn :
Ghi l i cc nguyn tc cng vic.
K
i s dng miu t cho chng ta m t ho
y ch
c thc hin trong nh
u kin nh nh, do nh ng tc nhn
nh nh..t
1
c cng vic.

c t cc yu c u ph n m m theo mu.
c t ch
thng, s tha thu n v ch
, c t h
thng.(SRS)
Gn nhn cc yu c u ph n m m.

u nh

c t.
Mi lin quan gi
c t vo giao di
i s dng.

1.26

G
-
-
-H

IEEE:
Gii thiu
M

C U)

CMU:

b
c.

ng d ki n v gp .
Ph m vi sn ph m.
Ti liu tham kho.
M t chung

m sn ph m
Ch
n ph m

m user

ng v n hnh
Thi t k v rng bu c
Gi nh v ph thu c
Yu c u v giao din ngoi
Giao di
i dng
Giao din ph n c ng
Giao din ph n m m
Giao di
T

thng
H th
M t
Kch c u/ th t
ng.
Yu c u ch
Yu c u phi ch .
Yu c u trnh din
Yu c u an ton
Yu c u bo m t
Yu c u ch
ng cc thnh ph n ph n m m
Nguyn tc cng vic
Ti li
i s dng
Cc yu c u khc
Thu t ng
M hnh phn tch
D
nh d ng

1.27 T
Software R

( R )

R .

.T

- Software Requirement

,
b
b. Trong t
R
R
Requirement:
R

- fw
R

1.28

,
x

( R ):
):

R ,b
,

1. Gi ngn ng
,

Tr li:

fw

2. My tr ng thi h u h n

(F

nh

nhau.

3. Cy quy

th

4. Bi

ho

ng

5. M hnh thc th lin k t

RD

6.

1.29
:

ng

: 11
Introduction (Gii thiu)
Glossary (t n thu t ng )
U
(
ng h p s dng)
Design Overview (thi t k t ng quan)
Obj
(

ng h thng)
Object Descriptions (m t
ng)
Obj
b
(
ng h p tc)
Data Design (thi t k d liu)
D
(
ng)
Non-functional Requirements (yu c u phi ch
)
Supplementary Documentation (ti liu b sung)
1. Introduction: cho ta bi t
M
:
Cung cp m t m t v cc thi t k ca m t h th

cho
php pht trin phn mm.
Cung cp thng tin cn thit
cung cp m t chi ti t cho cc ph n
m m v h th
c xy dng
Ph m vi: cho bi t ph m vi ca h thng
Cc t vi t t ,
:
u tr nn ngn g
,
c
d c, d hi
S tham kho
T
:
c c ci nhn t ng quan v h thng c n xy dng
2. Glossary:cung cp cc thu t ng
s dng n i b ca ti
liu
3. Use Cases: x
c nh ng ai s s dng h thng, tc nhn kch
ho , i din v qun tr h thng
4. Design Overview:
t t ng quan v thi t k , cho n vo m t ng
cnh vi cc h th b

i s dng
ti li
ng cho b
thi t k v nhn thy m t bn tm tt
c khi ti p tc thi t k cc chi ti t.
5. System Object Model : cho php m t cc h thng m t cch t ng th ,
cho thy cc nhm khc nhau ca cc ph n vo cc h th
ng
6. Object Descriptions: m t

ng trong ti liu
7. Object Collaborations: m t mi quan h

ng
8. Data Design:
thc th lin k t: cho bi t cc lin k t gi a cc i
ng (1-1, 1-nhi u, nhi u-nhi u)

9. Dynamic Model:
trnh t: cho thy m
t ng quan v hnh th c trnh t di chuy n t
d liu v m
c m t ti liu
chnh s a ti liu: cho thy m
t ng quan v trn t di chuy n t
m t ti liu ba
i cho m t ti liu s
i
10.Non-functional Requirements: cung cp cc yu c u thc hin (cc yu
c u phi ch
)
11.Supplementary Documentation: c th l ti liu tham khm, c th l
cng c
c s d
t o bi

1.30

1.31
P

:
x

,cy
,

1.

3.C

2.

b
,

.B

5.

.P

7.P

1.

(B

b b

40-50,

Hnh 28-1

F-ELSE-ENDIF
DO- H

2.

FOR-NEXT

1 m

b b

nin.
Hnh 28-2

3. C

Hnh 28-3
HOLIS.

(F

.
x

.B

5.

( RD) H

28-5

RD

RD

cho

RD

b
,

Trong hnh 28-6

OO

.
U

7.B

V d

28-7.

(DFD)
RD

1.32

C
.P

RD

Rng bu c v hi
:
n 9 gi ti.", "m

:
ng h n "h thng c n phc v lin tc t 5 gi
t hng c
trong ti thi u 7

Rng bu c v qu trnh pht tri n h thng: th i gian, ti nguyn, cht

ng. V d: khi no h thng c n hon thnh (th i gian); t ng chi ph cho
pht tri n h thng (ti nguyn); c n p dng cc tiu chu n no cho qu
trnh pht tri n h th ,
n l d n v
pht tri n h thng (ch
ng).
:

(Eliciting requirements):

x

x
(Analyzing requirements): x
x

,
,

(Recording requirements):
,

(use case),

(user story),

Ti

(prototyping)

tm (focus group)
(requirements workshops)

1.33

Ch m t v ch
,
b c
Khng m t v
t
Phi d
i (c cu trc)
K x
chnh xc ngay
Phi qua nhi b c xt duyt l i

:
,

(1)

(2)

,
(3)
,
(4)

,

,

(5)

Tnh r rng, chnh xc

Tnh ph h p

hon thin

1.34

:
Cc tc nhn tham gia vo qu trnh xem xt v thng qua (
:
-

i din c
i s dng (Product Champions): Thc hin qu trnh xc nh n cc
yu c (R
)
vo ti li
c t v cc yu c u thc t ca
h thng, h s phi tr l i cu h
m t
nm m
? Cc
xc nh n g m c:
o Tnh chnh xc (Correct)
o Tnh kh thi (feasible)
o Tnh c n thi t (necessary)
o
(
z ) a cc yu c u.

1.35
d

Cc phn tch vin (Requirements Analysts): Thc hin qu trnh xc minh cc yu c u

(Requirements Verif
)
vo ti li
c t v cc yu c
i dng, h s
phi tr l i cho cu h
xy dng ph n m
?
x
minh g m:
o Tnh ngn gn, sc tch (concise)
o Kh
t (traceable)
o K
a (non-redundant)
o T ch c tt (organized)
o
n (conformant to standards)
o Kh
m ch ng (verifiable)
Ngoi ra cn c cc thnh vin ca cng ty ph n m m tham gia vo qua trnh thc hin
pht tri n ph n m m: L p trnh vin, cc nh ki m th

A
BTL

:
M hnh ha use case

Requirements Modeling
b
,

R
b

b
(

b
b

b x

EA trong Toolbox)

b
(H

b
1)

(H

2)

Hnh 1

Hnh 2

x
Chu

b x

m bng custom

R
b
EA cho php b x
nh vi thu c tnh ca yu c u
o M

D
hi n th
o
x
R
b
b

O
k t thc
Nh ng thu c tnh ny c th s ch a l i sau ny bng cch double-click vo requirement
M t requirement m
c hi n th
j
w

(x

C
x
R
DoubleR
R
, ff
,
,
: x
2b

OK
y.
N

x
R
K

x
,

:
T o nh ng thu c tnh user-definable s dng tagged values
Viewing Requirement s dng Elements list view ho c diagram view
Thi t l p nh ng mi quan h gi a cc yu c ,
vi cc thnh ph n UML khc
,
,
Nh ng quan h d v t gi a nh ng yu c u v nh ng thnh ph n khc.
T o m t cy yu c u k tha s dng thnh ph n child ho c packages.
T

Add

R
x

- ff

b,

f +6(

w|

x
3

Hnh 3
Predefining Tagged Values Types for Requirements
,b

U
f

Hnh 4

,
x
n.


x
x

|[ ]

Hnh 5
Element Numbering

111

Hnh 6

b
f

Select m t package trong Project Browser

Right-click v t menu context select: Show Level Numbering

Hnh 7
T Project View, cc thnh ph
c th
c sp x p l
ko m t child element vo m t element khc. Nh ng elements con s
ph h p vi elements cha.

n bng cch
l

Hnh 8
Different Views of Requirements Using the Element List View
b
i dng khng ging v
U
EA h tr m t text-based view ca nh ng yu c u, trong khi vn duy tr cu trc phn cp
trong Project View.

The Project View. Ci ny c th gn

hi n th cy phn
cp.
w
ny c th thi t l p v ch
text view
o
i ch
diagram view v Elements List View t main menu,
sleect View| Element List.
The Notes and Tagged Value windows c th thi t l p l default view
o
xem the notes window select View| Notes
o
xem the tagged values window select View| Tagged Values.

x -b

x -based mode

Hnh 9
w

Hnh 10

1.36
d

A
BTL

:
T o ra cc yu c u ph n m m bn ngoi (External Requirements)
+ T o trong bi
( Diagram )
M Custom pages trong Enterprise Architect UML Toolbox. Chn
Requirements
C

ng Requirement, th vo trong bi
Nh p tn v cc thng tin khc cho Requirement. Save l i
+ T o trong gi ( Package)
Nhy phi vo gi, chn Insert | New Element ( ho c Ctrl + M )
Trong h p tho i New Element, chn Requirement
Nh p tn v cc thng tin khc cho Requirement. Save l i.
T o ra cc yu c u ph n m m bn trong m t Element khc (Internal
Requirements)

Ta c th t o ra cc yu c u ph n m
,

m v

ch ra r

thc hin vic ny, ta thc hi

t cc yu c

M h p tho i Properties ca Element.

Chn Tab Require
Nh p tn Requirement v cc thu c tnh ca n.
B
R
i
N u mun, b
w t o ti p Internal Requirement khc cho Element,

c thc hin cc thao tc qun l khc ( sp x p, s a, xa )

B OK
p tho i
Chuy n yu c u bn trong ra ngoi
M h p tho i Properties ca Element. Chn Tab Require
Chn Requirement c n chuy n. Bm Move External
Trong h p tho i m ra, chn package
x
R
Qun l cc thu

bn ca yu c u:
Cc thu
bn ca yu c
c qun l trong EA:
Tn
Tr ng thi thc hi ( xu ,
,
t, bt bu ,
m
tra)

kh

Lo i yu c u ( Ch
g, hi n th , bo co, ki m th , )
Ghi ch
Cc thng tin khc
Ghi ch cc thng tin b sung
S dng thu c tnh Note
S d

ng ch thch Note
S dng Tagged Values (la chn, m c a s Tagged Values, t o ra cc c p
Key
cc thng tin b sung cho yu c u )
Xa, sp xp cc yu c u
Thc hin trong c a s Project Browser, thng qua cc button trn toolbox ho c menu
ng cnh.
T o cu trc phn cp cho yu c u

Khi mun chuy n 1 Requirement thnh con ca 1 Requirement khc, trong c a s

Project Browser, ta r r i th Requirement-con vo Requirement-cha.

Vi ch

xy d

c cu trc phn cp cho Requirement: 1

requirement ln c th bao g m nhi u Reqiurement nh

cho cc Requirement:
Nhy phi vo package, chn Show Level Numbering

bn
La chn Requirement c n k t xut
Vo menu, chn Project | Documentation
La chn lo i bo co ph h ( R
x F
,H
,)
Trong h p tho i m ra, nh p cc thng s c n thi t. Ch chn Use
template l requirement template

Kt xu

CHNG IV. DUYT V KI

P

1.37

T CC YU CU PHN

*K
x

):

U
F
D

R
ional Requirement

a.

(R

.N

a.
(
)
b. Chnh xc (Correct)
c. K thi ( feasible)
d.
(
))
e. X

and stability)
f. R rng.
g.
(
f b )

a.

b.
(
f b )
c.

(
b )
d.

(
)

1.38

,
:

b.

x x

b.

b
,

- K
- K

1.39

x
x

.N

Quy trnh xem xt:

o
b

o
b

o
o K

o
o Requirement Inspection Checklist

o Cc PTV

1.40

D(

ng bn ngoi

i chng ta phi gii quy t bi ton mi

i ki n ca h

w):

m t h thng mi t n t
ng bn trong
Tht b i trong vic ly yu c u t
i dng (

yu c u t
nhi
i dng)
Tht b i trong vic t o m t quy trnh thc hnh gip qun l s
i yu
c u ph n m m
1.41

:
Vai tr:

:
delete hay khng?

d
d

1.42
d

b b

b
b

.C

gii thch m i m hnh l ph h p

N u c m t vi m hnh ca h th
gii thch nh ng s ph h p bn
trong v bn ngoi.

gii thch rng cc m hnh c tnh chnh xc vi cc yu c u thc ca

nh
b
n h th
t vic r
.

1.43

1.44

Cc k thu t ki m th chp nh n:
- Pht hin l :
c thc hin v k t qu l th c n ki m tra. N u
k t qu
, p tc thc hi b
ng. M t ki m tra tht b i l triu ch ng
ca m t l i. Ki m th chp nh n hiu qu nht n
c da trn cc tiu ch
c l p vi ch
c th nghim v c th tnh ton m
n
bi
c k t qu.
- Ch
i: Ki m th chp nh
x
c
th ni r
n l i: Ki m th chp nh n t o ra ro cn khng cho l i lan r ng.
- Che giu l i: Ki m th chp nh n che giu m t gi tr xu n u k t qu th l i ho c
thay th chnh xc trong th
c khi tuyn b tht b i
- B
ng l i: N u m
t b i trong ki m th chp nh n c th
thay th bng m
ng h p d phng. N
ng h p d phng thnh cng, c
th s d
b
ng h b
u
- S a l i:
- ------------------------------------------Ngu n-----------------------------------------------------

- 4.3 Acceptance Test Techniques

-

The fault detection mechanism used influences the remainder of the fault tolerance
activities (diagnosis, containment, masking, compensation, and recovery). The two
common mechanisms for fault detection are acceptance tests and comparison.

- 4.3.1 Fault Detection

Acceptance tests are the more general fault detection mechanism in that they can be used
even if the system is composed of a single (non-redundant) processor. The program or
sub-program is executed and the result is subjected to a test. If the result passes the test,
execution continues normally. A failed acceptance test is a symptom of a fault. An
acceptance test is most effective if it is based on criteria that can be derived independently
of the function being tested and can be calculated more simply that the function being
tested (e.g., multiplication of a result by itself to verify the result of a square root
function).

- 4.3.2 Fault Diagnosis

-

An acceptance test cannot generally be used to determine what has gone wrong. It can
only tell that something has gone wrong.

- 4.3.3 Fault Containment

-

An acceptance test provides a barrier to the continued propagation of a fault. Further

execution of the program being tested is not allowed until some form of retry successfully
passes the acceptance test. If no alternatives pass the acceptance test, the subsystem fails,
preferably silently. The silent failure of faulty components allows the rest of the system to
continue in operation (where possible) without having to worry about erroneous output
from the faulty component [Schlichting 83].

- 4.3.4 Fault Masking

-

An acceptance test successfully masks a bad value if a retry or alternate results in a new,
correct result within the time limit set for declaring failure.

- 4.3.5 Fault Compensation

-

A program that fails an acceptance test can be replaced by an alternate, as described in the
next section. If the alternate passes the acceptance test, its result may be used to
compensate for the original result. Notice that the alternate program run during a retry
may be a very simple one that just outputs a "safe" value to compensate for the faulty
subsystem. A common approach in control systems is to "coast" the result by providing
the value calculated from the last known good cycle.

- 4.3.6 Fault Repair

-

Acceptance tests are usually used in a construct known as a recovery block. A recovery
block provides backward fault recovery by rolling program execution back to the state
before the faulty function was executed. This repairs the faulty state and the result. When
a result fails an acceptance test, the program can be executed again before leaving the
recovery block. If the new result passes the acceptance test, it can be assumed that the
fault originally detected was transient. If the software is suspect, an alternative can be
executed in place of the original program fragment. If a single processor is used, the state
of the processor must be reset to the beginning of the function in question. A mechanism
called the recovery cache has been proposed to accomplish this [Anderson 76]. A

recovery cache records the state of the processor at the entrance to each recovery block.
Although a recovery cache is best implemented in hardware, implementations to date have
been limited to experimental software. Where multiple processors are available, the retry
may take the form of starting the program on a backup processor and shutting down the
failed processor. Recovery blocks can be cascaded so that multiple alternatives can be
tried when an alternate result also fails the acceptance test.
---------------------------------------------------------------------------------------------------------------

1.45

b
d

d
BTL

ton,

Kim ton:
b

EA. N
,

kch ho
:
1. T menu chnh b n chn: View | Other Project Tools | Audit View,s m ra:

2. B n chn Audit Settings

3. N s m ra c a s Audit Settings :

4. Trong c a s Audit Settings b n thi t l p kch ho

hnh v trn.

History

y c Element List xem cc ty chn thi t l p.c a s Output | Audit

Audit View:

x
Projects and
Teams | Change Management | Tracking Changes | Auditing
S dng ng c s:

Baseline Management

,
b ,

b
gip:

b x

Projects and Teams | Change Management | Tracking Changes | Package Baselines

Thay i yu cu v cc vn v yu cu ngoi
b

:
,

-Dng Maintenance View

ci

Issue " v "

a.S dng cc Xem Bo tr:

danh sch cho:

gi.

b w
,

Maintenance View

b
View | Other Element Tools | Maintenance or (Alt+4) . Hnh

-Y

b)S dng cc yu t bo tr cho Thay i v cc vn

b

Issue v Change.
nh ng truy c p t Toolbox | Maintenance ho c Toolbox | Custom

b
(

b
-C

b
b

Element List x

Relationship
:

1.46

:
K

D,

Ti sao phi kim th yu cu phn mm:
- D
2

D
trnh vin

Tiu ch kim th yu cu phn mm

- H

- Chnh xc
- K
- R rng
- K
,x
Quy trnh kim th yu cu phn mm:
Bussiness Requirement
Use Case
Functional Requirement
Cc cng c s dng:
Dialog Map
Test Case
Ma

CHNG V. CC K THUT N NG CA

1.47

:
2
o

:(
x

b
x

:
:

:
o K

CHT LNG YU CU PHN

Pressman p289)
,
b

o Features traceability table:

b

o Source traceability table: X

o Dependency traceability table:
b
o Subsystem traceability table:

o Interface traceability table:

(

1.48

).

.V

Ma trn vt (theo di) yu cu phn mm (Requirements Traceability Matrix - RTM)

Vai tr :

R
sot quy trnh v qu

x
Thnh ph :

(
c phn chia:

Cc d ng bi u din ma tr n:
p bng lin k t
p ma tr n lin k t

1.49

(
(f
(
)

Cc mi lin k t c th
t-M t
t-Nhi u

u-Nhi u

)
)
)
)

?
- Nhn t ngoi: V
,
- Nhn t
:

i,

ng thay

t b i trong vi

i
m trong sut qu trnh thu th p yu c b
u. Chng ta
tht b i trong vic t o ra m t qu trnh thch h
tr gip cho vic qun l
i tron yu c u ph n m m

1. Nh n th
c rng, s
i trong yu c u ph n m m l khng
th trnh khi v phi ln k hoach cho n
2. V ch ra cc yu c
.
3. Thi t l p m t knh duy nh
ki
i.
4. S dng m t h thng ki
nm bt nh
i
5. Qu
i th b c.
Qun l cu hnh yu c u:
n cc s
i tri php v c kh
y ho
i ti
yu c u
cc phin bn ti liu ca yu c u.
- T
u kin cho vic thu h i v/(ho c) xy dng l i cc phin bn ti liu
c.
- H tr qun l, t ch c cc chi
b
ci ti n c p nh t h thng.
n vic c p nh
ng th i cc ti liu ho c cc thng tin mu thun
nhau.

1.50

D:

:
1. Kh
bo tr: c kh
ca khch hng.

b ,

b
,

c hin nh ng ti n tri

tha mn yu c u

2. Kh
y: bao g m hng lo
tin c ,
an ton,
bo m
n m m tin c y khng th t o ra cc thit h i v t cht hay kinh
t
ng h
ng.
3.
h u hiu: ph n m m khng th ph ph m cc ngu
b
nh v cc chu k x l.
4. Kh
dng: ph n m m nn c m t giao di
i d
i
s d
cc h
ph n m m.

Tnh chnh xc ca yu c u?
Yu c u c b l p l i hay khng?
Tnh h p l ca yu c u?

1.51

Tr li:

1.52

*
K

c.
h.
i.
j.
k.
l.
m.
n.
d.
e.
f.

x x

(
)
Chnh xc (Correct)
K
(f
b )
(
))
X

stability)
R rng.
C t
(
f b )

(
f b )

(R

g.
h.
(

b )

)
)

Pseudocode (Gi ngn ng)

Finite state machines (my trng thi hu hn)
Decision trees (Cy quyt nh)
Activity diagrams (flowcharts) (Biu hot ng)
Entity relationship models (M hnh thc th quan h)
Object-oriented analysis (Phn tch hng i tng)
Structured analysis (Phn tch hng cu trc)

1.53

ng cho m hnh Use Case

ng cho gi SRS
ng d

c tnh ch

ng yu c u ph n m m

(f

(design element)

)
(

)
:

Qu trnh lp ma trn:
- X

- X
- X

- K

(R
b

x):

R
2

1.54

a.

Auditing
b
,

:
1. T menu chnh chn: View | Audit View,

,
b

2. Chn nt Audit Settings

3.
c c a s Audit Settings:

4. Trong c a s Audit Settings check vo enable Auditing

Ouput | Audit History

Help | Help Contents | Model Management | Auditing

b.
Using Baselines
,

w
:

.
b
b
x

b,x
Help | Help Contents | Model Management | Baselines, Diffirencing and Merges
c.
Change Requests and Issues on External Requirements

- S d
w
lit k nh
v nhim v da theo m i nhn t.
- S dng nh ng nhn t t chn ca ki
yu c
i

Using the Maintenance View

i, khi m khuy t, v

t vi cc

Y
Y
Y
Y

u t khi m khuy t
u t
i
u t v
u t nhim v

w
Maintenance or (Alt+4)

b
,

: View |

Using Maintenance Elements for Changes and Issues

b

b x|
b
b

- Nh ng nhn t
trong gi ch a cc yu c u lin quan ho c
trong m t gi ring bit ch a m t t p nh ng s
i.

- Chng c th
c lin k t ti nh ng nhn t yu c u trong bi
ng ho c s dng ma tr n quan h.
- Nh ng nhn t c th
c ty ch
t ph n ca m t h
g
c tnh m r ng.

bao

thng

N
1
2
3 X
4
5