Chapter 6 TC & Cases

Chapter 6 TC - Chapter 6 TC Cases TC 1 4 6 9 State Patrol Ticket System 1 TC 1 The following description identifies the business need for a simple

Info iconThis preview shows pages 1–9. Sign up to view the full content.

View Full Document Right Arrow Icon
TC 1, 4, 6, 9 TC 1, 4, 6, 9 State Patrol Ticket System 1 State Patrol Ticket System 1
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
TC 1 TC 1 The following description identifies the business need for a simple university library system. Based on the description, develop the following diagrams: Develop a domain class diagram Develop a use case diagram Do a CRUD analysis to ensure that the identified classes and use cases are consistent. Update both your class diagram and use case diagram as necessary.
Background image of page 2
TC 1 (a) TC 1 (a)
Background image of page 3

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
TC 1 (b) TC 1 (b)
Background image of page 4
TC 1 (c ) TC 1 (c ) Use Case Book Title Book Copy Loan Book Copy onLoan Patron Reservation Search for book title R R Reserve book C Check out books U C C U Check in book U U Enter new book information C C Print book title report R Delete book copy information D View overdue books R View reservations R
Background image of page 5

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
TC 4 TC 4 Given the following narrative, do the following: Develop an activity diagram for each scenario. Complete a fully developed use case description for each scenario.
Background image of page 6
TC 4 (a) TC 4 (a)
Background image of page 7

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
TC 4 (b) (b) Use Case Name: Create a new sale Scenario: A new sale to a contractor (on account sale) Triggering Event: New sale Brief Description: A contractor has items to purchase. The clerk rings up the items and then adds them to the contractor’s account. Actors: Sales clerk Stakeholders: Sales clerk, accounting department, Sales department Preconditions: Customer account must exist Inventory items must exist Postconditions: New sale created Sales line items created and connected to sale Customer (contractor) account updated Flow of Events: Actor System 1. Clerk enters contractor ID 2. Clerk enters each item 3. Clerk indicates end of sale 4. If contractor wants receipt, request receipt 1.1 System validates contractor account 2.1 System finds item in inventory, finds price, adds to total. 3.1 System calculates total and adds to contractor account 4.1 System prints receipt Exception Conditions: 1.1 If contractor account out of balance, then either treat this sale as a cash sale, or stop process and send contractor to accounting clerk.
Background image of page 8
Image of page 9
This is the end of the preview. Sign up to access the rest of the document.

This note was uploaded on 03/10/2012 for the course IT 1022 taught by Professor Tig during the Winter '12 term at UCSI.

Page1 / 17

Chapter 6 TC - Chapter 6 TC Cases TC 1 4 6 9 State Patrol Ticket System 1 TC 1 The following description identifies the business need for a simple

This preview shows document pages 1 - 9. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online