IJCST Vo l . 4, ISS u e 2, Ap r I l - Ju n e 2013 ISSN : 0976-8491 (Online) | ISSN : 2229-4333 (Print)
www.ijcst.com
490 InternatIonal Journal of Computer SCIenCe and teChnology
Modelling of Requirement Elicitation for the Complete
Banking System Using Agent Goal
Decision Information Approach
1Sandeep Mathur, 2Girish Sharma, 3A K Soni
1Amity University, Noida, UP, India
2BPIBS Shakarpur Delhi, India
3Dept. of IT, Sharda University, Greater Noida, UP, India
Abstract
Most of the data ware house project fails to meet the business
requirements and business goals. One of the reasons for this
is that requirement analysis is typically not done with keeping
the actual working conditions and situations. This leads the
improper requirement engineering phase. The chaos all through
the development of requirements evolves due to disparity between
users and developers resulting in project devastations and
terminations. Building a data warehouse is a very challenging task.
Data warehouse quality depends on the quality of its requirement
engineering models. Agent orientation is emerging as a unique
paradigm for constructing Data ware house. Agent oriented
systems are expected to be more powerful, more flexible, and
more robust than conventional software systems. Here presenting
the detail discussion of agent oriented methodology based model
AGDI used in early as well as late requirement elicitation. This
approach is illustrated through a case study of the general banking
system in [24] for which Data Ware house is to be built to support
decisional goals. In this paper the complete solution for banking
system is explored
Keywords
Data Ware House (DWH), Requirement Elicitation, Agents, Goal
Decision Information Model (GDI), AGDI
I. Introduction
Critical business decisions depend upon the availability of
proper strategic information in the enterprise [1, 5] and [7]. Data
Warehouse (DW) systems are used by decision makers to analyze.
DW acknowledged as one of the most complex information system
modules and its design and maintenance is characterized by several
complexity factors.
The solution of the aforesaid problem is data ware house. The
data warehouse is primarily used for the decisional purposes and
supports on-line analytical processing. The data in data warehouse
is historical in nature available in very huge amount. Because
of these basic requirements of a data warehouse system, the
development of a data warehouse system is also different from the
development of a conventional operational system. Therefore the
data warehouse design process has not been supported by a formal
requirements analysis method though there are some approaches
for requirements gathering. Thus requirements engineering for
the data warehouse aims to identifying the information needs of
the decision-makers. In recent years, requirements engineering
for DW has acquired importance. [7, 13, 17]. A relationship of
the Data Warehouse to the organizational context is established
at the requirements level. The requirements Engineering task has
been divided into two phases: early requirements engineering
phase and late requirements engineering phase [4, 23]. The early
phase of requirements engineering activities include to consider
how the intended system would meet organizational goals, why
the system is needed, The emphasis here is on understanding the
―whys‖ that underlies system requirements, rather than on the
precise and detailed specification of ―what‖ the system should
do. The late requirement analysis describes the developing system
within its operational environment along with its function and
properties. Now this phase specifies what the system will do and
how it will be done.
II. Agent Goal Decision Information Model
Fig. 1: Snap Short of Agent Goal Information Model
The notion agent represents each and every user of the system.
They can be stock holders, decision makers, information providers
etc. The organizational goals can be achieved by combining the
individuals goals of each stakeholders which can be in turn
depends on each other. The Agent may depend on another agent
for goals to be achieved, decisions to be suggested & information
to be provided. These dependencies among agents are called goal,
decision & information dependencies respectively. The extended
GDI model is called an AGDI model [8-9]. AGDI model is used
to support organization modelling and goal modelling activities.
AGDI uses the following concepts for requirement modelling
Agents
position of an agent can be considered as actors of use case
diagram. It represents the various users, stakeholders, decision
makers and users of the organization [8]. Defines various different
types of roles that termed as actors. The agent can be internal,
external depending upon the working of the agents’ w.r.t. to system.
Agents can be either simple agents or complex agents.
Agents & Goals
Goal are the objectives of agents to be achieve by the organization.
These goals are the prime driving force in requirement elicitation
for the developing DWH. Goals can be simple or complex that
can be subdivided into simple goals. These goals may have two
or more actors’ dependencies to achieving a particular goal.
