About the game
Teaching the process of requirements collection and analysis, the first stage of the database application lifecycle. The purpose of the game is to simulate the gathering of requirements in an organisation. The requirements are gathered by exploring the environment and asking particular questions to Non Playable Characters (NPCs) and interacting with objects. This requirments capture game is a prototype and the purpose of the evaluation is to determine how it can be improved.

Conversations
All your in game conversations are viewable at any time. Questions appear blue, To Do items are red and Requirements appear in green. These can also be tagged which will be added to your in game knowledge.

Requirments
The requirements contains all of the requirements you have collected and groups them into user requirements or technical requirements (system requirements).

The Clarify and Conflict buttons are used to generate new questions. This is done by selecting the check points beside the two requirements that need clarification or are in conflict and selecting the Clarify or Conflict button. When these generated questions are correct and are asked to certain NPCs in the game, then this will lead to the correct requirement being produced.

Each correct requirement has a positive score associated with it and each incorrect requirement has a negative score associated with it. The submit button is used when the player is satisfied that all relevant requirements are in the list. The submit button submits the requirements specification to the Project Manager, ends the game and generates a score.

Asking Questions
The questions are used to generate new dialog when talking to NPCs i.e. when the player is in a conversation with a character in the game they ask questions by clicking on the appropriate question in the questions tab. The game tracks all of the questions asked and will deduct marks if a question is posed to a game character too many times.

E-mail
E-mail from the project manager called Proj M. Proj M is opened by selecting the text "Proj M". This will generate two starting questions, that when clicked, will go into your knowledge in the question tab. Clicking on the orange text clients office address will start the game and the main office space displayed in figure 2 will be displayed.

User Requirements
(requirements of a high level of abstraction) Defined as “statements, in a natural language of what services the system is expected to provide and the constraints under which it must operate.”

System Requirements
(requirements of a highly detailed nature describing what the system should do) Defined as “set out the system’s functions, services and operational constraints in detail."

The B2B Sales Simulator was built on TPLD's Business Simulator, other applications also built on the same system are the Project Management Trainer and the B2B Sales Trainer.