TOC PREV NEXT INDEX

Put your logo here!


3 Use-cases

This chapter presents use-cases for the major tasks that will be performed by ArgoPrint.

3.1 Purpose

The purpose of the use-cases is to provide an overview of the system's main functionality and how the system is used. The use-cases are also used to trace the requirements back to the system.

3.2 Use-case notation

The notation used to write use-cases is in accordance with the notation used in [Pfleeger, 2001].

3.2.1 Notation

The use-cases will use the following notation:
U-n.n Name
Description of the use-case.



User category: The user
Traceable to requirement: Requirements based on this use-case, defined in the requirements specification.

3.2.2 Use-case identity number

To identify a use-case, each use-case is given a unique identity number. These are the same as in the requirements specification.

3.2.3 User categories

Specification of which user category the actor is a part of. The user category is considered a role, and one person can perform several use-cases - however as different roles.
The roles available are:
Designer:
The person that creates and maintains the model in ArgoUML.
Goals: To create a model upon which to base a project and the documents surrounding it.
Document Author (DA):
The person that creates and maintains the templates that are used by ArgoPrint to generate reports.
Goals: To write templates that define how to create the reports and documents that are based on information in the model.
Configuration Manager (CM):
The person responsible for the base-lining of all releases.
Goals: To create updated versions of the reports using a template and a model.
ArgoPrint:
The system that executes the functions specified in a template.
Goals: To extract data from the model in accordance with the templates given to it.

3.2.4 Traceable to requirement

A list of the requirements based on this use-case. If no requirements are based on the use-case, its' only function is to provide a better explanation of how the system will be used.

3.3 Use-cases

The following section contains different use-cases that show ArgoPrint in action.
U-1.1 Create and modify UML-model
To use ArgoPrint, a UML-model in ArgoUML is required. Therefore a designer needs to create one. This is not within the scope of this project, however a model is needed in order for a template to be successfully executed.



User category: Designer
Traceable to requirement: -
U-1.2 Create and modify template
The DA's responsibility is to create and update the templates so that they generate the output required by the CM when applied to a UML-model.



User category: DA
Traceable to requirement: F-1.1, F-1.2, F-1.3
U-1.3 Base-line model
In order to generate an end document CM needs to apply a template on a certain UML-model and supply some additional information.



User category: CM
Traceable to requirement: F-2.1, F-2.2.
U-1.4 Executing a template
This use-case describes what happens when a template is applied to a UML-model. The main actor is the template itself, since this entity can be seen as acting upon the selected UML-model.



User category: ArgoPrint
Traceable to requirement: F-3.1, F-3.2.
U-1.5 Loading ArgoPrint from command line
ArgoPrint should be possible to invoke from the command line when ArgoUML is started. This makes it possible to automate the generation of documents with updated versions of the UML-model.



User category: CM
Traceable to requirement: F-2.3.



Quadralay Corporation
http://www.webworks.com
Voice: (512) 719-3399
Fax: (512) 719-3606
sales@webworks.com
TOC PREV NEXT INDEX