Place Reactive System Actors on the Right-Most Side of Your Diagram.Place Human and Organization Actors On the Left-Most Side of Your Diagram.Include a Prose Description of the Logic.An Actor Can Have The Same Name as a Class.Name Classes Consistently With Your Class Diagrams.Name Actors Consistently With Your Use Case Diagrams.Strive for Left-To-Right Ordering Of Messages.Give you a feel for which classes in your application are going to be complex, which in turn is an indication that you may need to draw state chart diagrams for those classes.In fact some CASE tools even enable you to simulate this aspect of your software. By looking at what messages are being sent to an object, and by looking at roughly how long it takes to run the invoked method, you quickly get an understanding of where you need to change your design to distribute the load within your system. To detect bottlenecks within an object-oriented design.Explore your design because they provide a way for you to visually step through invocation of the operations defined by your classes.The logic of a usage scenario may be part of a use case, perhaps an alternate course one entire pass through a use case, such as the logic described by the basic course of action or a portion of the basic course of action plus one or more alternate scenarios or a pass through the logic contained in several use cases, for example a student enrolls in the university then immediately enrolls in three seminars. A usage scenario is exactly what its name indicates – the description of a potential way that your system is used. Validate and flesh out the logic of a usage scenario.UML sequence diagrams are typically used to: UML Sequence diagrams are a dynamic modeling technique, as are collaboration diagrams and activity diagrams.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |