Deficiencies in the process of determining requirements for an information
system has long been recognized as the major reason for the lack of success
of many information system development projects. Recognizing and interpreting,
describing and realizing requirements continue however to be problematic.
The solutions propagated most often by research, emphasize formal engineering
methods. That is modeling, tools and languages. However the problem as
well as the solution, when one is studying the relaying of ideas, have
more to do with people, how they are organized and how they communicate.
On the basis of the issues identified from the broad range of systems development
research, an explicit organizational structure will be proposed which should
enable customer organizations themselves to contribute to an increase in
the success rate of system development projects. This study is hence of
both a theoretical and practical nature. The results are a list of guidelines
for customer organizations suggesting how to prepare for requirements determination.
Enterprise Modelling:From F3 (Fuzzy to Formal) To P3 (Putting Participation in Perspective)
Submitted to the 10th CAiSE 98, Pisa, Italy, June 8-12, 1998.
Abstract
In the current ELEKTRA project, Enterprise Modelling, based on a further
development from the F3 project is being used to elicit domain knowledge
from stakeholders. The knowledge, skills, and expectations of these stakeholders
as they are involved in group-based participatory modelling sessions must
inevitably influence the contribution they make to the models being constructed.
This paper intends to put these contributions in perspective by reflecting
on observation and study of Enterprise Modelling in practice in the ELEKTRA
project. It will be argued that it is of importance to take into account
the composition of, and situational factors affecting the modelling group.
To focus solely on the modelling technique or language used, which is the
common today misses a vital input into the modelling activity and hence
requirements engineering process. Implicit assumptions, which guide the
modelling process, will be discussed as well as factors affecting these.
Any Questions?
Just mail me.
Danny Brash