Free Essays, Term Papers, Research Papers at Anti Essays

Tactics Based Approach for Integrating/ Non-Functional Requirements In Object-
Oriented Analysis and Design
Abstract
Non-Functional Requirements (NFRs) are rarely treated as \¯rst-class" elements in software
development as Functional Requirements are. Often they are stated informally and incorporated
in the ¯nal software as an after-thought. We leverage existing research work for the treatment of
NFRs to propose an approach that enables to systematically analyze and design NFRs in parallel
with functional requirements. Our approach premises on the importance of focusing on tactics
(the speci¯cs approaches used to ful¯ll NFRs) as opposed to focusing on NFRs themselves.
The speci¯c advantages of such approach includes ¯lling the gap between NFRs elicitation and
NFRs implementation, systematically treating NFRs through grouping of tactics so that tactics
in the same group can be addressed uniformly, remedying some shortcomings in existing work
(by prioritizing NFRs and analyzing tradeo® among NFRs), and integration of FRs and NFRs
by treating them as ¯rst-class entities.
Key Words: NFRs Analysis and Design, Software Design, NFR Framework, Aspect Oriented
Software Design
1 Introduction
The analysis and design of Functional Requirements (FRs) has received much attention since the
early days of software engineering. As a result, a number of approaches including waterfall[1],
iterative[2], and Rational Uni¯ed Process[3] have been proposed for capturing those functional re-
quirements. In addition, modeling languages such as UML (Uni¯ed Modeling Language)[4] make it
easier, by providing a common vocabulary for every stakeholder, to capture, analyze, and document
FRs (among other advantages). Therefore, software developers often dwell on eliciting, analyzing,
designing, implementing, testing, and maintaining FRs...