0% found this document useful (0 votes)
33 views38 pages

Arti Itr

The document is an internship report on Android Application Development submitted by Arti Baburao Jadhav as part of the Diploma in Computer Engineering at New Satara College. It details the training undertaken at Techno-Wings Solutions Pvt. Ltd., including methodologies, tools used, and a weekly overview of activities related to Android development. The report also includes acknowledgments, an abstract about the company, and learning objectives for the internship.
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
33 views38 pages

Arti Itr

The document is an internship report on Android Application Development submitted by Arti Baburao Jadhav as part of the Diploma in Computer Engineering at New Satara College. It details the training undertaken at Techno-Wings Solutions Pvt. Ltd., including methodologies, tools used, and a weekly overview of activities related to Android development. The report also includes acknowledgments, an abstract about the company, and learning objectives for the internship.
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 38

INTERNSHIP REPORT ON

“Android Application development”

Submitted in partial fulfillment of the requirements of the award of


degree of
DIPLOMA ENGINEERING
In
Computer Engineering
BY:-

Arti Baburao Jadhav

UNDER THE GUIDANCE:

Mr. Sumit Umbare

(Techno-wings Solutions Pvt. Ltd.,Pune)


New Satara College of Engineering (POLY)

KORTI 2024-25

CERTIFICATE
The project report entitled

“Android Application Development”

Submitted by
Sr.N Name Enrollment No
o
1 Preeti Anand Damakale 2215230061
2 Sakshi Sharad Lokare 2215230064
3 Arti Baburao Jadhav 2215230067
4 Sanika Vinayak Gajare 2215230068

Is approved for the Diploma of Engineering in Computer from New Satara College
(POLY),Korti.

Name of Guide Name of Mentor


Techno-wings Solutions Pvt. Ltd. Department of Computer Engineering
Solapur-413001 New Satara College (POLY),Korti
. (Mr. Sumit Umbare) (Mr.S.B.Puri)

Name of H.O.D Name of Principle

Department of Computer Engineering


New Satara College (POLY),Korti. New Satara College (POLY),Korti
(Prof.S.B.Puri)
(Prof. V.H.Londhe)
.

Date:
Place: Korti Examiner Principal
Declaration by Candidate

I hereby declare that the Industrial Training based on “Android Application Development”
completed in Techno-wings Solutions Pvt. Ltd.,Solapur Submitted to Maharashtra State Board of
Technical Education (MSBTE),for Computer Engineering in New Satara College Of Engineering,
Korti the guidance of Mr. Sumit Umbare .

I further declare that it has not been submitted to any other university or institution for the
award of diploma. I also confirm that all the literature which I have borrowed from other source
and incorporated in seminar report is duly acknowledge. If any literature is not duly acknowledge
and found incorporated in this report, it entirely my responsibility

Date:
[Arti Baburao Jadhav ]
Place:korti
Certificate by Guide

This is to certify that Ms. Arti Baburao Jadhav has completed the Industrial Training
under my guidance and supervision and that, I have verified the work for its originality in
documentation, problem statement, implementation and results presented in the Industrial
Training. Any reproduction of other necessary work is with the prior permission and has given
due ownership and included in the references.

Place: Korti
Signature of Guide

Date:
(Mr. Sumit Umbare)
Contents:

Acknowledgement………………… I

Abstract…………………………… II

List of Figures…………………….. III

List of Tables………………………. IV

List of Abbreviations………………. V
ACKNOWLEDGEMENT

We take this opportunity to thank all the individuals for their guidance, help and timely
support which made us to complete the project in stipulated time. It gives us a great pleasure and
immense satisfaction to present this project report on “Android Application Development”
which is the result of unwavering support, guidance and focused direction of our guide Mr.
Sumit Umbare whom I express our deep sense of gratitude and humble thanks, for his valuable
guidance throughout the project work.

The success of this project has throughout depended upon an exact blend of hard work and
unending co-operation and guidance, extended to us by the superiors at our college.

Furthermore, we are indebted to Prof. Puri S.B H.O.D, Computer Engineering and Prof.
V.H. Londhe Principal whose constant encouragement and motivation inspired us to do our best.
Lastly,we offer my regard for all those, in particular our parents, who supported us in every
respect during this project

Arti Baburao Jadhav


ABSTRACT

The Company :

Techno-Wings is a complete IT Solutions & IT enabled Services Company for offering


services like Software Development & Consulting, IT Infrastructure Services, IT Training &
Services, Manpower recruitment & Outsourcing Consultancy Services are some of the major
working area of our company. Techno-Wings has evolved as an organization by continuously
adding value to the businesses of our clients by innovative use of Training & Technology. Today,
our operations have taken a flying shape to serve the industry verticals such as Educational
Industry (Institutions, Schools & Colleges), Retail Industry, Manufacturing Industry, Healthcare
Industry, and Financial Services & Government Sectors with a business solution.

• Programmers and opportunities:

INPLANT TRAINING IN Techno-wings - WHY IT’S IMPORTANT?

The term, Inplant Training in Techno-wings -> Inplant training is really important to gain
knowledge of real time technologies and to get job. Techno-wings Inplant Training focus towards
latest job oriented technologies and improve interview related aspects. The breadth of
Engineering may be best understood in terms of the general areas of software systems, hardware,
theory and applications. Now a days it has been significant improvement in the usability and
efficiency of computing technology.

• Methodology:
This project is to provide information about students to any person or parents. In these project
we can insert new students data and store it to database and whenever we need we can fetch the
data of student from database. Also in these project we can update and delete the particular
student data from database.

• Benefits to the company / institution through your report:


The Institute combines pioneering research with top class education. An innovative
curriculum allows the student flexibility in selecting courses and projects. Students, even at the
undergraduate level, get to participate in on-going research and technology development - an
opportunity unprecedented in India.
WEEKLY OVERVIEW OF INTERNSHIP ACTIVITIES

DATE DAY ACTIVITIES CARRIED OUT

Introduction to Android, Introduction to Open


03/06/24 Monday
Handset Alliance, Android Ecosystem.

Need of Android, Features of Android,


04/06/24 Tuesday
Android Version.

Introduction to Tools and software required


05/06/24 Wednesday
for developing an Android application.

Android Architecture, Significance of


06/06/24 Thursday
components in Android Architecture.

Operating system, Java JDK, Android SDK.


07/06/24 Friday

08/06/24 Saturday Introduction to Android development Tools


(ADT’s) and Android Virtual Devices
(AVDS).
DATE DAY ACTIVITIES CARRIED OUT

Text View , Edit Text Button , Image Button ,


10/06/24 Monday
Toggle button , Radio Button and Group
Methods and Atrributes.

Introduced to the Dalvik Virtual Machine,


11/06/24 Tuesday
Configured the Android Development Tools
(ADT) plug-i, Created an Android Virtual
Device.

Explored the differences between JVM and


12/06/24 Wednesday
DVM, Developed a program to display “Hello
World” on the screen.

Studied the control flow of Android,


13/06/24 Thursday
Examined the directory structure in detail,
Introduced the fundamentals of UI Design,
including View,
View Group, and Activity.

Introduced Linear Layout, Absolute Layout,


14/06/24 Friday
and Constraint Layout. Developed a program
to implement Linear Layout and Absolute
Layout.

Introduced Frame Layout, Table Layout, and


15/06/24 Saturday
Relative Layout. Developed a program to
implement Frame Layout, Table Layout, and
Relative Layout.
DATE DAY ACTIVITIES CARRIED OUT

17/06/24 Studied and implemented ProgressBar and


Monday
ProgressDialog. Developed a ProgressBar
using a thread. Created registration and login
pages.

Learned about ListView and successfully


18/06/24 Tuesday implemented it. Gained knowledge of
GridView and ImageView and implemented
both.

Wednesday Explored ScrollView and implemented it.


19/06/24
Added validation to the login and registration
pages. Learned about Toast and created a
custom Toast.

Learned about TimePickerDialog and


20/06/24 Thursday
DatePickerDialog and implemented both.

Gained an understanding of Android


21/06/24 Friday components. Studied Intents and Intent Filters
and implemented them with all their attributes.

Explored the Activity and Activity Life Cycle.


22/06/24 Saturday
Successfully implemented the Activity Life
Cycle.
ACTIVITIES CARRIED OUT
DATE DAY

Explored the Broadcast Lifecycle, including


24/06/24 Monday
BroadcastReceivers, System Broadcasts, and
Broadcasting Custom Intents.

Studied Services in Android, covering the


25/06/24 Tuesday Features of Service, Android Platform
Services, Defining New Services, the Service
Lifecycle, Permissions, and examples of
services.

Learned about Android System Architecture,


Wednesday the Multimedia Framework, and how to play
26/06/24
audio and video using Multimedia API

Investigated Text-to-Speech functionality and


27/06/24 Thursday
captured video and images using the camera.
Also learned how to capture audio.

Introduced to Bluetooth, including turning


28/06/24 Friday
Bluetooth on and off, and getting the names
of bonded devices.

Reviewed DBMS concepts, including what


29/06/24 Saturday RDBMS is, and revised basic concepts of
DBMS.
DATE DAY ACTIVITIES CARRIED OUT

Explored SQLite Database, the necessity of


01/07/24 Monday SQLite creation, and the connection of the
database. Learned about the use of the
SQLiteOpenHelper class and SQLite class.

Extracted values from a cursor and


02/07/24 Tuesday
displayed them in the GUI using ListView
and GridView. Studied Transactions.

03/07/24 Introduced to Content Provider, including


Wednesday
the ContentProvider class with all its
methods, the ContentResolver class, and
the CursorLoader class.

Learned about SMS Telephony, including


04/07/24 Thursday an introduction to the SMS API,
SmsManager class, and SmsMessage class
with all their methods. Practiced sending
SMS using Intent.

05/07/24 Friday Sent SMS using the API and received SMS
using a Broadcast Receiver. Displayed the
received message in the application.

Introduced to Location-Based Services.


06/07/24 Saturday
Created a Map Project and displayed the
map using Intent.
DATE DAY ACTIVITIES CARRIED OUT

Worked on Location-Based Services. Created


08/07/24 Monday
a project, obtained the Maps API key,
displayed the map, and displayed the zoom
control.

Navigated to a specific location, navigated to


09/07/24 Tuesday
the current location, and added a marker at the
current location.

Obtained location data, performed geocoding


10/07/24 Wednesday and reverse geocoding, introduced the
Geocoder classes, and monitored the location.

11/07/24 Studied the Android security model, declared


Thursday
and used permissions, explored types of
permissions, and used custom permissions.

Learned about application deployment.


12/07/24 Friday
Created a small application, signed the
application, and deployed the app on the
Google Play Store.

13/07/24 Saturday Learned how to become a publisher. Explored


the Developer Console and its features.
INDEX

1. Structure Of Industry

2. Introduction to Organization

2.1 Types, Services

2.2 Number Of Employees

3. Equipments Used

4. Process Of Development

4.1 Planning and Control Methods

5. Testing

6. Safety Products

7. Maintenance

8. Project In Training

9. Conclusion
Learning Objectives/Internship Objectives

➢ Internships are generally thought of to be reserved for college students looking to gain
experience in a particular field. However, a wide array of people can benefit from Training
Internships in order to receive real world experience and develop their skills.

➢ An objective for this position should emphasize the skills you already possess in the area
and your interest in learning more

➢ Internships are utilized in a number of different career fields, including


architecture, engineering, healthcare, economics, advertising and many more.

➢ Some internship is used to allow individuals to perform scientific research while others
are specifically designed to allow people to gain first-hand experience working.

➢ Utilizing internships is a great way to build your resume and develop skills that can be
emphasized in our resume for future jobs. When you are applying for a Training
Internship, make sure to highlight any special skills or talents that can make you stand
apart from the rest of the applicants so that you have an improved chance of landing the
position.
1. INTRODUCTION

Techno-Wings is a complete IT Solutions & IT enabled Services Company for offering


services like Software Development & Consulting, IT Infrastructure Services, IT Training &
Services, Manpower recruitment & Outsourcing Consultancy Services are some of the major
working area of our company. Techno-Wings has evolved as an organization by continuously
adding value to the businesses of our clients by innovative use of Training & Technology. Today,
our operations have taken a flying shape to serve the industry verticals such as Educational
Industry (Institutions, Schools & Colleges), Retail Industry, Manufacturing Industry, Healthcare
Industry, and Financial Services & Government Sectors with a business solution.

Our Vision:

Our Vision is to help the Customers with the latest Technologies & Training so become the
preferred choice to be the business Partner

Our Mission:

Our Mission is to “Help the Customers to Build the Business”.


Chapter 2

Introduction To Organization

Techno-Wings is not an entity, it’s a family that represents togetherness for over two
decades of a successful journey. For Techno-Wings, the definition of success is to transcend
innovative ideas of people to reality with the help of our tech expertise , this is what we, as a
Team, want to be remembered for!
Our vision has led Techno-Wings to become a top IT company in Worldwide for delivering
various industry-led mobility solutions. The goal is to empower clients and businesses by
creating new possibilities leveraging the technologies of today and tomorrow with the utmost
quality, satisfaction, and transparency.

Our enthusiasm has led us to become a top IT company in Worldwide for delivering
various industry-led mobility solutions in web and mobile application development domains
leveraging futuristic technologies like Internet of Things (IOT), AI-ML, AR-VR, Voice assistants
and Voice Skills, DevOps & Cloud computing, etc. We feel empowered with our certified tech
experts and our R&D team who have always challenged themselves to help global clientele with
a plethora of IT services and solutions. Engagement with our team guarantees our clients to save
huge money on project development with faster delivery.
Chapter 3

Equipment’s Used

• Traditional Methodologies o

The Waterfall Model

o The Critical Path Method o

The Critical Chain Method

• Agile Methodologies

o Agile Project Management

o The Scrum Framework

o Kanban

o Extreme Programming

o Adaptive Project Framework

• Change Management Methodologies

o Event Chain Methodology

o Extreme Project Management

• Other Methodologies

o Rational Unified Process

o Program Evaluation & Review Technique

o The PMBOK Method

• Project Management Tools


.Recruitment life cycle diagram:
Chapter 4

Process Of Development

The Waterfall Model

The Waterfall approach suggests a sequential approach to managing projects. After stakeholders
and customers agree on and document project requirements, it’s executed in a step-by-step
manner until it’s finished. After that, the customer reviews the project to make sure that it
meets the requirements. Some projects require a post-production maintenance stage, e.g.,
software projects, where the customer reports bugs and requests new features to ensure lasting
project performance and success.

The most commonly preferred tool for the Waterfall model is the Gantt chart which
visualizes subtasks,dependencies and project phases as it goes through the project life cycle.

Best for: short and simple projects with clear guidelines that require a strict work structure to
ensure project success
.
 Requirement Gathering and analysis –

All possible requirements of the system to be developed are captured in this phase and
documented in a requirement specification document.
• System Design − The requirement specifications from first phase are studied in this phase and
the system design is prepared. This system design helps in specifying hardware and system
requirements and helps in defining the overall system architecture.
• Implementation − With inputs from the system design, the system is first developed in small
programs called units, which are integrated in the next phase. Each unit is developed and
tested for its functionality, which is referred to as Unit Testing.
• Integration and Testing − All the units developed in the implementation phase are integrated into
a system after testing of each unit. Post integration the entire system is tested for any faults and
failures.

• Deployment of system − Once the functional and non-functional testing is done; the product
is deployed in the customer environment or released into the market.
• Maintenance − There are some issues which come up in the client environment. To fix those
issues, patches are released. Also to enhance the product some better versions are released.
Maintenance is done to deliver these changes in the customer environment.
Chapter 5

Testing

There are different methods that can be used for software testing. This chapter briefly describes
the methods available.

Black-Box Testing

The technique of testing without having any knowledge of the interior workings of the
application is called black-box testing. The tester is oblivious to the system architecture and does
not have access to the source code. Typically, while performing a black-box test, a tester will
interact with the system's user interface by providing inputs and examining outputs without
knowing how and where the inputs are worked upon.

The following table lists the advantages and disadvantages of black-box testing.

Advantages Disadvantages

Well suited and efficient for large code segments. Limited coverage, since only a selected number
of test scenarios is actually performed.

Code access is not required. Inefficient testing, due to the fact that the tester
only has limited knowledge about an
application.

Clearly separates user's perspective from the Blind coverage, since the tester cannot target
developer's perspective through visibly defined roles. specific code segments or errorprone areas.

Large numbers of moderately skilled testers can test the The test cases are difficult to design.
application with no knowledge of implementation,
programming language, or operating systems.

White-Box Testing

White-box testing is the detailed investigation of internal logic and structure of the code.
White-box testing is also called glass testing or open-box testing. In order to perform white-box
testing on an application, a tester needs to know the internal workings of the code.

The tester needs to have a look inside the source code and find out which unit/chunk of the code
is behaving inappropriately.

The following table lists the advantages and disadvantages of white-box testing.
Advantages Disadvantages

As the tester has knowledge of the source code, it Due to the fact that a skilled tester is needed to
becomes very easy to find out which type of data can perform white-box testing, the costs are
help in testing the application effectively. increased.
It helps in optimizing the code It helps in optimizing
the code. Sometimes it is impossible to look into every
may create problems, as many paths will go
untested.
Extra lines of code can be removed which can bring in It is difficult to maintain white-box testing, as it
hidden defects. requires specialized tools like code analyzers
and debugging tools.

Black-Box Testing White-Box Testing


The internal workings of an application need not be Tester has full knowledge of the internal
known. workings of the application.
Also known as closed-box testing, data-driven Also known as clear-box testing, structural
testing, or functional testing. testing, or code-based testing.
Performed by end-users and also by testers and Normally done by testers and developers.
developers.

Testing is based on external expectations - Internal Internal workings are fully known and the
behavior of the application is unknown. tester can design test data accordingly.
It is exhaustive and the least time-consuming. The most exhaustive and time-consuming
type of testing.

Not suited for algorithm testing. Suited for algorithm testing.


This can only be done by trial-and-error method. Data domains and internal boundaries can be
better tested.
Chapter 6

Safety Products

SAFETY CASE ARCHITECTURES AND NEGATIVE REQUIREMENTS

The previous section describes how software to software techniques can be used in
conjunction with software to system techniques in order to identify unwanted software behaviour.
However, it is sometimes the case that the software is not amenable to sufficiently rigorous
examination that would allow us to claim that all unwanted behaviour have been identified [7].
Safety arguments, therefore, have typically considered the absence of specified behaviour only.
For example, software FMEA [10] can demonstrate that certain defined software failures do not
contribute unacceptably to system safety. However, such safety arguments do not always justify
the omission of other software failures from the analysis, and as a result can sometimes be
judged insufficiently complete. The concept of well-behaviourness [3] enables us to address this
incompleteness problem. Well-behaviourness of software in a SoS refers to the general integrity
[5] of that software’s behaviours: in essence, well-behaviourness is a requirement that certain
categories of undesirable behaviour should not occur. Examples of well-behaviourness
requirements include those relating to non-interference between components, the absence of
unintended communications between components, absence of data corruption across
communication paths, and absence of resource starvation. A single well- behaviourness
requirement can therefore be seen as an abstraction away from specific undesirable behaviours to
describe an entire class of unwanted behaviour. For example, instead of arguing about the
absence of all possible behaviours resulting from corruption of some specified communication
data between two specified components, we can simply argue the well-behaviourness property
that the components and methods responsible for communication within a SoS do not corrupt
(any) data.
Chapter 7

Software Maintenance

What is Software Maintenance?

Software maintenance is the process of changing, modifying, and updating software to keep
up with customer needs. Software maintenance is done after the product has launched for several
reasons including improving the software overall, correcting issues or bugs, to boost
performance, and more.
Software maintenance is a natural part of SDLC (software development life cycle). Software
developers don’t have the luxury of launching a product and letting it run, they constantly need to
be on the lookout to both correct and improve their software to remain competitive and relevant.
Using the right software maintenance techniques and strategies is a critical part of keeping any
software running for a long period of time and keeping customers and users happy.

Why is software maintenance important?

Creating a new piece of software and launching it into the world is an exciting step for any
company. A lot goes into creating your software and its launch including the actual building and
coding, licensing models, marketing, and more. However, any great piece of software must be
able to adapt to the times. This means monitoring and maintaining properly. As technology is
changing at the speed of light, software must keep up with the market changes and demands.

What are the 4 types of software maintenance?

The four different types of software maintenance are each performed for different reasons and
purposes. A given piece of software may have to undergo one, two, or all types of maintenance
throughout its lifespan.

The four types are:

i. Corrective Software Maintenance


ii. Preventative Software Maintenance
iii. Perfective Software Maintenance
iv. Adaptive Software Maintenance
Corrective Software Maintenance

Corrective software maintenance is the typical, classic form of maintenance (for software and
anything else for that matter). Corrective software maintenance is necessary when something
goes wrong in a piece of software including faults and errors. These can have a widespread
impact on the functionality of the software in general and therefore must be addressed as quickly
as possible.

Many times, software vendors can address issues that require corrective maintenance due to bug
reports that users send in. If a company can recognize and take care of faults before users
discover them, this is an added advantage that will make your company seem more reputable and
reliable (no one likes an error message after all).

Preventative Software Maintenance

Preventative software maintenance is looking into the future so that your software can keep
working as desired for as long as possible. This includes making necessary changes, upgrades,
adaptations and more. Preventative software maintenance may address small issues which at the
given time may lack significance but may turn into larger problems in the future. These are called
latent faults which need to be detected and corrected to make sure that they won’t turn into
effective faults.

Perfective Software Maintenance

As with any product on the market, once the software is released to the public, new issues and
ideas come to the surface. Users may see the need for new features or requirements that they
would like to see in the software to make it the best tool available for their needs. This is when
perfective software maintenance comes into play.

Perfective software maintenance aims to adjust software by adding new features as necessary and
removing features that are irrelevant or not effective in the given software. This process keeps
software relevant as the market, and user needs, change.
Adaptive Software Maintenance

Adaptive software maintenance has to do with the changing technologies as well as policies
and rules regarding your software. These include operating system changes, cloud storage,
hardware, etc. When these changes are performed, your software must adapt in order to properly
meet new requirements and continue to run well.
Chapter 8

Project In Training

In these Android project I have developed that application for calculating the age of
person.

Code
Java file:
MainActivity.java:
Output:
Chapter 9

Conclusion:

The Age Calculator application is a well-designed tool that offers users a simple yet
effective way to calculate their age or the age of a person based on given dates. With its modern
UI layout and efficient use of Android’s UI components, it provides a practical solution with a
user-friendly interface. Future enhancements could include additional features such as handling
different time zones or integrating with calendar APIs for more robust date handling.

References:

https://chatgpt.com/
https://www.geeksforgeeks.org/

You might also like