Sinhgad College of Engineering, Pune-41

Department of Information Technology

414459: Computer Laboratory VIII (2015 Course)
End Semester Oral Examination

Question Bank
Q. No. Question
1 What Is Uml?
 UML is Unified Modeling Language.
 Graphical language for visualizing artifacts of the system.
 Allow to create a blue print of all the aspects of the system.

2 What Are The Three Types Of Modeling In Uml?

 Structural.
 Behavioural.
 Architectural.

3 What do you understand by UML?

UML stands for the Unified Modelling Language and it is also a graphical language for
visualization, construction and documenting for the artifacts of any of the system. You can
efficiently create the blueprints for various aspects before the actual physical implementation
of the system occurs.
4 What Is Uml Architecture?
Takes care structural and behavioural aspect of a software system. Includes software usage,
functionality, performance, reuse, economic and technology constraints
5 Define Modeling In Uml And It Advantages?
 Modeling is a proven and well-accepted engineering technique which helps build a
model.
 Model is a simplification of reality; it is a blueprint of the actual system that needs to
be built.
 Model helps to visualize the system.
 Model helps to specify the structural and behaviour of the system.
 Model helps make templates for constructing the system.
 Model helps document the system.

6 What do you understand by relationships in UML?

There are basically three different kinds of relationships which are -

 Dependencies - They are the relationship between two different entities. If any single
entity is changed then the impact would be laid on the other too. It also depicts that one
class use another class as an argument in the signature of the operation.
 Generalization - In this relationship, the specified class and subclass ratio is
evaluated. It also depicts that one entity inherits the properties of the other entity.
 Association - Association is a structural relationship between two different objects

7 Name 9 modeling diagrams that are frequently used?

 Use case diagram
  Class Diagram
 Object Diagram
 Sequence Diagram
 State chart Diagram
 Collaboration Diagram
 Activity Diagram
 Component diagram
 Deployment Diagram.

8 Explain The Types Of Diagrams In Uml?

 Use Case Diagram: Use Case Diagram describes HOW the system works. It
identifies the primary elements and processes that form the system. It shows actors and
their roles
 Class Diagram: This diagram explores detail design of the system. The class
diagram is designed using Use Case diagram. We can identify all Nouns in use cases as
classes and verbs as method of the classes.
 Object diagram: This diagram represents the state of classes in the system and their
relationships or associations at a specific point of time.
 State Diagram: This diagram represents different states that objects in the system
undergo during their life cycle.
 Sequence diagram: This diagram is used to explore logic of complex operations,
function or procedure. In this diagram, sequence of the interactions between the objects is
represented step by step.
 Collaboration diagram: This diagram groups together the interaction between
different objects.
 Activity diagram: Activity diagram gives detail view of the business logic.
 Deployment diagram: It shows deployment view of the system. It shows how
hardware and software works together to run system.

9 Explain What is Relationships? Different Types of relationships.

Relationships in UML are used to represent a connection between several things, or grouping
things. It is also called a link that describes how two or more things can relate to each other
during the execution of a system.

 Dependencies: Are relationships between two entities. A change in specification of

one thing may affect another thing. Most commonly it is used to show that one class uses
another class as an argument in the signature of the operation.
 Generalization: is relationships specified in the class subclass scenario, it is shown
when one entity inherits from other.
 Association (Realization): Association is the semantic relationship between classes
that shows how one instance is connected or merged with others in a system. The objects
are combined either logically or physically. Since it connects the object of one class to the
object of another class, it is categorized as a structural relationship.

10 How are the diagrams divided?

The nine diagrams are divided into static diagrams and dynamic diagrams.
11 Which are Static Diagrams (Structural Diagram)
Static Diagrams are also called Structural Diagram

 Class diagram,
 Object diagram,
 Component Diagram,
  Deployment diagram.

12 Which are Dynamic Diagrams (Behavioural Diagrams)

Dynamic Diagrams are also called Behavioural Diagrams

 Use Case Diagram,

 Sequence Diagram,
 Collaboration Diagram,
 Activity diagram,
 State chart diagram.

13 What Are Uml Messages?

Specification of a communication. A message is the specification of a communication, when
a message is passed that results in action that is in turn an executable statement.
14 What Is Component Diagrams In Uml?
A component diagram is particularly useful with teams of larger size. UML components are
great to perform architectural landscape for a specific system. The component diagram
allows to model high level software components and interfaces to those components. The sub
teams effort is very less, once the interfaces are perfectly designed and accepted by the team
members.
15 Explain The Different Elements of A Use Case?
Use case diagram is a subset of various behaviour diagrams. Use case diagrams are used to
provide concrete examples of the elements which are supposed to implement. It is used to
analyze objects. Following are the elements of the use case diagrams:

 Actors: An actor is one of the entities who perform certain actions. These roles are
the actual business roles of the users in given system. An actor interacts with a use case of
the system. For example, for a banking system, a customer is one of the actors.
 Use Case: A use case is a use case diagram of UML represents a business
functionality that is distinct. The use case should list the discrete business functionality that
is specified in the problem statement. Every business functionality is a potential use case.
 System boundary: A system boundary defines the scope of the system. The systems
that use cases also need to be defined in the limits of the system. The system boundary is
shown as a rectangle that spans all use cases of the system.

16 What are important tips for drawing a Use Case diagram?

 A simple and complete use case diagram should be articulated.
 A use case diagram should represent the most significant interaction among the
multiple interactions.
 At least one module of a system should be represented by the use case diagram.
 If the use case diagram is large and more complex, then it should be drawn more
generalized.

15 What are the various components in sequence diagrams?

 Actor: Actor represents an external user / end user who interact with the system.
 Object: Object is represented by one of components of the system.
 Unit: A unit is a subsystem, or a sub component or other entity within the system.
 Separator: Separator represents a boundary among sub systems, components or
units.
 Group: Represents different header elements in the subsystem.

16 What are the parts of a Deployment Diagram?

  Nodes: A node represents any hardware component. The configuration of hardware is
represented by attributes of nodes.
 Components: A component represents software. Each component straight represents
a class or object that in turn represents methods.
 Dependencies: The reliability of one component with that of another is depicted by
dependencies.
 Links: To tie up tow nodes, the links are utilized. The links are implemented by
using nodes and their associations.

17 What are the elements in State Chart diagrams?

 Initial State: This state shows the first activity of the flow.
 State: A state represents the state of an object at a particular given point of time.
 Transition: The transition from one state to another state of objects is represented by
an arrow.
 Event and Action: A trigger that causes a transition to occur.
 Signal: When a message or a trigger caused by an event to a state, which causes a
transition, this message is called as a signal.
 Final State: The state diagram ends with a diagram that depicts a bulls eye is known
as Final State.

18 What are the different elements of a collaboration diagram?

 Object: The interaction between objects takes place in a system. An object is
depicted by a rectangle with the name of the object, preceded by a colon and underline.
 Relation/Association: Association among objects is linked by connecting them. The
cardinality can be depicted by placing qualifiers on either ends.
 Messages: An arrow that commencing from one object to the destination object. This
depicts the interaction between objects. The sequence or order of the interaction is depicted
by the number.

19 Explain Elements In Activity Diagrams?

 Activities: An activity indicates an action that performed in the system.
 Transitions: Transitions are represented by open arrow heads. Transitions are used to
indicate the flow among elements in the diagram.
 Decision Points: The logical branching is depicted by the decision points.
 States: A state is shown in a rounded rectangle. States are indicated to mention the
mile stones of processing in the activity diagrams.

20 What is the difference between activity and sequence diagrams?

The following are the difference between Activity and Sequence Diagrams:
A sequence diagram shows the way of processes execute in a sequence. For example, the
order of operations and the parameters.

An activity diagram depicts the operational workflows.

A sequence diagram is focused to represent interactions between different objects.
Activity diagram shows the actions for various objects.
21 What is sdlc?
SDLC is Software Development Life Cycle. SDLC of a system included processes that are
Use case driven, Architecture centric and Iterative and Incremental.
22 State Some Benefits Of Iterative Development?
 Mitigation of risks in an earlier stage.
 Visibility of progress.
 Feedback, adaptation and engagement.
  Complexity management.
 Iteration management can improve the overall process of the project because it details
and explains the various steps present in it.

23 Explain about Dependency?

This form of relationship exists when a change to a certain element changes the definition
and structure of the other element as well. This is indicated by a pointing arrow from the
dependent side to the independent side. This form of relationship can exist between classes
and inheritance.
24 Explain about Aggregation?
Aggregation gives a much more detail than association. In aggregation you can name it and it
can have same adornments. It may not be involved with more than two classes. It can have a
collection of classes but its classes are not dependent on the life cycle. It's contents are not
destroyed even when its classes are destroyed.
25 Association?
There are five types of association but importance is given to only two they are Bidirectional
and unidirectional. It represents a family of links. Binary associations are represented by two
ends and they are connected to class box. Higher order associations can have more than two
ends.
26 What is a UML package?
A package is a mechanism for grouping UML elements, usually classes, into groups.
Packages can be nested within other packages.
27 What is an activity diagram?
A variation of a statechart diagram that focuses on a flow of activity driven by internal
processing within an object rather than by events that are external to it. In an activity diagram
most (or all) states are action states, each of which represents the execution of an operation.
28 Define Sequence Diagram?
Sequence diagram shows an interaction between objects arranged in a time sequence.
Sequence diagram can be drawn at different levels of detail and also to meet different
purposes at several stages in the development life cycle.
29 Define event, state and transition?
Event: An event is occurrence of a stimulus that can trigger a state change and that is
relevant to the object.
State: A state reflects condition of an object at a given moment. The state of an object is
determined by values of its attributes and presence or absence of links to other objects.
Transition: The movement from one state to another state is called transition. A transition is
triggered by an event. A transition may start and end at the same state.
30 What are the Importance of Use Case Diagrams?
 To identify functions and how roles interact with them – The primary purpose of use
case diagrams.
 For a high-level view of the system – Especially useful when presenting to managers
or stakeholders. You can highlight the roles that interact with the system and the
functionality provided by the system without going deep into inner workings of the system.
 To identify internal and external factors – This might sound simple but in large
complex projects a system can be identified as an external role in another use case.

31 Which are Relationships in Use Case Diagrams?

 Association between an actor and a use case
 Generalization of an actor
 Extend relationship between two use cases
 Include relationship between two use cases
  Generalization of a use case

32 What is object oriented analysis and design?

 During object-oriented analysis there is an emphasis on finding and describing the
objects or concepts in the problem domain.
 During object-oriented design (or simply, object design) there is an emphasis on
defining software objects and how they collaborate to fulfil the requirements.

33 What is an object diagram?

Object Diagrams, sometimes referred as Instance diagrams are very similar to class
diagrams. As class diagrams they also show the relationship between objects but they use
real world examples. They are used to show how a system will look like at a given time.
Because there is data available in the objects they are often used to explain complex
relationships between objects.
34 What is interaction diagram? Mention the types of interaction diagram?
Interaction diagrams are diagrams that describe how groups of objects collaborate to get the
job done interaction diagrams capture the behaviour of the single use case, showing the
pattern of interaction among objects. There are two kinds of interaction models
• Sequence Diagram
• Collaboration Diagram
35 What is collaboration diagram?
Collaboration diagram represents a collaboration, which is a set of objects related in a
particular context, and interaction, which is a set of messages exchanged among the objects
with in collaboration to achieve a desired outcome.

36 Define UML?
Unified Modeling Language, a standard language for designing and documenting a system in
an object-oriented manner. It has nine diagrams which can be used in design document to
express design of software architecture.
37 Can you explain use case diagrams?
Use case diagram answers what system does from the user point of view. Use case answer
‘What will the system do?’. Use cases are mainly used in requirement document to depict
clarity regarding a system. There are three important parts in a use case scenario, actor and
use case.
Scenario: A scenario is a sequence of events which happen when a user interacts with the
system.
 Actor: Actor is the who of the system, in other words the end user.
Use Case: Use case is task or the goal performed by the end user. Below figure ‘Use Case’
shows a simple scenario with ‘Actor’ and a ‘Use Case’. Scenario represents an accountant
entering accounts data in the system. As use case’s represent action performed they are
normally represented by strong verbs. Actor’s are represented by simple stick man and use
case by oval shape
38 Can you explain primary and secondary actors?
Actors are further classified in to two types primary and secondary actors. Primary actors are
the users who are the active participants and they initiate the user case, while secondary
actors are those who only passively participate in the use case.
39 Can you explain ‘Extend’ and ‘Include’ in use cases?
Extend’ and ‘Include’ define relationships between use cases. Below figure ‘Extend and
Include’ shows how these two fundamentals are implemented in a project. The below use
case represents a system which is used to maintain customer. When a customer is added
successfully it should send an email to the admin saying that a new customer is added. Only
admin have rights to modify the customer. First lets define extend and include and then see
how the same fits in this use case scenario.
Include: Include relationship represents an invocation of one use case by the other. If you
think from the coding perspective its like one function been called by the other function.
Extend: This relationship signifies that the extending use case will work exactly like the
base use case only that some new steps will inserted in the extended use case.
40 Can you explain class diagrams?
Class diagram: Class is basically a prototype which helps us create objects. Class defines the
static structure of the project. A class represents family of an object. By using Class, we can
create uniform objects.
Basically there are three important sections.
Class name: This is the first section or top most section of the Class which represents the
name of the Class.
Attributes: This is the second section or the middle section of the class which represents the
properties of the system.
Methods: This section carries operation or method to act on the attributes.
41 How do we represent private, public and protected in class diagrams?
In order to represent visibility for properties and methods in class diagram we need to place
symbols next to each property and method as shown in figure ‘Private, Public and Protected’.
‘+’ indicates that it’s public properties/methods.
‘-‘ indicates private properties which means it cannot be accessed outside the class.
‘#’ indicate protected/friend properties. Protected properties can only be seen within the
component and not outside the component.

42 What does associations in a class diagram mean?

A single Class cannot represent the whole module in a project so we need one or more
classes to represent a module. For instance, a module named ‘customer detail’ cannot be
completed by the customer class alone, to complete the whole module we need customer
class, address class, phone class in short there is relationship between the classes. So by
grouping and relating between the classes we create module and these are termed as
Association. In order to associate them we need to draw the arrowed lines between the
classes
43 How do we represent an abstract class and interface UML?
Interface is represented by <<type>> in the class diagram. Below figure ‘Interface in action’
shows we have defined an interface ‘IContext’. Note the ‘<<type>>’ represents an interface.
If we want to show that the interface is used in a class we show the same with a line and a
simple circle
44 How do we achieve generalization and specialization?
By using inheritance.
45 What are the Process Workflows that evolve through these phases?
The Process Workflows that evolve through these phases are
Business Modeling,
Requirement gathering,
Analysis and Design,
Implementation,
Testing,
Deployment.
Supporting Workflows are Configuration, change management, and Project management.

How do we represent private, public and protected in class diagrams?

what does associations in a class diagram mean?
Can you explain aggregation and composition in class diagrams?
What are composite structure diagram and reflexive association in class diagrams?
Can you explain business entity and service class?
Can you explain System entity and service class?
Can you explain generalization and specialization?
How do we represent an abstract class and interface UML?
How do we achieve generalization and specialization?
Can you explain object diagrams in UML?
Can you explain sequence diagrams?