- The StatTracker application provides detailed statistical analysis for a sports league, covering game, league, and season metrics. It includes methods to determine the highest and lowest game scores, percentages of home and visitor wins, average goals per game, and games by season. League statistics cover team performance, identifying the best and worst offenses, and the highest and lowest-scoring teams at home and away. Season-specific methods analyze coach performance, team accuracy, and tackle counts. StatTracker is a comprehensive for analyzing league performance and trends.
- Ruby 3.2.2 & RSpec 3.13
Outline of Check-ins
- We are planning on having a standup meeting 30 minutes before class, as well as a daily post class check in.
- We plan on a larger meeting to redefine DTR on friday(tentatively).
Plan Organization
- We are utilizing Github Project as our primary organization source.
- Using Google Docs to organize more qualitative team building points.
- Frequent communication via Slack will be the standard.
Project Organizer Discussion
- When discussing the project organization tool, we considered Mirrorboard and Github Projects, but ultimately chose Github Projects due to its utility and seamless integration with our repository.
- We all agreed Github Project is most likely the industry standard and it would behoove us to familiarize ourselves with the application.
Code Design
-
After assessing the project requirements, we decided to structure our code design around four primary classes:
-
StatTracker: This class will encapsulate the core logic and functionality, managing most of the codebase. -
Game,Team, andSeason: These classes will act as auxiliary components and data storage.
-
Additionally, we created three simplified dummy CSV files with minimal data. This approach ensures our tests execute efficiently by avoiding the overhead of processing large datasets.
To streamline our development process and prevent issues with method assignment, we established a clear code architecture from the outset.
Given our asynchronous workflow and the fact that different team members were working on various methods concurrently, we anticipated potential misalignment between our to-do list and the evolving code structure. To mitigate this risk, we preemptively defined method names in both the library (lib) and specification (spec) files, adhering to the assignment order.
- We have implemented a style guide to adhere to for consistency.
DTRs
-
Discussed second DTR 8/02/24
Retro
What Went Well
-
Details in retro, but in summary:
- Communication
- Code Design
- Group Dynamic
Future Improvements
- Details in retro, but in summary:
- Code Spikes
- Refactoring
- Detail Orientation