Object-Oriented Modeling Using UML (2). CS 3331 Fall 2009. Outline. Modeling dynamic behavior Statechart diagram Sequence diagram Modeling requirements Use case diagram. Modeling Dynamic Behavior. Statechart diagram Depicts the flow of control using states and transitions
Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.
Event [Condition] / Action
[valid] / connect
Transition to/from composite state
Transition from substate
Model at least the following operations:
Description: View the grades of a specific year and semester
Precondition: The student is already registered
1. The system carries out “Validate User”, e.g.,
for user “miner” with password “allAs”.
2. The system prompts for the year and semester.
4. The system displays the grades of the courses
taken in the given semester, i.e., Fall 2007.
3. The user enters the year and
semester, e.g., Fall 2007.
The student enters “All” for the year and semester, and the system displays
grades of all courses taken so far.
The “Validate User” use case fails; the system repeats the validation use case.Use Case Scenarios
Identify the main actors and the key use cases for an e-bookstore, and draw a use case diagram. Describe the use case scenario for the most important use case.
The core requirements of the e-bookstore are to allow its customers to browse and order books, music CDs, and computer software through the Internet. The main functionalities of the system are to provide information about the titles it carries to help customers make purchasing decisions; handle customer registration, order processing, and shipping; and support management of the system, such as adding, deleting, and updating titles and customer information.