Simple Job board system

INTRODUCTION

This document defines the Software Requirements Specification (SRS) for a Simple Job Board
System. It outlines the software process model used, project objectives, and detailed
requirement analysis for designing and building the system.

Product Scope

The Simple Job Board System allows employers to post job listings and job seekers to browse,
apply, and manage applications. The system will support job search filtering, resume upload,
employer dashboards, and admin management.
Goals:
Simplify the hiring process for employers
Provide job seekers easy access to relevant job opportunities
Serve as a platform to manage the hiring lifecycle digitall

Product Value

This system saves time, reduces paperwork, and centralizes job listings in one place. It offers
value to both employers (by streamlining job posting and applicant management) and job
seekers (by offering filters and resume management tools).
Helps Intended Audience By:
Enabling faster application and hiring processes
Reducing the communication gap between job seekers and recruiters
Providing a simple user-friendly experience

Intended Audience

Primary Users: Job Seekers and Employers

Secondary Users: Admin users managing the platform
Other Stakeholders: HR teams, project sponsors, developers, testers

Intended Use

Job Seekers: Search, filter, and apply for jobs; upload resumes
Employers: Post jobs, review applicants, contact selected candidates
Admin: Monitor system performance, moderate content, manage user roles
Requirement Analysis

Functional Requirements:
User Authentication (Job seeker, Employer, Admin)
Job CRUD (Create, Read, Update, Delete)
Application tracking system

Non-Functional Requirements:
User-friendly UI
Scalable database
Secure login (password hashing)

Choice of Software Process Model

Selected Model: Agile Model

Why Agile?
Iterative development allows regular updates and feedback
Stakeholder involvement during development ensures alignment
Adaptive to changes in user needs

Project Scope & Objectives

Scope:
Develop a minimal, web-based job board system with core functionalities for
employers and job seekers.

Objectives:
Cover major modules: User login, job posting, and application tracking
Ensure responsive design and basic security practices
 TEST PLAN

SELECTION DESCRIPTION

Test Plan Name Simple Job Board System - Test Plan

To validate the core functionalities of the job

Objective
board system through manual testing

Includes user registration, job posting, job

Scope
application, admin login, and job search filters

Manual testing using black-box technique and

Test Strategy
exploratory testing; UI-based test cases

Pass: System meets expected output under valid

Test Criteria conditions
Fail: System does not behave as expected

Test Test Plan Document, Test Cases, Test Results

Deliverables Report

Resource Test environment, Test data, Browsers (Chrome,

Requirements Firefox), SQL DB, QA team

- Incomplete test coverage

Risk Analysis
- Last-minute requirement changes

Assumptions System is fully deployed and stable for testing

Backend APIs, Database connectivity, Admin

Dependencies
access setup
 Test Case 1

Test Title User Registration

Priority High

Test Case ID TC-001

Test Description Verify that users can successfully register

Test Dependencies Database connectivity

Test Conditions All mandatory fields must be filled correctly

Test Control Manual testing in Chrome browser

Step ID Step Description Test Date Expected Results Actual Results Pass/Fail

Enter user details "Registration Successful"

1
& submit 30 May 2… message shown
As expected Pass
 Test Case 2

Test Title Job Posting (Employer)

Priority High

Test Case ID TC-002

Validate employer can post a job with title, description, and

Test Description
category

Test Dependencies Database connectivity

Test Conditions All mandatory fields must be filled correctly

Test Control Manual testing in Chrome browser

Step ID Step Description Test Date Expected Results Actual Results Pass/Fail

1 Login as Employer 31 May 20… Redirect to dashboard As expected Pass

2 Fill job post form 31 May 20… "Job posted successfully" As expected Pass
 Test Case 3

Test Title Apply to a Job

Priority High

Test Case ID TC-003

Test Description Ensure job seekers can apply to available job posts

Test Dependencies Database connectivity

Test Conditions All mandatory fields must be filled correctly

Test Control Manual testing in Chrome browser

Step ID Step Description Test Date Expected Results Actual Results Pass/Fail

Dashboard with
1 Login as job seeker 1 Jun 2025 As expected Pass
job listings

"Application submitted"
2 Click on "Apply" button 1 Jun 2025 As expected Pass
message
 AGILE PRACTICES FOLLOWED

PRACTICE APPLICATION IN PROJECT

Daily Standups Regular status check meetings to track progress

Divided development into 2-week sprints (UI,

Sprint Planning
Backend, Testing)

Backlog
Maintained task list in a Kanban board
Management

Continuous
Local testing after every major feature
Integration

Reviewed what worked and what didn’t after each

Retrospectives
sprint
 STAKEHOLDER IDENTIFICATION

Role/
STAKEHOLDER POWER IMPACT CATEGORY
Interest

Oversees
Manage
Project Manager development & High High
delivery
Closely

Job Seekers Main users looking Keep

Low High
(Users) for jobs Informed

Post jobs and seek Manage

Employers talent
High High
Closely

Design the job Keep

UI/UX Designers board interface
Medium Medium
Satisfied

Build the Manage

Developers backend/frontend
Medium High
Closely

Test the system for

QA Testers bugs
Low Medium Monitor

Faculty evaluating
Academic Keep
project High Low
Evaluator performance
Satisfied
 PROJECT PLAN

PHASE DURATION
Tasks

Requirement Stakeholder meetings, define scope,

1 week
Analysis SRS creation

UI wireframes, database schema,

Design 2–3 weeks
architecture decisions

Frontend and backend

Development implementation (login, register, job 1 week
post, etc.)

Functional testing, usability testing,

Testing 1 week
bug fixing

Deploy on local server or hosting

Deployment 2–3 weeks
platform

Review & Final documentation, stakeholder

2–3 weeks
Documentation review

Project Objectives

User Registration/Login – Enable secure user access.

Job Posting by Employers – Allow employers to post job listings.
Job Search by Users – Search and apply for jobs easily.
Admin Panel – Manage users, jobs, and feedback.
Responsive Design – Ensure usability on multiple devices.
Basic Analytics – Show application trends, active jobs, etc.
 SUCCESS METRICS

METRIC Target Value

User registration time < 30 seconds

Average job post success rate > 90%

User satisfaction score (UI ≥ 4 out of 5

feedback)

System uptime > 99% during active hours

Bug resolution time < 48 hours

Number of successful
100+ within 1 month (test phase)
applications
 Gantt Chart
Activity DAY 1-3 Day 4-6 Day 7-13 Day 14-16 Day 17 Day 18-19 Day 20

Requirement Analysis

Design (UI + DB)

Development

Testing

Deployment

Documentation

Project Review
 SOFTWARE QUALITY PLAN

ASPECT DETAILS

Bug-free user registration, secure login,

Quality Goals responsive design, error handling

Standards Followed ISO 9126 (functionality, usability, reliability)

Verification
Code reviews, unit testing, integration testing
Methods

Validation
Manual UI testing, user feedback, UAT
Techniques

Bugs logged in Excel sheet with severity and

Defect Logging resolution status

Browser DevTools, Python unittest, Postman

Tools Used (for API)

Roles Involved Developer, Tester, End-user (during UAT)

 Final Documentation

Software Process & Models

For the Simple Job Board System, we began with a thorough requirement analysis,
identifying the key features such as job posting by employers, job search and
application by job seekers, and admin-level control for moderation. Based on the
nature of the project, the Agile Software Development Model was selected as the
preferred process model due to its iterative approach, flexibility for incorporating
feedback, and focus on continuous delivery. The project scope includes building a
responsive web application that connects job seekers with potential employers
efficiently. The main objectives are to streamline job searching, reduce hiring
time, and provide a platform that is accessible and easy to use for both
employers and applicants.

Software Requirements Specification (SRS)

Introduction: This document is intended for developers, testers, and

stakeholders involved in the Simple Job Board System project. It outlines the
system's requirements and expected functionalities.
Product Scope: The product aims to improve the job application and
recruitment process by allowing users to register, post and apply for jobs, and
manage applications.
Product Value: It benefits job seekers by offering a centralized platform to find
jobs and benefits companies by helping them efficiently find suitable
candidates.
Intended Audience: This system is designed for job seekers, employers, and
admin users.
Intended Use: Job seekers can apply for jobs, employers can post job
vacancies, and admins can manage users and content.
General Description: The system will include user registration/login, job
posting, job searching/filtering, application tracking, and basic analytics.
Test Plan and Test Cases

A detailed Test Plan was prepared including objectives, scope, strategy, criteria,
deliverables, risk analysis, and approval processes. Specific test cases were
written in a structured template, with each test case containing step ID,
description, expected result, actual result, and pass/fail status. Tests were created
for functionalities like user login, job posting, job searching, and application
submission. Agile testing practices such as regular sprint-based testing,
continuous feedback from stakeholders, and quick iterations were followed to
ensure quality and adaptability during development.

Stakeholder Identification and Planning

The project stakeholders were categorized using a Power vs. Impact matrix:
Manage Closely: Project Manager, Client
Keep Satisfied: Senior Developers, QA Lead
Keep Informed: Users (Employers and Job Seekers)
Monitor: Support Staff
A project plan was created detailing key development phases—requirement
gathering, design, development, testing, and deployment. The success metrics for
the system include user engagement rates, number of job applications submitted,
and average time-to-hire.

Activity Planning and Quality Plan

A Gantt chart was created to visually represent the timeline for each development
phase. Additionally, a network diagram was used to highlight task dependencies
and sequence. Using this, a Critical Path Analysis was performed to identify the
longest path and ensure timely project delivery. A Software Quality Plan was
established, covering code review procedures, functional and non-functional
testing, continuous integration, and post-deployment monitoring.
 Conclusion

This document outlines the complete Software Engineering life cycle followed in
developing the Simple Job Board System. From initial planning and requirement
analysis to testing and quality assurance, each phase was executed using
established engineering practices.

The project adopted the Agile model for its flexibility, enabling continuous
feedback and iterative development. A well-defined SRS captured all
requirements, serving as the basis for testing through a detailed test plan and
test cases. Agile testing methods ensured functionality, usability, and reliability.
Stakeholder analysis guided effective communication, while the project plan and
success metrics aligned development with goals. Gantt charts, network diagrams,
and critical path analysis supported efficient activity planning. A robust quality
plan ensured delivery met expected standards.

Overall, this project demonstrates how structured software engineering and Agile
practices can successfully deliver a functional, user-focused system.