Practical guidelines for the readability of IT-architecture diagrams

ACM SIGDOC Annual International Conference on Computer Documentation, Proceedings

Volumn , Issue , 2002, Pages 90-99

  Koning, Henk ^a   Dormann, Claire ^a   Van Vliet, Hans ^a  

^a VU UNIVERSITY AMSTERDAM   (Netherlands)

Author keywords

Architecture; Color; Diagrams; Form; Graphics; Guidelines; Hierarchy; Layout; Readability; Size; Text; Visualization; Width

Indexed keywords

COMPUTER GRAPHICS; HUMAN ENGINEERING; INFORMATION TECHNOLOGY; PROGRAM DOCUMENTATION;

SOFTWARE ARCHITECTURE;

COMPUTER AIDED SOFTWARE ENGINEERING;

EID: 0038303643     PISSN: None     EISSN: None     Source Type: Conference Proceeding    
DOI: 10.1145/584955.584969     Document Type: Conference Paper

References (28)

1. J. Bertin, Semiology of graphics, The University of Wisconsin Press, 1983.
2. Bernhard. H. Boar, Constructing Blueprints for Enterprise IT Architectures, Wiley, 1998
3. Jan Borchers, Oliver Deussen, Arnold Klingert, Clemens Knörzer, Layout Rules for Graphical Web Documents, Computers & Graphics, Vol. 20, No. 3, 1996
4. Britton et al, Evaluating the intelligibility of diagrammatic languages used in the specification of software, First International Conference, Diagrams2000, Edingburgh, 2000
5. rd International Conference on Software Engineering, Toronto, ACM, 2001.
6. Hideaki Chijiiwa, Color Harmony, Rockport Publishers, 1987
7. Henry Dreyfuss, Symbol Sourcebook: An Authoritative Guide to International Graphic Symbols, McGraw-Hill, 1972
8. M. Fowler, UML Distilled: A Brief Guide to the Standard Object Modeling Language, Addison-Wesley, Reading, Massachusetts, 1999.
9. Gretchen Hargis, Readability and computer documentation, ACM Journal of Computer Documentation, August 2000, Vol.24, No. 3.
10. Guido van der Harst, Rob Maijers, Effectief GUI-ontwerp, Academic Service, 1999 (in Dutch)
11. C. Hofmeister, R. Nord and D. Soni, Applied Software Architecture, Addison-Wesley, Reading, Massachusetts, 1999.
12. W. Horton, Illustrating Computer Documentation, Wiley, 1991.
13. IEEE, IEEE recommended practice for architecture description, IEEE Standard 1471, 2000.
14. Henk Koning, Guidelines concerning readability of IT-architecture diagrams, to be found on http://www.cs.vu.nl/̃henk, 2001
15. Henk Koning, Guidelines readability: example diagrams from internet, to bee found on http://www.cs.vu.nl/̃henk, 2001
16. P.B. Krachten, The 4+1 view model of architecture, IEEE Software 12 (6) (1995) 42-50.
17. Jill. H. Larkin, Herbert A. Simon, Why a Diagram is (Sometimes) Worth Ten Thousand Words, Cognitive Science 11, 65-99 (1987)
18. Rudolf Modley, William R. Myers, Diana G. Comer, Handbook of Pictorial Symbols: 3250 Examples from International Sources, Dover Pubns; 1977
19. James Martin, Carme McClure, Diagramming Techniques for Analysts and Programmers, Prentice-Hall, 1985
20. Narayanan, Diagrammatic communication: a taxonomic overview, Technical Report CSE97-06, December 2, 1997
21. D. A. Norman, The Psychology of Every Day Things, Basic Books, 1988.
22. Software Engineering Institute, Workshop on Software Architecture Representation, 16-17 January 2001, http://www.sei.cmu.edu/publications/documents/01.reports/01sr010.html
23. Dennis Smith, Bill Thomas, Scott Tilley, Documentation for software engineers: what is needed to aid system understanding, workshop at SIGDOC 2001, Annual ACM Conference on Systems Documentation, http://doi.acm.org/10.1145/501516.501570
24. th International Conference on Software Engineering, ACM, 1995, pp 196-207.
25. Robert Spence, Information Visualization, ACM, Addison-Wesley, 2001
26. H. van Vliet, Software Engineering: Principles and Practice, John Wiley & Sons, Chichester, 2000.
27. Colin Ware, Information Visualization, Morgan Kaufmann Publishers, 2000
28. Martijn van Welie, Task-based User Interface Design, Master Thesis, SIKS Dissertation Series No. 2001-6, electronically available at http://www.cs.vu.nl/̃martijn/gta/docs/Welie-PhD-thesis.pdf