Define the Business Requirements and Use Cases
Define the business requirements and use cases to state the project's business needs and success criteria clearly.
Ensure that the requirements and use cases identify the critical business processes and the plan to monitor these processes. You must specify the functional and non-functional requirements in your implementation plan.
- Business Users
- Project Manager
- Business Leads
Define the Functional Requirements
Establish the business objectives to determine the success criteria and measure the success of your Fusion Analytics solution.
The implementation team must identify all the functional requirements and get approval from all the stakeholders to ensure that the project team fully understands what is required to be built. It's also important to agree upon the testing scenarios for each of the functional requirements.
- Review the end-to-end process maps with the Oracle
Fusion Cloud Applications functional administrator for each area. Agree on the analytical reporting requirements
and how they're measured.
- Determine the business metrics that you want to monitor.
- Agree on the analytical workbooks functionality that complements the business metrics and provides further insight into the process.
- Agree on the applicable security setup such as permissions and data restrictions.
- Confirm the data sources for each reporting area.
- Agree on the frequency of the data load required to meet the reporting requirements.
- Map the Fusion Analytics modules to the configured Oracle Fusion Cloud Applications modules. You must ensure that the Fusion Analytics modules that you plan to activate relate to the Oracle Fusion Cloud Applications functional modules. This enables the data pipelines to function effectively.
- Do a fit-gap analysis to identify the gaps in the solution and initiate the conversation to remediate the feasibility gaps.
- Document these requirements and test them during the appropriate test phase of the project.
Use the checklist to confirm that the action items are planned for. See Define the Functional Requirements Checklist.
Define the Non-Functional Requirements
Non-functional requirements are related to the Fusion Analytics system functionality and how Fusion Analytics is expected to perform.
Consider the non-functional requirements such as performance, security, and reliability in your implementation plan. Identify all non-functional requirements and ensure that all senior stakeholders on the project, ranging from the business community to the security teams agree on these requirements. Based on the documented non functional requirements inventory, ensure that you check for the Oracle Fusion Cloud Applications source objects that don't have the corresponding view objects available for reporting. Flag these technical gaps during the early stages of implementation to accommodate the turn around time required for implementing enhancement requests in Oracle Fusion Cloud Applications. This will ensure that the project team fully understands the non-functional objectives and how these are measured. It's also important to agree upon the testing scenarios for each of the non-functional requirements. Document these requirements and test them during the appropriate test phase of the project.
Use the checklist to confirm that the action items are planned for. See Define the Non-Functional Requirements Checklist.
Define the Use Cases
Use cases describe the interaction between Fusion Analytics and the user to achieve a business process goal.
- Steps to create and deploy business metrics to a new or existing workbook.
- Steps to create new application roles and assign them to groups and users.
- Steps to monitor business metrics and related workbooks for a particular business process, such as monitoring headcount turnover.
Document the use cases to ensure that the project team fully understands the objectives and how these use cases would be fulfilled.