UML Diagrams Zicomi Systems publishes some UML example diagrams online from the world famous UML dictionary. more...
Version 2.5 Released Zicomi Systems is delighted to announce that version 2.5 of Zicomi Mentor is released. With support for UML 2.0 and all thirteen UML diagrams more...
Zicomi Systems' Director speaks about the UML at Objects by Design - an informative interview more...
Partner Programme Zicom Systems is delighted to announce a new world wide partner programme, become a partner today. more...
OMG Member Zicom Systems is made a member of the OMG!
Boundary
A boundary is a stereotyped class that is located on the periphery of the entity being modeled. Most commonly the entity is an entire system but can also be a subsystem. The boundary class communicates with actors, who exist outside the system and control, entity and other boundary classes inside the system.
Explanation
A boundary is a stereotype class that is used within an analysis model. Boundary classes represent the outer edge of the system. They are the parts of the system, which the actors can communicate with. They are used to model user interfaces and "graphical controls". They do not themselves carry out the work of the request but pass on the request to the control and entity classes, which lie deeper in the system.
A class is related to a boundary because it is the "base" element for the boundary which is simply a stereotyped class. The boundary, which adds its own semantics, has all the underlying properties and behavior of the class.
ControlSibling, Used Together, Graphically Similar
A control is related to a boundary because along with the entity they form a set of three stereotyped classes that are defined as part of the "UML Profile for Software Development Processes". The set is typically used in analysis. The control class manages or coordinates the interaction of classes the services of which communicate with the boundary classes and through them with the actors.
An entity is related to a boundary because along with the control they form a set of three stereotyped classes that are defined as part of the "UML Profile for Software Development Processes". The set is typically used in analysis.