AI Career Coach Project Report (SensAI)

1. PROBLEM STATEMENT

1.1 Identify the Software Project Problem Statement: SensAI aims to provide intelligent,
personalized career coaching using AI. The goal is to assist users with resume building, cover
letters, mock interviews, and insights tailored to specific career paths. This project bridges the
gap between traditional career counseling and modern digital tools. It empowers job seekers to
make informed career decisions through guided, AI-driven experiences.

1.2 Create Business Class Template: Defines business processes and entities involved,
including users, career goals, and coaching components. It ensures system alignment with
business goals. The template maps interactions between system actors and backend
processes. This acts as the foundation for requirement gathering and interface development.

2. STAKEHOLDERS & PROCESS MODELS

2.1 Identifying Stakeholders: Primary stakeholders include job seekers and recent graduates,
while secondary ones are employers and career counselors. Stakeholder input helps shape
system functionalities. Understanding each stakeholder’s role enhances feature prioritization.
This ensures the system meets diverse user expectations.

2.2 User Story: "As a user, I want to generate a personalized resume so that I can apply for
jobs more effectively." User stories help define key features from the perspective of end users.
They assist developers in designing relevant use cases. Additionally, they guide UI/UX
workflows for a smoother user journey.

2.3 Identify the Appropriate Process Modules: Modules include: Resume Builder, Cover
Letter Generator, Mock Interview Simulator, and Analytics Dashboard. Each module supports
specific user objectives within the platform. The modular structure promotes system flexibility
and easy maintenance. It also supports future feature expansion.

2.4 Arrive at Problem Statement: Many individuals lack access to personalized career
coaching services. SensAI fills this gap using AI tools and automation. By defining this problem,
the project focuses development efforts effectively. Clarity at this stage ensures the solution
addresses real-world needs. It also helps secure stakeholder buy-in.

2.5 Comparison between Agile and Waterfall Model: Agile development is preferred due to
its iterative nature and adaptability to changing user needs. Waterfall, being rigid, is less suitable
for projects with evolving AI models. Agile supports continuous feedback integration. It allows
for quick pivoting based on test results and user feedback.
3. IDENTIFYING THE REQUIREMENTS

3.1 Requirements: The software must deliver AI-based career tools including interactive
resume generators and simulated interviews. Requirements encompass functionality,
performance, and platform compatibility. Gathering clear requirements avoids project
misdirection. They serve as a baseline for tracking progress.

3.2 Functional Requirements:

●​ User Login and Role Management

●​ Resume Generation and Editing
●​ Interview Question Generation and Response Analysis
●​ Analytics Dashboard with Career Insights Functional requirements define core software
behavior. They act as acceptance criteria for completed features.

3.3 Non-Functional Requirements:

●​ High system availability

●​ Secure data storage
●​ Fast response time for AI tools These improve system usability, reliability, and security.
They also affect customer satisfaction and retention.

3.4 Hardware Requirements: Client: Modern browser-enabled device. Server: Node.js

compatible environment, cloud support for hosting. Minimal requirements ensure wide
accessibility. Cloud solutions enable horizontal scaling.

3.5 Software Requirements: Next.js 15, React 19, Tailwind CSS, Prisma ORM, Gemini API,
and NeonDB. These modern tools support fast, scalable web development. They also integrate
easily with third-party services and APIs.

4. PROJECT PLAN AND EFFORT

4.1 Project Plan: The plan includes sprint-based development, weekly task reviews, and
frequent deployments. Each sprint focuses on building or refining a feature. Tracking tools (e.g.,
Trello) manage tasks and timelines. Milestones are clearly defined for progress assessment.

4.2 Identifying Job Roles and Responsibility: Roles include: Frontend Developer, Backend
Developer, AI Specialist, UI/UX Designer, QA Tester, Project Manager. Clear role assignment
increases development efficiency. Responsibilities are distributed to ensure parallel work
streams. Team collaboration is encouraged via regular stand-ups.
5. PROJECT EFFORT BASED ON RESOURCES

5.1 Work Breakdown Structure: Tasks are broken into manageable units such as UI design,
authentication setup, resume module, and testing. Each task is time-bound with defined
deliverables. This method improves visibility into team progress. It ensures resource allocation
aligns with task complexity.

5.2 Risk Management: Risks include API rate limits, AI hallucinations, and data security
threats. Each risk is evaluated with a mitigation plan. Monitoring tools and fallback systems are
prepared. Risk logs are updated weekly for transparency.

6. ESTIMATION OF PROJECT METRICS

6.1 Function Point Analysis: Estimates project size by counting inputs, outputs, files, and
queries. This helps evaluate required effort and cost. Adjustments are made based on
complexity levels. It serves as a project sizing technique.

6.2 COCOMO Model: The Constructive Cost Model estimates effort using project size and
complexity. This project is categorized as an organic model with low constraints. Effort = a *
(KLOC)^b where KLOC = estimated lines of code. This model improves planning and budgeting.

7. DESIGN

7.1 System Architecture: SensAI uses a client-server architecture with API routing. Frontend
communicates with backend via REST and AI calls. It supports modular components for
scalability. The architecture separates concerns for better fault isolation. It also facilitates CI/CD
integration.

8. UML USE CASE & SCENARIOS

8.1 Use Case Description: Key use cases: Resume generation, interview simulations, and
insights tracking. Each use case maps a core user objective. Helps developers understand
scope and system limits. Supports end-to-end testing later.

8.2 Use Case Diagram: Actors: User, AI Module, PDF Exporter. Use Cases: Authenticate,
Create Resume, Conduct Interview. Illustrates functional boundaries and interactions. Aids in
visualizing user flow. It also supports early-stage design decisions.

9. ER MODELING
9.1 ER Diagram Description: Represents relationships among users, resumes, interviews, and
feedback. Entities have unique keys and mapped attributes. Logical relationships are
established for queries. Design supports a normalized database.

9.2 ER Diagram: Tables: Users, Resumes, Interview_Responses, AI_Feedback. Relationships:

One-to-many and many-to-one. Visual tool for understanding backend structure. ERDs reduce
redundancy and improve performance.

10. DOMAIN CLASS DIAGRAM

10.1 Domain Class Description: Models business logic via classes like User, ResumeBuilder,
InterviewSimulator. Includes attributes and methods. Defines the interaction between classes.
Used to derive backend schemas.

10.2 Domain Class Diagram: Shows inheritance and associations. User → ResumeBuilder →
PDFExporter. It enhances system abstraction. Useful for object-oriented design and planning.

11. STATECHART & COMMUNICATION

11.1 State Chart Description: Represents user session states: Logged Out → Logged In →
Resume Editing → Report Viewed Transitions are triggered by specific actions. Useful in
defining UI navigation. Ensures logical state transition control.

11.2 State Chart Diagram: Depicts allowed and restricted states based on authentication.
Supports validation of business logic. Useful for session timeout logic.

11.3 Communication Diagram: Illustrates object interactions: Frontend → API Server → AI

Engine → DB Describes how components communicate. Useful in backend flow validation.
Ensures consistency in data handoff.

12. CLASS & SEQUENCE DIAGRAMS

12.1 Class Diagram Description: Models relationships between system classes. Clarifies
which components hold data or perform actions. Important during system decomposition.
Supports maintainability.

12.2 Class Diagram: Includes UI components (Form), Logic (ResumeService), Storage

(DatabaseHandler) Displays attributes and methods. Defines clear interfaces and operations.
12.3 Sequence Diagram Description: Illustrates how objects collaborate over time. Describes
event flow during tasks like Resume Download. Used to refine backend logic. Enables better
API design.

12.4 Sequence Diagram: Example: User submits form → ResumeService → Gemini →

Response stored Defines message passing order. Improves synchronization between
components.

13. DATA FLOW DIAGRAM

13.1 DFD Description: Depicts flow of data across system processes. DFDs simplify
understanding of input/output. Useful for validating processing logic. Supports compliance with
data regulations.

13.2 Data Flow Diagram: Processes: Login, ResumeGen, InterviewSim. Data Stores:
UserData, Feedback Connects user actions with internal processes. Shows where
transformation or decision-making occurs.

14. IMPLEMENTATION

14.1 Module Implementation: React handles frontend UI; API routes perform backend logic;
Prisma communicates with NeonDB. Gemini API is used for AI interactions. Modular
components enhance maintainability. Deployment via Vercel for continuous integration.

15. TEST COVERAGE & COMPLEXITY

15.1 Control Flow Graph: Shows paths through resume and interview logic blocks. Helps
identify untested code. Used for cyclomatic complexity calculations. Enables better coverage
tracking.

15.2 McCabe’s Cyclomatic Complexity: Measures decision points in code. Ensures functions
are not overly complex. Target complexity < 10 for easier maintenance. Supports modular code
design.

15.3 Optimum Value: Maintained by splitting large functions. Promotes readability and
testability. Complexity tracked throughout development.

16. DESIGNING TEST SUITES

16.1 Software Testing: Unit, integration, and UI testing with Jest and Cypress. Covers both
happy and edge case paths. Ensures confidence in deployment. Verifies expected behavior
across modules.

16.2 Testing Frameworks: Jest: Logic layer, Prisma calls. Cypress: Form interactions,
download flows. Supports test automation. Integrated with CI tools.

16.3 Master Test Plan: Documents what to test, how, when, and by whom. Outlines test
objectives, tools, environments. Ensures structured testing across phases. Guides bug reporting
process.

16.4 Manual Testing: Performed for usability and exploratory testing. Validates user experience
and unexpected behaviors. Manual testing captures UI/UX defects. Used before every
deployment.

17. CONCLUSION

SensAI presents a comprehensive AI-based career guidance system with tools for resume
building, interview preparation, and personalized advice. Built with modern tech, it offers
scalable and interactive career support. Project meets design, performance, and functionality
goals. It is ready for user onboarding and feedback collection.

18. REFERENCES

●​ Gemini API Documentation

●​ Next.js Official Documentation
●​ Prisma ORM Official Docs
●​ Clerk Auth Documentation Citations ensure accuracy in architecture and logic. They
serve as a guide for future developers.