Application Development and Emerging Technologies, 2nd

Semester, 2025
Research Document Format (Research on Mobile
Applications)

Chapter I
Introduction

Background of the Study

- This part must include the full description of the app that will give the readers an
overview of what the mobile app is all about.
- This part should also include the reasons of the development of the app and the
researcher should also explain its importance.
- This part should likewise state the problems the app is trying to solve.

Sample format:

Background of the Study

The evolution of Technology nowadays increasingly gives higher impacts to

users all over the world. Computer Technology is the basic necessity in the modern
everyday life. It has made most of the daily activities easier faster and more
accurate. It is also used from communicating or even from the other sectors that
uses computer with internet connectivity, in which people can access anytime the
different websites like Facebook that most us or even children can access. It serves
us tool for communication across the globe. It simply makes the world smaller.
Websites are intended to provide rich information and quality service. It acts
as a connecting line between diverse individuals around the world. As an internet
tool, it is in itself diverse in many ways depending on the content that the website
provides. Having a computerized system in an organization makes the tasks easy,
because it will help to access data in a shorter period of time unlike the manual form
that can duplicate errors in the part of the concerns.
There is an urgent need for it at present since the numbers of Trainee/Job
seeker arise and the manual process of managing their profile is no longer being
practiced. This study aims to provide the organization and Trainee/jobseeker
convenience and quality management of data that would replace the manual
tracking and job placement.
Trainee Tracking and Job Placement Management System serves as an they
can record the Trainee/Job seeker data so that they can easily track them and
contact them if they are having a problems or need to update their profile and even
the employer have a data in the system.
Basic Information
- This part must contain the following app’s basic info:
a. Available Versions (android/ios version)
Our application is available in ….in 1 paragraph
b. Mainly Used Hardware Peripheral/s
In developing a application.. in 1 paragraph form

In using a application.. in 1 paragraph form

c. Mobile Application Development Approach (Native, Web or Hybrid)
in 1 paragraph form
d. Software Requirements (SDKs used, Computer OS details, etc.)
Each software requirements must be explain..
paragraph form
e. Programming Language Used(optional)
in 1 paragraph form
f. Compatibility Issues
In paragraph form list all the issues that you may encounter in
using your application

Scope and Limitation

Scope
• Emphasize all the functions of your application
• This part should state the features of the application
• The app’s scope must be listed in bullets form.
Limitation
• This part should state the app’s boundaries and constraints.
• The app’s limitation must be listed in bullets form.

Significance of the Application

- This part should clearly state the importance/ usefulness of the mobile app to
different specific groups/users (community, school, students/learners,
employees, gamers. bloggers etc.)

Sample format:

Trainee /Job seeker – this study will benefit them because they are the main
subject/center or beneficiary of this study the Trainee will store their data into a
system. And the job seeker can find a job opportunities it will save their efforts, time
and money. It will avoid from those who are scammer or fixers out there.

Definition of Terms
- This part defines the important terms all throughout the research document as
well as the terms that you think is unfamiliar with the readers. Examples: bugs,
rating, reviews, user interface, paper prototyping etc
 - The terms should be arranged alphabetically. You can define the terms as stated
in the dictionary but defining the terms according to how it was used in the study
(operational definition) is preferred.
- Don’t put a bullet

Sample format:

Definition of Terms

Trainee- a person who is learning and practicing the skills of a particular job.

Trainee Tracking System- is an online-based. application that helps to tracking of

Trainee. The project aims to improve current tracking procedure of El Nazareno and

providing Trainee and Job Seeker data to faculties.

Job Seeker - is an unemployed person who is trying to get a job.

Chapter II
Methodology
- Present the selected software development methodology, including an illustration to
provide a clear understanding of the framework being followed. Discuss each phase
of the methodology in detail, ensuring it aligns with the objectives and scope of the
project.
Use case
- Create a use case diagram that connected to the process of your application,

Sample format:
Chapter 2
METHODOLOGY

Software Development Methodology

Software development methodology is a process or series of processes used
in software development. Again, quite broad but that it is things like a design phase,
a development phase. It is ways of thinking about things like waterfall being a non
iterative kind of process. Generally it takes the form of defined phases. It is
designed to describe the how of the life cycle of a piece of software. (Ben Stickland,
2022)
In this RAD Methodology, this model is flexible in any change. It can adopt on
any change in the design if the client to change a part of the system. In each phase
of the RAD can bring the highest priority of the functionality to the costumer. It can
reduces the development time to finish the system perfectly. It increase the
reusability of the features so the testing period can be reduce.
 Figure 1 - Rapid Application Development

Phase 1. Requirements planning

In this phase requirement planning is more shortened and scaled down

compared to other project management mythologies, but here also can be seen the
complex steps to succeed the project.
Developers, users (software users), and group members interact to describe
the project's goals and expectations, as well as any present or potential difficulties
that must be resolved throughout the construction.
A basic breakdown of this stage involves:
• Researching the current problem
• Defining the requirements for the project
• Finalizing the requirements with each stakeholder’s approval
It is important that everyone has the opportunity to evaluate the goals and
expectations for the project. Groups can avoid miscommunications and costly
modification orders down the line by obtaining approval from each important
stakeholder and developer.

Phase 2. User design

Once the project is scoped out, it’s time to jump right into development,
building out the user design through various prototype iterations.
Unique is the right word to describe this phase because users are required to
collaborate with developers to make sure they met the needs in every step and
process of the project. Users said that each prototype need to be test for
confirmation that it will meet their expectations. Since the developer will be assign
to the design a prototype, so they can tell if it works or there is something they can
add and make.

Phase 3. Construction
Phase 3 takes the prototypes and beta systems from the design phase and
converts them into the working model.
In this phase, the majority of the problems and deviations were addressed
during the thorough iterative design phase. Developers can construct the final
 working model more quickly than they could by following a traditional project
management approach. The phase breaks down into several smaller steps:
• Preparation for rapid construction
• Program and application development
• Coding
• Unit, integration, and system testing
During this phase software development team of programmers, coders,
testers, and developers will need to sure everything and work on hand to the user
to ensure that they can met their expectations.
The construction phase is important it is because the user still gets to provide
input during the process. They can recommend alterations, changes, or even new
thoughts that can solve problems and complications as they arise.

Phase 4. Cutover
This phase is the implementation phase where the complete product goes to
launch. It contains testing, data conversion, and changeover to the new system, as
well as user training.
All final deviations are made while the users and coders will continue to find
for bugs in the system.

This use case diagram represents a Banking App, showing interactions between
the Customer and the Bank. The customer can perform various actions such as
logging in, checking balance, transferring funds, and making payments. The log in
process includes password verification and may extend to displaying a login error if
authentication fails. Both transferring funds and making payments require verifying
sufficient funds before proceeding. The Make Payment use case is further divided
into Pay from checking and Pay from savings, indicating different payment sources.
The Bank interacts with these use cases to process transactions and ensure
sufficient funds. The diagram uses "include" relationships for mandatory actions
 (e.g., verifying a password or funds) and "extend" relationships for optional
processes like displaying login errors. This structure ensures secure and efficient
banking operations while preventing unauthorized access and insufficient fund
transactions.

Chapter III
Discussion of Findings

- This will contain the screenshots of all the user interfaces of the app.
- The researcher must include the explanations

Sample Format:
Admin – their are the responsible in the system they can access all the features and
the admin will verify the data given by the students, etc…

• Login page – the admin has a login page…..

• Dashboard of the admin – this page indicate all the ….

Teacher – can simple registration and can update their profile online. Also they can
apply a specific subject…

• Sign up/ Log in – all the teacher…..

• Dashboard of teacher - …..

 Chapter IV
Recommendations

- These are worthy or acceptable and relevant suggestions that offer solution to
the problems/issues or the limitation of your application.

Paper Prototype

- Describe and Illustrate your recommendations by creating a sketch of user

interfaces of how your modifications will look like.

Sample Format:

Recommendation

In today's digital era, educational institutions are increasingly adopting

technology to enhance learning and assessment processes. Many schools and
universities now utilize online platforms such as Google Classroom and other Class
Assessment Management Applications to streamline tasks, improve efficiency, and
ensure a seamless learning experience. While some institutions have fully integrated
digital assessment tools, others still rely on manual methods, which can be time-
consuming and prone to inefficiencies.
To address this, we, the researchers, recommend implementing a Class
Assessment Management Application that will allow educators to efficiently manage
assessments, track student performance, and automate grading processes. This
system will help improve the overall quality of education by ensuring faster and
more accurate assessment results.
By implementing these recommendations, future developers and researchers can
contribute to the continuous improvement of Class Assessment Management
Applications, making digital learning more efficient, interactive, and effective.

To further enhance the application, we suggest the following features/functions for

better improvements:

Integrate a Live Assessment Feature – Enable real-time quizzes, exams, or

assignments with automated grading and feedback.
Enhance Google Classroom Integration – Ensure seamless synchronization of
assessments, scores, and feedback between the application and Google Classroom.

Improve Analytics and Reporting – Develop a comprehensive reporting module

that provides insights into student performance, strengths, and areas for
improvement.
Ensure Customization and Flexibility – Allow educators to customize
assessment formats, grading criteria, and feedback options to align with their
teaching methods.
Research Document Styling Requirements
Margins: One (1) inch on the bottom and the right, One and a half (1.5) inch on the
upper and left sides.
Font Size and Style : Font style is Times New Roman
Font size is 12.
Spacing: Double Space throughout the paper.
3 single space after the chapter numerical number and title.
Title: Chapter numerical number must be written in title case, centered. Example:
Chapter 1, Chapter 2 . .
Chapter title must be written in UPPERCASE, centered. Example: INTRODUCTION
Paragraph Alignment: Justified
Paragraph Indention: .5 inch from the margin or 1 tab.
Pagination: Page numbers appeared on the bottom of the paper, centered.
Paper Size: Letter Size, 8.5 x 11 inches
Note:
Active Voice: Active voice, third person must be used. For example, "The researcher
predicted that . .