Skip to main content

Project Timeline

The DEVision Job Manager subsystem development is divided into two major milestones with specific deliverables and requirements.

Milestone 1: Design Documentation

Due Date

18:00 on November 28, 2025

Overview

Milestone 1 focuses on system design and architectural planning. Teams must document design decisions and justifications in a comprehensive technical report.

Deliverables

Comprehensive documentation covering:
  • Data Model design and justifications
  • System Architecture diagrams and rationale
  • Design decisions for frontend and backend
  • Advantages and limitations of chosen approach
Note: Page count does NOT include cover page and table of contents
Entity Relationship (ER) Model including:
  • High-level database schema representation
  • All necessary entities and relationships
  • Data elements essential for system functionality
  • Design explanations and justifications
Advantages and drawbacks must be in ONE designated section (2 points penalty if scattered)
Choose one of two options:Option 1: UML Component Diagram
  • System level diagram (subsystems only)
  • Backend architecture diagram
  • Frontend architecture diagram
Option 2: C4 Model
  • System Context diagram
  • Container diagram
  • Component diagrams (Backend and Frontend)
All diagrams must show:
  • Component roles and responsibilities
  • Interaction patterns
  • Layer-based, Modular, or Microservice design
Evidence of frequent, professional GitHub usage:
  • Regular commits throughout the project
  • Appropriate commit messages
  • Professional communication
  • Team collaboration evidence
NOT using GitHub frequently: Up to 10 points penalty Missing contribution proof: 3 points penalty

Technology Analysis

Teams must analyze and decide on technologies:

Frontend Options

  • React-based frameworks (React, Vite, Next.js)
  • Vanilla HTML, CSS, and JavaScript

Backend Options

  • MEN Stack (MongoDB, ExpressJS, NodeJS)
  • Spring Boot
  • Redis and Kafka for messaging

Deployment Options

  • Docker
  • Kubernetes (Bonus)

Architecture Justification

Design justifications must address six key aspects:

Maintainability

Easily understood, updated, and tested by current and future teams

Extensibility

New features added with minimal impact on existing components

Resilience

Continues functioning under unexpected conditions and failures

Scalability

Handles increased load without sacrificing performance

Security

Protected from unauthorized access and data breaches

Performance

Quick and efficient response to requests

Presentation Requirements

1

System Overview

Present system architecture and data model
2

Feature Architecture

Explain how architecture provides job posting, searching, application, and approval features
3

Design Justification

Justify advantages and limitations of design choices
4

Individual Q&A

Each member answers questions about their contributions
Members who cannot explain sections they contributed to will be penalized.

Submission Requirements

Milestone 2: Implementation & Deployment

Due Date

18:00 on January 13, 2026

Overview

Milestone 2 focuses on implementing the designed architecture with full functionality and deploying the integrated system.

Implementation Requirements

Required Technologies

  • Frontend
  • Backend
  • Deployment
  • React-based framework (React, Vite, Next.js)
  • Vanilla HTML, CSS, and JavaScript
  • Responsive design (desktop and mobile)

Functional Requirements

All features must be implemented according to chosen complexity level:

Simplex (Basic)

  • N-Tier architecture
  • Basic authentication
  • Core CRUD operations
  • Simple search functionality

Medium

  • Modular Monolith
  • Componentized frontend
  • Advanced validation
  • Full-text search
  • Internal/External APIs

Ultimo (Advanced)

  • Microservices architecture
  • Headless UI components
  • Database sharding
  • API Gateway and Service Discovery
  • Real-time Kafka notifications

Database Initialization Script

Must include initial data:
-- 1 ADMIN account
INSERT INTO users (role, email, ...)
VALUES ('ADMIN', 'admin@devision.com', ...);

API Integration

APIs to Provide

Company Profile API

Public company profile data

Job Post API

Job posting data and management

Payment API

Subscription payment processing

Authorization API

Authentication and authorization

APIs to Consume

Applicant Profile API

Job seeker profile data

Job Application API

Application submissions and tracking

Job Applicant Auth API

Cross-system authorization

Deployment Requirements

  • Simplex
  • Medium
  • Ultimo
  • Frontend and backend deployed in development
  • Communication with Job Applicant system
  • API integration working

Presentation Requirements

1

System Demo

Deploy and demonstrate integrated DEVision system
2

Feature Showcase

Show all implemented functional requirements
3

API Integration

Demonstrate API provision and consumption
4

Individual Q&A

Answer questions about development contributions
Members who cannot explain their contributions will have corresponding grades deducted.

Quality Standards

All implementations must meet:
  • No OWASP Top 10 vulnerabilities
  • Proper input validation (frontend and backend)
  • Secure password storage
  • JWE token implementation
  • Brute-force protection
  • Lazy loading for search results
  • Optimized database queries
  • Efficient sharding implementation
  • Redis caching where appropriate
  • Follows architectural patterns
  • Clean, maintainable code
  • Proper error handling
  • Comprehensive documentation

Penalties

Failure to meet requirements results in grade penalties:
  • P1: Not using GitHub frequently: Up to 10 points
  • P2: Missing GitHub contribution proof: 3 points
  • P3: Not submitting repository zip file: 3 points
  • P4: Not submitting Project Charter: 3 points

Success Criteria

To successfully complete the project:

Resources