EXPERIMENT NO.

01

AIM: Software Requirement Specification for Project Management System

Theory :

The srs should contain the following Table of Contents

Table of Contents............................................................................................................................i
Revision History...............................................................................Error! Bookmark not defined.
1. Introduction..............................................................................................................................2
1.1 Purpose.................................................................................................................................2
1.2 Document Conventions........................................................................................................2
1.3 Intended Audience and Reading Suggestions......................................................................2
1.4 Product Scope......................................................................................................................2
1.5 References............................................................................................................................2
2. Overall Description..................................................................................................................2
2.1 Product Perspective..............................................................................................................2
2.2 Product Functions................................................................................................................2
2.3 User Classes and Characteristics..........................................................................................3
2.4 Operating Environment........................................................................................................3
2.5 Design and Implementation Constraints..............................................................................3
2.6 User Documentation............................................................................................................3
2.7 Assumptions and Dependencies...........................................................................................3
3. External Interface Requirements...........................................................................................3
3.1 User Interfaces.....................................................................................................................3
3.2 Hardware Interfaces.............................................................................................................3
3.3 Software Interfaces..............................................................................................................4
3.4 Communications Interfaces.................................................................................................4
4. System Features.......................................................................................................................4
4.1 System Feature 1.................................................................................................................4
4.2 System Feature 2 (and so on)...............................................................................................5
5. Other Nonfunctional Requirements.......................................................................................5
5.1 Performance Requirements..................................................................................................5
5.2 Safety Requirements............................................................................................................5
5.3 Security Requirements.........................................................................................................5
5.4 Software Quality Attributes.................................................................................................5
5.5 Business Rules.....................................................................................................................5
6. Other Requirements................................................................................................................5
Appendix A: Glossary...................................................................................................................5
Appendix B: Analysis Models.......................................................................................................6
Appendix C: To Be Determined List............................................................................................6
 Introduction

Purpose
This Software Requirements Specification (SRS) document outlines the requirements for the
development of the Project Management System. The purpose of this document is to provide a
comprehensive understanding of the functionality, features, and constraints of the system to guide
the development team throughout the project lifecycle.
Document Conventions
This document follows standard conventions for software requirements specification, including:
- Use of headings and subheadings to organize content.
- Use of priority levels (High, Medium, Low) to indicate the importance of requirements.
- Unique identifiers for each requirement statement.
- TBD (To Be Determined) placeholders for incomplete or undecided information.
Intended Audience and Reading Suggestions
This document is intended for various stakeholders involved in the development, deployment, and
maintenance of the Project Management System. The primary audience includes:
 Developers: To understand the technical requirements and implementation details.
 Project Managers: To oversee project progress and ensure alignment with business objectives.
 Testers: To verify that the software meets specified requirements.
 Users: To understand the capabilities and functionality of the system.
 Documentation Writers: To create user manuals and training materials.
The document is organized into sections covering different aspects of the system, beginning
with an overview and proceeding to detailed functional and non-functional requirements.
Readers are encouraged to start with the introduction and overview sections before delving
into specific requirements relevant to their role or interest.
Product Scope
The Project Management System is a web-based application designed to streamline project
planning, execution, and monitoring processes. It facilitates collaboration among team members,
improves task management, and provides insights into project progress and performance. The
system aims to enhance productivity, transparency, and accountability in project management
activities.
References

 Trello: https://trello.com/

 Asana: https://asana.com/

 Monday.com: https://monday.com/
Overall Description

Product Perspective

The Project Management System website serves as a standalone platform dedicated to facilitating
project planning, tracking, and collaboration. It is not part of a larger system but is designed to
integrate with existing project management tools and systems. The website provides a user-
friendly interface for managing projects and tasks, allowing users to access project information,
communicate with team members, and track project progress in real-time.
Product Functions
The major functions of the Project Management System website include:
- Project creation and management
- Task assignment and tracking
- Document sharing and version control
- Team collaboration tools (e.g., chat, forums)
- Reporting and analytic
User Classes and Characteristics

The anticipated user classes for the Project Management System website include:
 Project Managers: Responsible for creating and overseeing projects, assigning tasks,
and monitoring progress.
 Team Members: Responsible for completing assigned tasks, collaborating with team
members, and updating task status.
 Administrators: Responsible for managing user accounts, permissions, and
system configurations.

Each user class may have varying levels of technical expertise, project
management experience, and access privileges within the system.

Operating Environment
The Project Management System website will operate in a web-based environment, accessible via
modern web browsers such as Google Chrome, Mozilla Firefox, and Microsoft Edge. It is platform-
independent and compatible with major operating systems including Windows, macOS, and Linux.
The website will require a stable internet connection for real-time collaboration and data
synchronization.
Design and Implementation Constraints

User Interface: The website design must adhere to modern UI/UX principles to ensure ease of use
and accessibility for users with diverse backgrounds.
 Security: The system must implement robust authentication and authorization
mechanisms to protect user data and prevent unauthorized access.
 Performance: The website should be optimized for speed and responsiveness to ensure
smooth user experience, even under heavy load conditions.
User Documentation

User documentation components for the Project Management System website will include:
 User Manuals: Detailed guides on using various features and functionalities of the website.
 Online Help: Contextual help resources accessible within the website interface.
 Tutorials: Step-by-step tutorials for new users to get started with the system
 Documentation will be available in digital formats (e.g., PDF, HTML).
Assumptions and Dependencies
Assumptions:
 Availability of stable internet connection for users accessing the website.
 Compliance with data protection regulations (e.g., GDPR) for handling user data.
 Users have basic computer literacy skills and familiarity with web browsing.
Dependencies:
 Integration with third-party services for authentication (e.g., OAuth providers).
 Use of web development frameworks and libraries (e.g., React.js, Node.js) for system
Implementation.
 Availability of hosting infrastructure (e.g., cloud servers) for deploying the website.
External Interface Requirements User

Interfaces
The user interface of the Project Management System website is designed to be intuitive, user-friendly,
and visually appealing. Key characteristics of the user interface include:
 Modern and responsive design to ensure compatibility across various devices and screen sizes.
 Consistent layout and navigation to facilitate easy access to different features and functionalities.
 Interactive elements such as buttons, dropdown menus, and forms for user input and interaction.
 Visual indicators (e.g., color-coded status labels, progress bars) to provide feedback and enhance
 user experience.
 Standard buttons and functions (e.g., help, settings) available on every screen for easy access to
common actions.
 Keyboard shortcuts for power users to perform tasks quickly and efficiently
Hardware Interfaces
The Project Management System website does not have direct hardware interfaces. It operates as a web-
based application accessed through standard web browsers on various devices such as desktop
computers, laptops, tablets, and smartphones. The system is platform-independent and does not require
specific hardware components for operation.

Software Interfaces
The Project Management System website interacts with various software components to provide its
functionality:
- Database: The system interfaces with a database management system (e.g., MySQL, PostgreSQL) to
store and retrieve project data, user information, and system configurations.
- Operating System: The website is designed to be compatible with major operating systems (e.g.,
Windows, macOS, Linux) that support modern web browsers.
- Web Development Frameworks and Libraries: The system utilizes web development frameworks and
libraries (e.g., React.js, Node.js) for front-end and back-end development, respectively.
- Integrated Commercial Components: Third-party services and APIs (e.g., OAuth providers for
authentication) are integrated to enhance system functionality.
Communications Interfaces

The Project Management System website relies on standard communication protocols and technologies
for data transfer and interaction:
- HTTP/HTTPS: Communication between the client (web browser) and server is performed using the
Hypertext Transfer Protocol (HTTP) or its secure variant (HTTPS) for encrypted communication.
- WebSocket: Real-time communication and updates between the client and server are facilitated using
WebSocket protocol for efficient bi-directional communication.
- Email Notifications: The system sends email notifications to users for important events (e.g., task
assignments, project updates) using SMTP (Simple Mail Transfer Protocol).
 System Features
System Feature 1
4.1.1 Description and Priority
 This feature allows users to create, assign, prioritize, and track tasks within the
project management system
4.1.2 High.Stimulus/Response Sequences
 User creates a new task: System prompts for task details and adds it to the
task list.
 User assigns a task to a team member: System updates task assignment and
notifies the team member.
 User updates task status: System reflects the changes in the task status and
notifies relevant stakeholders.

4.1.3 Functional Requirements

 The system shall allow users to create tasks with a title, description, priority, due date, and
assigned team member.
 The system shall support assigning tasks to one or multiple team members.
 The system shall provide options to prioritize tasks (e.g., high, medium, low).
 The system shall allow users to update task details (e.g., title, description, due date).
 The system shall enable users to mark tasks as completed.
 The system shall provide notifications for new tasks assigned and task updates.
 The system shall enforce data validation for task creation and updates (e.g., mandatory fields,
date formats).
 The system shall allow filtering and sorting tasks based on various criteria (e.g., due date,
priority, status).
Other Nonfunctional Requirements

Performance Requirements
The website should load within 3 seconds on average, measured using tools like Google PageSpeed
Insights, to ensure a smooth user experience and reduce bounce rates.
- The system should be able to handle concurrent user sessions efficiently, with a minimum of 1000
simultaneous users supported without significant performance degradation, to accommodate peak
usage periods.
- Response times for critical functions such as project creation, task assignment, and data retrieval
should be less than 1 second to maintain user productivity and satisfaction.
Safety Requirements
- The system should provide regular data backups to prevent data loss in case of system failures or
disasters.
- User authentication credentials should be securely stored and encrypted to prevent unauthorized access
to sensitive information.
- The system should implement role-based access control (RBAC) to ensure that users only have access
to the features and data relevant to their roles and responsibilities.
- Compliance with relevant safety regulations and standards such as GDPR (General Data Protection
Regulation) should be maintained to protect user privacy and data security.
Security Requirements
- Data transmission between the client and server should be encrypted using HTTPS to protect
sensitive information from interception or tampering.
- The system should implement measures to prevent common security threats such as cross-site
scripting (XSS), SQL injection, and session hijacking.
- Regular security audits and vulnerability assessments should be conducted to identify and mitigate
potential security risks.
Software Quality Attributes
- Availability: The system should have an uptime of at least 99.9% to ensure continuous availability and
reliability for users.
- Maintainability: The codebase should be well-organized and documented to facilitate ease of
maintenance and future enhancements by developers.
- Usability: The user interface should be intuitive and easy to navigate, with clear instructions and
feedback provided to users to minimize learning curve and errors.
Business Rules
- Only project managers or administrators can create new projects and assign tasks to team members.
- Task deadlines should be set realistically based on project timelines and priorities to ensure timely
completion of tasks.
- - Users should not have access to projects or tasks outside of their assigned teams or projects unless
explicitly granted permission by project managers or administrators.
 Other Requirements

- Database Requirements: The system should use a relational database management system
(RDBMS) such as MySQL or PostgreSQL for data storage and retrieval.
- Internationalization Requirements: The user interface should support multiple languages to
accommodate users from different regions.
- Legal Requirements: The system should comply with relevant laws and regulations governing
data protection, privacy, and intellectual property rights.
- Reuse Objectives: The system should adhere to software design principles such as modularity and
encapsulation to promote code reusability and maintainability.
Appendix A: Glossary
Project Management System (PMS):
- A comprehensive software solution designed to facilitate project planning, execution, and monitoring
while promoting collaboration among team members.

Administrators:
- Users with extensive privileges and control over all PMS functionalities. They oversee project setup,
user management, and system configuration.

Project Managers:
- Users responsible for planning, organizing, and overseeing project execution within the
PMS. They manage tasks, assign resources, and track progress to ensure project delivery
within scope, schedule, and budget.

Team Members:
- End-users actively involved in project execution, responsible for completing assigned tasks,
collaborating with teammates, and providing status updates within the PMS.

Dashboard:
- An intuitive interface presenting real-time project metrics, task summaries, and upcoming deadlines
for quick decision-making and performance monitoring.

Responsive Design:
- A user interface design approach ensuring seamless access and optimal usability across various
devices, including desktops, tablets, and mobile phones.

Time Tracking:
- Functionality enabling users to record time spent on individual tasks or projects within the PMS,
facilitating accurate billing, resource allocation, and performance evaluation.

Gantt Charts:
- Visual representations of project schedules, depicting task dependencies, durations, and
milestones to aid in project planning and tracking.

File Sharing:
- Capability allowing users to upload, store, and share project-related documents, images, and
other files securely within the PMS, fostering collaboration and knowledge sharing.

Integration APIs:
- Interfaces enabling seamless integration between the PMS and external applications, such as
CRM systems, accounting software, or version control repositories, to streamline data
exchange and workflow automation.
Appendix B: Analysis Models

Appendix C: To Be Determined List

Integration Mechanism:
- The precise method and protocols for integrating the Project Management System with
external applications and organizational systems are pending further clarification and
analysis.

Customization Scope:
- The depth and breadth of customization options for workflows, dashboards, and reporting
tools within the Project Management System are subject to further evaluation and
specification.

Compliance Requirements:
- Specific details concerning the Project Management System's adherence to industry
standards, regulatory frameworks, and relevant certifications are pending determination and
review.
Reference:
1. ADP Article on Project Management:
https://www.adp.com/resources/articles-and-insights/articles/e/project-management.aspx
2. Indeed Career Advice on Project Management System:
https://in.indeed.com/career-advice/career-development/project-management-system
3. GeeksforGeeks Program for Project Management System:
https://www.geeksforgeeks.org/program-for-project-management-system/

For Faculty Use

Correction Formative Timely completion Attendance /

Parameters Assessment of Practical Learning Attitude
[40%] [ 40%] [20%]

Marks Obtained