How to design a system for a bank?
The company I work for is about to design a system for a bank. This system will be used by office clerks to help their daily works. For example they can handle bank accounts, credit cards, credit products, loans, client data, stuffs like this. It's a kind of accountant system.
As I don't want to reinvent the wheel I'm sure there are several solutions for this problem. Patterns, case studies, books, real life stories. I'm looking for them.
Would you be so kind to recommend something I can use?
[520 byte] By [
Alex76a] at [2007-10-3 9:45:01]
> The company I work for is about to design a system
> for a bank. This system will be used by office clerks
> to help their daily works. For example they can
> handle bank accounts, credit cards, credit products,
> loans, client data, stuffs like this. It's a kind of
> accountant system.
I don't know how big a company you're talking about. I'd look into ERP systems like SAP, Oracle/PeopleSoft, Great Plains, etc.
> As I don't want to reinvent the wheel I'm sure there
> are several solutions for this problem. Patterns,
> case studies, books, real life stories. I'm looking
> for them.
If you're really smart you'll look for a package to buy before you try to write one.
> Would you be so kind to recommend something I can use?
http://www.google.com/search?q=java+banking+software&ie=utf-8&oe=utf-8&rls=org.mozilla:en-US:official&client=firefox-a
%
> I don't know how big a company you're talking about.
> I'd look into ERP systems like SAP,
> Oracle/PeopleSoft, Great Plains, etc.
The task is to implement a system with which we can help the for of the office clerks. So we don't have to implement a whole accountancy system from the beginning to the end we just have to implement some kind of frontend and services for the frontend. These services will be used by the frontend and will be connected to the accountancy system of the company ( legacy app written in Cobol ).
So I need some books, strategies, etc on how to implement, architect a tipical banking app. E.g. What does account (, banking products, loans ) really mean? What kind of tipical patterns should I use?
I've browsed the web, of course, and I have found "Enterprise Integration Patterns: Designing, Building, and Deploying Messaging Solutions" for example but I'm not sure this is the thing I need. I've found Martin Fowler: Analysis patterns ( closer to what I need, so I've bought it already ). For example that one has a lots of patterns I should use ( Account, Transaction, Accounting Practice ).
So I'm looking for something similar to the book "Analysis patterns" but with more with strategies and practical information on design and architectures as well.
