Members Page/Richard Barrington/Q Tune/Use Cases

MembersPage/RichardBarrington/QTune/UseCases (2006-02-10 15:46:26)

USE CASES

This is where we define how, exactly, our software will be used. If we get this wrong, the rest will be too! So, we'll first make sure we've got a common vision and goals before writing the Use Cases themselves. That said, we'll come back and revise this and the cases as needed. We'll be doing iterative development.

Please feel free to edit this page to shape the vision of this software project.

Software Mission Statement

The software will provide a user-friendly interface for a VEMS Genboard v3.x to configure, tune, and debug the setup of the ECU. It will add value to the project as a whole, as this will be the tool that most Genboard users will use.

At least double the installed ECU base by reducing the apparent complexity.
Support installers with online access to a shared configuration database.
Reduce support requirements by avoiding unsafe configurations.

System Boundaries

The software will access the ECU through the serial port. The software will access the online database through a network socket. The user will operate the software through the keyboard and optionally the mouse, with feedback through the screen and audio system.

System Actors

The roles within the system are the Installer, the Tuner, and the Driver.

The Installer is responsible for the initial setup of the ECU. They are knowledgeable about the technical details of the Genboard.
The Tuner is responsible for getting the ECU maps and variables affecting drivability configured. They may or may not be knowledgeable about the technical details of the Genboard.
The Driver is the end user who is likely to have minimum technical knowledge.

User Value

The Installer:

Let the initial setup process happen quickly.
Make the process reproducable.

The Tuner:

Make the tuning process as easy as possible.
Consider "real world" factors.

The Driver:

Provide user-friendly feedback on the system's operation.
Make it easy to capture logs and diagnostic information.

Use Cases

Each UseCase is to be on a small story on a separate page. Each invididual UseCase will address a single and complete goal that supports the system vision described above.

Installer Use Cases

MembersPage/RichardBarrington/QTune/UseCases/ConfigureEcuManually

MembersPage/RichardBarrington/QTune/UseCases/ConfigureEcuAutomatically
- MembersPage/RichardBarrington/QTune/UseCases/GetConfigurationLocally
- MembersPage/RichardBarrington/QTune/UseCases/GetConfigurationRemotely

Tuner Use Cases

Driver Use Cases

...