Click on the above link, to go to the VB 'How To' website, where you will find lots of help on how to do stuff in Visual Basic.
Take note of the highlighted KEY words
Remember you are not changing anything in your VB prototype solution from this point on. Make a copy of your prototype solution, put it in your Software Development folder and continue working on this new version. The prototype solution remains unaltered and is sent to the examiner along with your final Software Development solution.
Purpose -Refine the prototype (take a copy first!) using the amended design documentation (post prototype review), ensuring that the finished system is functional and suitable for audience and purpose.
Take all of your objectives in turn, solving them in your chosen programming language. You should be aiming to produce a functioning solution to a highly demanding problem that meets your objectives for the solution to the problem.
Here is a checklist of requirements for your coded solution:
Meet all of your objectives
Use as many features of the language as you can (loops, IF statements, called procedures, user-defined procedures, datagrids, dropdown boxes, string manipulation, calculations, appropriate use of colour, font, formatting etc.)
Store your data in the most efficient way in textfiles which contain Primary and Foreign keys i.e. follow your normalised ERD
Make appropriate use of local and global variables
Annotate your code - write a paragragh at the beginning of each procedure to explain what the code is doing.
If you have some complex code, highlight it by means of annotation
Use appropriate validation
Make sure you have two complex outputs, which manipulate data
Consider the user-friendliness of your system. Could someone without much knowledge, use your system easily?
Purpose -Document the coded solution, so that another programmer could understand how your solution works, should they need to amend or add to it.
There are three aspects to the Maintenance Documentation:
Data Structures - Variables
Data Structures - Table design and implementation
User Interface
Data Structures - Variables
You need a table with the following headings:
Variable = Variable name
Procedure = the name of the procedure where it is used
Purpose = what it is being used for
You must include ALL variables in your coded solution (the list could be quite long!)
Here is an example of parts of a variable table:
Data Structures - Table design and implementation
a) Place your Entity Relationship Diagram from your Design here:
Example:
b) Screenshot each textfile with brief explanation of what data is being stored:
User Interface - Include evidence of the completed user interface including a full description of the features that make it fit for audience and purpose.
You need to screenshot all user interface forms, with comprehensive annotation surrounding them. The annotation should explain how you have designed your user interface with a sense of audience and purpose (HCI, colour, font, sequence of tabs, sequence of forms, etc). Put clear headings before each user interface, along with a sentence to describe what the user interface is being used for.
Examples of User Interface Documentation:
Please note: This background is a good example of what NOT to do.
The text is not easily readable on the chosen background, so marks would be lost for the lack of awareness of the audience trying to use this system!
However, the report itself is a good example of manipulating data to create a complex output - necessary for a good A2-standard project.
These powerpoints show you how to create and update records in textfiles in VB. They are also on the 'How To..' website, which is linked at the top of this page.
Here are a couple of videos which should help you:
This video shows you how to create your first order and associated multiple OrderLine details, using the correct foreign keys to link the data that you save into your textfiles
This video shows you how to create further Orders (with multiple OrderLines), and shows you what your textfiles will look like after you have created multiple orders.
This video shows the Order and OrderLine code (remember this code is for use with arrays of textboxes). IF you are using listboxes, your saving of the Orderline will be a bit different. You will have to loop through the listbox to create your OrderLines instead.