Use cases in Java - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is a use case in software development?

A use case describes how a user interacts with a system to achieve a specific goal. It shows the steps and actions involved.

beginner

Name two main parts of a use case.

1. Actors: who interacts with the system.
2. Scenarios: the steps or flow of actions to complete a goal.

intermediate

Why are use cases important in Java application development?

They help developers understand user needs and design the system to meet those needs clearly and simply.

intermediate

How can use cases improve communication in a project?

Use cases provide a common language between developers, testers, and users, making sure everyone understands what the system should do.

beginner

Give an example of a simple use case for a Java login system.

Actor: User
Scenario: User enters username and password → System checks credentials → System grants access if correct or shows error if wrong.

What does a use case primarily describe?

A The internal code structure of a program

B The color scheme of the user interface

C The hardware requirements for software

D How users interact with a system to achieve a goal

A use case focuses on user interactions and goals, not technical details like code or hardware.

Who is an 'actor' in a use case?

A A user or external system interacting with the software

B A class in Java code

C A database table

D A software bug

Actors represent users or other systems that interact with the software.

Which of these is NOT a benefit of use cases?

A Improving communication between team members

B Defining user goals clearly

C Automatically generating Java code

D Helping testers create test cases

Use cases help with understanding and communication but do not automatically generate code.

In a login use case, what is the system expected to do after receiving user credentials?

A Check if credentials are correct

B Display the main menu immediately

C Delete the user account

D Send an email to the user

The system must verify credentials before granting access.

Which part of a use case describes the steps to complete a task?

A Actor

B Scenario

C Class

D Package

The scenario outlines the sequence of actions in the use case.

Explain what a use case is and why it is useful in Java programming projects.

Think about how use cases help understand what users want from the software.

Describe the main parts of a use case and give a simple example related to logging into a system.

Consider who uses the system and what steps they take.

Practice

1. What is the main purpose of a use case in Java programming?

easy

A. To debug syntax errors

B. To write the actual Java code

C. To compile the Java program

D. To describe how users interact with the program

Solution

1. Step 1: Understand the definition of use case

   A use case explains how users will use or interact with a program, focusing on user actions and system responses.

2. Step 2: Differentiate use case from coding tasks

   Writing code, compiling, or debugging are programming tasks, not the purpose of use cases.

3. Final Answer:

   To describe how users interact with the program -> Option D

4. Quick Check:

   Use case = user interaction description [OK]

Hint: Use cases focus on user actions, not code details [OK]

Common Mistakes:

• Confusing use cases with code writing
• Thinking use cases are for debugging
• Assuming use cases are about compiling

2. Which of the following is the correct way to write a simple use case step in Java documentation?

easy

A. if(user == null) { throw new Exception(); }

B. User clicks the 'Login' button to access the system.

C. System.out.println('Login successful');

D. int loginButton = 1;

Solution

1. Step 1: Identify use case style

   Use cases are written as simple, clear steps describing user actions, not code.

2. Step 2: Check options for descriptive text

   User clicks the 'Login' button to access the system. describes a user action clearly; others are code snippets, not use case steps.

3. Final Answer:

   User clicks the 'Login' button to access the system. -> Option B

4. Quick Check:

   Use case step = user action description [OK]

Hint: Use case steps are plain user actions, not code [OK]

Common Mistakes:

• Writing code instead of user actions
• Using technical syntax in use case steps
• Mixing code and use case descriptions

3. Given this use case description:

1. User enters username and password.
2. System validates credentials.
3. System grants access if valid.
4. System shows error if invalid.

What is the expected system behavior if the user enters wrong password?

medium

A. System shows error

B. System grants access

C. System crashes

D. System ignores input

Solution

1. Step 1: Analyze the use case steps

   Step 4 says system shows error if credentials are invalid.

2. Step 2: Apply to wrong password case

   Wrong password means invalid credentials, so system shows error.

3. Final Answer:

   System shows error -> Option A

4. Quick Check:

   Invalid credentials = show error [OK]

Hint: Invalid login means error message shown [OK]

Common Mistakes:

• Choosing system grants access for wrong password
• Assuming system crashes on error
• Ignoring error handling step

4. Identify the error in this use case step:

Step 2: System checks if user password is correct.
Step 3: If password is wrong, system grants access.

medium

A. Step 3 should deny access if password is wrong

B. Step 2 should accept any password

C. Step 3 should crash the system

D. No error, steps are correct

Solution

1. Step 1: Review step 3 logic

   Granting access on wrong password is a security error.

2. Step 2: Correct expected behavior

   System should deny access or show error if password is wrong.

3. Final Answer:

   Step 3 should deny access if password is wrong -> Option A

4. Quick Check:

   Wrong password = deny access [OK]

Hint: Wrong password must never grant access [OK]

Common Mistakes:

• Allowing access on wrong password
• Ignoring security in use case steps
• Assuming system crashes on wrong input

5. You want to write a use case for a Java program that allows users to reset their password. Which sequence of steps best fits this use case?

hard

A. User logs in -> System checks password -> System grants access -> User resets password

B. System resets password automatically -> User notified -> User logs in

C. User requests password reset -> System sends reset link -> User sets new password -> System confirms update

D. User changes username -> System updates profile -> User logs out

Solution

1. Step 1: Identify correct password reset flow

   Reset involves user request, system sending link, user setting new password, and confirmation.

2. Step 2: Compare options to expected flow

   User requests password reset -> System sends reset link -> User sets new password -> System confirms update matches this flow clearly; others describe unrelated or incorrect sequences.

3. Final Answer:

   User requests password reset -> System sends reset link -> User sets new password -> System confirms update -> Option C

4. Quick Check:

   Password reset = request, link, new password, confirm [OK]

Hint: Password reset needs user action and confirmation steps [OK]

Common Mistakes:

• Confusing login with password reset
• Assuming system resets password without user input
• Mixing username change with password reset