Please note : This help page is not for the latest version of Enterprise Architect. The latest help can be found here.

Custom Toolbox

The Custom Toolbox contains extended UML elements that can be of use in modeling or designing your system in a Custom diagram.

Custom Toolbox pages

Image	Detail	See also
	A Package is a namespace as well as an element that can be contained in other package's namespaces. A Requirement is a custom element used to capture requirements external to standard UML elements; a Requirement expresses required system behavior that can cross several Use Cases. You can connect Requirements to other elements using the Realize connector to express the implementation of a requirement and hence the traceability from user requirements to what is being built. An Issue element is a structured comment that contains information about defects and issues relating to the system/model; affected elements are connected by Trace connectors. A Change element is a structured comment that contains information about changes requested to the system/model; affected elements are connected by Trace connectors. A Screen provides a stereotyped Class element that displays a GUI type screen; this can be used to express application GUI elements and flows between them. A UI Control likewise can be used to express GUI controls. A Test Case element defines what must be set up in order to test a particular feature; it enables you to define a set of tests once for a number of elements, and provides greater visibility for tests. An Entity is a stereotyped element that represents any general thing not captured by the element or Class type elements (for example a trading partner); use of this element is deprecated - it was originally intended to take the role now occupied by a Table element.	Package Requirements Traceability Issues (Defects) Trace Changes and Issues Screen UI Control Test Case Working on Test Records Table

Image

Detail

See also

CustomBar

A Package is a namespace as well as an element that can be contained in other package's namespaces.

A Requirement is a custom element used to capture requirements external to standard UML elements; a Requirement expresses required system behavior that can cross several Use Cases.

You can connect Requirements to other elements using the Realize connector to express the implementation of a requirement and hence the traceability from user requirements to what is being built.

An Issue element is a structured comment that contains information about defects and issues relating to the system/model; affected elements are connected by Trace connectors.

A Change element is a structured comment that contains information about changes requested to the system/model; affected elements are connected by Trace connectors.

A Screen provides a stereotyped Class element that displays a GUI type screen; this can be used to express application GUI elements and flows between them.

A UI Control likewise can be used to express GUI controls.

A Test Case element defines what must be set up in order to test a particular feature; it enables you to define a set of tests once for a number of elements, and provides greater visibility for tests.

An Entity is a stereotyped element that represents any general thing not captured by the element or Class type elements (for example a trading partner); use of this element is deprecated - it was originally intended to take the role now occupied by a Table element.

Working on Test Records

Table

Notes

•	To add an element to the currently-open diagram, click on the appropriate icon and drag it into position on the diagram; set an element name and other properties as prompted