1. Technology
1.1. Unity
1.2. PHP
1.3. client site requires IE9 + Chrome
2. Requirements
2.1. Big picture
2.1.1. Demonstrate information flow
2.1.1.1. gaming
2.1.1.2. analysis
2.1.1.3. Odin simulation
2.2. Cosmetic
2.2.1. maybe minor polishing
2.3. Features
2.3.1. Entering waypoints
2.3.2. Game levels
2.3.3. Game scoring
2.4. Backend
2.4.1. Existing implementation PHP, not working yet
2.4.2. Recommend Backend As A Service (BAAS)
2.5. New opportunities
2.5.1. Leaderboards / rewards via BAAS
2.5.2. Test coverage for C# codebase
2.5.3. Refactoring C# codebase (create firm foundation)
3. Constraints
3.1. Client organistion
3.1.1. ethics committee
3.1.1.1. not necessary if only storing email address
3.1.2. Login page (maybe)
3.2. Security / privacy
3.2.1. not sensitive, may be in future
3.2.2. data protection
4. Resources
4.1. People
4.1.1. Tommy G
4.1.1.1. 2d / week
4.1.2. Ed B
4.1.2.1. minimal?
4.2. Tech/Hosting
4.2.1. nn-Cloud
4.2.1.1. May require accreditation/funds
4.2.2. Internet
4.2.2.1. Free BAAS
4.2.2.2. Give stakeholders quickest access to updates
4.3. Cash
4.3.1. not discussed
5. Status
5.1. What's complete?
5.1.1. Everything worked when delivered
6. Plan
6.1. Phases
6.1.1. 0. Groundwork
6.1.1.1. Put code under version control (GitHub)
6.1.1.2. Host in client's GitHub organisation?
6.1.1.3. Use GitHub hosting to host app
6.1.1.4. Put PHP backend behind C# interface
6.1.2. 1. Get existing version working
6.1.2.1. Unity Plugin
6.1.2.1.1. Believed to be working fine
6.1.2.2. PHP Backend
6.1.2.2.1. Needs hosting, and connection to backend
6.1.2.3. Ian doesn't think this brings great value, but doesn't feel strongly about it, since it carries little cost
6.1.3. 2. Switch to HTML 5
6.1.3.1. HTML intro page (maybe)
6.1.3.2. Check browser performance on target machines
6.1.3.3. Replace PHP with BAAS
6.1.4. Iterative improvements (though next FY)