Design patterns: elements of reusable object-oriented software
Design patterns: elements of reusable object-oriented software
A cognitive framework for knowledge in informatics: the case of object-orientation
ITiCSE '99 Proceedings of the 4th annual SIGCSE/SIGCUE ITiCSE conference on Innovation and technology in computer science education
Encapsualtion and reuse as viewed by java students
Proceedings of the thirty-second SIGCSE technical symposium on Computer Science Education
Object-Oriented Analysis and Design with Applications (3rd Edition)
Object-Oriented Analysis and Design with Applications (3rd Edition)
Human Aspects of Software Engineering (Electrical and Computer Engineering Series)
Human Aspects of Software Engineering (Electrical and Computer Engineering Series)
Applying UML and Patterns: An Introduction to Object-Oriented Analysis and Design and Iterative Development (3rd Edition)
The quarks of object-oriented development
Communications of the ACM - Next-generation cyber forensics
An iterative methodology for teaching object oriented concepts
Informatics in education
How intuitive is object-oriented design?
Communications of the ACM - Web searching in a multilingual world
Agile architecture methodology: long term strategy interleaved with short term tactics
Companion to the 23rd ACM SIGPLAN conference on Object-oriented programming systems languages and applications
Consistency Checking for Component Reuse in Open Systems
ICSR '09 Proceedings of the 11th International Conference on Software Reuse: Formal Foundations of Reuse and Domain Engineering
| Hi-index | 0.00 |
The process of design construction and design review is notorious in its endless debates and discussions. Sometimes, these "gurus' style" debates are triggered by simple mistakes that could have been easily avoided. Precious time is lost, both because of the designer's lack of experience and the reviewer's overconfidence. If both sides were effectively prepared and armed with the same ammunition of knowledge, the "balance of terror" would reduce the will to argue and focus would be maintained. Reinforcing the abilities to face the intimidating guru's knowledge can be by formal encapsulation of that knowledge and systematic gurus' guidance to the design steps. This paper presents a methodology that captures the recommended selection of entities' relationships using UML notation. The UML arrow methodology is comprised of a checklist, which provides immediate yes/no feedback to simple guiding questions and a governing iterative process. The consolidated questions encompass best practice design methodologies, composed, edited and corroborated by the company's experienced designers. It contains a common process based on capturing the gurus' recommendations according to the company's specific needs. The methodology was evaluated in practitioners' workshops as well as practical design sessions, based on data received through questionnaires. The results obtained from 62 participants reveal that (1) usage of this methodology led to effective identification of inappropriate entities' relationships; (2) shortened the design review duration; (3) removed redundant technical remarks; (4) improved the preparation stages as well as brainstorming sessions, and (4) overall maintained a focused discussions regarding the problem.