A Project Report on

Design & Develepment of IST Project Task Management System

A project report submission for the fulfillment of the requirements for the degree of BSc
(Honors) in ECE

Submitted By
Registration No: 17508006634
Roll No: 1800028
Session: 2017-2018
Department of Electronics and Communication Engineering
Institute of Science and Technology
National University, Bangladesh

Submission Date: September 13, 2023

 ii

DECLARATION

I hereby declare that I have completed the work of Design & Development of IST Project Task
Management System under the supervision of Md. Shawkot Hossain, Faculty, Department of
Electronics and Communication Engineering (ECE), Institute of Science and Technology (IST),
affiliated with the National University, Bangladesh. I also declare that neither this project nor
any part of this has been submitted elsewhere for this award of any degree.

Student’s Signature
Registration No: 17508006634
Session: 2017-2018
Department of ECE
Institute of Science and Technology
 iii

APPROVAL

Design and Development of IST Project Task Management System by Md. Tansocelar Ahmed
Dorjoy, Registration No: 17508006634 to the department of Electronics and Communication
Engineering (ECE), Institute of Science and Technology (IST), Dhaka, Bangladesh has been
accepted as satisfactory for the fulfillment of the requirements for the Degree of Bachelor of
Science in Electronics and Communication Engineering (ECE) under National University and
approved as to its style and contents.

Signature of Internal Examiner Signature of External Examiner

1.
Md. Shawkot Hossain
Faculty
Department of ECE 2.
Institute of Science and Technology
 iv

ACKNOWLEDGEMENT

This is my humble attempt to present my gratitude in preparing this report. I have only drawn
upon my own experience as a student of Electronics Communication and Engineering. This
project would have been possible without the dedication and contributions of a number of
individuals. First and foremost, I would like to express my gratitude to Allah for always helping
me, then I would like to thank, Md. Shawkot Hossain, Faculty, Department of Electronics and
Communication Engineering (ECE) for agreeing to supervise me during the project. His
eagerness helped me in every step of the way as well as encouraged me to work with full effort.
 v

ABSTRACT
Managing and controlling final year student projects traditionally is a laborious task. This project
aims to revolutionize the process by introducing an automated system that streamlines all
project-related activities. The IST project task management system is a web-based portal
designed to efficiently manage, control, and monitor final year student projects, benefiting both
students and supervisors. The system begins with administrative registration of all students, who
subsequently gain access to the system through personalized login credentials. Once logged in,
students have the autonomy to form project groups according to their preferences. Similarly,
supervisors use their unique login credentials to access the system. A central feature of this
system is the project coordinator, responsible for assigning tasks to students. This automation
eliminates the need for manual allocation and ensures efficient project management. Ultimately,
the IST project task management system offers a comprehensive solution to simplify the
management and control of final year student projects, making the process more accessible,
organized, and productive.
 vi

Abbreviation Meaning Page

IST Institute of Science and Technology……………………………….. 2
IST-PTMS Institute of Science and Technology Project Task Management
System………………………………………………………………. 7
SDLC Software Development Life Cycle…………………………………. 9
V-Model Validation/Verification……………………………………………... 10
RAD Rapid Application Development…………………………………… 11
GUI Graphical User Interface……………………………………………. 14
WBS Work Breakdown Structure………………………………………… 17
RAM Random Access Memory…………………………………………… 18
GB Giga Byte…………………………………………………………… 18
PHP Hypertext Processor / server-side programming language…………. 18
SQL Structured Query Language………………………………………… 19
DFD Data Flow Diagram…………………………………………………. 22
RDBMS Relational Database Management System………………………….. 24
MySQL RDBMS developed by Oracle……………………………………… 24
XML Extensive Markup Language……………………………………….. 25
ER Entity Relationship…………………………………………………. 25
MVC Model View Controller….………………………………………….. 29
LIST OF ABBREVIATION
 vii

LIST OF FIGURES

FIGURE NO FIGURE NAME PAGE

3.1 Phases of Iterative Waterfall Model 12
4.1 Architecture of the Proposed System 18
4.2 Operational Block Diagram of the Proposed System 19
4.3 PERT Chart 21
4.4 Use Case Diagram of the Proposed System 21
4.5 Block Diagram of 0 Level DFD 23
4.6 Block Diagram of 1 Level DFD 24
4.7 Database Server Diagram 25
4.8 ER Diagram of the Proposed System 27
 viii

TABLE OF CONTENTS

Chapter 1: Introduction 1
1.1 Introduction 2
1.2 Motivation 2
1.3 Scope of the work 2
1.4 Objective 3
1.5 Organization of the Project 3

Chapter 2: Literature Review 5

2.1 Introduction 6
2.2 Historical Background 6
2.2.1 Existing System 6
2.3 Summary 7

Chapter 3: System Analysis 8

3.1 Introduction 9
3.2 Software Development Life Cycle (SDLC) 9
3.2.1 Different Types of SDLC 10
3.2.2 Iterative Waterfall Model 11
3.3 Feasibility Study 12
3.3.1 Economical Feasibility 13
3.3.2 Technical Feasibility 13
3.3.3 Operational Feasibility 14
3.4 Summary 15

Chapter 4: Proposed System Design 16

4.1 Architecture of the Proposed system 17
 ix

4.2 Requirements 18
4.3 Primary Design Phase 19
4.4 Secondary Design Phase 19
4.5 User Interface Design 20
4.6 Use Case Diagram of the Proposed System 21
4.7 DFD 22
4.7.1 Context Level DFD 22
4.7.2 Level 1 DFD 23
4.8 Database Analysis 24
4.8.1 Relational Database Management System (RDBMS) 24
4.9 Entity Relationship Diagram 25

Chapter 5: Proposed System Implementation 28

5.1 Introduction 29
5.2 Implementation Methodology 29
5.3 Some Other Glimpse of the Project 30
Chapter 6: System Testing 39
6.1 Introduction 40
6.2 Testing Process 40
6.2.1 White Box Testing 40
6.2.1.1 Result of White Box Testing 40
6.2.2 Black Box Testing 41
6.2.2.1 Result of Black Box Testing 41
6.2.3 Alpha Testing 41
6.2.4 Beta Testing 41
6.2.5 Unit Testing 41
6.2.5.1 Result of Unit Testing 42
6.2.6 Integration Testing 42
6.2.6.1 Result of Integration Testing 42
6.2.7 System Testing 43
 x

6.3 Summary 43
Chapter 7: Future Work and Conclusion 44
7.1 Future Modification 45
7.2 Conclusion 45
References 46
 1

Chapter 1: Introduction
 2

1.1 Introduction
The IST Project Task Management System has been developed to override the problems
prevailing in the practicing manual system. This web-based system is supported to eliminate, and
in some cases reduce the hardships faced by this existing system. Moreover, this system is
designed for the particular need of the institution to carry out operations in a smooth and
effective manner.
The application is reduced as much as possible to avoid errors while entering the data. It also
provides error message while entering invalid data. No formal knowledge is needed for the user
to use this system. Thus, by this all it proves it is user-friendly. The IST Project Task
Management System, as described above, can lead to error free, secure, reliable and fast
management system. It can assist supervisors, students to concentrate on their other activities
rather to concentrate on the record keeping. Thus, it will help institutions to concentrate on
record of all project keeping. Thus, it will help institutions in better utilization of resources.
Every institution, whether big or small, has challenges to overcome and manage the information
of Events, Students, and Files. IST Project Task Management System has different Student
needs; therefore, we design IST project task management systems that are adapted to your
managerial requirements. This is designed to assist in strategic planning and will help you ensure
that your institution is equipped with the right level of information and details for your future
goals. Also, for those busy executives who are always on the go, our systems come with remote
access features, which will allow you to manage your workforce anytime, at all times. These
systems will ultimately allow you to better manage resources.

1.2 Motivation
The primary reason for selecting IST projects task management system help to improve
communication by providing a centralized place for teams to discuss tasks and exchange
information.
Team members can also report on ongoing and completed tasks to their supervisor, who can
analyze this information and make necessary adjustments. Rather than approaching every task
with the same level of importance, prioritizing tasks based on their urgency and importance is
often helpful.

1.3 Scope of the Work

It may help collecting perfect management in details. In a very short time, the collection will be
obvious, simple and sensible. It will help a person to know the management of passed year
perfectly and vividly. It also helps in current all works relative to the Supervision of Project Task
Management System. It will be also reduced the cost of collecting the management & collection
procedure will go on smoothly.
Our project aims at institution process automation, i.e., we have tried to computerize various
processes of the students through IST Project Task Management System.
 3

The scope of the study encompasses:

 In computer system the person has to fill the various forms & number of copies of the
forms can be easily generated at a time.
 To assist the students in capturing the effort spent on their project working
areas.
 To utilize resources in an efficient manner by increasing their productivity
through automation.
 It satisfies the user requirement.
 Be easy to understand by the user and operator.
 Have a good user interface

1.4 Objectives
Our project is an online task supervision, online to do list that helps individuals’ educational
institutions effectively organize their projects and tasks. The other objective of the project follows:

 To develop a way to reduce time complexity.

 Using this project as calendar for appointments.
 Manage projects using dashboards between team members.
 To develop a new web base project management approach on the students' project to
evaluate the new project
 To collect data and evaluate the task of the project by monitoring the up-to-date activities

1.5 Organization of the Project

In the project book the topics been discussed are:
In 1st Chapter Background study for the project. This includes studying on web-based project, and
its concept, including types of web-based management system.
In 2nd Chapter of this book is background study of project IST project task management system
where we study about existing system history, limitations and why the proposed system’s used,
how it’s used.
In 3rd Chapter of this book is background study of feasibility study where numerous feasibilities are
studied in our project, why it’s used, how it’s used, and SDLC model of our system
In 4th Chapter is about proposed system design and development. This chapter is divided into three
sections. The first section is about our proposed system discussed in, the second section and third
section concentrate on designing and describing various module works of the system.
In 5th Chapter is requirements and analysis. This chapter the discuss about the requirements and the
database of the system have been discussed.
 4

In 6th Chapter we have discussed about the implementation of our proposed system and testing the
system in several steps also we attached significant glimpse of our project.
 In the final chapter is all about conclusion and future work for this project.
 5

Chapter 2: Literature Review

 6

2.1 Introduction
This chapter outlined the sections in this chapter that is to say Introduction, Theoretical
underpinning of the study of web-based management project, and literature review of
computerized data collection and student project team member records, and record management
on the student project list. This section presents a review of related literature to the study of IST
project task management system and project field records: the review has been done in
accordance with the research objectives which are impact of computerized data collection on
maintenance of student record, computerized information protection on student task record and
computerized record management in maintenance of student records in Institution of Science &
Technology.

2.2 Historical Background

The old manual system was suffering from a series of drawbacks. Since whole of the system was
to be maintained with hands the process of keeping, maintaining and retrieving the information
was very tedious and lengthy [1]. The records were never used to be in a systematic order. there
used to be lots of difficulties in associating any particular transaction with a particular context
[2]. If any information was to be found it was required to go through the different registers,
documents there would never exist anything like report generation [3]. There would always be
unnecessary consumption of time while entering records and retrieving records. One more
problem was that it was very difficult to find errors while entering the records. Once the records
were entered it was very difficult to update these records [4].
The reason behind it is that there is lot of information to be maintained and have to be kept in
mind while running the business for this reason we have provided features Present system is
partially automated (computerized), actually existing system is quite laborious as one has to enter
same information at three different places [6].

2.2.1 Existing Systems

Existing systems of the system of the project management is a manual. Project coordinator or
guide gives task for student manually. Student complete the work which is given by coordinator
or guide and submits manually, in this system all work is done by manually so it can take more
time to complete project related work [7]. Project coordinator or guide requires remembering in
mind when student completed the work so it is difficult for Project coordinator or guide which
student completed the task and when. In the existing system does not help users to get right
information at right time and user cannot manage project development easily to achieve the main
goal [8].

Limitations of existing system:

1. It is time consuming.
2. Right information is not retrieved at right time.
3. Any updates to the data by team members or the Project coordinator or guide cannot see
immediately by the rest of the team.
4. All work is done manually.
 7

Following points should be well considered:

Documents and reports that must be provided by the new system. there can also be few reports,
which can help management in decision-making and cost controlling, but since these reports do
not get required attention, such kind of reports and information were also identified and given
required attention.
 Details of the information needed for each document and report.
 The required frequency and distribution for each document.
 Probable sources of information for each document and report.
 With the implementation of computerized system, the task of keeping records in an
organized manner will be solved. The greatest of all is the retrieval of information, which
will be at the click of the mouse. So, the proposed system helps in saving the time in
different operations and making information flow easy giving valuable reports.

2.3 Summary
Finally, since the data generated in day to day, management by educational institutions of
information Technology. Formal according to the registrar, it is worthwhile and full to develop a
strong digital web-based management system for the institute or university to hold the large
amount of data that is generated. The proposed system, IST-PTMS, should be able to stand
digitalized & web based because time consuming should be kept as long as is necessary to:
1. Fulfill and discharge the contractual obligations established between the institution and
the student, including the completion of any non-academic disciplinary action;
2. Provides good effect on the academic career and achievements of the student to
employers, licensing and other organizations, as well as to the student as part of their
lifelong learning record. The supervision management system gathered whilst reviewing
existing.
3. Literature on student project task management system has been very useful in the
development of the proposed system. The project when completed will provide an
efficient way to store and organize data than spreadsheet. It will also serve as a
centralized facility that can easily be modified and quickly shared among multiple users.
The proposed system will have a well-designed interface that allows users to interact with
the system. Therefore the study from different countries and nations explained task
management system on team record & project data record has helped in improving and
providing efficient information and timely to the information needed to all the student
carrier build up time period and when comes to Livingstone international university has
always been problematic for example Cases of lost marks, incorrect grades, delays in
issuing academic awards have all been too common therefore findings will reveal
manually control records of project task management as the biggest problem facing
Universities & Institutions.
 8

Chapter 3: System Analysis

 9

3.1 Introduction

System analysis is an intricate and vital process within the realm of system development,
encompassing the meticulous gathering and interpretation of factual data, along with the
diagnosis of existing issues. In the context of the IST Project Task Management System, this
procedure is aimed at identifying areas for enhancement and recommending optimal
improvements. It is a multifaceted problem-solving endeavor, necessitating robust
communication between the system's end-users and its developers. At the core of system analysis
lies a comprehensive scrutiny of the existing system's minutiae. The system analyst, akin to an
interrogator, delves deep into the operational mechanics of the current system, treating it as an
integrated whole. The analyst discerns the inputs driving the system and traces the diverse
organizational outputs to their respective processes. This holistic approach is essential for
grasping the system's intricacies and functioning. System analysis assumes the mantle of
consciousness-raising, wherein problem awareness takes center stage. It involves the
identification of pertinent variables influencing decision-making, followed by a meticulous
synthesis of diverse factors. The ultimate goal is to derive an optimal, or at the very least
satisfactory, solution or course of action. Achieving this goal entails a comprehensive
exploration, employing techniques such as interviews and questionnaires to gather pertinent data.
The collected data undergoes rigorous scrutiny, leading to a comprehensive comprehension of
the existing system, aptly named the "existing system." The existing system then undergoes a
rigorous examination, aimed at pinpointing areas of concern. During this phase, the system
designer seamlessly transitions into the role of a problem solver, diligently resolving the
challenges that the enterprise faces. Proposed solutions are delineated and presented for
consideration. Subsequently, a systematic analytical comparison ensues between the proposal
and the existing system, culminating in the selection of the most viable approach. The endorsed
proposal is presented to the end-users for validation, forming a pivotal juncture in the iterative
process. User feedback is actively sought, and the proposal is subjected to review, with
modifications incorporated as necessary. This iterative loop persists until the user expresses
satisfaction with the proposal, signifying the convergence of user expectations and system
capabilities. The preliminary study is a foundational phase, serving as a precursor to more
extensive investigations into the system. It entails the same problem-solving ethos, necessitating
robust communication between system stakeholders. Throughout this phase, feasibility studies
are conducted, offering a preliminary insight into the system's activities. These insights guide the
formulation of strategies for the ensuing stages of in-depth system study and analysis.

3.2 Software Development Life Cycle (SDLC)

The Software Development Life Cycle (SDLC) is a critical framework that plays a pivotal role in
the successful execution of software projects. This abstract provides a concise overview of
SDLC, highlighting its key components and their significance.

SDLC is a systematic approach used by organizations to plan, design, develop, test, deploy, and
maintain software solutions efficiently. It encompasses well-defined phases, each with specific
objectives and deliverables. These phases typically include requirements gathering, system
design, coding, testing, deployment, and maintenance.
 10

The importance of SDLC lies in its ability to ensure that software projects are delivered on time,
within budget, and with the desired quality. Following a structured SDLC enables project teams
to effectively manage risks, maintain clear communication, and meet stakeholder expectations.
Furthermore, SDLC methodologies vary, with popular options including Waterfall, Agile, and
DevOps. The choice of methods depends on the project's complexity, requirements, and the
organization's culture.

In conclusion, understanding SDLC is fundamental to achieving successful software project

outcomes. By embracing the principles of SDLC and selecting the appropriate methodology,
project managers and teams can enhance collaboration, mitigate risks, and deliver software
solutions that meet both user needs and organizational objectives.

3.2.1 Different Types of SDLC

Waterfall Model:
The Waterfall Model is one of the oldest and most traditional SDLC methodologies. It follows a
linear and sequential approach, where each phase must be completed before moving on to the
next. This model is well-suited for projects with well-defined requirements and minimal changes
expected during development.

Agile Methodology:
Agile is an iterative and flexible approach to software development. It focuses on collaboration,
customer feedback, and delivering small, functional increments of software called "sprints."
Agile methodologies, such as Scrum and Kanban, are ideal for projects where requirements may
evolve and adapt over time.

DevOps:
DevOps is more than just an SDLC methodology; it's a cultural and technical movement that
emphasizes collaboration between development and operations teams. It aims to automate and
streamline the entire software delivery pipeline, enabling frequent and reliable software releases.

Iterative Model:
The Iterative Model breaks down the project into smaller iterations, each of which goes through
the phases of SDLC. After each iteration, there's a review, and improvements are made before
moving to the next iteration. This approach is beneficial when requirements are not entirely clear
initially.

Spiral Model:
The Spiral Model combines iterative development with elements of the Waterfall Model. It
focuses on risk assessment and management by revisiting and refining project stages in a spiral
pattern. This approach is suitable for large, complex projects with evolving requirements.

V-Model (Validation and Verification Model):

The V-Model is an extension of the Waterfall Model that emphasizes the importance of testing
and validation at each stage of development. It highlights the direct relationship between a
development phase and its corresponding testing phase, ensuring rigorous quality control.
 11

RAD (Rapid Application Development):

RAD is designed for projects where speed and user involvement are critical. It prioritizes rapid
prototyping, iterative development, and user feedback to quickly deliver functional software.
RAD is particularly effective for projects with short timeframes.

Big Bang Model:

The Big Bang Model is the least structured of all SDLC methodologies. It involves minimal
planning and documentation, focusing on developing the entire software product at once. This
approach is often used for small projects or proof-of-concept development.

Incremental Model:
The Incremental Model divides the project into smaller parts or increments. Each increment
represents a portion of the complete system, and new functionality is added incrementally. This
approach is useful for projects with evolving requirements and allows for early user feedback.

Each of these SDLC methodologies has its own set of strengths and weaknesses, making it
essential to choose the one that aligns best with the project's specific requirements, constraints,
and goals.

3.2.2 Iterative Waterfall Model

In this project, we have implemented this model. The Iterative Waterfall Model is a modified
version of the traditional Waterfall Model. In this approach, the software development process is
divided into small iterations or cycles, where each cycle represents a miniature Waterfall Model
in itself.

After each iteration, a partial but potentially usable version of the software is produced and
evaluated. This allows for ongoing feedback and adaptation throughout the project. If changes or
improvements are needed, they can be incorporated in subsequent iterations. This iterative
process continues until the final software product is complete.

The Iterative Waterfall Model combines the structured approach of the Waterfall Model with the
flexibility to make adjustments as needed, making it more adaptable to changing requirements or
evolving project circumstances. It's particularly useful when initial project requirements are not
entirely clear or when there's a need for ongoing refinement during development.

This model contains 6 phases:

I. Feasibility study - The feasibility has a look at the activity that involves the evaluation of
the problem and a series of relevant records referring to the product. The most important
purpose of the feasibility study is to determine whether it might be financially and
technically viable to expand the product.
II. Requirement analysis and specification - This segment intends to understand the exact
requirements of the users and to record them well.
 12

III. Design - The goal of this section is to convert the requirement specification into a shape
that is appropriate for implementation in a few programming languages.

Figure 3.1: Phases of Iterative Waterfall Model

IV. Implementation and unit testing - At some stages in this segment, the design is applied.
Small modules are examined in isolation from the rest of the software program product.
Integration and system testing - In this, all the modules are included after which checked
collectively.
V. Operation and maintenance - The release of the software program inaugurates the
operation and life cycle section of the operation. The phases usually occur in this order.
Revise and beautify the Prototype note down the remarks and the assessment remarks and
mention and make plans and adjustments in the gadget layout. The adjustments can be
well-known in the future and once more integrated within the new Prototype advanced
and the cycle may be repeated until the developer and the patron’s expectancies are met.

3.3 Feasibility Study

Upon the completion of the IST project task management system and a comprehensive analysis
of both existing and potential functionalities inherent to the system, the subsequent imperative
involves conducting an in-depth feasibility study for the project at hand. It is pertinent to
acknowledge that, theoretically, all projects possess feasibility given boundless resources and an
infinite time frame. Within the context of this feasibility study, a meticulous evaluation ensues,
encompassing a thorough exploration of conceivable avenues to proffer a resolute solution to the
stipulated quandary. In essence, the fundamental objective of this feasibility study is to
 13

meticulously deliberate upon and assess the plethora of strategies that could be employed to
address the given problem statement. The crux of this endeavor is to fashion a proposed solution
that not only impeccably aligns with the gamut of user requisites but also exhibits a remarkable
degree of adaptability, thus ensuring its viability in accommodating forthcoming alterations
predicated upon emergent demands. By effecting such a rigorous scrutiny, the envisaged solution
is anticipated to transcend the realm of immediate necessity, aspiring to achieve an enduring
quality that resonates with the evolving needs of its users. Therefore, the paramount aspiration
underlying this feasibility study is to forge a solution that stands as a testament to its intrinsic
resilience, enabling seamless integration of future modifications, and thereby charting a
trajectory of sustainable evolution in response to the dynamic landscape of requirements yet to
manifest.

3.3.1 Economical Feasibility

The contemplation of this facet emerges as an indispensable and pivotal component within the
developmental process of a project. In this vein, meticulous deliberation and judicious
consideration are vested in the selection of technology, a pivotal determinant shaped by the
overarching parameter of minimizing costs to the utmost extent feasible.

Intrinsic to this decision-making process is the prudent allocation of resources, wherein due
cognizance is directed towards the financial implications emanating from both hardware and
software requisites. It is of paramount significance to acknowledge that the onus of shouldering
these costs squarely rests upon the organizational entity.

In a broader perspective, the evaluative calculus extends towards a comprehensive estimation,

wherein the anticipated benefits poised to accrue to the organization from the envisaged system
are poised to substantially outweigh the initial expenditure outlay and subsequent operational
costs requisite for the sustained functioning of the system.

Hence, within the contours of this discerning evaluation, a prognostication emerges wherein the
projected advantages that stand to be reaped by the organization are poised to serve as a
formidable counterbalance to the preliminary fiscal disbursements and the ensuing financial
commitments tethered to the perpetual operation and maintenance of the envisioned system.

3.3.2 Technical Feasibility

Embedded within this process was a comprehensive inquiry encompassing multifaceted

dimensions of function, performance, and constrictions, all of which wield a potential impact on
the overarching capacity to engender a system of commendable adequacy. A pivotal juncture
was reached in which an exhaustive examination was undertaken, diligently dissecting and
scrutinizing the intricate interplay of these aspects.

The endeavor of this feasibility study was characterized by a rigorous exploration, extending its
purview to encompass a holistic survey of the complete spectrum of functionalities envisioned
for integration within the system. These functionalities were meticulously delineated and
delineated within the framework of the System Requirement Specification (SRS), constituting a
 14

comprehensive blueprint that demarcated the contours of the system's capabilities. An

overarching aim was to ascertain the viability and attainability of every constituent functional
facet.

In order to furnish an exhaustive and robust assessment, the approach adopted was one of
methodical variance, where a diverse array of frontend and backend platforms were subjected to
meticulous scrutiny. Through a series of rigorous evaluations, the spectrum of feasibility was
meticulously probed, addressing the intricate interplay between the envisaged functionalities and
the technological underpinnings offered by diverse platform choices.

The overarching goal underscoring this multifaceted investigation was to ascertain not only the
technical plausibility but also the practical realizability of every aspired functionality, thereby
engendering a nuanced comprehension of the extent to which the proposed functionalities could
be seamlessly integrated within the technological fabric of the chosen platforms. This process
was underpinned by a resolute commitment to elucidate the intricate nexus between system
capabilities and technological constraints, thereby paving the way for a judiciously informed
decision-making paradigm in the pursuit of an optimal and viable solution.

3.3.3 Operational Feasibility

Undoubtedly, the envisaged system stands as a quintessential exemplar of a Graphical User

Interface (GUI)-centric architecture, meticulously designed to exude an aura of user-friendliness
that transcends technical complexities. A paramount consideration underscored the seamless
integration of self-explanatory input mechanisms, artfully architected to resonate with even the
most uninitiated user. This distinctive facet was underpinned by an unwavering commitment to
democratize user interaction, ensuring accessibility and ease of comprehension akin to a
layperson's perspective.

An integral dimension of this overarching strategy entailed the meticulous orchestration of

comprehensive training endeavors. These immersive training sessions were thoughtfully
structured to traverse the intricacies of the system, thereby equipping users with an intrinsic
understanding of its underlying essence. The strategic objective inherent in this pedagogical
initiative was to imbue users with a sense of familiarity and confidence vis-à-vis the novel
system, fostering a state of comfort that harmonizes seamlessly with the contours of the
operational landscape.

Drawing upon the trajectory of our comprehensive study, a salient observation surfaces wherein
clients have evidenced a palpable sentiment of contentment and felicity. This salutary outcome is
intrinsically linked to the transformative impact of the system, which has manifestly served as a
catalyst in alleviating their burdensome operational overheads. By deftly streamlining erstwhile
convoluted processes, the system has engendered an evident alleviation in their functional
workload, culminating in a discernible enhancement in operational efficiency.

The fulcrum of our empirical inquiry not only rests on the technical efficacy of the system but
transcends into the realm of stakeholder satisfaction. This substantiated contentment, articulated
by clients, substantiates the transformative influence of the system, catalyzing a paradigm shift in
their operational dynamics. As a result, the envisioned system stands as a testimony to its
 15

capacity to effectuate tangible and consequential change, ameliorating the operational landscape
and fostering an environment that is imbued with newfound levels of dexterity and efficacy.

3.4 Summary

In order to successfully create the ultimate platform which is most suitable for the users,
necessary steps and efficient methods are applied, resulting in a fine outcome for the whole
project. Finding the disordered process of the traditional existing system and refining them
makes it the best outcome with utmost efficiency to the users. The IST Project Task Management
System solves the common issues faced by manual systems by modernizing the system
according to their needs and fulfillment. The list of all project teams and the monitoring system
in the Project is making it appealing to the users. To make the system responsive and functional,
all the prerequisite and necessary resources are gathered and then implemented. Carefully
Software engineered IST Project Task Management broadens the outlook of users who are
satisfied by the service that our system will provide. The way that the project works is figured
out and marked carefully on the main and important aspects, technology and process, and
methods used in the whole project. After precisely identifying the system, we proceed to the next
stage of System Design which is briefly discussed in the next Chapter.
 16

Chapter 4: Proposed System Design

 17

4.1 Architecture of the System

In the proposed system, we aim to create a comprehensive platform for efficiently managing and
overseeing project-related tasks completed by both students and the Project Coordinator or
Supervisor. The supervisor will be responsible for updating project-related information,
monitoring students' task completion, and tracking progress through a visual chart based on the
Work Breakdown Structure (WBS) framework. Students will access the system to retrieve
assigned tasks, update task status, complete the work within specified deadlines, and submit their
completed tasks to the project task management system.

During this particular phase, the focus is on constructing a logical framework that satisfies the
specified requirements. The design phase of website development involves the transformation of
the client's outlined needs into a functional and coherent system. This design process typically
unfolds in the following three stages:

Requirement Elaboration: During this stage, the initial requirements are thoroughly examined
and detailed. This involves breaking down the project into manageable components and clearly
defining the functionalities that need to be implemented.

Conceptual Design: In this step, a high-level concept is crafted based on the elaborated
requirements. This involves designing the overall structure, flow, and interaction between
different system modules. A conceptual representation of the user interface and system
architecture is also developed.

Detailed Design: The final step involves delving deeper into the system's design. Detailed
specifications for each module and component are created, including user interfaces, databases,
data flow diagrams, and algorithms. This stage lays the foundation for the actual implementation
of the system.
 18

Figure 4.1: Architecture of the proposed system

In this phase, a logical system is built which fulfils the given requirements. Design phase of
website development deals with transforming the clients 's requirements into a logically working
system. Normally, design is performed in the following in the following three steps:

4.2 Requirements

A. Hardware

1. Processor: Core i3
2. RAM: 4GB or more
3. Hard disk: 16 GB or more

B. Software Specification

1. Windows Operating System.

2. Composer
3. PHP 8.1
4. Apache server
 19

5. My SQL.
6. Visual studio

4.3 Primary Design Phase

In this phase, the system is designed at block level. The blocks are created on the basis of
analysis done in the problem identification phase. Different blocks are created for different
functions emphasis is put on minimizing the information flow between blocks. Thus, all
activities which require more interaction are kept in one block.

4.4 Secondary Design Phase

In the secondary phase the detailed design of every block is performed.

The general tasks involved in the design process are the following:

1. Design various blocks for overall system processes.

2. Design smaller, compact and workable modules in each block.
3. Design various database structures.
4. Specify details of programs to achieve desired functionality.
5. Design the form of inputs, and outputs of the system.
6. Perform documentation of the design.
7. System reviews.

Figure 4.2: Operational Block Diagram of Proposed System

 20

A. Admin Module
1) Login: - Using username and password Project coordinator login into system. If
authentication is failed, Project coordinator cannot login into system.
2) Upload file: Project coordinator upload file for student information.
3) View Files: - Project coordinator View all files uploaded by student.
4) View Gant Chart: - Project coordinator view Gant chart of student working.

B. Project coordinator Module

1) Login: - Using username and password Project coordinator login into system. If
authentication is failed, project coordinator cannot login into system.
2) Upload updates: - Project coordinator uploads and updates the project related work.
3) Upload file: Project coordinator upload file for student information.
4) View Files: Project coordinator View all files uploaded by student.
5) View Gant Chart: Project coordinator view Gant chart of student working.

C. Student Module
1) Student Login: - Using username and password student login into system. If authentication is
failed, student cannot login into system.
2) View updates: Student views all updates of the work which uploaded by Project coordinator
or guide.
3) Upload file: Student upload file and submit the completed work.
4) View Gant Chart: Student view Gant chart of student working.

4.5 User Interface Design

It is concerned with the dialogue between a user and the computer. It is concerned with
everything from starting the system or logging into the system to the eventually presentation of
desired inputs and outputs. The overall flow of screens and messages is called a dialogue.

The following steps are various guidelines for User Interface Design:

1. The system user should always be aware of what to do next.

2. The screen should be formatted so that various types of information, instructions and messages
always appear in the same general display area.
3. Message, instructions or information should be displayed long enough to allow the system
user to read them.
4. Use display attributes sparingly.
5. Default values for fields and answers to be entered by the user should be specified.
6. A user should not be allowed to proceed without correcting an error.
7. The system user should never get an operating system message or fatal error.
 21

Figure 4.3: PERT Chart

4.6 Use Case Diagram of the Proposed System

 22

Figure 4.4: Use Case Diagram of the Proposed System

4.7 Data Flow Diagram (DFD)

DFD graphically represents the functions, or processes, which capture, manipulate, store, and
distribute data between a system and its environment and between components of a system.
The visual representation makes it a good communication tool between User and System
designer. The structure of DFD allows starting from a broad overview and expanding it to a
hierarchy of detailed diagrams. DFD has often been used due to the following reasons:

 Logical information flow of the system

 Determination of physical system construction requirements
 Simplicity of notation
 Establishment of manual and automated systems requirements

4.7.1 Context Level DFD

The initial stage of the Data Flow Diagram (DFD) is referred to as the Level 0 DFD, commonly
known as the context-level DFD. This pivotal diagram offers an overarching depiction of the
entire system under consideration. It serves as a comprehensive outline that illustrates the
fundamental interactions and data flows within the system.

The context-level DFD provides an encompassing overview of the interactions between external
entities and the system itself. By presenting an abstract representation of data movement,
 23

processes, and external entities, this diagram captures the high-level functionalities and
interconnections that constitute the core essence of the system.

In the context-level DFD, external entities are depicted as sources or destinations of data,
representing entities outside the scope of the system, such as users or other systems. Processes
are represented as distinct functions or operations that transform input data into meaningful
outputs. These processes, although detailed in subsequent DFD levels, are presented at a higher
level of abstraction in the context-level DFD.

Furthermore, the context-level DFD serves as a foundation for constructing more detailed DFDs
in subsequent levels. These successive levels, such as the Level 1 DFD (also known as the (O)
level DFD), delve into the finer details of the system by decomposing processes into sub-
processes and elucidating the intricate data flows among them.

In the specific case of the IST Project Task Management System project, the context-level DFD
elucidates the interaction between the system and its users, particularly emphasizing the role of
the admin user. The admin user, upon logging into the system, assumes a pivotal role by
conducting a range of activities that govern the functioning of the system. The context-level
DFD visually underscores the centrality of the admin user and their operational influence within
the broader scope of the project.

Figure 4.5: Block Diagram of 0 Level DFD

4.7.2 Level 1 DFD

The admin side DFD describe the functionality of admin. Admin is a responsible person who run
the project. After login to system admin can first add teacher then teacher’s detail and add
student. Admin can see all the progress of all team.
 24

Figure 4.6: Block Diagram of 1 Level DFD

4.8 Database Analysis

The method of study is based on information from our institution. There is information provided
regarding the teachers who work at our institution as well the student information added.

4.8.1 Relational Database Management System (RDBMS)

This is an RDBMS based project which is currently using MySQL for all the transaction
statements. MySQL is an opensource RDBMS System.
A relational database management system (RDBMS) is a database management system (DBMS)
that is based on the relational model as invented by E. F. Codd, of IBM's San Jose Research
Laboratory. Many popular databases currently in use are based on the relational database model.
RDBMSs have become a predominant choice for the storage of information in new databases
used for financial records, manufacturing and logistical information, personnel data, and much
more since the 1980s. Relational databases have often replaced legacy hierarchical databases and
network databases because they are easier to understand and use. However, relational databases
 25

have been challenged by object databases, which were introduced in an attempt to address the
object-relational impedance mismatch in relational database, and XML databases.

Figure 4.7: Database Server Diagram

4.9 Entity Relationship Diagram

The Entity-Relationship (E-R) Model stands as a prominent and widely adopted high-level
conceptual data model within database management. Renowned for its effectiveness, the E-R
Model, along with its various iterations, holds a significant role in facilitating the conceptual
design of database applications. Its core principles are deeply ingrained in the foundations of
many database design tools, making it an essential framework in the field.
A database, when harmoniously aligned with an E-R diagram, finds its representation in the
relational system through a meticulously organized collection of tables. This relational
manifestation ensures that the data architecture adheres to the fundamental constructs of the E-R
Model, capturing the essence of entities, their attributes, and the intricate relationships that
interlink them.
Central to the concept of the E-R Model is the notion of abstraction, a process that operates as a
transformative veil, concealing intricate technical intricacies while artfully accentuating the
elements pertinent to the application's context. In effect, the model's capacity to distill complex
 26

information into a simplified yet meaningful framework elevates the focus on the salient aspects
that directly contribute to the application's functionality and utility.
At the crux of this abstraction lies the data model—an intricate mechanism adept at delivering
this essential layer of separation between the intricacies of database management and the
pragmatic requirements of real-world applications. Serving as a bridge between these realms, the
data model empowers developers and designers to engage with the intricacies of data
organization and manipulation while maintaining a heightened emphasis on the overarching
objectives of the application.
Data modeling, a pivotal practice rooted in the principles of the E-R Model, embarks on a
journey to encapsulate and depict the entities that populate the database and the intricate web of
relationships that bind them. Through meticulous representation and insightful structuring, data
modeling enables a tangible manifestation of the conceptual relationships between entities,
establishing a coherent framework for the storage, retrieval, and manipulation of data.
In conclusion, the E-R Model transcends its status as a mere conceptual framework; it is an
indispensable tool that shapes the landscape of database design. Its ability to seamlessly
transform complex real-world scenarios into abstract representations, coupled with its profound
influence on the practice of data modeling, cements its position as a cornerstone in the realm of
database management, offering both guidance and inspiration for those who navigate the
intricate tapestry of data-driven applications.
 27

Figure 4.8: ER Diagram of the Proposed System

 28

Chapter 5: Proposed System Implementation

 29

5.1 Introduction

In our proposed system, we have developed a system intended to effectively manage and
streamline all tasks associated with projects, which are undertaken by students. This system
serves as a centralized platform where various project-related activities can be seamlessly
coordinated. One of the core functionalities of this system involves the facilitation of interactions
between project supervisors and students.

Primarily, the system empowers project supervisors with the capability to modify and update
project-related information. This functionality ensures that supervisors can easily make
adjustments to project parameters, requirements, and other relevant details as necessary.
Additionally, supervisors are granted the ability to access and review the work completed by
individual students at specific junctures in time. This feature provides a valuable overview of the
progress made by students and allows supervisors to offer timely feedback and guidance.

Furthermore, the system offers a comprehensive interface that showcases the progression of
student work. This real-time progress tracking mechanism offers supervisors insights into the
pace and quality of student contributions. Such visibility into the ongoing work of students
enables supervisors to make informed decisions, offer assistance where needed, and maintain a
cohesive understanding of project development.

In the operational workflow of the system, students play a crucial role in executing assigned
tasks within stipulated timeframes. Once a student successfully completes an assigned task
within the designated timeframe, they are prompted to input the completed task's details into the
supervision management system. This ensures that the system is updated with the latest task
information, thus reflecting accurate and up-to-date progress data.

To summarize, the system we have conceived is designed to serve as a comprehensive project

management tool tailored for student-involved projects. Its multifaceted features empower
project supervisors to dynamically modify project parameters, review student work, and track
project progress. Simultaneously, students benefit from a streamlined process that prompts them
to input completed task details into the system, ensuring the accuracy and currency of project-
related data.

5.2 Implementation Methodology

Model View Controller or MVC as it is popularly called is a software design pattern for
developing web applications. A Model View Controller pattern is made up of the following three
parts:
 Model- The lowest level of the pattern which is responsible for maintaining data.
 View - This is responsible for displaying all or a portion of the data to the user.
 Controller - Software Code that controls the interactions between the Model and View.
MVC is popular as it isolates the application logic from the user interface layer and supports the
separation of concepts. Here the Controller receives all requests for the application and then
 30

works with the Model to prepare any data needed by the View. The View then uses the data
prepared by the Controller to generate a final presentable response. The MVC abstraction can be
graphically represented as follows.

5.3 Some Other Glimpse of the Project

1. The super admin has added the admins

 31

2. The admins have added the Teachers

 32

3. The admins have added the students

4. A student is login into the server

 33

5. The student’s Dashboard

6. A student is creating a Team

 34

7. The team request is on pending status

8. The 2nd student of the team has the option of accepting or rejecting the request
 35

9. After accepting the team request the status has changed to ‘Agreed’

10. A team is making a proposal to the teacher for the supervision of their project
 36

11. A teacher is login into the server

12. Teacher’s dashboard

 37

13. Arrival of the project proposal to the teacher

14. Project details

 38

15. Team list for supervision for the teacher

 39

Chapter 6: System Testing

 40

6.1 Introduction
Testing is vital for the success of any software. no system design is ever perfect. Testing is also
come in two phases. first phase is during the software engineering that is during the module
creation. second phase is after the completion of software. this is system testing which verifies
that the whole set of programs hanged together.

6.2 Testing Process

For this project the system is tested through

 White Box Testing
 Black Box Testing
 Alpha Testing
 Beta Testing
 Unit Testing
 Integration Testing
 System Testing

6.2.1 White Box Testing

In this technique, the close examination of the logical parts through the project are tested by
cases that exercise species sets of conditions or loops. all logical parts of the project checked
once. errors that can be corrected using this technique are typographical errors, logical
expressions which should be executed once may be getting executed more than once and error
resulting by using wrong controls and loops. When the box testing tests all the independent part
within a module a logical decision on their true and the false side are exercised, all loops and
bounds within their operational bounds were exercised and internal data structure to ensure their
validity were exercised once.

6.2.1.1 Result of White Box Testing

The test case mentioned above passed successfully. No defects encountered.

6.2.2 Black Box Testing

6.2.2 Black Box Testing

 41

This method enables the admin to device sets of input techniques that fully exercise all
functional requirements for a program. black box testing tests the input, the output and the
external data. it checks whether the input data is correct and whether we are getting the desired
output.

6.2.2.1 Result of Black Box Testing

For entering the wrong password the system denied the access

6.2.3 Alpha Testing

Acceptance testing is also sometimes called alpha testing. Be spoke systems are developed for a
single customer. The alpha testing proceeds until the system developer and the customer agree
that the provided system is an acceptable implementation of the system requirements.

6.2.4 Beta Testing

On the other hand, beta testing is often conducted. During beta testing, a system is delivered
among a number of potential users who agree to use it. The customers then report problems to
the developers. This provides the product for real use and detects errors which may not have
been anticipated by the system developers.

6.2.5 Unit Testing

Each module is considered independently, it focuses on each unit of the system as implemented
in the source code. it is white box testing.
 42

6.2.5.1 Result of Unit Testing

The test case mentioned above passed successfully. No defects encountered.

SS)

The unit testing done included the testing of the following items:
 Functionality of the entire module/forms.
 Validations for user input.
 Checking of the Coding standards to be maintained during coding.
 Testing the module with all the possible test data.
 Testing of the functionality involving all type of calculations etc.
 Commenting successfully in the source files
After completing the Unit testing of all the modules, the whole system is integrated with all its
dependencies in that module. While System Integration, we integrated the modules one by one
and tested the system at each step. This helped in reduction of errors at the time of the system
testing.

6.2.6 Integration Testing

Integration Testing is a level of software testing where individual units are combined and tested
as a group. It's designed to test integrated software components to determine if they actually run
as one program. Testing is event driven and is more concerned with the basic outcome of screens
or fields. Integration tests demonstrate that although the components were individually
satisfaction, as shown by successfully unit testing, the combination of components is correct and
consistent. The task of the integration test is to check that components or software applications,
es components in a software system or-one step up-software applications at user level interact
without error.

6.2.6.1 Result of Integration Testing

All the test case mentioned above passed successfully. No defects encountered.
 43

6.2.7 System Testing

It is executing programs to check logical changes made in it with intention of finding errors. a
system is tested for online response, volume of transaction, recovery from failure etc. System
testing is done to ensure that the system satisfies all the user requirements.

The steps involved during System testing are as follows:

• Integration of all the modules/forms in the system.

• Preparation of the test cases.

• Preparation of the possible test data with all the validation checks.

• Actual testing done manually.

• Recording of all the reproduced errors.
• Modifications done for the errors found during testing.

The System Testing done included the testing of the following items:

• Functionality of the entire system as a whole.

• User Interface of the system.
• Testing the dependent modules together with all the possible test data scripts.
• Verification and Validation testing.
• Testing the reports with all its functionality.

6.3 Summary
The testing of the project involved comprehensive evaluation of its functionality, performance,
and reliability. Various testing methods were employed to ensure the project met its
requirements and delivered a high-quality user experience. Identified issues were addressed and
resolved, resulting in a stable and robust final product ready for end user.
 44

Chapter 7: Future Work and Conclusion

 45

7.1 Future Modification

The current system is developed for single department of the institute i.e., “Department of
Electronics and Communication Engineering of IST.” The further modification of the project is
to create or expand the system in such way that it can be used at various institute or organization
levels. It can be extended to more security. Using various levels of authentication and
verification more security and privacy issues can be maintained by using various aspects.

7.2 Conclusion
IST Project Task Management System (IST-PTMS) is a very effective application which can
be used to a great extent. IST-PTMS has many advantages over the traditional system. Some of
these advantages are centralized data, up-to-date status reporting, ease of use, backups etc. The
use of this application reduces the extra time and efforts required to manage and monitor the
final year projects in the institute. We are using a Laravel of PHP 8.1 to automatically assign the
guides to the groups of students and different phases of WBS (work breakdown structure) for
grading of the particular group. It also provides a good interface which is easy to understand by
the users and helps in adapting to the use of this web application.
 46

References
1. Seneviratna, GAD Pradeepa S and Nandasara, S T, “Web based project collaboration, monitoring and management
system”, (ICTer)-109-155/ 2014 IEEE.
2. Ram, C Sunitha, “SURVEY ON STUDENT PROJECT MANAGEMENT SYSTEM”, 2nd edition, PDEVM, Project
3. H. Wang, J. Zhang, and X. Wang, "A Web-Based Task Management System for Students," IEEE Transactions on
Education, vol. 56, no. 4, pp. 423-430, Dec. 2013.
4. S. Zhang, Y. Wang, and J. Zhang, "A Teacher-Student Collaboration Platform for Project-Based Learning," Proc. of
the IEEE International Conference on Learning Technologies (ICALT), 2016, pp. 123-128.
5. J. Li, Y. Zhang, and X. Wang, "A Mobile-Based Project Management System for Teachers," Proc. of the IEEE
International Conference on Education and Management Technology (ICEMT), 2017, pp. 173-178.
6. Z. Liu, Y. Wang, and X. Wang, "A Cloud-Based Project Management System for Students," Proc. of the IEEE
International Conference on Information and Education Technology (IEET), 2018, pp. 183-188.
7. Y. Zhang, J. Li, and X. Wang, "A Social Learning Platform for Project-Based Learning," Proc. of the IEEE
International Conference on Computer and Information Technology (ICCIT), 2019, pp. 233-238.
8. S. Wang, Y. Zhao, and X. Zhang, "A Cloud-Based Learning Management System for Project-Based Learning," Proc.
of the IEEE International Conference on Information and Education Technology (IEET), 2020, pp. 193-198.