|
From: Ben <ct...@co...> - 2001-11-16 22:09:36
|
Here are the the initial requirements for 0.1 . Im not sure if they had
to be presented in a specific way, but if so feel free to tidy them up and
we can stick to a standard in future documents. We will also have to
discuss using the feature request etc available on the sourceforge
website-
Rgds,
ben
MOSPFT: Version 0.1 requirements
Last updated November 16th!
We need to represent:
- Checking accounts
- Savings accounts
- Credit cards
- Loans & other debtors
- Other receivers / ie family/friends
- Creditors - ie Employer
The ability to:
- Manually enter transactions
- Transfer money between accounts
- Schedule regular money transfers
- Log all transactions to maintain audit trail
- See basic summary statistics
UI at 0.1:
- Multiple window approach (cf Forte)
- User explorer - shows all elements
- HTML/PhP frontend
Tree Control example: // A change in this updates HTML accordingly
+ Accounts
+ Citibank Checking
+ Barclays Savings
+ Incoming
+ Employer
+ Outgoing
+ Barclays Credit Card
+ Car Loan // Expansion to other things which might not be
implemented yet
+ Details
+ Reporting
Considerations:
Need to think about user authentication at later stages. May have
implications for design at early stage,
When completing a transfer this could be into a new entity, ie a
stock purchase.
Need to decide on the main point of interaction. Will things such as
setting up a new loan
or changing payment details occur through HTML or in program. Maybe HTML
should just be used for displaying data??
--
Ben Wootton
ct...@co...
|