Example 1: System-Oriented Use Case Diagram

Request Mail Shipment

Table Maintenance

Register Shipping Request

of Correspondence Area
User Maintenance of
Master Tables

Maintenance of
Contractors
Management of the Correspondence Request

Administration of
Acceptance of Application Franking Machines
Mail shipment Department Processing

Documentary

Maintenance of
Directory of
Modification of Recipients (DD)
Shipping Requests
Correspondence

Administration of
Mail delivery Rate Matrix
the Contractor

Caso de Uso 1:CU-01 Registrar Solicitud de envío de Correspondencia

Allow the user area to carry out maintenance (registration, modification or cancellation) of the
Correspondence Request (SC) generated for the sending of documents, printed materials and
publications or other correspondence through the use of messaging services
of postal mail for the local, national, and international scope.
Functional Requirement
RF-01 Registration request for mailing correspondence
Involved Actors
USER AREA Request for shipping registration
Correspondence
Pre-Conditions
Have all the tables required by this option (Recipients, Types) registered in the system.
of correspondence, countries, etc.
Have the information to enter and/or update.
Main Process Flow
Basic Flow The USER AREA logs into the system
TRADE and heads towards the created option for
this end, the Registration window will be displayed
Request for correspondence shipment.
The following groups are distinguished from
information:
1. Datos Generales
2. Request Characteristics

Create a New Record:

- The window with the fields will be displayed
in white
- The USER AREA enters the data
 corresponding y select the
recipients.
- The USER AREA chooses to record the
information, if all were entered
mandatory fields and are fulfilled
validations will save the information.
- The system records the SC with the status
registered

Make a Modification of the Registry:

- The USER AREA selects one
registration from the SC list and
the fields will be filled automatically
with the corresponding information of the
selected application.
- The USER AREA modifies the data
required.
- The USER AREA chooses to record the
information, if all were entered
mandatory fields and they are met
validations will save the information.
- The status of the SC does not change.

Make a Cancellation:
- The USER AREA selects one or
more records from the SC list.
- The USER AREA chooses to Cancel
Request.
- The system changes the status of all the
selected SC records from
registered to canceled.

Make an Authorization:
- The USER AREA selects one or
more records from the SC list.
- The USER AREA chooses to Authorize
Request.
- The system changes the status of all the
selected SC records from
registered to authorized.
Alternative Flow If data validation fails, the
TRADE will request to enter or correct the
required information.
Post-Conditions
Insert and/or update the SC in the defined header and detail tables.
Audit trails generated.
Example 2: Use Case Diagram of the System (Graph)
List of System Use Cases

Packages CUS Code Actor

Maintenance CUS01 Warehouse Maintenance Administrator
CUS02 Maintenance of Article Lines
CUS03 Maintenance of Measurement Units
CUS04 Maintenance of Option Tables
CUS05 Equipment and Components Revenue for New Entries Operator
CUS06 Equipment Assignment
CUS07 Equipment Return
CUS08 Departures Due to Resignation

CUS09 Control of Equipment and Components

CUS10 Entry of Equipment or Components for Repair
CUS11 Equipment or Components Exit for Repair
Articles CUS12 Maintenance of Items Operator
CUS13 Income from Articles
CUS14 Item Outputs
CUS15 Item Stock
CUS16 Consolidated Stock of Items
Queries and Reports CUS17 Equipment History Operator
CUS18 Components History
CUS19 Kardex by Article
CUS20 Movements by Reason
Security CUS21 User Maintenance Administrator
CUS22 User Profile Maintenance
CUS23 Profile Configuration
1.1 Specifications of the System Use Cases
1. Name of the System Use Case CUS.01 Warehouse Maintenance
2. Description of the Use Case
The system will allow the registration, modification, or inquiry of the data of the Warehouses.
Artículos, para el respectivo control de stock.
3. Actor(s)
Administrator
4. Preconditions
The administrator must have the responsibility to create new warehouses as needed.
required for the management of the Articles.
5. Post conditions
It will be in Active status so that it can be used to record stock movements of
articles.
6. Flow of events
No. Actor's Action System Response
1 Start use case entering System presents the List of Warehouses
to the Maintenance option registered (ver 1.a).
of Warehouses.
2 Consult, Enter, Modify and The System presents a screen with the data of
Remove the description data and Warehouse (ver 2.a) and validate the data upon saving (ver
situation; and select option 3.a.).
Record. Save data in the system, display message 'Warehouse'
It was successfully recorded in the System.
7. Subflows and Alternative Flows
1.a. Present a list of registered Warehouses
1.a.1. Show the Warehouse List with the following data:
Warehouse Code
Description of the Warehouse
Situation
The available options are:
New Warehouse Data Registration
Modify warehouse data
Delete data from the Warehouse
Print Warehouse List

2.a. Show basic data of Warehouses

[Link] the Warehouse data isNew:
Display screen to enter Warehouse data:
Warehouse Code (Correlative)
Warehouse Description
Situation (Active by default)
If all the data is available, the option is enabled: Save (Save and return to the List)
The Cancel button is enabled at all times and allows you to exit the screen of
data, returning to the List.
[Link] the Warehouse is already registered (Modify):
Screen to modify Warehouse data and only the following are modified
data:
Warehouse Code (blocked)
Warehouse Description
Situation
The option is enabled: Save (Validates, Saves, and returns to the List)
The Cancel button is enabled at all times and allows you to exit the screen of
data, returning to the List.
[Link] the Warehouse is registered and you want to delete it:
Show data screen of the blocked Warehouse:
Warehouse Code
Warehouse Description
 Situation
A message is displayed: 'Are you sure you want to delete the warehouse?'
If accepted, the record is deleted after validating that there are no movements.
of items in the Warehouse to Remove.
If it is Cancel, it will return to the List

3.a. Validate warehouse data

3.a.1. In the New and Modify option:
Validate that it must have all the registered data.
Verify that there is no other record with the same Warehouse Description. If there is, then ...
A message should be presented: "A Warehouse with the Description already exists"
3.a.2. In the Delete option:
Validate that there are no item movements in the Warehouse. If there are, it must
presentar un mensaje “Almacén tiene movimientos de Artículos, No se puede Eliminar”

8. Associated requirement (Functional, Non-Functional)

8.a.1Functional
According to RQ.01 Stock Control of Items
8.a.2 Non-Functional
Web Environment
Use Ajax technology and jQuery.
Three-layer architecture at minimum
C# programming language
Visual Studio version 2010
SQL database engine version 2008 or higher
9. User interface prototype
See "I.01"