Professional Documents
Culture Documents
Versin:
<1.0>
Fecha: <dd/mmm/aa>
Historial de Revisiones
Fecha
<dd/mmm/aa>
Confidencial
Versin
<x.x>
Descripcin
<detalles>
, 2015
Autor
<nombre>
Pg. 2
Versin:
<1.0>
Fecha: <dd/mmm/aa>
Tabla de Contenidos
1.
Introduccin
1.1
Propsito
1.2
Alcance
1.3
Definiciones, Acrnimos, y Abreviaciones
1.4
Referencias
1.5
Organizacin de este Documento
2.
Posicionamiento
2.1
Oportunidad de Negocio
2.2
Sentencia que define el Problema
2.3
Sentencia que define la posicin del Producto
3.
4.
5.
6.
Restricciones
7.
Rangos de Calidad
8.
Precedencia y Prioridad
9.
Confidencial
, 2015
3
3
3
3
Pg. 3
Versin:
<1.0>
Fecha: <dd/mmm/aa>
Requisitos de Documentacin
Manual de Usuario
Ayuda en Lnea
Guas de Instalacin, Configuracin, y Fichero Lame
Etiquetado y Empaquetado
Atributos de Caractersticas
A.1 Estado
A.2 Beneficio
A.3 Esfuerzo
A.4 Riesgo
A.5 Estabilidad
A.6 Release que la Incluir
A.7 Asignacin
A.8 Justificacin
Visin
1. Introduccin
[El propsito de este documento es recopilar, analizar y definir las necesidades de alto nivel y las caractersticas de
<<System Name>>. Se centra en las capacidades necesarias de los Stakeholders y los usuarios destino, y el POR
QU existen estas necesidades. Los detalles de cmo el <system name>> satisface estas necesidades se detallan en
las especificaciones de caso de uso y complementarias.]
[The introduction of the Vision document provides an overview of the entire document. It includes the purpose,
scope, definitions, acronyms, abbreviations, references, and overview of this Vision document.]
1.1 Propsito
[Especifica el propsito de este documento VISIN]
1.2 Alcance
[Una breve descripcin del alcance de este documento Visin, qu proyecto (s) est asociado y cualquier otra
cosa que se vea afectada o influenciada por este documento.]
1.3 Definiciones, Acrnimos, y Abreviaciones
[This subsection provides the definitions of all terms, acronyms, and abbreviations required to properly interpret the
Vision document. This information may be provided by reference to the projects Glossary.]
1.4 Referencias
[This subsection provides a complete list of all documents referenced elsewhere in the Vision document. Identify
each document 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 Organizacin de este Documento
[This subsection describes what the rest of the Vision document contains and explains how the document is
organized.]
2. Posicionamiento
2.1 Oportunidad de Negocio
[Describa brevemente la oportunidad de negocio que se cumplen por este proyecto.]
Confidencial
, 2015
Pg. 4
Versin:
<1.0>
Fecha: <dd/mmm/aa>
[describe el problema]
afecta a
El impacto asociado es
[cliente destino]
Quien
Que
No como
Nuestro producto
[Una declaracin de posicin del producto comunica la intencin de la aplicacin y la importancia del proyecto a
todo el personal interesado.]
Confidencial
, 2015
Pg. 5
Versin:
<1.0>
Fecha: <dd/mmm/aa>
Description
Responsibilities
[Breve
descripcin
stakeholder.]
del
Descripcin
Responsabilidades
Stakeholder
[Nombre
del
Stakeholde
r tipo.]
[Briefly describe
what
they
represent
with
respect to the
system.]
captures details
produces reports
coordinates work
and so on]
, 2015
Pg. 6
3.5.1
Versin:
<1.0>
Fecha: <dd/mmm/aa>
Representante
Descripcin
Tipo
Responsabilid
ades
Criterio de
xito
Grado de
participacin
Artefactos
adicionales
[Are there any additional deliverables required by the stakeholder? These could be
project deliverables or outputs from the system under development.]
Comentarios
[Problems that interfere with success and any other relevant information go here.]
Representante
Descripcin
Tipo
Responsabilidades
[List the users key responsibilities with regard to the system being developed
that is, captures details, produces reports, coordinates work, and so forth.]
Criterio de xito
Grado de
participacin
[How is the user involved in the project? Relate where possible to Rational Unified
Process rolesthat is, Requirements Reviewer, and so on.]
Artefactos
[Are there any deliverables the user produces and, if so, for whom?]
Confidencial
, 2015
Pg. 7
Versin:
<1.0>
Fecha: <dd/mmm/aa>
adicionales
Comentarios
[Problems that interfere with success and any other relevant information go here.
These would include trends that make the users job easier or harder.]
[It is important to understand the relative importance the stakeholder or user places on solving each problem.
Ranking and cumulative voting techniques indicate problems that must be solved versus issues they would like
addressed.
Fill in the following tableif using Rational RequisitePro to capture the Needs, this could be an extract or report
from that tool.]
Necesidad
Prioridad
Importancia
Solucin Actual
Soluciones Propuestas
3.8 Alternativas
[Identificar alternativas que el stakeholder percibe como disponibles. Estos pueden incluir la compra del producto
de un competidor, construir una solucin desarrollada internamente o simplemente mantener el statu quo. Lista de
cualquier alternativas competitivas conocida que exista o que estn disponibles. Incluyen las principales fortalezas
y debilidades de cada competidor como percibidos por el interesado o el usuario final.]
3.8.1
<Una Alternativa>
3.8.2
<Otra Alternativa>
Supuestos y dependencias]
, 2015
Pg. 8
Versin:
<1.0>
Fecha: <dd/mmm/aa>
Visin sirve de apoyo al cliente ya que puede utilizar esta parte de la documentacin para revisar problemas de
direccin, enrutamiento y estatus sin mencionar en cantidad el detalle que cada una de estas funciones requiere.
Organizar las funciones en una lista que sea comprensible para el cliente o para cualquier otra persona al leer el
documento por primera vez. Una simple lista en la tabla con las principales ventajas y funciones de apoyo podra
ser suficiente. Por ejemplo:]
Table 4-1 Customer Support System
Beneficio para el Cliente
Funciones de Apoyo
New support staff can quickly Knowledge base assists support
get up to speed.
personnel in quickly identifying known
El nuevo personal de apoyo
fixes and workarounds.
puede ponerse al da
La Base de conocimiento ayuda al
rpidamente
personal de apoyo en la rpida
identificacin de soluciones y
correcciones conocidas.
Customer satisfaction is
Problems are uniquely itemized,
improved because nothing
classified and tracked throughout the
falls through the cracks.
resolution process. Automatic
La satisfaccin del cliente se
notification occurs for any aging
mejora
issues.
Los problemas son nicamente
detallados, clasificados y se realiza un
seguimiento durante todo el proceso de
resolucin. Notificacin automtica se
produce algn problema de caducidad.
Management can identify
problem areas and gauge
staff workload.
El Gestor puede identificar
reas problemticas y medir
la carga de trabajo de
personal.
Distributed support teams
can work together to solve
problems.
Equipos de apoyo distribuidos
pueden trabajar juntos para
resolver problemas.
Confidencial
, 2015
Pg. 9
Versin:
<1.0>
Fecha: <dd/mmm/aa>
Evitar el diseo. Mantener las descripciones de funciones a nivel general. Concentrarse en las capacidades
necesarias y por qu (no cmo) que deben aplicarse.
Si est utilizando el kit de herramientas de Rational RequisitePro, todos deben ser seleccionados como los
requisitos de tipo para facilitar la consulta y el seguimiento.]
5.1 <Una Caracterstica>
5.2 <Otra Caracterstica>
6. Restricciones
[Note any design constraints, external constraints or other dependencies.]
7. Rangos de Calidad
[Define the quality ranges for performance, robustness, fault tolerance, usability, and similar characteristics that
are not captured in the Feature Set.]
Confidencial
, 2015
Pg. 10
Versin:
<1.0>
Fecha: <dd/mmm/aa>
8. Precedencia y Prioridad
[Define the priority of the different system features.]
[Features are given attributes that can be used to evaluate, track, prioritize, and manage the product items proposed
Confidencial
, 2015
Pg. 11
Versin:
<1.0>
Fecha: <dd/mmm/aa>
for implementation. All requirement types and attributes need to be outlined in the Requirements Management Plan,
however, you may wish to list and briefly describe the attributes for features that have been chosen. The following
subsections represent a set of suggested feature attributes.]
A.1
Estado
[Set after negotiation and review by the project management team. Tracks progress during definition of the project
baseline.]
Propuesta
[Used to describe features that are under discussion but have not yet
been reviewed and accepted by the "official channel," such as a
working group consisting of representatives from the project team,
product management, and user or customer community.]
Aprobada
[Capabilities that are deemed useful and feasible, and have been
approved for implementation by the official channel.]
Incorporada
A.2
Beneficio
[Set by Marketing, the product manager or the business analyst. All requirements are not created equal. Ranking
requirements by their relative benefit to the end user opens a dialog with customers, analysts, and members of the
development team. Used in managing scope and determining development priority.]
Critica
Important
e
til
[Features that are useful in less typical applications will be used less
frequently or for which reasonably efficient workarounds can be
achieved. No significant revenue or customer satisfaction impact can be
expected if such an item is not included in a release.]
A.3
Esfuerzo
[Set by the development team. Because some features require more time and resources than others, estimating the
number of team or person-weeks, lines of code required or function points, for example, is the best way to gauge
complexity and set expectations of what can and cannot be accomplished in a given time frame. Used in managing
scope and determining development priority.]
A.4
Riesgo
[Set by development team based on the probability the project will experience undesirable events, such as cost
overruns, schedule delays or even cancellation. Most project managers find categorizing risks, as high, medium,
and low, is sufficient, although finer gradations are possible. Risk can often be indirectly assessed by measuring the
uncertainty (range) of the projects teams schedule estimate.]
Confidencial
, 2015
Pg. 12
Versin:
<1.0>
Fecha: <dd/mmm/aa>
A.5
Estabilidad
[Set by the analyst and development team, this is based on the probability that features will change or the teams
understanding of the feature will change. Used to help establish development priorities and determine those items
for which additional elicitation is the appropriate next action.]
A.6
Release que la Incluir
[Records the intended product version in which the feature will first appear. This field can be used to allocate
features from a Vision document into a particular baseline release. When combined with the status field, your team
can propose, record, and discuss various features of the release without committing them to development. Only
features whose Status is set to Incorporated and whose Target Release is defined will be implemented. When scope
management occurs, the Target Release Version Number can be increased so the item will remain in the Vision
document but will be scheduled for a later release.]
A.7
Asignacin
[In many projects, features will be assigned to "feature teams" responsible for further elicitation, writing the
software requirements, and implementation. This simple pull-down list will help everyone on the project team to
understand responsibilities better.]
A.8
Justificacin
[This text field is used to track the source of the requested feature. Requirements exist for specific reasons. This field
records an explanation or a reference to an explanation. For example, the reference might be to a page and line
number of a product requirement specification or to a minute marker on a video of an important customer review.]
Confidencial
, 2015
Pg. 13