CampusConnect: Interactive Educational Module
Budget: $30 – $250 USD
Project: Software Architecture Design for “CampusConnect”
I need a freelancer to create a complete software architecture design report for a university management system called CampusConnect.
The project has 4 phases, and the final output is one integrated report with all diagrams and explanations. All diagrams must be made using draw.io.
Scope of Work
Phase 1: Requirements & Use Cases
Identify 6+ core use cases
Draw UML Use Case Diagram
List 20+ Functional Requirements (FRs)
List 5+ Non-Functional Requirements (NFRs) with short explanations
Phase 2: Architectural Style Selection
Choose 1–2 architectural styles (e.g., Layered, Client-Server, Microservices, etc.)
Explain why this style fits the system based on NFRs
Provide a clear written rationale
Phase 3: Components & Class Design
Identify 5+ major system components
Create an Initial UML Component Diagram
Reorganize components according to the chosen architectural style and make an Updated Component Diagram
For 3 major components, create UML Class Diagrams showing internal classes
Apply at least 3 design patterns (e.g., Singleton, Factory, Observer) and label them
Provide a brief justification for each design pattern used
Phase 4: Deployment Model
Identify physical nodes (client, server, DB, etc.)
Map which components/artifacts run on each node
Draw a UML Deployment Diagram
Add annotations (communication paths, protocols, etc.)
Final Deliverable
A single, clean, well-organized report containing:
Use Case Diagram
FR & NFR lists
Architectural style descriptions + rationale
Initial & Updated Component Diagrams
3 Class Diagrams with design patterns labeled
Deployment Diagram
All diagrams must be UML and made in draw.io
Rest info is included in the 3 docs please see them .
I need a freelancer to create a complete software architecture design report for a university management system called CampusConnect.
The project has 4 phases, and the final output is one integrated report with all diagrams and explanations. All diagrams must be made using draw.io.
Scope of Work
Phase 1: Requirements & Use Cases
Identify 6+ core use cases
Draw UML Use Case Diagram
List 20+ Functional Requirements (FRs)
List 5+ Non-Functional Requirements (NFRs) with short explanations
Phase 2: Architectural Style Selection
Choose 1–2 architectural styles (e.g., Layered, Client-Server, Microservices, etc.)
Explain why this style fits the system based on NFRs
Provide a clear written rationale
Phase 3: Components & Class Design
Identify 5+ major system components
Create an Initial UML Component Diagram
Reorganize components according to the chosen architectural style and make an Updated Component Diagram
For 3 major components, create UML Class Diagrams showing internal classes
Apply at least 3 design patterns (e.g., Singleton, Factory, Observer) and label them
Provide a brief justification for each design pattern used
Phase 4: Deployment Model
Identify physical nodes (client, server, DB, etc.)
Map which components/artifacts run on each node
Draw a UML Deployment Diagram
Add annotations (communication paths, protocols, etc.)
Final Deliverable
A single, clean, well-organized report containing:
Use Case Diagram
FR & NFR lists
Architectural style descriptions + rationale
Initial & Updated Component Diagrams
3 Class Diagrams with design patterns labeled
Deployment Diagram
All diagrams must be UML and made in draw.io
Rest info is included in the 3 docs please see them .