Evidence Document

Relevant Implications

Functionality:
Functionality is having a program that works as expected or as it should. To check for
functionality, I will apply filters to the main data table to ensure that the data shown in the
queries is correct. For example, if I needed a query for only male players, I would make the
query, then go back to the table and apply a filter to double check the results are the same.

Accessibility:
Usability is how easy a program is to use. To apply usability, I will make sure that all titles
are formatted correctly with no spelling errors and relevant to the data inside. For example,
if I had a query for players who have signed up for CS: GO tournament I would name that
query “qrySignedUpForCSGO” not “SgnedUpForCZGO” or “qryPlayersFromMelvilleHigh”.

Aesthetics:
Aesthetics is how a program looks. To make sure my program looks has good aesthetics I
will change colors to the company colors and use logos. For example, if the text boxes in a
form were all various sizes, I would resize them to only three different sizes to make it easier
on the eyes. I will do this to make my program look more professional and polished.
Table:

I began by changing the view of the table and turning off the primary key
(table named “tblEOlympics”)

Next, I entered all field names I needed.

Then data types. For this I considered having age as short

text, but they may want to know the average age, so I put it
as number.

I noticed that the employer wanted the default on “PaidFee” to be

no and the format for date as dd-mmm-yy so I put that at medium
date.

I applied many other filters to other fields but one I would like to look at is my
“Gender” field on it I have changed the short text amount to one, the default value to
“M” and the validation rule to “M” or “F”. I did this to ensure usability, to make the
program easier to use.
Form:

I used for wizard to begin making the form, I moved all the
fields to the other side and named the form “frmEOlympics”

Next, I began entering the data, some people like to do this after they have finished
formatting the form, but I like to do it first meaning if I run into any mistakes I can fix them
quickly right off the bat. Sure, enough on the first entry I ran into a problem. I could not fully
enter in the first name. Easy fix. I closed the form and went back to
the table opening it in design view. I noticed that the field size for
first name was set to five. I changed it to ten, went back to my
form and sure enough I could enter the full name in.

I entered the rest of the data and encountered no problems worth

documenting. I ended up with a form looking like this.

To get better aesthetics I changed the title to proper English and changed the font. Changed
all the field names to proper English. Changed the color of the form to the company’s color
and added the company logo. As a final touch I resized all the boxes so they would line up
properly. I ended up with this.
Then I went through the data one last time to check for any mistakes. Turns out Ima Hogg is
not a male.
Queries:

Fees Not Paid:

To began I simply pressed the query design button.

I then went to the right hand side and double clicked on “tblEOlympics” to
bring up this list.

I added all the fields I think I need for the critrea; last name, first name, paid fees and phone
number.

I then added the sorting they wanted (sorted by players name) and the criteria (PaidFees
False)

I pressed run, named it “qryFeeNotPaid” to improve functionality and got five results.

To double check all the data in

the query was correct I went
over to my table and applied a filter to the PaidFee field so that only players who have not
paid their fee showed. I also got 5 results confirming that the data that shows on my query
is correct.

TAC Fortnite Not Paid List:

I started once again by pressing the query design button and bringing up
this screen.

Next, I double clicked the “tblEOlympics” on the right hand side to bring up
this drop down box.

I added all the fields I needed to fit the brief.

And then applied the filters that they needed. This included sorting the names and applying
a filter for TAC and Fortnite.

I pressed run and got two results.

I closed it and named it “qryTACForniteList” when I noticed that in the brief, they had called
it TAC Fortnite Not Paid. I read the content through again and saw no mention of having to
filter only people who have not paid so I left it at that a carried on. I went back and applied
filters to “TournamentSignedUpFor” and “School” I can’t screenshot myself applying these
filters as when I clicked out of access the dropdown box disappears but I did get tow results
proving that the data in my query is correct.

Report:

To begin the report, I used report wizard and moved

all the relevant (the fields that they wanted) fields
over.

I then grouped the report by tournament signed up for as the brief

had said.

After that I named it to improve accessibility and sorted by name to

improve functionality.
Then I clicked finish and got this. To edit it I closed
print preview and began.

To start I changed the title and field names to proper

English and found the font that I had used previously on my form for the title. I fiddled with
the spacing of the fields until they looked just right and put up the
font size of the tournament signed up for to make the grouping
stand out. I added the logo (stretch). Next, I changed the color to
match the company color of green and made a darker green for
the header and a lighter green for the body. I changed the color of the title to black to make
it stand out more as well. All of this was done to improve aesthetics.
To test that the report was showing the correct data I went back to my table and applied a
filter to only show players signed up for League of Legends to see if they matched.

Thankfully, they proved correct. I did this for all the other groups, and they gave the same
results. I had another idea to make the grouping stand out even more and returned to my
report to put it into action. I changed the color of the grouping to a darker green and I think
that greatly improves the overall aesthtics of the report.

Ethan Wisnewski