• Shuffle
    Toggle On
    Toggle Off
  • Alphabetize
    Toggle On
    Toggle Off
  • Front First
    Toggle On
    Toggle Off
  • Both Sides
    Toggle On
    Toggle Off
  • Read
    Toggle On
    Toggle Off
Reading...
Front

Card Range To Study

through

image

Play button

image

Play button

image

Progress

1/5

Click to flip

Use LEFT and RIGHT arrow keys to navigate between flashcards;

Use UP and DOWN arrow keys to flip the card;

H to show hint;

A reads text to speech;

5 Cards in this Set

  • Front
  • Back

What is Use Case Diagram?

1. To show representation of system


2. To understand the system before


building or modifying


3. Use case shows interaction


between the system and its


environment


4. To shows overview of functional


requirement


5. To serve as a basis for testing

Use Case Diagram Overview

1. It is a picture that describe


- how actors relate to use cases


- how use case relate to use case


2. Diagram are helpful but it doesnt


explain the full information


3. Textual description is essential

Purpose of Use Case Diagram

1. To specify system context


2. To capture system requirement


3. To validate system architecture


4. To drive implememtation and


generate test cases


5. To identify the classes required

Use Cases Element

Actor


1. Represent a user role or another


interacting system


2. Can be human, machine, system


3. Represented by stick figure



Use Case


1. External view of the system that


provide action user might


perform to complete a task


2. Function for business purpose


3. Represent by an eclipse



Use Case Description


1. Text description


2. Brief description, 3 word max


3. In or out of the use case eclipse



Boundary


1. The dividing line between the


system and the environment


2. Use cases in boundary


3. Actors outside boundary


4. Represent as a box



Relationship


1. Association


- Indicate communication,not data


flow


- Solid lines



2. Generalization


- Represent a specialized use case


to a more generalized one


- General are higher, arrow to me



3. <<Include>>


- Including another use case to


accomplish functionality


- To break bigger part of use cases


- dashed arrow, arrow from me



4. <<extend>>


- if a use case is optional


- to add extra functionality under


certain circumstances


- dashed arrow, arrow to me


Use Case Scenario Template

1. Use Case(name)


2. Description


3. Used By, actors


4. Preconditions


5. Main Scenario


- From User


- From System


6. Alternatives


7. Exceptional