Documentos de Académico
Documentos de Profesional
Documentos de Cultura
Version <1.0>
Rol N 3
ANALISTA FUNCIONAL
Comunicacin,
Rol N 4
ANALISTA
PROGRAMADOR
BittnerandSpence,USECASEMODELING,pp.301330,2002PearsonEducationInc.Reproduced
bypermissionofPearsonEducation,Inc.Allrightsreserved.
MJ
ANALISTA DE CALIDAD
YR
ANALISTA FUNCIONAL
LM
ANALISTA PROGRAMADOR
FORMATOS
ENFOQUE DE
ASEGURAMIEN
TO DE LA
CALIDAD (QA)
ENFOQUE DE
CONTROL DE
LA CALIDAD
(QC)
ENFOQUE DE
MEJORA DE
PROCESOS
REQUISITOS FUNCIONALES:
PRIORIDAD
STAKEHOLDER
OTORGADA
POR EL
CD
STAKEHOLDER
IGO
Medio
RE
01
Cliente:
Lder de
usuario
REQUISITOS
DESCRIPCIN
La interfaz de usuario
debe ser de color rojo
y con el fondo del logo
de la empresa.
Muy Alto
Asesor del
rea de
ventas de
BOTICA
VANESSA
Alto
REQUISITOS
NO
RE
02
RE
03
El clculo de las
boletas y facturas se
realicen
automticamente.
FUNCIONALES:
PRIORIDAD
STAKEHOLDER
OTORGADA
POR EL
REQUISITOS
CD
IGO
Alto
RE
04
RE
05
Verificar
cada
entregable y dar su
aceptacin antes de
presentar al cliente
(Lder de usuario).
RE
06
Durante el periodo de
ejecucin se espera
obtener
una
satisfaccin del 80 %
como mnimo de cada
entregable.
Sponsor:
Gerente del
rea de
ventas de
la BOTICA
VANESSA
Muy Alto
Alto
REQUISITOS
DE
CALIDAD:
PRIORIDAD
STAKEHOLDER
DESCRIPCIN
STAKEHOLDER
OTORGADA
POR EL
STAKEHOLDER
REQUISITOS
CD
IGO
DESCRIPCIN
NECESIDAD
DEL
Muy Alto
NEGOCIO
OPORTUNIDAD
RE
07
Durante
la
presentacin de los
entregables se espera
obtener
una
calificacin mnima de
15.0 sobre 20.0 de
satisfaccin del cliente
(Lder de usuario).
A APROVECHAR:
______________
______________
RU Financial Services
Revision History
Date
<dd/mmm/yy>
Version
1.0
Description
To support the review of the Withdraw
Cash Use Case
DE
<Name>Generated by
Paul Ramon
RESUMEN
1.1.1.1.1
Fecha:
Author
ENTREVISTA
23/04/2016
Duracin
de: 1:30
a: 2:30
Entrevistado(s):
Javier Andres
Sifuentes castillo
Nro. de entrevista:
Realizada por:
Rojas Changano Giancarlo Andree
Temas tratados:
Proceso de ventas
Control de Stock
Organizacin
RU Financial Services
Tema: <Tema de la entrevista 1>
<Pregunta 1.1>
<Respuesta 1.1.>
<Pregunta 1.2.>
<Respuesta 1.2.>
.
<Pregunta 2.1>
<Respuesta 2.1.>
<Pregunta 2.2.>
<Respuesta 2.2.>
.
Conclusiones de la entrevista
Prximas acciones/reuniones
Glossary Extract
Copyright IBM Corp. 2003
8
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
RU Financial Services
Version 1.3
Version:
<1.0>
Date: <dd/mmm/yy>
Revision History
Date
Version
Description
Author
1.0
J. Carlos Goti
1.2
J. Bell
1.3
Editorial changes
B. Baker
Confidential
Page 10
Version:
<1.0>
Date: <dd/mmm/yy>
Table of Contents
1.
Introduction
1.1
Purpose
1.2
Scope
1.3
Definitions, Acronyms and Abbreviations
1.4
References
1.5
Overview
2.
Functionality
2.1
Localization
2.2
Business Rules
2.2.1 Account Cash Minimum
2.2.2 Limit Order Allowable Accounts
2.2.3 Market Order Allowable Accounts
2.2.4 RU e-st terms and conditions
2.2.5 Transaction Fees
3.
Usability
3.1
Browser compatibility
3.2
Access to information
3.3
Online tutorial
4.
Reliability
4.1
Availability
4.2
Timeliness and Accuracy
5.
Performance
5.1
Response Time
6.
Supportability
6.1
Installability
7.
Design Constraints
8.
9.
Purchased Components
10.
Interfaces
10.1
Inputs
10.1.1 Asset Limit Purchase Information
10.1.2 Asset Limit Sale Information
10.1.3 Asset Purchase Information
10.1.4 Asset Sale Information
10.1.5 Dollar Transfer Information
10.1.6 New Account Information
10.1.7 News System Response
10.1.8 Quote System Response
Confidential
6
6
6
6
6
7
8
8
8
8
8
8
9
Page 11
10.3
Version:
<1.0>
Date: <dd/mmm/yy>
Outputs
10.2.1 Account List
10.2.2 Headline News Display
10.2.3 Market Trading Confirmation
10.2.4 Market Trading Request
10.2.5 Account Display
10.2.6 Quote Display
10.2.7 Stock Yearly History Chart
Systems with Which to Interface
10.3.1 Quote System
10.3.2 Market Trading System
10.3.3 News System
10.3.4 Financial Network System
10.3.5 IRS Reporting System
11.
Licensing Requirements
12.
13.
13.1
9
9
9
9
10
10
10
10
10
10
10
11
Applicable Standards
NASD, SIPC rules
Confidential
Page 12
Version:
<1.0>
Date: <dd/mmm/yy>
Glossary Extract
2.
Introduction
The purpose of this document is to collect, analyze and define the supplementary specifications for the RU
e-st system.
2.1
Purpose
This document records specifications that have general applicability to the RU e-st product with the
objective of achieving agreement of what the system does between stakeholders and developers.
2.2
Scope
This document is a record of specifications that affect the RU e-st product as a whole or large parts of it.
2.3
2.4
References
Vision document
Glossary
Use cases
2.5
Overview
This document contains the supplementary specifications, organized by type of requirement: Functionality,
Usability, Reliability, Performance, Supportability, Design Constraints, Documentation Requirements,
Purchased Components, Interfaces, Licensing Requirements, Legal Requirements, and Applicable
Standards.
3.
Functionality
Functionality at a high level is documented in the Vision document. Detailed functional requirements are
primarily documented in the Use Case Reports for individual uses cases of the RU e-st system. Here we
record a localization requirement that pertains to all use cases and business rules for the RU e-st system.
3.1
Localization
The application allows the user to select a language preference of English, Spanish, French, German, or
Swedish. The application displays all information to the customer in their selected language.
Confidential
Page 13
Version:
<1.0>
Date: <dd/mmm/yy>
3.2
Business Rules
3.2.1
3.2.2
3.2.3
3.2.4
3.2.5
Transaction Fees
When a transaction is confirmed by the Trading System, the fees are calculated and deducted from the cash
in the account. These monies are transferred to the RU e-st holdings.
4.
Usability
4.1
Browser Compatibility
The application can run under either MS Internet Explorer or Netscape Navigator.
4.2
Access to Information
The user can gather all information related to their accounts on one screen.
4.3
Online Tutorial
The application provides an online tutorial for the customer.
5.
Reliability
5.1
Availability
The application will be up and available 100 percent of the time during NYSE market hours. The
application should not be down for more than 15 minutes at any other time.
Confidential
Page 14
Version:
<1.0>
Date: <dd/mmm/yy>
5.2
6.
Performance
6.1
Response Time
A customer must receive status on their transaction within five seconds of placing the order. Even though
the transaction may not execute immediately, the customer should receive notification that the order has
been successfully accepted and is ready to be executed.
7.
Supportability
7.1
Installability
The user does not have to install any additional software to use the application.
8.
Design Constraints
TBD
9.
10.
Purchased Components
N/A
11.
Interfaces
In this section the interfaces that must be supported by the application are specified. The first two
subsections record the contents of all inputs and outputs that RU e-st has to support/provide. Also, the list
of systems that RU e-st interfaces with is shown.
11.1
Inputs
Each of the following sections specifies the content for a particular kind of input to the RU e-st system.
Confidential
Page 15
Version:
<1.0>
Date: <dd/mmm/yy>
Confidential
Page 16
Version:
<1.0>
Date: <dd/mmm/yy>
Outputs
Each of the following sections specifies the content for a particular kind of output from the RU e-st
system. The name of each output gives the type of content of the output and (if not a display to the
end-user) the system to which the output is sent.
List of headlines for the news stories for the last six months that relate to a given security.
Page 17
Version:
<1.0>
Date: <dd/mmm/yy>
Confidential
Page 18
Version:
<1.0>
Date: <dd/mmm/yy>
RU e-st,
12.
Licensing Requirements
13.
14.
Applicable Standards
14.1
Confidential
Page 19
Confidential
Version:
<1.0>
Date: <dd/mmm/yy>
Page 20
Version:
<1.0>
Date: <dd/mmm/yy>
Table of Contents
Introduction
Definitions
Confidential
Page 21
Confidential
Version:
<1.0>
Date: <dd/mmm/yy>
Page 22
Version:
<1.0>
Date: <dd/mmm/yy>
Glossary Extract
Introduction
This document provides an extract of the Sample Bank ATM Project Glossary to support the review of the key
Withdraw Cash Use Case.
This document was generated from the Sample Bank ATM glossary held in the Sample Bank ATM project
requirements repository.
Definitions
Term
Description
Additional Information
Account
ATM ID / ATM
iIdentifier
Bank Ccard
Card Number
Communication Retry
Number
Confidential
Page 23
Version:
<1.0>
Date: <dd/mmm/yy>
Communication Time-out
Period
Confiscated Cards
Customer
Customer Nnumber
Customers Bbank
Event LlLog
The session ID
The data and time of the event
The nature of the event
Financial Institution
Institution Iinter-bank
nNumber
Owning branch
Personal Identification
Number (PIN)
Confidential
Page 24
Version:
<1.0>
Date: <dd/mmm/yy>
Cash wWithdrawal
Deposit fFunds
Transfer fFunds
Manage aAccount
Service Organization
Smallest Denomination
Note Held
Standard Wwithdrawal
aAmount
Transaction FfFee
Transaction LlLog
Confidential
Page 25
Version:
<1.0>
Date: <dd/mmm/yy>
rejected
The bank systems response
For a withdrawal, the log also shows
The amount dispensed
Withdrawal Aacceptance
Withdrawal LlLimit
Withdrawal Receipt
Withdrawal Rrejection
Confidential
Page 26
Confidential
Version:
<1.0>
Date: <dd/mmm/yy>
Page 27