Practical Record

A printed, binded document.

Much much easier than the Project Record, considering it's just copy paste.

Two parts: Python and MySQL

Your file should contain the following headers:

• Cover Page

• Certificate

• Python programs (questions to be listed in index)

• MySQL programs

Your file should have borders on all pages. The borders should be formal. Consider selecting solid or double borders, preferably in black.

Your file should have page numbers on all pages. There is no rule regarding the format, but the preferred placement of the page number is either bottom centered or in the bottom right corner.

Leave a margin on the left for the binding. You may go with narrow borders, and then press custom borders and add 0.5 to 1 cm to the margin on the left.

Ensure that the page numbers are within the margins.

This page must be provided by your teacher.

This is the first page of your record.

Contains the title ("Practical Record"), the academic year, and a place for your details.

The page numbers for the record start from the cover page.

Ensure logos and other details are within the margins.

Ensure academic year mentioned is the correct academic year. Currently, it will be 2024-2025.

DO NOT PRINT THE DETAILS. These will be written by hand, using black/blue ink on or before the day of the practical exam.

This page must be provided by your teacher.

This is the second page of your record.

This page must be numbered as well.

Contains a certificate stating that the project is your own work and stuff.

Ensure that the teacher's name is typed, preferably in another color, and is spelled exactly as stated.

Ensure that the teacher's preferred title is used (Mr./Mrs./Ms./etc.)

Ensure academic year mentioned is the correct academic year. Currently, it will be 2024-2025.

DO NOT PRINT THE DETAILS. These will be written by hand, using black/blue ink on or before the day of the practical exam.

There should be at least 20 to 25 Python programs in your practical record.

These programs should be copy-pasted. NO SCREENSHOTS.

Ensure that the programs are part of the portions.

Ensure that the programs are numbered.

The format for each question is as follows:

• Experiment No. (number)

• Aim: (insert aim here)

• Code

  (insert code here)

• Output

  (insert output here)

Ensure that the code is in a monospace font (Courier New, Consolas, etc.)

Use Google Fonts to find monospaced fonts.

Try to run the program multiple times to fill the page. If the program has a menu, show the output of all the menus.

You may or may not have started this when you started learning MySQL.

This should contain around 50 to 70 SQL questions, from various concepts learnt throughout the whole SQL journey.

The format is as follows:

• (qs number). (Question)

• (SQL Query)

• (Output)

Ensure that the SQL queries and outputs are in a monospace font (Consolas, etc.)

Once you are done with the first draft of the file, export it as a PDF and send it to your teacher for approval.

Printing should be done preferably on 80 GSM paper. Size is compulsorily A4.

When sending for printing, please send the PDF. Using Word for printing will ruin the formatting.

Use a good quality printer. The print should be clear and readable.

If your parent's company has a printer, try asking if they can print. Otherwise, go to a stationery shop. Bargain as much as you can. Should be around 1 AED for 5 pages or so.

Once you have printed the file, bind it. Spiral binding is the only binding accepted. Color should be as decided by your teacher.

All students MUST use the same color of binding.

Once you have bound the file, you are done. Congratulations! Submit the file for final checks.

While there shouldn't be any reason for the teacher to make corrections now (if the file was previously approved), it is still a good idea to get it checked once and correct any errors that may be pointed out.

Color your code. Use a light theme in Visual Studio Code and then copy paste the code into Word.

The theme and the syntax highlighting will be copied as well. Looks nice, makes for a good first impression. Also "hides" errors because the examiner would be wow-ed by colors.

I personally used Kary Pro Colors after messing around a bit with the theme files to change a few colors. But you could use it as it is, or get a different theme. Just make sure it's light.