Information Technology Reference
In-Depth Information
the main ideas with an example and discusses the obtained results. Section 5
compares the results obtained by the application of the AHP method with those
obtained by using the simple weighted average for aggregation. Section 6 discusses
some related work and Sect. 7 concludes our work and points directions for future
work.
2 Aspect-Oriented Requirements Analysis Approach
From the AORE approaches studied (e.g., [4, 6, 13, 17, 18]), the Aspect-Oriented
Requirements Analysis (AORA) approach [6, 7] is the one that collects enough
information during requirements to allow a direct use of MCDM techniques.
Therefore, this approach was chosen for this work. AORA defines three primary
tasks, each one divided into several subtasks, as illustrated in Fig. 1
.
These tasks can
be accomplished iteratively and incrementally.
AORA Model
Plan 0:
1
2 3
(0.1)
(0.2)
(0.3)
Identify
Concerns
Specify
Concerns
Compose
Concerns
Plan 1:
12
(1.1)
(1.2)
Elicit
concerns
Reuse of
catalogues
Plan 2:
1 2 3
4 5
(2.1)
Identify
responsibilities
(2.2)
(2.3)
Identify
required
concerns
(2.4)
(2.5)
Identify
contributions
Identify
priorities
Build
concern models
Plan 3:
1
2 3
4
(3.1)
(3.2)
(3.3)
(3.4)
Identify
match
Identify
crosscutting
concerns
Handle
conflicts
Define
composition
rules
points
Fig. 1.
AORA model [6, 7]
2.1 Identify Concerns
This task
aims at identifying the concerns of a system, where a
concern
refers to a
matter of interest which addresses a certain problem that is of importance to one or
more stakeholders. Such a concern can be defined as a set of coherent requirements,
defining a property that the future system must provide. This can be accomplished by
analyzing the initial requirements, transcripts of stakeholders' interviews, etc. Good
sources for concern identification are the existing catalogues, such as the non-
functional requirements catalogue offered by Chung et al. [11].
Search WWH ::
Custom Search