Business Intelligence Initial Design and Prototype

From MIKE2.0 Methodology

Activity: Define Business Intelligence Prototype

Objective

The Business Intelligence Prototype activity refines the interfaces through which the end user works with the system when an information platform is being constructed. The initial design standards for reports are developed in this activity, along with the data requirements for reports. The report designer then begins development of the reports through prototyping - the idea is that the design should not go into too much detail before the prototypes are built – we want to begin interactively working with the users on a set up potential reports once the data model is relatively stable. The report design for the final construction of reports in formalised in the following phase – the focus of this activity is prototyping and design standards.

Major Deliverables

Initial BI Report Design including:

• Data Reporting Standards
• Detailed Business Requirements for Increment
• Requirements for Initial Prototype Reports

Tasks

Define Information Presentation Standards

Objective:

This task establishes standards for developers to follow when creating any BI Applications. Any early prototype shown to the users should be revisited with them. Before the design process for this interface begins, it is important to determine whether there are any standards established for creating interfaces. If so, this application should conform to the existing standards. If no such standards exist, then it is important to take the time to get agreement on this area. Some of these initial standards were developed during Phase 2 at a high level.

Mock-up report screens (without real data) may be created to help users capture the look-and-feel of reports.

Input:

• Data Reporting Standards
• Detailed Business Requirements for Increment
• Reporting Specification Standards

Output:

Initial Report Design, including:

• Information Presentation Standards

Define Data Requirements for Reports

Objective:

The key information that will be shown in the reports should be defined and reviewed with the users. In this task, mockup data may also need to be generated to help build the prototype.

Input:

• Detailed Information Requirements for Increment

Output:

Initial Report Design, including:

• Reporting Data Requirements

Design and Develop Initial Reporting Prototypes

Objective:

In this task, a complete prototype of the interface is created, including building the key screens to the user interface. In this task, user interface screens are built using the environment and development tools selected for the new system. The areas to be addressed include:

• Define scope of prototype
• Design prototype screens / reports
• Load / convert prototype data
• Iteratively test prototype application functionality and develop
• Review / refine prototype with users

As the prototype is created, developers can begin some early usability testing. This consists of asking users to step through the prototype and having them describe how they would perform various system tasks. As they do this, the tester watches for cases in which the interface is misinterpreted or misunderstood, or the users are not able to figure out how to do what they want. Usability analysis is an ongoing task from this point in the project since it can be done with more and more precision as the system nears completion.

Input:

• Detailed Business Requirements for Increment
• Information Presentation Standards
• Reporting Data Requirements

Output:

Initial Report Design, including:

• Conceptual Report Design
• Reporting Prototypes

Core Supporting Assets

• Reporting Requirements Deliverable Template provide samples for report design

Yellow Flags

• Business users not engaged in review of report prototypes

Key Resource Requirements

• Information Architect
• Report Developers