Fitin Fitness Tracker Project - Final Report

Overview:

Trello: Board Link

Source Code: Code

The Fitin Fitness Tracker Project aspires to redefine personal fitness management through a
comprehensive application, emphasizing efficient data management, user-friendly interfaces, and
collaborative development practices. This project aims to provide users with a powerful tool to monitor
and enhance their well-being, fostering a community of fitness enthusiasts.

Project Goal:

The primary goal of the Fitin Fitness Tracker Project is to empower users in their fitness journeys. Key
objectives include:

1. Comprehensive Tracking: Enable users to monitor exercise routines, log nutritional intake, and
track overall fitness progress.

2. Personalized Recommendations: Utilize calculated metrics to offer personalized suggestions,

3. User Collaboration: Foster community by incorporating social features for sharing

4. Ease of Use: Prioritize a seamless user experience with an intuitive and visually appealing
interface, ensuring accessibility for users of varying fitness levels.

5. Adaptability: Create a flexible system that adapts to changing user needs and fitness trends,
allowing for future expansions and enhancements.

The Fitin Fitness Tracker Project envisions becoming a leading solution for individuals seeking a holistic
approach to health and fitness management, promoting a healthier lifestyle through innovative
software solutions.

Progress Report:

Sprint 1: Define Foundations (2 weeks)

• Established clear milestones, use case diagram, and SSMS database structure.

• Defined functional/non-functional requirements, high-level use cases, and domain model.

• Achievements: Solid project foundation, effective collaboration with colleagues.

Sprint 2: System Design and Database Setup (2 weeks)

• Described critical use cases, created activity/class diagrams, initiated database tables.

• Implemented CRUD operations, set up repositories for efficient data management.

• Achievements: Detailed system design

Activity Diagram:
ER Diagram:
Architecture Diagram:
Use case Diagram:
Sprint 3: Implementation (2 weeks)

1. Database Implementation:

• Implement the SQL database schema based on the earlier defined database diagram.

• Create tables for users and exercise history to store relevant data.

• Ensure proper indexing and relationships between tables.

2. Database Connection:

• Develop the Database Connection component to manage connections between the

• Establish secure and efficient data access methods to interact with the database.

3. Data Population:

• Populate initial data into the database for testing and demonstration purposes.

• Ensure accurate representation of sample user profiles and exercise history.

4. User CRUD Operations:

• Implement CRUD (Create, Read, Update, Delete) operations for user data.

• Allow users to be created, read, updated, and deleted, ensuring data integrity.

5. History CRUD Operations:

• Implement CRUD operations for exercise history data.

• Enable logging and tracking of exercise-related information, supporting creation,

6. Java Implementation:

• Write Java code to integrate database functionality seamlessly into the Fitin Fitness
Tracker application.

• Ensure that Java classes responsible for database interactions follow best practices and
maintain code modularity.

7. Testing:

• Conduct thorough testing of the implemented database functionalities, including CRUD

Chosen Process Model

• Adapted Agile and Scrum for a small team with tailored practices.

• Utilized Trello with simplified boards and detailed cards for task management.

Mentionable Revisions of Initial Assumptions/Requirements

• All functional requirements retained excluding the one of the main features that is Personalized
Recommendation and Activity visualization feature deliberately removed for workload
management efficiency.

Key Requirements and Scenarios Used for Design

• Detailed use cases: "User”, “Exercise", “History” and their CRUD operations are Implemented

• Included activity diagram, use case diagram, domain model, ER diagram, and state of
architectural design.

Managing Team Transitions and Project Continuity: A Solution Approach

Team Transition Scenario: In the course of the Fitin Fitness Tracker Project, the team faced a significant
transition, with all members except one moving on to other commitments. This abrupt shift posed
challenges in project continuity, collaboration, and task distribution.

Solution Implemented: To navigate the transition effectively and ensure the seamless continuation of
the project, the following solutions were implemented:

1. Version Control and Documentation:

• Utilized Git as a version control system to track changes and maintain project history.

• Enhanced documentation practices, creating comprehensive README files and in-code

2. Solo Task Management:

• Leveraged project management tools like Trello for task organization, prioritization, and
progress tracking.

• Implemented a detailed task assignment and prioritization strategy for efficient solo
project management.

3. Knowledge Transfer and Self-Review:

• Conducted a knowledge transfer session, ensuring that key project insights were
transferred.
 • Continued the practice of code reviews, even as a solo developer, to maintain code
quality.

4. Communication and Logging:

• Established consistent communication channels through tools like Slack for self-logging
progress, challenges, and decisions made.

• Documented all communication and decisions to maintain a transparent record.

5. Backup and Recovery Planning:

• Regularly backed up the entire project, including codebase, databases, and

• Developed a recovery plan to handle unforeseen challenges and ensure project

Learning Outcomes:

1. Adaptability:

• Gained valuable experience in adapting to unforeseen challenges and managing a

2. Solo Project Management:

• Developed skills in solo project management, including task prioritization, efficient time
management, and effective communication with stakeholders.

3. Documentation Best Practices:

• Enhanced knowledge of documentation best practices, ensuring that the project

4. Resilience and Flexibility:

• Cultivated resilience and flexibility in project development, overcoming obstacles and

Conclusion:

Navigating the transition from a team-based project to a solo endeavor posed unique challenges, but
the implemented solutions and learning outcomes have positioned the Fitin Fitness Tracker Project for
continued success. This experience has not only strengthened project management skills but also
underscored the importance of adaptability and resilience in the dynamic landscape of software
development.

The commitment to robust documentation, version control, and efficient solo project management
strategies ensures that the Fitin Fitness Tracker Project remains a viable and sustainable endeavor. As
the sole contributor, the journey has been transformative, providing insights into the intricacies of
project continuity and reinforcing the importance of well-established development practices.