IT Report for ND Computer Science Students: Outline, Work Done and Sample

Quick summary:

An IT report for ND Computer Science follows the usual polytechnic layout: front pages, then Introduction, Background of the Organisation, Work Done (split into the areas you worked in, such as hardware maintenance, networking, software and web work), Skills Gained, and Summary, Conclusion and Recommendations. Describe each task with the tools you used and the steps you followed, add screenshots, photos or a network diagram as figures, and keep customer or company data out of them.

Computer Science is one of the most common ND courses, and the IT placements vary a lot. Some students spend their year fixing computers in a business centre, others work in a bank's IT unit, and others write code at a small software company. The report format stays the same, but your Chapter Three depends on where you were.

This guide gives a full outline and sample Work Done sections for the most common placements. For the general format, see how to write an IT report for polytechnic students.

Where ND Computer Science students usually train

If you are still looking, see how to get an IT placement.

Full chapter outline

Front pages: title page, certification, dedication, acknowledgement, abstract, table of contents, list of figures.

CHAPTER ONE: INTRODUCTION
1.1 Background of industrial training
1.2 Aims and objectives
1.3 Duration and place of attachment

CHAPTER TWO: BACKGROUND OF THE ORGANISATION
2.1 History of the organisation
2.2 Vision and mission
2.3 Services or products
2.4 Organisational structure (with an organogram as Figure 2.1)
2.5 The department where I worked

CHAPTER THREE: DESCRIPTION OF WORK DONE
(See the samples below.)

CHAPTER FOUR: KNOWLEDGE, SKILLS AND EXPERIENCE GAINED
4.1 Technical skills
4.2 Soft skills (customer service, teamwork, reporting to a supervisor)
4.3 Link between ND coursework and the training

CHAPTER FIVE: CHALLENGES, CONCLUSION AND RECOMMENDATIONS
5.1 Challenges faced
5.2 Conclusion
5.3 Recommendations (to the company, the polytechnic and the ITF)

Some schools use a 4-chapter layout that joins Chapters Three and Four. Check your department's guide.

Sample Work Done sections

If you worked in hardware maintenance

3.1 Computer Assembly and Disassembly

I learned to take apart and reassemble desktop computers. I identified the motherboard, processor, RAM, hard disk and power supply unit, and learned the safety steps, such as using an anti-static wrist strap and disconnecting power before opening the system unit.

3.2 Troubleshooting and Repair

I diagnosed common faults such as no display, overheating and slow performance. For a system with no display, I checked the power supply, reseated the RAM and tested the monitor cable before replacing the faulty part.

3.3 Operating System and Software Installation

I installed and configured Windows on new and repaired systems, installed drivers, Microsoft Office and antivirus software, and created recovery drives.

If you worked in networking

3.4 Cable Making and Testing

I made straight-through and crossover Ethernet cables using RJ45 connectors and a crimping tool, following the T568B colour code, and tested them with a LAN tester.

3.5 Network Setup

I assisted in setting up a small office network with a switch, a router and two access points. I assigned static IP addresses to printers and configured DHCP for staff devices.

A simple diagram of the office network (router, switch, access points and devices) makes a good figure here.

If you worked in software or web development

3.6 Website Development

I built pages for a client website using HTML, CSS and JavaScript, and made them responsive for phones. I used Git to save my changes and pushed them to the company's repository for review.

3.7 Database Work

I created tables in MySQL for a small inventory system and wrote queries to add, update and list products. I tested the forms that saved data to the database.

Add screenshots of pages you built, but use test data. Never put real customer names, phone numbers or passwords in your figures.

For the one-year IT: show progress across the year

If this is the year after ND, split Chapter Three by stage as well as by topic, for example:

• Months 1 to 3: orientation, hardware basics, assisting senior staff
• Months 4 to 8: handling repairs and user support on your own
• Months 9 to 12: network jobs, a website or a system you helped build

This shows the panel that your skills grew, and makes it easier to fill a long chapter with real work.

Figures to include

• Figure 2.1: organogram of the company
• Photos of the workshop or office (without customer details)
• A network diagram you drew
• Screenshots of software you installed or pages you built (with test data)

Your logbook is where most of these details come from. For a filled example, see filled logbook for Computer Science.

Using the MonoEd report tool

The MonoEd SIWES Report is built from what you tell it about your company and the work you did, so a repair-shop report and a software-company report come out different. Pick your polytechnic for the right chapter layout, choose your duration (including 1 year for the IT after ND), add your own photos to the figures, and download it as Word or PDF. You can read the front pages and Chapters 1 and 2 free first. If you also face a defence, it can make slides with speaker notes.

Frequently asked questions

What title should I use for my IT report?

Something plain, such as "A Report on Industrial Training Undertaken at [Company Name], [City]". Your department may give you the exact wording.

Can I use a university Computer Science SIWES sample?

You can use it to see the structure, but the title page, award and chapter titles may differ, and the work done must be your own. See Computer Science SIWES report samples.

How do I prepare for my IT defence?

Know your Chapter Three well and be ready to explain any tool or term you used. See defence questions and answers and how to make your defence slides.

Thinking ahead to HND?

See HND Computer Science project topics for ideas you can start thinking about during IT.