1) User registration as mobile baking services
2) Basic authentication: log-in, log-out
3) View user’s bank accounts
4) Transfer money
5) Alert (Add/delete/check)
User can be classified based on trader Type; Casual Trader, Frequent Trader, and Day Trader
Casual Trader may have no fixed data plan but pay for Data packets and use several times usage per month. Frequent Trader can have unlimited data plan, need ticker's information. Day Trader can have unlimited data plan, need ticker's information and daily trading transaction service.Trader can be enhanced by defining trader Type and its transaction fee.
Account can be categorized billing account for bill payment service, bank account such as savings and check account and stock account for stock trading.
Alert can be enhanced by defining Alert Method such as SMS, RSS, and Email.
Posts
2 comments:
Hi Sophie
I am lecturer in SE in Leiden in The Netherlands. I like your UML model for mobile banking. Do you also have source code for it? We are collecting such combinations (model + code) for our research.
(chaudron@liacs.nl)
Oh I do have ...but I would recommend to refer to IBM's Banking (finance ) component model, which is more close to CBD approach. mine is analysis model, which cannot cover all functions what finance model should provide.
Post a Comment