Skip to content

Standard C Programming Lab Report Format

Use this template when preparing a written report for an SPL Lab practical. Fill in the blank fields and adapt the report to the experiment assigned by your teacher.

Important: This is a suggested general format for organizing your lab report. If your department provides an official lab-record format, follow that format first.

Cover Information

Field Write here
Institution [Institution name]
Department [Department name]
Programme B.Sc. in Computer Science and Engineering
Course title Structured Programming Language Lab
Course code 510202
Experiment / Practical title [Title given by teacher]
Experiment number [As assigned by teacher]
Student name [Your name]
Student ID / Roll [Your ID or roll]
Session [Academic session]
Date of experiment [DD-MM-YYYY]
Date of submission [DD-MM-YYYY]
Submitted to [Teacher's name and designation]

1. Aim

Write one or two sentences describing what you want to achieve in this experiment.

Example: To write and execute a C program that reads two integers and displays their sum.

2. Theory

Briefly explain the programming concepts, statements, operators, functions, or data structures used in the experiment.

  • Define the important terms.
  • Explain the logic behind the program.
  • Include relevant syntax where useful.
  • Write in your own words; do not copy unrelated theory.

3. Algorithm

Write the solution as clear, ordered steps.

General format:

  1. Start.
  2. Declare the required variables.
  3. Take the necessary input.
  4. Process the input according to the problem.
  5. Display the result.
  6. Stop.

Change these steps to match your actual program.

4. Flowchart

Draw the flowchart using standard symbols:

Symbol Meaning
Oval Start / End
Parallelogram Input / Output
Rectangle Processing / Calculation
Diamond Decision / Condition
Arrow Direction of flow

Draw the actual flow of your program in the space below. Use a neat, readable diagram and label decision branches such as Yes and No.

Flowchart space: [Draw or insert your flowchart here.]

5. Source Code

Write the complete C program. Keep indentation consistent and use meaningful variable names.

#include <stdio.h>

int main(void)
{
    /* Write your program here */

    return 0;
}

If the experiment contains more than one program, label each program separately.

6. Sample Input

Write the input values used when you ran the program.

[Write sample input here]

7. Output

Write the output exactly as displayed by your program. If your teacher requires evidence, attach a clear screenshot or paste a printout.

[Write program output here]

8. Result

State whether the program produced the expected result.

Example: The program was compiled and executed with the given input, and it displayed the expected sum.

Only say that the program was compiled and executed if you actually performed those steps.

9. Discussion / Observation (if required)

Mention what you observed while running the program. You may include:

  • How the input affected the output.
  • Any test cases you tried.
  • An error you encountered and how you corrected it.
  • Any limitation of your program.

10. Viva Questions (if required)

Prepare short answers to questions related to the experiment's concepts and code.

Q1. [Write a relevant question.]

Answer: [Write a concise answer.]

Q2. [Write another relevant question.]

Answer: [Write a concise answer.]

Before Submission: Checklist

  • [ ] Cover information is complete.
  • [ ] Aim matches the assigned experiment.
  • [ ] Theory is relevant and written clearly.
  • [ ] Algorithm steps match the program.
  • [ ] Flowchart uses appropriate symbols and matches the algorithm.
  • [ ] Source code is complete and properly indented.
  • [ ] Sample input and output are included.
  • [ ] Result is based on an actual run.
  • [ ] Spelling, headings, and page numbering are checked.
  • [ ] Teacher-specific instructions are followed.

Quick Writing Guidance

  • Keep the Aim short and specific.
  • Write the Algorithm before drawing the flowchart and coding.
  • Make sure the Flowchart, Algorithm, and Program describe the same logic.
  • Do not invent output; run the program and record the actual result.
  • Use your teacher's required order if it differs from this template.