Object-oriented software engineering
Object-oriented software engineering
Mainstream objects: an analysis and design approach for business
Mainstream objects: an analysis and design approach for business
Use cases combined with BOOCH/OMT/UML: process and products
Use cases combined with BOOCH/OMT/UML: process and products
UML toolkit
Visual modeling with Rational Rose and UML
Visual modeling with Rational Rose and UML
Building object applications that work: your step-by-step handbook for developing robust systems with object technology
The Unified Modeling Language user guide
The Unified Modeling Language user guide
Use case driven object modeling with UML: a practical approach
Use case driven object modeling with UML: a practical approach
Requirements analysis and system design: developing information systems with UML
Requirements analysis and system design: developing information systems with UML
Using UML: Software Engineering with Objects and Rules
Using UML: Software Engineering with Objects and Rules
Extension of UML Sequence Diagrams for Real-Time Systems
«UML» '98 Selected papers from the First International Workshop on The Unified Modeling Language «UML»'98: Beyond the Notation
Timing analysis of UML sequence diagrams
UML'99 Proceedings of the 2nd international conference on The unified modeling language: beyond the standard
An Experimental Evaluation of Documentation Methods and Reusability
ICSR '08 Proceedings of the 10th international conference on Software Reuse: High Confidence Software Reuse in Large Systems
A Multi-level Methodology for Developing UML Sequence Diagrams
ER '08 Proceedings of the 27th International Conference on Conceptual Modeling
Conceptual modeling based on transformation linguistic patterns
ER'05 Proceedings of the 24th international conference on Conceptual Modeling
| Hi-index | 0.01 |
The UML (Unified Modeling Language) has been widely accepted as a standard language for object-oriented analysis and design. Among the UML diagrams, one of the most difficult and time-consuming diagrams to develop is the object interaction diagram (OID), which is rendered as either a sequence diagram or a collaboration diagram. Our experience shows that developers have significant trouble in understanding and developing OIDs. In this paper, we present an effective ten-step heuristic for developing sequence diagrams and illustrate the technique with a case study. In this technique, we show a proper use of control objects and boundary objects when developing sequence diagrams. In our heuristic the relationships among multiple sequence diagrams in a single use case are elegantly represented using control objects. We found that developers effectively developed sequence diagrams using this heuristic method.