This is because if you're not using business objects, most of your application logic resides inside methods of user interface objects or in functions and procedures?and there really isn't much messaging that occurs between objects. Why use Sequence Diagrams?Īs mentioned in the previous article on class diagrams, unless you are using business objects in your applications, you won't have much need for sequence diagrams. While the collaboration diagram's main focus is to show how objects are associated with each other, sequence diagrams show the time ordering of messages between objects. Sequence diagrams are closely related to collaboration diagrams (discussed in the next article in this series).
#Sequence diagram for log in software#
They are most often used in the construction phase of software projects and are especially useful when analyzing the process-intensive portions of your application. This third article in the series covers one of the most interesting diagrams in the UML - the sequence diagram. You often create a sequence diagram to model the logic of a use case. Sequence diagrams can help you comprehend and solve difficult issues in the process-intensive portions of your applications. It helps you document and understand the dynamic aspects of your software system - specifically the sequence of messages that are sent and received between objects. The Sequence Diagram is one of the most interesting and useful diagrams in the Unified Modeling Language (UML).
0 kommentar(er)
