Mid-Term Progress Review, Requirement Analysis & Architectural Design
Idea in plain words
Mid-Term Evaluation (30% Weightage): Comprehensive academic review assessing project progress, mentor feedback, and technical design artifacts.
Exam tip
High-yield exam topic (Very High).
Explanation
During the mid-term phase (weeks 6-8), students must demonstrate substantial system analysis and design progress. Mere coding without architectural documentation is heavily penalized. Students produce formal UML diagrams modeling system behavior and actor interactions. The host organization mentor submits a confidential progress evaluation report certifying the student's punctuality, code contributions, and team collaboration.
Key points
- Requirement Engineering: Documenting Functional Requirements (user actions) and Non-Functional Requirements (security, performance, scalability).
- Unified Modeling Language (UML) Modeling: Constructing Use Case diagrams, Sequence diagrams, Activity workflows, and Class diagrams.
- Database Architectural Design: Entity-Relationship (ER) modeling, normalization to 3rd Normal Form (3NF), indexing schemes, and foreign key integrity.
- Enterprise Tech Stack Selection: Justifying frontend frameworks, backend microservices, databases, and version control branching models.
Example
Example
Designing an authentication microservice: producing a UML Sequence Diagram showing client token request, OAuth 2.0 validation, database user lookup, and JWT response.
Code examples
/*
Mid-Term Evaluation Assessment Structure (30% Weightage):
Assessment Component | Marks
Host Organization Mentor Confidential Assessment | 10%
Requirement Analysis & System Design Documentation | 10%
Mid-Term Viva Voce & Prototype Demonstration | 10%
Total Mid-Term Score | 30%
*/
Exam questions
- [8 Marks] Explain the role of UML Class and Sequence diagrams in documenting the technical architecture of your internship project.
- [7 Marks] How are Non-Functional Requirements (NFRs) verified during mid-term technical design reviews?