Day 0: Define the Vision

The client wants a system for geocaching where he could track all the
information he has about his caches. It is basically a logbook system where
the items are stored and has information about it. Additionally, the system
also tracks his activities such as the location, date of the activity and his
findings. This system given the information will be only his and not
presumably to be use other users. Thus, the design of the system will be
based on the client’s need. Since the goal is to keep tracking on his
geocaching, it is best that the system will be a web-based wherein the
system can be access in devices such as computer, laptop, and mobile
devices.

Day 1: Plan the Project

Task 1-1
The System is divided into two sub-systems that meet the fundamental
needs of the client.
Tracker
This system using a mobile device will keep him track which allows the user
to keep track on where his location is. It tells the user his coordinates and
map. The coordinates will be based on the mobile device using the Global
Positioning System. The system also logs what the user finds by logging the
cache on the same device using the second sub-system. In that way, the
map of the sub system will mark the items on where he finds the cache, the
date, location and the information about the cache, which will be fetched
from the storage from the logbook system.
Logbook system
The purpose of the logbook system is simple; store, update, delete, and
display. Think of it as something of logbook where you can log your activity in
certain activities like attending a meeting, but the information can be
modified, or deleted. The user will have control of the information he finds.
Additionally, it can provide the location and map to tell the location although
the exact position of the cache based on the coordinates will be given is the
challenge intended for the treasurer hunter.
Task 1-2: Work breakdown structure

Day 2
Task 2-1
Logbook System
- Store / Add
The system will store the user’s finds and store it on storage of the
system for it to be use later such as to modify the information, delete
the information it was logged or display the information for further use.
- Modify
The user can modify the information to update his finds if there are any
changes to his activities.
- Delete
If the user wants to delete the information or his finds, he can.
- Display
These features allow the user to view the information as well as
provide visual aids such as mapping of the location of his finds.

Task 2-2
The main goal of the system is to keep track on the users geocaching
activities. But what are those activities; his finds, location, date and
additional information such as journal. So the system will be focusing on
tracking his activities by these following classes:
 - View
The information can be display
- Track
Track the user’s activity; based on the log or his current location
- Store
Store his finds (cache) to track on his activities

Task 2-3

Task 2-4
Day 3 : Define the User Experience
Task 3-1
Use Case: Logging a Geocaching Activity
Step 1: User Authentication – the user logs into the geocaching system using their
username and password.
Step 2: User Dashboard - after successful authentication, the user lands on their
dashboard, where they can access various geocaching-related options.
Step 3: Initiate Activity Log - the user selects the option to "Log Geocaching
Activity" from their dashboard.
Step 4: Select Geocache - the system presents the user with a search or selection
interface where they can search for the geocache they want to log in. The user can
search by geocache name, location, or other criteria.
Step 5: Choose Geocache – the user selects the specific geocache they want to log
from the search results.
Step 6: Record Activity Details – the system provides a form for the user to record
details of their geocaching activity, including the date of the venture and notes
about their geocaching experience. They can also add optional details like photos or
ratings
. Step 7: Submit Activity Log – the user reviews the documented information. If the
records are precise to his details, the user submits the activity log for the selected
geocache.
Step 8: Confirmation – the system confirms the successful submission of the
activity log. The user may receive a notification that their geocaching activity has
been recognized.
Step 9: Update Activity History – the system updates the user's geocaching activity
history to reflect the newly logged activity. This includes updating statistics, such as
the total number of geocaches found and any achievements or milestones.

Task: 3 –2 - Workflow Diagram

Task 3 –3 : Screen Sketch
Task 4 – 1

Task 4 – 2
Browser Based System

Pros:

- Works on Any Device: A web-based app can run on any device with a web
browser, so it’s easy for more people to use it without worrying about what
kind of computer or phone they have.
- Easy to Keep Updated: Since updates are made on the server, everyone
automatically gets the latest version without having to do anything.
- Access Anywhere: You can use the system from anywhere with an internet
connection, making it convenient and flexible.

Cons:

- Needs Internet: The app won’t work without a reliable internet connection,
which can be a problem in remote areas where people might go geocaching.
- May Run Slower: Web apps might not perform as well as desktop apps
when it comes to complex tasks or heavy data processing.
- Security Risks: Because it’s online, a web app could be more vulnerable to
security threats, so strong security measures are necessary.

Given that geocaching is a community activity where accessibility and

convenience are key, a web-based system is the better option. Eros and
others will be able to log their geocaching activities from any device, and
updates to the system can be done easily without needing to install anything
new. Even though it requires an internet connection, the benefits of being
able to access it anywhere make it the smarter choice.

Day 5: Develop the Detailed Design and

Program System
Task 5-1
Considering the development of Eros's geocaching logbook system,
JavaScript initially presents itself as a strong choice, due to its versatility in
building dynamic, interactive web applications. With frameworks like Node.js
and Express.js, JavaScript allows for full-stack development using a single
language, which can be advantageous for creating a seamless user
experience across devices.
However, if we assume that Eros would prefer quick development and easy
maintenance, Python emerges as a much better choice. Python's
straightforward syntax and robust frameworks like Django enable faster
development with built-in tools and a clean project structure. This not only
accelerates the development process but also ensures that the system
remains easy to maintain.
We also recommend Visual Studio Code for Eros because of it being a
lightweight, versatile development environment that also boasts about its
capability in debugging and code formatting. It also supports a variety of
programming languages such as Python and can be convenient to add other
extensions for the system’s overall development.

Day 6: Test and Deploy the System

Task 6-1
Programmer Testing involves the internal part of a system, where developers
conduct tests to identify certain code functions and fix bugs. It ensures the
system’s components are well within the specified requirements and
expected functions. However, there can always be cases where a
programmer overlooked a part of the code that may significantly affect the
function and performance of the system and still proceeds to release the
system. User Testing comes into place as “customers” and do tasks to
validate whether the system meets the user’s expectation on usability,
effectiveness, and convenience. As for Eros’ system, the people involved in
this User Testing are those outside the development team, which are regular
citizens who love to travel and log their journey.

Task 6-2
The deployment process for web-based systems ultimately requires various
issues from a technological standpoint. Let’s say Eros’ system may be
successfully deployed in a certain browser and system, however, users that
are on a different browser may encounter compatibility issues. Developers
must ensure that they have tested the system not just in various browsers,
but also in different devices. Like any web-based application, it could be
targeted by malicious attacks. If the system's database queries are not
properly secured, attackers might be able to manipulate or access sensitive
data by injecting malicious SQL code. Sensitive data related to activities,
such as location details and personal findings, could be at risk if the system
is not secured properly. For the user’s end, they may also encounter
difficulties on the system if they are not used to the interface and how the
system would work on their interaction. User Feedback would be very much
appreciated because it additionally offers recently found issues that has
been overlooked on both Programmer and User Testing. These are just some
of the deployment issues that are being encountered, however, as
developers continue to cooperate with user feedback, these issues will
eventually get resolved, and make the system prepared for usage.

Task 6-3
In addition to the issues on the above task, other issues such as website
uptime and financial protection have come to our concern. Developers must
ensure that they use a reliable host provider to prevent server failures and
always be accessible to the users. Unexpected spike in network traffic has
also been one of the downsides in web-based systems, which happens if the
system’s capacity is being overwhelmed by heavy loads of users attempting
to access the system at the same time. Moreover, a system that also
integrates an online merchandise feature would also need to manage
financial transactions accurately and more importantly, secure. An
Automated error handler would also prove to be effective because it
immediately responds to solve a certain issue without a developer needing
to find and manage the system all the time. Addressing these kinds of issues
is crucial to the deployment process of the system to prevent errors and
ensure a smooth customer experience.