Kuali Report Development Procedures

Steps for Developing KFS Reports

1. Report is requested by user to business analyst, or the business analyst determines there is a need for a new report to be developed
2. A new JIRA is created by the business analyst for the proposed report under the "UCI - KFS Data Warehouse" project with the type of "New Feature", component "Report Development", KFS module that the report is for, and label of "spec_needed". The assignee will be the business analyst until the reporting specs are finalized and ready for development.
3. Business analyst will gather report requirements, and document them using the KFS reporting specifications template.
   
   1. Each template will have a file name of "DW-<kfs module>-<sequential number> <report name (replacement of <legacy report>) <spec version number> <spec created date>", for example "DW-CAM-001 Capital Asset List (Replacement for EQS001) v1.0 2013-12-01.docx". 
   2. The specs will be attached to the JIRA ticket and placed in its own folder on the 'OIT Docs' network drive under: KUALI Project\D-1 Data Warehouse\Report Specs. For example the "DW-CAM-001" specs would be located in: KUALI Project\D-1 Data Warehouse\Report Specs\DW-CAM-001 Capital Asset List (Replacement of EQS 001).
   3. Any changes to this initial draft will result in new versions of this document being created under the same folder, with a new version number and updated date. The updated specs document will also be added to the original JIRA ticket.
4. Once the specs are finalized, the business analyst will assign the JIRA ticket to the KFS DS project manager. The KFS DS project manager will review the specs with the report development team and add the report to the report list on the KFS Decision Support Wiki page. The KFS DS project manager will ensure all the data is available for the report developers before report development commences.
5. Once the specs are well understood, the KFS DS project manager will review the requirements with the KFS Project Management group and determine a prioritization and due date. These will be updated on the KFS Decision Support Wiki page and the due date will be filled in the JIRA ticket.
6. The KFS DS project manager will then assign the JIRA to a report developer.
7. The report developer will develop the report using Cognos Report Studio, saving the report into their respective user folder under: Public Folders ‎> Kuali Financial System ‎> Users‬
8. Once the report is developed, the report developer will inform the reporting production control lead to copy their report into the QA folder under: Public Folders ‎> Kuali Financial System ‎> Reports ‎> Hidden - QA‬
9. The reporting production control team will review the report, modify the report to match current reporting style guidelines, and test the report according using the Cognos Report Studio QA checklist.
10. Once the report is tested and ready for review, the KFS DS project manager, business analyst and/or report developer will review the report with the KFS project management team. This is done in JIRA by updating the JIRA status as "Ready for test". Note, the JIRA status must be "In Progress" before it can be transition to "Ready for Test"
11. Once the report is approved by the KFS project management team, the report will be reviewed by the original requester/subject matter expert (SME) for approval.
12. Any changes resulting from the SME's review will be updated in a new version of the report specifications document, and steps 4-11 will be repeated.
13. Once the report approval is finalized, the report will go through OIT's standard change control process. A new change control JIRA will be created, and announcements will be made in the weekly change control meeting.
14. The reporting production control team will move the report into the Public Folders ‎> Kuali Financial System ‎> Reports ‎> Hidden‬ folder and a link will be created in the Public Folders ‎> Kuali Financial System ‎> Reports‬ folder in Cognos. It is recommended to make a backup of the entire "Hidden" folder before moving a report from "Hidden - QA" to "Hidden"

KFS Report Development Roles

Diagram Files

ReportDevProcess.jpg

ReportDevProcess.vsd