When defining a use case, you must first consider the potential actor. An actor is the third-party that will interact with your program. Identifying the actors allows you to create scenarios surrounding specific use cases. Learning how to identify the most common actors for your program can help you find potential problems before finishing development. Watch this online video to learn about the different types of actors and potential use scenarios while programming.
- View Offline
An Actor in a use case is anything with behavior who lives outside of your…system, outside of your application, but has a goal they want to accomplish within.…And these are usually human beings, but not always.…Now sometimes coming up with the actor is very straightforward.…If you're building a Calculator App for a mobile device or a simple one person…game, you may just have one actor, someone who uses the application, the user.…However, if you were building, say, a backend internal Payroll Application, you…might have multiple people that do very different goals within such as the…payroll administrator, or a manager, or an employee, and you also need to…interact with other computer systems.…
Perhaps this application will send data to an external system or it needs to…interact with another corporate system.…Well, these would be considered actors too.…They're external to your application, but they need to interact with it.…So it's usual to spend a few minutes brainstorming the main actors, and we can…actually start with one easy question.…
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