Business and ISD modelling problems

Get Complete Project Material File(s) Now! »

Introduction

The researcher, in his work experience, has found that one of the problems hampering information systems development (ISD) is the lack of a truly integrated modelling technique or set of techniques. Truly integrated modelling techniques will support modelling during all the phases of the ISD life cycle, from business analysis and systems design to development, and ultimately the maintenance of the resultant system. Integration does not pose such a huge problem during the later phases of system design and development. Techniques such as the Unified Modelling Language (UML) provide for modelling integration during the later phases of the ISD life cycle
more than adequately.

Background

Iivari, Hirscheim and Klein (2001b) point to the emphasis in ISD literature on improving ISD by the use of new tools, techniques, methods or methodologies. As a result of this emphasis, there is a proliferation of ISD paradigms, approaches, methodologies, methods, techniques and tools. This causes many problems for researchers and practitioners alike. If there are so many tools, techniques, paradigms and approaches, which ones should be used and how can decisions be made about them (Wand and Wang, 1996; Wyssusek, 2006)?

ISD problems

It is clear from the literature that a number of problems exist in ISD. The first and main problem relates to the sheer number of different approaches, methodologies and techniques in ISD. Iivari, Hirschheim and Klein (2001a:180) have identified four ISD paradigms and eleven approaches to ISD, and further point out the “… unabated proliferation of new methods and tools for developing information systems…”. They refer to research by Jayaratna (1994) showing the existence of over 1000 ISD methodologies already in 1994. This situation caused Avison and Fitzgerald (2006:566) to call this a “methodology jungle” and to ask: “Where to now for development methodologies?” (Avison and Fitzgerald, 2003:79). Oei et al. (1992:2) call it the “YAMA Syndrome” (yet another modelling approach).

Gailly and Poels (2007:407) define the goal of business modelling as follows: “… to create semantically faithful and pragmatically usable representations of business domain artefacts (e.g. transactions, processes, value chains).” In this section, business modelling problems are discussed from the viewpoint of general business domain modelling and the more specific viewpoints of business process modelling, requirements modelling and business rules modelling. Finally, problems related to linking business and systems modelling are discussed.

1. Introduction
1.1 Introduction
1.2 Background
1.3 Motivation for this study
1.3.1 ISD problems
1.3.2 Business and ISD modelling problems
1.3.3 Comparison with other disciplines
1.4 Research approach
1.4.1 Problem statement and research questions
1.4.2 Research methodology
1.4.3 The basis for the proposed integrative technique
1.4.4 Scope and limitations
1.5 Layout of thesis
1.6 Conclusion
2. Theoretical foundations
2.1 Introduction
2.2 Information
2.3 Systems theory
2.3.1 Systems thinking
2.3.2 System characteristics
2.3.3 System hierarchies
2.3.4 Complex engineering systems
2.3.5 System complexity
2.3.6 System control
2.4 Enterprise architecture
2.4.1 Background
2.4.2 Fundamental concepts
2.4.3 Zachman rows
2.4.4 Zachman columns
2.5 Conclusion
3. Business rules
3.1 Introduction
3.2 Business rules and ISD
3.3 Types of business rules
3.3.1 The Business Rules Group’s classification
3.3.2 Other business rule classifications
3.3.3 Summary of business rule types
3.4 Business rule relationships
3.5 Business rule representation
3.6 Conclusion
4. Part-whole relationships
4.1 Introduction
4.2 Background
4.3 Overview
4.4 Part-whole classifications
4.4.1 Classical mereology and classical extended mereology
4.4.2 The Opdahl et al. framework
4.4.3 The Gerstl and Pribbenow framework
4.5 Part-whole relationships in ISD
4.6 Conclusion
5. A linguistic analysis of IS modelling
5.1 Introduction
5.2 Linguistics and IS modelling
5.2.1 Morphology
5.2.2 Syntax
5.2.3 Semantics
5.2.4 Pragmatics
5.3 Conclusion
6. Research approach
6.1 Introduction
6.2 Research objectives, statement and questions
6.3 Research design
6.3.1 Research philosophy
6.3.2 The grounded approach
6.3.3 Data collection
6.4 Design science research
6.4.1 Background
6.4.2 Research methodology
6.4.3 Research output
6.4.4 Research guidelines
6.4.5 Design Science Research Theory
6.5 The journey
6.5.1 Part 1 – Grounded approach
6.5.2 Part 2 – Design science research
6.6 Conclusion
7. The Proposed Integrative Modelling Technique
7.1 Introduction
7.2 Overview of the modelling technique
7.3 The modelling technique in detail
7.3.1 Base entities
7.3.2 Structure entities
7.3.3 Role entities
7.4 Conclusion
8. Demonstration, implementation and evaluation of proposed integrative modelling language
8.1 Introduction
8.2 Case study
8.3 Demonstration and evaluation per perspective
8.3.1 Perspective 1: Business rules
8.3.2 Perspective 2: ISD modelling
8.3.3 Perspective 3: Requirements modelling using use cases
8.4 Implementation of the technique as software
8.5 Linking the integrative technique back to existing ISD techniques
8.6 Conclusion
9. Conclusion
9.1 Introduction
9.2 Answering the research questions
9.2.1 Is there a gap between business and ISD that current modelling cannot fill?
9.2.2 What are the fundamental constructs of any integrative modelling technique between business and ISD?
9.2.3 What are the properties and attributes of these fundamental constructs?
9.2.4 What are the relationships between these fundamental constructs?
9.2.5 Can it be demonstrated that the proposed technique does indeed integrate business and existing modelling techniques better than existing business modelling techniques?
9.3 Evaluation of the research
9.3.1 Grounded approach evaluation
9.3.2 Design science research evaluation
9.4 Contribution of the research
9.5 Future research
9.6 Concluding remarks
10. Appendix A: Derivation of basic concepts of integrated modelling language
10.1 Introduction
10.2 The grounded analysis codes
10.2.1 Agent
10.2.2 Thing
10.2.3 Action
10.2.4 Event
10.2.5 Location
10.2.6 View
10.2.7 Relationship
10.2.8 Language
10.2.9 Rule
10.3 Conclusion
11. Bibliography