Requirements and use cases in LLD - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to identify the primary actor in a use case.

LLD

The primary actor in a use case is the [1] who initiates the interaction.

Drag options to blanks, or click blank then click option'

Asystem

Bserver

Cuser

Ddatabase

Attempts:

3 left

💡 Hint

Common Mistakes

Confusing the system with the actor.

Choosing internal components like database as actors.

The primary actor is the user who starts the use case interaction.

2fill in blank

medium

Complete the code to specify the main goal of a use case.

LLD

The main goal of a use case is to [1] a specific function or service for the actor.

Drag options to blanks, or click blank then click option'

Adelay

Bdescribe

Cignore

Dachieve

Attempts:

3 left

💡 Hint

Common Mistakes

Choosing 'describe' instead of 'achieve' as the goal.

Selecting negative actions like 'ignore' or 'delay'.

The main goal is to achieve a function or service that the actor needs.

3fill in blank

hard

Fix the error in the use case description by completing the blank.

LLD

A use case should include [1] to handle exceptions and errors.

Drag options to blanks, or click blank then click option'

Aalternate flows

Bscenarios

Cactors

Ddiagrams

Attempts:

3 left

💡 Hint

Common Mistakes

Confusing scenarios with alternate flows.

Choosing actors or diagrams which do not handle errors.

Alternate flows describe how the system handles exceptions and errors.

4fill in blank

hard

Fill both blanks to complete the use case template fields.

LLD

Use case name: [1]
Primary actor: [2]

Drag options to blanks, or click blank then click option'

ALogin

BSystem

CUser

DDatabase

Attempts:

3 left

💡 Hint

Common Mistakes

Swapping actor and use case name.

Choosing system or database as primary actor.

The use case name is 'Login' and the primary actor is the 'User'.

5fill in blank

hard

Fill all three blanks to complete the use case description.

LLD

Precondition: [1]
Trigger: [2]
Postcondition: [3]

Drag options to blanks, or click blank then click option'

AUser is logged out

BUser clicks login button

CUser is logged in

DSystem is offline

Attempts:

3 left

💡 Hint

Common Mistakes

Mixing precondition and postcondition.

Choosing system offline as a trigger.

The precondition is that the user is logged out, the trigger is clicking the login button, and the postcondition is the user is logged in.