2.2 – Data Storage
Furthermore, the need for storage space will not be required within this event driven programme, additionally, the user will be able to use the calculator to gain an estimated quote, however there will not be a need for the company, “Kris Arts” to store the data for future reference, seeing as the event driven programme is only an estimation
2.3 – Action/Event Table
2.4 – Data Dictionary
2.5 – Design Review
I had to create an event driven application for the company “Kris Arts Media”, in order for them to be able to have a working calculator that provides their customers with a brief estimation on how much the cost will be to print out certain broachers. Additionally, the application that I produced and designed met this criterion, and managed to calculate the cost of pages, printing type, printing paper, graphic type and the PDF format cost, easily within just a few clicks. In addition, my event driven application has a formal design, allowing the application to be well presented to its users.
What I would do differently if I had more time would be that I would change the layout of my event driven application, allowing for more space for the cost to be shown on the actual event driven application in the format of currency, whilst the user makes a selection through each variable. This is mainly because I know that it would have been easier and presented well, instead of just having a new window pop up giving the customer the total price of their selection. Therefore that would be the main thing that I would change on my event driven application.
In conclusion, I do believe that my event driven application meets the desired requirements and purpose of those that the “Kris Arts Media” wanted me to perform. Additionally, this is mainly because I have created a working printing calculator which calculates an estimated cost of each selection that the user inputs. Therefore showing that I have successfully created a working event driven application.
