Industry Training Diary-1

Industrial Training Dairy
G.S. Mandal’s
Marathwada Institute of Technology Polytechnic, Aurangabad Beed

By Pass Road, Aurangabad- 431010, Maharashtra India
[Approved by AICTE New Delhi, DTE Mumbai & Affiliated to MSBTE Mumbai (MS)]
Ph.: +91 0240-2375333, 2376303 Fax. : + 91 0240 – 2376230

DTE Institute Code: 2224 MSBTE Institute Code: 0066
Website: - www. mit.asia; http://polyaurangabad.mit.asia

Email:sunil.deshmukh@mit.asia
Six Weeks Industrial Training Diary
Name of Student:_________________________________________________________
Department: ____________________________Enrollment No:_____________________
Student Contact No.___________________ Parent Contact No.___________________
Name of Industry/Organization: _____________________________________________
Name of Student Mentor: ________________________Contact No:________________
Name of Industry Training Charge: ___________________________________________
M.I.T., Polytechnic, Aurangabad Page 1

Academic Year 2022 - 2023

VISION OF THE INSTITUTE:
To become a globally recognized technical institution in skill and competency development for acquiring
latest requirements of industry by keeping social and environmental awareness.
MISSION OF THE:
INSTITUTE
Institute aims at imparting student centric quality education through teaching- learning process and
training for diploma students so that they will be able to start their own business, employable at the
best position in the field of engineering and technology, achieve higher education capability to become
a best citizen.
ABOUT MIT POLYTECHNIC, AURANGABAD
“Gramaudyogik Shikshan Mandal (GSM)” was established by the renowned freedom fighter and
visionary Late Shri. Aanandravaji Deshmukh. GSM focused on imparting education in science and
technology at village level in order to develop village and make it a self sustainable. G.S. Mandal has
established 24 institutes and 5 centres of learning at multiple locations in India. MIT is a group of
academic and research institutions.
MIT Polytechnic, Aurangabad was established in the year 1983. MIT Polytechnic offers 5
Diploma Full Time regular courses and 1 Part Time course. MIT provides best infrastructure facility
including well equipped laboratory and research development centre with highly qualified faculties.
Because of effective interaction with industrial sector and government organizations, MIT is pioneer in
establishing the triangular partnership amongst institution, industry and government organizations.
Institute has been awarded “EXCELLENT” Remark in External Institute Monitoring by MSBTE
Mumbai for all the courses.
MIT Polytechnic, Aurangabad has been ranked in “GOLDEN” category in the AICTE-CII Industry
Linked Technical Institute Survey 2018 Seventh Edition.

Rationale:
Industrial training course is introduced to all diploma programs with an objective to develop the
traits of industry culture among the students before they enter into the world of industry. By exposing
and interacting with the real life industrial setting, students will appreciate and understand the actual
working of an industry, best practices adopted in industry.
The industrial skills like Soft Skills i.e. Communication, Presentation, Life Skills i.e. Time
management, Safety, Innovation, Entrepreneurship, Team building, etc. and Hands-on Design,
Implementation and Quality Assurance will be included among the student. This short association with
industry will be instrumental in orienting the students in transforming them into industry ready output
after completion of diploma program.
Course Outcomes:
A student will be able to,
1. Communicate effectively (verbal as well as written) the work carried out.
2. Prepare and present the report of the work carried out.
3. Exercise time management and safety in the work environment.
4. Working in a team.
5. Demonstrate various quality assurances.
6. Exhibit the work carried out.
Teaching and Examination Scheme:
Teaching Scheme Total Credits Examination Scheme
L T P (L+T+P) Theory Marks Practical Marks Total Marks

PA ESE PA ESE
-- -- 6 6 -- -- #75 #75 150

About the Record Book:

Students are required to use this diary throughout the Industrial training. This diary must be filled in
everyday and must be verified form mentor every week. All relevant findings and activities must be
recorded weekly. Among the relevant information to be recorded include:
• Manufacturing processes.
• Testing and quality assurance methods.
• Design circuits, flowcharts, algorithms, if any.
• Specifications of machines, equipments, components, etc.
• Maintenance procedures, production planning.
• Organizational structure.
• Training progress.
• Suggestions, assignment and discussions results from mentor and industry supervisor.
• Summary of any relevant work that has been done.
Details of Industry/Organization
• Name of Industry: ______________________________________________________
• Address: ______________________________________________________
______________________________________________________
• Contact Details of Industry Training In charge:
o Name: ______________________________________________________ o
Designation: ______________________________________________________ o Email
Id: ______________________________________________________ o Contact
Number: ______________________________________________________
• Type of Products: Service Industry/Manufacturing Industry.  Type of Control: Government/
Semi- Government/PSU/Private
• Type of Company: Large Scale/ Medium Scale/Small Scale.

Day 1: Date:
-
Company Introduction
-
Visit Company
-
Project Environment
-
(Development, Testing, Production )
-
Development Desk
-
Development System Configuration
-
(Required System hardware and software )
-
Testing Desk
-
Development System Configuration
-
(Required System hardware and software )
-
Data Ware House
-
(MS sql server , Excel Server)
-
Data Storage Device
-
(Hard Disk, SSD Disk )
-
Deployment Desk
-
Customer Support Desk
Day: 2 Date:

Company And Project Employee Structure
BA (Business Analyst )
- Collect all project related information from stack holder and give this information to team.
- Prepare BRS and SRS Document (Software Requirement Specification And Business
Requirement Specifications)
- Direct Contact with Stack Holder and project manager.
PM (Project Manager)
- Setting and managing client expectations.

- Developing a detailed project plan.
- Defining the scope of the project understanding project risks and assigning team members
to specific tasks
- Monitor Project Progress and Set Deadlines
- Solve Issues That Arise
Day 3: Date:
Team Lead
- Team lead must understand technical concepts

- Team Lead must also both have good people and communication skills to motivate and
supportive
- Ensure that the company is delivering quality products and services
- Communicate with all stakeholders, supporting transparency and a free flow of information
- Report problems to higher-level leaders and get resources and support to resolve them -
Help to deploy new initiatives and procedures

Day: 4 Date:
SQA ( Software Quality Assurance)

It is a process in which client monitors and measures the strength of developed application.
Factors
1- Requirement of client are fulfilled are not.

2- Client expectations ( performance and security)
3- Time to deliver
4- Cost of project
5- Maintenance
Day: 5 Date:
1- SDLC – (Software development life cycle)/ Fish

model a- Fish model
b- Waterfall model
c- V- model
d- Agile model ( 90-95%)
SDLC – Software development life cycle.

It is a process used by the software industry to design , develop and test high quality
software.
The SDLC aims to produce a high quality software that meets clients expectations ,,
reaches completion within time and cost estimates.
Different types of phases / stages are there in SDLC

1-
Information gathering/ client requirement gathering
2-
Analysis
3-
Design
4-
Coding/ development
5-
Testing
6-
Maintenance/ Support
Day: 6 Date:
Process of SDLC Followed by software industry for smooth working of project,
Different Phases of SDLC
o Client (Application)
o Information gathering/ requirement gathering – BA ( BRS) ( Business requirement
specification )
o Analysis – BA – SRS, FRS,CRS ( Software / System / Functional/ Customer Requirement
Specifications)
o Design Architect Design HLD
LLD o Coding Developer –Application
Implementation o Testing – Tester = Testing The
Application o Maintenance – Support

Day: 7 Date:
SRS document Include

Functional flow diagram

Eg – Facebook app – Signup – Login page – Home page – profile page
 Functional requirement
Eg. Signup – ( Requirement – First name, middle name, last name, mobile number, mail id,
password , submit button)
 Use cases Cases consists of description and Acceptance criteria.
 Screenshot / snapshot
Snapshots are visualisation of functionalities before development of product.
Snapshot is made by BA using HTML code and Irise software.
Day: 8 Date:
Waterfall Model
1- It is a process to develop a software.
2- Waterfall model is called as a sequential model.
3- In Waterfall model we can move to next phase when previous phase is completed.
4- A phases fall from higher level to lower level , like a waterfall. Its named as a waterfall
model.
5- Duration of waterfall model is 3 months.
Advantages of waterfall model.

1- Simple and easy to understand and use.
2- For smaller projects waterfall model works well.
3- Phases are processed and completed one at a time.
Dis-advantages of waterfall model.

1- Cannot accept new CR ( Change request)
2- For bigger and complex projects this model is not good.
3- If we are getting any changes we cant go to the back stage.
Day 9: Date:
Agile model/Methodology/process
1- The Agile scrum methodology is combination of both incremental and
iterative model for managing product development.
(Incremental – which keeps on increasing, iterative – repetition till the project is
completed)
2- Agile is a continuous process for development and testing. 3- Duration –
1/2/3/4 weeks – 2 weeks 4- Agile is a Value driven process.
5- If CR comes then we will check its impact on development, testing and production or its
priority in the application.
Day: 10 Date:
Agile Meetings/Ceremonies
Meeting Purpose Involvement of people
Grooming Meeting ( Before To clear the doubts about the 30min/1hr Product owner
start of the sprint) requirement (Chair person), dev team,
testing team,design
team , Scrum
master(Optional)
Sprint Planning Meeting ( 1st 1- Decide the user story.( 1hr – Scrum master ( Chair
day of sprint) 1sprint – 20 req) person) , Product owner. Dev
2- Estimation( Time slot team , testing team, design
to complete the user team
story) ( 1 user story –
16hrs)
Daily stand up ( Scrum 1- What you have done 15min – Scrum master ( Chair
meeting) yesterday. person), Dev team, testing
2- What you are going to team, design team, Product
do today? owner (Optional)
3- What are the
roadblocks or issues?

Advantages
1- Sprint wise delivery.
2- Working software is delivered frequently.
3- Customers, developers and testers constantly interact with each other.
4- Change request are accepted immediately.

Day : 11 Date :
Sprint Review Meeting User story completed in 1 hr – Product

( end day of sprint ) testing ( Review) owner,Stackholder, Testing
team, design team , dev team ,
Scrum master
Sprint retrospective Meeting Good and bad things in the 30min – Scrum master
( End day of the sprint ) current sprint ( Discussion) ( Chair person) , Testing
team, dev team , design
team , product owner
( Optional)
Day: 12 Date:

Day :13 Date:

Day: 14 Date:
Day: 15 Date:

Day: 16 Date:

Day: 17 Date:

Day: 18 Date:
-At development site we create on registration form for practice

-Create Registration form
-There are different tabs and radio buttons
-Our aim is collect candidates information and saves in our data
base.
-After development testing process starts.
-In testing we check each and every phase of our code - Descriptive
and accretive criteria
Day : 19 Date:
Dev Environment
Unit testing
1- Testing which will be performed on individual module is called as unit testing.
2- Developer will perform unit testing
3- Test application is checked in +ve scenario/way
Integration Testing
1- The testing perform on main module by combining various sub module is
called
integration testing.
2- Integration testing is perform by developer.
There are 3 ways of integration testing

1- Top-down approach
2- Bottom-up approach
3- Sandwich/Bidirectional approach

Day: 20 Date:
SIT Environment (System integration testing)
Smoke testing
1- It is a software testing process that determines whether the developed software
build is stable or not.
2- When developer sends a new build/initial build to the tester then smoke testing is
performed.
3- It is also called as zero level testing or build Acceptance testing.
Smoke testing checkpoints/Validation.
1- Validating the core functionality

2- Validating the GUI/UI
functionality.
3- Validating the links present in
build. 4- Validating the tabs.
5- Validating the pages
In this testing we are going to verify all the basic functionalities are working

Day :21 Date:
SANITY TESTING
1- Sanity testing is a subset of regression testing.

2- After receiving the build from developer sanity testing is performed to ensure that the
changes are working as expected.
3- If it is working as expected, then we will be performing further functional testing.
4- If the defects are found during sanity testing, then build is rejected that is helpful inn
saving the time for execution of regression testing.

Day: 22 Date:
Regression Testing
1- After fixing the defect we will be checking that any other functionality of an application
will not be impacted that we are going to check that is nothing but regression testing.
2- Also when we are going to move from one environment to another we are performing
Regression testing.
3- Also we are going to perform regression testing whenever any CR comes from the
customer.

Day : 23 Date:
It includes six types of coverage
1- Behavioural coverage/testing.
2- Input domain coverage/testing.
3- Error handling coverage/testing.
4- Backend coverage/testing
5- Service level coverage/testing.
6- Calculation based coverage/testing
Day: 24 Date:
Types of Non-functional testing

1- Recovery testing
2- Compatibility testing
3- Configuration testing
4- Intersystem testing
5- Installation Testing
6- Parallel testing
7- Sanitation/Garbage testing
8- Globalisation Testing

Day : 25 Date:
UAT (User Acceptance testing)

1-
UAT is also called as customer acceptance testing.
2-
In UAT we check the real time scenarios of the application.
3-
UAT is a type of testing which is performed by the client or end user to verify /Accept the
software system before moving the software application to the production
environment.
4-
After completion of all the testing in SIT environment we perform UAT testing.
5-
In UAT both dev and testers are involved. 6- UAT is a type of testing, which is done by the
customer before accepting the final product.

Day: 26 Date:
Alpha testing
In alpha testing client is involved.
In alpha testing both dev and testers are present
Alpha testing ensures the quality of the product

before forwarding it further.
Alpha testing requires a testing environment
Alpha testing may require long execution cycle.
In alpha testing critical issues can be immediately

identified and fixed.
Day : 27 Date:
1- Error – If there is something wrong in the code then it is called as error.

2- Defect – while doing the testing when we found the error(functionality is
not working) then it is called as defect.
3- Bug – When developer will accept the defect then it is called as bug.

Day: 28 Date:
Execute Some Test cases on Pages :
1. Verify that all the required fields – username, email, password, confirm password, etc are
present on the registration page.
2. Verify that on passing valid values, a user should get registered and the same should be
allowed to login to the application.
3. Verify that if a user tries to register an existing username then an error message should get
displayed.
4. Verify that the required/mandatory fields are marked with the ‘*’ symbol.
5. Verify that for a better user interface – dropdowns, radio buttons, checkboxes, etc fields are
displayed wherever possible instead of just text boxes.
Remark, if any by Mentor:_________________________________________________________________
______________________________________________________________________________________
Mentor Industry Supervisor
Day : 29 Date:
1.
Verify the page has both submit and cancel/reset buttons at the end.
2.
Verify that clicking submits button after entering all the required fields, submits the data to
the server.
3.
Verify that clicking the cancel/reset button after entering all the required fields, cancels the
submit request, and reset all the fields.
4.
Verify that if no value is passed to the mandatory fields and submit button is clicked then it
leads to a validation error.
5.
Verify that the user can leave the optional fields blank and on clicking the submit button no

validation error appears.
6.
Verify that whenever possible validation should take place on the client side. For example,
if a user presses submit button without entering a username, and password then this
validation should take place on the client side instead of sending blank entries to the server.
7.
Check the upper limit of the different textbox fields.
Day: 30 Date:
Beta testing
In Beta testing End user is involved.
In Beta testing dev and testers are not available

immediately.
Beta testing also concentrates on the quality of

the product but collects users input on the
product and ensures that the product is ready
for real time users.
Beta testing doesn’t requires a testing

environment
Beta testing requires only a few weeks of

execution
Most of the issues or feedback collected from

beta testing will be implemented in future
version of the product.

Day : 31 Date:

Day: 32 Date:
On Going project record and code is store in following repository for easily available
o Remote repository server

o Github o Gitlab o BitBucket o cloud perform
Day : 33 Date:
o GitHub is a web-based version control and collaboration platform for software developers
o GitLab Continuous Integration and Delivery automates all the steps required to build, test
and deploy your code to your production environment.
o Continuous integration automates the builds, provides feedback via code review, and
automates code quality and security tests. It creates a release package that is ready to be
deployed to your production environment.
o Continuous delivery automatically provisions infrastructure, manages infrastructure
changes, ticketing, and release versioning. It allows, progressive code deployment, verifying
and monitoring changes made and providing the ability to roll back when necessary.
o Together, GitLab Continuous Integration and Delivery help you automate your SDLC,
making it repeatable and on-demand with minimal manual intervention.

Day: 34 Date:
Data Store on Database for online use.
Cloud Storage is a mode of computer data storage in which digital data is stored on servers
in off-site locations. The servers are maintained by a third-party provider who is responsible for
hosting, managing, and securing data stored on its infrastructure.
• Cost reduction
• Security
• Scalability

Day : 35 Date:
This are the clouds storage for project database and information.
 AW S
 Google Cloud
 Azure
 Digital Ocean
 Domain Racer
 Alibaba Cloud
 Oracle Cloud
 IBM Cloud
Day: 36 Date:
Reports:
Project Manager Report
Team Lead Report (Developer )
Team Lead Report (Tester )
Project deploy to client …
Remark, if any by Mentor:_________________________________________________________________
______________________________________________________________________________________
Mentor H.O.D

CERTIFICATE OF COMPLETION OF INDUSTRIAL TRAINING
This is to certify that Mr./Ms. __________________________________________
with Enrollment No._______________ has successfully completed Industrial Training
(22049) in _____________________________________________________________
from________________ to ________________.
We found him/her sincere during training period. We wish all the very best for his/her
future endeavors.
Mentor Head of Department
Seal of
Industry

TRAINING CALENDAR:

Industry Training Diary-1

Uploaded by

Document Information

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

Industry Training Diary-1

Uploaded by

Copyright:

Available Formats

Industrial Training Dairy

Marathwada Institute of Technology Polytechnic, Aurangabad Beed

Ph.: +91 0240-2375333, 2376303 Fax. : + 91 0240 – 2376230

Website: - www. mit.asia; http://polyaurangabad.mit.asia

Six Weeks Industrial Training Diary

Department: ____________________________Enrollment No:_____________________

Student Contact No.___________________ Parent Contact No.___________________

Name of Industry/Organization: _____________________________________________

Name of Student Mentor: ________________________Contact No:________________

Name of Industry Training Charge: ___________________________________________

M.I.T., Polytechnic, Aurangabad Page 1

Academic Year 2022 - 2023

ABOUT MIT POLYTECHNIC, AURANGABAD

M.I.T., Polytechnic, Aurangabad Page 2

Teaching and Examination Scheme:

Teaching Scheme Total Credits Examination Scheme

L T P (L+T+P) Theory Marks Practical Marks Total Marks

M.I.T., Polytechnic, Aurangabad Page 3

About the Record Book:

• Name of Industry: ______________________________________________________

• Contact Details of Industry Training In charge:

Designation: ______________________________________________________ o Email

Id: ______________________________________________________ o Contact

• Type of Products: Service Industry/Manufacturing Industry.  Type of Control: Government/

• Type of Company: Large Scale/ Medium Scale/Small Scale.

M.I.T., Polytechnic, Aurangabad Page 5

Company And Project Employee Structure

- Setting and managing client expectations.

- Team lead must understand technical concepts

M.I.T., Polytechnic, Aurangabad Page 6

SQA ( Software Quality Assurance)

1- Requirement of client are fulfilled are not.

1- SDLC – (Software development life cycle)/ Fish

d- Agile model ( 90-95%)

SDLC – Software development life cycle.

Different types of phases / stages are there in SDLC

Process of SDLC Followed by software industry for smooth working of project,

Different Phases of SDLC

M.I.T., Polytechnic, Aurangabad Page 8

SRS document Include

 Use cases Cases consists of description and Acceptance criteria.

Snapshots are visualisation of functionalities before development of product.

Snapshot is made by BA using HTML code and Irise software.

Advantages of waterfall model.

Dis-advantages of waterfall model.

M.I.T., Polytechnic, Aurangabad Page 10

M.I.T., Polytechnic, Aurangabad Page 11

Sprint Review Meeting User story completed in 1 hr – Product

M.I.T., Polytechnic, Aurangabad Page 12

Day :13 Date:

M.I.T., Polytechnic, Aurangabad Page 13

M.I.T., Polytechnic, Aurangabad Page 14

M.I.T., Polytechnic, Aurangabad Page 15

M.I.T., Polytechnic, Aurangabad Page 16

-At development site we create on registration form for practice

2- Developer will perform unit testing

3- Test application is checked in +ve scenario/way

2- Integration testing is perform by developer.

There are 3 ways of integration testing

M.I.T., Polytechnic, Aurangabad Page 17

SIT Environment (System integration testing)

Smoke testing checkpoints/Validation.

1- Validating the core functionality

M.I.T., Polytechnic, Aurangabad Page 18

Department: ________Enrollment No:_

Student Contact No._ Parent Contact No._

Name of Student Mentor: ________Contact No: