Chapter 5: Meta Modeling Concepts Generic Frameworks I: Evaluating Methods and Tools
Chapter 5: Meta Modeling Concepts Generic Frameworks I: Evaluating Methods and Tools
i. Conceptual level
High level overview description of the Universe of Discourse (UoD).
Example: the domain of interest for Overall IS or
Business System or
Society
ii. Logical level
Description of the IS without any references to the technology that could be used to
implement it.
Its scope, not concerned with modeling the UoD .
PROCESS MODELLING
1) Functional decomposition
Breaking down of a complex problem into more and more detail and a disciplined way.
Lowest level -> the units are simple and manageable enough so that they could be reflected
in a few lines of computer program code.
Enable people to
view the
processes at
different levels
System analysts
and user – > high
level
Programmer ->
low level
2) Decision Trees
Documentation of process logic (where there are many decision alternatives)
3) Decision Table
Inbuilt verification mechanism -> to check all the conditions have been catered for.
5) Structured English
“Readable” computer program
DATA MODELLING
Strengths:
o Data is more stable than process
Processes are more susceptible to change than data
Data constitute a better, more stable, basis for the design of an IS. Process
change. Example: students’ data more stable, registration process change.
o It is a model which is readily understandable by both developers and users because of it
graphical form.
o It is independent of any physical implementation (it is at a logical level)
o It does not show bias toward particular users as departmental views. The data model
can reflect a variety of different views of the data.
OBJECT MODELLING
Benefits:
i. Unify many aspects of IS Development process.
Example:
Analysis -> use object analysis and object modeling
Design -> use object orientation as the design approach
Human-computer interface -> designed using object oriented methods
Development -> Object programming languages, object-oriented tools
Data collection -> Object oriented multimedia database
ii. It facilitates the realistic reuse of software code and therefore makes application
development quicker and more robust.
Organization will develop a library of object classes that deal with all the basic
activities.
Software development -> selection and connection of existing classes
into relevant applications. (all classes are well tried and tested)
iii. It integrates methods of systems development with the system context
System not only for the purpose to replace labour intensive operation. It is to
support individuals in problem solving / communication.
Example: a system that dispatches ambulances to emergencies. Important:
Interaction of the ambulances / other vehicles / service
Ambulance drivers and their way of working
The patient and their potential injuries / problems
The hospital that may receive the patient.
iv. The ability to tackle more challenging problem situation because of the understanding
that the approach brings to the problem situation.
v. The improvement of analyst-user relationship, because the approach can be understood
by both equally and because it is not computer oriented.
vi. The improvement in the consistency of results, because it models all aspects of the
problem in the same way.
vii. The ability to represent factors for change in the model so leading to a more resilient
model.
CONCLUSION
Process Model
o Logical analysis of the processes and not the physical implementation.
o Focus on “what” not “how”
o Techniques
Functional Decomposition
Decision Tree
Decision Table
Data Flow Diagram
Structured English
Data Model
o Throught “identifying Entities” and after that “Entity Relationship Diagram”
o Independent of any physical implementation.
Object Model
o Involves the modeling of data and processes.
o It facilitates the realistic re-use of software code and therefore makes application
development quicker and more robust.