Professional Documents
Culture Documents
Industry Training Diary-1
Industry Training Diary-1
G.S. Mandal’s
Name of Student:_________________________________________________________
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.
“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.
Details of Industry/Organization
• Address: ______________________________________________________
______________________________________________________
o Name: ______________________________________________________ o
Number: ______________________________________________________
Semi- Government/PSU/Private
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:
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)
Day 3: Date:
Team Lead
Day: 4 Date:
Factors
Day: 5 Date:
b- Waterfall model
c- V- model
4-
Coding/ development
5-
Testing
6-
Maintenance/ Support
Day: 6 Date:
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:
Functional requirement
Eg. Signup – ( Requirement – First name, middle name, last name, mobile number, mail id,
password , submit button)
Screenshot / snapshot
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.
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 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: 14 Date:
Day: 15 Date:
Day: 16 Date:
Day: 17 Date:
Day: 18 Date:
Day : 19 Date:
Dev Environment
Unit testing
1- Testing which will be performed on individual module is called as unit testing.
Integration Testing
1- The testing perform on main module by combining various sub module is
called
integration testing.
Day: 20 Date:
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.
In this testing we are going to verify all the basic functionalities are working
SANITY 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:
1- Behavioural coverage/testing.
2- Input domain coverage/testing.
3- Error handling coverage/testing.
4- Backend coverage/testing
Day: 24 Date:
Day : 25 Date:
Day: 26 Date:
Alpha testing
In alpha testing client is involved.
Day : 27 Date:
Day: 28 Date:
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.
______________________________________________________________________________________
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
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
Day : 31 Date:
Day: 32 Date:
On Going project record and code is store in following repository for easily available
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.
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:
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:
______________________________________________________________________________________
Mentor H.O.D
(22049) in _____________________________________________________________
from________________ to ________________.
We found him/her sincere during training period. We wish all the very best for his/her
future endeavors.
Seal of
Industry
TRAINING CALENDAR: