DESIGN
DOCUMENTATION
Unit 14 Event Driven Programming
ELIOT HUNTER
Sunderland College
,Eliot Hunter (ID: 16002495) Assignment A Unit 14 Event Driven Programming
Design Documentation
User Requirements
These are the user requirements for the Especially for You program:
1. The car chosen, colour and how long for. The customer should be able to choose from four
categories of cars (wedding, classic, off-road, and sports.) The customer should also have the
option to be able to choose the colour that the car should come in (blue, dark green, dark
red, red, silver, and white.) The customer should lastly be able to choose when they can pick
the car from Especially for You and when to drop the car off again when the hire period ends.
2. Add any extras (service) that the customer wants. The customer should be able to choose
between 3 services (gold, silver, and bronze.) The gold service comes with champagne and a
chauffeur, the silver service comes with a chauffeur and the bronze service comes with
nothing. The 3 prices of the services are (gold – 50% added to price, silver – 30% added to
price, and bronze – 0% added to price.)
3. Date of the invoice that was created. The customer should be able to know when they
phoned the company up asking about a car for hire. The date of the invoice should go onto
the pricing form so they will know when the invoice was created.
4. Customers contact details. The user should be able to take the customers personal contact
details such as title, first name, surname, phone number, email address etc. A form should be
dedicated to this so the user can fill it in.
5. Sign in page for the user. The user should be able to have a sign in form, that allows the user
to sign into the whole program using a provided username and password.
6. Start and end days of the hire and this includes how long for. The customer should be able to
pick how long the hire period should be for with the car he has chosen. It should be
represented on the pricing form so that both the user and the customer can see it.
7. Show a 10% discount if hired for longer than 7 days. The customer should be offered a 10%
discount if they have hired the car longer than 7 days. This should be calculated in the maths
of the pricing form code, so that it can be seen on the receipt when it has been printed.
8. Grand total of the hire cost. The customer should see how much the total cost is going to be
without any VAT/Discount prices that have been applied. It should go onto the pricing form
so when it is printed off, the customer will see it.
9. Add any surcharge prices (service). The customer should be able to see how much the
surcharge pricing was and the customer should also be able to see it added to the total cost.
It should go onto the pricing form, so the customer will see it when it has been printed off
for them.
10. Help for the user. The whole program should have a help form, which will guide the user if
they have any difficulties when operating with the current form. For example, the user
1|Page
, Eliot Hunter (ID: 16002495) Assignment A Unit 14 Event Driven Programming
should be able to press a button and that will take them to a certain form, they can therefore
read what they need help with, then they can go back to the form that they were on
previously.
11. Validation so the program is robust. The whole program should have validation on certain
forms so that the program is difficult to get into by hackers, or hard to break by other users.
For example, the sign in form should have validation where it requires a username and
password to enter the program. The contact details form should have validation where a
field cannot be left blank.
12. The company name and logo. The program should have the company name and the logo on
every single form, to represent who the forms belong too, and to give a consistent feel.
IPSO (Input, Processing, Storage, Output)
Input Inputs of the program will be:
1. Username of the sign in form
2. Password of the sign in form
3. The customers contact details
4. The type of car the customer wants
5. The colour of car the customer wants
6. The pick-up date for the customer
7. The drop-off date for the customer
8. The user pressing the sign in button
9. The user pressing the car type button
10. The user pressing the car chosen button
11. The user pressing the help button
12. The user pressing the pricing button
13. The user pressing the print button
Processing The processing of the program will be:
1. The calculations of the pricing form
2. Loading each form up
3. The images of the cars loading
Storage The storage of the program will be:
1. The customers title, forename,
surname, phone number, address,
town/city, postcode.
2. The picture of the car for the car type
form. Held in resources.
3. The picture to be transferred into the
pricing form.
4. The dates for the car is being used.
Output The outputs of the program will be:
1. The customers contact details (name,
title, phone number, address, postcode,
town/city.)
2. The cost of the car per day
3. The sub total
4. The VAT Amount
5. The surcharge
6. The Discount Amount
7. The Total Cost
2|Page
DOCUMENTATION
Unit 14 Event Driven Programming
ELIOT HUNTER
Sunderland College
,Eliot Hunter (ID: 16002495) Assignment A Unit 14 Event Driven Programming
Design Documentation
User Requirements
These are the user requirements for the Especially for You program:
1. The car chosen, colour and how long for. The customer should be able to choose from four
categories of cars (wedding, classic, off-road, and sports.) The customer should also have the
option to be able to choose the colour that the car should come in (blue, dark green, dark
red, red, silver, and white.) The customer should lastly be able to choose when they can pick
the car from Especially for You and when to drop the car off again when the hire period ends.
2. Add any extras (service) that the customer wants. The customer should be able to choose
between 3 services (gold, silver, and bronze.) The gold service comes with champagne and a
chauffeur, the silver service comes with a chauffeur and the bronze service comes with
nothing. The 3 prices of the services are (gold – 50% added to price, silver – 30% added to
price, and bronze – 0% added to price.)
3. Date of the invoice that was created. The customer should be able to know when they
phoned the company up asking about a car for hire. The date of the invoice should go onto
the pricing form so they will know when the invoice was created.
4. Customers contact details. The user should be able to take the customers personal contact
details such as title, first name, surname, phone number, email address etc. A form should be
dedicated to this so the user can fill it in.
5. Sign in page for the user. The user should be able to have a sign in form, that allows the user
to sign into the whole program using a provided username and password.
6. Start and end days of the hire and this includes how long for. The customer should be able to
pick how long the hire period should be for with the car he has chosen. It should be
represented on the pricing form so that both the user and the customer can see it.
7. Show a 10% discount if hired for longer than 7 days. The customer should be offered a 10%
discount if they have hired the car longer than 7 days. This should be calculated in the maths
of the pricing form code, so that it can be seen on the receipt when it has been printed.
8. Grand total of the hire cost. The customer should see how much the total cost is going to be
without any VAT/Discount prices that have been applied. It should go onto the pricing form
so when it is printed off, the customer will see it.
9. Add any surcharge prices (service). The customer should be able to see how much the
surcharge pricing was and the customer should also be able to see it added to the total cost.
It should go onto the pricing form, so the customer will see it when it has been printed off
for them.
10. Help for the user. The whole program should have a help form, which will guide the user if
they have any difficulties when operating with the current form. For example, the user
1|Page
, Eliot Hunter (ID: 16002495) Assignment A Unit 14 Event Driven Programming
should be able to press a button and that will take them to a certain form, they can therefore
read what they need help with, then they can go back to the form that they were on
previously.
11. Validation so the program is robust. The whole program should have validation on certain
forms so that the program is difficult to get into by hackers, or hard to break by other users.
For example, the sign in form should have validation where it requires a username and
password to enter the program. The contact details form should have validation where a
field cannot be left blank.
12. The company name and logo. The program should have the company name and the logo on
every single form, to represent who the forms belong too, and to give a consistent feel.
IPSO (Input, Processing, Storage, Output)
Input Inputs of the program will be:
1. Username of the sign in form
2. Password of the sign in form
3. The customers contact details
4. The type of car the customer wants
5. The colour of car the customer wants
6. The pick-up date for the customer
7. The drop-off date for the customer
8. The user pressing the sign in button
9. The user pressing the car type button
10. The user pressing the car chosen button
11. The user pressing the help button
12. The user pressing the pricing button
13. The user pressing the print button
Processing The processing of the program will be:
1. The calculations of the pricing form
2. Loading each form up
3. The images of the cars loading
Storage The storage of the program will be:
1. The customers title, forename,
surname, phone number, address,
town/city, postcode.
2. The picture of the car for the car type
form. Held in resources.
3. The picture to be transferred into the
pricing form.
4. The dates for the car is being used.
Output The outputs of the program will be:
1. The customers contact details (name,
title, phone number, address, postcode,
town/city.)
2. The cost of the car per day
3. The sub total
4. The VAT Amount
5. The surcharge
6. The Discount Amount
7. The Total Cost
2|Page
