Class Diagram Example: GoF Design Patterns - Proxy


Proxy design pattern is one of the Gang of Four (GOF) design patterns. Proxy design pattern allows for object level access control by acting as a pass through entity or a placeholder object.

Use this Proxy pattern template to get started building your own class model. Click Use this Template to start.

What is Class Diagram?

A Class is a blueprint that is used to create Object. The Class defines what object can do. Class Diagram gives the static view of an application. Class diagrams are at the heart of UML. They are based on the principles of object orientation and can be implemented in various phases of a project. A class diagram describes the types of objects in the system and the different types of relationships that exist among them. UML Class Diagram gives an overview of a software system by displaying classes, attributes, operations, and their relationships. Class Diagram can also help to construct the code for the software application development.

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

Purpose of Class Diagram

Class diagrams is widely used model for visualizing, specifying, and documenting structural features at different levels of details in software development process and they can help to achieve many benefits for your team, for example:

  • Capture and define the structure of classes together with other related classifiers.
  • Establish relationships between classes and classifiers.
  • Elaborate the class structure of a model by using attributes, operations, interface and etc.
  • Illustrate the common classifier roles and responsibilities that define the behavior of the system.
  • Organize the implementation classes in a package.
  • Refine an inheritance hierarchy among classes and classifiers for better reuse.
  • Refine class diagram from use case diagram or sequence diagram and establish the traceability among them.

Keen to try VP Online?

No limitations, no obligations, no cancellation fees.

Start a Free Trial