Use Cases

The specific needs of the software are documented via Use Cases, combining diagrammatic and textual sensibilities.

Site Navigation.

bbc home page
About these pages
About bbc
Download bbc
Mailing lists
Frequently Asked Questions
bbc project documentation
Other resources and information

This site is hosted by

Connect to a BBS

Name: Connect to a BBS.
Description: The user makes a connection to a Bulletin Board System.
Scope: The network.
Level: Primary task.
Preconditions: The client must have read its configuration file and initialized its state.
Success Postcondition: The user will be connected to the desired BBS.
Failure Postcondition: The user will be provided a message of the failure and probable cause.
Primary Actor: The user.
Trigger: The user selects the Connect option.

Main Path

Extensions

Diagram

Disconnect from a BBS

Name:Disconnect from a BBS.
Description:The user disconnects from a Bulletin Board System.
Scope:The network.
Level:Primary task.
Preconditions:The client must be connected to a BBS.
Success Postcondition:The connection is closed; data related to it has been updated.
Failure Postcondition:This is a Can't Fail Use Case.
Primary Actor:The client user.
Trigger:The user requests that a BBS connection be closed.

Main Path:

Extensions

Diagram

Create a Filtering Rule

Name: Create a Filtering Rule
Description: The user sets criteria for treatment of messages sent from the BBS.
Scope: The text processor
Level: Primary task
Preconditions: The client must have a record of known users and rooms.
Success Postcondition: The rule will be stored for pre-display processing by the client
Failure Postcondition: The client warns of the resource failure which prevented the rule creation.
Primary Actor: The client user.
Trigger: The user requests creation of a new filtering rule.

Main path

Extensions

Diagram

Edit a Filtering Rule

Name: Edit a Filtering Rule
Description: The user modifies an existing filtering rule.
Scope: The text processor
Level: Primary task
Preconditions: At least one filtering rule must exist.
Success Postcondition: The modified rule will replace the previous version.
Failure Postcondition: The client warns of the resource failure which prevented the rule creation.
Primary Actor: The client user.
Trigger: The user selects an existing rule and chooses to edit it.

Main path

Extensions

Diagram

Delete a Filtering Rule

Name: Delete a Filtering Rule
Description: The user removes a filtering rule.
Scope: The text processor
Level: Primary task
Preconditions: At least one filtering rule must exist.
Success Postcondition: The deleted rule will no longer be applied to incoming text.
Failure Postcondition: The client warns of the resource failure which prevented the rule deletion.
Primary Actor: The client user.
Trigger: The user selects an existing rule and chooses to delete it.

Main path

Extensions

Diagram

Modify Known List Sequence

Name: Modify Known List Sequence
Description: The user changes the order in which rooms with unread notes are seen.
Scope: The BBS navigation
Level: Primary task
Preconditions: The client must have stored a list of existing rooms.
Success Postcondition: The new room sequence is used when presenting the user with new rooms to read.
Failure Postcondition: The client warns of the resource failure which prevented the resorting of rooms.
Primary Actor: The client user.
Trigger: The user invokes the known room list and chooses to edit it.

Main path

Extensions

Diagram