Information & Technology Management Standards
Domain Class Diagram
UML class diagram is used to model the structural aspects of the system; i.e. classes and its attributes (fields) and operations (methods) and also the interrelationships (association, composition, aggregation and generalization) between the classes. Class diagrams are used for domain modeling as well as for detailed design modeling. This document describes the standards for domain modeling. Domain modeling is an inside-out approach, meaning the modeling starts with the identification of core classes in the system and then working from inside outward to see how the classes participate in the system. Domain model is a representation of real world conceptual classes, not of software components.
Domain Class Diagram has no specification or template explicitly for documentation purposes. However, documenting the Domain Class model is very important. Most UML tools provide in-built documentation capturing and printing capabilities for the Class diagram and its elements. Use this facility to sufficiently document the class diagram and its elements.
Template |
Contact |
||
| Domain Class Diagram has no specification or template | Senior Application Analyst | ||
Deliverable Reviewers
IMG Reviewers |
Other Typical Reviewers |
||
| Application Analyst | Client User | ||
| Technical Architect | ITMB Business Analyst | ||
| Database Administrator | Software Development Team | ||
| Data Architect | |||
Related Standards
| Domain Class Diagram Modeling Standards & Guidelines |
|
| Model Driven Development and Model Driven Architecture Issues |
|
| UML Diagram Interchange Issues |
NOTE: Acrobat Reader needed to view or print PDF versions.

