Project Based Learning

Written and reviewed by Rohit Singh, Computer Science & Commerce faculty at UniDrill (MCA, Osmania University · 6 years teaching). Based on NCERT Computer Science Class XII, Chapter 13.

Why do group projects fall apart, and how do you stop that?

Every class has seen it: four students, one deadline, and three people waiting for the fourth. The chapter on project based learning is the fix. It gives you a fixed route from the first idea to the finished product, a way to cut a big problem into small pieces, and the habits a team needs. The key facts are the order of the steps and who does what, so learn the steps by heart and understand why each one sits where it does.

What project based learning is

Project based learning (PBL) gives students thorough practical exposure to the problem on which a project is based. Projects are usually done in groups, so students also learn to work together, solve problems, take decisions and investigate. The work follows a pattern: analyse the problem, split it into small modules, apply a method to solve each module, and then integrate the solutions of all the modules into the complete solution.

To solve the problem, the team gathers the relevant data in the format the project needs, processes it with a chosen method, and reports the results in a predetermined format. All team members must be involved.

Three approaches to a project

A modular plan can be worked out either top down or bottom up.

Beyond the textbook. For the exam: learn the three approach names and the modular definition: modules with defined tasks, inputs and outputs. In reality: real teams rarely use one approach in its pure form. They plan top down so that everyone sees the whole, build and test small parts bottom up, and revisit the plan as testing shows problems. The ability to change the plan is part of good planning.

The five steps of a project

The cycle in one line: Identification of a project → Defining a plan → Fixing a time frame and processing → Guidance and monitoring → Outcome of the project.

Why this order? You cannot plan a project you have not identified, you cannot set a time frame for activities you have not defined, and guidance is needed only once work is under way. The outcome is judged against the idea you began with.

Pause and predict: A member is stuck on a part of the program, and the team asks a senior student and searches a website. Which step of the project is this, and who must make sure progress continues?

Check your answer: Step 4, providing guidance and monitoring. Guidance can come from books, websites and experts. The project leader must ensure monitoring, and the guide teacher also helps.

Teamwork

Teamwork is the combined effort of individuals to accomplish a task. In cricket, a good ball by the bowler does not take a wicket unless a fielder catches the ball. Winning needs batting, bowling and fielding, and so every member's effort. A project team needs technical ability and also six qualities.

Worked example: match the situation to the teamwork component.

The three sample projects

Each description in the chapter is a model. A group may choose any other project in consultation with the guide teacher.

Worked example: break the restaurant project into modules. Applying the modular approach, each module has a task, an input and an output.

Integration is the last step. The billing module needs the order entry module's output, and the report module needs the saved bills.

Worked example: the bill identification and the day's report. The order number starts from 1 every day, so the order number alone does not identify a bill. Order number 3 exists on every day. Joining the date to it makes a unique identification, for example 2026-10-21 and order 3. The manager's report then adds the bill amounts for one date.

The report asks for a date, then adds up only the bills of that date, 450 plus 300 for the first date and 280 for the second. The common wrong design is to identify bills by order number alone, which would clash across days.

Worked example: the clue in the puzzle. The board is 6 by 6, so it has 36 cells and 6 bombs. If the first click is on a random cell, the chance it is a bomb is $\dfrac{6}{36} = \dfrac{1}{6}$. A clue counts the bombs in the adjacent cells. A cell in the middle has 8 neighbours, a cell on an edge has 5 and a corner has 3, so the clue can be at most 8, and the code must stay inside the board.

With bombs at (0, 1) and (1, 0), the corner cell (0, 0) has both as neighbours, so its clue is 2. The middle cell (3, 3) has none of them near, so its clue is 0. The test 0 <= nr < 6 and 0 <= nc < 6 stops the program from looking outside the grid, which would otherwise cause an error. This is the kind of situation for which the project asks you to handle exceptions.

Worked example: Match the Sum. The cells hold 3, 7, 2, 9, 1, 5, 4 and the player types 3 and 7.

The typed digits are 2 or 3 in number and add to 10, so they are removed from the list. If the player had typed 3 and 9, the sum would be 12, nothing would be removed and the message appears. The game ends when all 15 cells are full and there is no empty cell for the next digit.

Pause and predict: In Match the Sum, the player types the digits 2, 3 and 4. What should the program do?

Check your answer: Nothing is removed, because 2 plus 3 plus 4 is 9 and not 10. The program must show a message or let the player try again. It must not crash, which is why the specification asks you to take care of digits that do not add up to 10.

Exam traps

60-second revision

Where this chapter connects