Use Case Specification:
UI Modernization NJ SUCCESS
Use Case Specification: Creating Reports System Use Case 36
Version 1.0
Revision History
|Date |Version |Description |Author |
|07/13/04 |1.0 |Creation |TK, RL, WJ, LS |
| | | | |
| | | | |
| | | | |
Table of Contents
1. Use Case Name – Creating Reports 1
1.1 Brief Description 1
2. Flow of Events 1
2.1 Basic Flow 1
2.1.1 The system receives a request to create an Ad Hoc report 1
2.1.2 The system will provide user with accessible data fields 1
2.1.3 The system provides data sample for validation of report 1
2.1.4 The system allows user to save the newly created report 1
2.1.5 The system will gather the required data for report 1
2.1.6 The system documents all actions taken 1
2.2 Alternative Flows 1
2.2.1 The report created is for Federal statistics 1
2.2.2 The requester needs ability to save report with existing data 1
3. Special Requirements 2
4. Preconditions 2
5. Post Conditions 2
6. Extension Points 2
6.1 Documenting Action Taken 2
Use Case Specification: Creating Reports
Use Case Name – Creating Reports
1 Brief Description
This use case will allow for the creation of AD HOC reports and mandatory Federal reports to be created, manipulated, and designed.
Flow of Events
1 Basic Flow
1 UC1625 The system receives a request to create an Ad Hoc report
The system will provide an interface for the requester to initiate the creation of a report from their accessible data.
2 UC1626 The system will provide user with accessible data fields
The system will show all available data fields to the user so that they can access the information and position the data on the report.
3 UC1627 The system provides data sample for validation of report
The system will provide a real data sampling to assure that the report is formatted correctly and meets the user needs.
4 UC1628 The system allows user to save the newly created report
The system will allow for the user to save the report for future report generation and allow for other similar users to access the report template. The user can mark any newly created report to be automatically run at a scheduled time and sent to specified users.
5 UC1629 The system will gather the required data for report
The system will provide the creator with the actual requested data in order to analyze. The system will allow for the report to be printed or sent to any other system users requested by the user.
6 UC1630 The system documents all actions taken
2 Alternative Flows
1 UC1631 The report created is for Federal statistics
The system should allow for the creator to mark a report for Federal statistics and automatically send the report to the USDOL and other interested parties on a scheduled date and time. The generated report should allow for others to comment based on the information provided in the report prior to sending to USDOL.
2 UC1632 The requester needs ability to save report with existing data
Each time a report is run the system should allow for the requester to save the report with static data on either local machine or document repository.
Special Requirements
Preconditions
Post Conditions
Extension Points
1 Documenting Action Taken
................
................
In order to avoid copyright disputes, this page is only a partial summary.
To fulfill the demand for quickly locating and searching documents.
It is intelligent file search solution for home and business.
Related download
- use case specification
- nbd requirements meeting minutes august 20
- electronic records management use cases overview
- business use case tennessee
- model covid 19 prevention program
- business requirements document nyu
- rit online learning peer evaluation
- project 1 software design using uml
- below is the list of use cases and associated business