Modeling and Diagrams Quiz

An actor is a role that a user can play, such as instructor, advisor, or student. Actors do not have to be human and are always outside of the system boundary.

Use cases are actions on a system initiated by an actor. They represent the main tasks performed by each actor and the complete functionality of a task.

Use case modeling helps uncover requirements in a way that clients find easy to understand. It describes who uses the system and what they use it for.

Example: Actor - Customer, Use Case - Withdrawal. The customer interacts with the system to perform the task of withdrawing cash.

A use case model represents the complete functionality of tasks performed by each actor. It shows how different users interact with the system.

In the UCC registration system, an actor could be a student, an instructor, or an administrator. These are external entities that interact with the system.

The main actors are: 1) Customer - can check balance, deposit, withdraw, transfer money. 2) Bank staff - can do all customer actions plus adding money and paper, repair the ATM.

A use case diagram models the different use cases or functionalities of a system and the actors that interact with those use cases.

Use cases can be composed of smaller sub use cases. For example, the 'ordering a meal' use case may be part of a larger 'buying a meal' use case that also includes payment and delivery.

Some potential use cases are: check balance, deposit cash, withdraw cash, transfer funds between accounts.

The key actors are: Registration officers, Students, Faculty officers, Registration staff, Accounts staff, Hall porters.

The relationships are shown using lines connecting the actors to the use cases they interact with. Different line styles may represent different types of relationships.

The key actors in an ATM system are: 1) Customer, 2) Bank, 3) ATM machine. Their roles are: Customer - withdraws/deposits cash, checks balance; Bank - maintains customer accounts, authorizes transactions; ATM - interface for customer transactions.

A use case diagram provides an external perspective of the system, showing the interactions between the system and its environment (actors). It models the functional requirements of the system by depicting the key use cases and actors.

Use cases can be composed through generalization (inheritance), inclusion (one use case including another's behavior), and extension (extending a use case with additional behavior). This allows for reuse and better organization of use cases.

A key use case in an ATM system is 'Withdraw Cash' where the customer inserts their card, enters PIN, selects withdraw amount, takes cash dispensed, and gets card returned.

A use case model for the UCC registration system could include actors like Student, Lecturer, Administrator and use cases like Register Courses, Enroll Student, Assign Courses, Generate Transcript etc. showing how different users interact with the system.

The key UML diagram types for system modeling are: Use case diagrams (external perspective), Activity/Data flow diagrams (behavioral perspective), Class diagrams (structural perspective), Sequence/Communication diagrams (interaction perspective).