1Course specification
The official document for one course: title, code, credits, a summary, the Course Outcomes, the unit-wise syllabus, teaching hours, the assessment plan, the CO-PO-PSO map and resources. Many people edit it over the years, so mistakes creep in. Your app reads the messy one and produces a corrected one.
2Credits: L:T:P
Lecture : Tutorial : Practical. 3:0:1 means 3 lecture, 0 tutorial, 1 practical. A non-zero Practical means the course has a lab, so it uses the Integrated template. Otherwise it uses the Non-Lab template.
3Question-paper blueprint
A second document listing the Course Outcomes and units for the same course. When you have both, the blueprint decides the COs and the syllabus. Everything else comes from the existing spec.
4Course Outcome (CO)
What a student can do at the end of the course, written as a verb plus content. Example: "Explain how a stack stores data." A course has a handful, numbered CO-1, CO-2 and so on.
5Bloom's level
How deep a CO goes, taken from its first verb.
| Level | Name | Typical verbs |
| 1 | Remember | define, list, recall, state |
| 2 | Understand | explain, describe, summarise, classify |
| 3 | Apply | apply, solve, use, implement |
| 4 | Analyse | analyse, compare, differentiate, select |
| 5 | Evaluate | evaluate, assess, justify, critique |
| 6 | Create | design, develop, build, construct |
6PO and PSO
PO (Programme Outcome): broad abilities the whole degree builds, PO-1 to PO-11 (PO-3 is about design, PO-5 about using tools).
PSO (Programme Specific Outcome): abilities specific to this programme, PSO-1 and PSO-2. Exact wording: Annexure A in the Kit.
7The CO-PO-PSO map
How strongly each CO supports each PO and PSO. Rows are COs, columns are POs and PSOs. 3 very strong, 2 strong, 1 moderate, blank = no link.
| CO (fictional) | Bloom | PO-1 | PO-3 | PO-5 | PSO-1 |
| CO-1 Explain data structures | 2 | 3 | | | 1 |
| CO-2 Implement a sorting routine | 3 | 2 | 2 | 3 | 2 |
| CO-3 Design a small app | 6 | 1 | 3 | 3 | 3 |
Every filled cell needs a one-line reason. A low Bloom's level ("Explain") cannot map strongly to design (PO-3). Tool use (PO-5) needs a real lab or programming activity.
8Defects
Mistakes inside the messy spec: hours that don't add up, a CO in one table but missing from another, text left over from a different course. Finding them is Level 4.
9What your app does, in five steps
- Read the spec (and blueprint).
- Pick the template.
- Fill it with the right COs and units.
- Build the CO-PO-PSO map with reasons.
- Export the output file and spec document, run
npm run verify, submit.