Evaluation for Exhibition Guest List Management System
Based upon the system that I’ve recently created, I think that the database is very professional and carries out all requirements that the university stated. The forms that I created throughout the system allow for all relevant details to be recorded, and with the reports structured on the queries created earlier, the report documents are very professional. Overall, I am very happy with the quality of the system, and I think the database is easily capable of carrying out all the tasks that the university needs the system to achieve. I think I could have potentially created some additional features in my system though, such as advanced reports or even macros to search for information within the system. Despite this, I think I used Access to its best capabilities it offers.
The Rapid Development method that I chose to use was the right choice in my personal opinion, due to the fact that I could keep adding new features as the versions increased. My rapid development method of prototyping allowed me to constantly keep looking back at my database and see which features I would need to add in order to make the next version of the system, better than the last. I possibly think in the future I might have tried using the Phased strategy for creating my work, as this would have resulted in a lower risk of errors being found in later versions.
Personally, I think that Microsoft Access was the best application to use for creating this system, due to the number of queries I knew I had to create, I instantly knew Microsoft Access would be the best application to use. Similarly, a high quality user-interface was needed, with access to multiple reports, both of which Microsoft Access can provide to a high standard. Prior to starting the database creation, I knew Microsoft Access provided high quality reports, and due to reports being one of the required elements in the document from the university, I knew I could easily meet the administrator's needs. I would have liked to have had some of the features that Zoho Creator and DabbleDB contain, such as the graph and chart features which could have represented the number of guests attending a particular event. I wouldn’t have benefitted from the coding available though, hence why I chose not to use these applications.
Friday 14 May 2010
Evaluation for Books Order System
Now that I have completed the system, I think that the database is professional and allows the school to complete all the tasks that they need to do in order to produce orders for books. The forms that I’ve created meet a very high standard, as they allow for all relevant data to be entered through various easy methods, text boxes or combo (look-up) boxes, and also provide a consistent colour scheme, supported by the reports. I would have liked to advance my system, by potentially inserting some macros or passwords, to assist with the security of the database. I would've liked to advance on the colour scheme, as most of the colours used are one solid colour – blends might help the professionalism of the database to increase.
The Rapid Development Method of prototyping that I used was definitely the right choice in my opinion, for this type of database, as I could start with a system that literally contained the bare minimum of features, but constantly keep adding new features in later versions. This allowed me to easily track the progress of my database, and due to the Functional Specification I created, allowed the system to be constructed very quickly. Despite the Prototyping approach been the right option for me, I would’ve liked to experiment with Phased approach, as this would have resulted in errors been erased. An example of an error that occurred in my system was a button that I assigned with the wrong feature (Last Record in Order Form) – this error wasn’t noticed until the third version was released.
Personally, I think that Microsoft Access was the best application to use, due to the number of forms and reports that were needed. These could be easily constructed in Microsoft Access due to the query feature available. I also needed to produce a high quality user-interface for the financial administrator to use, therefore ensuring the interface was professional was a major goal to me. I knew that before construction of the system began, Microsoft Access produced high quality reports and reports were stated as a major requirement in the ICA document. Potentially, Zoho Creator maps, graphs and charts features could have been useful, as these could have shown the money each teacher had spent each year. Despite this, the coding would have proved difficult to assign to this database.
Now that I have completed the system, I think that the database is professional and allows the school to complete all the tasks that they need to do in order to produce orders for books. The forms that I’ve created meet a very high standard, as they allow for all relevant data to be entered through various easy methods, text boxes or combo (look-up) boxes, and also provide a consistent colour scheme, supported by the reports. I would have liked to advance my system, by potentially inserting some macros or passwords, to assist with the security of the database. I would've liked to advance on the colour scheme, as most of the colours used are one solid colour – blends might help the professionalism of the database to increase.
The Rapid Development Method of prototyping that I used was definitely the right choice in my opinion, for this type of database, as I could start with a system that literally contained the bare minimum of features, but constantly keep adding new features in later versions. This allowed me to easily track the progress of my database, and due to the Functional Specification I created, allowed the system to be constructed very quickly. Despite the Prototyping approach been the right option for me, I would’ve liked to experiment with Phased approach, as this would have resulted in errors been erased. An example of an error that occurred in my system was a button that I assigned with the wrong feature (Last Record in Order Form) – this error wasn’t noticed until the third version was released.
Personally, I think that Microsoft Access was the best application to use, due to the number of forms and reports that were needed. These could be easily constructed in Microsoft Access due to the query feature available. I also needed to produce a high quality user-interface for the financial administrator to use, therefore ensuring the interface was professional was a major goal to me. I knew that before construction of the system began, Microsoft Access produced high quality reports and reports were stated as a major requirement in the ICA document. Potentially, Zoho Creator maps, graphs and charts features could have been useful, as these could have shown the money each teacher had spent each year. Despite this, the coding would have proved difficult to assign to this database.
Subscribe to:
Posts (Atom)