You are on page 1of 22

Integrating Visual Models Into the Rational Unified Process

Authors : K. Cooper, S.P. Abraham, R.S. Unnithan, L. Chung, S. Courtney From : Journal of Visual Languages & Computing, 2006 Presented by : K.W. Lee, 14.10.2007

1

Outline
1 Introduction 2 Representing Requirements 3 Enhance Vision Document 4 Refining Functional & Non-functional Goals into Use Cases 5 Conclusions

2

1 Introduction (1/3)
 When

using the RUP, goals are captured in the Vision Document (Text based)  Once defined, goals in the Vision Document are refined & captured in additional models.

E.g. functional goals -> Use Case Diagrams non-functional goals -> Special Requirements section of the use cases

3

1 Introduction (2/3)
Problem :  RUP does not provide any guidance on how to create the traceability matrix. Solution :  Their work provides a specific approach to defining these traceability relationships.
 QARAT

is used to illustrate this approach.
4

1 Introduction (3/3)
 Quality

Assurance Review Assistant Tool (QARAT)
Supports capturing & managing the results of conducting quality assurance inspections, or reviews, of various SE artifacts. Reviewer can conduct their inspections remotely & submit their comments, defects identified.

5

2 Representing Requirements (1/2)
 RUP
 

Vision document Use case model

 AND/OR

Graph

Functional requirements

 Softgoal

Interdependency Graph
6

Non-functional requirements

2 Representing Requirements (2/2)
Vision Document in RUP

7

3 Enhanced Vision Document (1/7)
 Functional

Product Features (visual)

8

3 Enhanced Vision Document (2/7)

Functional product features (textual)

9

3 Enhanced Vision Document (3/7)

10

3 Enhanced Vision Document (4/7)
 Non-functional

product features (visual)

11

(a)QARAT system: Non-functional Product Features (top-level)

3 Enhanced Vision Document (5/7)

12

(b)QARAT system: decomposition of security feature

3 Enhanced Vision Document (6/7)

Non-functional product features (textual)

13

3 Enhanced Vision Document (7/7)

14

4 Refining Functional & Nonfunctional Goals into Use Cases (1/7)
Refining Functional Goals into Use Cases
3.

Straightforward refinement of each leaf of the goal model into one Use Case(1:1)
- Disadvantage : does not allow for defining Use Cases that merge or split various goals

4.

Flexible refinement of a goal into one Use Case
- many goals combined into one Use Case, and/or a goal split into many Use Cases(N:M)

15

4 Refining Functional & Nonfunctional Goals into Use Cases
(2/7)

16

4 Refining Functional & Nonfunctional Goals into Use Cases
(4/7)

Textual Description

17

4 Refining Functional & Nonfunctional Goals into Use Cases
(5/7)

18

4 Refining Functional & Nonfunctional Goals into Use Cases
(3/7)

Refining Non-functional Goals into Use Cases

Allows a N:M mapping For each goal in the decomposition, the analyst identifies the Use Case(s) it applies to.

19

4 Refining Functional & Nonfunctional Goals into Use Cases
(6/7)

 Refining

Non-functional Goals into Use

Cases

20

4 Refining Functional & Nonfunctional Goals into Use Cases
(7/7)

21

5 Conclusions
 Integrate

functional & non-functional visual goal models into the RUP  Intuitive visual presentations in addition to the textual representations can provide more detail requirements

22