1) The document discusses various approaches to visualizing OCL constraints, including traditional AST visualization, vOCL, Eclipse QVTs visualization, constraint diagrams, and Visual OCL.
2) It analyzes examples of each approach using a sample OCL constraint and finds that constraint diagrams can represent constraints compactly but are only partially expressive. Eclipse QVTs visualization and traditional AST are more complete but more verbose.
3) The author concludes that while pictures can complement text for understanding constraints, text will generally be better for expressing complex OCL expressions and tooling support for visual editors is unlikely. Debugging aids like AST and QVTs visualizations can still be helpful.