Team Half and Half
Table of Contents
Overview
SpireBooks is a management decision tool, made with the intent to facilitate and help organizations make informed financial and strategic decisions based on a comprehensive consolidation of financial data and integration of non-financial factors.
GitHub organization page: github.com/Team-Half-and-Half
Key Outcomes
- Succeed in building a decision-making management tool that can be easily used by autonomous companies
- Visualize an interactive fiscal sustainability model spreadsheet
- Make it easy for companies to understand their current financial state based on the historical data
- Utilize features for companies to input their own data which will then allow the web application to do the math and show a visual representation of the forecast
- Visually present the companies numbers as non-static, allowing them to see how different inputs can change the forecast
- Create visually pleasing charts and dashboard that are easy to look at and navigate
User Guide
Landing
Sign In
Sign Up
Dashboard
Financing > Audited Balance Sheet
Financing > Budget P&L Sheet
Financing > Scenario Profiles
Audit > Upload
Visualize > Compare Projections
Visualize > Manage Projections
Manage > Verification Table
User Settings
Continuous Integration
SpireBooks uses GitHub Actions to automatically run ESLint and TestCafe each time a commit is made to the default branch. You can see the results of all recent “workflows” at https://github.com/Team-Half-and-Half/spirebooks/actions.
Development History
The development process for SpireBooks conformed to Issue Driven Project Management practices. In a nutshell:
- Development consists of a sequence of Milestones.
- Each Milestone is specified as a set of tasks.
- Each task is described using a GitHub Issue, and is assigned to a single developer to complete.
- Tasks should typically consist of work that can be completed in 2-4 days.
- The work for each task is accomplished with a git branch named “issue-XX”, where XX is replaced by the issue number.
- When a task is complete, its corresponding issue is closed and its corresponding git branch is merged into master.
- The state (todo, in progress, complete) of each task for a milestone is managed using a GitHub Project Board.
- The following sections document the development history of SpireBooks.
Milestone 1
The goals for Milestone 1 were to have several mockup pages and acceptance tests.
Milestone 1 was managed using SpireBooks Github Project Board Milestone 1.
Milestone 2
The goals for Milestone 2 were to add functionality to the pages and to setup our databases.
Milestone 2 was managed using SpireBooks Github Project Board Milestone 2 (Customer Meeting).
Milestone 3-4
The goals for Milestone 3-4 were to continue implementing functionality, with a focus on the databases.
Milestone 3-4 was managed using SpireBooks Github Project Board Milestone 4 (Customer Meeting).
Milestone 5
Milestone 5 was managed using SpireBooks Github Project Board Milestone 5.
Milestone 6
Milestone 6 was managed using SpireBooks Github Project Board Milestone 6 (Customer Meeting).
Milestone 7
The goals for Milestone 7 were to finalize the application and implement specific roles and permissions for each page.
Milestone 7 was managed using SpireBooks Github Project Board Milestone 7 (Customer Meeting).
Team Members
SpireBooks was created for and in collaboration with Spire Hawaii as part of the University of Hawaii at Manoa’s Software Engineering II Fall 2024 course. It is developed and maintained by the following students: Nicholas Beydler, Xavier Burt, Payton Higa, Samantha Mallari, Brandon Nelson, Christopher Pascual, Jonathan Sapolu, and Anthony Tirabassi.
View our team contract here.