Project Analysis and Use Case Diagrams

1
Project Analysis and Use Case Diagrams

• 1-30-2002

2
Description of Project

• Remember that you are designing a system to work
  as a scalable, extensible, accesible client
  server system that can be used to facilitate the
  implementation of different services.
• A possible set of services would include
  multi-user games. However, I would encourage a
  group (or 2) to do something non-game related if
  you are inspired to.

3
Discussion of Project

• At this point I would like to have a discussion
  of the analyses that you have done on this
  project over the last two weeks. Basically this
  is a discussion of what you are going to be
  turning in to me a bit later in this class.
• Two weeks ago you basically decided that Java
  would be the language of choice for this project.
  What else have you come up with?

4
Use Case Diagrams

• UML (Unified Modeling Language) is a graphical
  way of representing the analysis and design of
  programs, typically object-oriented programs.
• We will be looking at different types of UML
  diagrams over the course of the semester, for
  today we are focusing on Use Case Diagrams which
  are helpful in the analysis phase of software
  design.

5
Use Cases

• The fundamental component of a Use Case Diagram
  are the use cases. These are basically
  activities in the system that users can engage
  in.
• They are represented by labeled ovals. The names
  of these ovals should use the style used for
  behaviors of objects (methods of classes).

6
Actors

• UCDs also typically include the people/entities
  who would be performing the given use cases.
  These are referred to as actors. These typically
  represent different types of users, though it is
  possible that in a distributed system one
  component might view another component as an
  actor.
• These are represented by stick figures and the
  names follow class naming conventions.

7
Relationships

• Communicates
• This is when an actor can invoke a certain use
  case. It is denoted by a line.
• Includes/Uses
• This allows us to add detail by having a use case
  specify what other behaviors it invokes.
• Extends
• This allows us to specify that a use case is a
  more specialized version of a different use case.

8
Group Discussions

• Now I want you to break up into the groups that
  you were assigned in and discuss the project. Of
  primary importance is deciding what part of the
  project your group wants to do. Along with your
  written analysis work I want each group to hand
  me a written description of what you want to work
  on. Ill try to make assignments from that.