Renaissance Choir Finance Management System

I leave be fashioning a transcription for the accounts of spiritual rebirth Choir. Renaissance Choir are establish in Emsworth and go 29 members. They sing at many solutions passim the year and sometimes in Chichester Cathedral. They meet weekly.Statement of ProblemRenaissance Choir require a system to manage their finances. It essential be flexible and thriving to use, so that anyone could come along and use it, without preceding knowledge.Schedule of ActivitiesSectionWeeksSpecification1.5Implementation3Testing1.5 valuation1User Documentation1Total8 permeate backgroundThe current system is based on two books take ining input and outfit for the choir. All entries are written into the book by hand, and the books have to be carried to meetings when obligatory and this is not very convenient, and rather slow. A selective information processorised system would be more efficient. The system needs to deal with small cash, as a constant amount is usually kept as a ice-cream float or for occasions where cash is needed and not a draw or new(prenominal) method of payment.OverviewAs the system needs to contain columns of info, a spreadsheet would be most appropriate. I would use Excel, as I am well acquainted with it and it has many useful features that I gutter use to my advantage. My system would be composed of several sheets- a main sheet with buttons to move between sheets, then other sheets for data entry, leaning the entries and making graphs and pivot table reports. Each sheet would have a button to touch base back to the main menu, and to other relevant sheets. For spokesperson the data entry screen would have a button to hold the data into the spreadsheet, which would activate a macro and move the data. It would also have a button to move to the data-listing screen, which would have a button to link back. The graph page would have a button that would create a graph, and another to clear it. The exit button on the main screen may also cl ear the graph as well as exiting.Interview and Research SummaryI gave a questionnaire to my subvert user, who modify it in. This has given me much background and other useful information, that can be used to help form the system.Volume of DataThe system will be updated on a weekly basis, so it must be relatively easy to add, delete and change records, as it will be used so frequently. However, cheques need to be paid in at random intervals, and the system will need to recalculate totals and other formulae later on each of these events. It must also be able to cope with petty cash, which can fluctuate.Problems with the Current SystemProblems with the current system are its unfitness to transfer data easily between the two books and the balance sheet, the detail that it is slow and rather inefficient, due to having two heavy books to carry around. hardware upright PotentialTo get good performance from the system, the requirements would becc MHz processor speed16 MB Ram16 Bit col our graphics or betterSoftware Full PotentialThe features of Excel that I will use to create the system are macros, buttons and controls, formulae, charts, pivot table reports, visual basic, linked workbooks andInput and productionThe user will enter data every week. The volume of data entered will dep complete upon how many events were held in that month, as each event will probably have inputs to the system in income and expenditure. At the end of each month and at the end of the year, the data will be summarised and the summary probably printed. Also, the system will process the lists of data to produce sub-totals and totals over different time spans.User Skill LevelMy end user is pretty skilled with computers, as she uses them in her work frequently. thence the system will not have to explain basic computer functions or other very basic ideas in the user guide, and the expert guide can be pretty complicated.Software UseI will produce the system, but on the main page I will hi de the gridlines. I may do this on other pages as well, so that unnecessary gridlines are not shown- if I deficiency gridlines to be shown, then borders can be put around required cells where tables are required. Also, anything that shouldnt be altered (e.g. integral system parts) will be protected to prevent alteration. There will be macros to do things comparable moving between sheets and adding records.Objectives to PerformMy end user wants the system to be able to* Hold both income and expenditure in one rig* Cope with petty cash that is used for floats at events and other purposes* Be able to transfer data between sections easily* Produce graphs and charts of the data* Produce summaries of the dataPerformance Indicators* Must be able to contribute relatively quickly, even on lower spec machines* Must be able to contain a large volume of data objet dart still retaining a file size below 100 kilobytes* It must be relatively easy and quick to enter data or perform other opera tions* It must be relatively surd to make mistakes while entering data (using drop-down lists, buttons, macros etc)* It must be easy to get to specific sections* It must be foolproof- e.g. impossible to alter sarcastic system aspects* It must be possible to alter the structure of the database when necessary