Object-oriented software engineering
Object-oriented software engineering
Experimentation in software engineering: an introduction
Experimentation in software engineering: an introduction
Evaluating Impact Analysis – A Case Study
Empirical Software Engineering
Replicating the CREWS Use Case Authoring Guidelines Experiment
Empirical Software Engineering
IFM '02 Proceedings of the Third International Conference on Integrated Formal Methods
Software factories: assembling applications with patterns, models, frameworks and tools
OOPSLA '03 Companion of the 18th annual ACM SIGPLAN conference on Object-oriented programming, systems, languages, and applications
Automotive software engineering: an emerging application domain for software engineering
Languages for system specification
An empirical comparison of the dynamic modeling in OML and UML
Journal of Systems and Software
Requirements Abstraction Model
Requirements Engineering
ECBS '06 Proceedings of the 13th Annual IEEE International Symposium and Workshop on Engineering of Computer Based Systems
On evaluating the layout of UML diagrams for program comprehension
Software Quality Control
Journal of Systems and Software - Special issue: Quality software
The Impact of UML Documentation on Software Maintenance: An Experimental Evaluation
IEEE Transactions on Software Engineering
Model-driven Development of Complex Software: A Research Roadmap
FOSE '07 2007 Future of Software Engineering
Interactive Views to Improve the Comprehension of UML Models - An Experimental Validation
ICPC '07 Proceedings of the 15th IEEE International Conference on Program Comprehension
Improving the quality of use case descriptions: empirical assessment of writing guidelines
Software Quality Control
Industry evaluation of the Requirements Abstraction Model
Requirements Engineering
An Empirical Investigation on Dynamic Modeling in Requirements Engineering
MoDELS '08 Proceedings of the 11th international conference on Model Driven Engineering Languages and Systems
Data Model Comprehension: An Empirical Comparison of ER and UML Class Diagrams
ICPC '08 Proceedings of the 2008 The 16th IEEE International Conference on Program Comprehension
Information flow between requirement artifacts: results of an empirical study
REFSQ'07 Proceedings of the 13th international working conference on Requirements engineering: foundation for software quality
Imperfect requirements in software development
REFSQ'07 Proceedings of the 13th international working conference on Requirements engineering: foundation for software quality
Impact of MDE approaches on the maintainability of web applications: an experimental evaluation
ER'11 Proceedings of the 30th international conference on Conceptual modeling
Hi-index | 0.00 |
Objective: Graphical requirements representation is often considered needed to advance model-driven development. Dedicated modelling languages include formalisms for graphically representing requirements, and together with new methods for structuring requirements, graphical modelling promises improvements such as more efficient change management. This paper examines whether the use of a graphical notation of a requirements affects the task of assessing the impact of a proposed change to a requirements specification. Method: The efficiency of using a graphical requirements representation was examined through an experiment – using 18 student subjects. Time, perceived confidence and accuracy were measured as dependent variables. Result: The results showed that using a graphical representation decreased the time required and increased the perceived confidence, but the accuracy decreased. However, the statistical analysis of the results showed that only the difference in time was significant. Furthermore, there was a large difference in variance within the dependent variables between the groups.