Class Diagram Example: GoF Design Patterns - Bridge

Description:

Bridge design pattern is one of the Gang of Four (GOF) design patterns. Bridge design pattern defines an abstract object structure independently of the implementation object structure in order to limit coupling.

You can edit this Bridge design pattern template to build your class model. Just click Use this Template to start.

What is Class Diagram?

Class diagrams still represent by far the most important and widely used modeling technique of UML. A class diagram is a static model of a system which shows the structure of the software in terms of the constituent classes and how each class is related to other classes. A class diagram gives a static view of the system. As opposed to a dynamic view, which describes what the software does when it runs, a class diagram provides a static view, which describes the classes that make up the software. Class Diagrams can also be used to generate source code for system implementation.

Guidelines for creating Class Diagram?

  1. Identify classes
    • a. From domain analysis such as textual analysis
    • b. From CRC cards
    • c. From use case description
    • d. From sequence diagram or use case scenarios
  2. Give analysis a name and a brief description which could be done through terms and glossary
  3. Structure classes in the right places of the diagram and related them with simple relationships
  4. As the development move forward, detail the class with attributes and operations, this often done in conjunction with use case and sequence diagrams
  5. Refine the class diagram with inheritance for future reuse
  6. Elaborate the details which is helpful for implementation such as accessibility, rules, constraints and etc.
  7. Put related classes into packages to form your software architecture

When to use Class Diagram?

As a sketch:

  • Perform visual modeling rather than lengthy textual description
  • Casually use for illustrate initially ideas develop without the need of upfront requirement documentation
  • Instant revise from code to class diagram to pinpoint a specific problem
  • Used it to visual model to get rough selective ideas just in time whenever needed

As a blueprint:

  • a complete design to be implemented
  • typically done with a proper UML modeling tools

As code engineering:

  • Perform model to code forward engineering
  • Perform code to model reverse engineering
  • Keep code and model in sync by performing round-trip engineering

As data engineering:

  • Design data modeling based on detailed class diagram
  • Reverse class or object wrapper base on database
  • Use database framework such as Hibernate ORM Framework

As Web API generation

  • Generate web API based on Class Diagram such as SWAGGER

Keen to try VP Online?

No limitations, no obligations, no cancellation fees.


Start a Free Trial