When programming, a broad use case can usually be broken down into smaller scenarios. A scenario is defined as a goal that an actor can accomplish with a single encounter. Identifying the scenarios may be as simple as looking at potential outcomes. A user might buy a product, check their balance, contact the company, or any other task that can be accomplished with a single visit through multiple steps. Watch this online video to learn how to identify scenarios specific to your application.
When we describe a use case scenario, we're typically looking at describing a…goal that an actor can accomplish in a single encounter, and we're trying to…stay focused on the user's goal, on their intention.…So, for example, log in to application might first sound like a use case.…It has an active verb, it typically has multiple steps, multiple conditions, you…could forget the password or be required to register and so on.…But if we emphasize the users focus their goal, we realized that their goal with…our system is not to log in, the reason they want to log in is to do something.…
So what is that something in your system?…We're looking for something like Purchase items, Create new document, Balance…accounts, these are user-focused goals, each with several steps that could be…accomplished in one encounter.…Logging in might be part of one of these use cases, part of one of these goals,…but it's not a use case in itself.…On the other side of the equation, a goal on the level of Write book or Merge…organizations would be too broad.…
Let Simon Allardice introduce you to the terms—words like abstraction, inheritance, polymorphism, subclass—and guide you through defining your requirements and identifying use cases for your program. The course also covers creating conceptual models of your program with design patterns, class and sequence diagrams, and unified modeling language (UML) tools, and then shows how to convert the diagrams into code.
- Why use object-oriented design (OOD)?
- Pinpointing use cases, actors, and scenarios
- Identifying class responsibilities and relationships
- Creating class diagrams
- Using abstract classes
- Working with inheritance
- Creating advanced UML diagrams
- Understanding object-oriented design principles
Skill Level Intermediate
1. Core Concepts
2. Object-Oriented Analysis and Design
Defining requirements6m 9s
3. Utilizing Use Cases
4. Domain Modeling (Modeling the App)
5. Creating Classes
6. Inheritance and Composition
7. Advanced Concepts
8. Object-Oriented Design Patterns
9. Object-Oriented Design Principles
- Mark as unwatched
- Mark all as unwatched
Are you sure you want to mark all the videos in this course as unwatched?
This will not affect your course history, your reports, or your certificates of completion for this course.Cancel
Take notes with your new membership!
Type in the entry box, then click Enter to save your note.
1:30Press on any video thumbnail to jump immediately to the timecode shown.
Notes are saved with you account but can also be exported as plain text, MS Word, PDF, Google Doc, or Evernote.