System design and implementation plan notes — Unit 2
Free unit-wise study notes on system design and implementation plan for Major Project, Semester 8 of B.Tech — Computer Science & Engineering — key concepts, examples, important questions and a revision checklist for semester exams.
Translating the abstract problem statement into a concrete architectural blueprint using UML, database schemas, and rigorous implementation scheduling.
Notebook — 5 pages
Page 1
Wink Notes
B.Tech CSE — 8th Semester
Major Project
— Unit - 2 —
1. System Architecture Design
System Design is the process of defining the architecture, modules, interfaces, and data for a system to satisfy specified requirements. This phase converts the 'What' from Unit 1 into the 'How'.
⇒1.1 High-Level Architecture
The High-Level Design (HLD) provides a 'bird's-eye view' of the system. For a modern CSE project, this typically involves defining the distribution of components:
Client-Server Architecture: Web/Mobile frontend communicating with a backend via REST/GraphQL APIs.
Microservices: Breaking the backend into independent, loosely coupled services (e.g., Auth Service, Processing Service).
Cloud/Edge Infrastructure: Deciding where ML models will run (e.g., inferencing on a Raspberry Pi vs. deploying to AWS SageMaker).
Page 2
Wink Notes
B.Tech CSE — 8th Semester
Major Project
— Unit - 2 —
2. UML Structural and Behavioral Modeling
Unified Modeling Language (UML) diagrams are mandatory in the Major Project design document. They provide a standardized visual vocabulary.
Diagram Type
Category
What it shows in the Report
Use Case Diagram
Behavioral
Interactions between 'Actors' (users/systems) and the system. Defines scope boundaries.
Class Diagram
Structural
The object-oriented backbone. Shows classes, attributes, methods, and relationships (Inheritance, Aggregation).
Sequence Diagram
Behavioral
The exact chronological flow of messages between objects (e.g., tracing a login request from UI to Database and back).
Deployment Diagram
Structural
The physical mapping of software nodes onto hardware/cloud servers.
Page 3
Wink Notes
B.Tech CSE — 8th Semester
Major Project
— Unit - 2 —
3. Database Schema and Storage Design
Data persistence must be rigorously planned before coding begins.
⇒3.1 Relational (SQL) vs Non-Relational (NoSQL)
The choice of database must be justified in the design document.
RDBMS (PostgreSQL, MySQL): Chosen when data has strict schemas, requires complex table joins, and demands ACID compliance (e.g., financial transactions). Modeled using ER Diagrams.
NoSQL (MongoDB, Firebase): Chosen for unstructured data, rapid schema iteration, or highly nested JSON documents (e.g., social media feeds, IoT telemetry).
Object Storage (AWS S3): Required for storing large binary blobs like user-uploaded images, videos, or raw datasets.
Page 4
Wink Notes
B.Tech CSE — 8th Semester
Major Project
— Unit - 2 —
4. Implementation Plan and SDLC
A project without a timeline is just an idea. You must select a Software Development Life Cycle (SDLC) model and map out the timeline.
⇒4.1 Agile Methodology
Most modern projects use Agile (specifically Scrum or Kanban) rather than Waterfall. The implementation plan should divide the 6 months into 2-week 'Sprints'.
⇒4.2 The Gantt Chart
A Gantt chart is a visual timeline required in almost all project reports. It plots tasks on the Y-axis against time (weeks/months) on the X-axis, showing dependencies (e.g., you cannot start 'Frontend Integration' until 'Backend API' is complete).
Page 5
Wink Notes
B.Tech CSE — 8th Semester
Major Project
— Unit - 2 —
5. Unit Summary and Evaluation Focus
Unit 2 corresponds to the 'First Internal Review' (Architecture Presentation).
Justification: Evaluators will ask why you chose a specific stack (e.g., 'Why use MongoDB instead of SQL for this data?'). 'Because it's easier' is not an acceptable engineering answer. You must cite performance, scalability, or data structure requirements.
Diagram Accuracy: Ensure arrow directions in UML are correct (e.g., Inheritance arrows point to the parent).
Timeline Feasibility: The Gantt chart must look realistic. Leaving 1 week for testing at the end of a 6-month project is an immediate red flag.
