Vision Statement - Jon-Lowe/Skyscii GitHub Wiki
Project Vision: docs.google.com/document/d/1Y4CQIaVe60tr-uEfYIQWq574_Xaljxvk79TD9C-JiJI/edit
1. Executive Summary - Vision Statement To create an easy to play and navigate ASCII game that Swinburne students can play when they are feeling down and lonely in their time off, which will help them connect with one-another and conveniently relax in their downtime. 2. Problem: Loneliness, depression and boredom in students; this game will help them connect, communicate and have fun. Even if it just gives them something in common to discuss! It will also give them something to do in their down time to help them relax in a positive way. 3. Initial architecture: C# - Team is familiar with the language and is fit for the purpose. (Program doesn’t require high performance & optimisation) AWS may be used to implement multiplayer. Apache Kafka may be used to implement a player-to-player messaging system. We considered using Unity, but decided not to such that development is not slowed down too much by learning too many new technologies.
4. Scope/initial requirements: A summary of the scope, potentially including a list of the major stakeholder goals to be addressed. A scope overview diagram is often useful, such as a use case diagram or a business process diagram.
The primary aim of the game will be to spend time between classes with a fun, easy to run, and easy to play game. The initial requirements are that the game must be able to have the player progress through rooms and defeat all the monsters they encounter for “a tonne of looooooot!”
5. Cost estimation & Funding strategy: As this will be a self-funded, we will make a preference to using a free tier AWS / Azure and other free tier solutions. Funding Strategy will be discussed with the product owner as we progress.
6. Release plan:
The project schedule showing number of iterations, their durations, and expected release dates. May use a high-level Gantt chart. 7. Risks: Technology learning curves, could cause a delay in production & Deployment of the product. Concept of the game could result in a limited audience, niche product Funding strategy & cost are very limited Limited time to complete (10 weeks) Team members have many other responsibilities (other subjects & home life) There is a risk of scoping the project too far and planning features that are never completed. 8. Assumptions: A list of key assumptions and decisions (if applicable). It will be an RPG Users will be english speaking/reading. Users have computer. Users will have a Windows operating system Users has keyboard.
9. Software development process: An indication of the process being followed (if applicable). Git Flow Agile
-
Other project details (where applicable):
-
Team Composition
Jon: Product Owner Terrence: Team Leader Sarah: Developer Daniel: Developer James: Developer
-
budget constraints
As we are self funded we have to rely on free tier options
-
communication plans
Meetings with agenda and minutes. Online messaging. Tutorials. ok