Theoretical and practical complexity of modeling methods

Authors:
John Erickson;Keng Siau
Affiliations:
University of Nebraska at Omaha;University of Nebraska-Lincoln
Venue:
Communications of the ACM
Year:
2007

Citing 5
Cited 7

Information modeling and method engineering: a psychological perspective

Journal of Database Management - Special issue on information modeling methods
Will UML 2.0 be agile or awkward?

Communications of the ACM - Internet abuse in the workplace and Game engines in scientific research
Software Engineering Economics

Software Engineering Economics
How Do We Understand a System with (So) Many Diagrams? Cognitive Integration Processes in Diagrammatic Reasoning

Information Systems Research
Software Function, Source Lines of Code, and Development Effort Prediction: A Software Science Validation

IEEE Transactions on Software Engineering

Assessing the influence of import-coupling on OCL expression maintainability: A cognitive theory-based perspective

Information Sciences: an International Journal
Benefits of supplementing use case narratives with activity diagrams-An exploratory study

Journal of Systems and Software
Research Review: A Systematic Literature Review on the Quality of UML Models

Journal of Database Management
Toward a Unified Model of Information Systems Development Success

Journal of Database Management
Are forward designed or reverse-engineered UML diagrams more helpful for code maintenance?: a controlled experiment

Proceedings of the 17th International Conference on Evaluation and Assessment in Software Engineering
On the impact of UML analysis models on source-code comprehensibility and modifiability

ACM Transactions on Software Engineering and Methodology (TOSEM)
Unified modeling language: the teen years and growing pains

HCI International'13 Proceedings of the 15th international conference on Human Interface and the Management of Information: information and interaction design - Volume Part I

Quantified Score

Hi-index	48.22

Visualization

Abstract

Highlighting the importance of taking into account typical usage when estimating the complexity of a systems development method.