Use Case Name: Maintain updated Call-type and DNIS list ID: 1 Importance Level: high
Primary Actor: DBMS Administrator Use Case Type: detail, essentials
Stakeholders and Interests: DBMS Administrator- maintains and updates the call-type and DNIS lists.
Brief Description: This use case will be used to maintain and show a dynamically created call-type and Dnis checkbox list in the html form. Trigger: When html form is generated
Type: Internal Relationships: Association: DBMS Administrator Include: Extend: Generalization: Normal Flow of Events: o When a new Dnis and calltype is discovered, it needs to be added to the database table o The html form generates a checkbox list based on the updated database table.
Sub Flows: S-1:
Use Case Name: User Input ID: 2 Importance Level: high Primary Actor: The Manager Use Case Type: detail, essentials Stakeholders and Interests: The Manager wants to see the statistics for call volume for specific Calltypes or Dnis numbers. Brief Description: This use case will display the call volumes in a time series line graph. Trigger: User selection
Type: Relationships: Association: Manager Include: Submitting Query for Reports Extend: Generalization: Normal Flow of Events: o User selects view type o User selects Start Date o User selects End Date o User selects Select by o User selects Graph Type o User selects from generated checkbox list o User submits selections
Sub Flows: S-1:
Use Case Name: Submitting query for report ID: 3 Importance Level: high Primary Actor: Manger Use Case Type: detail, essentials Stakeholders and Interests: customer: enters the required information and gets into the database system.
Brief Description: This use case will query the database using parameters passed on by the user and return a result set Trigger: Submitting the query to generate the report
Type: Relationships: Association: Include: Extend: Querying the Database and returning a ResultSet Generalization: Normal Flow of Events: o User submits the report o The application gets parameters from the form o Uses parameters to decide what kind of report to generate o Queries the database Sub Flows: S-1:
Use Case Name: Querying database ID: 4 Importance Level: High Primary Actor: Manager Use Case Type: detail, essentials Stakeholders and Interests: Brief Description: Trigger:
Type: Relationships: Association: Include: Filling the XML template Extend: Generalization: Normal Flow of Events: o Uses user parameters to create a dynamic sql query o Executes query o Returns resultset o Fills the xml template with resultset
Sub Flows: S-1:
Use Case Name: Filling the XML template ID: 6 Importance Level: High Primary Actor: Application Use Case Type: Dynamic Stakeholders and Interests:
Brief Description: Uses result set from dynamic sql query results and uses that data to fill a custom .jrxl template Trigger: submitting Query for Report
Type: Relationships: Association: Include: Outputting Report Extend: Generalization: Normal Flow of Events: o Uses JasperDesign to load query o Compiles report using JasperCompileManager o Uses JasperPrint to fill report template o Outputs report in the html ouput stream
Sub Flows: S-1: Alternate/Exceptional Flows:
Use Case Name: Outputting Report ID: 7 Importance Level: High Primary Actor: Application Use Case Type: Detail, Essential Stakeholders and Interests: Brief Description: Gets reports from the output stream and outputs the report in the local browser of the user Trigger: If user selects a specific view type and submits report
Type: Relationships: Association: Include: Extend: Generalization: Normal Flow of Events: o Retrieves the output stream o Outputs report in the local browser o Depending on the user selection of view type the report can be viewed in the browser or downloaded o Uses ImageServlet to handle graphic files to be shown in the browser