Name

: Navindren Baskaran

Student ID

: TP037027

(1) What is a model?

Model can be also referred as diagrams. Model or modeling is used in the field of science and
technology to provide an abstraction of a system at some level of precision and details. A model
is then analyzed to obtain a better understanding of a system which is being developed or to be
developed. A model is actually the designing of software application before coding. Through the
model or the modeling technique certain information can be gained such as the requirement of
the users through data flows, the communication between the system through sequence diagram,
this are very important because this model act as the input to several users the basic data
flow(use-cases) can be used by the end users whereas the several diagrams with technical
notations will be used by the developers to develop the software.

(2) What is UML model, Data Model and Code Model?

UML Model:
UML model is actually a representation of the overall system as a whole, the model doesnt not
contain much details about the system. UML has to modeling techniques static modeling and
dynamic modeling.
Static Modeling: The architecture is represented in terms of classes and relationships
which can be associated
Dynamic Modeling: This view describes the architecture in terms of objects as well as the
interaction between the objects.
Data Model:
Data model represents the type of data needed by a database. A data model actually shows the
relationship between each data in the database. The data contained in the database will be used to
define the primary keys, relational tables and foreign key in the table. The data model focuses on
what are the data needed and the how is the data organized rather than what operations will be
performed on the data.
The goal of the data modeling is to ensure that all data which are collected are accurate , it is
easy for the end users to review and verify thanks to the understandable easy notations and
natural language. The data model has sufficient and detailed data to use it as a blueprint to build
a physical database.

Code Model:
Code model is a process of converting UML diagrams in to behavioral source codes. For an
example a class diagram which has its own set of properties and methods can be converted into
source codes which implement the properties and the methods.

(3) Compare UML model and UML diagrams?

As explained earlier UML models are the representation of the whole system, it has two views of
the UML model which is the static view and the dynamic view. The static view the structure of
the system in terms of objects, attributes and the relationships among them ex: Class diagrams.
Whereas the dynamic view shows the interaction and states between the object when performing
a certain process ex: Sequence diagram, State-Machine.
Diagrams are partial representation of a system, where it only represent a component or a process
of a system. The diagrams can be categorized in three groups, Structure diagrams, Behavior
diagrams and Interaction diagram.
Structure diagrams:
Emphasizes on things that must be there (present) in the system being modeled. Ex class
diagrams: Which describes the systems classes, its attributes and the relationship among the
classes.
Behavior diagram:
Emphasizes on what must happen in the system being modeled. Ex: Activity diagram: Which
shows the steps taken by users to fulfill a process or a request using the system, this typically
shows the business flow of the system.
Interaction diagram:
Emphasizes on the flow of the system and the data passed among them. Ex: Communication
diagram: Shows the interaction between the objects and the information passed among them.

(4) List out UML diagrams?

(a) Use Case diagram defines the interaction between the actor (users) and the system.
(b) Class diagram - describes the systems classes, its attributes and the relationship among
the classes.
(c) Communication diagram shows how objects interacts with each other by sending and
receiving message.
(d) State Machine diagram to describe the state of an object when a process occurs.
(e) Activity diagram to describe the steps and the condition that has to be taken to complete
a certain activity by the user through the system.
(5) How many diagrams do you need in a system?
There is no specific amount of on how many UML diagrams that the developer has to create, the
main purpose of various type of UML diagrams are because all of the diagrams represent or
serves to bring out different information out of the system. This UML diagrams are usually used
to explore the system in more detail and to gain better understanding of the system.
(6) Differentiate the UML elements and the diagrams?
The main element of the UML diagrams, are the notations. There a unique set of notations for
each diagram. The diagram is a partial graphical representation of the system but in order to
provide the correct diagram, the correct diagram notations has to be used.
Example:

The notation above show a class, a class typically contains the class name as the header and after
the header it is separated into to two main segments which is the attributes, and the operations.
The attributes are the properties of the class and the operations are the actions that can be
performed by a certain class. Special symbols such as:
+ public

# protected
- private
Each of the symbols above represents the access modifiers for the class properties and the
operations.
Example:

The notations above is used to represents the users in Use Case diagram to show the interaction
between the users and the system.
Example:

The above symbol shows the notation for the activity diagram which indicates the starting point
of a specific process.

The above notation indicates the end of a process in an activity diagram.