Information Technology Reference
In-Depth Information
3.2.9 Information Systems Work and Analysis of Changes
(ISAC)
Information Systems Work and Analysis of Changes, known as ISAC, was devel-
oped in the 1970s at the Institute for Development of Activities in Organizations in
Stockholm, Sweden. It is a methodology for IS development that centers on the
client
s needs, and it was created in order to guarantee that the business gets the IS it
requires. Therefore, it starts with thorough analysis of the organization
'
'
s present
situation and the speci
c problem, and aligns the development of the system by the
perspective of that analysis. It maintains the emphasis on the organization
c
issues and needs, by encouraging the participation of users and all other stakeholders
in the development process, monitored by the developers (Wieringa
1996
).
Nilsson (
1989
) states that the ISAC methodology, in general, spans two main
development areas. Change analysis consists of the examination of problems, and
possible solutions, for business activities in a company. ISD consists of the analysis
and design of the IS as a support to the business activities.
The ISAC approach is based on the notion that by establishing an IS, one alters
the environment, rather than creating a new one (Hanani and Shoval
1986
).
Moreover, ISAC is a methodology oriented to the problem, which attempts at
specifying its root causes and solutions. But because it is focused on business
demands, it is essentially used for client-oriented development.
ISAC can be divided into four stages that focus on user and management
questions. The following table (Table
3.3
)de
'
s speci
nes each of the four stages, according
to Wieringa (
1996
).
ISAC is primarily focused on problem analysis and activity modeling, while
neglecting data modeling techniques, which lead to some researchers combining it
with data modeling methodologies of IS development in order to improve its
flexibility (Wieringa
1996
).
It can also be asserted that ISAC is not adequate for complex control systems
(Wieringa
1996
). Its encouragement of user participation and preference for
meetings rather than documentation means it stands closer to the agile spectrum of
IS development and therefore is more suitable for client-focused projects with
dynamic requirements.
Table 3.3 Stages of ISAC
Change
analysis
The main goal is to identify the organization
is needs, by identifying the
problem and what changes need to be performed in order to overcome it
'
Activity study
The selected model of the situation is broken down into information
subsystems, so as to allow for the identification of essential features and
interfaces between the subsystems
Information
analysis
A speci
cation of which inputs and outputs the IS has, and what are the
quantitative requirements of each subsystem
Implementation
A decision is made on the technology that will be used to build the IS, and it
is designed and programmed accordingly
Search WWH ::
Custom Search