You are on page 1of 27

Sistemas II

Plantillas

Fabin Andrs Giraldo


COD:1800026

Plantillas
Requirement Shell
Requirement No.:

Requirement Type:

Use Cases:

Description:

Rationale:

Source (Originator):
Fit Criterion:

Customer Satisfaction Rating:

Customer Dissatisfaction Rating:

Priority: (Must Have, Should have, Could have , want have)


Dependencies:

Conflicts:

History:

Supporting Materials:

Test Name:
Description:
Requirement(s):
Prerequisites:
Setup:

Test Case 2:

Tester must point to Mock P drive in test environment. Verify that the most recent file is currently in
Trademarks\FAST 2.1\BIN\Fast Application.exe of the current CM Build. Create a desktop shortcut of the FAST
executable file from Mock P and launch the FAST exe.
Map to the TICRS drive(s):

Plantillas
Actor Cards
Actor Specification

Actor Name:
Type: (Primary/Secondary)

Personality: (I, E, R or F)

Abstract: (Yes/No)

Role Description:

Actor Goals:

Use Cases Involved with:

Plantillas
Use Case Diagram
ATM System
Withdraws Funds

Makes Deposits

Monitors ATM
Status

Replenishes Cash
ATM Service Rep

Customer
Manages Account
Upload Customer
Transaction
Data
Inquires Customer
Activity
Customer Accounts System

Bank Manager

Plantillas
Elaborated Use Case Form w/Business Steps
(This is the same form as the prior Elaborated Use Case
form, but it has two columns where you can differentiate
system steps from business steps. Use cases normally
only have system steps, but describing business steps may
provide important context information for your application. It
is important that developers can differentiate system
actions from business actions in your use cases.)

Plantillas
Use Case ID
Use Case
Elaboration Phase

(prefix your Use Case IDs with UC, to distinguish them from other models)
Elaborated use case

Actors

Description

(brief)

System Steps

Business Steps

Pre-conditions
1.
2.
3.
Flow of Events
(include conditional flows
here as they occur)

4.

If xxx
1.
Else
1.
2.

5.

1.
2.
3.
4.

If xxx
1.
Else
1.
2.

5.
etc.

etc.

Post-conditions
Alternative Flows
Priority
Non-Functional
Requirements
Assumptions

(briefly describe alternative flows here for base Use Cases; extend this into complete flow of events for Elaborated Use Cases,
either here or in the next template)
(High, Medium or Low)
(only those associated with this use case, if any)

Outstanding Issues
Source

Plantillas
Use Case Form for Alternative Flows
(An Alternative Use Case MUST be associated with an existing Elaborated Use
Case)
Use Case ID

(same ID as the base Use Case ID, but with suffix A1, A2, etc., for each alternative flow Use Case)

Use Case
Elaboration Phase

(indicate whether its initial, base or elaborated use case)

Actors
Description

(brief)

Insertion Point

(step in Base Use Case where this alternative flow should be inserted)

Pre-conditions

(clearly indicate under which conditions the alternative flow is triggered)

Alternative Flow of Events

1.
2.
3.
4.
5.

Post-conditions
Priority

(High, Medium or Low)

Non-Functional
Requirements

(only those associated with this use case, if any)

Assumptions
Outstanding Issues
Source

Plantillas
Form for Extending Use Cases
(An Extending Use Case MUST be associated with an existing Elaborated Use
Case)
Use Case ID

(same ID as the base Use Case ID, but with suffix E1, E2, etc., for each extending Use Case)

Use Case
Elaboration Phase

(indicate whether its initial, base or elaborated use case)

Additional Actors

(only list actors not listed in the extended use case)

Description

(brief)

Extended Use Case

(ID and name)

Extension Point
Guard Condition
Flow of Events

(step in Base Use Case where it is extended)


(pre-condition in the extended Use Case that causes it to execute)
1.
1.
2.
2.
3.
1.
2.

Conditional Flows
Post-conditions
Alternative Flows
Priority
Non-Functional
Requirements
Assumptions
Outstanding Issues
Source

(briefly describe alternative flows here for the Extending Use Case; extend this into complete flow of events in
an Alternative Use Case form if needed)
(High, Medium or Low)
(only those associated with this use case, if any)

10

Plantillas
Form for Included Use Cases
(An Included Use Case is generic and can be re-used and included in any other
Use Case, so it does not need to be associated with a specific Use Case)
Use Case ID

(prefix your Use Case IDs with IUC, to distinguish them from other Use Cases)

Use Case
Elaboration Phase
Description

(indicate whether its initial, base or elaborated use case)


(brief)

Including Use Cases


Pre-conditions
Flow of Events

(list all Use Cases that use this Included Use Case)
1.
1.
2.
2.
3.

Conditional Flows
Post-conditions
Alternative Flows
Priority
Non-Functional Requirements

1.
2.
(briefly describe alternative flows here for the Included Use Case; extend this into complete flow of events in an
Alternative Use Case form if needed)
(High, Medium or Low)
(only those associated with this use case, if any)

Assumptions
Outstanding Issues
Source

11

Use cases

Requirements

U1

U2

U3

U4

R1

R2
R3
R4
R5

12

Plantillas
Desing
Diagrama de Estructura

13

Diagrama de Flujo por cada mdulo del diagrama de


Estructura.

14

15

Plantillas
Testing
Test
Name

Operator Action (Entered)

Expected Results

Observed
Results

Pass/
Fail

16

Ejercicio
1. Online ATM Use Case Analysis
El Sistema a ser analizado es un simple Sistema de cajero
automtico en lnea. Este sistema mantiene la informacin
sobre los clientes , sus cuentas corrientes y los depsitos y
retiros que hacen, as como las consignaciones a otras
cuentas que pueden realizar ( una consignacin es un
pago directo que se hace entre dos cuentas bancarias )
Hay dos tipos de usuarios de los sistemas de : empleados
bancarios y gerentes de los bancos. Cada uno tiene
acceso a las diferentes partes del sistema ATM en lnea.
Tenga en cuenta que esto no significa que un gerente de
banco no puede actuar como un empleado de banco .
Guide to the Unified Process featuring UML, Java
and Design Patterns, John Hunt, Springer, 2003

17

Ejercicio
Tenga en cuenta cada una de las preguntas que se considera a continuacin:

Cules son las principales tareas del empleado ? Empleados del


Banco desearn saber la cantidad de dinero en una cuenta bancaria .
Ellos tambin quieren tener la posibilidad de depositar y retirar dinero
de los clientes . En el caso de la retirada de dinero se debe tener en
cuenta si hay fondos suficientes en la cuenta del cliente .
El empleado tiene que leer / escribir / cambiar cualquiera de la
informacin del sistema ? Como se trata de un sistema bancario , no
queremos que los empleados sean capaces de cambiar directamente
datos de la cuenta del cliente (slo se permite a un administrador para
hacer eso ) . Sin embargo, nosotros queremos que sean capaces de
depositar y retirar fondos que indirectamente va a cambiar los datos de
un cliente. No queremos que los empleados sean capaces de cambiar
el saldo total del cliente, pero s queremos que sean capaces de
acceder a l . Adems , queremos que un empleado sea capaz de
imprimir extractos bancarios de un cliente.
18

Ejercicio
El empleado tiene que informar al sistema sobre los
cambios externos? En este sistema particular, la respuesta
es no . Sin embargo, en un sistema bancario real que
podramos cambiar la informacin , como el cambio de
domicilio, el empleador o el estado marital. Nos gustara
que el gerente sea capaz de cambiar el nombre del cliente.
Desea que el empleado sea informado sobre los
cambios inesperados? Una vez ms, debido a la
simplicidad de esta aplicacin, la respuesta es no ; sin
embargo, en el sistema real , la respuesta no es tan clara .

19

Ejercicio
Se tiene planteado Interfaces grficas como las mostradas
a continuacin.

20

Ejercicio

21

Ejercicio

22

Ejercicio

23

Ejercicio

24

Ejercicio

25

Ejercicio

26

Ejercicio
Actividades
1. Identificar y escribir los requerimientos
2. Desarrollar la especificacin de requerimientos.
3. Identificar los requerimientos de testing
4. Identificar los casos de uso y realizar la especificacin
5. Completar la matriz de trazabilidad requerimientos vrs casos
de uso.
6. Diseo.
1. Diagrama de Estructura
2. Diagrama de Flujo
7. Cdigo en el lenguaje de Programacin Java
8. Ejecucin de casos de prueba.
27