Your SlideShare is downloading. ×
Class11
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Class11

169
views

Published on

Published in: Education

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
169
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
0
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide
  • PurchasingOrder(date, quantity) SaleTransaction(date) AdvertisementTVShow(date, price) AccountLedger(Date/TimeOfUpdate) LedgerPayable(Date/TimeOfUpdate) LoanedBook(CopyNumber, Overdue)
  • Transcript

    • 1. Class diagram II Asper School of Business University of Manitoba Systems Analysis & Design Instructor: Bob Travica Updated: October 2009
    • 2. Outline
      • More on associations
      • Association class
      • Fully developed classes
      • Completing procedure for creation of class diagrams
      3510 Systems Analysis & Design * Bob Travica of 9
    • 3. Associations
      • One-to-many (most frequent; example: Customer—Order)
      • One-to-one (occasionally; example: Customer—CustomerBillingAddress)
      • Many-to-many (moderately frequent; examples:
        • Student—Course Section
        • Order—Item (Product)
        • Employee—Project
      3510 Systems Analysis & Design * Bob Travica of 9
    • 4. Association class
      • Two ways to think about it:
        • 1) A class that stores some extra attributes that characterize associations between classes
      3510 Systems Analysis & Design * Bob Travica of 9 2) A class that intermediates in many-to-many relationship (resolves variation that exists on both sides of association) term
    • 5. RMO class diagram (simplified) 3510 Systems Analysis & Design * Bob Travica of 9
      • Customary simplification:
      • Show just maximum multi-
      • plicity
      • Just attributes of Association
      • Classes shown
      Figure 8-9 modified
      • Association Entity consists of transaction data.
      Catalog ReturnItem Product Order ProductOrder Customer CatalogProduct productPrice InventoryItem Shipper * * 1 has * 1 * 1 * delivered by * 1 * 1 * has can be places delivered by appears on * * ReturnItemOrder dateReturned reason quantity Shipment ordered on * ProductShipment quantity quantity
    • 6. Fully developed classes (design level) 3510 Systems Analysis & Design * Bob Travica of 9 Methods Attributes
      • = private
      • + = public
      • () = attribute affected or
      • input data
      • : string, number = data type
      Figure 8-7
    • 7. How to get information for class diagram
      • The source of information can be:
        • Description (narrative)
        • Use case diagrams & descriptions
        • Use case table
        • Analyzing master data and transactional data
      3510 Systems Analysis & Design * Bob Travica of 9
    • 8. Completing a class diagram
      • Standard procedure:
      • 1. List classes
      • 2. List attributes
      • 3. Draw simplified class rectangles (name and attribute spaces only)
      • 4. Insert attributes in class rectangles
      • 5. Determine keys
      • 6. Draw associations and name them
      • 7. (New) Draw Association Class for each relationship that has attribute(s) on its own, or that you think is M:M.
      3510 Systems Analysis & Design * Bob Travica of 9
    • 9. Exercises
      • Determine if Association Class is needed between the classes:
        • 1. Product – Supplier
        • 2. Product – SalesPerson
        • 3. Advertisement – TVShow
        • 4. Advertisement – MarketingAgency
        • 5. BankAccount – TransactionLedger
        • 6. GeneralLedger – AccountPayable
        • 7. Book – LibraryLoan
      3510 Systems Analysis & Design * Bob Travica of 9

    ×