UML interview questions

  1. What are the messages and the dynamic diagrams?
  2. What are the elements which are utilized in the state chart diagram?
  3. What are the different parts of a deployment diagram?
  4. Name some of the roles that are played by the packages, modules and wrappers?
  5. What do you understand by relationships in UML?
  6. Tell us the difference between activity and sequence diagrams?
  7. What are the elements which are used in activity diagrams?
  8. Can you name the different elements with the collaboration diagram?
  9. What is known as static diagrams?
  10. What do you understand by SDLC and name its processes?
  11. Can you give us a brief defining the architecture?
  12. What are the modelling diagrams that are most commonly used?
  13. Can you tell us a few advantages of creating a model?
  14. What are the different views that have to be considered before the buildup of an object oriented software system?
UML interview questions

UML (Unified Modeling Language) has been spreading its roots among the designing and visualization part. This field has a lot for the potential seekers and the individuals interested in the visualization in software engineering. This perfect set of UML interview questions contains their most accurate answers that will help you with the subject. These questions will guide you thoroughly so that you may get a modelling language platform in the specific field of software engineering.

We are presenting the most beneficial UML interview questions that will provide you with enough direction towards your interview. UML generally includes a perfect set of the graphical notation in the technique which is used to create the visuals of software-intensive systems and their objects

Download UML interview questions PDF

Messages are the specifications for any sort of communication. When a message is passed then the estimated action is expected which is basically a statement for the execution that held prior. Dynamic diagrams are also called the behavioral diagrams. The names of few of the dynamic diagrams are:

  • Use case diagram
  • Sequence diagram
  • Collaboration diagram
  • Activity diagram
  • Statechart diagram.

The elements which are in the state chart diagram are:

  • Initial state
  • State
  • Transition
  • Event and action
  • Final state

The deployment program consists of the –

  • Nodes
  • Components
  • Dependencies
  • Links
  • Modules are known as component diagrams which include the physical computers as a node and display the different packages inside it is a component.
  • Packages are used to organize the different classes, all at one place.
  • Wrappers are collectively used to constitute the multiple packages which include the content from it.

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.

Sequence diagrams basically show the way of processing or the execution of the process with any of the sequence. Sequence diagrams are entirely focused on the representative interaction among different objects.

On the other hand, activity diagrams actually detect the following phases-

  • Depicts the operational workflow in a system.
  • Shows the actions and sequences for a number of objects.

The significant elements which are used in activity diagrams are:

  • Activities - it indicates the action which has to be performed or had been performed in the system.
  • Transitions - they are represented by an arrow and used to indicate the floor that is occurring among the elements in the diagram.
  • Decision points - in the system the logical branching is highlighted by the decision points.
  • States - these are indicated in order to mention the milestones for the processing of activity diagrams and is shown by a rounded rectangle.

There are basically three types of elements of a collaborative diagram:

  • Object - the interaction in a system always takes place between two objects. An object is always depicted by a rectangle with the name of the object. This is preceded by a colon and an underline.
  • Relation - it is also known as an association which is always among the objects which are linked with the connection in a system. They are depicted by placing the qualifiers on both ends.
  • Message - An instance of communication from one point to the other significant point or destination is a message. It always depicts the interaction that is offering between the objects in a system. The sequence of this interaction is directly shown by the number.

Static diagrams are also known as the structural diagrams. They are known by the following names-

  • Class diagram
  • Object diagram
  • Component diagram
  • Deployment diagram.

SDLC stands for the software development life cycle and it is an amalgamation of the number of processes. This entire life cycle is divided into several phases. The major of them are:

  • Use case driven
  • Architecture-centric
  • Iterative
  • Incremental

Architecture means with the structural and behavioral aspects of the entire software system. It significantly monitors over the software usage and the functionality evolving around it. With architecture, the entire performance is economical and all the technical constants can be well managed.

The most frequently used modeling diagrams are 9 in number. These are as:

  • Use case diagram
  • Class diagram
  • Object diagram
  • Sequence diagram
  • State chart diagram
  • Collaboration diagram
  • Activity diagram
  • Component diagram
  • Deployment diagram

There are a number of advantages for creating any model like:

  • They help to document the entire system.
  • They help to make templates for the construction in the system.
  • They help in the visualization of the system.
  • The structural dimensions of a system can be specified.
  • Modeling is entirely accepted by the engineering technique.

Before the actual building up of an object-oriented software system, there are generally 5 views-

  • Use case view - it exposes the requirements of any system.
  • Design view - it captures the vocabulary of the system.
  • Process view - this view models the distribution across the system.
  • Implementation view - this view addresses the implementation of the system.
  • Deployment view - this view focuses over the components which are required for the deployment of the system.

There are basically three types of modeling used

  • Architectural modeling
  • Behavioral modeling
  • Structural Modeling.

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.