Developing ideas
Plan for: Car Data
Field Name
|
Data Type
|
Width
|
Example
|
License Plate
|
Text
|
7
|
A 12345
|
Brand
|
Text
|
25
|
Nissan
|
Mode
|
Text
|
19
|
Lancer
|
Year of Production
|
Number
|
5
|
2012
|
Mileage
|
Text
|
15
|
10000KM
|
Engine Displacement
|
Text
|
10
|
2000cc
|
No. of cylinders
|
Text
|
4
|
V2
|
Color
|
Text
|
19
|
Red
|
Seats
|
Number
|
2
|
5
|
Transmission
|
Text
|
15
|
Automatic
|
Picture
|
OLE object
|
||
Service History
|
Scan as picture
|
||
Rent per Day
|
Number
|
8
|
345
|
Date Rented
|
Date
|
22/2/2015
|
|
Date Returned
|
Date
|
28/2/2015
|
|
Days borrowed
|
Number
|
13
|
|
Type
|
Text
|
20
|
Sedan
|
Accident
|
Yes/No Field
|
3
|
Yes or no
|
Extra Features
|
Text
|
1000
|
Air Conditioning
|
Validation Rules:
Field Name
|
Validation Rule
|
Validation Text
|
License Plate
|
Presence check, Is not null
|
This field cannot be left empty
|
Brand
|
Presence check, Is not null
|
This field cannot be left empty
|
Model
|
Presence check, Is not null
|
This field cannot be left empty
|
Mileage
|
Presence check, Is not null
|
This field cannot be left empty
|
Colors
|
Presence check, Is not null
|
This field cannot be left empty
|
Transmission
|
“Automatic” or “Manual”
|
Please write Automatic or
Manual
|
Date rented
|
Presence check, Is not null
|
This field cannot be left empty
|
Return Date
|
Presence check, Is not null
|
This field cannot be left empty
|
Accident
|
“Yes” or “No”
|
Please write Yes or No
|
Extra features
|
Presence check, Is not null
|
This field cannot be left empty
|
Plan for: Customer Data
Field Name
|
Data Type
|
Width
|
Example
|
First Name
|
Text
|
15
|
|
Last Name
|
Text
|
30
|
|
Phone No.
|
Number
|
0567890123
|
|
Date of Birth
|
Date
|
14/6/1996
|
|
Nationality
|
Text
|
30
|
|
ID Number
|
Number
|
21656
|
|
License Number
|
Number
|
123456
|
|
Police History
|
Text
|
150
|
No fines
|
Menu layout flow chart:
Login Flow chart:
![]() |
Login:
Main Menu:
Fleet:
Rental Information:
Customer Data:
Query Menu:
Tools:
Evaluation:
This chosen design showcases the basic
layout of my database. It does not showcase what will be a combo-box and a
button but the features will be implemented into the final product. This design
has the employers chose color scheme and can look very professional once
finalized. There are quite a few improvements that can be added if this design
is chosen, The sizes and positioning should be adjusted slightly and the data
fields need to be adjusted to correspond with the correct data. If finalized
the design should include the company's logos and pictures instead of text on
some of the buttons. This design is good as a basic idea but would need major
adjustments that can make it even better.
Test plan:
Test Level
|
When?
|
Who?
|
Passed/Failed
|
Unit
Testing
|
20th
Oct
|
Personal
Testing
|
|
Integration
Testing
|
21st
Oct
|
Personal
Testing
|
|
Security
Testing
|
23rd
Oct
|
Secondary
Testing
|
|
Connectivity
Testing
|
25th
Oct
|
Personal
Testing
|
|
User
Acceptance Testing
|
27th
Oct
|
Secondary
Testing
|
|
Production
Verification Testing
|
30th
Oct
|
Secondary
Testing
|
Chosen Design:
I have chosen the first design as it looks more visually appealing and fits the exact color scheme of the employers company. It looks a bit messy as it is a basic design but with small adjustments the design can be improved to look really professional with many features that are useful for the company. Buttons and combo boxes will be used to make it have professional features and the size of the components will be adjusted to make a good design. Logos and pictures will also be used to give the database an added WOW factor. In conclusion the design itself appears to be a bit messy but with some finalization can be made to look very professional. I believe that this design has the most potential and that is why I have chosen it. All the features missing in the first design will be added in the next criteria as they couldn't be shown visually.
Why is Criterion C and D not posted?
ReplyDeleteCriterion B 5/8
ReplyDelete