BSOD

High Level Design Document

1 - Project Summary ............................................................................................................................................... 1 1.1 - Organizational Profile................................................................................................................................. 1 1.2 - Brief Outline of the Situation ................................................................................................................. 2 1.3 - Characteristics of the Project.................................................................................................................. 2 2 - High Level System Requirements ..................................................................................................................... 3 3 - High Level System Design (UML) ................................................................................................................... 4 3.1 - Use Cases.................................................................................................................................................... 4 3.1.1 - Actors................................................................................................................................................... 4 3.1.2 - Use Case Index .................................................................................................................................... 5 3.1.2.1 - Generic Use Case Index ............................................................................................................... 5 3.1.2.2 - Manage Document Use Case Index.............................................................................................. 6 3.1.2.3 - Manage Report Use Case Index ................................................................................................... 7 3.1.2.4 - Manage User Use Case Index....................................................................................................... 7 3.1.2.5 - Manage Reminder Use Case Index .............................................................................................. 8 3.1.3 - High Level Use Case Descriptions...................................................................................................... 8 3.1.3.1 - Generic Use Case Descriptions .................................................................................................... 8 3.1.3.2 - Manage Document Use Case Descriptions .................................................................................. 9 3.1.3.3 - Manage Report Use Case Descriptions ...................................................................................... 16 3.1.3.4 - Manage User Use Case Descriptions.......................................................................................... 18 3.1.3.5 - Manage Reminder Use Case Descriptions ................................................................................. 19 3.1.4 - Use Case Diagrams............................................................................................................................ 22 3.1.4.1 - Generic Use Cases ...................................................................................................................... 22 3.1.4.2 - Manage Document Use Cases .................................................................................................... 23 3.1.4.3 - Manage Report Use Cases.......................................................................................................... 24 3.1.4.4 - Manage User Use Cases ............................................................................................................. 25 3.1.4.5 - Manage Reminder Use Cases ..................................................................................................... 25 3.1.5 - Other Diagrams.................................................................................................................................. 26 3.1.5.1 - Create, Modify and Send RAS to BPMS Flow Chart ................................................................ 26 3.2 - Report Requirements ................................................................................................................................ 27

- ii -

1 - Project Summary
1.1 - Organizational Profile

The Information Technology Service Branch's (ITSB) mandate is to provide IM/IT support to PWGSC and its modernization initiatives and spearhead the implementation of the government-wide IT Shared Services initiative. The Application Management & Information Technology Operational Services (AM&ITOS) sector's mandate is to enable the business success of PWGSC by being a valued partner in the delivery of enterprise IT operational services. Managers and director's administrative assistants procure resources by making requests for acquisition services to the Contract Management and Administration Services (CMAS) division. The directors, directors' administrative assistants and managers of AM&ITOS are the users of the contract repository system to be implemented. The Integrated Operational Support Services (IOSS) directorate provides centralized operational support to AM&ITOS in the areas of contracting, HR, finance, and business services. The IOSS are the owners and administrators of the system. The Business Planning and Management Services (BPMS) Sector enables ITSB's operation and delivery of both PWGSC's internal IM/IT functions and the IT Shared Services. The Contract Management and Administrative Services (CMAS) group is responsible for the procurement planning, procurement initiation and contract administration for all contracting activity conducted with the Branch, including: professional services, hardware, software, and local item purchasing. The CMAS is -1-

responsible for providing contracts or task authorizations against contracts for requests for acquisition services made by managers or director's administrative assistants in AM&ITOS and other sectors.

1.2 - Brief Outline of the Situation

Today, the IOSS must collect contract-related documents from a variety of sources of information in order to provide resource planning services to AM&ITOS staff: shared drives, emails, spreadsheets, etc. This process is slow, outdated and prone to human error. The IOSS requires a central repository for AM&ITOS contract-related documents, RASs, TAs that will provide a history of theses documents and the modifications to their information. The IOSS also needs to query and generate reports on all this data in order to provide proactive resource planning to AM&ITOS staff.

1.3 - Characteristics of the Project

Project Name: Contract Repository System (CRS) Project Purpose: To create a central repository for AM&ITOS contract-related documents, RASs, TAs and contracts, that will provide a history of theses documents and the modifications to their information. The system will allow users to query and generate reports on all data fields in order to be used for resource planning purposes. Team Name: Blue Screen of Death (BSOD) Team Organization Chart:

-2-

2 - High Level System Requirements

The Contract Repository System (CRS) must satisfy the following requirements:

Implement IT security safeguards in order to comply with the Government of Canada Management of Information Technology Security (MITS) Operational Security Standard, Allow the user to view the graphical user interface in her official language of choice in order to comply with the Official Languages Act and Federal Policy (93-8E), Restrict access the system via the use of user credentials: user name and password, If possible, implement a single sign-on functionality in order to automatically validate a user's credentials against the user information in the User Directory System (no need to manually login), Restrict access to the information and functionality of the system via the use of user profiles: administrator, requester (manager and administrative assistant) and viewer, Allow the administrator of the system to create users and manage their user profile and access to the system, Allow the user to input and store Request for Acquisition Services (RAS), Contract and Task Authorization (TA) information in the system, Record all changes to the data contained within the system, the date, time and user who performed those changes: user, Request for Acquisition Services (RAS), Contract and Task Authorization (TA) information for auditing purposes, Automate the sending of RAS information to BPMS via system-generated email messages and attachments, Allow the user to generate and export canned and ad-hoc reports on the Request for Acquisition Services (RAS), Contract and Task Authorization (TA) information contained within the system, If time permits the implementation of this feature, allow the user to create reminders reminding her when a Contract or TA is due for renewal, etc., Store the system's information in a central relational database management system, Install the software component (user interface and business logic) of the system locally on each user's workstation computer,

-3-

3 - High Level System Design (UML)

The BSOD has chosen to describe the high level system design by using the Unified Modeling Language (UML) which defines each functionality of the system as a "use case" and each human and IT system that interacts with the system as an "actor". Both concepts are described visually by using use case diagrams and textually by using use case descriptions. * Note: The database entity-relational diagram (ERD), graphical user interface (GUI) and report mock-ups will be included in the Detailed System Design document that will be created during the next round of Top Dogs Competition.

3.1 - Use Cases

3.1.1 - Actors
The following table lists all of the actors (human and IT systems) that will be interacting with the system. Actor Name: User Base: Administrator Requester Viewer AM&ITOS Directors User Directory System N/A Email System N/A

Members of IOSS AM&ITOS Managers and Administrative Assistants

Roles :

Manage Users Generate reports

Create RAS Track and view RAS, TA and contracts Generate reports

Track and Authenticate user Transmit view RAS, TA credentials against email and contracts the user directory. messages to Generate recipients. reports

Goals:

Give access to the system to the AM&ITOS directors, managers and administrative assistants. Provide

Acquire Resources via RAS Provide Proactive Resource Planning

Provide Proactive Resource Planning

-4-

Proactive Resource Planning Information All user, RAS, TA and Access Contract Scope: information in system Administrative Assistants: Only RAS, TA and Contract information in user's directorate

Only RAS, TA and Contract information in user's directorate

Managers: Only RAS, TA and Contract information in user's division RASs TAs Contracts Reports

Input:

User Information

Success or failure message.

Success or failure message. Email message

Output:

Reports

Reports

User credentials

3.1.2 - Use Case Index

3.1.2.1 - Generic Use Case Index Use Use Case Name Case ID 1 2 25 26 Login Logout View Online help Set User Interface Language Preference Primary Actor Administrator/Requester/Viewer/User Directory System Administrator/Requester/Viewer Administrator/Requester/Viewer Administrator/Requester/Viewer Scope Complexity Priority In In In In Low Low Medium Medium 1 1 2 1

-5-

3.1.2.2 - Manage Document Use Case Index Use Case ID Use Case Name Primary Actor Scope Complexity Priority 3 Create Document Requester In Medium 1 3.1 Create RAS Requester In Medium 1 3.1.1 Create RAS from Existing RAS Requester In Medium 2 4 Cancel Document Requester In Medium 1 4.1 Cancel RAS Requester In Medium 1 5 Send Document Requester/Email System In Medium 1 5.1 Send RAS to BPMS Requester/Email System In Medium 1 6 Find Document Requester/Viewer In Medium 1 6.1 Find RAS Requester/Viewer In Medium 1 6.2 Find TA Requester/Viewer In Medium 1 6.3 Find Contract Requester/Viewer In Medium 1 7 View Document Requester/Viewer In Medium 1 7.1 View RAS Requester/Viewer In Medium 1 7.2 View TA Requester/Viewer In Medium 1 7.3 View Contract Requester/Viewer In Medium 1 8 Import and Link File to Document Requester In Medium 1 8.1 Import and Link TA File to RAS Requester In Medium 1 8.2 Import and Link Contract File to RAS Requester In Medium 1 9 Update or Amend Document Requester In Medium 1 9.1 Update or Amend RAS Requester In Medium 1

-6-

3.1.2.3 - Manage Report Use Case Index Use Case ID 10 11 12 13 Use Case Name Generate Report Print Report Export Report Create Report Template Create Report Template from Existing Report Template Modify Report Template Delete Report Template Primary Actor Scope Complexity Priority Medium Medium Medium High 1 1 1 1

Administrator/Requester/Viewer In Administrator/Requester/Viewer In Administrator/Requester/Viewer In Administrator/Requester/Viewer In

13.1

Administrator/Requester/Viewer In

Medium

14 15

Administrator/Requester/Viewer In Administrator/Requester/Viewer In

High Low

1 1

3.1.2.4 - Manage User Use Case Index Use Case ID 16 16.1 17 18 19 Use Case Name Create User Create User from Existing User Modify User Find User View user Primary Actor Administrator/User Directory System Administrator/User Directory System Administrator Administrator Administrator Scope Complexity Priority In In In In In Low Low Low Medium Low 1 2 1 2 1

-7-

3.1.2.5 - Manage Reminder Use Case Index Use Case Use Case Name ID 20 Create Reminder Create Reminder from 20.1 Existing Reminder 21 Modify Reminder 22 Delete Reminder 23 View Reminder Send Reminder to 24 User 25 View Online help Set User Interface 26 Language Preference Primary Actor Requester/Viewer Requester/Viewer Requester/Viewer Requester/Viewer Requester/Viewer Scope Complexity Priority Out Out Out Out Out High High High Low Medium High Medium Medium 3 3 3 3 3 3 2 1

Requester/Viewer, Email System Out Administrator/Requester/Viewer In Administrator/Requester/Viewer In

3.1.3 - High Level Use Case Descriptions

3.1.3.1 - Generic Use Case Descriptions Use Case ID: Use Case Name: Actors: Type: 1 Login

Administrator/Requester/Viewer (Initiator), User Directory System Primary The use case begins when an Administrator, Requester or Viewer accesses the system, the system asks the actor for their user credentials, the actor provides the system with their credentials, the Description: system verifies that the credentials are valid and the system allows the Administrator, Requester or Viewer to access the information within the system. 2 Logout Administrator/Requester/Viewer (Initiator) Primary The use case begins when an Administrator, Requester or Viewer asks the system to end her user session; the system ends the user session.

Use Case ID: Use Case Name: Actors: Type: Description:

-8-

Use Case ID: Use Case Name: Actors: Type: Description: Use Case ID: Use Case Name: Actors: Type:

25 View Online help Administrator/Requester/Viewer (Initiator) Primary The use case begins when the Administrator, Requester or Viewer asks the system to display the help documentation and the system displays the help documentation. 26 Set User Interface Language Preference

Administrator/Requester/Viewer (Initiator) Primary The use case begins when the Administrator, Requester or Viewer asks the system to change her user interface language preference, the systems displays a list of alternative languages, the user Description: selects the language of her choice and the system changes the user interface language preference to match the chosen language.

3.1.3.2 - Manage Document Use Case Descriptions Use Case ID: Use Case Name: Actors: Type: Cross-Ref.: 3 Create Document

Requester (Initiator) Primary 3.1, 3.1.1 The use case begins when a Requester asks the system to create a new document. The system provides a blank document form to the Requester. The Requester enters the required information Description: and asks the system to save the new document. The system saves the new document and assigns the status of "Draft" to it.

-9-

Use Case ID: Use Case Name: Actors: Type: Cross-Ref.:

3.1 Create RAS

Requester (Initiator) Primary 3, 3.1.1 The use case begins when a Requester asks the system to create a new RAS. The system provides a blank RAS form to the Requester. The Requester enters the required information and Description: asks the system to save the new RAS. The system saves the new RAS and assigns the status of "Draft" to it. Use Case ID: Use Case Name: Actors: Type: Cross-Ref.: 3.1.1 Create RAS from Existing RAS

Requester (Initiator) Secondary 3, 3.1 The use case begins when a Requester asks the system to create a new RAS from the data contained in an existing RAS. The system provides a prefilled RAS form to the Requester. The Description: Requester modifies the required information and asks the system to save the new RAS. The system saves the new RAS and assigns the status of "Draft" to it. 4 Cancel Document

Use Case ID: Use Case Name: Actors: Type: Cross-Ref.:

Requester (Initiator) Primary 4.1 The use case begins when a Requester asks the system to cancel a document. The system asks the Requester to enter a reason for the cancellation. The Requester enters the required Description: information and asks the system to save the information and proceed with the cancellation of the document. The system saves the information and assigns the status of "Cancelled" to the document.

- 10 -

Use Case ID: Use Case Name: Actors: Type: Cross-Ref.:

4.1 Cancel RAS

Requester (Initiator) Primary 4 The use case begins when a Requester asks the system to cancel a RAS. The system asks the Requester to enter a reason for the cancellation. The Requester enters the required information Description: and asks the system to save the information and proceed with the cancellation of the RAS. The system saves the information and assigns the status of "Cancelled" to the RAS. 5 Send Document

Requester (Initiator), Email System Primary 5.1 The use case begins when a Requester asks the system to send a document to another person. The system provides list of people for the Requester to choose from. The Requester selects a Description: person from the list and asks the system to proceed with sending the document to that person. The system sends the document as an email attachment to the specified person. Use Case ID: Use Case Name: Actors: Type: Cross-Ref.: 5.1 Send RAS to BPMS

Use Case ID: Use Case Name: Actors: Type: Cross-Ref.:

Requester (Initiator), Email System Primary 5 The use case begins when a Requester asks the system to send a RAS to BPMS. The system provides list of BPMS staff for the Requester to choose from. The Requester selects a BPMS Description: staff from the list and asks the system to proceed with sending the RAS to that person. The system sends the RAS as an email attachment to the specified person and assigns the status of "Sent to BPMS" to it.

- 11 -

Use Case ID: Use Case Name: Actors: Type: Cross-Ref.:

6 Find Document

Requester/Viewer (Initiator) Primary 6.1, 6.2, 6.3 The use case begins when an Requester or Viewer ask the system to find and retrieve document(s), the system asks the Requester or Viewer to specify which criteria the document(s) Description: should be matched on, the Requester or Viewer enters their criteria into the system and the system displays a list of documents matching that criteria. 6.2 Find TA

Use Case ID: Use Case Name: Actors: Type: Cross-Ref.:

Requester/Viewer (Initiator) Primary 6 The use case begins when an Requester or Viewer ask the system to find and retrieve TA(s), the system asks the Requester or Viewer to specify which criteria the TA(s) should be matched on, Description: the Requester or Viewer enters their criteria into the system and the system displays a list of TAs matching that criteria. 6.3 Find Contract

Use Case ID: Use Case Name: Actors: Type: Cross-Ref.:

Requester/Viewer (Initiator) Primary 6 The use case begins when an Requester or Viewer ask the system to find and retrieve contract(s), the system asks the Requester or Viewer to specify which criteria the contract(s) should be Description: matched on, the Requester or Viewer enters their criteria into the system and the system displays a list of contracts matching that criteria.

- 12 -

Use Case ID: Use Case Name: Actors: Type: Cross-Ref.: Description: Use Case ID: Use Case Name: Actors: Type: Cross-Ref.: Description: Use Case ID: Use Case Name: Actors: Type: Cross-Ref.: Description: Use Case ID: Use Case Name: Actors: Type: Cross-Ref.: Description:

7 View Document Requester/Viewer (Initiator) Primary 7.1, 7.2, 7.3 The use case begins when a Requester or Viewer asks the system to display a document and the system displays the document. 7.1 View RAS Requester/Viewer (Initiator) Primary 7 The use case begins when a Requester or Viewer asks the system to display a RAS and the system displays the RAS. 7.2 View TA Requester/Viewer (Initiator) Primary 7 The use case begins when a Requester or Viewer asks the system to display a TA and the system displays the TA. 7.3 View Contract Requester/Viewer (Initiator) Primary 7 The use case begins when a Requester or Viewer asks the system to display a Contract and the system displays the Contract.

- 13 -

Use Case ID: Use Case Name: Actors: Type: Cross-Ref.:

8 Import and Link File to Document

Requester (Initiator) Primary 8.1, 8.2 The use case begins when an Requester ask the system to import and link a file to a document, the system asks the user to select a file, the Requester selects a file and asks the system to import the file, the system imports the file and pre-populates some data fields from the file contents, the Description: Requester modifies the data field values if required, provides additional information (i.e.: number of resources allocated per resource category) and asks the system to save the information, the system saves the information and links the file and its information to the document. If a file is already linked to the document, the system amends the file with the new one. Use Case ID: Use Case Name: Actors: Type: Cross-Ref.: 8.1 Import and Link TA File to RAS

Requester/Viewer (Initiator) Primary 8 The use case begins when an Requester ask the system to import and link a TA file to a RAS, the system asks the user to select a TA file, the Requester selects a TA file and asks the system to import the TA file, the system imports the TA file and pre-populates some data fields from the TA file contents, the Requester modifies the data field values if required, provides additional Description: information (i.e.: number of resources allocated per resource category) and asks the system to save the information, the system saves the information and links the TA file and its information to the RAS. If a TA file is already linked to the RAS, the system amends the TA file with the new one.

- 14 -

Use Case ID: Use Case Name: Actors: Type: Cross-Ref.:

8.2 Import and Link Contract File to RAS

Requester/Viewer (Initiator) Primary 8 The use case begins when an Requester ask the system to import and link a Contract file to a RAS, the system asks the user to select a Contract file, the Requester selects a Contract file and asks the system to import the Contract file, the system imports the Contract file and prepopulates some data fields from the Contract file contents, the Requester modifies the data field Description: values if required, provides additional information (i.e.: number of resources allocated per resource category) and asks the system to save the information, the system saves the information and links the Contract file and its information to the RAS. If a Contract file is already linked to the RAS, the system amends the Contract file with the new one. Use Case ID: Use Case Name: Actors: Type: Cross-Ref.: 9 Update or Amend Document

Requester/Viewer (Initiator) Primary 9.1 The use case begins when the Administrator asks the system to amend (or update) an existing document, the system displays the document, the Administrator modifies the document and asks Description: the system to save her amendments (or updates), the system saves the document amendments (or updates). 9.1 Update or Amend RAS

Use Case ID: Use Case Name: Actors: Type: Cross-Ref.:

Requester/Viewer (Initiator) Primary 9 The use case begins when the Administrator asks the system to amend (or update) an existing Description: RAS, the system displays the RAS, the Administrator modifies the RAS and asks the system to save her amendments (or updates), the system saves the RAS amendments (or updates).

- 15 -

3.1.3.3 - Manage Report Use Case Descriptions Use Case ID: Use Case Name: Actors: Type: 10 Generate Report

Administrator/Requester/Viewer (Initiator) Primary The use case begins when a Requester or Viewer ask the system to generate a report, the system displays a list of reports templates available to the Requester or Viewer, the Requester or Viewer Description: selects a report template and the system generates the report based on the selected report template. 11 Print Report

Use Case ID: Use Case Name: Actors: Type:

Administrator/Requester/Viewer (Initiator), Printer System Primary The use case begins when a Requester or Viewer ask the system to print the generated report, the Description: system displays a list of printers available to the Requester or Viewer, the Requester or Viewer selects their preferred printer and the system prints the report on the selected printer. 12 Export Report

Use Case ID: Use Case Name: Actors: Type:

Administrator/Requester/Viewer (Initiator) Primary The use case begins when a Requester or Viewer ask the system to export the generated report, the system displays a list of file export formats available to the Requester or Viewer, the Description: Requester or Viewer selects their preferred file export format and the system exports the report in a file formatted in the selected file format.

- 16 -

Use Case ID: Use Case Name: Actors: Type: Cross-Ref.:

13 Create Report Template

Administrator/Requester/Viewer (Initiator) Secondary 13.1 The use case begins when the Requester or Viewer asks the system to create a new report template, the system asks the Requester or Viewer for the report template's information, the Description: Requester or Viewer enters the report template information and asks the system to proceed with the creation of the new report template, the system saves the new report template. Use Case ID: Use Case Name: Actors: Type: Cross-Ref.: 13.1 Create Report Template from Existing Report Template

Administrator/Requester/Viewer (Initiator) Secondary 13 The use case begins when the Requester or Viewer asks the system to create a new report template based on the information associated to an existing report template, the system displays Description: the new report template's information, the Requester or Viewer modifies the report template information and asks the system to proceed with the creation of the new report template, the system saves the new report template. Use Case ID: Use Case Name: Actors: Type: 14 Modify Report Template

Administrator/Requester/Viewer (Initiator) Primary The use case begins when the Requester or Viewer asks the system to modify an existing report template, the system displays the report template's information, the Requester or Viewer modifies Description: the report template information and asks the system to save her modifications, and the system saves the report template information modifications.

- 17 -

Use Case ID: Use Case Name: Actors: Type:

15 Delete Report Template

Administrator/Requester/Viewer (Initiator) Primary The use case begins when the Requester or Viewer asks the system to delete an existing report template, the system asks the Requester or Viewer whether or not they wish to proceed with the Description: deletion, the Requester or Viewer confirms that they wish to proceed and the system deletes the report template. 3.1.3.4 - Manage User Use Case Descriptions

Use Case ID: Use Case Name: Actors: Type: Cross-Ref.:

16 Create User

Administrator (Initiator), User Directory System Primary 16.1 The use case begins when the Administrator asks the system to add a new user, the system asks the Administrator for the user's information, the Administrator enters the user information and Description: asks the system to proceed with the creation of the new user, the system validates the information against the information contained in the User Directory System and saves the new user. 16.1 Create User from Existing User

Use Case ID: Use Case Name: Actors: Type: Cross-Ref.:

Administrator (Initiator) Secondary 16 The use case begins when the Administrator asks the system to add a new user based on the information associated to an existing user, the system displays the new user's information, the Description: Administrator modifies the user information and asks the system to proceed with the creation of the new user, the system validates the information against the information contained in the User Directory System and saves the new user.

- 18 -

Use Case ID: Use Case Name: Actors: Type:

17 Modify User

Administrator (Initiator) Primary The use case begins when the Administrator asks the system to modify an existing user, the Description: system displays the user's information, the Administrator modifies the user information and asks the system to save her modifications, and the system saves the user information modifications. Use Case ID: Use Case Name: Actors: Type: 18 Find User

Administrator (Initiator) Primary The use case begins when an Administrator ask the system to find and retrieve user(s), the system asks the Administrator to specify which criteria the user(s) should be matched on, the Description: Administrator enters their criteria into the system and the system displays a list of users matching that criteria. 19 View User Administrator (Initiator) Primary The use case begins when an Administrator asks the system to display a user's information and the system displays the user's information.

Use Case ID: Use Case Name: Actors: Type: Description:

3.1.3.5 - Manage Reminder Use Case Descriptions Use Case ID: Use Case Name: Actors: Type: Cross-Ref.: 20 Create Reminder

Requester/Viewer (Initiator) Optional 20.1 The use case begins when the Requester or Viewer asks the system to create a new reminder, the system asks the Requester or Viewer for the reminder's information, the Requester or Viewer Description: enters the reminder information and asks the system to proceed with the creation of the new reminder, and the system saves the new reminder. - 19 -

Use Case ID: Use Case Name: Actors: Type: Cross-Ref.:

20.1 Create Reminder from Existing Reminder

Requester/Viewer (Initiator) Optional 20 The use case begins when the Requester or Viewer asks the system to create a new reminder based on the information associated to an existing reminder, the system displays the new Description: reminder's information, the Requester or Viewer modifies the reminder information and asks the system to proceed with the creation of the new reminder, and the system saves the new reminder. 21 Modify Reminder

Use Case ID: Use Case Name: Actors: Type:

Requester/Viewer (Initiator) Optional The use case begins when the Requester or Viewer asks the system to modify an existing reminder, the system displays the reminder's information, the Requester or Viewer modifies the Description: reminder information and asks the system to save her modifications, and the system saves the reminder information modifications. 22 Delete Reminder

Use Case ID: Use Case Name: Actors: Type:

Requester/Viewer (Initiator) Optional The use case begins when the Requester or Viewer asks the system to delete an existing reminder, the system asks the Requester or Viewer whether or not they wish to proceed with the Description: deletion, the Requester or Viewer confirms that they wish to proceed and the system deletes the reminder.

- 20 -

Use Case ID: Use Case Name: Actors: Type:

23 View Reminder

Requester/Viewer (Initiator) Optional The use case begins when an Requester or Viewer ask the system to display a reminder's Description: information, the system displays the list of the Requester or Viewer's reminders, the Requester or Viewer selects a reminder from the list and the system displays the reminder's information. Use Case ID: Use Case Name: Actors: Type: 24 Send Reminder to User

Email System Optional The use case begins when the conditions specified in a reminder are met (cost and/or timebased), depending on the reminder's information specified by the Requester or Viewer, the Description: system displays and/or sends and email message to the Requester or Viewer who created the reminder reminding them that the reminder's conditions have been met.

- 21 -

3.1.4 - Use Case Diagrams

3.1.4.1 - Generic Use Cases

- 22 -

3.1.4.2 - Manage Document Use Cases

- 23 -

3.1.4.3 - Manage Report Use Cases

- 24 -

3.1.4.4 - Manage User Use Cases

3.1.4.5 - Manage Reminder Use Cases

- 25 -

3.1.5 - Other Diagrams

3.1.5.1 - Create, Modify and Send RAS to BPMS Flow Chart

- 26 -

3.2 - Report Requirements

The system must provide the user with the following canned reports (on top of the ad-hoc reporting functionality) and allow her to export them in one or more file formats such as the Portable Document Format (PDF). 1. Contract Status: - $ value - How much $ left in contract - Start/end date of contract - Monthly burn rate 2. Contract Usage: - which directorate and cost centre - which categories used - $ value per category 3. RAS: - date RAS sent to BPMS - date service requested - which directorate/cost centre requested service - resource category requested - RAS activity (tracking activity/progress on RAS between AM&ITOS directorate and BPMS 4. TA: - by vendor - TA total $ amount; how much spent; how much remaining committed but unspent - start/end date of TA - cost centre - resource category - resource name (i.e. name of contractor) Note: for this exercise, assume that we can only request one resource per TA

- 27 -