The Cloze procedure and software comprehensibility measurement
IEEE Transactions on Software Engineering
The practical guide to structured systems design: 2nd edition
The practical guide to structured systems design: 2nd edition
A field study of the software design process for large systems
Communications of the ACM
Modern structured analysis
Object-oriented analysis
Document classification for software quality systems
ACM SIGSOFT Software Engineering Notes
How effective are software engineering methods?
Journal of Systems and Software
The effects of naming style and expertise on program comprehension
International Journal of Human-Computer Studies
ACM SIGPLAN Notices
A methodology for studying the psychological complexity of computer programs.
A methodology for studying the psychological complexity of computer programs.
ACM SIGPLAN Notices
Software psychology: Human factors in computer and information systems (Winthrop computer systems series)
An Introduction to Language
Assessing maintainability change over multiple software releases
Journal of Software Maintenance and Evolution: Research and Practice
A framework supporting the utilization of domain knowledge embedded in software
ER '07 Tutorials, posters, panels and industrial contributions at the 26th international conference on Conceptual modeling - Volume 83
Identifier length and limited programmer memory
Science of Computer Programming
Predicting software maintenance using fuzzy model
ACM SIGSOFT Software Engineering Notes
Software reusability assessment using soft computing techniques
ACM SIGSOFT Software Engineering Notes
Software quality evaluation through maintenance processes
ECS'10/ECCTD'10/ECCOM'10/ECCS'10 Proceedings of the European conference of systems, and European conference of circuits technology and devices, and European conference of communications, and European conference on Computer science
Hi-index | 0.00 |
Software developers and maintainers need to read and understand source programs and other kinds of software documents in their work. Understandability of software documents is thus important. This paper introduces a method for estimating the understandability of software documents. The method is based on a language theory according to which every software document is considered to contain a language of its own, which is a set of symbols. The understandability of documents written according to different documentation practices can be compared using the rules of the language theory. The method and the language theory are presented by using source programs with different naming styles as example documents. The method can, at least theoretically, be applied to any kind of document. It can also be used to explain the benefits of some well-known software design methods.