Use Case Diagram for Virtual 3D Lab depicting the functional requirements
Non-functional Requirements
The project must be open source
The project must be able to be accessed online
The project must be in 3D and utilise 3D components
The project should have good usability — users should be able to easily figure out what the next steps of the lab are
The project should have good response time — interactable objects should respond to user input in no more than one second
The project should be robust — Users should be able to retrace their steps and fix any step that they did wrong
Tables and Fields
There are no tables and fields involved in the creation of our project. This is because we do not have any data to store, and thus we will not be having any databases. Our team is only tasked with the establishment of the 3D aspect and flow of the virtual lab game, and we were informed that a different team will pick up on data storing and the other aspects of this game.
Screenflow diagram
Because our project doesn't have different "screens", the attached screenflow diagram depict the flow into different "states" of the game instead.
Screenflow Diagram for Virtual 3D Lab
Prototype Design
Below are some early renditions of what our game looks like:
Prototype Project Image 1: Player Holding a Test TubePrototype Project Image 2: Player holding a Pipette
