Explore topic-wise InterviewSolutions in .

• Advantages of USING UML breaks the COMPLEX system into discrete pieces that can be understood easily.
• HANDOVER the system to new team becomes EASIER.
• Complex system can be understood by the disparate DEVELOPERS who are working on different platforms.
• UML model is not a system or platform specific. It unifies all disparate developers under one roof.

We have nine types of diagram 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.

We have nine types of diagram 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.

• SDLC is Software Development Life Cycle.
• SDLC of a system INCLUDED processes like Use case driven, ARCHITECTURE centric, ITERATIVE and Incremental. This Life cycle is divided into phases.
• Phase is a time span between TWO milestones.
• The milestones are Inception, Elaboration, CONSTRUCTION, and Transition.
• Process Workflows that evolve through these phase are Business Modeling, Requirement gathering, Analysis and Design. Supporting Workflows are configuration, change management, and project management.

• Use Case view - Presents the REQUIREMENTS of a system.
• Design View - Capturing the VOCABULARY.
• Process View - MODELING the systems processes and threads.
• Implementation view - Addressing the physical implementation of the system.
• Deployment view - Model the components REQUIRED for deploying the system.

• MODEL is a simplification of reality.
• BLUEPRINT of the ACTUAL system.
• Specify the structural and behavior of the system.
• TEMPLATES for designing the system.
• Helps document the system.

SPECIFICATION of a COMMUNICATION.

Specification of a communication.

TAKES care STRUCTURAL and behavioral ASPECT of a software system.
Includes software usage, functionality, PERFORMANCE, reuse, economic and technology constraints.

Takes care structural and behavioral aspect of a software system.
Includes software usage, functionality, performance, reuse, economic and technology constraints.

• STRUCTURAL.
• BEHAVIORAL.
• ARCHITECTURAL.