High Level Functional Requirement-nanlix

spinabundantInternet και Εφαρμογές Web

30 Ιουλ 2012 (πριν από 4 χρόνια και 10 μήνες)

306 εμφανίσεις

1.1

High Level
Functional Requirement

The
high level
functional requirements of this project have been classified into four
categories



Data abstraction



Traceability views



Importing data



Authorization

1.

Data Abstraction

ID

Description

FR1

The system shall allow the user to define new abstract data element or create a new
data element that represents an existing data element in Jazz data repository.

FR
2

The system shall allow an abstract
data element to be associated with Jazz repository’s
楮t敲n慬aT慴愠敬e浥湴猠(攮朮⁷潲k 楴敭ⰠT敦散tⰠ整e⸩.


3

周e 獹獴敭 獨慬a 慬a潷oan ab獴牡rt T慴愠敬e浥nt to be 慳獯捩慴敤 w楴h a f楬攠牥癩vi潮o楮
the 䩡空Jr数潳ot潲礮


4

周e 獹獴敭 獨慬a 慬a潷o
s敬ect楮g c敲t慩a att物bute猠潦o䩡zz T慴a 敬敭ents t漠be 愠p慲t 潦o
慢獴牡捴 Tat愠敬e浥nt.


5

周攠 獹獴敭e sh慬氠 慬汯眠 the 獹獴敭❳e T慴愠 浯Tu汥l t漠 牥慤 Tata 楴敭e f牯洠 th攠 䩡zz
牥p潳ot潲礠捯yp潮敮t.


6

周攠獹獴e洠獨ou汤
慬汯w 愠t牡n獦o牭rti潮 f楬i敲 t漠be

慳獯捩慴eT w楴h 慮 慢獴牡捴 Tat愠
敬e浥湴m



Traceability Views

ID

Description

FR7

The system shall allow the user to create a relationship between two abstract data
elements. The relation is called as a traceability definition.

FR8

The system shall allow

the user to create a new relationship of existing two traceability
definitions

(chaining of relationships)
.

FR9

The system shall allow an authorized user to view instances of a selected traceability
definition. Instances are elements that are participati
ng in a selected traceability. Let’s
c慬氠th楳 牥獵lt楮g 癩敷 慳 t牡捥rb楬楴礠癩敷e

䙒㄰

周e 獹獴敭 獨慬a b攠ab汥 t漠牥pr敳ent co浰汥l Tat愠敬e浥nts th慴 c潮瑡in p物r楴楶i 慮T
潴he爠c潭pl數eTat愠敬e浥mt献 剥qu楲i浥湴猬mch慮来gr敱u敳e猬sm整物捳 w楬氠b攠浯T
敬eT
慳ac潭p汥砠ab獴牡rt T慴a 敬e浥nt献

䙒F
1

周攠獹獴敭e獨慬氠T楳i污礠the t牡捥rb楬楴y 癩敷 癩vu慬汹a

FR1
2

The system shall represent the bidirectional traceability between requirements and
components
,
components and work packages
,
requirements and work
packages
,
work
packages and test cases
,
requirements and related requirements
,
requirements and
design documents
,
customer requests and requirements
,
the design and
code/implementation
,
components and the responsible people who are working or had
worked on

the components.

FR
13

The system shall represent the traceability from requirements to the related discussion
or clarifications.

FR1
4

The system shall share traceability definitions among authorized users.

FR
15

The system shall allow user to copy and pa
ste the data of the traceability view in the
table.

FR1
6

The system
should allow

the user to define different sorting criteria in a traceability
view.

FR1
7

The system
should

allow the user to define his filter criteria in the traceability view.

FR
18

The system
should

allow user to export the table of the data of traceability view to CVS
file.

FR
19

The system
should

allow user to export the graphical view of traceability to image.

3.

Import Data

ID

Description

FR
20

The system shall import a fixed
format comma separated file into Jazz repository. The
mapping of fields in a CSV file to the elements in the Jazz repository is known.

4.

Authorization

ID

Description

FR
21

The system shall allow a process manager to assign roles to the defined users.

FR
22

The system shall allow authorization on the abstract data elements in the data module.

FR
23

The system shall share abstract data definitions only with authorized users

FR
2
4

The system shall allow a process manager to grant read/write privileges on
traceability
definitions to the users.

FR
2
5

The system
may allow

an authorized user to engage elements in a selected traceability
definition.




Description of
Figure 5.1.1 Allocation view of GSD System


This

allocation view shows how our product will be deployed

and
what
the

r
elationship
between
the elements

we have
and environment

they should run
.
As shown in the figure 5.1.1,
w
e will have four elements, Jazz Server Instance, GSD Server Instance, RTC Client,

and GSD
Client, within which RTC Client and GSD Client will be run
on the same PC
in Eclipse
environment while Jazz Server and GSD
S
erver
will be
deployed into
a
web/application server

separately. We plan to use
WebSphere Application Server (
WAS) for
both
Jazz and GSD server
,

and
they will communicate
with

the corresponding

application
, RTC Client
or

GSD Client,
separately through Https protocol.





Table 5.
1
.
4
# Element Catalog of

T
raceability

V
iew

P
lug
-
in


Component

Responsibility

View(s)

View is responsible for displaying screens in the GSD client.
These screens
primarily include

traceability graphics screens showing different relationship
between elements

and popup menus. These UI views communicate with
their corresponding handlers via ec
lipse runtime (menu selection bus).
These notifications are handled by the handlers.

Handler(s)

Handlers receive events generated by the UI Views. Each event will have its
own handler. Action handlers invoke methods of
Traceability View
Controller

based o
n the user actions.

Traceability
Data Broker

Traceability Data Broker communicates with GSD Data
-
plug
-
in to get the
data
required to generate the traceability view
s

the user requests.

Traceability
View
Controller

Traceability View Controller works as a

hub
,
communicating with other
components, View(s), Handler(s), Traceability Data Broker, Config Manger,
and Data Exporter, to
achieve successful representations of traceability
views to the user.


Config
Manager

Config Manager
is responsible for handling

the configuration for traceability
views according to the user’s request
, such as sorting view, filter view.

Data
Exporter

Data Exporter exports traceability view to the corresponding type of file
according to the

user’s request. The types of the exporte
d file include CSV
file or image.

Table 5.
1
.
4
#
Connector used in

“GSD
Traceability View

P
lug
-
in”

Connector

Purpose

WebServiceCallReturnConn

This connector represents a web service call made by a
caller to a callee. The information is transferred over
http(s)
connection.

FileReadWriteConnT

This connector allows a “user” role to read from or write to
a disk file.

EventConnT

This represents an event bus. Event providers put events on
the event bus which are received by the concerned event
listeners.

CallReturnConnT

Caller calls a certain method of callee
,

and callee performs
the requested
operation

and returns the result back to the
caller.