din-din - Project Hosting on Google Code

Earlier this year Feb 16, 2009 issue 9 (Add a Category field to the deposit transaction) Blocked on changed by monoman - Feb 16, 2009 issue 10 (Report- transaction history for an account) Labels changed by monoman - Completing acceptance test: ... shows the transactions as specified. Also validation tests for the range of dates should be ensued. Clarifying: future dates are allowed, but show only available data like future transactions applied over current balances Labels: Milestone-Iteration01 Points-Estimated04 −Milestone-IterationXX Completing acceptance test: ... shows the transactions as specified. Also validation tests for the range of dates should be ensued. Clarifying: future dates are allowed, but show only available data like future transactions applied over current balances Labels: Milestone-Iteration01 Points-Estimated04 −Milestone-IterationXX Feb 16, 2009 issue 10 (Report- transaction history for an account) reported by monoman - select an account, click for the report. Asks the period (start and end date) defaults to current month, if after the second day, or the previous month and the current, otherwise. end date must be greater or equal to the start one. Both fields are mandatory lists date, description, category and amount with sign (negative for expensea), ordered by date, category. Initial and final balance for the account, and its identification also should be shown as the report header. Acceptance Test: after selecting dates over a period that transactions where recorded select an account, click for the report. Asks the period (start and end date) defaults to current month, if after the second day, or the previous month and the current, otherwise. end date must be greater or equal to the start one. Both fields are mandatory lists date, description, category and amount with sign (negative for expensea), ordered by date, category. Initial and final balance for the account, and its identification also should be shown as the report header. Acceptance Test: after selecting dates over a period that transactions where recorded Feb 16, 2009 issue 9 (Add a Category field to the deposit transaction) reported by monoman - Just add a category field (and auto-growing list) mandatory Acceptance Test: field should not filled and validation message shown, after filling it and the other needed ones, the transaction should be correctly persisted Just add a category field (and auto-growing list) mandatory Acceptance Test: field should not filled and validation message shown, after filling it and the other needed ones, the transaction should be correctly persisted Feb 16, 2009 issue 8 (Permit a Expense Transaction) Labels changed by monoman - Labels: Points-Estimated04 Labels: Points-Estimated04 Feb 16, 2009 issue 8 (Permit a Expense Transaction) reported by monoman - after selecting an account allow to enter Amount (mandatory) Date (mandatory - pre filled with current date/time) Means (mandatory - Account defines its means like: Check/Debit Card and the default one which comes pre filled) Merchant (optional - auto-growing list) Category (mandatory - auto-growing list) Description (optional - may be a large text) Acceptance Test: Select an account, fill the data partially to see that all validation is made and saving is not allowed, fill completely and be enabled to save, and after that the final balance for the account is decremented correctly if date is past, final balance can be negative. If date is future, the balance will be affected only at the end of the day the date points. after selecting an account allow to enter Amount (mandatory) Date (mandatory - pre filled with current date/time) Means (mandatory - Account defines its means like: Check/Debit Card and the default one which comes pre filled) Merchant (optional - auto-growing list) Category (mandatory - auto-growing list) Description (optional - may be a large text) Acceptance Test: Select an account, fill the data partially to see that all validation is made and saving is not allowed, fill completely and be enabled to save, and after that the final balance for the account is decremented correctly if date is past, final balance can be negative. If date is future, the balance will be affected only at the end of the day the date points. Jan 23, 2009 r10 (Ignoring temporary files from MonoDevelop) committed by monoman - Ignoring temporary files from MonoDevelop Ignoring temporary files from MonoDevelop Jan 21, 2009 r9 (Issue 6 - Work started - failed at TDD again) committed by monoman - Issue 6 - Work started - failed at TDD again Issue 6 - Work started - failed at TDD again Jan 21, 2009 issue 6 (User Story: Viewing account information including final/curr...) Status changed by monoman - Status: Started Status: Started Jan 21, 2009 issue 6 (User Story: Viewing account information including final/curr...) Labels changed by monoman - Raising the priority Labels: Priority-Critical −Priority-High Raising the priority Labels: Priority-Critical −Priority-High Jan 21, 2009 issue 6 (User Story: Viewing account information including final/curr...) Labels changed by monoman - Labels: Milestone-Iteration01 −Milestone-IterationXX Labels: Milestone-Iteration01 −Milestone-IterationXX Jan 21, 2009 issue 6 (User Story: Viewing account information including final/curr...) reported by monoman - For each account it should be possible to view a page of information with identification data, and the current balance for the account Acceptance Test: Enter application select the account tab and see the data. (current thinking is that tabbing is easier in the user than selecting an account from a menu or list and open up a popup or document window. For each account it should be possible to view a page of information with identification data, and the current balance for the account Acceptance Test: Enter application select the account tab and see the data. (current thinking is that tabbing is easier in the user than selecting an account from a menu or list and open up a popup or document window. Jan 21, 2009 issue 5 (User Story: Permit a deposit transaction) commented on by monoman - Clarifying: This should be expanded and then split so that a new story covers showing account data (including the final or current balance, so that this story could become verifiable) Clarifying: This should be expanded and then split so that a new story covers showing account data (including the final or current balance, so that this story could become verifiable) Jan 21, 2009 issue 3 (User Story: Create omnipotent main user on first usage) Labels changed by monoman - Estimating story Labels: Points-Estimated01 Estimating story Labels: Points-Estimated01 Jan 21, 2009 issue 2 (User Story: Demand user identification to access the system ...) Labels changed by monoman - Estimating story Labels: Points-Estimated02 Estimating story Labels: Points-Estimated02 Jan 21, 2009 issue 4 (User Story: Add a bank deposit account with initial balance) Labels changed by monoman - Assuming velocity of 5 points per week - Points consumed = 4 Labels: Points-Estimated03 Assuming velocity of 5 points per week - Points consumed = 4 Labels: Points-Estimated03 Jan 21, 2009 issue 5 (User Story: Permit a deposit transaction) Labels changed by monoman - Labels: Points-Estimated04 Labels: Points-Estimated04 Jan 19, 2009 r8 (Reorganizing things a bit) committed by monoman - Reorganizing things a bit Reorganizing things a bit Jan 18, 2009 r7 (Creating MonoDevelop aolution fle, ND Mking it compile and r...) committed by monoman - Creating MonoDevelop aolution fle, ND Mking it compile and run on Linux Creating MonoDevelop aolution fle, ND Mking it compile and run on Linux Jan 15, 2009 issue 4 (User Story: Add a bank deposit account with initial balance) Status changed by monoman - Status: Fixed Status: Fixed Jan 15, 2009 r6 (Issue 4:Done - but acceptance test is fragile) committed by monoman - Issue 4 :Done - but acceptance test is fragile Issue 4 :Done - but acceptance test is fragile Jan 15, 2009 r5 (More work on issue 4:Mainly done, except that data isn't per...) committed by monoman - More work on issue 4 :Mainly done, except that data isn't persisted and vanishes when leaving the program. No full TDD, some classes where coded without prior unit tests existing More work on issue 4 :Mainly done, except that data isn't persisted and vanishes when leaving the program. No full TDD, some classes where coded without prior unit tests existing Jan 14, 2009 r4 (More work on issue 4:Doesn't compile, but internet is going ...) committed by monoman - More work on issue 4 :Doesn't compile, but internet is going away so be it More work on issue 4 :Doesn't compile, but internet is going away so be it Jan 13, 2009 issue 5 (User Story: Permit a deposit transaction) Status changed by monoman - Clarification: Accounts can be of varying types and some may not accept deposits (like Credit Card, which allow debt payment but not deposits) Status: Accepted Clarification: Accounts can be of varying types and some may not accept deposits (like Credit Card, which allow debt payment but not deposits) Status: Accepted Jan 13, 2009 issue 2 (User Story: Demand user identification to access the system ...) Labels changed by monoman - Labels: Type-UserStory Milestone-Iteration01 −Type-Enhancement Labels: Type-UserStory Milestone-Iteration01 −Type-Enhancement Jan 13, 2009 issue 3 (User Story: Create omnipotent main user on first usage) Labels changed by monoman - Labels: Type-UserStory Milestone-Iteration01 −Type-Enhancement Labels: Type-UserStory Milestone-Iteration01 −Type-Enhancement Jan 13, 2009 issue 4 (User Story: Add a bank deposit account with initial balance) Labels changed by monoman - Labels: Type-UserStory Milestone-Iteration01 −Type-Enhancement Labels: Type-UserStory Milestone-Iteration01 −Type-Enhancement Jan 13, 2009 issue 5 (User Story: Permit a deposit transaction) reported by monoman - Permit that a deposit transaction be registered for an existing deposit account. Data is: * = mandatory Value* (strictly positive [>0]) Description DateTime* (auto) Acceptance Test: For an existing account enter transaction data and if validated as above, record it, account final balance should change to previous balance + Value. Permit that a deposit transaction be registered for an existing deposit account. Data is: * = mandatory Value* (strictly positive [>0]) Description DateTime* (auto) Acceptance Test: For an existing account enter transaction data and if validated as above, record it, account final balance should change to previous balance + Value. Jan 13, 2009 r3 (Issue #4 - Progressing implementation Service layer added - ...) committed by monoman - Issue #4 - Progressing implementation Service layer added - core tests all green with handwritten mock repository Issue #4 - Progressing implementation Service layer added - core tests all green with handwritten mock repository Jan 13, 2009 issue 4 (User Story: Add a bank deposit account with initial balance) changed by monoman - Summary: User Story: Add a bank deposit account with initial balance Status: Started Summary: User Story: Add a bank deposit account with initial balance Status: Started Jan 13, 2009 issue 4 (User Story: Add a bank deposit account with balance) reported by monoman - Form to add a bank deposit account = mandatory shortname (unique) name* bank name bank agency id* bank account id* currency* (default = current culture currency) initial balance* date of creation* (auto) Acceptance test: Should be able to add account, validating fields as above. Form to add a bank deposit account = mandatory shortname (unique) name* bank name bank agency id* bank account id* currency* (default = current culture currency) initial balance* date of creation* (auto) Acceptance test: Should be able to add account, validating fields as above. Jan 13, 2009 issue 3 (User Story: Create omnipotent main user on first usage) reported by monoman - On first usage the the system should ask a name and password for the main user of the system, which will be the first one in the known users list. Acceptance test: freshly install and run the app, and it should demand an username and password, both non-empty and the password with a minimal length of 5, looping until correctly filled or the application entry is cancelled. Exiting and reentering should not ask for creation again. On first usage the the system should ask a name and password for the main user of the system, which will be the first one in the known users list. Acceptance test: freshly install and run the app, and it should demand an username and password, both non-empty and the password with a minimal length of 5, looping until correctly filled or the application entry is cancelled. Exiting and reentering should not ask for creation again. Jan 13, 2009 issue 2 (User Story: Demand user identification to access the system ...) reported by monoman - The system must identify the user (Authenticate) before allowing access to the data and features. Acceptance test: On entering the system it must query username and password and reject unknown users or wrong passwords. Desktop application only for now. The system must identify the user (Authenticate) before allowing access to the data and features. Acceptance test: On entering the system it must query username and password and reject unknown users or wrong passwords. Desktop application only for now. Jan 13, 2009 issue 1 (Multplatform --> Multiplatform) Status changed by monoman - Thanks Status: Fixed Thanks Status: Fixed Jan 10, 2009 issue 1 (Multplatform --> Multiplatform) reported by rockpiper - The din-din tagline ATM reads: “Multplatform Home Finance Distributed System”—you may want to fix the spelling. Cheers! The din-din tagline ATM reads: “Multplatform Home Finance Distributed System”—you may want to fix the spelling. Cheers! Jan 09, 2009 r2 (First Commit, the License file) committed by monoman - First Commit, the License file First Commit, the License file Jan 09, 2009 Project din-din created by monoman - Multplatform Home Finance Distributed System Multplatform Home Finance Distributed System

issue 8 (Permit a Expense Transaction) reported by monoman - after selecting an account allow to enter Amount (mandatory) Date (mandatory - pre filled with current date/time) Means (mandatory - Account defines its means like: Check/Debit Card and the default one which comes pre filled) Merchant (optional - auto-growing list) Category (mandatory - auto-growing list) Description (optional - may be a large text) Acceptance Test: Select an account, fill the data partially to see that all validation is made and saving is not allowed, fill completely and be enabled to save, and after that the final balance for the account is decremented correctly if date is past, final balance can be negative. If date is future, the balance will be affected only at the end of the day the date points.

after selecting an account allow to enter Amount (mandatory) Date (mandatory - pre filled with current date/time) Means (mandatory - Account defines its means like: Check/Debit Card and the default one which comes pre filled) Merchant (optional - auto-growing list) Category (mandatory - auto-growing list) Description (optional - may be a large text) Acceptance Test: Select an account, fill the data partially to see that all validation is made and saving is not allowed, fill completely and be enabled to save, and after that the final balance for the account is decremented correctly if date is past, final balance can be negative. If date is future, the balance will be affected only at the end of the day the date points.

Earlier this year