Time Logger- BSc.CSIT Internship report

TRIBHUVAN UNIVERSITY
PRIME COLLEGE
Institute of Science and Technology
A Final Year Internship Report
On
"Time Logger"
At
“Ontreat Services Pvt. Ltd”
Under the Supervision of
Dikshya Singh
Submitted By:
Rashna Maharjan [S.N. 4906/071]
TU Regd. No. : 6-2-0038-0238-2013
Submitted To:
Department of Computer Science and Information Technology
Prime College
An intern report submitted in partial fulfillment of the requirements for the degree of Bachelor of Science
(B.Sc.) Computer Science and Information Technology awarded by IOST, Tribhuvan University.
FEBRUARY 2019

PRIME COLLEGE
INTERNSHIP PROPOSAL REPORT
ON
TIME LOGGER SYSTEM
AT
ONTREAT SERVICES PVT. LTD.
In partial fulfillment of the requirements for the Bachelor’s Degree in Computer Science
and Information Technology awarded by Tribhuvan University.
Submitted By:
Rashna Maharjan
[S.N. 4906/071]
TU Regd. No. : 6-2-0038-0238-2013
FEBRUARY 2019

Date: …………………….
SUPERVISOR’S RECOMMENDATION
It is my pleasure to recommend that a report on “Time Logger” has been prepared under
my supervision by Rashna Maharjan in partial fulfillment of the requirement of the degree
of Bachelor of Science in Computer Science and Information Technology (BSc.CSIT).
Their report is satisfactory to process for the future evaluation.
…………………………………
Mrs. Dikshya Singh
Internal Supervisor
Department of Computer Science & IT
Prime College

Date: ……………………...
CERTIFICATE OF APPROVAL
The undersigned certify that he has read and recommended to the Department of Computer
Science and Information Technology for acceptance of report entitled “Time Logger”
submitted by Rashna Maharjan in partial fulfillment for the degree of Bachelor of Science
in Computer Science and Information Technology (BSc.CSIT), Institute of Science and
Technology, Tribhuvan University.
----------------------------
Mrs. Dikshya Singh
Coordinator and Internal Supervisor
Department of Computer Science & IT
Prime College
------------------------
Mr. Dhirendra Yadav
External Examiner, TU

i
ACKNOWLEDGEMENT
The successful completion of this internship report would not have been possible without
the support and assistance of many individuals and organizations. I feel immensely blessed
to have gotten this during the course of my internship program. I would like to take this
opportunity to offer my earnest admiration to each and every one of them.
I am very thankful to Mrs. Dikshya Singh Gupta, B.Sc. CSIT coordinator of Prime College,
for providing regular feedbacks and suggestions to perform an internship project
assignment so that we can practically implement our studies in the real world.
First and foremost, I am highly indebted to Mr. Krishna Bahadur Kunwar who took
confidence in me and provided me with the opportunity to work as an Intern at Ontreat
Services Pvt. Ltd. I had a wonderful and an unforgettable experience being part of such a
lovely and lively team.
I express my sentiment of gratitude to Mr. Mizal Tandukar, an acclaimed Django
Developer, who has been a continuous source of inspiration as my intern mentor. Without
his constant guidance and suggestions, this report and the system TL would have been
nowhere near completion. My gratitude for his trust and generosity goes beyond words.
Finally, my thanks and appreciations go to each and every one of my colleagues, and the
entire Ontreat team, who irrespective of the situation, always encouraged and supported
me to prepare this report.
Sincerely,
Rashna Maharjan (4906/071)

ii
ABSTRACT
Significant number of employee has admitted that they are wasting nearly an hour of day
on their working days. Even the managers of the company cannot look after every single
employee in the organization what they have been working on each day. So, for a fair
accurate account of the employees’ work history there was necessity of the tool like time
logger which will not only keeps the track of employees’ work but also analyze the growth
graph of project or task that employees’ are performing. Also it helps to calculate the gross
time spent for the task or project for better productivity of the organization. TL will help
everyone who want to grow their productivity of work and achieve their goals in time. This
web application can be used from any devices like desktop, laptop or smart phones which
can access internet. The data abstraction is used to hide information of an employee from
other employees and clients who are not assigned to that project. Only admin is responsible
to manage all the users, projects and tasks. Clients can only view the assigned projects and
tasks associated with it while employees can view projects and add tasks associated with
it. This application is built on Django framework so it can be converted into mobile apps
if required.
Keywords: Django framework, data abstraction, mobile apps, web application

iii
LIST OF TABLES
Table 1: Company Products................................................................................................ 4
Table 2: Internship details................................................................................................... 5
Table 3: Comparing Existing System ............................................................................... 11
Table 4: Use Case Description.......................................................................................... 14
Table 5: Technical Feasibility........................................................................................... 16
Table 6: Schedule.............................................................................................................. 18
Table 7: Data Structure ..................................................................................................... 25
Table 8: List of Files......................................................................................................... 28
Table 9: Testing ................................................................................................................ 31
Table 10: Test case for login............................................................................................. 31
Table 11: Test Case for Project Addition ......................................................................... 33
Table 12: Test Case for Task Addition............................................................................. 33
Table 13: Test Case for Logout ........................................................................................ 34
Table 14: System Testing.................................................................................................. 36

iv
LIST OF FIGURES
Figure 1: Hierarchy of organization.................................................................................... 3
Figure 2: Use Case Diagram............................................................................................. 14
Figure 3: Gantt chart ......................................................................................................... 19
Figure 4: EER Diagram .................................................................................................... 20
Figure 5: Context Diagram ............................................................................................... 21
Figure 6: DFD Level 1...................................................................................................... 22
Figure 7: Architectural Design.......................................................................................... 23
Figure 8: Database Schema............................................................................................... 24
Figure 9: Class Diagram ................................................................................................... 26
Figure 10: Sequence diagram for employee ..................................................................... 27
Figure 11: Incremental Process Model ............................................................................. 30
Figure 12: Integration Testing .......................................................................................... 35
Figure 13: Front end view for everyone who visits.......................................................... 38
Figure 14: Back End View as admin ................................................................................ 39

v
LIST OF ABBREVIATIONS
API Application Programming Interface
CRM Customer Relationship Management
CRUD Create, Read, Update and Delete
CSS Cascading Style Sheet
DFD Dataflow Diagram
EER Extended Entity Relationship
HTML Hypertext Markup Language
IT Information Technology
MBps Megabytes per second
SDLC Software Development Life Cycle
SEO Search Engine Optimization
SQL Structured Query Language
TL Time Logger
URL Uniform Resource Locator
USD United States Dollar

vi
TABLE OF CONTENTS
ACKNOWLEDGEMENT................................................................................................... i
ABSTRACT........................................................................................................................ ii
LIST OF TABLES............................................................................................................. iii
LIST OF FIGURES ........................................................................................................... iv
LIST OF ABBREVIATIONS..............................................................................................v
CHAPTER 1: INTRODUCTION........................................................................................1
1.1 Introduction.......................................................................................................... 1
1.1.1 Introduction to Project........................................................................................ 1
1.1.2 Scope .................................................................................................................. 1
1.1.3 Limitations.......................................................................................................... 2
1.1.4 Brief Introduction to Organization ..................................................................... 2
1.1.5 Duration of Internship ........................................................................................ 5
1.2 Problem Statement .................................................................................................... 6
1.3 Objective ................................................................................................................... 6
1.4 Responsibilities Assigned ......................................................................................... 6
1.5 Motivation............................................................................................................ 7
1.6 Report Organization.................................................................................................. 8
CHAPTER 2: LITERATURE REVIEW.............................................................................9
2.1 Definition of Time Tracking ..................................................................................... 9
2.2 Study of Existing Reports ......................................................................................... 9
2.3 Study of Existing System........................................................................................ 10
2.3.1 Toggl................................................................................................................. 10
2.3.2 Time Doctor...................................................................................................... 10
CHAPTER 3: SYSTEM ANALYSIS................................................................................12

vii
3.1 Requirement Collection........................................................................................... 12
3.1.1 Study of Existing Reports:................................................................................ 12
3.1.2 Prototyping ....................................................................................................... 12
3.2 Functional Requirements......................................................................................... 13
3.3 Non Functional Requirements................................................................................. 15
3.4 Feasibility Analysis ............................................................................................. 15
3.4.1 Technical .......................................................................................................... 15
3.4.2 Operational ....................................................................................................... 17
3.4.3 Economical ....................................................................................................... 17
3.4.4 Schedule............................................................................................................ 18
3.4 Data Model of System............................................................................................. 20
3.5 Process Model of System........................................................................................ 21
3.5.1 Structured Approach - Context Diagram (DFD 0) ........................................... 21
3.5.2 Structured Approach- DFD 1 ........................................................................... 22
CHAPTER 4: SYSTEM DESIGN.....................................................................................23
4.1 Architectural Design ............................................................................................... 23
4.2 Database Design...................................................................................................... 24
4.2.1 Database Schema.............................................................................................. 24
4.2.2 Data Dictionary................................................................................................. 25
4.3 Class Diagram ......................................................................................................... 26
4.4 Sequence Diagram................................................................................................... 27
CHAPTER 5: IMPLEMENTATION ................................................................................28
5.1 Front End Tools....................................................................................................... 28
5.2 Back End Tools....................................................................................................... 28
5.3 List of Files.............................................................................................................. 28

viii
5.4 Development Methodology..................................................................................... 30
CHAPTER 6: TESTING....................................................................................................31
6.1 Unit Testing............................................................................................................. 31
6.2 Integration Testing .................................................................................................. 35
6.3 System Testing........................................................................................................ 36
CHAPTER 7: CONCLUSION ..........................................................................................37
7.1 Conclusion............................................................................................................... 37
7.2 Lesson Learnt.......................................................................................................... 37
APPENDICES ...................................................................................................................38
Appendix 1: Screenshots............................................................................................... 38
Appendix 2: Codes of the system.................................................................................. 40
REFERENCES ..................................................................................................................50
BIBLIOGRAPHY..............................................................................................................51

1
CHAPTER 1: INTRODUCTION
1.1 Introduction
1.1.1 Introduction to Project
Time logger system is a tool used by managers, employees and clients to record or
analyze worked hours for billing, payroll or operations. In general, they capture
time spent on assigned tasks and use payment gateway for customer subscription
for the system. They can also provide insights on your operations, such as, which
tasks are completed and which are ongoing, allowing users to plan project
accordingly. Also, people who want to get update and know more about the system
can subscribe to the project from its site.
Time logger system is a web application developed on Django framework. This
web application helps client to know how much time is spent on the specific task
or project.
There are many system or web applications paid or free which helps to track the
tasks and time of employee. Some of them are Toggl, Harvest, and Time Camp etc.
Toggl is popularly used by many companies and organizations for tracking their
employees’ time spent in every tasks as it is free convenient and very reliable. Toggl
also tracks our costs and earnings and get detailed project overviews. It helps us to
manage our large team and can share our project details with anyone.
Along with this, Time Doctor is another mobile, web and desktop application which
can also integrate with project management tools like Trello with the help of API.
Also, we can manage lots of configuration as the setting tools for the ease of use.
1.1.2 Scope
This project can be highly used on all kind of field where there is manager who
want to take care of their client’s work. Keeping employees on track not only helps
to know the time spent for every tasks or project but also, it helps to know the
employee who is hardworking and dedicated towards his/her works.

2
Admin or Clients can see the status of the task or project at a glance which will help
them to track the growth of their works and target and analysis the completion of
goal of their company or organization.
Time logger will help for the productive work in any kind of organizations as we
can actually take a glance of our work on process and report of completed works
which can help us to realize our mistakes and overcome them in next projects or
tasks.
1.1.3 Limitations
 Fear of being watched for the employees
 Technical Knowledge is required along with the simple English Language
knowledge.
 Employees’ dissatisfaction because they feel like being watched and only
physical work is calculated.
 Internet is essential to use the system, so device with at least 4MBps is required
for ease use of the system.
1.1.4 Brief Introduction to Organization
Ontreat once was restaurant booking platform for giving treats to friends and family
while living afar, pivoted to a Django Developer Agency. It still same group of
people who founded and developed Ontreat platform.
Today it provides Python/Django development services. A renowned web site
developing and optimization organization that uses Python/Django as a
programming platform to perform its tasks. Ontreat Services Pvt. Ltd was
established on 2013 A.D with aim to provide high quality software development
services focusing on web application and mobile development. Since
establishment, it has provided services to several clients across the globe. Every
single project of clients is accomplished in a way that nourishes its relationship with
them by taking the necessary time and effort to understand the core expectation of
the clients.

3
Organizational hierarchy
Hierarchy is a way to structure an organization using different levels of authority
and a vertical link, or chain of command, between superior and subordinate levels
of the organization. The highest level of authority is at the top of the, and orders
flow from this top level down to the next level where it continues to move on down
until it reaches the level where the order is supposed to be carried out.
Information and directions flow vertically in a hierarchical structure. Information
flows up through each level until it reaches the top. After all the information has
been received and assessed, a decision will be made at the top and will flow down
through the levels of the hierarchy until it reaches the level where the decision will
be implemented.
Figure 1: Hierarchy of organization

4
Organization product and services
Ontreat services Pvt. Ltd is responsible in the field of web hosting, web developing,
digital marketing and SEO of the websites in google ranking. These services are
available internationally for all the global clients. Some of its works are as follows:
Table 1: Company Products
Name Website URL
Clickmandu: https://clickmandu.com/
Food Petter https://www.petterfood.com/
International Sherpa Guides http://www.internationalsherpaguides.com/
BPJ Healthonline http://bpjhealthonline.com/
7 Summits Foundation http://www.7summitsfoundation.org/
Multi Adventure https://multiadventure.com/
Helambu Heritage https://helambuheritage.com/
Contact information
Company Website URL: http://ontreat.com/
Company Logo:
Location: Nayabazar, Kathamandu
CEO Name: Krishna Bahadur Sunuwar
Contact No.: 9851004639

5
1.1.5 Duration of Internship
Author has completed Internship program in partial fulfillment of the requirement
for the Bachelor of Science in Computer Science and Information Technology
(BSc.CSIT) 8th semester of Tribhuvan University, Nepal, on Django Framework
from Ontreat Services Pvt. Ltd. The students require at least six credit hours
(minimum if ten weeks or 180 hours long) internship for attaining a successful
completion of the degree.
As per requirement, the students have to do internship under sectors involving IT
for at least 3 months and involve in an ongoing project. The information on
duration, timing, supervisor, mentors, working days, start and end date, and
position is provided below:
Table 2: Internship details
Starting Date 5th
Nov 2018
Ending Date 3rd
Feb 2019
Total Duration 90 Days
Position Intern Trainee
Supervisor Mr. Krishna Bahadur Sunuwar
Mentor Mr. Mizal Tuladhar
Office Hour 10:00 am - 6:00 pm
Working Days 6 working days a week

6
1.2 Problem Statement
The conducted surveys revealed that 89 percent of people admit to wasting time at work
every single day. 31 percent of workers waste 30 minutes during their working day.
Another 31 percent waste roughly an hour per day. 16 percent waste about 2 hours, 6
percent waste roughly 3 hours, 2 percent 4hours, and the last 2 percent 5 or more hours
daily. (Pros and Cons of time tracking system, 2017)
So, for a fair accurate account of the employee’s work history there was necessity of the
tool like time logger which will not only keeps the track of employees’ work but also
analyze the growth graph of project or task that employees’ are performing. Also it helps
to calculate the gross time spent for the task or project for better productivity.
1.3 Objective
 To keep records of project and tasks assigned to number of employees
 To manage the task by assigning task to the employee by admin
 To keep track of time spent in each task by analyzing them by admin and client
 To analyze the work by line chart
1.4 Responsibilities Assigned
The responsibility assigned to author by the organization was the development of complete
website which will keep the track of the work of the employees namely “Time Logger”.
Author have to develop a complete website with both front and back end with Django
Framework of Python.
So as to meet that objective, this internship required the extensive preliminary studies about
the Python and Django Framework before actually analyzing the actual requirement of the
system. The study was required not only to understand the subject under study but also to
realize the solutions to the existing problems and implementing the findings from the study
was another bigger challenge.
Following responsibilities were assigned to the author:
 Practice and perform the industry level design, development and deployment of
products.

7
 Solve problems and build logic for the project
 Explore and create work experiences with respect to the field of interests.
 Practice with the hardware and software tools and application used in the company in
order to gain the better output.
 Learn to use the pre-built components or APIs for the fast output.
1.5 Motivation
The selection of organization is twofold. The first is the student’s area of interest and
second is the willingness of the host company to take the student as an intern. As a student
in search of a host company for internship program, students are required to prepare a
competent résumé and perform well in the ‘interview’ and/or ‘assessment’.
As author has interest in the domains of Python (Django Framework), the author wanted
to utilize internship program to explore and learn about this dynamic field. And, since
Python (Django Framework) was something that wasn’t part of the curriculum, the author
was in search of an IT company with a vibrant team and enviable workplace environment
looking for fresh talent and energy to join them.
Ontreat Services Pvt. Ltd is an IT company that can help to enhance the knowledge and
skills in the required field and could help to gain excellence of professional skills as they
are using the same framework under author’s interest for building the system. Further
exploring on interviews author came to know that they provide proper guidelines and
support throughout the internship duration.
Also, the location is very near from the place author has been living, it was an easy option
to be in this company. No need of any vehicle to be there on time also has been a plus point
for choosing this company for internship.
After exploring available options, author came to the conclusion that the opportunity to
intern at Ontreat Services Pvt. Ltd. under the guidance Mr. Krishna Bahadur Sunuwar
would be a perfect match for author’s ambition to learn experience and develop skills in
the domains of Python (Django Framework).

8
1.6 Report Organization
Chapter 1:
This chapter describes about the project, its scope, limitations, and organization along
with the selection of organization, internship and internship duration. It also covers the
responsibility assigned on the time of internship.
Chapter 2:
This chapter covers all the history or report paper published by different peoples on the
field of time tracking of employee.
Chapter 3:
This chapter include methods, requirement specification, feasibility analysis, and
structured of the system. Here all the necessary diagram are presented to describe data
model and process model of the system.
Chapter 4:
Data organization, system architecture and process are explained with the suitable
diagram as required.
Chapter 5:
Tools used for front end and back end for the system is described in this chapter along
with the selection of development methodology.
Chapter 6:
The testing plans, tested inputs and comparison between expected outcome and real
outcome is analyzed.
Chapter 7:
The whole system and its purpose is described in a summary.

9
CHAPTER 2: LITERATURE REVIEW
2.1 Definition of Time Tracking
Counting time spent by the people on work can be defined as time tracking in this system.
It has been one of the most popular ways to measure performance and, subsequently,
calculate payments. Already in the ancient Egypt, the Hammurabi’s code
established minimum wages for workers. Some of them were calculated per days, months
and years; some were paid per work done. The wages depended on professions and types
of work: a doctor’s wage was higher than a field worker’s. (AciTIme, Aug 2018)
Historically, time-tracking has been being used as the simplest way to measure work and
calculate payments. In today’s world, it is often used as a source of essential data on how
work is performed, what can be improved, and what trends of the work process require
closer attention. Advanced time tracker tools are used for collection and analysis of this
vital information.
2.2 Study of Existing Reports
On 2010 June 04, Shirish Prabhakar Deodhar, Swati Shirish Deodhar, Madhukar Sharan
Bhatia invented System And Method To Measure, Aggregate And Analyze Exact Effort
And Time Productivity in association with Sapience Analytics Private Ltd which track the
daily time spent by employees, irrespective of whether the time is spent on one or more
computing devices, or away from any computing system while in meetings, discussions,
calls, lab work, outside travel, and remote visits. (Shirish Prabhakar Deodhar, 2010) In
contrast to this TL keeps the records of the time spent on the particular task and use it for
further purpose.
Roland Heumesser associated with Hewlett Packard Development Co LP developed
Virtual desktops and project-time tracking in 31st
Oct 2003 which provide a plurality of
virtual desktops which are assignable to different projects and switchable by the user, and
to track the time spent by the user working on the different desktops, thereby tracking the
time spent on the projects to which the respective desktops are assigned. (Heumesser, 31
Oct 2003) Improvising this, TL can be operated by any device with the access of internet
and keep records of any tasks performed.

10
2.3 Study of Existing System
Some of the existing systems which are similar to proposed system are as follows:
2.3.1 Toggl
Toggl is the leading time tracking app for agencies, teams and small businesses. A simple
time tracker with powerful reports and cross-platform functionalities. It is a premium
application but the users can also use it for 30 days as a trial version of the application.
Toggl also tracks our costs and earnings and get detailed project overviews. It helps us to
manage our large team and can share our project details with anyone.
The service was initially developed for internal use and is targeted at small groups and
developers. It is designed for several different operating systems including iPhone,
Android, Windows, Mac and Linux Toggl employs more than 30 employees. Time entries
and active timers are synchronized in real-time via a cloud service to the website and
various applications. Reporting features allow users to track the time spent on various
projects and analyze productivity. (Toggle, 2018)
2.3.2 Time Doctor
This application can be used in any platform like mobile, desktop or web. Time Doctor
supports integration with other software or application with the help of API. Time Doctor
is a SaaS time tracking and productivity tool launched by the owners of Staff.com in 2012.
It has desktop software, mobile and web based components. A multi-functional time
tracking software with CRM and white label capabilities. (Time Doctor, 2018)
This application is available in Spanish, Russian, Portuguese and English language too.
Time Doctor offers screenshot software, website and application tracking, and time-based
reporting. It also provides idea for companies practicing remote employee monitoring and
managing virtual teams
Comparing some of the popular time tracking system with features and platform they can
be executed is shown in the table below:

11
Table 3: Comparing Existing System
S.N Software Main Features Launched Date Platform
1 Toggl Better organized tasks,
teams and projects.
2017 Mobile and
desktop
application
2 Harvest Invoice in multiple
currencies and helps in
budgeting of the project.
2006 Iphone
application
3 Time Camp Tips and Tricks available
for remote workers.
2009 Mobile and
desktop
application
4 Time Doctor Flexible Configuration and
supports integrations and
APIs.
2012 Mobile, web and
desktop
application
5 Red Mine Multilanguage support and
custom fields for issues and
discussion
2006 Web application

12
CHAPTER 3: SYSTEM ANALYSIS
3.1 Requirement Collection
3.1.1 Study of Existing Reports:
The worldwide survey was conducted among the business people for the
satisfaction of the work of their employee. Or in another words, do their employee
gives at least more than 80% of their working hours actually working.
The conducted surveys revealed that 89 percent of people admit to wasting time
at work every single day. 31 percent of workers waste 30 minutes during their
working day. Another 31 percent waste roughly an hour per day. 16 percent waste
about 2 hours, 6 percent waste roughly 3 hours, 2 percent 4hours, and the last 2
percent 5 or more hours daily. (Pros and Cons of time tracking system, 2017)
This concluded in need of the time or task tracking software within the organization
for productive work and growth.
Moreover, this survey was supported by data from salary.com in 2014, who
gathered the response of 750 employees. Which results that 31% waste roughly 30
minutes daily, 31% waste roughly 1 hour daily, 16% waste roughly 2 hours daily,
6% waste roughly 3 hours daily , 2% waste roughly 4 hours daily, 2% waste 5 or
more hours daily. Which means, according to Salary.com contributor Aaron
Gouveia that 4% of people surveyed waste at least half the average workday on
non-work-related tasks. Half. (Conner, Jul 31, 2015)
3.1.2 Prototyping
The team of 5 members (including author, supervisor, and mentors) held the
meeting on 2018 November 7 to discuss the static prototype of the system. Modules
needed for TL were listed out and the database structure was written on the paper.
Also, login and signup authentication was mentioned to keep in the system.

13
3.2 Functional Requirements
 User Dashboard:
The system shall authenticate the user and then display panel based on the particular
identified user. All the tasks and projects associated with the user (clients and
employees) are listed in this platform for the general view. Whereas, admin can view
any project, tasks and users of the system.
 Add project:
Project can only be added by the admin.
 Add Task:
Tasks can be added by any employee assigned in respective project and the admin while
clients can view which tasks are going on and completed.
 Assign Project and Task:
Admin assigns projects to client and employee but tasks are assigned to employee only.
If employee creates the task then s/he is automatically assigned to that respective task.
 Update Task:
Task credentials can be updated if required by the employee and admin.
 View Project:
Authorized and assigned users and admin can view the projects.
 Administrator Dashboard
Admin can control whole system. Admin can add, edit, update, and delete user, tasks,
and projects. Admin can set privileges and access permission to services of system to
users.

14
Figure 2: Use Case Diagram
Table 4: Use Case Description
Name Description
User Admin, Employee and Client
Add Project Admin can only add project
Add Task Admin and Employee can add task
Assign Project
Admin can assign project to employee
and client
Update Task Employee can update task if required
View Project All authorized and assigned users can
only with the project.

15
3.3 Non Functional Requirements
 Usability:
This system is very easy to use as it has simple navigation menu-bar on its left to
navigate on any page the user likes.
 Reliability:
Each data record is stored on a well-built efficient database schema. There is no risk
of data loss. The internal evaluation of data is well coded. User authentication is used
to provide privileges to the user.
 Supportability:
Maintenance is easy. It is supported by any web browser in any OS like windows,
Linux, MacOs etc. for use.
 Performance:
In order to ease the accessibility, tasks can be created and assign a creator
automatically.
 Availability:
System can be used 24/7 no time constraint. The system shall have 85% availability
to the users.
 Security
All users of the system shall login using some form of unique identification (e.g.,
username and password. All login attempts shall be done so in a secure manner (e.g.,
encrypted passwords). Each user shall either be trusted or not be trusted.
3.4 Feasibility Analysis
3.4.1 Technical
Technical feasibility tests for the whether the proposed system can be developed
using existing technology or not. The proposed system is developed using Django
Framework of Python. The application can be browsed from any devices having
any kind of internet browser and internet access. A webserver supporting Django
version 1.11 and SQLite 3 can serve multiple number of devices at a time is enough
for the main server. It is evident 12 that the necessary hardware and software are

16
available for the development and implementation of the proposed system. Hence
the solution is technically feasible.
Table 5: Technical Feasibility
Hardware Specification Software Specification
1. 1 GB Ram
2. Processor 1.2
1. Python 3.6.*
2. SQlite 3
3. Nginx or Apache
4. astroid==2.1.0
5. certifi==2018.11.29
6. chardet==3.0.4
7. Click==7.0
8. colorama==0.4.1
9. Django==1.11.17
10. django-appconf==1.0.2
11. django-bootstrap3==11.0.0
12. django-newsletter==0.7
13. django-paypal==0.2.5
14. django-user-accounts==2.1.0
15. Flask==1.0.2
16. idna==2.8
17. isort==4.3.4
18. itsdangerous==1.1.0
19. Jinja2==2.10
20. lazy-object-proxy==1.3.1
21. ldif3==3.1.1
22. MarkupSafe==1.1.0
23. mccabe==0.6.1
24. paypal==1.2.5
25. Pillow==5.4.1
26. pylint==2.2.2

17
27. python-card-me==0.9.3
28. python-dateutil==2.7.5
29. pytz==2018.7
30. requests==2.21.0
31. six==1.12.0
32. sorl-thumbnail==12.5.0
33. South==1.0.2
34. surlex==0.2.0
35. unicodecsv==0.14.1
36. urllib3==1.24.1
37. Werkzeug==0.14.1
38. wrapt==1.10.11
3.4.2 Operational
This test of feasibility checks if the system works with least difficulties when it is
developed and installed. It can take some time to learn and use every aspect of this
application if the user is not comfortable with smart devices. Users only have to
know how to browse the application and signup or login to use the web application.
Hence it can be concluded that the system is operationally feasible.
3.4.3 Economical
Time Logger is a web application, so it only needs the access of internet and
internet accessing device for the use of this application by the end user. By this
process they can only view the projects if they are assigned.
To have the full access or to track employee work on some projects then they have
to pay some amount per projects. Considering it takes 3 months to develop and
deliver fully functioning system with average 5 person team, it might take around
3*50 thousand = 150 thousand rupees spent on labor cost. Other miscellaneous
charges like maintenance cost can add up to 50 thousand. So, the total cost is 200
thousand rupees (i.e. 2000 USD)

18
Even if the system is sold for about 20 thousand with a year support for a client, the
investment can be recovered for making a deal with 15+ clients. This will involve
the action of installing the system in separate subdomain of the company so that
data privacy can be maintained. Also, the users can buy the system for only one
project which will cost for 10 USD online which can help the small company who
wants to take advantage of this system. This activity make them work for employee
only without any administration authority.
On client side also, it is very reasonable price for the startups or big company to
analyze their work per project. Hence, this application is also feasible
economically.
3.4.4 Schedule
Activities were list out as to do list and duration, start and end time were assigned
according to the dependencies. The sequence and time was assigned as to complete
it on my internship period. The table below shows the sequential breakdown of
individual tasks with start and end date with the number of days.
Table 6: Schedule
S.N Activities Start Date Duration End Date
1 Requirement
Collection
2018/11/05 15 Days 2018/11/20
2 Planning 2018/11/20 10 Days 2018/11/30
3 Designing 2018/11/30 10 Days 2018/12/10
4 Front End developing 2018/12/10 15 Days 2018/12/25
5 Back End Developing 2018/12/25 20 Days 2019/01/14
6 White box Testing 2019/01/14 10 Days 2019/01/24
7 Deployment 2019/01/24 2 Days 2019/01/27

19
8 Black box Testing 2019/01/27 8 Days 2019/02/03
9 Documentation 2018/11/05 90 Days 2019/02/03
The Gantt chart below shows the task and task dependencies along with duration.
Figure 3: Gantt chart

20
3.4 Data Model of System
Figure 4: EER Diagram
The EER diagram of the system is shown in figure above. There are 3 major entities in the
system. They are user, project and tasks. User has many attributes like userid, username
and designation. User can be admin, client or employee. Employee is responsible to work
on project by adding tasks modifying it. Client analyze the work perform by employees
and admin manages all the projects, tasks and users. Project can have many tasks so it is
one to many relationship between project and tasks. Tasks has four attributes in general
which are task_id, taskname, starttime and endtime. Futher, user_id and project_id are the
foreign key associated with the task.

21
3.5 Process Model of System
3.5.1 Structured Approach - Context Diagram (DFD 0)
Figure 5: Context Diagram
The figure shown above is the context diagram for the system. Employee works on the
project assigned by the admin and clients views and analyze the time spent by employee in
number of tasks. Three types of users work differently on the system for the output
required.

22
3.5.2 Structured Approach- DFD 1
Figure 6: DFD Level 1
The above diagram is for DFD level 1 where we can track work time through the processes
it is involving. The process time logger is further divided as project and tasks management
and login account management. The employee creates and modifies tasks. Admin is
responsible for managing all the aspects of the system. The login account checks the
authentication of the user records. All the processes use same database to work. All three
types of user have to login in the system to view, create and modify projects and tasks.
Admin, Employee and Client send the login request to the user account table for
authentication and authorization. Data abstraction is used for client and employee to hide
the projects, tasks and user of unassociated projects.

23
CHAPTER 4: SYSTEM DESIGN
4.1 Architectural Design
Figure 7: Architectural Design
The main components involve in the system are internet, webserver, database and users.
More than one can use the system at once by the use of internet which is linked with the
database that contain all the necessary data of the system provided by the users and admin.
The admin responsible for managing system and providing privilege to the users and
assigning them projects and tasks.

24
4.2 Database Design
4.2.1 Database Schema
Figure 8: Database Schema
There are three tables in our application database which are user, task and project. In above
diagram the tables covers their respective primary key, foreign key and their fields. All the
primary key or id of the tables are generated by the system to be unique and non-redundant.
User has its primary key user_id in int value and other attribute fields username, firstname,
lastname, email, password and status. Project has its primary key project_id and foreign
key user_id and an attribute projectname. Task has its primary key task_id, two foreign
key project_id and user_id and other attribute fields taskname, starttime, endtime, diff and
status.

25
4.2.2 Data Dictionary
A data dictionary also known as metadata repository is a centralized repository of
information about data such as meaning, relationship to other data, origin, usage and
format.
Table 7: Data Structure
S.N Entity Attribute Data type Constraints
1 User user_id Int Primary
username varchar(100)
firstname varchar(100)
lastname varchar(100)
password varchar(100)
roles Options – active,
staff and superuser
2 Project project_id Int Primary
projectname varchar(100)
Client Int Foreign
employee Int Foreign
3 Task task_id Int Primary
employee Int Foreign
Diff Varchar(100)
starttime DateTime(timezone)
endtime DateTime(timezone)
status Options – completed
and ongoing

26
4.3 Class Diagram
Figure 9: Class Diagram
There are three main model in the system – user, project and tasks. User has three data
members’ username, email, firstname, lastname, roles and password and three methods
AccontSignUp, AccountLogin, AccountLogout. Project has only one data member that is
project name. Tasks has four data members’ taskname, starttime, endtime, diff and status
and two methods TaskCreate, TaskModify and TaskDelete.

27
4.4 Sequence Diagram
Figure 10: Sequence diagram for employee
Employee lands on the login page of the system and authenticate self by providing valid
username and password. Then employee views the dashboard page where s/he can view
the projects and task. Also, if the user is employee or admin then they can add the tasks on
the respective projects they are working on. Data abstraction is used to hide the project
which are not associated to them so that the work of any employee can’t be viewed by other
employees.

28
CHAPTER 5: IMPLEMENTATION
5.1 Front End Tools
 HTML, CSS, Bootstrap, JS, JQuery:
These are the front end web developing tools for responsive website which can be
browse from any size of device with proper alignment and user friendly behavior
in the system while working.
HTML: used to build all the front accessible pages for the users.
CSS: On every page of the system CSS is used to beautify the HTML or displaying
components on screen. Also, to include font awesome icons, and other fonts used
in the project CSS plays a vital role.
Bootstrap CSS: For responsive view of the system on any size of devices.
JS/ Bootstrap JS: Used for validation of user login, signup, project form and task
form. Also, it is used for image carousel to display number of images in one place.
5.2 Back End Tools
 Back End: Python (Django Framework), SQLite 3
Django is a python web framework for using python code to develop a dynamic
websites by collecting data from database and show them on the web browser with
the help of template view. This project is using SQLite 3 for the database.
Django is used in TL to manage all CRUD operation for projects, tasks and users.
SQLite is used to record all the data provided by any type of the users.
5.3 List of Files
Table 8: List of Files
Tools Files
HTML 1. base.html
2. index.html
3. detail.html

29
4. form.html
5. task.html
6. updatetask.html
7. task_confirm_delete.html
8. account/base.html
9. account/signup.html
10. account/login.html
11. account/logout.html
12. payment/cancel.html
13. payment/done.html
14. payment/process.html
15. newsletter/subscription_subscribe.html
16. newsletter/subscription_update.html
CSS 1. bootstrap.min.css
2. custom.css
3. font-awesome.min.css
JS 1. bootstrap.js
2. custom.js
PYTHON 1. logger/__init__.py
2. logger/settings.py
3. logger/urls.py
4. logger/wsgi.py
5. project/__init__.py
6. project/admin.py
7. project/apps.py
8. project/forms.py
9. project/hooks.py
10. project/mail.py
11. project/models.py
12. project/tests.py
13. project/urls.py

30
14. project/views.py
15. payment/__init__.py
16. payment /admin.py
17. payment /models.py
18. payment /tests.py
19. payment /urls.py
20. payment /views.py
5.4 Development Methodology
Process Model Used
Incremental Software Development Process is used for the development of the system.
This SDLC model is the iterative approach, where certain layers of activity arranged in
linear order are repeated until all the requirements are fulfilled and the output is gained as
required.
TL is the client based project so all the requirements were not clear in the beginning of the
project. The requirements were being added as the project was going on. Thus, all the
requirements were added one by one as they were emerging with all the required activity
like design, code, test, and integrate. Although the schedule was planned previously as their
dependencies, the requirements were solved sequentially by the time they have risen in
front of the developers. Hence, the incremental model was the best SDLC for this project.
Figure 11: Incremental Process Model

31
CHAPTER 6: TESTING
Testing is the process of evaluation a software item to detect differences between given
input and expected output. Testing is a process that should be done during the development
process.
Table 9: Testing
Tester Roles Test Case ID Description
Client TC-LG-01 Login
TC-PRJ-03 Add Project
TC-AT-04 Add Task
TC-LGO-01 Logout
Admin TC-PRJ-01 Add Project
TC-AT-01 Add Task
Employee TC-PRJ-02 Add Project
TC-AT-03 Add Task
6.1 Unit Testing
The Unit testing part of a testing methodology is the testing of individual software modules
or components that make up an application or system.
Table 10: Test case for login
SN Test
Case Id
Test
description
Input test
data
Expected
Result
Actual
Result
Remarks
1 TC-LG-
01
Enter valid
data in
username
and
password
field
rashna
*********
Show home
page for user
Rashna
Displayed
dashboard
page for
user
Rashna
pass

32
2 TC-LG-
02
Enter valid
data in
username
and leave
password
field empty
and click
Login
rasna Show error Didn’t
show any
error and
navigate
nowhere
fail
3 TC-LG-
03
Leave
username
empty and
press log in
*********
Show error Printed
“Please fill
out this
field”
Pass
4 TC-LG-
04
Enter invalid
username
and
password
rashana
******
Show error Printed
“Please
enter the
correct
username
and
password
Note that
both fields
may be
case-
sensitive.”
Pass

33
Table 11: Test Case for Project Addition
SN Test
Case Id
Test
description
Input test
data
Expected
Result
Actual
Result
Remarks
1 TC-
PRJ-01
Add project
if user role is
admin
url
redirection to
add project
Show
project form
and add
project to
database
Displayed
Project
form and
allow to
add project
pass
2 TC-
PRJ-02
Add project
if user role is
employee
url
redirection to
add project
Show
assigned
project
Displayed
all
assigned
project list
pass
3 TC-
PRJ-03
Add project
if user role is
client
url
redirection to
add project
Show
assigned
project
Displayed
all
assigned
project list
Pass
Table 12: Test Case for Task Addition
SN Test
Case Id
Test
description
Input test
data
Expected
Result
Actual
Result
Remarks
1 TC-AT-
01
Add task if
user role is
admin
url
redirection to
add task
Show task
form and add
task to
database
Displayed
task form
and allow
to add task
Pass
2 TC-AT-
02
Add task if
user role is
employee
url
redirection to
add task
Show task
form and add
task to
database
Displayed
“Only
staffs are
allowed to
add work
timings.”
Fail

34
3 TC-AT-
03
Add task if
user role is
employee
url
redirection to
add task
Show task
form and add
task to
database
Displayed
task form
and allow
to add task
Pass
4 TC-AT-
04
Add task if
user role is
client
url
redirection to
add task
Don’t show
task form
Displayed
“Only
staffs are
allowed to
add work
timings.”
Pass
Table 13: Test Case for Logout
SN Test
Case Id
Test
description
Input test
data
Expected
Result
Actual
Result
Remarks
1 TC-
LGO-
01
Logout from
the
dashboard
Click logout
and click
confirm
button
URL
redirection
to logout
confirmation
Redirection
to logout
confirmation
pass

35
6.2 Integration Testing
The Integration testing part of a testing methodology is the testing of the different
modules/components that have been successfully unit tested when integrated together to
perform specific tasks and activities. The test is often done on both the interfaces between
the components and the larger structure being constructed, if its quality property cannot be
assessed from its components. After integrating the requirements then tested it, it was fine
and satisfactory.
Figure 12: Integration Testing

36
6.3 System Testing
The system testing part of a testing methodology involves testing the entire system for
errors and bugs. This test is carried out by interfacing the hardware and software
components of the entire system, and then testing it as a whole.
Table 14: System Testing
SN Test
Case Id
Test
description
Input test data Expected
Result
Actual
Result
Remarks
1 TC-LG-
01
Enter valid
data in
username and
password
field
rashna
*********
Show home
page for user
Rashna
Displayed
dashboard
page for user
Rashna
pass
2 TC-PRJ Add project
by the admin
Go to project
page and input
project name
with the client
and employee
to be assigned
Add Project
with
respective
client and
employee
assigned
Project
Added and
show up on
the list
Pass
3 TC-AT-
01
Add task by
the employee
Add all the
credentials
needed
Update
database with
the tasks with
respective
project
Showed
added task
under
respective
project
Pass
4 TC-
LGO-01
Logout from
the dashboard
Click logout
and click
confirm button
URL
redirection to
logout
confirmation
and then to
base page
Redirection
to logout
confirmation
and then to
base page
pass

37
CHAPTER 7: CONCLUSION
7.1 Conclusion
In conclusion, time logger is the solution for tracking working sequence and work time
logs of employees of the certain organization. It helps for better productivity of the
organization or company in terms of time consumed by employees to finish their tasks or
number of tasks they have performed to analyze the work of staffs.
This software or application can be also used to analyze the target rate of the goals by the
work rate and number of tasks done under deadline. Also, best employee of the
organization will be chosen wisely depending upon their work rather than using nepotism.
7.2 Lesson Learnt
This report is an attempt to express the activities that went through during of almost 90
days of internship program as an on the job training. Getting involved in real and practical
environment, coping up with the arising problems and finding the appropriate solutions
was a valuable experience. This internship has helped me to gain the knowledge of the
practical environment of the organization.
 It has helped me to deal with the real world problem which is different from the
theoretical knowledge.
 Far from the main objective of building a system application, working in the
organization has given me better knowledge about collecting the user requirement
and its analysis. This has helped me to increase my communication skills with the
people.
 The exposure to the practical environment has increased experience and confidence
to deal with various organizational communications with customer.
 To work in a group and keep out the frustration and pressure no matter how the
situation is and learnt to solve them.

38
APPENDICES
Appendix 1: Screenshots
Figure 13: Front end view for everyone who visits

39
Figure 14: Back End View as admin

40
Appendix 2: Codes of the system
settings.py
"""
Django settings for logger project.
Generated by 'django-admin startproject' using Django 1.11.17.
For more information on this file, see
https://docs.djangoproject.com/en/1.11/topics/settings/
For the full list of settings and their values, see
https://docs.djangoproject.com/en/1.11/ref/settings/
"""
import os
# Build paths inside the project like this: os.path.join(BASE_DIR, ...)
BASE_DIR = os.path.dirname(os.path.dirname(os.path.abspath(__file__)))
# Quick-start development settings - unsuitable for production
# See https://docs.djangoproject.com/en/1.11/howto/deployment/checklist/
# SECURITY WARNING: keep the secret key used in production secret!
SECRET_KEY = '8jea^dt7f1n@h$zbknvu0cxx80imgdiq3j3c7u((f6$ax+6wr3'
# SECURITY WARNING: don't run with debug turned on in production!
DEBUG = True
ALLOWED_HOSTS = []

41
# Application definition
INSTALLED_APPS = [
'django.contrib.admin',
'django.contrib.auth',
'django.contrib.contenttypes',
'django.contrib.sessions',
'django.contrib.messages',
'django.contrib.staticfiles',
'project',
'account',
'django.contrib.sites',
'bootstrap3',
'paypal.standard.ipn',
'payment',
]
MIDDLEWARE = [
'django.middleware.security.SecurityMiddleware',
'django.contrib.sessions.middleware.SessionMiddleware',
'django.middleware.common.CommonMiddleware',
'django.middleware.csrf.CsrfViewMiddleware',
'django.contrib.auth.middleware.AuthenticationMiddleware',
'django.contrib.messages.middleware.MessageMiddleware',
'django.middleware.clickjacking.XFrameOptionsMiddleware',
'account.middleware.LocaleMiddleware',
'account.middleware.TimezoneMiddleware',
'account.middleware.ExpiredPasswordMiddleware',
]

42
AUTHENTICATION_BACKENDS = [
'account.auth_backends.EmailAuthenticationBackend',
'django.contrib.auth.backends.ModelBackend',
]
TEST_RUNNER = "lib.tests.MyTestDiscoverRunner"
ROOT_URLCONF = 'logger.urls'
TEMPLATES = [
{
'BACKEND': 'django.template.backends.django.DjangoTemplates',
'DIRS': [],
'APP_DIRS': True,
'OPTIONS': {
'context_processors': [
'django.template.context_processors.debug',
'django.template.context_processors.request',
'django.contrib.auth.context_processors.auth',
'django.contrib.messages.context_processors.messages',
'account.context_processors.account',
],
},
},
]
WSGI_APPLICATION = 'logger.wsgi.application'
# Database
# https://docs.djangoproject.com/en/1.11/ref/settings/#databases
DATABASES = {

43
'default': {
'ENGINE': 'django.db.backends.sqlite3',
'NAME': os.path.join(BASE_DIR, 'db.sqlite3'),
}
}
# Password validation
# https://docs.djangoproject.com/en/1.11/ref/settings/#auth-password-validators
AUTH_PASSWORD_VALIDATORS = [
{
'NAME':
'django.contrib.auth.password_validation.UserAttributeSimilarityValidator',
},
{
'NAME': 'django.contrib.auth.password_validation.MinimumLengthValidator',
},
{
'NAME': 'django.contrib.auth.password_validation.CommonPasswordValidator',
},
{
'NAME': 'django.contrib.auth.password_validation.NumericPasswordValidator',
},
]
# Internationalization
# https://docs.djangoproject.com/en/1.11/topics/i18n/
LANGUAGE_CODE = 'en-us'
TIME_ZONE = 'UTC'

44
USE_I18N = True
USE_L10N = True
USE_TZ = True
# Static files (CSS, JavaScript, Images)
# https://docs.djangoproject.com/en/1.11/howto/static-files/
STATIC_URL = '/static/'
ACCOUNT_EMAIL_UNIQUE = True
ACCOUNT_PASSWORD_USE_HISTORY = True
ACCOUNT_OPEN_SIGNUP = True
ACCOUNT_LOGIN_URL = 'account_login'
ACCOUNT_LOGIN_REDIRECT_URL = "/"
ACCOUNT_LOGOUT_REDIRECT_URL = "/"
ACCOUNT_PASSWORD_CHANGE_REDIRECT_URL ="account_password"
ACCOUNT_PASSWORD_RESET_REDIRECT_URL = "account_login"
ACCOUNT_PASSWORD_EXPIRY = 0
ACCOUNT_PASSWORD_ME_EXPIRY = 60*60*24*5 # seconds until pw expires, this
example shows five days
ACCOUNT_USER_DISPLAY = lambda user: user.username
ACCOUNT_USER_DISPLAY_EMAIL = lambda user: user.email
ACCOUNT_CREATE_ON_SAVE = True
ACCOUNT_EMAIL_UNIQUE = True
ACCOUNT_EMAIL_CONFIRMATION_REQUIRED = False
ACCOUNT_EMAIL_CONFIRMATION_EMAIL = True
ACCOUNT_EMAIL_CONFIRMATION_EXPIRE_DAYS = 3
SITE_ID = 3
PAYPAL_RECEIVER_EMAIL = 'info@rasna.com.np'
PAYPAL_TEST = True

45
project/views.py
from django.core.urlresolvers import reverse
from django.shortcuts import render
from paypal.standard.forms import PayPalPaymentsForm
from django.views.decorators.csrf import csrf_exempt
@csrf_exempt
def payment_done(request):
return render (request, 'payment/done.html')
@csrf_exempt
def payment_cancel(request):
return render (request, 'payment/cancel.html')
def payment_process(request):
# What you want the button to do.
paypal_dict = {
"business": "receiver_email@example.com",
"amount": "10000000.00",
"item_name": "name of the item",
"invoice": "unique-invoice-id",
"notify_url": request.build_absolute_uri(reverse('paypal-ipn')),
"return": request.build_absolute_uri(reverse('done')),
"cancel_return": request.build_absolute_uri(reverse('cancel')),
"custom": "premium_plan", # Custom command to correlate to some function later
(optional)
}
# Create the instance.

46
form = PayPalPaymentsForm(initial=paypal_dict)
context = {"form": form}
return render(request, 'payment/process.html', context)
project/forms.py
from django.forms import ModelForm
from .models import Project, Task
from django import forms
import account.forms
class SignupForm(account.forms.SignupForm):
def __init__(self, *args, **kwargs):
super(SignupForm, self).__init__(*args, **kwargs)
del self.fields["username"]
class ProjectForm(ModelForm):
class Meta:
model = Project
fields = ['projectname', 'client']
class TaskForm(ModelForm):

47
employee = forms.IntegerField(widget=forms.HiddenInput(), initial=123)
class Meta:
model = Task
fields = ['taskname','starttime', 'endtime', 'diff', 'project']
project/models.py
from django.db import models
from django.conf import settings
from django.utils import timezone
# Create your models here.
class Project(models.Model):
projectname = models.CharField(max_length = 100)
client = models.ForeignKey(settings.AUTH_USER_MODEL,
related_name='client_name')
#provider = models.OneToOneField(Provider,
related_name='user_ind_provider_profile')
employee = models.ManyToManyField(settings.AUTH_USER_MODEL)
#employee = models.ForeignKey(settings.AUTH_USER_MODEL,
on_delete=models.CASCADE)
def __str__(self):

48
return str(self.projectname)
class Task(models.Model):
taskname = models.CharField(max_length = 100)
project = models.ForeignKey(Project, on_delete=models.CASCADE)
employee = models.ForeignKey(settings.AUTH_USER_MODEL,
related_name='tasks')
starttime = models.DateTimeField(default=timezone.now)
endtime = models.DateTimeField(blank=True, null=True)
diff = models.CharField(max_length = 100)
def __str__(self):
return str(self.taskname)
project/urls.py
from django.conf.urls import url, include
from . import views
from .views import ProjectCreate, ProjectDetail, TaskCreate, BaseView, TaskDelete,
TaskModify
#from .views import CreateView
#from .models import Project
urlpatterns = [

49
url(r'^$', BaseView.as_view(), name="index"),
url(r'^project/add/$', ProjectCreate.as_view(), name='create'),
url(r'^project/(?P<pk>d+)/$', ProjectDetail.as_view(), name='project_detail'),
url(r'^task/add/$', TaskCreate.as_view(), name='taskcreate'),
url(r'^task/update/(?P<pk>w+)/$', TaskModify.as_view(), name='taskmodify'),
url(r'^task/delete/(?P<pk>w+)/$', TaskDelete.as_view(), name='taskdelete'),
url(r'^paypal/', include('paypal.standard.ipn.urls')),
url(r'^payment/', include('payment.urls')),
#url(r'^contact/', Mail.as_view(), name='contact')
#url(r"^account/signup/$", SignupView.as_view(), name="account_signup"),
#url(r"^account/", include("account.urls")),
]

50
REFERENCES
Conner, C. (Jul 31, 2015). Wasting Time At Work: The Epidemic Continues. Forbes.
Heumesser, R. (31 Oct 2003). Virtual desktops and project-time tracking. Hewlett Packard
Development Co LP.
Pros and Cons of time tracking system. (2017). Retrieved from timecamp.com: https://
www.timecamp.com/ blog/2017/06/the-pros-and-cons-of-time-tracking/
Shirish Prabhakar Deodhar, S. S. (2010). System And Method To Measure, Aggregate And
Analyze Exact Effort And Time Productivity. Sapience Analytics Private Ltd.
The complete guide to Time Tracking. (2018, Aug). Retrieved from actitime.com:
https://www.actitime.com/time-tracking/time-tracking-software-essay
Time Doctor. (2018). Retrieved from en.wikipedia.org: https://en.wikipedia.org/wiki/
Time_Doctor
Toggle. (2018). Retrieved from en.wikipedia.org: https://en.wikipedia.org/wiki/Toggl

51
BIBLIOGRAPHY
AciTIme. (Aug 2018). The Complete Guide . AciTIme.
Conner, C. (Jul 31, 2015). Wasting Time At Work: The Epidemic Continues. Forbes.
Dar, I. J. (Apr 24, 2012). employee-time-and-task-tracking-system. Slideshare.
gary, S. (Feb10, 2017). Advantages and Disadvantages of Employee Time Tracking Software.
Recruiting Blogs.
Heumesser, R. (31 Oct 2003). Virtual desktops and project-time tracking. Hewlett Packard
Development Co LP.
Pros and Cons of time tracking system. (2017). Retrieved from timecamp.com: https://
www.timecamp.com/ blog/2017/06/the-pros-and-cons-of-time-tracking/
Shirish Prabhakar Deodhar, S. S. (2010). System And Method To Measure, Aggregate And
Analyze Exact Effort And Time Productivity. Sapience Analytics Private Ltd.
The complete guide to Time Tracking. (2018, Aug). Retrieved from actitime.com:
https://www.actitime.com/time-tracking/time-tracking-software-essay
Time Doctor. (2018). Retrieved from en.wikipedia.org: https://en.wikipedia.org/wiki/
Time_Doctor
Toggle. (2018). Retrieved from en.wikipedia.org: https://en.wikipedia.org/wiki/Toggl

Time Logger- BSc.CSIT Internship report

More Related Content

What's hot (20)

Similar to Time Logger- BSc.CSIT Internship report (20)

More from Rashna Maharjan (20)

Recently uploaded (20)

Time Logger- BSc.CSIT Internship report