Design patterns: elements of reusable object-oriented software
Design patterns: elements of reusable object-oriented software
Visual explanations: images and quantities, evidence and narrative
Visual explanations: images and quantities, evidence and narrative
Program understanding behavior during debugging of large scale software
ESP '97 Papers presented at the seventh workshop on Empirical studies of programmers
AntiPatterns: refactoring software, architectures, and projects in crisis
AntiPatterns: refactoring software, architectures, and projects in crisis
IEEE Transactions on Software Engineering
Reverse Engineering and Design Recovery: A Taxonomy
IEEE Software
Nice class diagrams admit good design?
Proceedings of the 2003 ACM symposium on Software visualization
A new approach for visualizing UML class diagrams
Proceedings of the 2003 ACM symposium on Software visualization
Pattern Visualization for Software Comprehension
IWPC '98 Proceedings of the 6th International Workshop on Program Comprehension
Towards a documentation maturity model
Proceedings of the 21st annual international conference on Documentation
Proceedings of the 21st annual international conference on Documentation
Precise Modeling of Design Patterns in UML
Proceedings of the 26th International Conference on Software Engineering
An integrated approach to program redocumentation
An integrated approach to program redocumentation
The Elements of UML(TM) 2.0 Style
The Elements of UML(TM) 2.0 Style
On Evaluating the Layout of UML Class Diagrams for Program Comprehension
IWPC '05 Proceedings of the 13th International Workshop on Program Comprehension
Case Studies of Visual Language Based Design Patterns Recovery
CSMR '06 Proceedings of the Conference on Software Maintenance and Reengineering
Documenting software systems with views VI: lessons learned from 15 years of research & practice
Proceedings of the 27th ACM international conference on Design of communication
Empirical Software Engineering
Hi-index | 0.00 |
Cognitive science research indicates that a system is more readily understood when it is presented at progressive levels of decomposition, exposing increasing amounts of detail. One logical level of detail would present a system in terms of its implemented design patterns. However, to date, no entirely satisfactory method of documentation has been devised for explicating a software system as a set of design patterns. This paper discusses the challenges inherent in visualizing a software system as a set of design patterns, reviews the progress of another current effort, and describes a UML-compliant enhanced class-participation diagram as one possible solution.