# polygon

## A regular polygon is a polygon which is equiangular (all angles are equal in measure) and equilateral (all sides have the same length).

Note the appearance of model information (like 'concave') from other logical contexts. In most UML tools one has the ability to choose to display or not display such information, to better reflect the immediate context. Often one has to return to "earlier" diagrams to find out what information has been introduced later and hide the display of information from "later" contexts (source sentences), at one's discretion.

Note also the use of the SysML Real.

## An equilateral polygon is a polygon which has all sides of the same length.

Note that Circuit is placed outside the logical context provided by the source sentence, yet included in the diagram ! It is the boundary of the «wrapper» Component, not the diagram, which defines the logical context. Dr Darren says:

Often I am asked "Why not just use a diagram to provide a logical view without stealing ownership of elements in the diagram ?". This is one reason, to be able to show elements outside the logical context. There are many others, including the ability to nest contexts, as well as the ability to trace from «wrapper» Components using ComponentRealization.

## These segments are called its edges or sides, and the points where two edges meet are the polygon's vertices or corners.

Here one can navigate from a lower (nested) context back to it's higher parent context via an automatically generated InterfaceRealization. This approach works well when the source text is stable (i.e., the paragraph from which both the lower and higher context source sentences come is stable).

## In geometry a polygon .. is traditionally a plane figure that is bounded by a closed path or circuit, composed of a finite sequence of straight line segments (i.e., by a closed polygonal chain)

Logical wrapping contexts can be nested to reflect sentences (or phrases) from the same paragraph, providing convenient navigation points from a higher to lower contexts, however this technique should not be employed too often, as it leads to graphical clutter and can introduce undesired coupling.