CS 2401
Software Engineering 1
Discussion Assignment Unit 3
Difference Between a Scenario and a Use Case
In software engineering, both scenarios and use cases play crucial roles in defining system
behavior, yet they differ in their scope and purpose. A scenario is a specific instance of a use
case, representing a detailed sequence of events in a system from the perspective of an actor. A
use case, on the other hand, is a generalized description of a system's functionality that outlines
various possible scenarios.
Definition and Usage
Scenario
A scenario is a concrete and specific sequence of interactions between an actor (user or external
system) and the system. It describes a single execution path and can be categorized into happy
path scenarios (successful executions) and exception scenarios (failure or error situations).
Scenarios are useful for testing and validating system behavior in particular situations.
Use Case
A use case is an abstraction that defines how actors interact with the system to achieve a goal. It
encompasses multiple scenarios, including success and failure conditions, and is represented
using UML diagrams to illustrate system functionalities. Using cases help in system design by
outlining user interactions and guiding the development process.
Examples
Example 1: Online Library System
Use Case: "Borrow a Book"
Actor: Library Member
Description: A member borrows a book from the library.
Scenarios:
o Happy Path Scenario:
1. The member logs into the library system.
2. The member searches for a book and selects it.
3. The system checks book availability.
4. The member confirms the borrowing request.
5. The system records the transaction and updates the book status.
6. The member receives a confirmation message.
o Exception Scenario:
1. The member logs in and searches for a book.
2. The book is unavailable for borrowing.
3. The system notifies the member about the unavailability and suggests
alternatives.
Example 2: Online Banking System
Use Case: "Transfer Funds"
Actor: Bank Customer
Description: A customer transfers funds between accounts.
Scenarios:
o Happy Path Scenario:
1. The customer logs into the banking portal.
2. The customer selects the "Transfer Funds" option.
3. The customer enters the recipient details and the transfer amount.
4. The system validates the details and processes the transaction.
5. The customer receives a transaction confirmation.
o Exception Scenario:
1. The customer attempts to transfer funds.
2. The system detects insufficient funds.
3. The system notifies the customer and rejects the transaction.
When to Use Each Construct
Use cases are used in the early stages of software design to capture functional
requirements and define system interactions broadly.
Scenarios are used for detailing specific use case executions, including test case design
and validation.
References
Marsic, I. (2012). Software engineering. Rutgers: The State University of New Jersey.
Retrieved from https://my.uopeople.edu/pluginfile.php/57436/mod_book/chapter/46513/
CS4403MarsicTextbook.pdf
Ambler, S. (2003-2018). UML 2 Use Case Diagrams: An Agile Introduction. Agile
Modeling. Retrieved from http://www.agilemodeling.com/artifacts/useCaseDiagram.htm
Bell, D. (2003). An introduction to the Unified Modeling Language. IBM DeveloperWorks.
Retrieved from http://www.ibm.com/developerworks/rational/library/769.html
Bell, D. (2004). The class diagram. IBM DeveloperWorks. Retrieved from
http://www.ibm.com/developerworks/rational/library/content/RationalEdge/sep04/bell/
index.html
