Information Modelling with ORM - Desklib

This article discusses Information Modelling with ORM and its importance in the online library for study material with solved assignments, essays, dissertation etc. It explores the ORM diagram and fact diagrams for entities like PC, Worker, Programming Language, Student, Book, Exam and Department. The article also covers uniqueness and mandatory constraints for each entity.

Running Head: INFORMATION MODELLING
Information Modelling with ORM
Student’s Name:
Institution Affiliation:

Information Modelling
TASK1
Part1
Question 1
It is the process of coming up with abstract models or prototypes of system components. The
representation is through graphical notations in the Unified Modelling Language (UML). This
description helps the experts to realize the functionality of the system and models are useful in
communicating to the end users.
Question 2
The use of different model helps to conceptualize and construct the system in different point
of views. Example, Functional model helps to represent the functions/activities/processes in a
specific structure; System architecture is a model that is used to describe the behavior of a
system, among others.
Part 2
Step1:
The following are elementary facts, and profound structure sentences identified based on the
familiar examples from the scenario.
(1)The Worker with Initials ‘EFC’ uses the PC with PC Nr ‘pc01
(2)The Worker with Initials 'EFC' uses the room with room No 507.
(3) The worker uses Pc with No pc03 with Initials PAB.
(4) A worker uses Pc with No pc03 with Initials JM.
(5) Pc with No pc03 is stored in room no 618.

Information Modelling
(6) Pc with No pc03 has Hope, Miranda programming languages installed.
(7) Programming language COBOL is of type Procedural programming paradigm.
(9) Programming language COBOL is of type Procedural programming paradigm is taught by
Experts with Worker Initials PNC in roomNo508, REK in room No 611.
(10) Prolog which is a declarative programming paradigm which is guided by worker/expert with
initials JM for 3 hrs.
(11).The worker with initials PNC is an expert of COBOL which is a programming Language of
declarative type.
Step2:
Above is an ORM diagram that captures details of how workers get assigned to different
PCs which get stationed in separate rooms where the workers are. The PCs have that are installed
Worker PC
Language
ORM Diagram for Information Systems.
uses/is used
by
Room
is in/has
expert in/teach
es/
Declarative
Functional
Procedural
Hours
type/
type/
type/ taught for/
installed/has

Information Modelling
with the different programming language which belongs to a different paradigm and gets taught
by various experts at different times.
Below are examples of facts diagrams:
The above fact table demonstrates the facts types used to come up with the entities
Worker and PC, and they are elementary since each worker get assigned to a PC, and a pc can
get attached to at least one worker. Example: From the fact table above, a worker with initials
PAB get accredited to PC with PCNO pc03, and Pc01 get assigned to both worker with initials
EFC and worker with initials TAH.
PC
Room
is in/has
Worker PC
uses/is used by
EFC pc01
TAH pc01
NW pc05
PAB pc03
Pc01 507
Pc03 618
Pc04 508

Information Modelling
The above fact table demonstrates the facts types used to come up with the entities PC
and Room. Each PC is stored or get assigned to a room. Example: From the diagram above, pc01
is assigned to room No 507. These rooms' numbers also helps to identify the place where the
worker is assigned since each worker get attached to a PC which has to have a room
The above fact table demonstrates the facts types used to come up with the entities
Worker and Programming language. Some workers are expert in one or more programming
languages, and a programming language can get only taught by a worker who is an expert.
Example: From the diagram above, a worker with initial PNC is an expert in COBOL
programming language which is a type of procedural programming (Oakshot, 2016). COBOL
can be only taught an expert worker like a person with initial PNC.
Worker
Programminglan
guage
expert in/taught by
PN
C
COBO
L
JM LISP
PA
B
Mirand
a
JS Prolog

Information Modelling
Step 3:
From the diagram the entities are specific, and hence there is no need to combine them
since they exist as objects of their own. The picture shows the constraints of the units, therefore,
they have to remain as single. For Example, Pc with No pc03 is used by Worker with Initials
PAB. PC and Worker have to exist separately. One worker gets assigned to 1 PC, and one
worker can access 1 PC at any time.
Step4:
Uniqueness Constraints
From the diagram, unique constraints are represented by the two-arrow sign.
a. There exist a unique constraint between Worker and PC in that, each worker has access to
precisely one PC, and at least one Worker accesses each PC. Each worker has to have a
PC which he/she has to access, and a PC can have accounts of different workers who can
access it at different times. Hence it is possible to find the number of workers that access
the same PC.
b. There is a unique constraint between PC and Room. Each PC has to get allocated to a
room. So for every PC in that might arise, it has to get found in a specific room, so it is
possible to find out the number of PC in one particular place.
c. There is a unique constraint between worker/expert and language. An expert teaches
every programming language. The different styles get assigned to a different expert who
teaches them.
d. There is a unique constraint between PC and language. Every pc has a style that gets

Information Modelling
installed in it, and a specific language gets installed on a PC.
Step5:
Mandatory Constraints
From the diagram above (in step 2) binding constraints are indicated by a solid dot at the
joint of the entity type and the line showing the role (Oakshot, 2016). It gets used when the
object type plays a mandatory position. From the diagram, there is a compulsory constraint
between entity worker and entity pc. That is each worker has access to one Personal computer
using their initials. For a worker to performs there task like teaching specific programming or
being an expert in a language, they must have access to a PC. Example: A worker with initials
‘EFC' has access to or uses the PC with initial Pc01. Also from the diagram, there is a mandatory
constraint between entity type PC and entity type Room. That is every PC must get stored in a
particular room. PC is strongly dependent on a room. A room can exist and can or cannot contain
any PC, but a PC must get stored in a particular place. Example; PC with initial Pc01 should get
kept in a room with room number 507.

Information Modelling
TASK2
Part1
Step1:
The following are elementary facts, and profound structure sentences identified based on the
familiar examples from the scenario.
(1)The student with Regno ‘01’ is in department with initials ‘CS.'
(2)The student with Regno ‘01’ can borrow a book with id ‘01’.
(3)The Student with Regno ‘01' can learn programming language ‘COBOL.'
(4)The Student with Regno ‘01' can sit for an exam for a programming language.
Step2:
Department Student
Language
ORM Diagram for Information Systems.
/has
Book
borrow or
read/
learns/
Exam
of/
of/
do/

Information Modelling
The ORM diagram above illustrates the additional features that can get added to the
information system. It has entities department, exam, student, language, and book.
Below are fact diagrams of the additional entities;
The above fact table demonstrates the facts types used to come up
with the entities Student and Programming language, and they are
elementary since each student has to learn one or more programming
language. One programming language can get determined by more than one student (Vernadat,
2010). Example: From the fact table above, a student with initials regNo ‘01' is learning a
COBOL. COBOL is not limited to a student with initial regNo ‘01' but can also be learned by
other students.
Student Language
learns/
regNo'
01'
COB
OL
regNo'
02'
LISP
regNo'
03'
Mira
nda
regNo'
04'
Prolo
g

Information Modelling
The above fact table demonstrates the facts types used to come up
with the entities Student and Exam, and they are elementary since
each student has to do an exam (Vernadat, 2010). One student can do one
review at a particular time, i.e., two exams cannot get done by one student at the same time.
Example: From the fact table above, a student with initials regNo ‘01' is doing the exam with
exam number Exam 01.
Student Exam
do/
regNo'0
1'
Exa
m
01
regNo'0
2'
Exa
m
02
regNo'0
3'
Exa
m
03
regNo'0
4'
Exa
m
04

Information Modelling
The above fact table demonstrates the facts types used to come up with the entities
Student and Book, and they are elementary since the student can borrow a book. Only one book
can get assigned to a student. That is two students cannot acquire the same book at the same
time. Example: From the above fact type table student with initial regNo ‘01’ is borrowing book
with book number Book 1
Step3:
From the diagram the entities are specific, and hence there is no need to combine them
since they exist as objects of their own. The structure shows the constraints found in the entities;
thus they have to remain as single. For Example, A student has to belong to a particular
Student Book
borrow/
regNo'
01'
Boo
k 1
regNo'
02'
Boo
k 2
regNo'
03'
Boo
k 3
regNo'
04'
Prol
og

Information Modelling
department, and a Student can borrow a specific book which is one specific programming
language. The student can also do an exam in a programming language.
Step4:
Uniqueness Constraints
From the diagram, unique constraints are represented by the two-arrow sign.
a. There exist a unique constraint between Student and department in that, each student can
have to belong to a specific office.
b. There is a unique constraint between Exam and Language. Each exam is a specific
language, and each style has a particular review.
Step5:
Mandatory Constraints
From the diagram above (in step 2) necessary constraints are indicated by a solid dot at
the joint of the entity type and the line showing the role. It gets used when the object type plays a
mandatory position. From the diagram, there is a compulsory constraint between entity Student
and entity department. That is each student belongs to a particular office. For every student that
exists in an institution or the information system, he/she must belong to an individual
department. A student cannot be without a unit. The unit can exist without a student but not the
other way round.
References
Vernadat, F.B. 2010. Enterprise Modelling and Integration, Chapman & Hall, London.
Oakshot, L. 2016. Business Modelling and Simulation, Pitman Publishing, London.

Information Modelling