SHRI GOVINDRAM SEKSARIA INSTITUTE

OF TECHNOLOGY AND SCIENCE, INDORE

COMPUTER SCIENCE ENGINEERING

AGILE SOFTWARE METHODOLOGY

2024-25

SUBMITTED TO: SUBMITTED BY:

Ms. Priyanka Kokate Chitransh Guha
Ms. Ashwini Pahade Vanshika Sahu
Yukta Tumbekar
Nabannita Debnath
Kshitij Edlabedkar
 INDEX

I. Software Requirements Specification (SRS)

II. UML Diagrams

III. Definition of Done or Ready

IV. Burnup , Burndown Chart

V. Sprint Report

VI. Test Cases

VII.
 SOFTWARE REQUIREMENTS SPECIFICATION (SRS)

Software Requirements Specification for Project “EMPOWER HER”

Introduction
1.1 Purpose
The purpose of this document is to specify the software
requirements for a user-centred website platform that connects
unemployed and uneducated women with potential employers in
household and caregiving roles. The roles include household helpers,
caretakers, cooks, laundry workers, and play school staff. This
platform aims to provide a seamless and effective job matching
experience, ensuring the safety and security of both job seekers and
employers.
1.2 Document Conventions

- REQ-#: Requirement identifier

- TBD: To Be Determined
- Priorities are indicated as High, Medium, or Low.

1.3 Intended Audience and Reading Suggestions

This document is intended for the following audiences:
- Developers: To understand the requirements and design the system
accordingly.
- Project Managers: To plan and manage the development process.
- Marketing Staff: To understand the features and benefits of the
platform.
- Users: To know what to expect from the platform.
- Testers: To create test cases based on the requirements.
- Documentation Writers: To develop user manuals and help guides.
Readers are suggested to start with the overview sections and then
proceed to the sections that are most pertinent to their role.

1.4 Product Scope

The scope of this product includes:
- User registration and profile management for both job seekers and
employers.
- Job posting, searching, and application management.
- Matching algorithm to suggest suitable jobs to job seekers.
- Accessibility and localization to support diverse users.
- Training resources for job seekers and guidelines for employers.
- Integration of a payment gateway for potential membership fees.
- Notification system to keep users informed about relevant updates.
- Reporting and analytics tools for administrators.

1.5 References
- Vision and Scope Document for Women Empowerment Job
Platform
- User Interface Style Guides
- Corporate Security Policies
- Regulatory Standards for Data Protection and Privacy
2. Overall Description

2.1 Product Perspective

This platform is a new, self-contained product designed to connect
unemployed and uneducated women with potential employers. It
operates independently but may interface with external payment
gateways and training resource providers.

2.2 Product Functions

The major functions of the product include:

- User Registration
- Job Posting
- Job Searching
- Matching Algorithm
- Application Management
- Accessibility and Localization
- Training and Resources
- Payment Gateway
- Profile Management
- Notification System
- Reporting and Analytics
2.3 User Classes and Characteristics

- Job Seekers: Unemployed and uneducated women looking for

household and caregiving jobs. They may have low technical
expertise and require a simple, intuitive interface.
- Employers: Individuals or organizations seeking household helpers,
caretakers, cooks, laundry workers, and play school staff. They may
vary in technical expertise and require efficient tools to manage job
postings and applications.
- Administrators: Users responsible for managing the platform,
monitoring usage, and ensuring compliance with policies.

2.4 Operating Environment

The platform will operate in a web environment accessible via

modern web browsers. It should be compatible with common
operating systems, including Windows, macOS, Linux, iOS, and
Android.

### 2.5 Design and Implementation Constraints

- The platform must comply with data protection and privacy
regulations.
- The system should be designed to handle high traffic and large
volumes of data.
- The matching algorithm must be efficient and scalable.
- Integration with third-party payment gateways and training
resources is required.
2.6 User Documentation
User manuals, online help, and tutorials will be provided to assist
users in navigating and utilizing the platform effectively.

2.7 Assumptions and Dependencies

- Assumes availability of internet access for users.
- Dependent on third-party payment gateways for transaction
processing.
- Assumes collaboration with training resource providers for content.

3. External Interface Requirements

3.1 User Interfaces
The platform will feature a user-friendly interface with the following
characteristics:
- Simple registration forms for job seekers and employers.
- Intuitive job posting and searching interfaces.
- Clear and accessible profile management pages.
- Notification center for updates and alerts.

3.2 Hardware Interfaces

No specific hardware interfaces are required beyond standard web-
enabled devices.

3.3 Software Interfaces

The platform will interface with:
- Third-party payment gateways (e.g., PayPal, Stripe).
- External training resource providers.

3.4 Communications Interfaces

The platform will use:

- HTTP/HTTPS for web communication.
- Email protocols (SMTP, IMAP) for notifications.
- Secure communication channels for payment processing.

4. System Features

4.1 User Registration

4.1.1 Description and Priority
Allow job seekers and employers to register and create profiles. High
priority.

4.1.2 Stimulus/Response Sequences

- User navigates to the registration page.
- User fills in the required information.
- System validates the information.
- System creates the user profile and sends a confirmation email.
4.1.3 Functional Requirements
- REQ-1: The system shall allow job seekers to register with personal
details and skill sets.
- REQ-2: The system shall allow employers to register with company
details and contact information.
- REQ-3: The system shall send a confirmation email upon successful
registration.

4.2 Job Posting

4.2.1 Description and Priority
Enable employers to post job openings with descriptions,
requirements, and contact information. High priority.

4.2.2 Stimulus/Response Sequences

- Employer navigates to the job posting page.
- Employer fills in the job details.
- System validates the information.
- System posts the job opening.

4.2.3 Functional Requirements

- REQ-4: The system shall allow employers to post job openings.
- REQ-5: The system shall validate job posting information before
submission.
- REQ-: The system shall display job postings to job seekers.
4.3 Job Searching
4.3.1 Description and Priority
Allow job seekers to search for jobs by location, job type, and other
relevant criteria. High priority.

4.3.2 Stimulus/Response Sequences

- Job seeker navigates to the job search page.
- Job seeker inputs search criteria.
- System retrieves and displays matching job listings.

4.3.3 Functional Requirements

- REQ-7: The system shall provide search filters for location, job type,
and other criteria.
- REQ-8: The system shall display job listings based on search criteria.

4.4 Matching Algorithm

4.4.1 Description and Priority
Develop an algorithm to suggest suitable jobs for job seekers based
on their profiles and preferences. High priority.

4.4.2 Stimulus/Response Sequences

- Job seeker updates profile with preferences.
- System runs the matching algorithm.
- System suggests suitable job listings to the job seeker.
4.4.3 Functional Requirements
- REQ-9: The system shall match job seekers to job postings based on
profile information.
- REQ-10: The system shall update suggestions as profiles and job
postings change.

4.5 Application Management

4.5.1 Description and Priority
Enable job seekers to apply for jobs and employers to manage
applications. High priority.

4.5.2 Stimulus/Response Sequences

- Job seeker applies for a job.
- Employer reviews applications.
- System notifies job seeker of application status.

4.5.3 Functional Requirements

- REQ-11: The system shall allow job seekers to apply for job postings.
- REQ-12: The system shall allow employers to review and manage
applications.
- REQ-13: The system shall notify job seekers of application status
updates.

4.6 Accessibility and Localization

4.6.1 Description and Priority
Ensure the platform is accessible and usable for job seekers and
employers with disabilities. Provide language support and localization
for different regions and countries. Medium priority.

4.6.2 Stimulus/Response Sequences

- User selects accessibility options or language preferences.
- System adjusts interface accordingly.

4.6.3 Functional Requirements

- REQ-14: The system shall provide accessibility features (e.g., screen
reader support).
- REQ-15: The system shall offer multiple language options and
regional settings.

4.7 Training and Resources

4.7.1 Description and Priority
Offer online training and resources for job seekers to improve their
skills and knowledge in household and caregiving roles. Provide
employers with resources and guidelines for creating a safe and
respectful work environment. Medium priority.

4.7.2 Stimulus/Response Sequences

- User navigates to the training and resources section.
- User selects and accesses training materials or guidelines.
4.7.3 Functional Requirements
- REQ-16: The system shall provide training materials for job seekers.
- REQ-17: The system shall offer guidelines for employers.

4.8 Payment Gateway

4.8.1 Description and Priority
Integrate a payment gateway for job seeker membership fees (if
applicable). Low priority.

4.8.2 Stimulus/Response Sequences

- User selects membership option.
- System processes payment through gateway.
- System updates membership status.

4.8.3 Functional Requirements

- REQ-18: The system shall integrate with third-party payment
gateways.
- REQ-19: The system shall process membership fees securely.

4.9 Job Seeker Profile Management

4.9.1 Description and Priority
Allow job seekers to update their profiles and skills. High priority.

4.9.2 Stimulus/Response Sequences

- Job seeker navigates to the profile management page.
- Job seeker updates profile information.
- System saves changes.

4.9.3 Functional Requirements

- REQ-20: The system shall allow job seekers to update their profiles.
- REQ-21: The system shall save and display updated profile
information.

4.10 Employer Profile Management

4.10.1 Description and Priority
Allow employers to update their profiles and job postings. High
priority.

4.10.2 Stimulus/Response Sequences

- Employer navigates to the profile management page.
- Employer updates profile or job postings.
- System saves changes.

4.10.3 Functional Requirements

- REQ-22: The system shall allow employers to update their profiles.
- REQ-23: The system shall save and display updated profile and job
posting information.

4.11 Notification System

4.11.1 Description and Priority
Send notifications to job seekers and employers about new job
postings, applications, and interview schedules. High priority.

4.11.2 Stimulus/Response Sequences

- System detects relevant events (new job posting, application status
change, etc.).
- System sends notifications to users.

4.11.3 Functional Requirements

- REQ-24: The system shall send notifications about new job postings
to job seekers.
- REQ-25: The system shall notify users about application status
changes.
- REQ-26: The system shall send reminders for scheduled interviews.

4.12 Reporting and Analytics

4.12.1 Description and Priority
Provide reporting and analytics tools for administrators to monitor
platform usage and performance. Medium priority.

4.12.2 Stimulus/Response Sequences

- Administrator accesses reporting tools.
- System generates and displays reports based on selected criteria.
4.12.3 Functional Requirements
- REQ-27: The system shall provide usage reports to administrators.
- REQ-28: The system shall offer analytics on job postings and
applications.

5. Other Nonfunctional Requirements

5.1 Performance Requirements
- REQ-29: The system shall support up to 10,000 concurrent users.
- REQ-30: The system shall respond to user actions within 2 seconds
under normal conditions.

5.2 Safety Requirements

- REQ-31: The system shall ensure data integrity and prevent data
loss.

5.3 Security Requirements

- REQ-32: The system shall enforce user authentication and
authorization.
- REQ-33: The system shall encrypt sensitive user data during
transmission and storage.

5.4 Software Quality Attributes

- REQ-34: The system shall have an availability of 99.9% uptime.
- REQ-35: The system shall be maintainable with minimal downtime
for updates.
5.5 Business Rules
- REQ-36: The system shall comply with local labor laws and
regulations.
- REQ-37: The system shall ensure fair and non-discriminatory job
matching practices.

6. Other Requirements
- REQ-38: The system shall be scalable to accommodate future
growth and additional features.
Appendix A: Glossary
- Job Seeker: A user looking for employment opportunities.
- Employer: A user or organization posting job openings and seeking
candidates.
- Administrator: A user managing the platform and overseeing its
operations.

Appendix B: Analysis Models

- Use Case Diagrams
- Data Flow Diagrams

Appendix C: To Be Determined List

- Finalize third-party payment gateway provider.
- Determine additional languages for localization.
- Identify specific training resource providers.
UML Daigrams
1. Usecase diagram
2. Sequence Daigram
3. Activity Daigram
4. Class Daigram
5. ER Daigram
Definition of Ready
1. Clearly Defined User Story: The user story has a clear description,
acceptance criteria, and enough details to be actionable.
2. Acceptance Criteria Defined: The success conditions for the story are
clearly defined and agreed upon by the team.
3. Dependencies Identified: Any dependencies (e.g., database, APIs, or
third-party services) are identified, and there is a plan to resolve them.
4. User Story Estimated: The team has estimated the effort required (e.g.,
story points or hours) and agrees it is achievable in the sprint.
5. Test Cases Identified: QA or the team has drafted the basic test cases to
ensure the feature works as intended.

Definition of Done
1. Code Complete: All necessary coding has been completed, and the
feature works as expected.
2. Unit Tests Written and Passed: All relevant unit tests have been written
and passed successfully
3. Integrated into System: The feature is integrated into the larger system
without breaking other functionality.
4. Documentation Updated: Any necessary documentation (e.g., user
manuals, code comments, or API documentation) has been updated.
5. Approved by Stakeholders: The feature has been demonstrated and
approved by the product owner or relevant stakeholders.
6. Acceptance Criteria Met: All the criteria laid out in the user story have
been satisfied.
 BURNUP CHART

BURNDOWN CHART

SPRINT REPORT
TEST CASES