Best practices for evaluating SAP BusinessObjects Design Studio

Best practices for evaluating SAP BusinessObjects Design Studio

BI2015

About my talk at the BI 2015 conference

Next month, 16-18 June, I will attend the SAPinsider BI2015 conference in Nice, France. Additionally I will present a lecture about best practices for introducing SAP Design Studio into your organization. Almost all of the best practices come from actual cases that I participated in or witnessed in the past year. Some of them we did and were really happy about the outcome, others where we wished we did them and learned lessons for the next time.

Additionally I will be available in the expert sessions, I am looking forward having discussions about all kinds of subjects relating to Design Studio! If you are planning on going, use our special link to receive a €300,- discount on the registration fee.

So, what am I going to discuss?

On Design Studio

First of all Design Studio itself. What is it? What does it do well? and where is it lacking in comparison to others? This is an important subject as most of the time you need to fit the application into an existing environment. So what can you do with it, and where do you need other applications to fill a gap?

Then I will look at the current version (1.5 when we all are in Nice when everything goes well). Rather than repeat the roadmap that will be covered by others I will focus on the main direction, my thoughts on them and what aspects I think you need to pay special attention to in the coming months.

On Managing the evaluation process

Once you decided to give Design Studio a try, typically you start out with a Proof of Concept. Let the tool proof that it’s worth its salt. But there are things that you have to keep in mind to keep the project focused. Do we have the right goals, how do we avoid getting distracted? When are we satisfied? These are the things I will discuss in this section.

On Building applications

When all goes well at some point you will start to build a new portfolio of reports with Design Studio. So how to make sure that these applications are well made, are maintainable, look great and deliver valuable information? In this part I will go through guidelines that help you to achieve these goals. One of the pitfalls when starting is that when you start with an empty application, it looks so easy. You follow a tutorial and there is a clickable graph and additional down drillable crosstab.  But that is only the start. At some point you have a larger number of applications and these applications tend to get more complex over time. How do you avoid that the complexity is getting in the way of reaching the previously stated goals?

On SDK development

If you need something that can’t be achieved by standard components there is the option to install your own components. You either buy them from third parties or build them yourself.  But at what point do the benefits outweigh the drawbacks? An SDK is basically JavaScript that you have to write yourself. And maintenance is also your responsibility. On the other hand we see lot of examples where a relative small development on a SDK component resulted in a sizable contribution to the application portfolio.

Wrapping up

Finally we will have some time for a discussion. I look forward to your comments and questions as I am very interested in other experiences. I will also ask you for things that you want to see added to the new book “Design Studio, Comprehensive guide (working title)”. We’re looking to publish it at the end of the year and if you have anything that you would like to see included, let me know!

BI2015

About my talk at the BI 2015 conference

Next month, 16-18 June, I will attend the SAPinsider BI2015 conference in Nice, France. Additionally I will present a lecture about best practices for introducing SAP Design Studio into your organization. Almost all of the best practices come from actual cases that I participated in or witnessed in the past year. Some of them we did and were really happy about the outcome, others where we wished we did them and learned lessons for the next time.

Additionally I will be available in the expert sessions, I am looking forward having discussions about all kinds of subjects relating to Design Studio! If you are planning on going, use our special link to receive a €300,- discount on the registration fee.

So, what am I going to discuss?

On Design Studio

First of all Design Studio itself. What is it? What does it do well? and where is it lacking in comparison to others? This is an important subject as most of the time you need to fit the application into an existing environment. So what can you do with it, and where do you need other applications to fill a gap?

Then I will look at the current version (1.5 when we all are in Nice when everything goes well). Rather than repeat the roadmap that will be covered by others I will focus on the main direction, my thoughts on them and what aspects I think you need to pay special attention to in the coming months.

On Managing the evaluation process

Once you decided to give Design Studio a try, typically you start out with a Proof of Concept. Let the tool proof that it’s worth its salt. But there are things that you have to keep in mind to keep the project focused. Do we have the right goals, how do we avoid getting distracted? When are we satisfied? These are the things I will discuss in this section.

On Building applications

When all goes well at some point you will start to build a new portfolio of reports with Design Studio. So how to make sure that these applications are well made, are maintainable, look great and deliver valuable information? In this part I will go through guidelines that help you to achieve these goals. One of the pitfalls when starting is that when you start with an empty application, it looks so easy. You follow a tutorial and there is a clickable graph and additional down drillable crosstab.  But that is only the start. At some point you have a larger number of applications and these applications tend to get more complex over time. How do you avoid that the complexity is getting in the way of reaching the previously stated goals?

On SDK development

If you need something that can’t be achieved by standard components there is the option to install your own components. You either buy them from third parties or build them yourself.  But at what point do the benefits outweigh the drawbacks? An SDK is basically JavaScript that you have to write yourself. And maintenance is also your responsibility. On the other hand we see lot of examples where a relative small development on a SDK component resulted in a sizable contribution to the application portfolio.

Wrapping up

Finally we will have some time for a discussion. I look forward to your comments and questions as I am very interested in other experiences. I will also ask you for things that you want to see added to the new book “Design Studio, Comprehensive guide (working title)”. We’re looking to publish it at the end of the year and if you have anything that you would like to see included, let me know!

Jeroen van der A