UML Diagrams CSE 403 Think of it as A more concise and accurate - - PowerPoint PPT Presentation

uml diagrams
SMART_READER_LITE
LIVE PREVIEW

UML Diagrams CSE 403 Think of it as A more concise and accurate - - PowerPoint PPT Presentation

UML Diagrams CSE 403 Think of it as A more concise and accurate documentation of software architecture than English A way to guide discussion to reveal assumptions and miscommunications A compact and quick way to take notes in


slide-1
SLIDE 1

UML Diagrams

CSE 403

slide-2
SLIDE 2

Think of it as …

  • A more concise and accurate documentation
  • f software architecture than English
  • A way to guide discussion to reveal

assumptions and miscommunications

  • A compact and quick way to take notes in

meetings

slide-3
SLIDE 3
  • A way to verify that a system is capable of

meeting its requirements

  • An intuitive way to identify a system’s

weaknesses

  • A way to quickly onboard new team

members

  • A way to remind yourself of decisions you

made months ago

Think of it as … (Cont.)

slide-4
SLIDE 4

Class Diagrams

slide-5
SLIDE 5

A Brief Review

Describes

  • The system’s classes
  • Their attributes
  • Their operations
  • Their relationships with each other
slide-6
SLIDE 6

Representing a class

slide-7
SLIDE 7

A two-way connection between peers

General Association

slide-8
SLIDE 8

One or more classes are generally treated as members of some larger whole, but may belong to multiple objects during their lifetimes

Aggregation

slide-9
SLIDE 9

One or more classes are always treated as members of some larger whole, and are destroyed with the whole

Composition

slide-10
SLIDE 10

Dependency

Changing the interface of one class may change the implementation or interface of another

slide-11
SLIDE 11

http://msdn.microsoft.com/en-us/library/dd409437.aspx

slide-12
SLIDE 12

Sequence Diagrams

slide-13
SLIDE 13

A Brief Review

  • Describes the sequence of messages

passed between instances of components

  • ver time
  • Time flows down the diagram
  • Shows how control flow moves from one

component to another

slide-14
SLIDE 14

http://msdn.microsoft.com/en-us/library/dd409377.aspx

slide-15
SLIDE 15

Design the models (not any views or controllers) for course registration software based on the UW’s system. Create:

  • A sequence diagram for the use case “user attempts to

register for one or more courses by entering their SLNs”.

  • A class diagram.

The system should let a student register if and only if they have taken the prerequisite courses and have no scheduling conflicts.

Design Exercise