8 TH Sem Report
8 TH Sem Report
A PROJECT REPORT
Submitted by
211210116013
BACHELOR OF ENGINEERING
in
Information Technology
April, 2025
Apollo Institute of Engineering & Technology
Ahmedabad
CERTIFICATE
This is to certify that the project report submitted along with the project
year 2024-25.
DECLARATION
We hereby declare that the Internship / Project report submitted along with the
Internship/ Project entitled PROJECT TRACKER submitted in partial
fulfillment for the degree of Bachelor of Engineering in
INFORMATION TECHNOLOGY to Gujarat Technological University,
Ahmedabad, is a bonafide record of original project work carried out by me at
GROWNITED PVT. LTD. under the supervision of RAHUL KIRPEKAR
and that no part of this report has been directly copied from any students'
reports or taken from any other source, without providing due reference.
i
ACKNOWLEDGMENTS
I am grateful to our guides, Mr. Rahul Kirpekar Sir (Arth Infosoft Pvt. Ltd.) and Prof.
Heena Patel Internal Guide, for their tireless efforts and insightful comments throughout
the internship. Their dedication, genuineness, and enthusiasm for research have
profoundly influenced me. Working and studying under his supervision was a wonderful
honour and privilege. I really appreciate our HOD's assistance throughout the
internship. I also appreciate the assistance I received from my seniors.
211210116013
ii
ABSTRACT
A Project Tracker is an essential time management tool that helps organizations and
teams become more organized, efficient, and productive. The application enables real-
The primary objective is to ensure that projects are completed on or before the
deadline, while also identifying low productivity areas and assisting team members who
iii
LIST OF FIGURES
iv
LIST OF TABLES
v
LIST OF ABBREVIATIONS
vi
TABLE OF CONTENTS
Acknowledgement ii
Abstract iii
List of Figures iv
List of Tables v
List of Abbreviations vi
Table of Contents vii
Chapter 1 OVERVIEW OF THE COMPANY 1
1.1 History 1
1.2 Different Product 1
1.3 Organization Chart 2
1.4 Company Objective 2
Chapter 2 PROPOSED SYSTEM 3
2.1 Details of project Implementation Procedure 3
2.2 Technical Specifications Of Major Equipment Used In Each 3
Department
2.3 Schematic Layout Of Operation For Manufacturing Of End 4
Product
2.4 Details About Each Stage Of Production 5
Chapter 3 INTRODUCTION OF PROJECT 8
3.1 Project Summary 8
3.2 Purpose 8
3.3 Objective 8
3.4 Scope 8
3.5 Technology and Literature Review 8
3.6 Project Planning 9
3.6.1 Project Development Approach 9
3.6.2 Project / Internship Effort and Time, Cost Estimation 10
3.6.3 Roles and Responsibilities 11
3.7 Project Scheduling (Gantt Chart/PERT/Network Chart) 11
Chapter 4 SYSTEM ANALYSIS 12
4.1 Study of Current System 12
4.2 Problem and Weaknesses of Current System 12
4.3 Requirements of New System 12
4.4 System Feasibility 13
1. HISTORY
Grownited Pvt. Ltd. is an India-based IT company dedicated to delivering global software
solutions. With development centers in Ahmedabad and active operations in Gandhinagar
and Surat, the company has successfully executed various government projects. Our
mission is to understand our clients' business objectives and become a key component of
their organizational strategy. We focus on delivering fast, easy, and low-effort solutions
without compromising on quality. Through powerful SEO (Search Engine Optimization)
strategies, we help businesses extend their reach to a wider audience. Committed to
building long-term relationships, we offer 24x7 support as a core value of our business
approach.
2. DIFFERENT PRODUCT
•SQL Development & Training: Services and guidance in managing and developing
structured databases using SQL, tailored for both beginners and advanced users.
•C# Development & Training: Training and development support in C#, enabling clients
to build powerful applications using Microsoft's modern programming language.
•Python Development & Training: Expertise and instruction in Python for web
development, data science, automation, and general-purpose programming.
•Ruby on Rails Development & Training: Development and hands-on training in Ruby
on Rails, aimed at building scalable web applications efficiently.
CHAPTER 2
• Analysis
• Designing
• Implementation
• Testing
• Deployment
• Maintenance
With more than 10 years of practical experience we bring the experts in Following Web
Technologies as following: -
PSD to HTML/CSS/Any Conversation
Adobe Illustrator/Photoshop Designers
Python FAST API Development
React.js for frontend development
MongoDB database
Postman for testing
SEO Expert Services
Database Design, Programming, and Management
VS Code
Visual Studio Code combines the simplicity of a source code editor with powerful
developer tooling, like IntelliSense code completion and debugging.it have
frictionless edit-build-debug cycle.
GitHub
GitHub provide various features like Access Controls/Permissions, Application
Security, Authentication, Automated Testing, Collaboration Tools,
Commenting/Notes, Data Import/Export, Debugging, Feedback Management,
Integrated Development Environment, Milestone Tracking, Monitoring.
Planning
Planning for the quality assurance requirements and identification of the risks associated
with the project is also done in the planning stage. The outcome of the technical
feasibility study is to define the various technical approaches that can be followed to
implement the project successfully with minimum risks.
Requirement analysis
Requirement analysis is the most important and fundamental stage in SDLC. It is
performed by the senior members of the team with inputs from the customer, the sales
department, market surveys and domain experts in the industry. This information is then
used to plan the basic project approach and to conduct product feasibility study in the
economical, operational and technical areas.
Designing
In this third phase, the system and software design documents are prepared as per the
requirement specification document. This helps define overall system architecture.
This design phase serves as input for the next phase of the model.
Implementation / coding
Once the system design phase is over, the next phase is coding. In this phase, developers
start build the entire system by writing code using the chosen programming language. In
the coding phase, tasks are divided into units or modules and assigned to the various
developers. It is the longest phase of the Software Development Life Cycle process. In
this phase, Developer needs to follow certain predefined coding guidelines. They also
need to use programming tools like compiler, interpreters, debugger to generate and
Testing
Once the software is complete, and it is deployed in the testing environment. The testing
team starts testing the functionality of the entire system. This is done to verify that the
entire application works according to the customer requirement.
During this phase, QA and testing team may find some bugs/defects which they
communicate to developers. The development team fixes the bug and send back to QA
for a re-test. This process continues until the software is bug-free, stable, and working
according to the business needs of that system.
Deployment
Once the software testing phase is over and no bugs or errors left in the system then the
final deployment process starts. Based on the feedback given by the project manager,
the final software is released and checked for deployment issues if any.
Maintenance
Once the system is deployed, and customers start using the developed system, following
3 activities occur :
• Bug fixing – bugs are reported because of some scenarios which are not tested at
all
• Upgrade – Upgrading the application to the newer versions of the Software
• Enhancement – Adding some new features into the existing software
The main focus of this SDLC phase is to ensure that needs continue to be met and that
the system continues to perform as per the specification mentioned in the first phase.
CHAPTER 3
INTRODUCTION TO PROJECT
1. PROJECT SUMMARY
We are building HR Project Tracker, is an essential time management tool that
helps organization and teams to become more organized, efficient and
productive.
Admin: - Who can control the main system and having the decision-making Authority.
User: - who uses this portal to see deadline, status and Other Details .
2. PURPOSE
The main purpose is to provide smooth experience in project completion with more
efficiency, better resource allocation and time management.
3. OBJECTIVE
The primary objective of this app is to ensure that projects are completed on or
before the deadline, while also identifying low productivity areas and assisting team
members who need additional support. With detailed reports and analytical insights,
organizations can make informed decisions to optimize their workforce and
project execution.
4. SCOPE
Scope of any project means is it scalable or a contender for further building of that
particular project.
Project scope is the part of project planning that involves determining and documenting
a list of specific project goals, deliverables, tasks and deadlines.
Time tracking applications have become a vital part of modern project management,
enabling organizations to enhance productivity and streamline workflows.
• Allocation of resources.
• Database Designing.
• website Designing.
Login 100
Registration 200
Home 950
company 150
product 250
Report 450
Designation 200
Employee 200
logout 150
Profile 150
Admin 250
Review 250
User 500
3800
KLOC=3.8
=2.4 (KLOC)1.05 PM
=9.74 PM
Existing system
The present system in the different companies is working on the offline paper-based
system. This system becomes much more difficult to use when the number of
project and employee increases.
Thus, we created an online system control for official work.
Our system consists of web-based management system which includes many
functionalities and can be accessed at any time.
4. SYSTEM FEASIBILITY
Technical feasibility means does the model is technically possible to build or not?
i.e., does it really sound technical to build the model.
So, talking about our project, we assure you that it sounds really good to build this type
of project because the software industry needs to manage all data.
The Project Tracker system is to be developed for any user who wants to use it. We want
our system user friendly and easy to use.
The administrator also may be non-technical, so the user interface will be designed in
such a way that it gets comfortable for non-technical person to operate easily.
2. Can The System Be Integrated With Other Systems Which Are Already In
Place?
Currently, all firms are automating the repetitive and tedious tasks that individuals
perform. The primary process areas of the existing system are well suited to automation,
proving the technological capability without a shadow of a doubt. Python is being
used to create this project. It has a lot of features that make it user-friendly. The
login/signup process is also quite straightforward. Data may be easily added, modified,
and deleted from the database. Because it is an online project, it may be accessed from
any location and on any platform.
This module provides a centralized dashboard for creating, assigning, and tracking
project tasks. Users can define project timelines, set milestones, allocate resources,
and monitor progress in real time.
Task Logging
Handles account creation and access control. Admins can assign roles such as
Hardware Characteristics :
Processor : Intel i3 or up
RAM : 512 MB
Hard disk : 5 GB
Admin side
Step 1: enter the URL to open the system
Step 2: provide user name and password
Step 3: if username and password both is correct then it will login successfully.
Step 4: it shows home page
CHAPTER 6
Implementation Environment
• Our project is suitable to all type of users like single and multi-users.
• Multi users are allowed to operate the website at the same time.
• We provide the interface which is user friendly.
• We have GUI (graphical user interface) by which all type of users can easily
access the application
• If we don’t provide the GUI in the website then user won’t like our website.
• For better performance and reliability, we have to include GUI in the website
• So, for the more security and performance we have to use the GUI.
User authentication
Password Protection:
• Every user who is to be allowed to access the portal is given his own username
and password and given his own access rights so that only authorized and
authenticated users can access the project.
Confidentiality:
Scalability:
• We provide the scalable website to make sure that every user can access the
website in a proper order.
• User likes those type of website which are in one particular order that user
cannot wait for the usage of the services.
• Every company follows a different coding standard based on their best practices.
• Coding standard is required because there may be many developers working on
different modules so if they will start inventing their own standards then the
source will become very unmanageable and it will become difficult to maintain
that source code in the future.
• Here are several reasons why to use coding specifications:
• Your peer programmers have to understand the code you produce.
• A coding standard acts as the blueprint for all the team to decipher the code.
• Simplicity and clarity achieved by consistent coding save you from common
mistakes.
• If you revise your code after some time then it becomes easy to understand code.
• There are few guidelines that can be followed while coding in python-Django.
Python Tags : One must use the Python standard tags(), rather than the shorthand
tags() to delimit the Python-Django code.
Commenting :
Use of standard python commenting style i.e., (#) – for single line and (“””
“””) – for multi- line is highly encouraged.
Function Calls :
While writing a function call statement, there must be no space between the
function name and the opening parenthesis and use ‘_’ to separate if there is a two
words in function name.
Block alignment:
Every block of code and curly braces must be aligned.
Short Functions:
All functions and methods must limit themselves to a single page and must not be
lengthy.
6.4 IMPLEMENTATION
CHAPTER 7 TESTING
7.1 TESTING STRATEGY
• The testing strategy followed by the company is unique in its own way.
• The developer first takes into account the UNIT Testing.
• Then the Integration testing is conducted to check the over functionality of the
system.
• Then the Validation Testing is performed once the whole project is done. Alpha
and Beta testing are done once by the testing team and the clients respectively.
• Then the over System testing is done and after that Acceptance testing is done.
Unit Testing
• Black Box Testing - Whether the particular class meets the requirements
mentioned in the specification.
• White Box Testing - The tester looks inside that class and checks if there is error
in the code which is not found while testing the class as a black box.
Integration Testing
• User Interface Testing - Testing is done by moving through each and every menu
item in the interface either in top‐down manner or bottom‐up manner.
• Interaction Testing - When the system performs data processing, Interaction
between various.
Validation Testing
• For Validation Testing stage, we have performed functional test cases and the
result share compared in the form of actual and expected outcomes.
• The testing proved that the Validation was compliant with the requirements as
specified in the Use Case and SRS (Software Requirement Specification).
System Testing
• It is carried to see that functionality related sets of units used together function as
designed.
• The system test specifications, incorrect operation of the system is narrowed down
to incorrect operation of unit(s) and is taken care of by filing the units.
• Test data covers the possible values of each parameter based on the requirements.
Acceptance Testing
• After each module completion, the system tester tested the system to check user
acceptance and changes are made accordingly as per requirements.
1. CONCLUSION
2. FUTURE ENHANCEMENT
It is not possible to develop a system that satisfies all the requirements of the user at
once. As the system evolves and usage expands, New needs arise. some of the Future
enhancements that can be done to this system are:
Chapter 9 REFERENCES
• https://docs.python.org/3/tutorial/controlflow.html
• https://fastapi.tiangolo.com/
• https://www.w3schools.com/html/html_responsive.asp
• https://www.w3schools.com/js/js_output.asp
• https://www.mongodb.com/docs/
• https://app.diagrams.net/