QUIZ 2 solutions 1 - Consider a file system with

Transcript:QUIZ 2 solutions 1 - Consider a file system with:
QUIZ 2 solutions 1 - Consider a file system with a graphical user interface, such as Macintosh’s Finder, Microsoft’sWindows Explorer, or Linux’s KDE. The following objects were identified from a use case describing how to copy a file from a floppy disk to a hard disk: File, Icon, TrashCan, Folder, Disk, Pointer. Specify which are entity objects, which are boundary objects, and which are control objects. Entity objects: File, Folder, Disk, TrashCan (if regarded as folder) Boundary objects: Icon, Pointer, TrashCan (if regarded as icon) Control objects: none in this example. 2 - From the sequence diagram below, draw the corresponding class diagram for 2BWatch. Hint: Start with the participating objects in the sequence diagram. Warning 1: Actor is not an object! Warning 2: You need to list attributes for some of the objects. SimpleWatch is an instance of 2BWatch LCDdisplay is an instance of 2BWatchDisplay Time is an instance of 2BWatchTime Boundary object: 2BWatchButtons or 2BWatchInput (ok if you left it as attributes) Messages: pressButton1(), pressButton2(), pressButton1and2()  2BWatchInput blinkHours(), blinkMinutes(), stopBlinking(), refresh()  2BWatchDisplay possible attribute: digitBlanking incrementMinutes(), commitNewTime() possible attribute: time 2BWatch 2BWatchInput pressButton1() pressButton2() pressButton1and2() 2BWatchDisplay 2BWatchTime blinkHours() blinkMinutes() stopBlinking() refresh() digitBlanking incrementMinutes() commitNewTime() time Midterm: Chapters 1-5 You should know… Use case diagrams Describe the functional behavior of the system as seen by the user Used during requirements elicitation Class diagrams Describe the static structure of the system: Objects, attributes, associations Sequence diagrams Describe the dynamic behavior between objects of the system State diagrams Describe the dynamic behavior of an individual object Activity diagrams Describe the dynamic behavior of a system, in particular the workflow. UML Core Conventions All UML Diagrams are composed of graphs of nodes and edges Nodes are entities and drawn as rectangles or ovals Rectangles denote classes or instances Ovals denote functions Names of Classes are not underlined SimpleWatch Firefighter Names of Instances are underlined myWatch:SimpleWatch Joe:Firefighter An edge between two nodes denotes a relationship between the corresponding entities Use case diagrams Use case diagrams represent the functionality of the system from user’s point of view Actor. Use Case System boundary Classifier Use case diagrams Use case diagrams represent external behavior Uses should be verbs Actor-use relations are marked with an edge: Which actor is related to which use (what does an actor do?) Relationships between uses: Extends Relationship To represent seldom invoked use cases or exceptional functionality Includes Relationship To