Professional Documents
Culture Documents
Use Case Document: Created: Last Update: Print Date: By: Distribution
Use Case Document: Created: Last Update: Print Date: By: Distribution
Version:
Created:
Last Update:
Print Date:
By:
Distribution:
Table of Contents
Use Case Document.............................................................................................1
1 Introduction......................................................................................................5
1.1 Purpose of Document................................................................................5
1.2 Glossary.....................................................................................................5
2 Application Overview.......................................................................................6
2.1 Define the Scope.......................................................................................6
2.2 Context.......................................................................................................6
2.3 Technical Environment...............................................................................6
Use Cases.............................................................................................................7
3 Use Case Model..............................................................................................7
3.1 Administrador...........................................................................................10
3.2 Administrador...........................................................................................10
3.3 Administrador...........................................................................................10
3.4 Cliente......................................................................................................11
3.5 Cliente......................................................................................................11
3.6 Cliente......................................................................................................11
3.7 Cliente......................................................................................................11
3.8 Cancelar peticion de compra...................................................................11
3.9 Comprar un producto...............................................................................11
3.10 Crear cuenta Skype...............................................................................11
3.11 Crear cuenta de usuario........................................................................12
3.12 Desactivar cuenta..................................................................................12
3.13 Detallar el producto................................................................................12
3.14 Enviar comprobante de pago................................................................12
3.15 Enviar confirmacion de compra.............................................................12
3.16 Enviar peticion de compra.....................................................................13
3.17 Enviar productos....................................................................................13
3.18 Enviar propuesta de horario..................................................................13
3.19 Escoger horario de clase.......................................................................13
3.20 Escoger la modalidad del producto.......................................................13
3.21 Iniciar sesion .........................................................................................13
3.22 Modificar datos de cuenta......................................................................13
3.23 Modificar el catalogo..............................................................................14
3.24 Modoficar precios .................................................................................14
3.25 Rcibir confirmacion de compra..............................................................14
3.26 Recibiir peeticion de compra.................................................................14
3.27 Recibir curso on line..............................................................................14
3.28 Recibir pedido........................................................................................14
3.29 Recibir solicitud de curso on line...........................................................15
3.30 Registrar................................................................................................15
3.31 Seleccionar producto.............................................................................15
3.32 Solicitar curso online..............................................................................15
3.33 Ver galeria productos.............................................................................15
3.34 Visualizar costo de los materiales.........................................................15
3.35 Visualizar costo de los productos..........................................................16
3.36 Visualizar lista de materiales.................................................................16
3.37 Vizualizar el catalogo.............................................................................16
3.38 Actors.....................................................................................................16
3.38.1 User..................................................................................................16
3.39 Primary Use Cases................................................................................17
3.39.1 Use Case1.......................................................................................17
3.39.2 Use Case2.......................................................................................17
· 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 the Copy Template drop-down - select:{use case template}.
Below are some simple introductory remarks on the purpose of the document.
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.
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 a connection 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 and software
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 Deployment Architecture 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 which
one 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 use
cases which are used from many other places -
for example updating a train record may be part
of many larger business processes.
Technical Use Case
· Application Overview
Some text on the application Overview…
2. Context
This is to give a brief definition of the context in which of the application will be implemented.
Specifying the relationship this system will have to existing systems within the environment.
3. Technical Environment
This is to give a brief definition of any applications relevant to the system being implemented.
There needs to be a definition of the relationship between these as well as any aspects that this
system is reliant upon.
Use Cases
Registrar
Crear cuenta de
usuario
Ver galeria
productos
«extend»
Iniciar sesion
Cliente
«include»
«include»
Desactiv ar cuenta
Modificar datos de
cuenta
Seleccionar el producto
«include» «include»
Escoger la
Detallar el producto modalidad del
«include» producto
Cliente «include»
«include»
«invokes»
Modificar el catalogo
Comprar un producto
Seleccionar producto
Cancelar peticion de
compra
«include»
«include»
«include»
Recibiir peeticion de
compra
«include»
Cliente
«include»
Rcibir confirmacion
de compra
«include»
Env iar confirmacion Administrador
de compra
Recibir pedido
«include»
Env iar productos
Cursos on line
«include»
«include»
Recibir solicitud de
«include»
curso on line
Administrador «include»
«invokes» Cliente
«include»
1. Administrador
Es la persona que maneja todos lo que tiene que ver con los cursos on line,
como recibir solicitudes y enviar horarios.
2. Administrador
Es el enacrgado de recibir las peticiones de compras, e nviar confirmacion y por
ultimo enviar productos.
3. Administrador
Es el encargado de publicar el catalogo y hacer los cambios que este requiera.
4. Cliente
Es la persona que compra un producto, solicita el curso y el horario para recibir
la clase on line por medio de Skype.
5. Cliente
6. Cliente
Es el usuario que ingresa y observa el catalogo de productos disponible en la
pagina WEB.
7. Cliente
Es el usuario que ingresa a la pagina WEb de SKYD, el cual requiere una
cuenta, para esto debe registrarse para luego iniciar sesion.
9. Comprar un producto
El cliente compra un producto.
30. Registrar
El cliente ingresa datos personales para registrarse en la base de datos de
SKYD o ingresa su nickname y password para iniciar sesion y poder escoger
el producto y ver sus detalles.
38. Actors
uc Actors
User
Figure 5: Actors
1. User
39. Primary Use Cases
uc Primary Use Cases
System Boundary
The System Boundary shows the
logical interface between users
and the system being described.
Use Case1
User
Use Case2
1. Use Case1
2. Use Case2