Академический Документы
Профессиональный Документы
Культура Документы
For 2D.P6: learners should review their program in light of the results of their testing
and should explain how their program is fit for purpose and meets the original
requirements.
For level 1, as a minimum, learners should identify how their software meets the
original requirements and the purpose.
For 2D.M5: learners should consider the outcomes of their testing and should review
the extent to which the program solves the given problem. Learners should gather
feedback from others and consider changes they would like to make in the light of
this feedback.
For 2D.D4: learners should evaluate their initial designs and the completed program.
They should identify any changes made from the design stage and justify these
changes in terms of the requirements and the features of the language used, and
any other constraints. Learners should make at least three specific suggestions for
improving the completed program to ensure it is fully functional, well coded and fit
for purpose. Learners do not need to implement the enhancements.
Task 1
● Testing table included as a separate document
Introduction
In this assignment, I am going to explain how I feel I have met the
brief that the client gave to me regarding the currency converter.
I will achieve this by first breaking it down into various sections and
then within those sections explaining how I have met the brief and
then provide evidence in the form of screenshots of how I have
fulfilled the client's needs. I will also show be providing a testing
table to show what I have done is working and fit for purpose.
Ease of use
The software had to be easy to use by users of different IT levels, I
achieved this by using clear labels that guide the user to
understand what different parts of the converter did.
As you can see from the above images I have used large clear
labels to show what everything does I also included a help screen
which clearly shows the users what to do by using a GIF, it also
shows users who are more comfortable using a computer that
there are keyboard shortcuts to help them quickly switch between
conversions. These can be seen working on tests 22 - 27.
As you can see from the above image the help screen loads, this
is also shown to work on test 1 and 2.
I believe that I have been consistent throughout my program with
regards to layout and colour scheme, this will help the user feel
familiar with the program once they have used it. All the labels are
clear and concise to help the user understand what they need to
do and what each box does and the labels being big enough to
read for people with poor eyesight
I have used a visual hierarchy with the conversion rates in a
separate coloured box at the side of the converter that clearly
separates it from the rest of the converter. The actual converter
has a clear method running from top to bottom with the user
entering the amount first, then entering the currencies they are
converting and finally coming down to the convert button to see
their conversion. With the Go To Export button being right by the
convert button.
Being forgiving of user error
I also made the currency converter to be forgiving of user error, I
put in as much validation that I could think of, this is to help the
user understand either what they have done wrong or to explain
what they need to do to complete the process.
The first example I have of my validation is the message box that
appears if the user enters a conversion amount into a conversion
box that does not match the currencies they have chosen to
convert to.
Example:
In the above image, you can see that the user has entered the
conversion rate into the American Dollar to British Pound
conversion box but they have selected the opposite conversion
with the currencies selected. The message box clearly tells them to
check that they have chosen the correct conversion and
currencies. This works with all other wrong conversions as well as
you can see on tests 16 - 21. I feel this gives the client an extra
layer of security against mistakes because if there was only one
conversion rate box for all the currencies, mistakes like this would
not be detected and could cost the company time and money
which is what they wanted to avoid and the reason they asked for
this application in the first place.
The validation also covers conversions that you are not allowed to
do, this is because the client only wanted the user to be able to
convert certain currencies so all others are blocked from being
used together.
This is one of the
conversions you are not
allowed to do, as you
can see there is a
message box that clearly
states that this a
conversion they are not
allowed to do. This saves any mistakes being made using wrong
conversions and stops the user doing something the client does
not want them to do.This message appears for all conversions that
are not allowed which can be seen working on tests 28 - 35.
There is an option that comes up when clicking the X close button
on the converter if there is text in the display box, which is to ask if
you want to save the text before they close the application. The
reason I did this is to stop conversions accidentally being lost
before being saved. If the display box is empty then the
application will close without any warnings.
As you can see from the above image it asks if you want to save
before exit. This will save the company from losing conversions that
have not been saved. You can this working on test 41.
The client did not want the user to be able to convert anything
above £1,000,000. If anything above that number is entered a
message box appears to say that they cannot do that.
This can be seen working on test 43.
The professional appearance of the form
I believe I have made a professional looking application that fits
well with the company's aesthetics, their company logo is yellow
and blue which I have tried to match as closely as I can and have
used it throughout the application. You can clearly see this in the
above pictures.
Up to date currencies- making sure the conversions are correct
The user gets up to date currency conversion rates from the XE
website which is linked directly from the currency converter. As I
have stated in some of the above material I have tried to mitigate
any mistakes the user can make regarding conversions and
making sure they are correct, first the conversion rate box that is
filled out needs to match the currencies selected in the to and
from combo boxes in the same way in order for the conversion to
take place.
This is the website the link takes the user to, here they can get the
latest conversion rates.
What currencies are involved
There are four currencies in the currency converter, this is because
the client only wanted these specific currencies. As I have
explained above the client not only just wanted these four
currencies but they also only wanted to convert either to or from
Pound Sterling, this means that any other combination is not
needed so I have put validation in to tell the user exactly that it is
not a conversion that is allowed.
Rounding up Answers
When doing currency conversions there is a need to round up the
amounts in both the total boxes and also the commision, this is
because money is displayed up to two decimal places. The only
part that is not rounded is the conversion boxes, these need to be
as precise as possible because it can cost not only the company
but a customer a lot of money if these are slightly off.
As you can see from the image, the final amounts and commision
are rounded to two decimal places, with the conversion box
allowing as many decimals as needed. You can see this working
on tests 4 - 9.
Labels changing based on currencies selected
To make it clear to the user exactly what currency is being
displayed in each box I have put the currency symbol next to the
amounts, this changes based on what currency is being
displayed.
As you can see from the above image there is a currency symbol
in each of the boxes, these can be seen working on tests 10 - 15.
The only currency symbol that does not change is the commision
one because we are always charging commision on the Pound
Sterling amount.
Pounds being in the convert from, or convert to transactions
As I mentioned in my validation section the client only wanted to
be able to convert either from pounds or to them, I have fulfilled
this as you will see on tests 16 - 21
Saving a transaction to a text file
The client wanted to have the option to save the conversion as a
text file, this is because at the moment the client's company is
using copy and paste to get the conversions into a file to save
them, this is causing users to make mistakes which are causing the
company to lose money and time. I have not only added the
ability to save the file I have given the user the ability to add their
own comments to the file before saving, I did this because it gives
the user more options, there may be a time when they want to
make a note or amendment on the file.
As you can see from the image once the save button is pressed a
new save form opens up which allows the user to name the file
what they want and then save it wherever they want. You can
see the text file working on test 42.
Adding a commision calculation
As this converter is being used by a business there needed to be a
0.5% commision made on every conversion. The commission is
always on the Pound Sterling amount, to do this I had to do two
calculations in the code, if the conversion was from Pound Sterling
then the calculation needed to be the amount box multiplied by
0.005 and if the conversion was to Pound Sterling then the
calculation would change to the total multiplied by 0.005.
As you can see from the image the commission has been taken
from the amount because it is being converted from Pound
Sterling, there is also a box that displays the total after the
commission has been deducted.
Task 2
Task 3
learners should evaluate their initial designs and the completed
program.
Stage 1: Learners should identify any changes made from the
design stage and justify these changes in terms of the
requirements and the features of the language used, and any
other constraints.
This is my original design:
This is my final design:
As you can see there is little change between the two designs, the
biggest change was to add a textbox for the commission and the
total after the commission, these boxes show the amount of
commission the company will be making on the transaction and
the total will show how much the customer will receive after the
company has taken off their commission.
The other changes are from my peer reviewer in assignment three
and the feedback from the client, the peer reviewer asked if I
could change my convert to and convert from combo boxes so
that the user cannot delete what was inside, I did this and now
they are greyed out. My peer voters mentioned having me
change my text boxes to read-only so that the information inside
could not be deleted this is a change that I would make. The
client wanted me to add a label next to the XE logo so that the
user not only understood that the logo was a button but what the
button actually did. Another change was to add validation to the
display conversion button, if a conversion has not been made
then a message will appear to say that there is nothing to display
in the text file. Both of these are good changes because the label
gives the user more instruction of what to do and the other lets the
user know that they have made a mistake pressing the display
button without making a conversion.
Stage 2:Learners should make at least three specific suggestions
for improving the completed program to ensure it is fully
functional, well coded and fit for purpose.
Learners do not need to implement the enhancements.
First change
The first change I would make is to the code, I would completely
rewrite it from scratch and make it more efficient because my
code is really inefficient with multiple lines being written when one
line would have done. This would make my program better
because it is important to have a well-written code so if anyone
else looks at the code they don’t feel like they would have to
rewrite it themselves to get it right.
Second change
The second change I would make is one that would make the
biggest change to the converter and this is to have the
conversion rate be chosen automatically in the background
without the user even thinking about it. This would greatly increase
the converter's ability and give the user fewer steps than they
currently have. This is important because the less time it takes the
user to make a conversion the more they can fit into a certain
amount of time, this increases the productivity of the company
and makes them more money which is the company's main aim.
Third change
The third change I would make is to the way the conversions are
saved, currently, they are saved as a text file either all in one or as
separate files. The way to improve this would be for the
conversions to be saved on an excel file with any new saves been
added to the table each time, this way at the end of the day the
company can easily use Excel's features to do a running total of
the amount of money they have converted and the commission
they have made. This excel file could be renewed each working
day, week, month or even be used for a full business year. I think
this would give the company more control overseeing exactly
how much money they have made because it will already be in a
total column if they continue using the text file way they will have
to manually go through each of the transactions and add them
up themselves. This would cause human mistakes which is one of
the reasons they wanted this converter to be made in the first
place.
Constraints
There are constraints to some of the changes I would like to do
mainly my ability to carry them out, I would not know how to add
the conversion rate automatically or have each conversion
added to an Excel document as a new line each time.
Appendix
Attach scans of your completed forms here