Documentos de Académico
Documentos de Profesional
Documentos de Cultura
Version:
<1.0>
Date: <dd/mmm/yy>
Revision History
Date
<dd/mmm/yy>
Confidential
Version
<x.x>
Description
<details>
Universidad, 2008
Author
<name>
Page 2 of 5
Version:
<1.0>
Date: <dd/mmm/yy>
Tabla de Contenidos
1.
Introduccin
1.1
Propsito
1.2
Alcance
1.3
Definiciones, Acrnimos y Abreviaciones
1.4
Referencias
1.5
Visin general
2.
3.
Objetivos de Rendimiento
3.1
<nombre del mtrico de rendimiento>
4.
Flujo de trabajo
4.1
Flujo de trabajo bsico
4.1.1 <Nombre del paso>
4.2
Flujos de trabajo alternativos
4.2.1 <Nombre del paso del flujo alternativo>
5.
Requerimientos especiales
5.1
<nombre del requerimiento especial>
6.
Extensiones
6.1
<nombre del punto de extensin>
Confidential
Universidad, 2008
5
5
Page 3 of 5
Version:
<1.0>
Date: <dd/mmm/yy>
Introduccin
[The introduction of the Business Use-Case Specification should provide an overview of the entire
document. It should include the purpose, scope, definitions, acronyms, abbreviations, references and
overview of this Business Use-Case Specification.]
1.1
Propsito
[Specify the purpose of this Business Use-Case Specification]
1.2
Alcance
[A brief description of the scope of this Business Use-Case Specification; what Use Case model(s) it is
associated with, and anything else that is affected or influenced by this document.]
1.3
1.4
Referencias
[This subsection should provide a complete list of all documents referenced elsewhere in the Business
Use-Case Specification. Each document should be identified by title, report number (if applicable), date,
and publishing organization. Specify the sources from which the references can be obtained. This
information may be provided by reference to an appendix or to another document.]
1.5
Visin general
[This subsection should describe what the rest of the Business Use-Case Specification contains and
explain how the document is organized.]
2.
2.1
Descripcin breve
[The description should briefly convey the role and purpose of the business use case. A single paragraph
should suffice for this description.]
3.
Objetivos de Rendimiento
[A specification of the metrics relevant to the business use case and a definition of their goals.]
3.1
4.
Flujo de trabajo
[A textual description of the workflow the business use case represents. The workflow should describe
what the business does to deliver value to a business actor, not how the business solves its problems.
Only one level of workflow steps is indicated in the subsections below, but you may add more levels if
necessary.]
Confidential
Universidad, 2008
Page 4 of 5
4.1.1
Version:
<1.0>
Date: <dd/mmm/yy>
4.2.1
5.
Requerimientos especiales
[The special requirements of the business use case are included here. These are requirements not covered
by the workflow as it has been described in the sections above.]
5.1
6.
Extensiones
[Extension points of the business use case.]
6.1
Confidential
Universidad, 2008
Page 5 of 5