Affiliated to Pokhara University

POKHARA ENGINEERING COLLEGE

Phirke, Pokhara-8

A
Project Proposal on
Android Application

Submitted By:
Sagar Acharya (15070285)
Saroj Tamang (15070286)
Sujan Gurung(15070292)
Tshering Tamang (15070294)

Submitted To:
Research & Development,
Pokhara Engineering College
 Approval Certificate

The project entitled “HIMALAYAN” is proposed by the students. Sagar

Acharya, Saroj Tamang, Sujan Gurung and Tshering Tamang of Computer
faculty, Pokhara Engineering College, under the department of Computer
Engineering have been submitted as per the content, style and format
proposed by the R&D.

________________________
Chief Research and Development
Pokhara Engineering College
HIMALAYAN

Executive Summary

HIMALAYAN is a gym record and membership management system where

gym owner can keep records of members, their memberships, and have quick
and easy communication between him/her and the members. It provides
functions such as data entry of member, keep record of membership and notify
on termination of one’s membership. It also provides functions for the gym
owner to inform members on important announcements and for the members to
ask their concerns and discuss with gym owner.

Background

Keeping record in a hardcopy/paper is such a hassel and with having to go

through each record of a very long list is a total headache. Our software allows
the gym owner to store record on his/her phone and present him/her with the
outcome, with all work described by him/her done within the system therefore
making his/her work simple.
Project Objectives

Although all of the objectives can’t be defined at the starting of the project,
the objectives of our project are:

 The main objective of the project is to develop software that facilitates the data
storage, data maintenance and its retrieval for the gym in an igneous way.

 To store the record of the members.

 Also, only the administrator has the privilege to access any database and make
the required changes, if necessary.

 To develop easy-to-use software which handles the member-administrator

relationship in an effective manner.

 To develop a user friendly system that requires minimal user training. Most of
the features and function are similar to those on any windows platform.
 Feasibility Study

The necessary tools for the construction of our app are as follows:

Language: Java, JavaScript, PHP, MYSQL

IDE: Android Studio, Sublime text

For every project, UI plays an important role. Our interests are attracted
by those things that do the work and are flashy with many eye-catching
layouts. The integration of the database available on the server plays
an important role too. So everything should be sensitively handled.
 Limitations

Some limitations of this project are:

 App usage must be compulsory to all member to get notifications.

Risks

Some of the risks that we must account for while the project is under way are:

 The hard drive containing the project code and documentation crashes
(Can be mitigated by keeping multiple backups of all code
and documentation)
 One of the team members falls ill and cannot work (Can be mitigated by
constantly informing each other of what the other is doing, so he may take
over the other’s work until the ill team member has recovered).

In order to minimize risks and the delays in project development that they
May cause, the project team will meet regularly discuss any issues
that may arise. This will allow us to plan ahead and mitigate risks before
they occur.
 Project Schedule

The project is expected to run for approximately three months. This includes
writing up of the reports along with the completion of the project. The following
table shows all the deliverables for this project based on the planned
timeline:

TIMELINE CHART
20-Aug 27-Aug 6-Sep 16-Sep 26-Sep 6-Oct 16-Oct 26-Oct 26-Nov

Planning

Research and Analysis

Design

Start Date
Implementation
Days to Complete

Testing

Deployment

Follow-up

Conclusion

The project we purposed, seems tobe of great usages in present context. Further
modifications and additional features can be implemented later. Through the
development of this project, we hope to gain more knowledge and experience on
the field of android app development.
Methodoloy

Current methodologies for developing mobile applications are mostly based on the

application programming interfaces (APIs) offered by the native platform. Hence, most
solutions are characterized by a low portability or reusability. In this paper, we propose a
novel methodology based on a declarative and device-independent approach for developing
event-driven mobile applications.

Requirement Analysis

First of all we studied the necessary equipments for making our plan successful. We used Software
called Android studio and different java platforms to support it. We learned coding, java language,
database management through PHP. Consulting our teachers and our seniors we managed to go
through all this.

Designing
We took a strategy to go ahead with work on designing and tried to prepare a design that
delivers the best user experience. Test it on different devices. Ensure smooth navigation on
the Mobile App.

Coding
While working on designing, Start implementing back-end Processes. Deploy each
functionality one by one and keep testing it. The coding part was the most difficult one.
It was the hardest part of all. It took longer and harder than we expected.

Testing and Modifications

We tested the functionalities and make necessary changes. Asked dummy users to use the
app and make necessary changes according to their inputs.
Launching

The end result is that one team efficiently develops a feature from end to end rather than
four teams duplicating efforts. It certainly sounds more like common sense than it does a
revolutionary idea, but sometimes common sense gets pushed aside in the frenzy of rushing
mobile products to market.