Part 4 - Specify the proposed solution
In this part of developing a solution to a problem, you need to:
a) Specify and justify the solution requirements including hardware and software configuration (if appropriate).
b) Identify and justify measurable success criteria for the proposed solution.
Things to consider doing:
a) Put a heading, The solution requirements and success criteria.
b) You need to produce a Requirements Specification. This is a list of objectives, that specifies exactly what you will do for your user and exactly how the success of each item in the list will be measured. By the end of the project, what will your user be able to do with your system? How will you know if this has been achieved, partially achieved or not at all completed? Typically, you should start by producing a 'Draft Requirements Specification' with success criteria. You then state that you need to check this with your user. You then go back to your user and get further information to clarify points. You them produce a 'Final Requirements Specification'. You then go back to your user to check it. If they are happy, both you and they sign and date a copy of the final User Requirements Specification on headed paper (your school's is fine). All of the above needs to be clearly documented. Don't forget the diary entries. The evidence gather here can also be used in Part 3. Examples of entries include:
The user will be able to search for a student and get back all of their test results within two seconds. This will be tested by using John Smith and observing all his test results being displayed on the screen within two seconds.
Each time the hero is killed, the 'Lives left' data on the screen will be updated correctly. If the hero loses three lives, the game should end and the final statistics should be displayed. This will be tested by killing the hero after zero, one and two lives have already been lost and observing that the data is updated correctly, and the game ends after losing the third life.
Each player should be able to select what character they would like to be. This will be tested by asking Jack Jones to select each one of the options at the start of a new game and observing that this is possible.
c) Now you have the Requirements Specification, you know what you need to design and make for your user. Now you have to describe a suitable hardware and software specification, taking into account what they already have and use. What hardware do they need? What software do they need? Justify your choices by discussing the needs of your user. Why do they need a keyboard? Why do they need access to cloud storage? for example:
The user will need a keyboard and mouse. They needs to select the characters in the game and to type in instructions to tell the game what their character must do next.
The system will need to back-up data. We are proposing to do this directly to cloud storage because this is the most secure method of data storage. The user will need an Internet connection for this to happen so we are proposing that a pen drive is available for any time the internet is offline for any reason.
The game will make use of extensive sounds as part of the gaming experience. We would therefore like the final solution to have a soundcard and speakers of suitable quality. We suggest a XXXX and YYYY speakers would give an excellent quality sound for a reasonable outlay.