sprint 4 finalization stuff

sprints/sprint4/sprint4.md

@@ -2,7 +2,7 @@
 
 *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 >>
 
@@ -12,28 +12,28 @@
 
 ### SRS Sections Updated
 
-
 requirements
 
 ### User Story
 
-arugably the initial story
+arguably the initial story
 
 ### Sprint Requirements Attempted
 
-- Archetecture Diagram Missing
+- Archetecture Diagram completion
 
 ### 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
 
-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
 
-<< 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
 
-<< Any requirements from the previous sprint that are using a technical flex >>
-
 ### 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
 
-<< Corresponding User Stories >>
-
-### 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 >>
+Initial user story
 
 ### 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
 
-<< 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