Scribd
Upload
66 views4 pages

CRC Card Model

The CRC card model represents the relationships between classes in a ticket vending machine system. The main ticketVendingMachine_iGo class allows users to reload their iGo cards or purchase tickets. The system first authenticates users and verifies their credentials before allowing them to recharge their cards or purchase day, weekly, or monthly passes. It then connects to a database storing user information and transaction details are stored in the userTransaction class.

Uploaded by

17itkhushali.parmar
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
66 views4 pages

CRC Card Model

The CRC card model represents the relationships between classes in a ticket vending machine system. The main ticketVendingMachine_iGo class allows users to reload their iGo cards or purchase tickets. The system first authenticates users and verifies their credentials before allowing them to recharge their cards or purchase day, weekly, or monthly passes. It then connects to a database storing user information and transaction details are stored in the userTransaction class.

Uploaded by

17itkhushali.parmar
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 4

CRC card model

The relationship between all of CRC card classes is represented by the CRC model. The
main class, ticketVendingMachine_iGo, allows users to choose between reloading their
iGo card or purchasing a ticket.
The system begins by verifying the users’ information and authenticity if they are using
their own iGo card. Then they can recharge their cards using any of the available fare
options (debit or credit card), see their transaction history, and schedule regular payments
in opusRecharge class. After that, the system connects to the database to check the users’
credentials. All the opus-related information on every opus card has been saved in the
database. Then the transaction is done based on the user's credentials and stores in details
in userTransaction class. The system will issue a receipt for the user after a successful
transaction and then shut down.
If users want to purchase a ticket, they can choose between Day Pass, Weekly Pass, and
Monthly Pass in Fare class after validation is done. Then go for a payment, which provides
a payment gateway for the users to pay through debit or credit card. For this, the system
opens a third-party payment gateway and then generates the payment receipt for the user
if asked for it.
ticketVendingMachine_iGo

iGoRecharge ticketPurchase

userAuthentication Fare

userInformation Payment

Credentials userTransaction paymentGateway


ticketVendingMachine_iGo

Ticket Purchase userAuthentication


OPUS Recharge opusRecharge
ticketPurchase

userAuthentication

Verify the user's OPUS credentials Credentials

opusRecharge

Allows the user to recharge their cards instantly using any of the available Fair
fair options Payment
Allows the users to see their transaction history Credentials
Allows the user to schedule regular payments userTransaction

ticketPurchase

Provides users with different fair options (Like Day Pass, Week Pass, Fair
Monthly Pass) Payment
Allows them to pay based on their selection

Credentials

A database having all the OPUS-related information of every OPUS card


holder.
Fair

Stores all fair details (Day Pass, Weekly Pass and Monthly Pass)

Payment

Provides payment gateway for the users to pay through debit/credit card paymentGateway
Generates the payment receipt for the user if asked for.

paymentGateway

Opens 3rd party payment gateway.

userTransaction

Stores all the transaction details of each user based on their OPUS details Credentials

You might also like