- This article was considered for deletion at Wikipedia on May 9 2015. This is a backup of Wikipedia:Robustness_Diagram. All of its AfDs can be found at Wikipedia:Special:PrefixIndex/Wikipedia:Articles_for_deletion/Robustness_Diagram, the first at Wikipedia:Wikipedia:Articles_for_deletion/Robustness_Diagram.
A robustness diagram is a simplified UML communication or collaboration diagram which uses the graphical symbols to do robusteness analysis. Robustness diagrams depict several types of concepts:
- Actors. This is the same concept as actors on a UML use case diagram.
- Boundary elements. These represent software elements such as screens, reports, HTML pages, or system interfaces that actors interact with. Also called interface elements.
- Control elements. These serve as the glue between boundary elements and entity elements, implementing the logic required to manage the various elements and their interactions. Also known as process elements or simply as controllers. It is important to understand that you may decide to implement controllers within your design as something other than objects - many controllers are simple enough to be implemented as a method of an entity or boundary class for example.
- Entity elements. These are entity types that are typically found in your conceptual model, such as Student and Seminar.
- Use cases (optional). Because use cases can invoke other use cases you need to be able to depict this on your robustness diagrams.