Pratiksha Patel 180630107060 Report

3180701 Cover Page
SOFTWARE ENGINEER INTERNSHIP
FROM
AN INTERNSHIP REPORT
Submitted by
Pratiksha S. Patel
180630107060
In partial fulfillment for the award of the degree of
BACHELOR OF ENGINEERING
in
Computer Engineering
Madhuben and Bhanubhai Patel
Institute of Technology
Gujarat Technological University, Ahmedabad

April, 2022
Gujarat Technological University MBIT

3180701 College Certificate
Madhuben and Bhanubhai Patel Institute of Technology

New Vallabh Vidyanagar, 388121
CERTIFICATE
This is to certify that the project report submitted along with the project entitled
Software Engineer Internship has been carried out by Pratiksha S. Patel
under my guidance in partial fulfillment for the degree of Bachelor of
Engineering in Computer engineering, 8th Semester of Gujarat Technological
University, Ahmadabad during the academic year 2021- 22.
Prof. Sunit Parmar Prof. Nirav Raja
Internal Guide Head of the Department
Gujarat Technological University i MBIT

3180701 Industry Letter Head
[Industry Letter Head]

Date: 11/04/2022
Gujarat Technological University ii MBIT

Candidate’s Acknowledgement and Declaration
3180701
Madhuben and Bhanubhai Patel Institute of Technology

New Vallabh Vidyanagar, 388121
DECLARATION
I hereby declare that the Internship report submitted along with the Internship
entitled software engineer internship submitted in partial fulfillment for the
degree of Bachelor of Engineering in computer engineering to Gujarat
Technological University, Ahmedabad, is a bonafide record of original project
work carried out by me at Crest Data Systems under the supervision of Bhumika
Dave 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.
Name of the Student Sign of Student
Pratiksha S. Patel
Gujarat Technological University iv MBIT

Candidate’s Acknowledgement and Declaration
3180701
ACKNOWLEDGEMENT
The success and final out comes of this internship required a lot of guidance and assistance from
many people and we are extremely privileged to have got this all along the completion of my
internship. All that we have done is only due to such supervision and assistance and we would not
forget to thank them.
I would like to take the opportunity to thank and express my deep sense of gratitude corporate
mentor Mr. Mehul Solanki. I am greatly indebted to them for providing their valuable guidance
at all stage of the study, their advice, constructive suggestions, positivity and supportive attitude
and continuous encouragement, without it would have not been possible to complete the
internship. I would also like to thank Miss. Helly Dhamelia Who in spite of busy schedule has
co-operated with us continuously and indeed, his valuable contribution and guidance have been
certainly indispensable for my internship work.
I heartily thank my faculty mentor of Computer Engineering department Prof. Sunit Parmar. I
am thankful to and fortunate enough to get constant encouragement, support and guidance from
all teaching staffs of Information Technology which helped us in successfully completing my
internship program. I am thankful to Crest Data Systems for giving me the opportunity. I owe
my wholehearted thanks and appreciation to the entire staff of the company for their cooperation
and assistance during the course of my work.
Gujarat Technological University iv MBIT

3180701 Abstract
ABSTRACT
This application is integrated development of the Jira application with a custom
analytics platform where all the employees daily, weekly, monthly, and yearly
activities will be analyzed.
Employees in the organizations are required to manage their daily activities in the
work-log management system. The Jira application as an efficient work-log
management system provides support for the employee timesheet management
where all the users can manage their daily activities on different tasks along with
working hours and descriptions.
These details are required to manage daily and max weekly as it impacts many
modules of the organization. All the Employees are required to manage this log
without delay. This application is focused on identifying delays in logs and updating
employees for other timesheet activities on regular basis.
Gujarat Technological University v MBIT

3180701 List of Figures
List of Figures
Fig 1.1 Company Logo 1
Fig 2.1 Agile Technology 5
Fig 4.1 Data Flow Diagram (Level 0) 10
Fig 4.2 Data Flow Diagram (Level 1) 11
Fig 5.1 Activity Diagram (Login) 12
Fig 5.2 Activity Diagram (TATIM Main Function) 13
Fig 5.3 UseCase (Admin) 14
Fig 5.4 UseCase (PMO) 15
Fig 5.5 Registration Page UI 16
Fig 5.6 Login Page UI 17
Fig 5.7 Dashboard Page UI 18
Fig 5.8 Reports Page UI 18
Fig 5.9 Configuration Page UI 19
Fig 6.1 Scrum Details 23
Gujarat Technological University vi MBIT

3180701 Abbreviations
Abbreviations
CEO Chief Executive Officer
CTO Chief Technical Officer
QA Question & Answers
API Application Programming Interface
Gujarat Technological University vii MBIT

3180701 Details of Chapters
Table of Contents
Certificate i
Industry Letter Head ii
Declaration iii
Acknowledgment iv
Abstract v
List of Figures vi
Abbreviations vii
Table of Contents vii
Chapter 1 Overview of the Company 1
1.1 History 1
1.2 Different Products 1
1.3 Capacity of Company 2
Chapter 2 Different Unit of the Organization 3
2.1 Different Departments 3
2.2 Sequence of Operation for Manufacturing of End Products 3
2.3 Different Stages of the Production 4
Chapter 3 Introduction to Internship 6
3.1 Internship Summary 6
3.2 Purpose of the Project 6
3.3 Objective of the Project 7
3.4 Scope of the Project 7
Chapter 4 System Analysis 8
4.1 Study of Current System 8
4.2 Problem and Weakness of the Current System 8
4.3 Proposed System 8
4.4 Features of Proposed System 8
4.5 Main Modules in New System 9
Chapter 5 System Design 12
5.1 System Design & Methodology 12
5.2 UseCase Diagrams 14
5.3 User Interface 15
5.4 Backend APIs 19

3180701 Details of Chapters
Chapter 6 Implementation 21
6.1 Implementation Environment (Tools and Technology) 21
6.2 Coding Standard 24
Chapter 7 Project Requirements 26
7.1 Prerequisites 26
7.2 Requirements 26
Chapter 8 Conclusion and Discussion 27
8.1 Timesheet Automation Tool (Project Outcomes) 27
8.2 Learning Outcomes 27
8.3 Experience 27
8.4 Conclusion 27
References 28

3180701 Overview of the Company
1.0 OVERVIEW OF THE COMPANY
I got the internship at the Crest Data Systems. Crest Data Systems was founded in 2013 and works
in several fields of data analysis and cyber security. Crest Data Systems offers software
development, product integrations, cloud operations, and managed services to global enterprises and
innovative start-ups.
Fig 1.1 Company Logo
1.1 HISTORY
Crest Data Systems was founded in 2013 by current CEO Malhar Shah and current CTO Neha Shah
with a vision to provide quality service in the area of data analysis and automation. Going forward it
expanded it’s horizon with cyber security, DevOps and cloud. Crest Data Systems was started with
3 person organization and now it operates with over 1000 employees in it.
Crest Data Systems’ first client was CISCO. Now it’s client list includes many of the fortune 500
companies and some well known industry leaders like VMware, Lockhead Martin, Splunk, aws,
docker, etc. Currently company holds very high number of clients across the glob and have been
very successful in maintaining them.
1.2 DIFFERENT PRODUCTS
Crest Data Systems mainly works with the data analysis and security analysis. It also provides
automation solutions for cloud and DevOps related works.
It also provides scalable solutions for data visualization and data migration problems for very large
scale data. It includes capabilities to provide systems that automatically ingest the data and create
Gujarat Technological University 1 MBIT

3180701 Overview of the Company
indicators for cyber threat.
One of the main partners of the company is Splunk. Splunk is tool used for the data visualization
and any data related operations. It also provides use case as security tool.
1.3 CAPACITY OF COMPANY
Currently our company holds over 1000 employees. But as company is growing rapidly it’s
capacity is going higher and higher.

3180701 Different Unit of Organization
2.0 DIFFERENT UNIT OF THE ORGANIZATION
As company has grown in size, it was needed to separate various departments to maintain the
management and smooth flow of process. Crest Data Systems has various units to handle different
use cases.
2.1 DIFFERENT DEPARTMENTS
Some departments in the company are as per below:
2.1.1 BU
This unit deals with the businesses and management. It is mainly concerned with the
development of software for various clients.
2.1.2 HR
Most common department of the company which deals with the human resource management
processes like hiring, evaluation for promotion, salary related issues etc.
2.1.3 IT
This department is used to maintain the IT infrastructure of the company and employees. They
also helps with any type of technical issue faced by clients and employees of the company.
There are some other departments out there which falls under the BU which handles various types
of the work.
2.2 SEQUENCE OF OPERATION FOR MANUFACTURING OF

END PRODUCT
Main end product of our company is mostly the software. Software is very different thing than other
industry’s end products. It’s process is very different.

2.2.1 Client requirement understanding
First step to build something is to know what to build. Specially in case of software it is
very important to understand the client requirement completely as if the requirement
changes then it will create huge problems in later part of the development. Often a
requirement document is created which is called client requirement document to make
thing more clear.
2.2.2 Planning
Second step to build something is to know how to build. In software development, we

need to decide the entire flow of the process like which technology stack will be used?
Which type of architecture will be used? Etc.
Development: After sufficient planning comes the development part. In this part actual
software is build. Or at least the part of the software is build in methods like agile delivery
method.
Review and QA: Internal review and QA is done to ensure the quality of the final product
as in software in this case. It also helps to identify the bugs before releasing the software.
Release or Deployment: In this phase the software is delivered to the client either the
direct code or hosted service.
Maintenance: This part comes in picture after the final delivery of the software. This
phase includes tasks such as making sure the service is always running, bug fixes etc.
2.3 DIFFERENT STAGES OF THE PRODUCTION
At our company we mostly use agile development process in which the software is delivered in
different parts or phases which are called the sprints.

Each sprint contains the upgraded version of the software and it is kept upgrading unless we reach
the final product.
Fig 2.1 Agile Methodology

3180701 Introduction to Internship
3.0 INTRODUCTION TO INTERNSHIP
The chapter elaborates the process of the training, the overview about the
technology learned, scope, objective and purpose of the internship.
3.1 INTERNSHIP SUMMARY
The entire internship period was a huge exposure towards the software development and its different
stages along with learning of different technologies and tools.
During the 13 weeks of internship a lot of learning is being done on different tools and technologies
which can enhance the overall efficiency and coding standards. Training begun with the basic concept of
Linux, Git and Bitbucket and VS Code , Basics of HTML, CSS and JavaScript, Advanced JavaScript,
TypeScript and Angular JS.
Followed by training a project was assigned to all the interns under the guidance of the project lead and
the mentor, wherein had to build a software from scratch using the concepts and skills learnt during the
entire training and along with it also an experience was gained regarding the real software development
process, right from planning, researching, designing and prototyping to development and testing.
Project Title is Timesheet Automation Tool. It is a tool that monitor employees daily, weekly, monthly,
and yearly activities. And in case of any improper entry employees will be notified automatically.
3.2 PURPOSE OF THE PROJECT
Main purpose of this internship is to gain the knowledge about the usage of various technologies in
industry.

3180701 Introduction to Internship
Also gain knowledge how to behave in the professional environment. Also improve communication
skills specifically for the professional environment.
3.3 OBJECTIVE OF PROJECT
Employees in the organizations are required to manage their daily activities in the work-log
management system. The Jira application as an efficient work-log management system provides support
for the employee timesheet management where all the users can manage their daily activities on
different tasks along with working hours and descriptions. Also, a check is to be done constantly,
whether the employees have entered all correct information or not, whether their work log hours are
exceeding max limit, etc. All these tasks are currently done manually by the employees. And hence, an
automation tool is to be made to ease this manual task eventually saving energy and time of the
employees.
3.4 SCOPE OF THE PROJECT
By using this project, PMO can easily monitor data and take actions. This project has an automated part
and a user-specific part. The later one is web-based. Automated part will be running at a specific time
every day. The web-based part is to provide the administrator with the information obtained from the
automated part. An access to the HRMS is required to get the employee information. Also, an access to
the Jira Database is required to get the Employee daily work log hours information.

3180701 System Analysis
4.0 SYSTEM ANALYSIS
The chapter states the information about the project. It describes the features,
scope, weakness and detailed description of the project.
4.1 STUDY OF CURRENT SYSTEM
In the current system, on every weekend PMO, need to fetch the data from Jira Database of the
work log hours of all the employees and then manually need to figure out the list of employees
with exceeding work logs and mistaken work logs.
4.2 PROBLEM AND WEAKNESSES OF CURRENT SYSTEM
The entire task of finding the list of employees with incorrect work log hours is to be filtered out
manually which is time consuming and tedious task.
4.3 PROPOSED SYSTEM
An automation tool can be developed which can fetch data from the Jira Database and can directly
give the list of employees with incorrect work logs, employees with leaves, and also list of
employees who have worked extra and who have worked less than the preferred time. Also this
tool can save the energy and time of employees working manually in order to do the same task.
4.4 FEATURES OF PROPOSED SYSTEM
The project is Timesheet Automation Tool. It is on the issue of employees logging their work
hours in a timely manner. The project has both user-specific functionalities and automated
functionalities. It is a web-based application. We have only one type of user, an admin.
4.4.1 The Automated Part of the Application
Every day at 12:00 PM, this automated process will run and it will fetch all the users and
their associated log hours of the previous week(starting from Monday to Sunday). It will
send emails to all the users who have not regularly updated log hours.
4.4.2 The User-specific part of the application
After analyzing the previous week’s data, the information will be shown to the admin.
Information is extracted from the analyzed data. The admin can now check the
employees and log hours related information like the number of regular and irregular
employees. Employees who are most irregular. We can extract a good amount of
information from the stored data. The admin can also manually trigger the automated
process of the application. Here the mail will not be sent.
4.4.3 Business Reason:
The employer will benefit from this project as it will help them discover the irregular log
hours data. By sending an email, we are reminding the employees to be timely in their
log hours. This will help regulate the log hour information to be regular and track the
employee’s progress.
4.5 MAIN MODULES IN NEW SYSTEM:
4.5.1 Login and Registration Module

Registers the user to and performs the Login Functionality.
4.5.2 Manage Employee

Show the Employee details and manage their leaves.
4.5.3 Manage Employee Work log Details

Check and Notify the employees who have entered incorrect log hours.
4.5.4 Configuration
Contains the information about log hours and the mail send to the employees.
4.5.5 Report
It contains the day wise information about the employees who have entered incorrect log
hours
4.5.6 Dashboard
Represents the data graphical to get a clear view.
Data Flow Diagram(Level 0): The log hours data from JIRA API and the leave and
holiday data from the HRMS API are used in by Timesheet Automation tool and the
useful data is then sent to PMO and the related employees are notified
Fig 4.1 Data Flow Diagram (Level 0)

Data Flow Diagram(Level 1): PMO can login using the credentials and they will be allowed to
use the functionality and manage configurations while the PMO who is admin will be allowed to
use the additional settings of System Configuration and can access email sending functionality.
Fig 4.2 Data Flow Diagram (Level 1)

3180701 System Design
5.0 SYSTEM DESIGN
The chapter describes the data flow and the Interface design of the project. It also
specifies the use of backend APIs.
5.1 SYSTEM DESIGN & METHODOLOGY
System Design and Methodology refers to the process flow and working of the project.
Activity Diagram (Login) : PMO can login by entering credentials and if they are valid they will
be redirected to Dashboard Page.
Fig 5.1 Activity Diagram (Login)
Activity Diagram (TATIM Main Function) : Worklog data is fetched from the JIRA and the data
is then used to verify the employees who have entered incorrect log hours and check the holiday list. If
there are any incorrect logs then mail will be sent to the employee and the weekly data will be stored in

the JSON format.
Fig 5.2 Activity Diagram (TATIM Main Function)

5.2 USECASE DIAGRAMS
The UseCase diagrams refers to the functionality and cases which a specific user can have access
of.
UseCase(Admin): Admin can login through the valid credentials and can access an addon
configuration settings and can get Employee Performance Charts.
Fig 5.3 UseCase(Admin)
UseCase (PMO): PMO can access all the features of the project except the Addon Configuration
Settings.

Fig 5.4 UseCase (PMO)
5.3 USER INTERFACE
The User Interface for all the modules in the project are as following :
5.3.1 Registration Page
INPUT: Using the valid credentials (user email id and password), registration can be done.
OUTPUT: There are 3 Possibilities with registration. First, is user gets successfully registered and is
navigated to login screen. Second, is the user is already registered, and that’s why would be navigated to

login screen. And the third case is when user doesn’t exist, and so invalid credentials or invalid user
itself.
Fig 5.5 Registration Page UI
5.3.2 Login Page
INPUT: Using the valid credentials (user email id and password), can be done.
OUTPUT: Invalid credentials can lead to failure in logging in.

Fig 5.6 Login Page UI
5.3.3 Dashboard Page
System will show employees' data in the form of Charts, Descriptions, and Graphics. It should
display total users. Previous Week Statistics: Up to Date, Email Sent for Update, etc.. with the
donut chart. Current Month Statistics.

Fig 5.7 Dashboard Page UI
5.3.4 Reports Page

There should be a search bar at the top that users will use to search for specific employees. The
Employee details should contain information like Employee Name, Employee Email, Business
Unit, Weeks and Logs.
Fig 5.8 Reports Page UI

6.3.5 Configuration Page

Configurations of the email that is to be sent and the system parameters like - minimum hours per week,
maximum hours per week can be edited.
Fig 5.9 Configuration Page UI
5.4 BACKEND APIs
Registration API: This API will take the Registration Details Along with username (E-mail) and
Password, that will Used as Credentials while Login
Login API: This API Will Allow PMO and ADMIN Login, with their Credentials, if the credentials are
correct then system will allows them to Access the Another Features of the TATIM, otherwise they are
not able to Access the Dashboard
Dashboard API: This API will Allow PMO and Administrators to show the data and generated Reports
in the form of Graph and chart. It shows the total number of Employees along with the previous weeks
of Statistics.
Report API: This API Will Generate the Report, so from this Report PMO can Check the List of
defaulters (Who have entered Improper Logs).

Configuration API: This API will allow PMO to change the E-mail as well as the System
Configuration. This API Also Manage the list of higher authority(Exceptional Employee), So that they
will not get the Email Regarding Improper log.

3180701 Implementation
6.0 IMPLEMENTATION
The chapter describes the tools, technology and methods which are used in the
creation in the project.
6.1 IMPLEMENTATION ENVIRONMENT (TOOLS & TECHNOLOGY) :
Tools and Technology used in the project are as follows:
6.1.1 TOOLS
VS Code
VS Code is an integrated development environment (IDE) used in computer
programming. It is developed by the Microsoft It provides code analysis, a graphical
debugger, an integrated unit tester, integration with version control systems, and supports
web development.
Visual Studio
Visual Studio have good features and performance such as : Very high performance, on par
with Angular JS.: Increase the speed to develop features by about 200% to 300%. Reduce about
40% of human (developer) induced errors. Great editor support. Completion everywhere. Less
time debugging. Designed to be easy to use and learn. Less time reading docs. Minimize code
duplication. Multiple features from each parameter declaration. Fewer bugs.
6.1.2 TECHNOLOGY
Angular JS
This topic can help you understand Angular: what is Angular, what advantages it
provides, and what you might expect as you start to build your applications. Angular is a
development platform, built on TypeScript. As a platform, Angular includes: A
component-based framework for building scalable web applications A collection of well-

integrated libraries that cover a wide variety of features, including routing, forms
management, client-server communication, and more A suite of developer tools to help
you develop, build, test, and update your code
With Angular, taking advantage of a platform that can scale from single-developer
projects to enterprise-level applications is obtained. Angular is designed to make
updating as straightforward as possible, so an advantage of the latest developments with a
minimum of effort. Best of all, the Angular ecosystem consists of a diverse group of over
1.7 million developers, library authors, and content creators.
Angular Material UI:
Angular Material is a User Interface (UI) component library that developers can use in
their Angular projects to speed up the development of elegant and consistent user
interfaces. The key features are: High quality : Internationalized and accessible components
for everyone. Well tested to ensure performance and reliability. Straightforward APIs with
consistent cross platform behaviour. Versatile : Provide tools that help developers build their own
custom components with common interaction patterns. Customizable within the bounds of the
Material Design specification. Frictionless: Provides a smooth flow in using all the components
of Material UI in the project.
Built by the Angular team to integrate seamlessly with Angular. Whether starting from scratch or
dropping into existing applications, flexibility is provided.
.net Framework 6.0:

Getting started is easy. New language features in C# 10 reduce the amount of code you
need to write. And investments in the web stack and minimal APIs make it easy to
quickly write smaller, faster microservices. .NET 6 is the fastest full stack web
framework, which lowers compute costs if you're running in the cloud. .NET 6
and Visual Studio 2022 provide hot reload, new git tooling, intelligent code editing,
robust diagnostics and testing tools, and better team collaboration.
SCRUM:
Scrum is a framework within which people can address complex adaptive problems,
while productively and creatively delivering products of the highest possible value.
Scrum is a lightweight framework that helps people, teams and organizations generate
value through adaptive solutions for complex problems. Scrum co-creators Ken
Schwarber and Jeff Sutherland have written The Scrum Guide to explain Scrum clearly
and succinctly. This Guide contains the definition of Scrum. This definition consists of
Scrum’s accountabilities, events, artifacts, and the rules that bind them together.
In a nutshell, Scrum requires a Scrum Master to foster an environment where: A Product

Owner orders the work for a complex problem into a Product Backlog. The Scrum Team
turns a selection of the work into an Increment of value during a Sprint. The Scrum Team
and its stakeholders inspect the results and adjust for the next Sprint. Repeat
Fig 6.1 Scrum Detail
6.2 CODING STANDARD

6.2.1 File Naming Convention

File names use proper letters only. File names should have its first letter small cap. All code
and text files should be completely free of TAB characters. All indentation should be done
with space.
6.2.2 Creating the source code

We first require adding the purpose in all the files at the beginning in the comment. Class
files should be coded correctly and objects also should be declared correctly.
6.2.3 General Coding Standard

It is acceptable to break up long statements into multiple lines. Do not put multiple statements
on one line. Every coding block should be intended. All the variables and constant declaration
should be at the top. Source code in the particular form or module or class module.
6.2.4 Variable Standard

Variable names must be meaningful. Variables are formed from letters A-Z, a-z, digits 0-9
and underscore_. They are case-sensitive. Variable names consist of a data type used in it.
6.2.5 Programming Conventions

Statements: We have returned only one statement per line.
Spacing: We have typed a space before and after all operators such as (+,*,1<,=, etc.) and
the assignment symbols (=).
Indenting: Improve the readability of script by using tabs to indent the body of statements
such as these: DO, FOR, IF.
Also use a tab to indent statements continued onto a new line. The coding standard is well
defined and standard style of coding. With the help of coding standards any person can find
the exact meaning of code and understand the working of the system. A coding standard
includes the way the variables are to be named, the code that is to be laid out, the comments
that are to be described etc.

6.2.6 File Naming Conventions:
The files created in the project are named in such a way that the first letter is capitalized. The
files in the same module are grouped together in a folder with appropriate name. This makes it
easier for the developer to navigate to the appropriate file. Thus, it is a good coding technique
that enables faster access to the files.
6.2.7 Identifier Standards:

The other variable names must also be relevant and must be descriptive.
6.2.8 Comment Standards:

The other technique used for programming is comments. The few lines of comments make the
code more elegant. Sometimes it makes the code easier to understand and works as a help for the
programmers.

3180701 Project Requirements
7.0 PROJECT REQUIREMENTS
7.1 PREREQUISITES:
Visual Studio
Vs Code
Node JS
Angular CLI
ASP.net
7.2 REQUIREMENTS :
The application must be to identify employee’s information from Jira Application. The
application should perform daily checks on employee’s timesheet details for previous weeks.
The application must notify of the delay in timesheet update based on configurable criteria
( Minimum work hours log required daily/weekly, Max work hours per week/day). Analytics
Dashboard for Admin. Algorithmic development for critical delays. All the Employees and
Admin must get the notification through email daily. Email configuration and Templates.
Application configuration ( identifying modular and automation in the workflow)

3180701 Conclusion and Discussion
8.0 CONCLUSION AND DISCUSSION
8.1 TIMESHEET AUTOMATION TOOL (PROJECT OUTCOMES)

Successfully developed frontend of the Automation tool using Angular JS framework. APIs
where also created successfully using .net framework. Followed by it, integration of frontend
with backend was done.
8.2 LEARNING OUTCOMES

A practice-oriented and 'hands-on' working experience in the real world or industry, and to
enhance the student's learning experience. An opportunity to develop a right work attitude, self-
confidence, interpersonal skills and ability to work as a team in a real organizational setting.
8.3 EXPERIENCE
The entire atmosphere and environment at CREST DATA SYSTEMS has been vibrant,
energetic and full of inquisitiveness to learn and explore new things. At the end of every Sprint,
Retrospection meetings are conducted, wherein what we did nice, what could be improvised and
who were helpful to whom is being discussed which promotes reflection towards one’s own work
and teamwork. Also, all the seniors are very gentle and responsive. Overall experience was
outstanding.
8.4 CONCLUSION
This project intends to introduce more user friendliness. We provided Analytical data to Project
Manager so that they can easily Analyze that data and use effectively to take actions according to
Employee Data.

3180701 References
REFERENCES
1. Angular: https://angular.io/
2. JavaScript: https://javascript.info/
3. TypeScript: https://www.typescriptlang.org/
4. Angular Material: https://material.angular.io/

Pratiksha Patel 180630107060 Report

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Pratiksha Patel 180630107060 Report

Uploaded by

Copyright:

Available Formats

3180701 Cover Page

SOFTWARE ENGINEER INTERNSHIP

Gujarat Technological University, Ahmedabad

Gujarat Technological University MBIT

Madhuben and Bhanubhai Patel Institute of Technology

Software Engineer Internship has been carried out by Pratiksha S. Patel

under my guidance in partial fulfillment for the degree of Bachelor of

Engineering in Computer engineering, 8th Semester of Gujarat Technological

University, Ahmadabad during the academic year 2021- 22.

Prof. Sunit Parmar Prof. Nirav Raja

Internal Guide Head of the Department

Gujarat Technological University i MBIT

[Industry Letter Head]

Gujarat Technological University ii MBIT

Madhuben and Bhanubhai Patel Institute of Technology

entitled software engineer internship submitted in partial fulfillment for the

degree of Bachelor of Engineering in computer engineering to Gujarat

Technological University, Ahmedabad, is a bonafide record of original project

Name of the Student Sign of Student

Gujarat Technological University iv MBIT

forget to thank them.

certainly indispensable for my internship work.

all teaching staffs of Information Technology which helped us in successfully completing my

and assistance during the course of my work.

Gujarat Technological University iv MBIT

This application is integrated development of the Jira application with a custom

activities will be analyzed.

work-log management system. The Jira application as an efficient work-log

management system provides support for the employee timesheet management

working hours and descriptions.

employees for other timesheet activities on regular basis.

Gujarat Technological University v MBIT

Gujarat Technological University vi MBIT

CTO Chief Technical Officer

QA Question & Answers

API Application Programming Interface

Gujarat Technological University vii MBIT

Gujarat Technological University i MBIT

Gujarat Technological University i MBIT

1.0 OVERVIEW OF THE COMPANY

Fig 1.1 Company Logo

1.2 DIFFERENT PRODUCTS

Gujarat Technological University 1 MBIT

1.3 CAPACITY OF COMPANY

Gujarat Technological University 2 MBIT

2.0 DIFFERENT UNIT OF THE ORGANIZATION

2.1 DIFFERENT DEPARTMENTS

Some departments in the company are as per below:

2.2 SEQUENCE OF OPERATION FOR MANUFACTURING OF

Gujarat Technological University 3 MBIT

Second step to build something is to know how to build. In software development, we

2.3 DIFFERENT STAGES OF THE PRODUCTION

Gujarat Technological University 4 MBIT

Fig 2.1 Agile Methodology

Gujarat Technological University 5 MBIT

3.0 INTRODUCTION TO INTERNSHIP

3.1 INTERNSHIP SUMMARY

3.2 PURPOSE OF THE PROJECT

Gujarat Technological University 6 MBIT

3.3 OBJECTIVE OF PROJECT

3.4 SCOPE OF THE PROJECT

Gujarat Technological University 7 MBIT