Answers to Customer Concerns Over Functional Specifications
Answers to Customer Concerns Over Functional Specifications
Here are the answers to the customers comments on our Functional Specifications and management plan. They are taken in Order starting at the summary and continuing through each document in succession.
List of Concerns by Section:
Concerns
1. We intended that the fuel delivery person access the system at the station instead of at Head Office.
We
have modified this so that the fuel delivery personal will access the AGS
at one of the station pumps rather than the Head Office.
1. For the purposes of the assignment, you can simply assume one company will want stolen cards to not be returned to the customer, and demonstrate both cases.
We
will assume this.
2. What about Diesel Fuel? In our informal specifications we mentioned four types of fuel ?
We
have added a diesel fuel selection, however you can not pump this type
of gas with the same pump as regular types of fuel so you will need a separate
pump anyway !
3. We would like to avoid the tanks being shut down, so there should be an adjustable lower limit (default to 1500 Litres), below which the system notifies the main office that refilling is required and continues normal operation. There should also be the 500 Litre shutoff limit, which we think is a great idea.
We
will implement this as well. We have also added the low level tank alert.
1. We also need the transaction total.
We
have also added the transaction total.
Head Office and Remote Operations
1. Is the Employee ID the person's name or employee number?
This
is the persons employee number. Another screen shot will show this.
2. For every number entered (or changed) in the system we would like an error/boundary check on the number. Also, is there the ability to: Add a station? Add an employee? Add a fuel delivery employee? Select a station?
We
have implemented this already, and there is the ability to add and delete
personal.
3. Can we get feedback before changes are made? Also, the price of a fuel type should not be changed while some of it is being sold - i.e. the station would not update the pumps and signs until there are no customers buying that fuel type.
We
have also implemented this.
4. Feedback with double check? When any change is made at the office we would like a window to double check that selection (eg. if a user changes the fuel price then a window should appear asking if this price is correct. Giving old price as well as new price.)
This
is partially implemented as far as I know, it does come back with a confirmation
screen but as to weather or not the prices are also displayed, I will have
to double check.
5. We like this method. If possible, we would like each option to appear onscreen as a pictorial icon of the relevant function.
If
time permits this we will add it.
6. We need a provision for the main office to be notified ASAP if a gas pump is manually shut down by a field service technician or if the gas station automatically shuts it down for some reason. Whether or not you implement this for the assignment is up to you, and probably depends on how you're going to simulate the gas station end of things.
We
will not be implementing this for the assignment. In real life it would
be handed of to a hardware company to deal with. We are only a software
company.
7. In our original requirements, we intended that the fuel delivery would be handled entirely at the gas station. The delivery person would use a keypad to interact with the gas station to request tanks be unlocked and then to record the amounts delivered. We like the idea of placing overriding locks on the gas tanks from the office end, but we wish to make it clear that the delivery person interacts only with the station, and not with the office software.
We
will not be implementing electronic locks on the gas tanks, simply a manual
lock and key. The driver still interacts with a pump at the station to
fill in his reports on time of delivery ect...
8. We would like context-sensitive help available everywhere in the program by pressing a standard help key like F1. Or, at a minimum, a Help button on every different screen leading to a help page specific to that screen. We feel that having online help available quickens training and reduces errors.
We
are in agreement with you 100%, however there is not enough time to place
this into the assignment now. This was not part of your original specs,
however we will provide the facilities to easily add a context help module
later if you desire.
9. Although security is not of major importance to this system, it would be desirable for the system to either automatically log the user out or demand re-entry of the password if left unattended for more than 15 minutes.
Again
if we have time we will implement this also.
Management Plan Data Structures and Algorithms
1. We would also like to know the total street value of the fuel delivered.
We
are confused by this ?? Are we selling Drugs ?? (Just Kidding, thought
you would need some humor by now :).. Seriously, what do you mean here
?
2. This is essentially right, but it must be able to handle the possibility of a sale being in progress when the report is generated.
What
will actually happen is that the pump will generate a report after the
current transaction is finished.
Author : Carey Bingham
Send Comments to Supplier Group 11
Last Updated
on 2/09/97
By Carey Dean Bingham
Email: bingham@cpsc.ucalgary.ca
