Pagwin/BinghamtonBetterBus-v2
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

sprint 4 finalization stuff

Browse source
This commit is contained in:
Pagwin 2025-03-26 12:40:41 -04:00
parent cf28ad4a4b
commit 69defed537
No known key found for this signature in database
GPG key ID: 81137023740CA260
1 changed files with 13 additions and 21 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

34
sprints/sprint4/sprint4.md
View file

@ -2,7 +2,7 @@
*note: replace anything surrounded by << >> and **remove** the << >>* *note: replace anything surrounded by << >> and **remove** the << >>*
**Attended**: << record the team members in attendance (virtual counts as long as they are participating) >> **Attended**: Spencer Powell
**DATE**: << meeting date >> **DATE**: << meeting date >>
@ -12,28 +12,28 @@
### SRS Sections Updated ### SRS Sections Updated
requirements requirements
### User Story ### User Story
arugably the initial story arguably the initial story
### Sprint Requirements Attempted ### Sprint Requirements Attempted
- Archetecture Diagram Missing - Archetecture Diagram completion
### Completed Requirements ### Completed Requirements
- Data format conversion for a single bus system - Client and server now share a language although the plumbing between them isn't setup yet
- server now determine's stops for a "route" although those stops aren't related to the response given by `/path` due to them not considering bus directionality
### Incomplete Requirements ### Incomplete Requirements
The path from point to point is in the form of 3 stops instead of Depends on how you interpret the requirements and completing them, ultimately it was determined that picking a somewhat useful route was a bigger requirement than expected however the naive algorithm which ignores bus directionality was implemented but not connected to the actual API due to being fundamentally unfit for purpose
### The summary of the entire project ### The summary of the entire project
<< A general overview of the entire project >> Things are almost coming toegether into a state where we can show something but getting useful functionality will probably be pushed back a few weeks
*** ***
@ -45,28 +45,20 @@ The path from point to point is in the form of 3 stops instead of
## Technical Debt ## Technical Debt
<< Any requirements from the previous sprint that are using a technical flex >>
### Requirement Target ### Requirement Target
<< The corresponding SRS requirement that our team will be complete in next sprint >> - Display routes or display routes (changed from text based simply giving back info retrieved from api to actually using google maps)
- decide on representation of graph and graph representation of the bus systems and create nodes in the representation of the graph for the graph representation of the system
### User Stories ### User Stories
<< Corresponding User Stories >> Initial user story
### Planning
<< Our team's detailed plan to complete the sprint >>
### Action Items
<< A list of things that need to happen in our for our team to complete the sprint >>
### Issues and Risks ### Issues and Risks
<< A list of potential obstacles that could keep us from completing the sprint and what's being done about them >> - Graph representation will probably need to be complicated
### Team Work Assignments ### Team Work Assignments
<< A list of each team member and their works assignments for this sprint >> - Levi will setup the client to use google maps instead of just displaying text
- Spencer will figure out the representation of the graph and graph representation of the system