Docstoc

details of UML

Document Sample
details of UML Powered By Docstoc
					       UML and WSDL
for JISC e-Learning Projects
        UML Details

        Richard Hopkins
         rph@nesc.ac.uk
   NeSC Training Team Member
                              Goals
Goals –
 To understand sufficient details of UML to be
 able to use it as documentation for
      user requirement
      System (service) definition
 To have an appreciation of other parts of
 UML




  JISC UML/WSDL – UML – some details, 9th Nov. 2004   2
                        Overview
Overview –diagram types
 Use Case –                                           more detail
 Class -                                              more detail
 Collaboration –                                      new
 Object –                                             new
 Sequence –                                           more detail
 State –                                              new
 Appreciation only-                                   new
        Activity
        Packages
        Deployment
 Summary
 Exercise

  JISC UML/WSDL – UML – some details, 9th Nov. 2004            3
                          Warning
Exactly what is and what is not UML?
 Difficult question
 No Full implementation to test a question
 Different Author give conflicting views
 The Formal Definition is obscure




  JISC UML/WSDL – UML – some details, 9th Nov. 2004   4
                Simple Use Cases

                     Return Copy


BookBorrower
                     Notify lost
                     Copy




  Use case diagram showing our first
  attempt at two of the functionalities
  Further consideration leads to -



      JISC UML/WSDL – UML – some details, 9th Nov. 2004   5
             Use Case Relationships
                                                                                  show clerk –
                                        Return Copy
                                                                                  sometimes involved,
                                                                                  sometimes not
Book                                                                     Clerk    system might record
Returner                                   <<extend>>                             which clerk –
                                                                                  affects class diag.
               Notify lost
                                                  Return Overdue
               Copy                   <<include>> Copy                            <<extend>>
                                                                                  – a variation of
                 <<include>>
                                                                                  the indicated base
                                    Pay fine                                      case
                                                   <<extend>>    Defer fine

 Note – Participant
 Inheritance                                                                        <<include>>
                                                Pay fine by                         – allows common
 BookReturner & CLerk                           credit card                         sub-structure to
 implicitly involved in                                                             be factored out.
 Return Overdue Copy

 Pay Fine needs to be                                          Generalisation /Specialisation
 specific about                                                (same arrow type as in class diag.)
 participants                                                  – a special case of.

           JISC UML/WSDL – UML – some details, 9th Nov. 2004                  6
           Use Case Relationships
                                            Specialisation vs Extension
   Return Copy
                                            Distinction not clear-cut
                                            (some say UML should not have both)
     <<extend>>

                                            For extension base case can document the
             Return Overdue                 conditions for the extension case
 <<include>> Copy                           (“extension point”)

Pay fine                                    One possible decider -
             <<extend>>    Defer fine
                                            Generalisation is when user unilaterally
                                            chooses a variant
           Pay fine by
                                            Extension is when system detects the
           credit card
                                            condition, or needs to check whether it is OK
                                            – testing internal system state

                                            .

       JISC UML/WSDL – UML – some details, 9th Nov. 2004             7
              Use Case - Variants

                   Library
                                      Reserve book
Book                                  personally
Reserver                                                             Clerk


 <<actor>                                                            Show system boundary
                      Reserve
 >Book                Book                                 Reserve   With system name
 Reserver             electronically                       Book      Particularly when
                                                                     A sub-system of
                                                     Authenticate    A larger model
                                                     User


  The actor can be another system (a class) –
      In this case a library enquiry and reservation system
      Which is modelled as a separate system
       Electronic vs Personal reservation have different requirements
               E.g. user authentication is inside vs outside the system

       JISC UML/WSDL – UML – some details, 9th Nov. 2004                8
 Use Case Diagrams - Usage
Identification of Actors and functionalities
Requirements feed-back
   To communicate to the clients what the providers have understood
   a being the requirements
   DANGER –
     generalisations, extensions and inclusions
     make the diagrams too complex and technical for the clients to
      understand properly
Test Case generation
   Design Walk-throughs (sequence diagrams) of all Use Cases
   Implementation tests for all Use Cases
To drive the system design (not a good use!)
   Producing one module of code for each use case.
     Leads to top down, function-oriented system
     Loses the maintainability and flexibility benefits of object-

      oriented design
Keep focus on requirements documentation
   Include what is import for understanding system functionality
    JISC UML/WSDL – UML – some details, 9th Nov. 2004   9
  Use Case Documentation
Each use case needs supporting by
documentation –
  the name and diagram are not enough information


Generally, this would conform to some
organisation standard

An example
  See
  http://www.imsglbal.org/es/esv1p0/imes_usecasev1p0.html
  for full examples using an extension this format




  JISC UML/WSDL – UML – some details, 9th Nov. 2004   10
 Documentation - Essentials
Title:
  Return Overdue Book
Brief Description
  BookReturner hands book (copy) for return to Clerk
  and the system detects that the book is overdue
Actors:
  BookReturner: A user of the Library
  Clerk: A library employee in the clerical role
Stakeholders (those benefiting from this
functionality)
  Users: want their return of books recorded
  Clerks: want to be seen to be doing their job properly
  Administrators: Want to be able collect fines; want to
  ensure records are up-to-date

   JISC UML/WSDL – UML – some details, 9th Nov. 2004   11
  Documentation - Details
Triggers
  The BookReturner spontaneously decides to return
  the book, or has been prompted by a reminder
Basic Flow of events
  BookReturner hands book to Clerk.
  Clerk enters book return into system.
  System informs clerk that is over-due and what the
  fine is.
  Clerk negotiates actual or deferred payment with
  BookBorrower, and enters outcome to the system




  JISC UML/WSDL – UML – some details, 9th Nov. 2004   12
  Documentation - Details
Pre-conditions
  The period of loan terminated by this book return is
  greater than that allowed for this type of user and
  this type of book.
Post-conditions
  The payment of a fine is recorded, or the clerk agrees
  a deferred payment which is recorded.
Exception Handling
Related Use Cases:
  Defer Fine
  Pay Fine by Credit Card




  JISC UML/WSDL – UML – some details, 9th Nov. 2004   13
             CLASS DIAGRAMS
Overview –diagram types
 Use Case –                            more details
 Class -                               more detail
 Object –                              new
 Collaboration –                       new
 Sequence –                            more detail
 State –                               new (appreciation only)
 Activity -                            new (appreciation only)
 Packages -                            new (appreciation only)
 Deployment -                               new (appreciation only)



  JISC UML/WSDL – UML – some details, 9th Nov. 2004    14
             Class Relationships
          User                                                  Item



Student             Staff                 Copy           Book      Journal   Article

Generalisation (= Inheritance)
    Class relationship –
    Every instance of Staff is an instance of User
    Every operation of User is an operation of Staff
    Every Attribute of User is an attribute of Staff
    Every association of User is an association of Staff

This is model, not implementation
    Not necessarily “code re-use”
    For a O-O language implementation –
             might not be implemented as sub-class
    (Implementation language might not be O-O)

Its for understanding structure –
     although probably will drive implementation
     JISC UML/WSDL – UML – some details, 9th Nov. 2004                 15
                             Associations
          User                                                         Item         Is part     contains
                                                                                    of
                                        borrows       Is copy
                                                           of
Student              Staff                  Copy                Book      Journal                Article
                                                                         borrows
                                                                                          Orders print-off


   Associations – knows about
      Instance oriented - A staff instance may order print-off of an
      article
      Often can only be understood by drawing instance example –
      object diagram
      Class diagram records the potential actual associations, and
      defines some characteristics
      Name is associated with a line-end –
        role name - what role the associated object plays for the other

         object
        Usually name at most one end


          JISC UML/WSDL – UML – some details, 9th Nov. 2004                   16
                             Associations
          User                                                         Item         Is part     contains
                                                                                    of
                                        borrows       Is copy
                                                           of
Student              Staff                  Copy                Book      Journal                Article
                                                                         borrows
                                                                                          Orders print-off

   Associations – knows about
      Subsumes entity/relationship diagrams for showing data
      structures
      Subsumes inter-connection diagrams for showing which entities
      communicate
   Conceptual View (user communication)
      there is an association if there is a relevant real-world association
      – “a student can borrow a book”
   Implementation View (design)
      A (navigable) association implies a class has an attribute of the
      associated type, and vice-versa
      Don’t duplicate attributes and associations
         Copy does not need to show attribute – isCopyOf : Book

          JISC UML/WSDL – UML – some details, 9th Nov. 2004                   17
 Aggregation and Composition
     Journal                Article                 Author



              composition             (other) aggregation


Special Associations
  Aggregation – To model a collection of things
    Journal has a collection of Articles
    Article has a collection of Authors
 Composition
    A special case of aggregation – “ownership”
    Part can only belong to one whole
    The part cannot exist without the whole
 Role name
    Not given explicitly – implicit in the line end-point –
    “is part of”
    JISC UML/WSDL – UML – some details, 9th Nov. 2004        18
                         Multiplicities
                                                 Number of Copy objects that can
                                                  be associated with one student
            0..1                                     object : At least 0; At most 6
Student                                  0..6
                                                     1..*          1
                borrows                      Copy                       Book            Exactly 1
                                                              Is copy
                                         0..12                     of
Staff
        0..1            0 or
                        1                                   At least 1,no upper limit

   Constrains the number of instance of one end
   that can be associated with one instance
   of the other end (in this association type, at any one time)
   Either – single number (usually 0 or 1)
   Or range X .. Y.
       * for Y means no upper limit
   Can also do set of ranges –
       1..5 , 8..20      (hard to find an example!)
   Composition (“owner”) implies 1
   Note – “borrows” has become “has on loan” !!!!! –
        structure rather than interaction
        JISC UML/WSDL – UML – some details, 9th Nov. 2004                      19
                       Navigability

borrows     Is copy                                      borrows   Is copy
                 of                                                     of
  Copy                 Book                                 Copy             Book

 One-way                                                Two-way
 from copy to the                                       Also -
 Book it is a copy of                                   From a Book to any of its copies

Arrow-head means the association can be followed in
the direction shown
In implementation view, navigability requires attributes
to hold the link(s)to associated object(s)
How to show navigability and aggregation?




    JISC UML/WSDL – UML – some details, 9th Nov. 2004              20
Attribute / Operation Visibility
                Item
                                                       Book
                                        - Title : String

    Journal                             + copiesOnShelf() : Integer


Visibility
+         public                  accessed by any client of the class –
                                           default for operation
#         protected               typically from same class or sub-class
~         package                 typically anything in the same package
-         private                 typically, from the same class -
                                           default for attribute




        JISC UML/WSDL – UML – some details, 9th Nov. 2004             21
          OBJECT DIAGRAMS
Overview –diagram types
 Use Case –                            more details
 Class -                               more detail
 Object –                              new
 Collaboration –                       new
 Sequence –                            more detail
 State –                               new (appreciation    only)
 Activity -                            new (appreciation    only)
 Packages -                            new (appreciation    only)
 Deployment -                          new (appreciation    only)



  JISC UML/WSDL – UML – some details, 9th Nov. 2004    22
  Complex Class Structures
                                0..*
                                         Book
                                                1
                      by
               1..*                                 0..*
                                                           0..* contains
                      Author                  Division
                  1..*     by                       1

                            0..*       Part
                                                    Chapter


The intended structure would be elucidated by
giving some examples !
Particularly if audience is not familiar with this
particular view on the possible structure of
book
So illustrate the class diagram by one or more
instance diagrams

  JISC UML/WSDL – UML – some details, 9th Nov. 2004                        23
                             Object Diagram
               0..*     Book
                                1                                                     Class Diagram
       by
1..*                              0..*
                                       0..* contains
   Author                     Division
  1..*  by                          1

            0..*      Part          Chapter
                                                                B1: Book               Object Diagram
                                                          Title: UML & WSDL
                 A1: Author
                Name: Richard
                                             P11: Part              P12: Part              A2: Author
                   A2: Author                Title: UML            Title: WSDL            Name: David
                   Name: Guy

                        C111: Chapter                 C112: Chapter
                        Title: Classes               Title: Use Cases


       Object Diagram does not show full range of possibilities
       The lines are “links” – instances of associations
       Can annotate links with navigability and role if useful
       Special case of collaboration Diag.
            JISC UML/WSDL – UML – some details, 9th Nov. 2004                    24
COLLABORATION DIAGRAMS
Overview –diagram types
 Use Case –                            more details
 Class -                               more detail
 Object –                              new
 Collaboration –                       new
 Sequence –                            more detail
 State –                               new (appreciation    only)
 Activity -                            new (appreciation    only)
 Packages -                            new (appreciation    only)
 Deployment -                          new (appreciation    only)



  JISC UML/WSDL – UML – some details, 9th Nov. 2004    25
      Collaboration Diagrams
                             theUser: User
                                                         theCopy: Copy
                             suspended: No
Book
Borrower

                                                         theBook: Book


 To show an example of message passing interaction between
 objects
 Links - instances of class associations


 Actors/Objects –
    Show name and type
    Can show values for objects where useful




     JISC UML/WSDL – UML – some details, 9th Nov. 2004     26
       Collaboration Diagrams
     1: borrow (theCopy)                             1.2: borrow ()
                              theUser: User
                                                                       theCopy: Copy
                              suspended: No
Book
Borrower                                                                      1.2.1: borrowed()
                                                   1.3: borrowStatus
                     1.1: okToBorrow
                                                                       theBook: Book

Messages – actual messages passed,
   Can show operation invoked at destination
   Use self-messages to indicate internal
   condition testing
   Use structured sequence numbering scheme
   1.1 – first message produced as a result of
   receiving message 1
   1.2 - second message produced as a result of
   receiving message 1
      JISC UML/WSDL – UML – some details, 9th Nov. 2004                  27
     Collaboration Diagrams
     1: borrow (theCopy)                                1.2: borrow ()
                              theUser: User
                                                                         theCopy: Copy
                              suspended: No
Book
Borrower                                                                        1.2.1: borrowed()
                                                   1.3: borrowStatus
                     1.1: okToBorrow
                                                                         theBook: Book

Shows same kind of information as sequence diagram
  But with emphasis on object structure, rather than time
  sequence
  Both are interaction diagrams
  Sequence diagrams also have attribute values, if useful
  Same Structured sequence numbering

Generally, Sequence diagrams more useful for understanding
system behaviour – shows the time sequence more clearly

Use collaboration diagrams without specific messages, to
exemplify system interconnection structure
    JISC UML/WSDL – UML – some details, 9th Nov. 2004                    28
     SEQUENCE DIAGRAMS
Overview –diagram types
 Use Case –                            more details
 Class -                               more detail
 Object –                              new
 Collaboration –                       new
 Sequence –                            more detail
 State –                               new (appreciation    only)
 Activity -                            new (appreciation    only)
 Packages -                            new (appreciation    only)
 Deployment -                          new (appreciation    only)



  JISC UML/WSDL – UML – some details, 9th Nov. 2004    29
       Simple Sequence Diagram
    Book            theUser: User              theCopy: Copy             theBook: Book
    Borrower
                                                                                                     t
                                 1.1: okToBorrow
    1: borrow(theCopy)                                                                               i
                                                                                                     m
                                                                                                     e
                                   1.2: borrow()             1.2.1: borrowed()

     borrowStatus


                                                                                      Sending a message
 Object existence lifeline                Period of activation
                                                                                      The reply
Shows all replies ; Uses structured sequence numbering
1      BookBorrower invokes the use case -activates corresponding theUser object
1.1 theUser checks whether this is OK – self message
1.2 theUser tells theCopy object that it is now borrowed – it changes its state
1.2.1. theCopy tells theBook that it has been borrowed –
                                        it reduces its count of available copies
Reply - theUser confirms success to BookBorrower
         JISC UML/WSDL – UML – some details, 9th Nov. 2004                       30
                Creation and deletion
Librarian
                             theCatalogue:Catalogue                             Creation-
                                                                                Lifeline starts
                                                                                As a result
                                                                                of message
       registerBook(theBook)

                                          createBook(theBook)
                                                                theBook: Book



Librarian
                             theCatalogue:Catalogue             theBook: Book

                                                                                Deletion -
       removeBook(theBook)                                                      Lifeline ends
                                                                                Marked by a cross
                                           destroy()




            JISC UML/WSDL – UML – some details, 9th Nov. 2004             31
 So Far – Synchronous Messages
Librarian
                       theAccounts:Accounts              mailer: MailingLIst

       loseUser


         owesMoney

       loseUser



            Synchronous – the sender suspends until receives reply
            So no need for reply to be explicit

            Explicit reply to a synchronous message




     JISC UML/WSDL – UML – some details, 9th Nov. 2004            32
                  Asynchronous
Librarian
                       theAccounts:Accounts            mailer: MailingLIst

       loseUser


       loseUser


         owesMoney




              Asynchronous – the sender retains control and can
                send and receive further messages
                 other versions of arrow heads are also used

              Unspecified (simple) – could be synchronous or
                asynchronous
   JISC UML/WSDL – UML – some details, 9th Nov. 2004            33
           STATE DIAGRAMS
Overview –diagram types
 Use Case –                            more details
 Class -                               more detail
 Object –                              new
 Collaboration –                       new
 Sequence –                            more detail
 State –                               new
                                       (appreciation only)
 Activity -                            new (appreciation only)
 Packages -                            new (appreciation only)
 Deployment -                          new (appreciation only)


  JISC UML/WSDL – UML – some details, 9th Nov. 2004    34
Basic State(chart) Diagrams
In Wings                    On Shelf                    In Bindery            Statechart
                                                                              For Copy
                                                                              Class


     On Loan                Reserved on Shelf           Reserved In Bindery


Based on finite state machine concept
   Identifying all the different states a discrete-state system can be in
   Identify all the possible transitions between states




    JISC UML/WSDL – UML – some details, 9th Nov. 2004          35
Basic State(chart) Diagrams
In Wings    Catalogue()      On Shelf         Rebind()            In Bindery            Statechart
                                                                                        For Copy
                                                                                        Class
    Borrow()                         Reserved()                         Reserved()
                    Return()

      On Loan                Reserved on Shelf         Rebind()   Reserved In Bindery




UML Statecharts
  Generic life history of objects of a particular class
  Named states; Transition arrows
  Can associate a “trigger” with a transition ; e.g. receive particular
  message
  Dummy states
     Start State

     Final states




   JISC UML/WSDL – UML – some details, 9th Nov. 2004                    36
Basic State(chart) Diagrams
 In Wings    Catalogue()      On Shelf         Rebind()            In Bindery            Statechart
                                                                                         For Copy
                                                                                         Class
     Borrow()                         Reserved()                         Reserved()
                     Return()

       On Loan                Reserved on Shelf         Rebind()   Reserved In Bindery



Conveys a lot of information
   E.g. Can’t remove a copy till its been catalogued –
   right?; Some problems?
A basic state diag. is easy to read
Therefore a good vehicle for requirements clarification
Important to choose level of abstraction
 Actual book implementation will have more states
 Whether to show trigger
                                  Note – it’s a book, not a copy that gets reserved!! –
                                 this was just to make a more interesting example
    JISC UML/WSDL – UML – some details, 9th Nov. 2004                    37
                         Statecharts
   Full capabilities give programming language expressivity
   Most useful are –
      Guards – express conditions
      Compound states - abstraction


Guard
   identify (internal) condition on
     transition being possible                            On Shelf
   Trigger [guard]
                                                                 Reserved() [not shortTermCopy]

                                                          Reserved on Shelf




      JISC UML/WSDL – UML – some details, 9th Nov. 2004                38
Compound States - Abstraction
  In Wings   Catalogue()      On Shelf          Rebind()           In Bindery



      Borrow()                          Reserved()                       Reserved()
                      Return()

       On Loan                Reserved on Shelf         Rebind()   Reserved In Bindery




                             On Shelf +         Rebind()           In Bindery



      Borrow()                          Reserved()                       Reserved()
                      Return()

       On Loan                                       Reserved


 Give separate statechart for Reserved and On Shelf +
 And / or show them in-place as compound state
    JISC UML/WSDL – UML – some details, 9th Nov. 2004                   39
    FURTHER DIAG. TYPES
Overview –diagram types
 Use Case –       more details
 Class -          more detail
 Object –         new
 Collaboration –  new
 Sequence –       more detail
 State –          new
 Appreciation only
      Activity
      Package
      Deployment




  JISC UML/WSDL – UML – some details, 9th Nov. 2004   40
                           Activity
A flow-chart
 Used to develop implementation of object
 Also used for business level modelling
 Just give a business level example




  JISC UML/WSDL – UML – some details, 9th Nov. 2004   41
      Business Activity Diagram
                 user                              librarian

      [borrower] Find Book
                 on shelf


                     Wait in
    [returner]       queue

                                                             [returning]

                                           [borrowing]
                                       Record                    Record         Put book back
                                       return                    return         On shelf

                                       finalise




              decision          description       activity             Synchronisation bar –
                                                                       Start/collect concurrent activities
[guard]                                                                “concurrent” = non-sequenced
             transition                           Start / stop         Any order or parallel
          JISC UML/WSDL – UML – some details, 9th Nov. 2004                         42
                                 Packages
          User                                                          Item         Is part        contains
                                                                                     of
                                        borrows        Is copy
                                                            of
Student              Staff                  Copy                 Book      Journal                  Article
                                                                          borrows
                                                                                               Orders print-off

          User                                                                      To do with items
                                                 items
                                                                                     Dependency on
Student              Staff
                                                                                     something in
                                                                                     the package

   Group any collection of elements and into a named package
   which can be included in diagrams which depend on the
   package
   Any collection of components
   Used in any type of diagram
          JISC UML/WSDL – UML – some details, 9th Nov. 2004                    43
                         Packages
Possible reasons for use
 Just to hide irrelevant detail
 To reflect implementation team structure
 Factor the design process
 Create different namespaces
      Names must be unique within package
      Full name is package-name::element-name
 Control visibility –
       and thus reduce dependencies




  JISC UML/WSDL – UML – some details, 9th Nov. 2004   44
Deployment and Components
Component (here) –
 “a distributable piece of an implementation
 of a system, including S/W code , but also
 including business documents etc. in a
 human system”
 A WSDL definition could usefully viewed as
 a component
Deployment Diagram shows –
 Hardware items and physical communication
 links
 Location of components on H/W items



  JISC UML/WSDL – UML – some details, 9th Nov. 2004   45
  Deployment/Component Example



User’s:PC          <<Internet>>        Univ:Server         <<LAN>>        Clerk’s:PC


B:Browser                                P:Portal                           L:Library
                                                                            System




   Shows Hardware Structure
   Shows an example of intended deployment

   Shows component dependencies –
        Design/Implementation of Portal depends on-
            Characteristics of expected user browers
            Interface to Library System

       JISC UML/WSDL – UML – some details, 9th Nov. 2004             46
                          Summary
Requirements
  Use Case Diag.
    Document requirements
    Structured with extension/inclusion/specialisation
    Provides a handle for the supporting documentation,
    which is essential –
    use-case diag. itself can be fairly vacuuous


Structure
  Class Diag.
    Develop structure of objects in system
    Classes of objects provide the basis for subsequent
    diagrams
    Central step in firming up the system

    JISC UML/WSDL – UML – some details, 9th Nov. 2004   47
                           Summary
Behaviour – Draws out detail
1. Track one example through multiple participants
    Show how different participants interact in one case

   Sequence Diag.
      Walk-through of particular use-case
      To show details of behaviour and interactions
      Important clarifications

   Collaboration Diag.
      Same role as sequence diagrams, but -
       Emphasises Object linking structure
       Sequence of events less clear
       Less useful than Sequence Diagram
      Special case is Object diagram (really structure)
       For providing examples to elucidate complex class
        structures

     JISC UML/WSDL – UML – some details, 9th Nov. 2004   48
                           Summary
Behaviour – Draws out detail
1. Track one example through multiple participants
    Show how different participants interact in one case
2. Tracks one participant through all alternative
    interactions –
    Shows how different cases interact for one participant
    the orthogonal perspective

   State(chart) Diag.
      States and transitions between them
      Triggers and guards

   Activity Diagram
     Flow chart
     Can show concurrency and multiple participants
     Most useful is for modelling overall enterprise


     JISC UML/WSDL – UML – some details, 9th Nov. 2004   49
                         Summary
Supplementary
 Packaging
   Cut the model up into manageable pieces
 Component Deployment
   Show how the model elements manifest in
   the real world




   JISC UML/WSDL – UML – some details, 9th Nov. 2004   50
      An Overall Development Process
                             Partially articulated
                             requirements

Capture
Require-
  ments

                          Use Case Diag.                                                 REQUIREMENTS




Construct
 Model of                  Class Diag.                          Deployment Diag..         STRUCTURE
  Overall
 system



                     Sequence Diag.                                State Diag.             BEHAVIOIUR
                     Collaboration Diag                            Activity Diag.
                 Single case                                    Single participant
                 multi-participant interaction                  multi-case interaction


            JISC UML/WSDL – UML – some details, 9th Nov. 2004                       51
                              END




JISC UML/WSDL – UML – some details, 9th Nov. 2004   52
                 Practical Work
Use of the Poseidon Tool (Community
version)
 Examples of inputting given diagram
 Putting in some diagrams you have invented


Requires some UML diagram creation,
 to do manually beforehand –




  JISC UML/WSDL – UML – some details, 9th Nov. 2004   53
 1. Class Diagram Exercise
Define a Class Diagram
For a Journal series – probably mythical
Such that the it can support the
requirements –
 Users being able to do searches on:
      author,
      keyword,
      ….. (anything else you think appropriate)
 Staff being able to find out the status –
      On-the-shelf
      Being-bound
      … (anything else you think appropriate)



  JISC UML/WSDL – UML – some details, 9th Nov. 2004   54
2. Remote Borrowing Example
We add to the Library System the requirement that
     a member of staff can electronically submit a request to

      borrow an item
  if successful, the request results in
     the item being posted to them in the internal University
      snail-mail system.
   the use case(s) for this must include verifying the
  staff members identity

Do (at least)
   a sequence diagram for this remote-borrowing case
  A use-case diagram that combines
     The remote borrowing case

     The normal case – user physically going to the library




   JISC UML/WSDL – UML – some details, 9th Nov. 2004   55

				
DOCUMENT INFO
Shared By:
Categories:
Tags:
Stats:
views:0
posted:10/7/2012
language:Unknown
pages:55