Green University of Bangladesh

Department of Computer Science and Engineering (CSE)

Semester: (Spring, Year: 2024), B.Sc. in CSE (Day)

Project Task Management S

Course Title: IDP Lab

Course Code: CSE-324
Section: 221-D12
Students Details
Name ID
Hasnat Zamil 221902001
Md. MohibuLLah Foysal 221902275
Ruma Akter 221902044

Submission Date: 14-09-2024

Course Teacher’s Name: Sakhaouth Hossan

[For teachers use only: Don’t write anything inside this box]

Lab Project Status

Marks: Signature:

Comments: Date:
Abstract
This project proposal outlines the development of a project management system aimed at help-
ing organizations, particularly IT firms, manage tasks, track project progress, and schedule
meetings effectively. The system will allow users to create or join companies, manage tasks
collaboratively, and schedule weekly meetings to discuss project updates. A user-friendly in-
terface will help both individuals and teams stay organized and focused on delivering projects
on time.

Problem Analysis and Motivation

Problem Statement
n modern organizations, managing multiple projects with distributed teams can become cum-
bersome. Most organizations struggle with the following:

• Inefficient task assignment and tracking.

• Lack of real-time collaboration tools.

• Difficulty in managing weekly meetings and task updates.

• Complex systems that are expensive and require training.

Motivation
The proposed system seeks to provide an all-in-one solution that combines task management,
progress tracking, and easy scheduling of meetings. This system is designed to be user-friendly,
cost-effective, and adaptable for small to medium enterprises (SMEs), freelancers, and individ-
ual developers. The motivation stems from the need for a simpler alternative to platforms like
Jira or Asana, with a focus on integration with virtual meeting tools and straightforward task
management.

Literature Review

Existing Systems
Jira, Trello, and Asana are popular tools currently available in the market. However, they tend
to focus on large-scale project management or are too simple for some organizations. Below is
a brief comparison:

• Jira: Known for its powerful task tracking and Agile management features but can be
complex and expensive for smaller teams.

1
 • Trello: Offers a simple Kanban-style interface but lacks advanced features like task de-
pendencies or integrations for virtual meetings.

• Asana: Provides robust task and project management but has a steep learning curve and
can be too feature-heavy for SMEs.

Gaps in Existing Literature

Existing literature points to the need for:

• Simpler, affordable tools for smaller teams or individual users.

• Seamless integration with online meeting platforms like Zoom or Google Meet.

• Easier reporting features and a focus on tracking both individual and team progress.

This project will aim to fill these gaps by focusing on usability, simplicity, and meeting
integration, targeting a different user demographic.

Methodology
The development of the project management system will follow an Agile methodology, allow-
ing for iterative development and continuous feedback. The system will be built in five main
phases:

Development Phases
Phase 1: Planning & Requirements Gathering

The initial phase will focus on gathering requirements by identifying pain points in existing
systems and defining the features needed by potential users. Key user personas, such as devel-
opers, project managers, and administrators, will be identified, with their respective needs and
system interactions outlined.

• Deliverables:

– Detailed project requirements

– User personas and use cases
– Initial project roadmap

Phase 2: System Architecture Design

In this phase, the system architecture will be designed to ensure scalability and maintainability.
The project will follow a modular design, using the following tech stack:

2
 • Backend: Node.js with Express or Django (Python)

• Database: PostgreSQL or MongoDB

• Frontend: React.js or Vue.js

The key components of the system include:

• User Management Module: Handles registration, authentication, and role management.

• Task Management Module: Allows task creation, assignment, and tracking.

• Meeting Scheduler: Integrates with third-party APIs (e.g., Zoom, Google Meet) to
schedule meetings.

• Deliverables:

– System architecture and design documentation

– Database schema and ER diagrams
– API design for task management and meeting scheduling

Phase 3: Development

During this phase, the system’s core features will be developed. The focus will be on de-
veloping the user registration system, task management functionality, and meeting scheduling
integration. The development will be carried out in sprints, with regular testing and feedback
loops.

• Deliverables:

– Core modules (User Management, Task Management, Meeting Scheduler)

– Integration with third-party APIs (Zoom, Google Meet)
– Frontend and backend functionality

Phase 4: Testing & Validation

In this phase, rigorous testing will be conducted to ensure the system works as intended. Unit
tests, integration tests, and user acceptance tests will be performed. Feedback will be gathered
from a small group of users to identify areas of improvement.

• Deliverables:

– Comprehensive test cases and results

– Bug fixes and system optimizations
– User feedback for further enhancements

3
Phase 5: Launch & Feedback Loop

The final phase involves the launch of the Minimum Viable Product (MVP) to a broader audi-
ence. A continuous feedback loop will be established, and new features will be added based on
user feedback and changing needs.

• Deliverables:
– Fully functional MVP
– User feedback collection and analysis
– Feature enhancements and new sprint planning

Feasibility Study

Technical Feasibility
The project management system will be technically feasible due to:

• The availability of proven development frameworks (Node.js, React.js).

• Readily available APIs for integration (Zoom API, Google Calendar API).
• Scalable cloud-based infrastructure (AWS, Google Cloud) to host the system.

Economic Feasibility
• Low Development Cost: Using open-source tools and APIs.
• Revenue Potential: Freemium model with subscription plans for advanced features.
Target SMEs and freelancers, who need affordable solutions.
• Market Opportunity: Increasing demand for remote work solutions and project track-
ing tools.

Operational Feasibility
• User Adoption: Simple and intuitive UI, ensuring ease of use for non-technical users.
• Team Structure: Small team of developers required initially, with the possibility of
scaling as the project grows.

Detailed Working Plan

The development of the project management system is divided into well-defined stages. Below
is the detailed working plan for each stage, outlining the tasks to be completed, the expected
deliverables, and the timeline for each phase.

4
Phase 1: Project Proposal and Planning
• Objective: Outline the project scope, goals, and deliverables.

• Tasks:

– Identify key problem areas and target users.

– Develop project goals and objectives.
– Create a high-level project timeline and resource estimation.
– Prepare the initial project proposal document.

• Deliverables: Project proposal document with an overview of the system.

• Timeline: 1 week

Phase 2: Requirement Specification

• Objective: Gather and document all functional and non-functional requirements of the
system.

• Tasks:

– Conduct stakeholder meetings and surveys to understand user needs.

– Identify functional requirements (e.g., user management, task assignment, meeting
scheduling).
– Define non-functional requirements (e.g., security, performance).
– Prepare the Software Requirements Specification (SRS) document.

• Deliverables: Completed SRS document.

• Timeline: 2 weeks

Phase 3: System Architecture Design and SDLC Selection

• Objective: Select an appropriate SDLC model and design the system architecture.

• Tasks:

– Choose the Agile SDLC model to facilitate iterative development.

– Develop a high-level system architecture that ensures scalability and modularity.
– Design the database schema for user management, task tracking, and meeting schedul-
ing.
– Create detailed design documentation.

• Deliverables: System architecture diagrams and design documentation.

• Timeline: 2 weeks

5
Phase 4: Data Flow Diagram (DFD) Modeling
• Objective: Create a Data Flow Diagram (DFD) to map the movement of data within the
system.
• Tasks:
– Identify key entities and processes involved in data flow (e.g., user, task manage-
ment, meeting scheduler).
– Develop Level 0, Level 1, and Level 2 DFDs to represent different layers of data
flow.
– Validate the DFD with stakeholders.
• Deliverables: Completed DFDs at all levels.
• Timeline: 1 week

Phase 5: UML Diagrams Development

• Objective: Develop UML diagrams (Use Case, Sequence, Communication, and Class
Diagrams) to represent the system’s functional behavior.
• Tasks:
– Develop a Use Case Diagram representing all major interactions with the system.
– Create Sequence and Communication Diagrams to illustrate object interactions for
specific use cases.
– Develop a Class Diagram to show the structure of the system, its classes, attributes,
methods, and relationships.
• Deliverables: UML Use Case, Sequence, Communication, and Class Diagrams.
• Timeline: 2 weeks

Phase 6: Development and Coding

• Objective: Develop and implement the system according to the defined architecture and
requirements.
• Tasks:
– Develop the backend logic using the selected technology stack (e.g., Node.js, Django).
– Implement the frontend interface using React.js or Vue.js.
– Integrate core functionalities such as task management, meeting scheduling, and
user authentication.
– Conduct unit testing during development to ensure code quality.
• Deliverables: Completed source code for backend and frontend, including core features.
• Timeline: 6 weeks

6
Phase 7: Software Testing and Validation
• Objective: Conduct comprehensive testing to ensure the system is functional, reliable,
and secure.
• Tasks:
– Perform unit testing on individual modules.
– Conduct integration testing to ensure modules work together.
– Carry out user acceptance testing (UAT) with real users to gather feedback.
– Perform performance testing to verify system scalability and responsiveness.
– Fix any bugs and optimize the system.
• Deliverables: Test case results and a bug-free, optimized system.
• Timeline: 4 weeks

Phase 8: Deployment and Maintenance

• Objective: Deploy the system to a production environment and ensure ongoing mainte-
nance and updates.
• Tasks:
– Deploy the system to the cloud or a server environment.
– Ensure proper configuration for scalability and security.
– Monitor the system post-deployment for any issues.
– Provide ongoing support and updates based on user feedback.
• Deliverables: Deployed system, monitoring logs, and user feedback reports.
• Timeline: 2 weeks (ongoing maintenance as needed)

Project Timeline Summary

• Phase 1 - Planning: 1 week
• Phase 2 - Requirements: 2 weeks
• Phase 3 - Design: 2 weeks
• Phase 4 - DFD Modeling: 1 week
• Phase 5 - UML Diagrams: 2 weeks
• Phase 6 - Development: 6 weeks
• Phase 7 - Testing: 4 weeks
• Phase 8 - Deployment and Maintenance: 2 weeks (ongoing)

Total Estimated Time: 20 weeks

7
Gantt Chart
Project Timeline (weeks)

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24

Planning

Requirement Gathering

System Design

Diagram(UML, DFD)

Development

Testing

Deployment

Training & Support

Budget Overview
The table below outlines the detailed budget for implementing a Library Management System.

Item Description Cost (tk)

Software PTMS Software License 5,000
Software Presentation Guidelines and Manuals 1,000
Server Hardware Cloud or Physical Server Setup 3,000
Development Team Developers and Designers 30,000
Database Setup Initial Database Design and Configuration 5,000
Training Staff Training 10,000
Support Ongoing Maintenance and Support 1,000/months
Total Cost 55,000
Table 1: Estimated Budget for Project Task Management System