A use case diagram is drawn for an 11-module banking system. The Retail Institution and User actors interact with the M_Transaction module, which includes M_InsertCard and its extension M_InvalidCard. M_InsertCard is included in M_ATMTransaction, which also includes M_PinValidation and its extension M_InvalidPin. M_OnlineTransaction and M_ClientDesktopTransaction both include M_LogIn and M_LogOut, with M_InvalidLogIn extending M_LogIn. The BankDatabase actor interacts with M_Transaction, M_ATMTransaction, M_OnlineTransaction and M_ClientDesktopTransaction. The User actor interacts with M_ATMTransaction and M_Online

1. (Topic: Use Case Diagram)
Software Engineering
Faculty: Vinay Arora
Draw a neat and clean use case diagram for a banking system that constitutes eleven
modules in which all the functionality has been defined. Actor named Retail Institution
and User interact with M_Transaction. which includes M_InsertCard which is a base
module for extension use case M_InvalidCard. M_InsertCard is included under
M_ATMTransaction. Module M_PinValidation is also included under module
M_ATMTransaction. M_InvalidPin is an extension use case for module
M_PinValidation. Use case M_OnlineTransaction and M_ClientDesktopTransaction both
include two modules namely M_LogIn, M_LogOut. M_InvalidLogIn serve as an
extension use case for M_LogIn. Actor BankDatabase interact with M_Transaction,
M_ATMTransaction, M_OnlineTransaction and M_ClientDesktopTransaction. Actor
User interact with M_ATMTransaction as well as M_OnlineTransaction. Actor User is a
generalization for actors WebMerchant and BankEmployee. BankEmployee interacts with
M_ClientDesktopTransaction. (prefix M_ refers to module name / use case name)