Developing Android health care app integration
Ahtola, Tomi (2022)
Ahtola, Tomi
2022
All rights reserved. This publication is copyrighted. You may download, display and print it for Your own personal use. Commercial use is prohibited.
Julkaisun pysyvä osoite on
https://urn.fi/URN:NBN:fi:amk-202204074709
https://urn.fi/URN:NBN:fi:amk-202204074709
Tiivistelmä
This thesis report covers the background of the commissioned thesis and the software
components that the project produced. The author will discuss and define the goals,
scope and objectives of the thesis project in the introduction chapter.
After introducing and establishing the project management, author discloses some
research and how it was applied in the product that the thesis project produced. This
was done by referring to the Android Developer technical reference manual. The author
also used an article as source and research material for writing unit tests how it was
used in this project.
After research had been concluded author discussed software development
methodologies and tools used in this project. The author also discussed how
methodologies were adapted in the commissioning party.
Implementation of the product that was created by this thesis project was presented
next. The author discusses how the implementation process started, how to achieve
what was required in the description of the mininum viable product. The research done
earlier is connected to the information and skills required in the implementation. The
author references a 3rd party source and project in a public code repository, assesses
its usefulness to this project and extracts necessary knowledge and utilizes it to create
software component.
Product chapter discusses code review that is required to maintain the integrity and
quality of the code commited to master repository of the product. The author had two
code reviews, that he got feedback from. Necessary suggested changes and feedback
were taken into account and the software components were commited to master
repository. The author also visualises functionality of the created software components
and its required behaviour.
Conclusions of the report discuss how the result of this project matches the
expectations, goals and objectives set in the introduction and planning phase of the
project. The author reflects on research, methodologies, tools, and practises and how
they were used in the project. He also discloses the latest status of the product in the
commissioning party, and how does its future look going in to the production
environment.
components that the project produced. The author will discuss and define the goals,
scope and objectives of the thesis project in the introduction chapter.
After introducing and establishing the project management, author discloses some
research and how it was applied in the product that the thesis project produced. This
was done by referring to the Android Developer technical reference manual. The author
also used an article as source and research material for writing unit tests how it was
used in this project.
After research had been concluded author discussed software development
methodologies and tools used in this project. The author also discussed how
methodologies were adapted in the commissioning party.
Implementation of the product that was created by this thesis project was presented
next. The author discusses how the implementation process started, how to achieve
what was required in the description of the mininum viable product. The research done
earlier is connected to the information and skills required in the implementation. The
author references a 3rd party source and project in a public code repository, assesses
its usefulness to this project and extracts necessary knowledge and utilizes it to create
software component.
Product chapter discusses code review that is required to maintain the integrity and
quality of the code commited to master repository of the product. The author had two
code reviews, that he got feedback from. Necessary suggested changes and feedback
were taken into account and the software components were commited to master
repository. The author also visualises functionality of the created software components
and its required behaviour.
Conclusions of the report discuss how the result of this project matches the
expectations, goals and objectives set in the introduction and planning phase of the
project. The author reflects on research, methodologies, tools, and practises and how
they were used in the project. He also discloses the latest status of the product in the
commissioning party, and how does its future look going in to the production
environment.