Download as docx, pdf, or txt
Download as docx, pdf, or txt
You are on page 1of 6

System Vision Document - Rough Draft

Title: Geocaching Outing Tracker

1. Introduction

The Geocaching Outing Tracker is a software system designed to assist Wayne Johansen in managing and
tracking his geocaching activities. The system aims to provide Wayne with a comprehensive tool to plan,
record, and analyze his geocaching outings. It will offer features that enhance his overall geocaching
experience and make it more convenient for him to engage in this hobby.

2. System Objectives

The Geocaching Outing Tracker will serve the following objectives:

2.1 Efficient Outing Planning

The system will enable Wayne to plan his geocaching outings by allowing him to search for geocaches
based on location, difficulty level, and other criteria. It will provide detailed information about each
geocache, including coordinates, description, and hints, to assist Wayne in choosing suitable caches for
his outings.

2.2 Real-time GPS Tracking

The system will leverage Wayne's handheld GPS device to track his movements during geocaching
outings. It will display his current location, route, and distance covered, helping him navigate to the
designated geocaches accurately.

2.3 Geocache Logging and Management

Wayne will be able to log his geocache finds directly within the system, recording important details such
as date, time, geocache ID, and personal notes. The system will maintain a logbook of Wayne's
geocaching achievements, allowing him to easily review his past finds.

2.4 Custom Geocache Creation

The system will enable Wayne to create his own geocaches and share them with the geocaching
community. He will be able to specify the coordinates, write descriptions, and set difficulty levels and
hints for others to solve. The system will assist Wayne in managing and monitoring the activity on his
created geocaches.

2.5 Statistical Analysis and Reporting

The system will provide Wayne with statistical insights and reports based on his geocaching activities. It
will generate summaries of his finds, including the number of caches found, average difficulty ratings,
distances traveled, and other relevant metrics. These reports will help Wayne track his progress and set
personal goals.

3. Benefits to Wayne

The Geocaching Outing Tracker will bring numerous benefits to Wayne:

3.1 Enhanced Planning and Exploration

With the system's search and filtering capabilities, Wayne will be able to discover geocaches tailored to
his preferences, making each outing more exciting and rewarding. He can explore new locations and
challenge himself with caches of varying difficulty levels.

3.2 Streamlined Recording and Organization

The system will simplify the process of logging geocache finds, eliminating the need for manual record-
keeping. Wayne can conveniently access his geocache history, review his accomplishments, and
reminisce about past adventures.

3.3 Community Engagement and Contribution

By creating and sharing his own geocaches, Wayne can actively contribute to the geocaching community.
The system will facilitate interactions with fellow geocachers, allowing Wayne to receive feedback and
engage in discussions related to his created caches.

3.4 Progress Tracking and Motivation

The system's statistical analysis and reporting features will enable Wayne to track his geocaching
progress and set personal milestones. By visualizing his achievements and improvement over time,
Wayne will stay motivated and continuously strive for new geocaching goals.

4. Conclusion
The Geocaching Outing Tracker aims to provide Wayne Johansen with a comprehensive solution for
managing his geocaching activities. By facilitating efficient planning, real-time tracking, geocache logging,
custom geocache creation, and statistical analysis, the system will enhance Wayne's geocaching
experience and enable him to fully immerse himself in this exciting hobby.

Note: This is a rough draft of the System Vision Document, which will be refined and revised throughout
the

development process based on feedback and further analysis.

-------------------------------------------------------------------------

Divide the system into at least two separate components or subsystems, which can be supported with
two iterations. Briefly describe each.

1. Iteration 1: Geocaching Outing Management

This component will focus on the core functionalities related to planning and managing geocaching
outings.

Key Features:

- Geocache search and filtering based on location, difficulty level, and other criteria.

- Real-time GPS tracking and navigation assistance during outings.

- Geocache logging with essential details such as date, time, and personal notes.

- Geocache history and logbook for reviewing past outings.

2. Iteration 2: Geocache Creation and Analysis

This component will extend the system's capabilities by incorporating features for geocache creation and
advanced analysis of geocaching activities.

Key Features:

- Geocache creation tools, allowing Wayne to set coordinates, difficulty levels, descriptions, and hints for
his created caches.
- Management and monitoring functionalities for Wayne's created geocaches.

- Statistical analysis and reporting, generating summaries and metrics based on Wayne's geocaching
activities.

- Integration with external platforms (such as photo albums or blog posts) to enhance geocache content
and presentation.

-------------------------------------------------------------------------

Work Breakdown Structure (WBS) for Iteration 1: Geocaching Outing Management

1. Requirement Gathering and Analysis

- Identify system requirements and user needs (2 hours)

2. Geocache Search and Filtering

- Implement search functionality based on location, difficulty level, and other criteria (8 hours)

3. Real-time GPS Tracking and Navigation

- Integrate GPS device with the system to display current location, route, and distance (12 hours)

4. Geocache Logging

- Develop a user interface for logging geocache finds with relevant details (6 hours)

5. Geocache History and Logbook

- Create a database structure for storing and retrieving Wayne's geocache history (4 hours)

6. User Interface Design and Development

- Design an intuitive and user-friendly interface for the system (10 hours)

7. Testing and Quality Assurance


- Perform testing and debugging to ensure the reliability and accuracy of the implemented features (8
hours)

Total estimated time for Iteration 1: 50 hours

Note: The time estimates provided are preliminary and may be subject to change during the
development process based on further analysis and evaluation.

Certainly! Here's a Work Breakdown Structure (WBS) for Iteration 2: Geocache Creation and Analysis:

1. Requirement Refinement and Analysis

- Review and refine the requirements based on user feedback and additional analysis (2 hours)

2. Geocache Creation Tools

- Develop a user interface for creating and editing geocaches with coordinate selection, difficulty level
setting, and description/hint input (10 hours)

3. Management and Monitoring Functionality

- Implement features for Wayne to manage and monitor his created geocaches, including editing,
archiving, and visibility settings (8 hours)

4. Statistical Analysis and Reporting

- Design and develop algorithms and data processing functions to generate statistical insights and
reports based on Wayne's geocaching activities (12 hours)

5. Integration with External Platforms

- Establish connections and integrate the system with external platforms (such as photo albums or blog
posts) to enhance geocache content and presentation (10 hours)

6. User Interface Enhancement

- Enhance the user interface to accommodate new functionalities, such as geocache creation and
analysis features (6 hours)
7. Testing and Quality Assurance

- Conduct thorough testing and quality assurance to ensure the robustness, accuracy, and performance
of the implemented features (8 hours)

Total estimated time for Iteration 2: 56 hours

Please note that the time estimates provided are approximate and subject to change based on the
specific requirements, complexity of implementation, and additional factors encountered during the
development process.

You might also like