Turbulence is in the nature of business environments. Changes brought about because of different requirements such as social, political, technical and economic, exert pressures on organisations to respond in a timely and cost effective way to these challenges. In such an unstable environment information system developers are challenged to develop systems that can meet the requirements of modern organisations.
In this decade organisations also experience the effects of the integration and evolution of Information Technology (IT). While information systems continue to serve traditional business needs such as co-ordination of production and enhancements of services offered, a new and important role has emerged namely the potential of such systems in adopting a more supervisory and strategic support role. These developments offer opportunities for changes to organisational structures and the improvement of business processes.
The traditional approach to information systems development has proved to be too monolithic and lacking facilities for dealing with highly complex, multidimensional, and distributed systems. In the traditional paradigm little attempt is made in understanding how the proposed system relates to other components (some of which may be legacy systems themselves) or the effect that the system will have on the enterprise itself. This paper advances a position, based on research work and the application of this work on many industrial and commercial applications, which states that 'the single most important factor to successful business evolution through the use of information technology is Enterprise Knowledge Management'. Enterprise Knowledge Management involves many facets of the information systems domain including technical (business processes, flow of information etc), organisational and social (policies, structures and work roles etc) and teleological (purposes and reasons) considerations. Conceptual modelling plays a central role in the way that one can capture, reason, represent, use for agreement between many stakeholders and discover new knowledge from legacy systems.
[1]
Bashar Nuseibeh,et al.
Managing inconsistencies in an evolving specification
,
1995,
Proceedings of 1995 IEEE International Symposium on Requirements Engineering (RE'95).
[2]
Kent L. Beck,et al.
Smalltalk best practice patterns
,
1996
.
[3]
B. F. Castro.
Buschmann, Frank; Meunier, Regine; Rohnert, Hans; Sommerlad, Peter; Stal, Michael. Pattern-oriented software architecture: a system of patterns, John Wiley & Sons Ltd, 1996
,
1997
.
[4]
John M. Wilson,et al.
Business Processes: Modelling and Analysis for Re-engineering and Improvement
,
1995
.
[5]
David C. Hay,et al.
Data Model Patterns: Conventions of Thought
,
1965
.
[6]
Ralph Johnson,et al.
design patterns elements of reusable object oriented software
,
2019
.
[7]
James O. Coplien,et al.
Pattern languages of program design
,
1995
.
[8]
Martin Fowler,et al.
Analysis patterns - reusable object models
,
1996,
Addison-Wesley series in object-oriented software engineering.
[9]
Kent Irwin,et al.
Workflow technology: trade-offs for business process re-engineering
,
1995,
COCS '95.
[10]
Laurian M. Chirica,et al.
The entity-relationship model: toward a unified view of data
,
1975,
SIGF.
[11]
Peter Coad,et al.
Object-oriented patterns
,
1992,
CACM.
[12]
John Mylopoulos,et al.
From E-R to "A-R" - Modelling Strategic Actor Relationships for Business Process Reengineering
,
1994,
ER.
[13]
John Mylopoulos,et al.
Understanding "why" in software process modelling, analysis, and design
,
1994,
Proceedings of 16th International Conference on Software Engineering.