Profesional

Use Case Document
Version:||
Created:||
Last Update:||
Print Date:||
By:||
Distribution:||









































Table of Contents

Use Case Document 1
1 Introduction 3
1.1 Purpose of Document 3
1.2 Glossary 3
2 Application Overview 4
2.1 Define the Scope 4
2.2 Context 4
2.3 Technical Environment 4Use Cases 5
2.4 Administrar información del Proyecto 5






1 Introduction
This document can be modified to reflect the company logo as well as the general corporate layout. To create an editable copy of this template:
- Press F8.
- Press the option: [Manage Templates] .
- From this select: [New]
In the Dialog box:
- In the field: Template Name - type in a name.
- From theCopy Template drop-down - select:{use case template}.
Below are some simple introductory remarks on the purpose of the document.

1.1 Purpose of Document
The Purpose of this Document is to define the Use Case for ...

This is to be a standard paragraph to layout that the Business Logic and the elements within the package which are laying out the Use Cases for the package under development.This text is definable as a template by the user and stored locally. The system variables are filled in by EA via the RTF Document Generator.


1.2 Glossary
.
Group|Term|Definition|
Business|Accounting Periods|A defined period of time whereby performance reports may be extracted. (normally 4 week periods).|
Technical|Association|A relationship between two or more entities. Implies aconnection of some type - for example one entity uses the services of another, or one entity is connected to another over a network link.|
Technical|Class|A logical entity encapsulating data and behavior. A class is a template for an object - the class is the design, the object the runtime instance.|
Technical|Component Model|The component model provides a detailed view of the various hardware andsoftware components that make up the proposed system. It shows both where these components reside and how they inter-relate with other components. Component requirements detail what responsibilities a component has to supply functionality or behavior within the system.|
Business|Customer|A person or a company that requests An entity to transport goods on their behalf.|
Technical|DeploymentArchitecture|A view of the proposed hardware that will make up the new system, together with the physical components that will execute on that hardware. Includes specifications for machine, operating system, network links, backup units &etc.|
Technical|Deployment Model|A model of the system as it will be physically deployed|
Technical|Extends Relationship|A relationship between two use cases in whichone use case 'extends' the behavior of another. Typically this represents optional behavior in a use case scenario - for example a user may optionally request a list or report at some point in a performing a business use case. |
Technical|Includes Relationship|A relationship between two use cases in which one use case 'includes' the behavior. This is indicated where there a specific business usecases which are used from many other places - for example updating a train record may be part of many larger business processes.|
Technical|Use Case|A Use Case represents a discrete unit of interaction between a user (human or machine) and the system. A Use Case is a single unit of meaningful work; for example creating a train, modifying a train and creating orders are all Use Cases.Each Use Casehas a description which describes the functionality that will be built in the proposed system. A Use Case may 'include' another Use Case's functionality or 'extend' another Use Case with its own behavior.Use Cases are typically related to 'actors'. An actor is a human or machine entity that interacts with the system to perform meaningful work.|

2 Application Overview
Some text on the...