4 Addressing Common Requirements

Addressing common requirements involves strategic planning and best practices to ensure optimal performance and user satisfaction.

Here are some key common requirements and the associated best practices.

Table 4-1 Addressing Common Requirements

Requirement Design Best Practices
Understand your detailed business requirements before designing the application. Getting Started with Your Design:
Plan your application design: single or multiple applications based on your use case. Decide on a Single Application or Multiple Applications
Choose the right application type based on your business requirements. Cube Types Design
Plan for efficient model design. For example, optimize sparse and dense dimensions. Dimension Design
Enable the Hybrid BSO application type, and consider the number of Hybrid BSO and ASO cubes.
Plan for security and access control, and address requirements for audit and compliance. Security Design
Design your application for scalability and flexibility. Application Design
Have a plan to manage metadata. Design Checklist for Dimensions: Table 6-2
Include performance tuning options. For example:
  • Minimize complex dynamic calc members
  • Set the aggregation properties and data storage type
  • Optimize calculation scripts
  • Follow effective form design guidelines
 Design Checklist topics, including:
  • Business Rules and Calculation Design, Table 6-4
  • Forms and User Interface Design, Table 6-3
Design the appropriate approval workflow. Approvals Design
Implement integration best practices. Integration Design
Plan for disaster recovery and backup. Design checklist for Maintenance: Table 6-9
Incorporate change management. Creating and Running an EPM Center of Excellence
Create and run an EPM Center of Excellence (CoE). Creating and Running an EPM Center of Excellence