0% found this document useful (0 votes)
19 views

Com213 Marking Scheme 2020

Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
19 views

Com213 Marking Scheme 2020

Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 5

ADAMAWA STATE POLYTECHNIC YOLA.

COLLEGE OF SCIENCE AND TECHNOLOGY, COMPUTER SCIENCE DEPARTMENT


2019/2020 SESSION - UNIFIED MODDELING LANGUAGE (COM 213)
MARKING SCHEME

1a) Define Unified Modelling Language (UML)?


The Unified Modeling Language (UML) is a standard language for specifying, visualizing,
constructing, and documenting the artifacts of software systems, as well as for business modeling
and other non-software systems. The UML represents a collection of best engineering practices
that have proven successful in the modeling of large and complex systems. The UML is a very
important part of developing Object Oriented Software and the software development process.
(3 Marks)

b) What are the Goals of UML?


It is often said ‘A picture is worth a thousand words’, this absolutely fits while discussing about
UML. Therefore, the goals of UML is to give a comprehensive pictorial representation of software
development process.
The primary goals in the design of the UML were:
1. Provide users with a ready-to-use, expressive visual modeling language so they can develop and
exchange meaningful models.
2. Provide extensibility and specialization mechanisms to extend the core concepts.
3. Be independent of particular programming languages and development processes.
4. Provide a formal basis for understanding the modeling language.
5. Encourage the growth of the OO tools market.
6. Support higher-level development concepts such as collaborations, frameworks, patterns and
components.
7. Integrate best practices.
(6 Marks)
c) Purpose of the UML Class diagram.

The UML diagrams like activity diagram, sequence diagram can only give the sequence flow of the
application but class diagram is a bit different. So it is the most popular UML diagram in the coder
community.
So the purpose of the class diagram can be summarized as:
 Analysis and design of the static view of an application.
 Describe responsibilities of a system.
 Base for component and deployment diagrams.
 Forward and reverse engineering.

(6 Marks)

Question 1 = (15 Marks)

2. a) What are the Limitations of UML Language Application. (4 Marks).


 UML is not complete and it is not completely visual. Given some UML diagram, we can't be sure
to understand depicted part or behavior of the system from the diagram alone.
 Some information could be intentionally omitted from the diagram, some information
represented on the diagram could have different interpretations, and
 Some concepts of UML have no graphical notation at all, so there is no way to depict those on
diagrams. For example, semantics of multiplicity of actors and multiplicity of use cases on use
case diagrams is not defined precisely in the UML specification and could mean either concurrent
or successive usage of use cases.
 Name of an abstract classifier is shown in italics while final classifier has no specific graphical
notation, so there is no way to determine whether classifier is final or not from the diagram.
(4 Marks)
b) What are the 3 major elements of UML building blocks?

 UML building blocks


 Rules to connect the building blocks
 Common mechanisms of UML
(4 Marks)
c) Create a UML Diagram Order Management System.

(7 Marks)
Question 2 = (15 Marks)
3. a) The 4 UML Standard Specification:- (5 Marks)
UML is a standard modeling language that has the following specifications:
 Provides guidance as to the order of a team’s activities,
 Specifies what artifacts should be developed,
 Directs the tasks of individual developers and the team as a whole, and
 Offers criteria for monitoring and measuring a project’s products and activities.

b) UML Extensibility Notation: (10 Marks)


All the languages (Programming or Modeling) have some mechanism to extend its capabilities like
syntax, semantics etc.
In UML, Extensibility notations are used to enhance the power of the language. It is basically additional
elements used to represent some extra behaviour of the system. These extra behaviours are not covered
by the standard available notations.
UML is also having the following mechanisms to provide extensibility features.
 Stereotypes (Represents new elements)
 Tagged values (Represents new attributes)
 Constraints (Represents the boundaries)

(7 Marks)
 Question 3 = (15 Marks)

4.a) UML Class Notation: (5 Marks)


UML class is represented by the diagram shown below. The diagram is divided into four parts.
 The top section is used to name the class.
 The second one is used to show the attributes of the class.
 The third section is used to describe the operations performed by the class.
 The fourth section is optional to show any additional components.

Classes are used to represent objects. Objects can be anything having properties and responsibility.

b) Explain any 5 fundamental concepts of Object Oriented.


 Objects: Objects represent an entity and the basic building block.
 Class: Class is the blue print of an object.
 Abstraction: Abstraction represents the behavior of a real world entity.
 Encapsulation: Encapsulation is the mechanism of binding the data together and hiding them
from outside world.
 Inheritance: Inheritance is the mechanism of making new classes from existing one.
 Polymorphism: It defines the mechanism to exist in different forms.
(Any 5 of the above 7 fundamental concepts)
(5 Marks)

c) The building blocks of UML can be categorized as: Things, Relationships and Diagrams

THINGS: Things are the most important building blocks of UML. Things can be:
 Structural
 Behavioural
 Grouping
 Annotational
While Relationship is another most important building block of UML. It shows how elements are
associated with each other and this association describes the functionality of an application. (5 Marks)

Question 4 = (15 Marks)


5. a) Discuss the Role of UML in OO design.
UML is used for non-software systems the emphasis is on modelling object oriented software
applications. Most of the UML diagrams discussed so far are used to model different aspects like
static, dynamic etc. Now what ever be the aspect the artefacts are nothing but objects.
If we look into class diagram, object diagram, collaboration diagram, interaction diagrams all
would basically be designed based on the objects.
So the relation between OO design and UML is very important to understand. The OO design is
transformed into UML diagrams according to the requirement. Before understanding the UML in
details the OO concepts should be learned properly. Once the OO analysis and design is done the
next step is very easy. The input from the OO analysis and design is the input to the UML
diagrams.

(9 Marks)
b) Architectural Diagram:
Architectural model represents the overall framework of the system. It contains both structural and
behavioural elements of the system. Architectural model can be defined as the blue print of the
entire system.
• Package diagram comes under architectural modeling. (6 Marks)

Question 5 = (15 Marks)

6a) UML Component Notation:


A component in UML is shown as below with a name inside. Additional elements can be added wherever
required.
Component is used to represent any part of a system for which UML diagrams are made. (5 Marks)

6b) With the aid of diagrams, write short notes on the following UML Building blocks:
i. Generalization
ii. Collaboration
iii. Node
iv. Dependency
v. Association. (10 Marks)

Generalization: can be defined as a relationship which connects a specialized element with a


generalized element. It basically describes inheritance relationship in the world of objects.

Collaboration: defines interaction between elements.

Node: A node can be defined as a physical element that exists at run time.

Dependency: Dependency is a relationship between two things in which change in one element also
affects the other one.

Association: Association is basically a set of links that connects elements of an UML model. It also
describes how many objects are taking part in that relationship.

(10 Marks)
Question 6 = (15 Marks

You might also like