Use Case Packet

General Instructions

This assignment will be used to assess your design abilities in this course. It requires you to understand the customer design of the system (the use cases and their descriptions) and to take that as input and transform it into a software design for evaluation prior to programming.

In an actual large project these packets are not all completed at one time but rather trickle out as design continues. As they are deemed complete, the project manager assigns them to programmers.

Make sure you take the time to assure you have a good understanding of the use case prior to your development of the individual deliverables within the packet.

This assignment is done individually. Each student is responsible for one use case packet. It should be a use case that contains a substantial number of use case points. Each deliverable in this packet has supporting documents that aid you in completing the specific deliverable.

Each team member will turn in just one Use Case Packet for individual grade, even though the entire team project is likely to involve several additional use cases. One objective of the assignment is to demonstrate that you understand how to put together a Use Case Packet.

Your submission must be in HTML 4.01, and follow the template structure given below, so that it can be merged with the work of other students to become part of your team's Software Design Specification (SDS) document.

Organization

Your submission should be organized into the following sections:

1. Header
2. Use Case Diagram
3. Class Diagram
4. Use Case Database Table Definitions
5. Use Case Description
6. Use Case User Interface Designs
7. Use Case User Interface Navigational MatrixUse Case Functional Testing Scenario
8. Use Case Sequence Diagram
9. Use Case Extended Class Diagram

Specific Instructions

  Header

Begin with a header giving the name of the use case, and your name:

Use Case Packet: use case name

Author: your name

  1. Use Case Diagram

This must be a copy of what is in the team's SDS. Anyone changing the SDS must notify everyone else that it is changed. Use a ".gif" or ".jpg" image.

  2. Class Diagram

This must be a copy of what is in the team's SDS. Anyone changing the SDS must notify everyone else that it is changed. Use a ".gif" or ".jpg" image.

  3. Use Case Table Definitions

This must be a copy of the tables that apply to this use case. It must be a copy of what is in the current SDS. Anyone changing the SDS must notify everyone else that it is changed.

  4. Use Case Description

This is your work. It must match the Use Case Diagram, so anyone changing the SDS UCD must get approval from all that it can be changed.

  5. Use Case User Interface Designs

This must describe all the screen and report layouts that are needed for this use case. It is a copy of what is in the SDS. Anyone changing the SDS must get approval from everyone who has that particular screen or report.

  6. Use Case Navigational Matrix

Show the navigation for just this one use case. Use the HTML table format.

  7. Use Case Functional Tests

This is your work. It must match the Use Case Diagram, so anyone changing the SDS UCD must get approval from all that it can be changed.

  8. Use Case Sequence Diagram

This is your work. It must match the Use Case Diagram, so anyone changing the SDS UCD must get approval from all that it can be changed.

  9. Use Case Extended Class Diagram

This is your work. It must match the Class Diagram, so anyone changing the SDS CD must get approval from all that it can be changed.

Grading Criteria

Points may be deducted for all of the following defects that are found:

1. Items that are common to the entire project SDS missing or incorrect
   1. Use Case Diagram
   2. Class Diagram
2. Use Case Functional Test
   1. Missing actions or incorrect actions
   2. Missing or incorrect test scripts
   3. Missing or incorrect sequence of events tests
   4. Missing or incorrect alternative paths tests
3. Use Case Description
   1. Missing actions or incorrect actions
   2. Missing or incorrect messages or use case linkages
   3. Missing or incorrect sequence of events
   4. Missing or incorrect alternative paths
4. Sequence Diagram
   1. Missing or incorrect objects
   2. Missing or incorrect messages
   3. Missing or incorrect lifelines
   4. Missing or incorrect activation boxes
5. Use Case Extended Class Diagram
   1. Missing or incorrect Classes
   2. Missing or incorrect relationships
6. Any other items specific to this use case