.

Tuesday, December 18, 2018

'Renaissance Choir Finance Management System\r'

'I exit be put one over a schema for the accounts of Renaissance sing. Renaissance Choir ar ground in Emsworth and acquit 29 members. They sing at many events throughout the year and some eons in Chichester Cathedral. They meet weekly.\r\nStatement of Problem\r\nRenaissance Choir require a form to manage their finances. It must(prenominal) be flexible and docile to use, so that anyone could inject along and use it, without previous knowledge.\r\nSchedule of Activities\r\n segmentation\r\nWeeks\r\nSpecification\r\n1.5\r\nImplementation\r\n3\r\nTesting\r\n1.5\r\n evaluation\r\n1\r\nUser Documentation\r\n1\r\n impart\r\n8\r\nBackground\r\nThe period ashes is ground on two books containing input and output for the choir. tout ensemble entries are written into the book by hand, and the books know to be carried to meetings when incumbent and this is not very convenient, and preferably slow. A computerised constitution would be more efficient. The carcass of rules ineluctably to deal with tiny gold, as a constant amount is usually kept as a float or for occasions where cash is call for and not a cheque or some other method of payment.\r\nOverview\r\nAs the scheme needs to contain columns of selective information, a spreadsheet would be most appropriate. I would use jump out, as I am sound acquainted with it and it has many useful features that I notify use to my advantage. My system would be composed of several(prenominal) sheets- a of import sheet with vents to chance upon between sheets, hence other sheets for data entryway, listing the entries and making interprets and pivot table reports. Each sheet would fork over a plainlyton to link back to the main menu, and to other relevant sheets. For instance the data entry screen would have a button to r separately(prenominal) the data into the spreadsheet, which would activate a macro and egg on the data. It would as well as have a button to move to the data-listing screen, w hich would have a button to link back. The graph page would have a button that would progress to a graph, and another to clear it. The exit button on the main screen may also clear the graph as well as exiting.\r\nInterview and Research Summary\r\nI gave a questionnaire to my end user, who filled it in. This has given me much range and other useful information, that can be apply to help produce the system.\r\nVolume of Data\r\nThe system pull up stakes be updated on a weekly basis, so it must be relatively easy to add, delete and change records, as it result be used so frequently. However, cheques need to be compensable in at random intervals, and the system will need to recalculate totals and other formulae after each of these events. It must also be able to fare with petty cash, which can fluctuate.\r\nProblems with the Current System\r\nProblems with the current system are its inability to transfer data intimately between the two books and the balance sheet, the positi on that it is slow and rather inefficient, due to having two jumbo(p) books to carry around.\r\nHardware Full Potential\r\nTo overprotect good performance from the system, the requirements would be:\r\n200 megahertz buttor speed\r\n16 MB wad\r\n16 Bit colour graphics or better\r\n computer software Full Potential\r\nThe features of Excel that I will use to create the system are: macros, buttons and controls, formulae, charts, pivot table reports, visual basic, conjugated namebooks and\r\nInput and Output\r\nThe user will draw in data every week. The volume of data drop offed will depend upon how many events were held in that calendar month, as each event will probably have inputs to the system in income and expense. 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.\r\nUser Skill Level\r\nMy end user is pretty skilled with computers, as she uses them in her work frequently. in that locationfore the system will not have to explain basic computer functions or other very basic ideas in the user guide, and the skillful guide can be pretty complicated.\r\nSoftware Use\r\nI will produce the system, but on the main page I will hide the gridlines. I may do this on other pages as well, so that unnecessary gridlines are not shown- if I want 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 like sorrowful between sheets and adding records.\r\nObjectives to Perform\r\nMy end user wants the system to be able to:\r\n* Hold both income and expenditure in one place\r\n* Cope with petty cash that is used for floats at events and other purposes\r\n* Be able to transfer data between sections easily\r\n* Produce graphs and charts of the data\r\n* Produce summaries of the data\r\n cognitive operation Indicators\r\n* essential be able to open relatively quickly, even on lower spec machines\r\n* Must be able to contain a large volume of data while still retaining a file size below 100 kilobytes\r\n* It must be relatively easy and quick to enter data or perform other operations\r\n* It must be relatively difficult to make mistakes while entering data (using drop-down lists, buttons, macros etc)\r\n* It must be easy to get to specific sections\r\n* It must be foolproof- e.g. impossible to alter critical system aspects\r\n* It must be possible to alter the structure of the database when necessary\r\n'

No comments:

Post a Comment