Information Technology Reference
In-Depth Information
“the other system” is often seen to belong to “the real world” as opposed to the
abstract plans and specifications of the so far intangible information system to be.
Information systems are closely intertwined with computer systems. Modern
information systems are unthinkable unless based on computers, computation and
communication technology. So we have to distinguish between the information sys-
tem and its computer system, where the computer system is seen as a part of the
information system which it serves. The computerized parts of information sys-
tems are often called application systems (or data systems) reflecting that they apply
computer technology (to store and process data) in order to meet their aims. In the
Nordic countries it is common to distinguish between infology (the discipline of
information systems) and datalogy (the discipline of data systems).
In spite of having built information systems for half-a-century there is still much
to be desired in improving the cost-effectiveness of building and maintaining infor-
mation systems. The IT profession has attracted a vast talent pool over many years.
In spite of this there is widespread concern that the methodological basis for building
sustainable computerized information systems is too weak.
The dissatisfaction comes both from within the IT-profession and from the user
side, both from those who engineer the systems and from those who pay the bill
for failed projects. The IT-profession is not satisfied with itself. The self-criticism
comes both from the information system side [ 19] , and also from the data system
side, e.g., from software engineering [ 47] . Much of the dissatisfaction is due to the
profound technological changes of the last 10-20 years. Solutions to old problems
are no longer relevant in the new reality [ 32] . The academic community trans-
lates the dissatisfaction into research agendas aimed at defining new problems and
solutions [ 12, 19, 21, 23, 32] .
The recent SEMAT initiative [47] calls for improving current software engineer-
ing method and theory. Of particular concern is the perceived lack of a sound, widely
accepted theoretical basis for building and maintaining computerized systems of
sufficient size. The SEMAT initiative calls for developing an approach to software
engineering that is based on solid theory, proven principles and best practices, and
that includes a kernel of widely-agreed elements, extensible for specific uses, which
addresses both technology and people issues.
It is unclear why we have not reached further, why the dissatisfaction is so deep.
Research has been going on for several decades aiming at developing a sound theo-
retical basis for information systems engineering, see [4] for an overview. Research
results have come out both from the academic world and the industrial world. Even
if much progress has been achieved over the years there is still some way to go
before we can declare “mission accomplished”.
Some elements in an explanation may be that
domain issues are so different from computer issues that they demand different
treatment, so that it is difficult to arrive to a unified theory;
domain issues are so different from each other that the relationships between the
computer sphere and the various domains are so different that there is not one
solution for all, but separate solutions have to be developed for each computer-
domain pair;
Search WWH ::




Custom Search