International Internet Cafécafesource.sourceforge.net/phase1/useCaseDescriptions.pdf ·...

International Internet Café

Use Case Descriptions

Use Case Name: Add Billing Rate

Triggering Event: A new billing rate has been requested.

Brief Description: The System Administrator adds a new billing rate to the system so that defines how a customer is to be billed for his/her usage.

Actors: System Administrator

Related Use Cases:

Stakeholders: Customer: a new way of being charged for usageMarketing Department: a new way of charging customers, promotionalBranch Manager: another measurement for customer usage

Preconditions: Billing Rate must not exist

Post Conditions: Billing Rate addedSystem Message created

of 73Revised: February 25, 2007


Use Case Name: Add Branch Location

Triggering Event: A new branch has opened and requires identification.

Brief Description: The System Administrator adds the new branch into the system so that it's tracking information can be kept.


Related Use Cases:

Stakeholders: Customer: a new branch to visitMarketing Department: branch promotion for customers in the area

Preconditions: Branch Location must not exist

Post Conditions: Branch Location addedSystem Message created



Use Case Name: Add Customer

Triggering Event: New Customer would like to start using the services of the Internet Café.

Brief Description: A new customer signs up for an account with International Internet Café for Internet use, he/she must provide their home contact information, and a credit card for billing rates.

Actors: Customer

Related Use Cases: Includes: Customer Login

Stakeholders: Customer: now able to use the Internet CaféMarketing Department: more customer statistics to trackBranch Manager: another customer to serve

Preconditions: Customer must not exist

Post Conditions: Customer is createdInternet Usage transaction createdSystem Message created



Use Case Name: Ban Customer

Triggering Event: A customer has broken the terms of agreement.

Brief Description: A customer has broken the terms of agreement for usage in the café – the branch manager has been notified – and the customer will be banned from logging into the system.

Actors: Branch Manager

Related Use Cases:

Stakeholders: Customer: no longer able to use the Internet café

Preconditions: Customer has broken the terms of use agreement.

Post Conditions: Customer is no longer able to login and use the systemSystem Message created



Use Case Name: Bill Customers

Triggering Event: End of day.

Brief Description: End of the day, all customer transactions are totaled up, and a bill for the customer is created.

Actors: Time

Related Use Cases:

Stakeholders: Customer: will be getting billed for resources used at the café

Preconditions: Customer transactions are completed

Post Conditions: Customer bill createdSystem Message created



Use Case Name: Bill Printed Document

Triggering Event: Customer has printed a document to one of the café printers.

Brief Description: Printed Document transaction is created for the pages printed.

Actors: Customer

Related Use Cases:

Stakeholders: Customer: will be getting billed for document printed

Preconditions:

Post Conditions: Customer transaction createdSystem Message created



Use Case Name: Credit Printed Document

Triggering Event: Customer has printed a document to one of the café printers that failed to print correctly.

Brief Description: Customer must approach one of the branch managers and request a refund for the document that failed to print. Branch manager will login, and credit the document to the customer's account.

Actors: Branch ManagerCustomer

Related Use Cases:

Stakeholders: Customer: will be getting a credit for document printed that failed

Preconditions: Customer must have a Printed Document transaction on file

Post Conditions: Printed Document transaction credit createdSystem Message created



Use Case Name: Customer Log Off

Triggering Event: Customer Logs off of the system

Brief Description: Customer no longer requires the services of the café and logs off of the system

Actors: Customer

Related Use Cases:

Stakeholders: Customer: will be billed for time used

Preconditions: Customer must have an open Internet Usage transaction

Post Conditions: Internet Usage transaction closedSystem Message created



Use Case Name: Customer Login

Triggering Event: Customer logs into the system

Brief Description: Customer arrives at the café and logs in to use the service

Actors: Customer

Related Use Cases:

Stakeholders: Customer: Internet Usage transaction started for which he/she will be billed

Preconditions: Customer does not have an open connection at another locationCustomer has a valid credit cardCustomer has not been suspended (requires account correction)Customer has not been banned (not allowed to connect again)

Post Conditions: Customer connection is open and available for useSystem Message created



Use Case Name: Suspend Customer

Triggering Event: Time.

Brief Description: Nightly customer credit cards, and transactions are checked. Customers that haven't logged into the system in a long time (defined by system administrator) or that have expired credit cards will be suspended.

Actors: Time

Related Use Cases:

Stakeholders: Customer: will be notified of

Preconditions: Customer has not logged into the system in a predefined period of timeCustomer has an expired credit card on file

Post Conditions: Customer will be notified of “infractions” in the systemCustomer will be suspended from using the system until corrections have been madeSystem Message created



Use Case Name: Daily Sales Report

Triggering Event: End of day.

Brief Description: Nightly completed customer transactions are compiled into a report that lists the details of the transactions for each branch (new customers, customers that logged in, time billed, printed documents, etc).


Related Use Cases:

Stakeholders: Branch Manager: receives the details of the sales completed at his/her branch

Preconditions: Customer transactions for the day have been completed

Post Conditions: Report printedSystem Message created



Use Case Name: Delete Billing Rate

Triggering Event: A billing rate is no longer required

Brief Description: System administrator removes billing rate from the system that is no longer required


Related Use Cases:

Stakeholders: Customer: a new way of being charged for usageMarketing Department: a new way of charging customers, promotionalBranch Manager: another measurement for customer usage

Preconditions: Billing Rate exists

Post Conditions: Billing Rate removedSystem Message created



Use Case Name: Delete Branch Location

Triggering Event: A Branch Location has been closed

Brief Description: System administrator “removes” branch location from the system. It is important to note that the branch will not be deleted, but disabled


Related Use Cases:

Stakeholders: Customer: branch closed and unable to visitMarketing Department: branch promotion for customers in the area

Preconditions: Branch Location exists

Post Conditions: Branch Location removedSystem Message created



Use Case Name: Disconnect Customer

Triggering Event: Customer has been connected for too long, consumed too much bandwidth, or has been idle for a specified period of time.

Brief Description: System recognizes that the customer has been connected for an inappropriate amount of time. Customer will automatically be logged off.

Actors: Network System Monitor

Related Use Cases: Includes: Customer Log off

Stakeholders: Customer: automatically disconnectBranch Manager: potential customer abuse

Preconditions: Internet Usage transaction open

Post Conditions: Customer Internet Usage transaction closedSystem Message created



Use Case Name: Look up customer statistics

Triggering Event: Marketing department requires a report on customer specifics.

Brief Description: Marketing manager builds a report with the specific customer details that are required for the promotion that they are working on

Actors: Marketing Manager

Related Use Cases:

Stakeholders: Marketing Department: report on customer statistics for promotional purposes

Preconditions:

Post Conditions: Report printedReport Parameters updatedSystem Message created



Use Case Name: Lookup Customer Usage

Triggering Event: Branch Manager requires report on the Branch Locations usage by customer.

Brief Description: Branch Manager generates the usage report for his/her branch, if required he/she may be able to view more detail about the customers usage for the period of time that he/she is looking up


Related Use Cases: Extends: Ban Customer

Stakeholders: Branch Manager: looking for loyal customers, or potential system abuse

Preconditions:




Use Case Name: Lookup Websites Visited

Triggering Event: Marketing Department requires statistics on web traffic usage.

Brief Description: Marketing Manager builds report with selected parameters for web sites visited by location for use in promotions

Actors: Marketing Manager

Related Use Cases:

Stakeholders: Marketing Department: customer profiling on web usage

Preconditions:




Use Case Name: Manage System Parameters

Triggering Event: Branch parameters need to be updated.

Brief Description: The Branch Manager has decided that the system parameters need to be updated to provide a better service to it's customers.


Related Use Cases:

Stakeholders: Customer: ability to connect, and for how long will be changed

Preconditions:

Post Conditions: Branch operational parameters are updatedSystem Message created



Use Case Name: Record Web Sites Visited


Brief Description: System will read through logs created on web traffic logs and generate statistics on customer usage

Actors: Time

Related Use Cases:

Stakeholders: Customer: web sites visited will be recorded for analysis (anonymously)Marketing Department: gather customer demographics for promotional purposes

Preconditions:

Post Conditions: Sites Visited created



Use Case Name: Report Security Log

Triggering Event: System Administrator is required to review system logs.

Brief Description: System Administrator builds required report on system logs looking for potential problems


Related Use Cases:

Stakeholders:

Preconditions:

Post Conditions: Report printed Report Parameters updatedSystem Message created



Use Case Name: Request Password

Triggering Event: Customer requires a new password.

Brief Description: Customer has forgotten password his/her password, and has put in a request for a new password. A security question will be required.

Actors: Customer

Related Use Cases:

Stakeholders: Customer: new password will set for his/her account

Preconditions:

Post Conditions: Customer password updatedSystem Message created



Use Case Name: Unsubscribe

Triggering Event: Customer no longer wants to be a user on the system

Brief Description: Customer no longer requires the services of the café and requests to be removed from the system

Actors: Customer

Related Use Cases: Extends: Customer Log off

Stakeholders: Customer: customer will no longer be able to use the services in the café

Preconditions: Customer's has no outstanding transactions

Post Conditions: Customer deleted from the systemSystem Message created



Use Case Name: Update Address Validation

Triggering Event: New address validation information is available

Brief Description: System administrator uploads the address data into the system


Related Use Cases:

Stakeholders: Customer: new address validation added, able to create an account if living in a newly developed areaSystem Administrator: address validation updatedBranch Manager: new address validation added, more customers

Preconditions:

Post Conditions: Address Validation information updatedSystem Message created



Use Case Name: Update Billing Rate

Triggering Event: Billing rates have been reviewed, and need to be updated

Brief Description: System administrator changes the current billing rates as required


Related Use Cases:

Stakeholders: Customer: billing rates have been changedSystem Administrator: billing rates updatedBranch Manager: billing rates updated

Preconditions:

Post Conditions: Billing rates updatedSystem Message created



Use Case Name: Update Branch Location

Triggering Event: Branch location has moved

Brief Description: System administrator changes the current address of branch that has moved


Related Use Cases:

Stakeholders: Customer: branch location has changedSystem Administrator: branch location has changedBranch Manager: branch location has changed properly in the systemMarketing Department: branch location has changed, will sales be affected, new customers in the area

Preconditions:

Post Conditions: Branch location updatedSystem Message created



Use Case Name: Update Customer

Triggering Event: Customer's information has changed

Brief Description: Customer recognizes that his/her personal/credit card information has changed since last connected, and updates the file with the current information.

Actors: Customer

Related Use Cases:

Stakeholders: Customer: personal information is currentMarketing Department: customer has moved? Send out promotions?

Preconditions:

Post Conditions: Customer information updated



Use Case Name: View Account History

Triggering Event: Customer wants to see his/her transactions with the café

Brief Description: Customer logs into the café and reviews the transactions that he/she has placed over time.

Actors: Customer

Related Use Cases:

Stakeholders: Customer: billing information is correct

Preconditions: Customer exists

Post Conditions:



Use Case Name: Login

Triggering Event: System user needs to gain access to the system

Brief Description: User enters their username and password to login to the system

Actors: User

Related Use Cases:

Stakeholders: System Administrator: potential system abuse

Preconditions: User must exist in the system

Post Conditions: User has been logged in and has access to a specified set of programs



Use Case Name: Rotate System Messages


Brief Description: The oldest System Messages will be deleted, next oldest will be moved to oldest, etc. Current System Messages will be moved into the newest block of rotated messages, and then deleted from the current System Messages table.

Actors: Time

Related Use Cases:

Stakeholders: System Administrator: disk space isn't completely consumed by system messages, old system messages/warnings may be deleted before reviewed

Preconditions:

Post Conditions:



Use Case Name: Bill Printed Document (Host/Hostess)

Triggering Event: Customer has printed a document to one of the café printers.

Brief Description: Printed Document transaction is created for the pages printed, this billing is not automatic, it requires a Host/Hostess to intervene and bill the customer by filling out an electronic form.

Actors: Customer

Related Use Cases:

Stakeholders: Customer: will be getting billed for document printed

Preconditions:

Post Conditions: Customer transaction createdSystem Message created



Use Case Name: Add User

Triggering Event: A new is required for access to the system.

Brief Description: The System Administrator adds the new user to the system, setting him/her up with a default password (must be changed at first login).


Related Use Cases:

Stakeholders: System User: now able to log into the system

Preconditions: User must not exist

Post Conditions: New User addedSystem Message created



Use Case Name: Update User

Triggering Event: User information has been changed.

Brief Description: The System Administrator updates the user information as required, this could be any one of username, the user's full name, account status, or the password.


Related Use Cases:

Stakeholders: System User: personal information has been updated.

Preconditions: User must exist

Post Conditions: User updatedSystem Message created



Use Case Name: Delete User

Triggering Event: User has left the company an need to be removed from the system.

Brief Description: The System Administrator deletes the user so they will not be able to login from any other locations.


Related Use Cases:

Stakeholders: System User: no longer able to login to the system.

Preconditions: User must exist

Post Conditions: User removed from the systemSystem Message created



Use Case Name: Add Group

Triggering Event: A new group of users is required

Brief Description: The System Administrator adds the new group to the system, the new group will be assigned a set of users that can execute the use cases that belong to the group.


Related Use Cases:

Stakeholders: System User: able to execute specific use casesManagement: refined access to specific use cases

Preconditions: Group must not exist

Post Conditions: New User addedSystem Message created



Use Case Name: Update Group

Triggering Event: A group need to be updated.

Brief Description: The System Administrator updates the details of the group.


Related Use Cases:

Stakeholders: System User: able to (not)execute specific use cases

Preconditions: Group must exist

Post Conditions: Group updatedSystem Message created



Use Case Name: Delete Group

Triggering Event: A group need to be removed.

Brief Description: The System Administrator removes the group from the system. The group must not be a part of any use cases, or have any users in the group.


Related Use Cases:

Stakeholders: System User: group will no longer existManagement: group will no longer exist

Preconditions: Group must exist

Post Conditions: Group updatedSystem Message created



Use Case Name: Update User Password

Triggering Event: Users password has expired.

Brief Description: When the User logs into the system with a password that has expired, he/she will be required to update the password.


Related Use Cases:

Stakeholders: System User: password updated

Preconditions: User exists

Post Conditions: User's password updatedSystem Message created



Use Case Name: Update System Action

Triggering Event: Permissions need to be refined for a specific action from within the system.

Brief Description: System Administrator modifies the group that has access to the specific system action.


Related Use Cases:

Stakeholders: System User: permissions updated

Preconditions: System Action exists

Post Conditions: System Action permissions updatedSystem Message Created



Use Case Name: Print Account History

Triggering Event: Customer wishes to print his/her account history.

Brief Description: Customer selects a date range to print the account history, and presses the print button.

Actors: Customer

Related Use Cases:

Stakeholders: Customer: account history printed

Preconditions: Customer is logged in

Post Conditions: Customer's account history is printed



Use Case Name: Add Tax Rate

Triggering Event: A new tax rate is required.

Brief Description: System administrator adds a new tax rate for the required provinces.


Related Use Cases:

Stakeholders: Branch Manager: correct tax rates are being chargedCustomers: correct tax rates are being charged

Preconditions: Tax rate for specific province exists

Post Conditions: New tax rate is added, on the next cycle of customer bills will be charged the new rate



Use Case Name: Update Tax Rate

Triggering Event: Tax rate has changed, and requires updating.

Brief Description: System administrator updates the specific tax rate for the specific provinces.


Related Use Cases:


Preconditions: Tax rate exists

Post Conditions: Tax rate is updated, on the next cycle of customer bills will be charged the new rate



Use Case Name: Delete Tax Rate

Triggering Event: A tax rate is no longer required

Brief Description: System administrator deletes the specific tax rate for the specific province.


Related Use Cases:


Preconditions: Tax rate exists

Post Conditions: Tax rate is deleted, on the next cycle of customer bills will not be charged the old rate



Use Case Name: Credit Internet Usage

Triggering Event: Customer has disputed charges made on their account, and requires a refund.

Brief Description: Customer must approach one of the branch managers and request a refund. Branch manager will login, and credit the the customer's account.

Actors: Branch ManagerCustomer

Related Use Cases:

Stakeholders: Customer: will be getting a credit for mischarge to their account

Preconditions: Customer must have an Internet Usage transaction on file

Post Conditions: Internet Usage Transaction transaction credit createdSystem Message created


International Internet Cafécafesource.sourceforge.net/phase1/useCaseDescriptions.pdf ·...

Documents

Transcript of International Internet Cafécafesource.sourceforge.net/phase1/useCaseDescriptions.pdf ·...