By Priority. This is the default setting. The to-do items are organized into three hierarchies by priority: High, Medium and Low. The priority associated with the to-do items generated by a particular critic may be altered through the Critique > Browse Critics... menu (see Section 10.9.4, “ Browse Critics... ”).

By Decision. The to-do items are organized into 17 hierarchies by design issue: Uncategorized, Class Selection, Behavior, Naming, Storage, Inheritance, Containment, Planned Extensions, State Machines, Design Patterns, Relationships, Instantiation, Modularity, Expected Usage, Methods, Code Generation and Stereotypes. The details of the critics in each category are discussed in Section 10.9.2, “ Design Issues... ”.

By Goal. ArgoUML has a concept that critics may be grouped according to the user goals they affect. This presentation groups the to-do items into hierarchies by goal.

	Caution
	In the current release of ArgoUML there is only one goal, Unspecified and all to-do items will appear under this heading.

By Offender. The to-do items are organized into a hierarchy according to the model element that caused the problem. Todo items that were manually created with the "New ToDo item" button (i.e. not by a critic), are not listed here.

By Poster. The to-do items are organized into a hierarchy according to which critic generated the to-do item. The class name of the critic is listed instead of just its headline name since the former is guaranteed to be a unique name.

By Knowledge Type. ArgoUML has the concept that a critic reflects a deficiency in a category of knowledge. This presentation option groups the critics according to their knowledge category: Designer's, Correctness, Completeness, Consistency, Syntax, Semantics, Optimization, Presentational, Organizational, Experiencial and Tool. The former category (Designer's) contains the manually entered todo items.