finished solo meeting
This commit is contained in:
parent
0f8695636f
commit
4732dbfff8
1 changed files with 50 additions and 26 deletions
|
@ -69,89 +69,113 @@ Combine that with the other things I mentioned and it's a pain.
|
|||
|
||||
**Clarification & Notes:**
|
||||
|
||||
-
|
||||
- forgot line of thought due to interview being interrupted
|
||||
|
||||
---
|
||||
|
||||
#### **4. What is the most important feature?**
|
||||
|
||||
**Client’s Response:**
|
||||
(Example: "Initiative tracking needs to be easy and automatic.")
|
||||
|
||||
Getting a reliable preferably optimal route of buses to get from point to point
|
||||
|
||||
**Clarification & Notes:**
|
||||
- This feature should be the **core focus** of the software.
|
||||
- Other features (e.g., dice rolling) are secondary.
|
||||
|
||||
- Focus on getting routes first and be reasonably certain they'll work
|
||||
|
||||
---
|
||||
|
||||
#### **5. Is there a similar product on the market?**
|
||||
**Client’s Response:**
|
||||
(Example: "Yes, but they are either too complex or too expensive.")
|
||||
|
||||
Google maps can be used to get routes which only use broome county buses but doesn't take OCCT buses into account.
|
||||
Furthermore it isn't clear if google maps can/would take into account live info for it's routes.
|
||||
|
||||
There's also etaSpot which is only a live map of OCCT buses
|
||||
|
||||
**Clarification & Notes:**
|
||||
- Competitor analysis needed.
|
||||
- Find a way to differentiate: **Simpler UI? Free version? Customizable?**
|
||||
- Worth investigating how google maps determines routes algorithmically
|
||||
- Need to integrate OCCT buses to be useful
|
||||
|
||||
---
|
||||
|
||||
#### **6. Are there any existing products or technologies that will need to be integrated?**
|
||||
|
||||
**Client’s Response:**
|
||||
(Example: "It would be nice if it worked with Roll20 or D&D Beyond.")
|
||||
|
||||
No
|
||||
|
||||
**Clarification & Notes:**
|
||||
- Check for **APIs** for possible integrations.
|
||||
- Consider a **manual import/export** feature if full integration isn’t feasible.
|
||||
|
||||
- The client isn't aware of Broome county providing GTFS
|
||||
- Furthermore from prior question etaSpot can be used for live OCCT bus info
|
||||
|
||||
---
|
||||
|
||||
#### **7. What does success look like for this project?**
|
||||
|
||||
**Client’s Response:**
|
||||
(Example: "If my players can see whose turn it is without me saying anything, that’s a win.")
|
||||
|
||||
If I can put in a place I want to go on my phone and get instructions to go there via bus that are good then I'd say it's a success.
|
||||
|
||||
**Clarification & Notes:**
|
||||
- Focus on **visual clarity and notifications**.
|
||||
|
||||
- Again focus on reliability and speed
|
||||
|
||||
---
|
||||
|
||||
#### **8. What risks are associated with a malicious user?**
|
||||
|
||||
**Client’s Response:**
|
||||
(Example: "Not much, unless players try to cheat dice rolls.")
|
||||
|
||||
nothing?
|
||||
|
||||
**Clarification & Notes:**
|
||||
- Consider **server-side dice validation** to prevent cheating.
|
||||
|
||||
- There's some risk of DDOS on our endpoints and possible free riders but that isn't really a risk to other users
|
||||
|
||||
---
|
||||
|
||||
#### **9. What is the expected lifetime of this software?**
|
||||
|
||||
**Client’s Response:**
|
||||
(Example: "I want to use it for many campaigns, so it should last for years.")
|
||||
|
||||
For my remaining time in university.
|
||||
|
||||
**Clarification & Notes:**
|
||||
- Future **maintenance and updates** should be considered.
|
||||
|
||||
- While this client will be leaving university soon there will be a continuous stream of new users so long term sustainability should be somewhat accounted for
|
||||
|
||||
---
|
||||
|
||||
#### **10. What additional features would you like?**
|
||||
|
||||
**Client’s Response:**
|
||||
(Example: "A way to send private messages to players would be cool.")
|
||||
|
||||
Live map
|
||||
|
||||
**Clarification & Notes:**
|
||||
- Nice-to-have, but **not essential** for version 1.
|
||||
|
||||
- nice to have and reasonably easy to implement for OCCT, harder for broome county
|
||||
|
||||
---
|
||||
|
||||
## **Key Takeaways & Next Steps**
|
||||
- **Most important feature:** Initiative tracking
|
||||
- **Secondary features:** Dice rolling, notifications, private messaging
|
||||
|
||||
- **Most important feature:** Route calculation
|
||||
- **Secondary features:** Live map and viewing schedules
|
||||
- **Deadline:** 3 months
|
||||
- **Risks:** Potential cheating in dice rolls
|
||||
- **Risks:** DDOS and freeloading users
|
||||
|
||||
### **Next Steps:**
|
||||
✅ Prioritize initiative tracking
|
||||
✅ Research existing products for inspiration
|
||||
✅ Explore integration options with Roll20/D&D Beyond
|
||||
|
||||
- [ ] Collect data from GTFS and etaSpot api
|
||||
- [ ] Use data to calculate crude route from point to point
|
||||
- [ ] Improve route making
|
||||
- [ ] Add live map
|
||||
|
||||
---
|
||||
|
||||
### **Signatures**
|
||||
(Client) **[Client’s Name]** – *Reviewed & Approved*
|
||||
(Developer) **[Your Name]** – *Re
|
||||
(Client) **Spencer Powell** – *Reviewed & Approved*
|
||||
(Developer) **Spencer Powell** – *Re
|
||||
|
|
Loading…
Reference in a new issue