Progress Report

Of
“To-Do List”

Submitted By
Student’s Name-Apoorva Srivastava
RollNo- 2204162074
Enroll No- A-8034
Class- B.C.A
Semester- 5th
Under Supervision of
Ms. Shagufta Khan

Department of Computer Science and Information Technology

KhwajaMoinuddinChishtiLanguage University
Lucknow

1
 INDEX

S.No. TOPIC Page No.

1. Abstract
3

2 Objective
4

3 Limitations of Existing System

5-7

4 Proposed System
8 - 10

5 Feasibility Study
11

6 Tools Description
12 - 14
6. 1 Hardware Requirement
6.2 Software Requirement
8 System Analysis
16 - 17

9 Data Flow Diagram

18 - 20

10 Entity Relationship Diagram

21 - 22

11 Modules
23

12 Work Remaining
24

13 References
25

2
 Abstract
Project – Task Manager

Task Manager is a crucial system utility that enables users

to monitor, manage, and control running processes,
applications, and services on a computer. It provides real- time
information on system resource utilization, allowing
users to optimize performance, identify potential issues,
and terminate malfunctioning processes.
Task Manager web application using MERN stack is a
project that basically implements basic CRUD operation

using MERN stack (MongoDB, Express JS, Node JS,

React JS). The users can read, add, update, and delete their
to-do list in the table using the web interface. The
application gives a feature to the user to add a deadline

to their task so that it user can be reminded of the last

day to complete the project.

3
 Objective
 Task Management:
Each objective can have a list of associated tasks. Tasks can
have details like due dates, priority levels, and status

(completed/incomplete).

 S u b-Tasks:
Allow each task to have smaller sub-tasks to break down complex

 Progress Tracking:
Track progress at the task level and aggregate progress at the

objective level (e.g., percentage of tasks completed for an

objective).

 Reminders and Notifications:

Add reminders for specific tasks or objectives to ensure deadlines

are met.

4
 Limitations of Existing System

1. Lack of Objective/Goal-Oriented Focus

Problem : Most to-do lists focus solely on individual tasks

without considering how these tasks contribute to larger
objectives or long-term goals. Users can lose sight of the
bigger picture when tasks are treated as isolated items.
Impact : Users might complete tasks without feeling they’ re
making progress on important objectives, leading to a lack of

motivation or prioritization issues.

2. Limited Task Hierarchy

Problem : Many systems allow users to create tasks and

maybe subtasks, but they don't support more complex

structures, such as tasks grouped under projects or

objectives.

Impact : Managing complex projects becomes cumbersome, as

users cannot effectively break down larger objectives into
manageable steps with clear relationships between them.

5
3. Poor Progress Tracking:

Problem : Basic to-do apps often lack robust progress

tracking features. Users can only see tasks marked as
“completed” or “ not completed,” without tracking how much
work is left or how far along they are in reaching a goal.

Impact : This lack of visibility into progress may demotivate

users, especially in long-term projects where it’s hard to see
incremental progress.

4. Weak Prioritization and Categorization

Problem : Many systems lack effective ways to prioritize

tasks beyond a simple "high/medium/low" priority level. They may
also lack sufficient categorization, tags, or filters.

Impact : Without sophisticated prioritization and

categorization, users struggle to determine what tasks
should be done first, especially when juggling multiple
projects with varying levels of urgency.



6
 Proposed System

A proposed system for an advanced to-do list application aims to address

the limitations of traditional to-do list apps by incorporating features that

focus on objective-based task management, prioritization, progress

tracking, collaboration, and flexibility. Below is a comprehensive outline

modern, objective-driven to-do list system:

1. Objective-Based Framework:
Core Concept: Unlike traditional task managers, the proposed system
organizes tasks around objectives (high-level goals or projects). This
approach provides users with clarity on how individual tasks
contribute to larger achievements.

Structure :
o Objectives: Users define long-term objectives or projects.
o Milestones: Each objective can have milestones, which act
as intermediate goals.
o Tasks: Tasks are created under objectives or
milestones, making it easier to see the big picture.

2. Enhanced Task Hierarchy:

7
Feature: Sub-Objectives and Tasks: Tasks can be grouped into sub-
tasks, with support for multiple layers (i.e., breaking down large tasks

into smaller, manageable ones).

8
 Benefit: This provides better structure for complex projects, allowing

users to break down objectives into actionable steps.

3. Prioritization and Categorization

Feature:
o Custom Prioritization: Support for detailed priority levels
(Urgent, High, Medium, Low) with optional custom labels
(e.g., "Client
Priority").
o Tags and Categories: Users can categorize tasks with tags,
such as "Work," "Personal," "Urgent," "Long-term,"
allowing for quick filtering and sorting.

o Task Importance vs. Urgency Matrix: A visual

matrix helps users prioritize tasks based on
importance and urgency.

4. Integrated Progress Tracking

Feature:
o Completion Progress Bars: Each objective and milestone
comes with a progress bar reflecting the percentage of
tasks completed.

o Task Progress: Support for partially completed tasks

(e.g., marking tasks as 50% done).

9
 F easibility Study

This feasibility study evaluates the technical, operational, economic, and

scheduling feasibility of implementing such a system.

Technical Feasibility:-

Hardware: The system requires PC or Laptop for each classroom, along

with a centralized server for data storage and processing.

Software: Development and implementation of the software system will

involve costs for programming, testing, and ongoing maintenance.

Network: A reliable network infrastructure is crucial for real-time data

transfer between devices and the central server. The existing network
capabilities and potential upgrades will be evaluated.

Operational Feasibility: -

User Acceptance: The system's user interface must be intuitive and

user-friendly. Training sessions for administrators and teaching staff will be
organized to ensure smooth adoption.

Integration: Compatibility with existing attendance tracking systems,

databases, and student information systems will be assessed. The system
should seamlessly integrate with the current operational structure.

10
 Tools Description

Hardware Requirement :

 256 MB RAM
 Storage (ROM)
 Keyword and Mouse

 Display

 Internet Connection

Software Requirement:

 No Sql Database: MongoDB

.
 Web Server: Node.js with Express.js
 IDE: Visual Studio Code Editor.

 Frontend- HTML, CSS, Javascript Libraries (React.js).

11
 Methodology or Planning of work

The Agile methodology is highly recommended for app development

because it focuses on iterative development, allowing flexibility and quick
adjustments based on feedback. Here's how the Agile methodology could

be applied to your project:

Work To-Do List (Organized by Phases)

Phase 1: Requirements Gathering and Planning

Conduct stakeholder meetings to gather requirements.

Identify user personas and document use cases.
Define functional and non-functional requirements.
Create user stories and acceptance criteria.
Draft a project timeline and initial budget estimate.

12
Phase 2: Prototyping (Sprint 1)

 Develop a basic prototype with core functionalities.

 Implement UI design in the front-end.

Set up initial back-end architecture.

Integrate basic API calls (if applicable).
 Conduct internal testing and gather feedback from stakeholders.



Phase 4: Core Feature Development (Sprints 2-5)

  Sprint 2:

o Develop authentication and user account features.

o Set up user roles and permissions.
o Test user registration and login functionalities.

  Sprint 3:

o Develop core app functionality (e.g., task management,

social interaction).

o Implement the database and business logic layer.

o Conduct unit and integration tests.

13
  

 Sprint 4:

o Complete secondary features (e.g., notifications,

messaging).

o Connect external services or APIs.

o Perform user acceptance testing (UAT)

Sprint 5:
o Refine user interface based on feedback.
o Fix bugs found in UAT.
o Prepare for deployment (production environment setup).

Phase 5: Deployment

 Set up CI/CD pipelines for continuous deployment.

Deploy the app to a cloud service or hosting platform.

Conduct final security audits and performance tests.

Submit the app to relevant app stores (if mobile).


14
Phase 6: Post-Launch Monitoring and Maintenance

 Monitor app performance (using tools like Google Analytics, New
Relic).
 Set up error tracking and user feedback channels.




15
 Data Flow Diagram

0-level DFD:

16
1-Level DFD:

17
2-Level DFD:

18
Entity Relationship Diagram

19
flowchart

20
 Modules

To-do list modules help users manage tasks, keep track of deadlines, and organize
their daily activities. Here are some core features and components typically found
in to-do list modules:

1. Task Creation and Management

 Users
can create tasks with descriptions, assign priorities, due dates, and
deadlines.
 Tasks can be edited, marked as complete, or deleted.

2. Categorization and Tagging

 Tasks can be categorized by project, type, or tags for easier sorting.
 Custom
categories or folders can be used to group tasks by context (e.g.,
work, personal, shopping).
21
 Work Remaining
Work Remaining To-Do List Template

1. High Priority (Urgent)

[Task 1]: (e.g., Submit report to manager)

o Due Date: (e.g., Today at 5 PM)
o Status: In Progress
o Subtasks:
1. Review data
2. Proofread
3. Send via email
[Task 2]: (e.g., Client presentation preparation)

o Due Date: (e.g., Tomorrow at 10 AM)

o Status: Not Started
o Subtasks:
1. Gather slides from team
2. Finalize content
3. Rehearse

2. Medium Priority

[Task 3]: (e.g., Team meeting agenda creation)

o Due Date: (e.g., 3 days from now)

o Status: Not Started
22
 o Subtasks:

1. Confirm meeting objectives

2. Draft and circulate agenda

[Task 4]: (e.g., Update project documentation)

o Due Date: (e.g., End of week)

o Status: In Progress
o Subtasks:

1. Collect updates from team

2. Review project status
o Due Date: (e.g., No specific deadline)
o Status: Not Started

[Task 6]: (e.g., Research new tools for team

collaboration)

o Due Date: (e.g., Next week)

o Status: Not Started
o Subtasks:

23
 1. Explore tools

2. Read reviews and features

4. Recurring Tasks

[Task 7]: (e.g., Weekly team check-in)

o Due Date: (e.g., Every Monday at 9 AM)

o Status: Ongoing

Steps to Maintain the To-Do List :

 Update daily: Mark completed tasks, add new

ones, and adjust priorities based on urgency and
deadlines.

 Break down tasks: Split bigger tasks into manageable

subtasks.

24
 References

https://chatgpt.com/

https://www.w3schools.com/

25