Skip to content
Object Oriented Analysis & Design with UML
  • Pages
    • Course Resources
      • How to Draw UML Diagrams
      • Agile Learning
      • Full Overview of UML
        • Overview of UML Software Architecture
        • Building Blocks of UML
        • Structural Modeling
        • UML - Architecture
        • UML - Basic Notations
        • UML - Standard Diagrams
        • UML - Class Diagram
        • UML - Object Diagrams
        • UML - Component Diagrams
        • UML - Deployment Diagrams
        • UML - Use Case Diagrams
        • UML - Interaction Diagrams
        • UML - Statechart Diagrams
        • UML - Activity Diagrams
        • UML - Quick Guide
        • Lucid Chart
      • Further Help with the Assignment
        • 000
        • 001
        • 002
        • 004
        • 003
        • 005
        • 006
        • 007
        • 008
        • 009
      • Design Patterns Reference
      • How to Sign up and use LinkedIn learning
      • Structure
        • Weekly Structure
          • 15
          • 9
          • 5
          • 3
          • 8
          • 7
          • 12
          • 1
          • 6
          • 14
          • 2
          • 10
          • 11
          • 13
          • 16- Assessment
          • 4
    • Contact Details
    • MODULE HANDBOOK
    • Assignment
    • Week 01- SDLC Methods: Principles of Object Orientated Thinking
    • Week 02- FURBS+ A.P.I.E Requirements Gathering Techniques
    • Week 03-Practical Application of UML Diagramming with Video Tutorials Part-01
      • Tutorial
    • Week 04-How to Create a Sequence, Activity, Class Diagram:
    • Week 05-Unified Software Development Process USDP
    • Week 06-Requirements & What is Agile
    • Week 07-User Stories in Agile
    • Week 08-User Mapping
    • Week 09 Intro to Design Patterns
    • Week 10 Model View Controller Design Patterns
    • Week 11 What is an API?
    • Week 12 Task Presentations
    • Week 13 Feedback from Presentations
    • Week 14 More Design Patterns Assignment Work
    • Week 15 Assignment Work
    • Week 16- In Class Exam 2 Hours
    • Full Overview of UML
      • Introduction to UML
      • Building Blocks of UML
      • UML - Architecture
      • Structural Modeling
      • UML - Standard Diagrams
      • UML - Basic Notations
      • UML - Class Diagram
      • UML - Object Diagrams
      • UML - Component Diagrams
      • UML - Deployment Diagrams
      • UML - Use Case Diagrams
      • UML - Interaction Diagrams
      • UML - Statechart Diagrams
      • UML - Activity Diagrams
      • UML - Quick Guide
    • Learn Agile & Scrum
      • 01-Discover the Waterfall and Iterative Approaches to Software Development
      • 02-Learn Agile Principles and Discover the Agile Manifesto
      • 03-Discover Three Different Types of Agile Project Management Frameworks
      • 04-Master the Fundamentals of Kanban
      • 05-Get Some Practice by Creating a Kanban Board Using Trello
      • 06-Principles of Agile Development Quiz
      • 07-Discover the Theory and Values Behind the Scrum Framework
      • 08-Identify the Members of the Scrum Team
      • 09-Learn the Events of the Scrum Framework
      • 10-Learn About Scrum Artifacts
      • 11-The Scrum Framework Quiz
      • 12-Write Effective User Stories
      • 13-Write Acceptance Tests
      • 14-Create a Definition of Done
      • 15-Get Started With Scrum in Your Organization
    • Assignment Brief 2022

UML - Architecture


Any real-world system is used by different users. The users can be developers, testers, business people, analysts, and many more. Hence, before designing a system, the architecture is made with different perspectives in mind. The most important part is to visualize the system from the perspective of different viewers. The better we understand the better we can build the system.
UML plays an important role in defining different perspectives of a system. These perspectives are −
Design
Implementation
Process
Deployment
The center is the Use Case view which connects all these four. A Use Case represents the functionality of the system. Hence, other perspectives are connected with use case.
Design of a system consists of classes, interfaces, and collaboration. UML provides class diagram, object diagram to support this.
Implementation defines the components assembled together to make a complete physical system. UML component diagram is used to support the implementation perspective.
Process defines the flow of the system. Hence, the same elements as used in Design are also used to support this perspective.
Deployment represents the physical nodes of the system that forms the hardware. UML deployment diagram is used to support this perspective.
It is very important to distinguish between the UML model. Different diagrams are used for different types of UML modeling. There are three important types of UML modeling.

 
Want to print your doc?
This is not the way.
Try clicking the ··· in the right corner or using a keyboard shortcut (
CtrlP
) instead.