Free unit-wise study notes on development and integration for Major Project, Semester 8 of B.Tech — Computer Science & Engineering — key concepts, examples, important questions and a revision checklist for semester exams.
The execution phase where the architectural designs are coded into functional modules, version controlled, and integrated into a single cohesive system.
Notebook — 4 pages
Page 1
Wink Notes
B.Tech CSE — 8th Semester
Major Project
— Unit - 3 —
1. Development and Version Control
Development is the process of writing the actual code. Unlike junior-year assignments, a Major Project must be built using industry-standard collaboration tools.
⇒1.1 Git and Version Control
Version Control Systems (VCS) like Git are mandatory. They allow multiple team members to work on the same codebase simultaneously without overwriting each other's work.
Branching: Never commit directly to `main`. Create feature branches (e.g., `feature/user-auth`) for new work.
Pull Requests (PRs): Once a feature is done, open a PR to merge it into `main`. This allows teammates to review the code before it becomes part of the final project.
Commit Messages: Must be semantic and descriptive. 'Fixed bug' is unacceptable. 'Fix: resolved race condition in payment gateway' is correct.
Page 2
Wink Notes
B.Tech CSE — 8th Semester
Major Project
— Unit - 3 —
2. Modular Development and Clean Code
The project must be broken down into discrete modules developed independently.
⇒2.1 Clean Code Principles
DRY (Don't Repeat Yourself): Abstract repetitive logic into reusable functions or components.
Separation of Concerns: The UI code should not directly query the database. Use layered architectures (e.g., MVC or Controller-Service-Repository).
Environment Variables: Never hardcode API keys, database passwords, or URLs in the source code. Use `.env` files.
Page 3
Wink Notes
B.Tech CSE — 8th Semester
Major Project
— Unit - 3 —
3. System Integration
Integration is often the most painful part of the project. This is where the frontend (built by Student A) must connect to the backend (built by Student B) and the ML model (built by Student C).
⇒3.1 API Contracts
Integration fails when teams don't agree on data formats. An API Contract (often documented in Swagger/OpenAPI or Postman) dictates exactly what JSON the frontend will send, and exactly what JSON the backend will return.
⇒3.2 Continuous Integration (CI)
Setting up automated pipelines (like GitHub Actions) to automatically build the project and run tests every time someone pushes code. If the code fails the build, it cannot be merged.
Page 4
Wink Notes
B.Tech CSE — 8th Semester
Major Project
— Unit - 3 —
4. Unit Summary and Evaluation Focus
Unit 3 corresponds to the 'Second Internal Review' (Implementation Progress).
Live Demo: You will usually be asked to show a working sub-module (e.g., 'Show me the login flow working against the live database.').
Code Walkthrough: Evaluators will open your IDE and ask you to explain specific blocks of code. They are checking for plagiarism and verifying that you actually wrote it.
Git History: A strong team will show a rich Git commit history across all team members. If all commits belong to one person, the team will be penalized for poor contribution distribution.
