UML distilled (2nd ed.): a brief guide to the standard object modeling language
UML distilled (2nd ed.): a brief guide to the standard object modeling language
The Object-Oriented Development Process: Developing and Managing a Robust Process for Object-Oriented Development
Uml and the Unified Process: Practical Object-Oriented Analysis and Design
Uml and the Unified Process: Practical Object-Oriented Analysis and Design
Using UML: Software Engineering with Objects and Rules
Using UML: Software Engineering with Objects and Rules
Developing Sequence Diagrams in UML
ER '01 Proceedings of the 20th International Conference on Conceptual Modeling: Conceptual Modeling
Translating Use Cases to Sequence Diagrams
ASE '00 Proceedings of the 15th IEEE international conference on Automated software engineering
Object-Oriented Software Engineering: A Use Case Driven Approach
Object-Oriented Software Engineering: A Use Case Driven Approach
Finding Reusable UML Sequence Diagrams Automatically
IEEE Software
Sequence diagram presentation in technical documentation
Proceedings of the 22nd annual international conference on Design of communication: The engineering of quality documentation
Applying UML and Patterns: An Introduction to Object-Oriented Analysis and Design and Iterative Development (3rd Edition)
Object naming analysis for reverse-engineered sequence diagrams
Proceedings of the 27th international conference on Software engineering
Detecting and resolving semantic pathologies in UML sequence diagrams
Proceedings of the 10th European software engineering conference held jointly with 13th ACM SIGSOFT international symposium on Foundations of software engineering
PPPJ '06 Proceedings of the 4th international symposium on Principles and practice of programming in Java
UML 2 for Dummies
Hi-index | 0.00 |
Although the importance of UML Sequence Diagrams is well recognized by the object-oriented community, they remain a very difficult UML artifact to develop. In this paper we present a multi-level methodology to develop UML Sequence Diagrams. Our methodology is significant in three aspects. First, it provides a multilevel procedure to facilitate ease of the development process. Second, it makes use of certain patterns to ensure the validity of SQDs. Third, it uses consistency checks with corresponding use-case and class diagrams. Throughout the steps of the method we present rules and patterns demonstrating correct and incorrect diagramming of common situations through examples. The purpose of this study is to serve as a reference guide for novice sequence diagram modelers. This methodology is particularly useful for novice practitioners who face challenges in learning the process of SQD development.