You need the following mark scheme headings in b(i) of your project:

• Detailed systems design.
• Evidence the the user has seen the designs.
• Proposed record, file and data structures.
• Design limitations.
• Design of data capture forms.
  
• Design of the Input screens.
• Design of the output screens.
• Summary of the aims and objectives.

Remember - approach this section as if you were providing information for someone else to design the system. There are a number of different ways to tackle this section. I will describe how to complete it using a RAD (Rapid Application Design) approach.

Detailed systems design.
Briefly discuss RAD and why you will use it. In PowerPoint, Word or any other package, put together a mock-up of what you think the final product will look like. Now arrange a meeting and show it to your user. Discuss and document the meeting in the diary. Is this what they were thinking of? What comments would they make? Any features missed out? etc etc. Now do another draft and repeat the process, until you and your user are happy with the look and feel of the proposal. Make sure the printouts of each drafts and redraft is included. Make sure you detail each meeting you had with your user to discuss each draft, possibly by referring the reader to your diary.

The final thing to do here is to draw out a map, showing all of the different menus, screens, outputs and buttons and how they are related to each other. This will help a reader visualise the entire system.

Evidence the the user has seen the designs.
All you need to do here is to refer the reader to the previous section and the appropriate diary entries.

Proposed record, file and data structures.
Looking at your proposed solution, you need to start thinking about what record structures you need to store any records. Describe e.g. any arrays you need (size and data type), break down and describe any record structures you need, any links to external databases you need and a description of those. How will you store records? What sort of file will you use? What data items do you need to use. Do a Data Dictionary. This is a table with the following headings: Data item name, Data type, Validation rule(s), Example, Why has it been included (where is it needed) and an example of the data. Now complete the table for each data item in your intended system.

Design limitations.
What features would be a good idea to include in your system, that you are not designing in to it for some reason? These are design limitations. You need to describe some and explain why you are not including them. Make sure you do this from the point of view of your user and their needs.

Design of data capture forms.
Design on paper or on the computer any data capture forms you need. Annotate it with justification comments. In your annotated comments, keep writing about your user and their needs.

Design of the Input screens.
Start by explaining that because you used RAD, you designed the screens on the computer, discussed them with your user, made appropriate changes and repeated the process until everyone was happy. What you can then do here is to simply annotate a copy of your mock-up printouts. You need to say why you have put things on the screens, why you have positioned them where you have, discuss features of each screen and so on. In your annotated comments, keep writing about your user and their needs.

Design of the output screens.
Again, start by explaining that because you used RAD, you designed the outputs on the computer, discussed them with your user, made appropriate changes and repeated the process until everyone was happy. Then simply annotate the mock-up printouts with appropriate comments that justify why you have included what you have included. In your annotated comments, keep writing about your user and their needs.

Summary of the aims and objectives.
All you need to do here is to refer the reader to the page number where they can find your final Requirements Specification.

CHECK:

ARE YOU USING YOUR TEMPLATE(S)?

ARE YOU USING REPORT WRITING STYLE?

HAVE YOU BEEN UPDATING YOUR DIARY?