YMCA Account Manager

Title: YMCA Account Manager Objective: The essence of this application is to model the financial dynamism of an association. The financial dynamism shall include among others: (i) the budget of the association (ii) individual contributions of the members of the association (iii) all sources of income to the association (iv) expenses made by the association (v) Daily/Weekly/Monthly financial position of the association Functional requirements (the expected functionality/capability of the system) 1. The system shall capture the profile details of individual members of the association such as (i) membership id (ii) first and last names (iii) any other membership details to be captured can be added at anytime 2. The system shall capture the different income headings(such as Registration Fee, Monthly dues, Welfare Levy, Outstanding debts, Social Function Levy, Annual anniversary Donation, Freewill donation, etc) of the association (this should be configurable as all the income headings may not be known at any point in time) 3. The system shall capture the individual contributions of the members of the association under different income headings 4. The system shall capture the different expenses headings (Annual Membership dues to N/O, Admin Charges for national affiliation, Anniversary Expenses, Refreshments at monthly GM’s, Outreach support, End of year get together, Bank Charges, Administrative Expenses, Members Welfare Expenses, Evangelism Support, etc) of the association (this should be configurable as all the expenses headings may not be known at any point in time) 5. The system shall capture the position of the bank balances of the association. Non Functional Requirements (specifies criteria that can be used to judge the operation of a system, rather than specific behaviours) The following are the expected non-functional requirements of the application. (i)The system shall be platform independent (ii) the system shall have audit trail (iii) the system shall have administrator and user roles, the administrator create the users under different roles) (iv) the system shall be a standalone system Report Requirements Would generate report of (i)individual member contributions (ii)individual expenses reports (iii)summary income headings reports (iv)summary expenses headings reports (v) Daily/Weekly/Monthly financial position of the association Note: the report can be exported to a spread sheet application such as Microsoft Excel for further analysis. Other Requirements (i) A comprehensive technical and user manual of the application shall be provided (ii) The source code and the packaged application shall be made available