LO2: production plan
The problem of the website needs to store dossiers and
access them to view or edit as well as sort them.
Some wireframes of the website pages are based primarily on
my stakeholder’s criteria which are that it has to be simple and easy to use.
This is the wireframe for the log in page which is required
to keep any confidential information private.
I have designed the log in page to look like this so that it
is easy to understand and read. The login page will be the first page that is
viewed as it will stop unauthorised access to private documents which follows
the data security act.
This is the wireframe for the home page.
I have designed the home page based on a set of criteria
given by my stakeholder. Which is the design idea I have chosen as it doesn’t
have many displayed items which means that the end users would be less likely
to be distracted by any undesirable aspects.
This is the wireframe for the about page.
For this design I have decided to stick to a style to create
branding and follow the criteria of my stakeholder. The about page will contain
what the purpose of the website is why the website was made and contact details
to report any issues that may arise for any potential users.
This is the wireframe for the table page.
For this design I have decided to stick to a style to create
branding and follow the criteria of my stakeholder. The table page uses a basic
and easy to understand table which displays the names and dates of dossiers and
when they were last edited this is to allow people to see what needs to be
updated and saved.
This is the wireframe for the dossier page.
For this design I have decided to stick to a style to create
branding and follow the criteria of my stakeholder. The dossier page is a
simple and easy to understand dossier layout which would allow my stakeholders
to understand and fill in the dossier with ease.
This is the wireframe for the make or edit dossier page.
For this design I have decided to stick to a style to create
branding and follow the criteria of my stakeholder. This make page or edit page
allows the user to change dossiers with sets of data for the different fields
of data. This would allow the user to keep track of any medicine given to
animals and any medical history.
The colour scheme of the project is a chartreuse and teal as
this is what my research shows to be both calming and energetic
Psychology
of Teal: Teal
blends blue’s tranquil stability with green’s optimism and healing properties.
Teal’s understated elegance encourages a calm, reflective mood. Color code is
RGB, R= 0, G= 128, B= 129.
Psychology
of Chartreuse: Chartreuse
represents enthusiasm, happiness, nature, growth, and youth. Chartreuse is
rarely associated with calm and relaxation. It’s seen as a highly energetic
color and is great for inspiration and motivation. Color code is RGB, R= 128,
G= 255, B=0.
As the project will be a website I have made a sitemap for
the website to show the paths o navigation and to give a baseline of how it
should work when it has full functionality.
The dossier design is the type of fields that the user has
to fill in to make the dossier.
•
|
Key:
Black = universal
Red = game characters/people
blue = veterinary
|
•
Date of Birth:
•
Age:
•
Ethnicity:
•
Biography:
•
Animal:
•
Photo:
•
Issue:
•
Owner:
•
Game:
•
Gender:
•
Address:
•
Contact:
•
Occupation:
•
Neutered:
•
Pregnant:
•
Diagnosis:
I have outlined the dossier fields so that the dossiers so
that the form is easy to understand and outline the display of the actual form.
To show that the project will process data through the validation
of an email to create an account.
Bool isvalidemail(string
email)
{
Try {
Var
addr = new System.Net.Mail.Mailaddress(email);
Return
addr .address == email
}
Catch {
Return
false;
}
}
This checks whether the email is in the right format even if it is
not an active or used email.
To manipulate the data, I will use a sorting algorithm to organise
the dossiers based on an ID that will be given per dossier. Then I would have a
report of when each dossier was last opened or edited.
The data types for the dossier forms are
|
Field
name
|
Data
types
|
|
Name
|
Varchar
(50)
|
|
Date
of Birth
|
Date-time
|
|
Age
|
int
|
|
Ethnicity
|
Varchar
(50)
|
|
biography
|
Varchar
(500)
|
|
Animal
|
Varchar
(50)
|
|
Photo
|
image
|
|
issue
|
Varchar
(200)
|
|
Owner
|
Varchar
(50)
|
|
game
|
Varchar
(50)
|
|
gender
|
bool
|
|
Address
|
Varchar (120)
|
|
contact
|
varchar
|
|
Occupation
|
Varchar
(50)
|
|
neutered
|
Yes/no
|
|
pregnant
|
Yes/no
|
|
diagnosis
|
Varchar
(200)
|
The data types of the data fields in the dossier are important and
key to this project as the dossiers can not hold any data without specified
fields and data types. This table of datatypes enables me to see what the
dossier field types should be and allow me to create the dossier templates.
This is my plan for production
|
The
home page will look aesthetically pleasing and function according to how it
is planned.
|
To
check this, I will run the home page and review how It looks and then I will
open the links to see if they work as intended.
|
This
milestone will be complete by the 11th of December.
|
I
will also check with my client to see if they approve of the progress or
changes made to the project as to follow what they want and not what I want
as it is their project and will be their property.
|
|
The
create page will look aesthetically pleasing and function according to how it
is planned.
|
To
check this, I will run the create page and review how It looks and then I
will open the links to see if they work as intended.
|
This
milestone will be complete by the 18th of December.
|
I
will also check with my client to see if they approve of the progress or
changes made to the project as to follow what they want and not what I want
as it is their project and will be their property.
|
|
The
about page will look aesthetically pleasing and function according to how it
is planned.
|
To
check this, I will run the about page and review how It looks and then I will
open the links to see if they work as intended.
|
This
milestone will be complete by the 22nd of January.
|
I
will also check with my client to see if they approve of the progress or
changes made to the project as to follow what they want and not what I want
as it is their project and will be their property.
|
|
The
dossier page will look aesthetically pleasing and function according to how
it is planned.
|
To
check this, I will run the dossier page and review how It looks and if the
data is saved on it then I will open the links to see if they work as
intended.
|
This
milestone will be complete by the 29th of January.
|
I
will also check with my client to see if they approve of the progress or
changes made to the project as to follow what they want and not what I want
as it is their project and will be their property.
|
|
The
table page will look aesthetically pleasing and function according to how it
is planned.
|
To
check this, I will run the table page and review how It looks and then I will
open the links to see if they work as intended.
|
This
milestone will be complete by the 5th of February.
|
I
will also check with my client to see if they approve of the progress or
changes made to the project as to follow what they want and not what I want
as it is their project and will be their property.
|
|
The
login page will look aesthetically pleasing and function according to how it
is planned.
|
To
check this, I will run the login page and review how It looks and then I will
input data into the fields and see if the data is saved.
|
This
milestone will be complete by the 12th of February.
|
I
will also check with my client to see if they approve of the progress or
changes made to the project as to follow what they want and not what I want
as it is their project and will be their property.
|
Comments
Post a Comment