Before we start generating code, lets first check if our model is as well-formed as it should be. There are certain design rules for software that are generally acknowledged by developers. The implementation of these kinds of rules into Poseidon for UML is in fact one of its finest features. This feature of cognitive support, which acts like a built in auditor, is called 'critique'.
When activated in the critiques menu, the critiques are constantly analyzing and criticizing your design. The Critiques pane in the bottom left corner of the working area contains three priority nodes in the 'by Priority' view.
Available Views in the Critiques Tab
by Decision Type - The type of action to be taken determines the category of the critique. The available categories are:
Uncategorized, Behavior, Class Selection, Naming, Storage, Inheritance, Containment, Planned Extensions, State Machines, Design Patterns, Relationships, Instantiation, Modularity, Expected Usage, Methods, Code Generation, and Stereotypes
by Diagrams - Critiques are arranged according to the diagram in which they appear
by Knowledge Type - Critiques are listed according to type. The available types are:
Correctness, Syntax, Presentation, and Completeness
by Offenders - Lists design elements of the current model and the critiques associated with them
by Posters - Critiques are arranged according to the critic who reported the problem
by Priority - Critiques are categorized in a priority of high, medium, or low
Broadening and improving this feature is part of each development cycle of Poseidon.