Series Introduction – School Management System Course | Lesson 1
Introduction
Welcome to the course. In the next 100 or so lessons, you will build one real application from an empty folder: a School Management System. We will call it the SMS from now on.
This first lesson has no code. It shows you what you will build, in what order, and how each lesson works.
By the end of this lesson, you will be able to:
- Describe what the finished School Management System does.
- Explain the three parts of the course: SQL Server, C#, and ASP.NET Core Web API.
- Explain why we build the database first and the API last.
- Use every part of a lesson: code tags, homework, quiz, and interview levels.
Why this matters
Many learners watch tutorials for months and still cannot build anything alone. Each tutorial teaches one topic with its own tiny example. Nothing connects.
Interviewers notice this quickly. They rarely ask "What is a JOIN?" and stop there. They ask "Show me where you used a JOIN in your project, and why."
If you have no project, you have no answer.
In this course, every topic exists because the school needs it. You learn a JOIN because the class teacher needs a student list with roll numbers. You learn authentication because a parent must not see another child's marks.
At the end, you have one project you can explain from the database to the API.
The concept
A backend developer builds the parts of an application that users never see. That means the database that stores the data, the code that applies the rules, and the API that other apps call. The frontend is what users see and click, like a website or a mobile app.
Think of a school building:
- The database is the record room. Everything is stored there.
- The C# code is the school office. It applies the rules, like "a student cannot join two sections in the same year."
- The API is the front desk window. Parents and teachers never walk into the record room; they ask at the window.
Example: the three layers of the SMS
| Layer | Technology | Its job in the SMS |
|---|---|---|
| Database | SQL Server | Stores students, classes, attendance, marks, fees |
| Business logic | C# (.NET) | Applies school rules, calculates grades and dues |
| API | ASP.NET Core Web API | Lets websites and mobile apps read and change data safely |
An API (Application Programming Interface) is a set of addresses that other programs call to get or change data. You will build one in Module 10.
Example: why we build in this order
The course follows the order real teams use:
- Requirements first. You cannot design tables if you do not know what the school needs.
- Database second. The data lives longest. Apps get rewritten; school records stay for years.
- C# third. The code works with the tables you designed.
- API last. The API exposes the finished logic to the outside world.
Building in this order means you never write code for data that does not exist yet.
Apply it to the SMS
Here is what the finished SMS does. Every row is a module you will build.
Example: the SMS modules
| Module | What it does | Built in |
|---|---|---|
| Masters | Academic years, classes (Class 1 to 10), sections (A, B), subjects | Module 3 |
| Students and guardians | Admissions, student details, parents and guardians | Module 3 |
| Teachers | Teacher records and which subjects they teach | Module 3 |
| Enrollment | Places each student in a class, section, and roll number every year | Module 3 |
| Attendance | Daily attendance for every student | Modules 3 and 11 |
| Exams and marks | Exams, subject papers, marks, report cards | Modules 3 and 11 |
| Fees | Fee structures, invoices, payments, receipts | Modules 3 and 11 |
| Users and roles | Login for admin, principal, teachers, accountant, parents | Modules 3 and 12 |
| Dashboard | Today's numbers for the principal | Module 11 |
Our sample school is NexCoding Public School. It has Classes 1 to 10, with Sections A and B in each class.
You will meet the same teachers and students in every lesson. For example, Aarav Sharma is in Class 10-A with roll number 1, and his sister Advika is in Class 6-A.
Example: a day in the school
Follow one school day to see how the modules work together:
- 8:45 AM. Anitha Rao, class teacher of 10-A, opens the attendance screen. She marks Kabir absent. One row per student is saved in the attendance table.
- 11:00 AM. Aarav's father, Rajesh Sharma, pays the term fee online. The SMS records the payment and creates a receipt number.
- 2:00 PM. Anitha enters Mathematics marks for the unit test. The SMS refuses a mark of 105 when the paper is out of 100.
- 4:30 PM. The principal opens the dashboard. It shows today's attendance percentage and the fees collected today.
Every step uses all three layers: the screen calls the API, the API runs the C# rules, and the C# code reads or writes the database.
Example: how to use each lesson
Every lesson has the same parts, in the same order:
| Part | What you do there |
|---|---|
| Why this matters | Read the school problem the lesson solves |
| The concept | Learn the idea with one small example |
| Apply it to the SMS | Build it in the project, step by step |
| Common mistakes, In real projects | Learn what goes wrong at work |
| Homework | Build one piece of your own Library module |
| Quiz | Check yourself with 5 questions |
| Interview questions | Practise answers, marked by experience level |
| Resources | Get the code for that lesson |
Interview levels tell you who usually gets asked a question:
- F = Fresher (0 to 2 years)
- M = Mid level (3 to 5 years)
- S = Senior (6 to 9 years)
- A = Architect or Lead (10+ years)
A fresher should master the F questions and read the rest.
Code tags: the project's code is stored with a git tag for every lesson. A tag is a named bookmark in the code's history.
If you join at Lesson 30, you load the Lesson 29 tag and continue from there. You will set this up in Lesson 4.
Your own project: while the lessons build the SMS, you build a Library module for the same school on your own. It has books, copies, and book issues to students.
Common mistakes
- Skipping the database part. Many learners rush to C# and APIs. Then every query they write is slow or wrong. Fix: finish Modules 2 to 5 before C#.
- Copying code without running it. Reading code feels like learning, but it is not. Fix: type and run every block, and break it on purpose once.
- Skipping homework. Following along proves you can copy. Fix: do the Library task every lesson; that is where you actually learn.
- Jumping between courses. Each new course starts from zero again. Fix: finish one project end to end.
In real projects
In my interviews with freshers, the strongest candidates were rarely the ones with the most certificates. They had one project they could explain deeply. They knew why each table exists, what happens when two users save at once, and how they found a slow query.
That depth comes from building one thing completely, which is exactly what this course does.
On real teams, nobody starts with code either. The first weeks of a project are spent on requirements and data design, because a wrong table design costs months later.
Best practices
- Follow the lessons in order unless you already know a module well.
- Keep the SMS running on your machine at all times; fix errors before moving on.
- Do one Library task after every lesson.
- Say your interview answers out loud, not just in your head.
Recap
- You will build one School Management System from requirements to API.
- The course goes in order: requirements, SQL Server, C#, ASP.NET Core Web API.
- The database comes first because data outlives every application.
- Every lesson has the same parts, a git tag, homework, a quiz, and interview questions.
- Interview questions are marked F, M, S, or A by experience level.
- You build your own Library module alongside the SMS.
Homework
Library module task: Write down what a school library needs to do. List at least 5 features and the people who use it.
A correct result looks like: a short list of features, such as "issue a book to a student". Add 2 or 3 user types, such as "librarian".
Show a sample solution
Features:
- Add a new book with its title, author, and ISBN.
- Track how many copies of each book the library owns.
- Issue a copy to a student, with a due date.
- Record the return of a copy.
- Charge a fine when a copy is returned late.
- Show which copies are available right now.
Users: librarian, student, principal (for reports).
Quiz
Which part of the SMS stores attendance and marks permanently?
Show answer
Answer: B. The database The database stores the data; the other layers read and change it.
In what order does this course build the SMS?
Show answer
Answer: C. Database, C#, API Requirements and the database come first, C# next, and the API last.
What is an API?
Show answer
Answer: B. A set of addresses other programs call to get or change data Websites and mobile apps call API addresses instead of touching the database.
You join the course at Lesson 30. How do you get the project's code?
Show answer
Answer: C. Check out the Lesson 29 git tag Each lesson has a git tag that holds the project exactly as it is at the end of that lesson.
Which interview level is meant for a developer with 3 to 5 years of experience?
Show answer
Answer: B. M M stands for Mid level, 3 to 5 years.
Interview questions
Questions are grouped by experience level. Click a question to see a model answer. All questions: Architecture interview questions, Leadership interview questions.
Fresher (0-2 yrs)
F What does a backend developer do? concept
A backend developer builds the parts of an application that users never see: the database, the business rules, and the APIs that apps call. They are responsible for data being correct, safe, and fast. In a School Management System, that means the attendance tables, the rule that marks cannot exceed the maximum, and the API the mobile app uses.
F What is the difference between frontend and backend? concept
The frontend is what users see and click: a website or mobile app running on their device. The backend runs on a server: it stores data, applies business rules, and exposes APIs. The frontend never touches the database; it calls the backend over HTTP.
F Tell me about a project you have built. behavioral
Use a clear structure: the problem, who uses it, your role, the technology, one hard problem you solved, and the result. Keep it to about two minutes. For example: "I built a School Management System with SQL Server, C#, and ASP.NET Core. The hardest part was making sure attendance could not be saved twice for the same student and day."
Mid (3-5 yrs)
M Why do teams usually design the database before writing application code? concept
Data outlives applications: screens and services get rewritten, but school records stay for years. The tables decide what the code can do, and changing a table after real data exists means migrating that data. Designing the data model early also exposes missing requirements, such as a student having two guardians, before any code depends on them.
M How would you split a School Management System into modules? design
Split it by business capability: masters (years, classes, sections, subjects), students and guardians, enrollment, attendance, exams and marks, fees, users and roles, and a dashboard. Each module owns its tables and endpoints. Note the dependencies: attendance, marks, and fees all depend on enrollment, so masters and enrollment are built first.
M How do you explain your project's architecture in an interview? behavioral
Go layer by layer from the user to the data: the client, the API, the business logic, and the database, naming the technology for each. Then follow one real request through all of them, such as a teacher saving attendance. Finish with one design decision and why you made it.
Senior (6-9 yrs)
S What makes a project production-ready rather than tutorial-level? concept
A production-ready system enforces its rules on the server and in the database, not only on the screen. It handles two users saving at once, records who changed what, restricts data by role, logs errors, has tests, and stays fast with realistic data volumes. A tutorial usually shows only the happy path with ten rows.
How to answer: Start with the definition (rules, security, reliability, performance, observability). Then give SMS examples: marks above the maximum are refused by the database, receipt numbers are unique even with double clicks, every marks change is audited. Finish with the trade-off: you cannot build everything at once, so say what you would add first (data integrity and security) and what can wait (caching, advanced monitoring).
S The school wants attendance, fees, exams, transport and hostel modules live in three months with two developers. What do you build first? scenario
Order the work by dependency and value. Masters, students, and enrollment come first because every other module needs them. Then attendance (used every day) and fees (money and legal records), then exams. Transport and hostel move to a later phase, and the agreed scope is written down and delivered in small increments.
How to answer: Name the principle (dependencies first, then business value and risk). Walk through the SMS module order with the reason for each. Then state the trade-off honestly: cutting scope is acceptable, cutting data integrity or security is not, and the client must agree in writing to what moves to phase two.
Resources
- Code for this lesson: git tag
lesson-1-series-introduction(code repository coming soon) - Video: coming soon
What's next
Next, you will see how a client, an API, and a database talk to each other when a teacher opens a student list. Lesson 2: How a client, an API and a database work together
Want live sessions, code reviews, and interview preparation? Join the next batch at Sahasra Technologies.