Designing a Navigation and Structure Model for the "BSM Dashboard" - BSM Solution Development Series and Demo Development
dmcclure 0600011K8N Visits (1527)
Continuing our blog series on developing a BSM Solution and the “BSM Dashboard”, the next critical aspect is designing how the target end user (LoB Application Owner) will interact with the "BSM Dashboard". When I talk about “BSM Dashboard” interactions these are the designed actions we expect the target end user to take when they are engaged with the dashboard, interpreting the content, making decisions and taking action(s).
Interaction activities are discussed in the BSM Solution Methodology and are outputs from the BSM Solution Workshop. We want to have a well thought out flow within the BSM Solution that enables the target end user to enter, move around and exit in the easiest way possible in accordance with our designed dashboard use cases. We never want to allow the target end user to end up in an area where the content presented doesn't support the overall BSM Solution design. Be very aware of the default actions, menus, etc. within TBSM/TIP/WebGUI, etc. These often lead to much confusion for the target end user. If they don't need to see it - don't show it!
During the BSM Solution Workshop we learned that the LoB Application Owner was likely to take the following actions from the top level dashboard:
Reviewing our "BSM Dashboard" design below we see our target navigation areas and target drill down dashboard (DDD) pages.
Based upon this Navigation Model design, we can identify the following key requirements for our Structure Model to allow for our expected operation. We'll also have some other elements in the Structure Model that don't play an operational role in our key navigation flows.
Note the section highlighted in red above. This is an area where we do not want any navigation interactions to occur. Remember, anything you place on the custom canvas dashboard will have some sort of default interaction associated with it. We must take specific actions to override any default navigation that may occur if the LoB Application owner clicked on a metric indicator.
One technique I often use is mind mapping to
capture key design information during the BSM Solution workshop. I use a free
mind mapping program called Freelane (htt
We have enough information to now begin to lay our foundational structure model within TBSM using the new Business Service Composer (BSC) capability. In the next blog post we'll step through part one of using the BSC to build our static resources.
Over the next few posts I will describe the process for designing and implementing the following key components of the BSM Solution and the "BSM Dashboard".
I look forward to hearing from you!