A use case diagram shows an actor connected to a use case with a dashed arrow labeled ">". What is the likely issue if the arrow is drawn as a solid line instead?

medium📝 Analysis Q14 of 15

Software Engineering - Requirements Engineering

A use case diagram shows an actor connected to a use case with a dashed arrow labeled "<>". What is the likely issue if the arrow is drawn as a solid line instead?

AThe diagram incorrectly shows a direct association instead of an include relationship

BThe actor symbol is wrong

CThe use case should be a rectangle

DThe diagram is missing actors

Step-by-Step Solution

Solution:

Step 1: Understand <> notation
The <> relationship is shown with a dashed arrow from one use case to another, not from actor to use case.
Step 2: Identify the error in arrow style
A solid line from actor to use case shows direct association, not an include relationship, so the diagram is incorrect.
Final Answer:
The diagram incorrectly shows a direct association instead of an include relationship -> Option A
Quick Check:
Include = dashed arrow between use cases, not solid actor line [OK]

Quick Trick: <> uses dashed arrows between use cases only [OK]

Common Mistakes:

Drawing solid lines for <>
Confusing actor symbols with use case symbols
Misplacing <> arrows from actors

Master "Requirements Engineering" in Software Engineering

9 interactive learning modes - each teaches the same concept differently

Learn Why Deep Visual Try Challenge Project Recall Time

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions

More Software Engineering Quizzes

A use case diagram shows an actor connected to a use case with a dashed arrow labeled ">". What is the likely issue if the arrow is drawn as a solid line instead?

Step 1: Understand <> notation

Step 2: Identify the error in arrow style

Final Answer:

Quick Check:

Want More Practice?