Its scary that there have been several "How do I build a banking website" question asked by obvious novices on here. Hopefully that's not a reflection of the state of the security of online banking :P
–
micmcgJul 6 '09 at 1:57

At least my bank in the UK seems to take security seriously, so things probably aren't that bad. Maybe they're all opening these banks in Nigeria ;-)
–
quant_devJul 6 '09 at 20:13

@micmcg - I would suspect a school assignment has come up, but maybe that's just my cynicism ;)
–
Mark MayoSep 21 '09 at 13:42

2 Answers
2

Your domain expert should provide a specific definition of what's required. There are way too many variables for you to determine this, and (with respect) you're not the person to make this decision.

e.g. how do you report rates ? How do you report when they're applied ? Can you make withdrawals immediately etc. These are all attributes and behaviours related to the savings account and should manifest themselves in some fashion on the front-end.

Also add privacy concerns on who can access financial data. Any SEC laws since this is a financial institution. Reliability assurance so that when a person transfers $100 to an account it actually works. This is why he needs a domain expert.
–
Cody CJul 5 '09 at 15:02

These things shouldn't be a part of the website code.
–
quant_devJul 5 '09 at 15:02