Use Case: Cooperative game creation

Use-case: Cooperative game creation

Use-case:

Cooperative game creation

Primary Actor:

Group of student programmers

Goal in context:

Creating a game where each student programmer programs an aspect of the game.

Preconditions:

The students know how to program their part, the instructor has a framework game (either one that comes out of the box or custom made) in place.

Trigger:

The instructor and programmers starts their session.

Scenario:

1) Each student programmer writes their code.
2) Student programmers test their code on a local copy of the framework.
3) All the student programmers transfer their code file to the instructor's system using a network.
4) Instructor runs executable program from the command line with all the transferred files and the original framework game project file.
5) Everyone may repeat the process to explore possibilities.

Exceptions:

3a) The students and instructor do not wish to use a network:

3a1) They can use any file transferring method to transfer the files. However since compile errors and such can only be detected after the transfer, a fast transfer method is preferred for efficiency.

4a) Program has compile errors:

4a1) The main program will display which file and the line numbers of the errors so that student programmer can go back and fix it.

4b) Program has runtime errors:

4b1) The instructor and programmers analyze the error and goes back to fix it.

Priorities:

Essential, must be implemented

When Available:

At least Version 1.5, certain features will be implemented later.

Frequency of Use:

Often, a major component of use

Channel to Actor:

Via their own IDE instances and file transfer method to the instructors system. Also via oral or any other interpersonal communication method.

Secondary Actors:

Instructor

Channels to Secondary Actors:

Instructor's IDE and command line main program

Open Issues:

None