Professional Documents
Culture Documents
IT4460 Cauhoi
IT4460 Cauhoi
1.3
1.4 1.5
Hy nu cc thi quen tt v thi quen khng tt trong cng ngh hc yu cu phn m m ......... 6 N N y y P Q 6 ....... 7
1.6
1.7 1.8
M t Quy trnh cng ngh hc yu cu phn m m (Requirement Engineering Process) ............ 8 N y y ............................................................................................10
N S Trnh by cc yu c x
..........11
1.10
1.11
......................................................12
1.12 Trnh by quy trnh thc hi ( b ), m v nh ng k thu x nh yu cu phn m m Phng vn (interview) ..................................................................................................14
N N V ) T
y M ...................................................................................................................................20 y T TL (V W b ...............................................................................20
b y
1.22 T b y tiu ch
..........................................................23
Nu cc yu cu c
1.27 R
1.28 1.29 1.30 1.31
c t yu cu phn m m (SRS) System Requirement v Software c t v tr no trong ti liu SRS. ..............28 c t yu cu phn m m ........................................................................28 y y y y y y y y y ........................31
1.32
1.33 1.34
N P
x x ( y ) y ............................................................................................................................................42
u phn m m .....................................52
1.38 T i sao cn ki m th y u phn m m. Nu tn m t s m th yu cu phn m m thng dng m em bi t. ..........................................................................................53 1.39 y 1.40 1.41 1.42
N P N N V
y y y .................................................................................................................................55 y y ......................56
1.43
1.44
...................56
1.45
y y TL.................................................................................................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 cu phn m m ......................................................................................63
N P y y y N N y K thu t qu
t ca yu cu phn m m. .......................................................64
1.48
1.49 1.50 1.51 1.52
m bo cc yu cu phn m m .............68
1.53
1.54
C UH I
CHNG I. TNG QUAN V YU CU PHN MM V QUY TRNH 1.1 C T : y (1993) : ( , ) b J (1994) : y b S S wy (1997): Y y I (1) y y y (2) y y , , b b b (3) V b (1) (2) D y y , y y x , x . IEEE. y .
1.2 Hy T S b
: y N
1.3 N T : I
y y
y y
y (1)
1.4 Hy T T : : L K
y y
y , y
T N
1.5 N T :
.Q
H M K T y K D
chnh xc
H M y y y
1.6 N
K b
.P
y (note) :
a)
b)
c)
d)
y : Phn lo i theo yu cu ch . - Cc yu cu ch nh ng ch n m m s thc hin. V d bn hay thu tn hiu. - Cc yu cu phi ch y rng bu c ca gii php thc hin. C th gi yu cu phi ch y u v tnh rng bu c v v ch ng phn m m. Phn lo i cc yu cu phn mm theo ngun gc t m t hay nhiu yu cu c c cc thu c tnh ni bt (emergent property), ho ch u ng ca phn mm b i din s dng (stake holder) ho c m t s ngun khc: emergent property: C m t s yu cu phn m m s c y y u khng th x nh cho m t thnh ph , m cn ty thu p cc thnh phn trong h thng. V d y 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 y c bit ph thu c vo ki n trc h thng. Phn lo i theo cc yu c t ra cho sn ph m ho c l trn tng tin trnh. Cc yu cu 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), hoc l nh ng chu t ra. Phn lo n mm: T ng, cc yu c n l nh ng yu cu quan tr c xy dng da trn m t s y u t y nhi , mong mun, hoc tnh c hay khng bt bu c.
e) Phn theo ph m vi yu cu phn mm: Ph m vi yu cu phn m m ng ca yu cu ln phn m m v cc thnh phn ca phn m m. f) Phn lo d bi ng/ tnh nh (volatility/ stability): M t s yu cu phn m m s y i ca phn m m, v th m ch ngay c trong qu trnh pht tri n ca yu cu phn m m. Chng ta c th phn lo i cc yu cu bng cch thng k nh y i m yu cu c th pht sinh. N b T , , : Guide to the Software Engineering Body of Knowledges 2004 39 202 y , b b x
1.7 M Q y Process) T : Q y Q y P y
(R
T ,P
P y
2 y , y
:P y
HNH 1-2 P -T P P y
P y
K y -Q y : y y ( MU S I 1995) Q y sau. X y (R b ) D y Q y y
Q y
HNH 1-3. Bin phn chia gia pht trin yu cu v qun l yu cu.
M M
y M y ,
: y y , ) K , y , ( y y b
Requrireme ( P b
T b 10
y 1 0) b
y ,b y y M M y
y ,x , y
y, :
R V y By 1.8 N T : V T
-
, y Q y
, T
b 1 1 b 1 1
y y
y N
y i s dng:
Cung cp yu cu cng vic(Business Requirement): th hin cc mc tiu yu cu m c cao ca t ch c hay khch hng v kh , m vi ng dng v gii h n ca phn m m; cung cp cc thng tin v tng nhim v c th m h s lm vic vi phn m m Yu cu ngi s dng (user requirement): th hin cc nhim v c th m NSD cn ph , c vi phn m m. T ng,tha th n v i pht tri n cc yu cu phn m m. - N i pht trin: Pht hin cc yu cu Phn tch cc yu cu c t cc yu cu Ki m th cc yu cu y : - N i s dng: c ng ti y : phn m i qu cao hoc ch t cod n qu trnh pht tri n
ng yu c ngh rt kh chp nh y PTV Cc yu cu phn m nh p nhng T a cc nh phn tch: lm l i yu cu phn 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 NSD ng yu cu qu ngn gn m khng miu t k chng l g N i pht trin:c ng ti y : Phn tch c cc v Hi u bi t v nhu cu s dng Hi c h thng Hi u ph m vi qun tr Tinh chnh cc tnh h thng
T 1.
: x nh yu cu phn 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 cu phn m m y N y y , y x , x
2. Ngu S
b I V :
1997 , y (2) 2b 1 y y
y y y 1 1 b
1.10 T
S :
6 Phng vn
y T ch c h i tho
T ,
chnh xc
1.11 T
T :
by
Trong pht T T
: y
P T w N
y , , b b y H y , y y , ( , y , , ,
, b T b N T , y
u l d
( w)
t ph m vi.
b :
y,
- N - T N -
y?
- T
(K b
1.13
T
by x
( b ), H o
1. Quy trnh thc hin b H o Q b o b b o b o K (w ): b 2 w -up materials: T T b b y , , b ,b x , ,b , , b y b f ( y ): o b , x y o L o Ch c k x y ng s ng lng hay xy dng nhm v ng chc. L c c cc thnh vin trong nhm v ngoi nhm tn trng. v i mt vi nh ng thch th c trong h i tho. - L H y o o Brainstorming o S b y cc y 2. m
S ,f
,f
- H i tho yu cu c l l k thu t m nh m nh g i ra cc yu cu - 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 cu c th m bo s thnh cng ca h i tho. - Brainstorming l phn quan trng nht ca m t h i tho. 3. K thu t - P y b b N b y K
1.14
T -N , -T
by x
( b ), B
2 : : M :P ,
, ,
Khuy c mi thnh vin tham gia. Cho php cc thnh vin tranh lu n vi nhau v cc ki N u phi ho y c h i tho khng b Din ra nhanh chng. i php kh thi cho v . Khuy , y , nh:
xut. n.
Q y
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.
1.15
T 3 :
by x
( b ), S yb
yb :G :L T :T
: b y , , yb N
: K S yb K yb u ny. , y S yb
1.16
T :
by x
( b ), d
U b U U -case.
UML U
1.17
T N b :
by x
y
( b ), P y
y S , b
b 1 y b
, V
y (M V )
, ,
y , y V y z , f (N R S fw 13 x y y , y T
) , ,
y ,
: M
x y y D y
w w y,
L b y b y , b
1.18 N .
T : ??????
. M
1.19 N W b
T :
V )
y d
.T .
BTL (V
N 1.20
T :
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) T 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 d M hnh ha use case M hnh ha nghip v M hnh ha d liu T by b ( y :
)P
Phn lo i cc yu cu phn m m:
C N C C
y y y
: :
, , , y, ,
, ,
, ,
: y : , y
, b
M b
T Y K
b y
hng
-T , x I y y x 2000 y : u b T y -T
y y
- Ph b
, y
, y y
b , y
1.21
T :
1.22
T :
by
. .
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.
P thm
1.23 C d
EA BTL
.E
1. Xem xt c t ca yu cu phn mm 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 cu 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 y 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
c hin.
L R
ng : thng tin v Requirement v cc ng. C nhi nh d bn khc nhau :R T x F , HTML, Bo co quan h t Bo co quan h ph thu c
c t
HNG III
YU U PHN MM
1.24
T G M y
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
T :
Khi nim: L hi u bi t h thng ca khch hng vo th m thi t k v pht tri n phn 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 cu phn m , c xy dng no? Cui cng bao gi ch c t cc yu cu ny. 1 c t: tnh nht qun, tnh thn thin v tnh d s dng. - T c t yu cu phn m m ph c c yu c i, ph m vi ng dng, gii h n ca ng dng. - T c t ph y c cc yu c i s dng, s dng cc mu(template) c ng h p s dng ca tng yu cu 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 y c cng vic. c t cc yu cu phn mm theo mu. L c t ch thng, s tha thu n v ch , c t h thng.(SRS) Gn nhn cc yu cu phn m m. u nh c t. Mi lin quan gi c t vo giao di i s dng.
Comment [n1]: Cc yu cu i vi bn c t
1.26
T
G - - -H
N
:
IEEE CMU)
V b y 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 M ng v n hnh Thi t k v rng bu c Gi nh v ph thu c Yu cu v giao din ngoi Giao di i dng Giao din phn c ng Giao din phn m m Giao di T thng H th M t Kch cu/ th t ng. Yu cu ch Yu cu phi ch . Yu cu trnh din Yu cu an ton Yu cu bo m t Yu cu ch ng cc thnh phn phn m m Nguyn tc cng vic Ti li i s dng Cc yu cu khc Thu t ng M hnh phn tch D nh d ng
CMU:
(SRS) Sy
.T - Sy
y (y y , x y N
1.28
Tr li:
1. Gi ngn ng G , y
2. My tr ng thi h u h n
M y , FSMS T th nhau. y y , nh , y
(FSMS)
3. Cy quy
V x y
4. Bi V
ho
ng UML, b
SRS
RD 6. P
ng
1.29
T :
y : 11 Introduction (Gii thiu) Glossary (t n thu t ng ) U ( ng h p s dng) Design Overview (thi t k t ng quan) Sy Obj M ( ng h thng) Object Descriptions (m t ng) Obj b ( ng h p tc) Data Design (thi t k d liu) Dy M ( ng) Non-functional Requirements (yu cu 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 y cho php pht trin phn mm. Cung cp thng tin cn thit cung cp m t chi ti t cho cc phn 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 cn 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 phn 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: S 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: - S 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 - S 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 cu thc hin (cc yu cu 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
T
y : x y
1.31 P
T
x b , : , , : y ,cy , y y
(B d )
1.M M b b b T Q y L
FOR-NEXT
Hnh 28-1
2.M y T T
. , , 1 m
b b
(FSMS)
y . x y
y y y
4.B
UML, y
: N y
RD x
x ? T :
cho
M 6.M V b ,
RD OO . UML,
7.B
V d
28-7.
(DFD) RD
RD
1.32 y
T
C .P
:
y y
b , ,
y y
, , b , y : Rng bu c v hi : ng h n "h thng cn phc v lin tc t 5 gi n 9 gi ti.", "m 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 cn hon thnh (th i gian); t ng chi ph cho pht tri n h thng (ti nguyn); cn 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). : L (Eliciting requirements): x y X x y (Analyzing requirements): x x y , , , y , y L y (Recording requirements): y , , (use case), y (user story), L y : b y y
1.33
T :
Ti y
y : (1) , (2) S , y (3) V , (4) T : , , , (5) T : Tnh r rng, chnh xc Tnh ph h p T y hon thin
1.34
P y
d y )
y )
i din c i s dng (Product Champions): Thc hin qu trnh xc nh n cc yu c (R V ) vo ti li c t v cc yu cu thc t ca h thng, h s phi tr l i cu h T m t n m m y ? Cc xc nh n g m c: o Tnh chnh xc (Correct) o Tnh kh thi (feasible) o Tnh cn thi t (necessary) o ( z ) a cc yu cu.
Cc phn tch vin (Requirements Analysts): Thc hin qu trnh xc minh cc yu cu (Requirements Verif ) vo ti li c t v cc yu c i dng, h s phi tr l i cho cu h T xy dng phn m ? x minh g m: o Tnh ngn gn, sc tch (concise) o Kh y t (traceable) o K a (non-redundant) o T ch c tt (organized) o y n (conformant to standards) o Kh m ch ng (verifiable) Ngoi ra cn c cc thnh vin ca cng ty phn m m tham gia vo qua trnh thc hin pht tri n phn m m: L p trnh vin, cc nh ki m th
1.35 d
EA BTL
.E
Hnh 1
Hnh 2
x Chu
R b EA cho php b x nh vi thu c tnh ca yu cu o M S D hi n th o N 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 P j V w (x x b
) C Ex R DoubleR R , ff y, y, y V : x 2b T y OK y. N Ex R K x , y V : T o nh ng thu c tnh user-definable s dng tagged values Viewing Requirement s dng Elements list view hoc diagram view Thi t l p nh ng mi quan h gi a cc yu c , vi cc thnh phn UML khc , , Nh ng quan h d v t gi a nh ng yu cu v nh ng thnh phn khc. T o m t cy yu cu k tha s dng thnh phn child hoc packages. T T Add A b R y T T +S f +6( M V w| T V ) V x b - ff b b, 3 yx x y y, ,
Hnh 4
N T V x 5
y x
y | |S w
|[ ]
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 T y b i dng khng ging v UML EA h tr m t text-based view ca nh ng yu cu, 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. T L V w S ny c th thi t l p v ch text view o y 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. y x -based mode
x -b
Hnh 9 V w
Hnh 10 V y b T b y
1.36 d T
C :
EA BTL
x y d
.E
+ 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 ( hoc 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 cu phn mm bn trong m t Element khc (Internal Requirements)
b m v
1 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 S R i N u mun, b N 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 Chuyn yu cu bn trong ra ngoi M h p tho i Properties ca Element. Chn Tab Require Chn Requirement cn chuy n. Bm Move External Trong h p tho i m ra, chn package x R Qun l cc thu bn ca yu cu: 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 cu ( 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 cp Key V cc thng tin b sung cho yu cu ) Xa, sp xp cc yu cu Thc hin trong c a s Project Browser, thng qua cc button trn toolbox hoc menu ng cnh.
T o cu trc phn cp cho yu cu
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.
Kt xu
bn La chn Requirement cn k t xut Vo menu, chn Project | Documentation La chn lo i bo co ph h ( R T x F , HTML,) Trong h p tho i m ra, nh p cc thng s cn thi t. Ch chn Use template l requirement template
*K x V S D y Q y U F
y y
(T
): V y y
y : R y
ional Requirement : D M T M * y
y ,
, y
x , : y
x x
y y
a.
b.
(R
1.38 T
T :
y d
.N b.
V , y M - K - K y
y y y
b , y
SRS
1.39
N x x y
.N
NSD (P : LTV,
1.40
P T
y y
y m t h thng mi t n t T
ng bn trong Tht b i trong vic ly yu cu t i dng ( y y yu cu t nhi i dng) Tht b i trong vic t o m t quy trnh thc hnh gip qun l s y i yu cu phn m m y d y y
1.41
T : Vai tr:
y y , ,
y y
b b , y y b y b y b
b y
1.42 d
N d y
d y
.C
T T
: y
N T
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 cu thc ca nh b n h th y t vic r .
1.43
d y
1.44
T :
d y
Cc k thu t ki m th chp nh n: - Pht hin l : c thc hin v k t qu l th cn 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 N c th ni r - N 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 hoc thay th chnh xc trong th y 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-----------------------------------------------------
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).
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
T :
.E
b EA d
d BTL
d y
ton,
,y
y y
y y kch ho y: 1. T menu chnh b n chn: View | Other Project Tools | Audit View,s m ra:
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. V History y c Element List xem cc ty chn thi t l p.c a s Output | Audit y y :
y Audit View:
y (
. N
b gip:
, Baseline Management , b , x y ) y x
y y b x
Projects and Teams | Change Management | Tracking Changes | Package Baselines Thay i yu cu v cc vn v yu cu ngoi b x -Dng Maintenance View -S y y y y M ci gi. T y N b , by w , w y : y y y danh sch cho: y : y Issue " v " , y , ,y y y
: b
V y
-Y
y b y
y y
Element List x
Relationship :
1.46
T :
)y
K y NSD, Q , N y
y ,
y y b
NSD y P K
, y
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
: 2 :T o T : : M y o K :V P S :( x b x y
b y y
S Pressman p289) y , b y y M b :
o Features traceability table: b y o Source traceability table: X o Dependency traceability table: b o Subsystem traceability table: P o Interface traceability table: ( b
y y
).
1.48
T :
y y
.V
Ma trn vt (theo di) yu cu phn mm (Requirements Traceability Matrix - RTM) Vai tr : P y ( ) V RTM sot quy trnh v qu RTM y b x Thnh ph :
y y
N ,
y y M T ( (
(y (f ( )
) ) ) )
c phn chia:
1.49
T :
y y
y y
? i, NSD y y ,M 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 y i tron yu cu phn m m y :
1. Nh n th c rng, s y i trong yu cu phn 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 y i. 4. S dng m t h thng ki y nm bt nh y i 5. Qu y i th b c. Qun l cu hnh yu cu: - N n cc s y i tri php v c kh y ho i ti yu cu - L cc phin bn ti liu ca yu cu. - T u kin cho vic thu h i v/(hoc) 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 n vic c p nh ng th i cc ti liu hoc cc thng tin mu thun nhau.
1.50
T :
T VD:
b , y
b ,
b , , y
x ,
c hin nh ng ti n tri
tha mn yu cu
2. Kh y: bao g m hng lo tin c y, an ton, bo m P 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: phn m m khng th ph ph m cc ngu y b nh v cc chu k x l. 4. Kh dng: phn m m nn c m t giao di i d i s d y cc h phn m m. y Tnh chnh xc ca yu cu? Yu cu c b lp l i hay khng? Tnh h p l ca yu cu?
1.51
Tr li:
1.52
T
N
:
y y
* K y
(R
( T
g. h. T
( ) )
(T
b )
y y
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) t ng cho m hnh Use Case ng cho gi SRS ng d
c tnh ch
ng yu cu phn m m
1.53
T :
EA
d y
L - P
y y M T M M y . y
(y (f ) ) : y y
( ) (
(design element) ) :
M N L L
N N b b :
1.54
T :
EA
y y
a.
Auditing b y , y y y b N ,
V w :
x y :
. b b x b,x Help | Help Contents | Model Management | Baselines, Diffirencing and Merges c. Change Requests and Issues on External Requirements - S d M V w lit k nh v nhim v da theo m i nhn t. - S dng nh ng nhn t t chn ca ki I yu c y i M Using the Maintenance View y y : y : i, khi m khuy t, v y N
t vi cc
M Y Y Y Y b
, M V w Maintenance or (Alt+4)
b , y
: View |
y y y y b y Using Maintenance Elements for Changes and Issues N b :I y T b x| N b b b ( y ) y y - Nh ng nhn t trong gi ch a cc yu cu lin quan hoc trong m t gi ring bit ch a m t t p nh ng s y i.
- Chng c th c lin k t ti nh ng nhn t yu cu trong bi ng hoc s dng ma tr n quan h. - Nh ng nhn t c th c ty ch t phn ca m t h g c tnh m r ng. y y I
thng bao
L :
N 1 2 3 X y 4 5
d y
b y
y y y