/

Drum prüfe, wer sich bindet

Ob der Aufbau und Betrieb eines ISMS erfolgreich war, sollte geprüft und dann zertifiziert werden.

Der Aufbau und Betrieb eines ISMS ist nicht einfach. Darum ist es wichtig, dass fertige ISMS auf Herz und Nieren zu prüfen. Auch keine einfache Aufgabe. Hierbei hilft die Prüfung und Zertifizierung von externen Personen.

SAP UX strategy and Fiori overview - [Presenter] In this module, we'll briefly review the overall SAP user experience and Fiori strategy. Let's start by clarifying two phrases that are commonly used in this context, and those are user interface and user experience. You will often see these phrases or even their acronyms used, such as UI and UX, used interchangeably in many ways, because many people believe that they are referring to the same thing. But in fact they're quite different, and I'd like to illustrate this with an example. I live in Colorado, and I have a Jeep that I have modified significantly to be very capable to go off road into the Colorado mountains, with many aftermarket parts and other upgrades. Now I do this not just because I love having a Jeep sitting in my driveway, I do this so that I can actually go into the mountains and go over amazing mountain roads and get amazing views such as this one here which was taken from a place called Mosquito Pass in Colorado. And this is really the ultimate goal of why I created my Jeep. So to correlate back to our phrases, I would consider my Jeep a user interface, whereas I would consider the outcome of what I'm trying to accomplish the user experience. And in that way you can see how the Jeep itself is really a tool, or an interface, in order to achieve a much bigger outcome being the user experience. In order to successfully and repeatedly drive innovation, it is key to consider three aspects with respect to user experience. Business or business processes, how the actual business model works. People and their requirements for interfacing with that business process or model, and achieving outcomes. And then the actual technology in and of itself. And while it may seem obvious that each of these aspects is essential by itself, what's most important is that they work together seamlessly in a balanced way. For example, you may have a great business model in order to be successful in the market, and you might even have great technology in order to realize your idea. But imagine if you have these things, but the people either cannot or don't want to use it. It's only when you consider all three of these aspects holistically that innovation can be successful, and user experience requires the consideration of all three holistically. So these three aspects are key to SAP's overall user experience strategy and direction. On the business side, it really needs to represent the simplification of re-imagined processes in a digitized world. Next we must fully understand human interaction requirements using design driven development, and ensure that it is user-centered and covers all possible SAP solutions and user rules. The UIs can then be properly designed. SAP uses technology such as SAP UI Five which are based on open standards, and the UI is decoupled from the back-end, through other open standards such as REST-based OData services. So really SAP Fiori is the end result, and it's the true confluence of all three aspects of consideration, and is the combination of simplified business processes, where user interaction follows a user-centric and design-driven approach, and is implemented with open standards technologies. So the concept of Fiori, which goes far beyond just applications, is really decomposing user roles into very simplified, consumable modules. It's really a shift from large monolithic solutions that require everybody to go through the same screens which is very common to the prior generation technologies such as SAPgui. And it really lets you work the way you work, both personalized and with your role, without having to operate in a uncomfortable way in the same screens that everybody else works with. And as such, SAP Fiori was really started by defining this set of design principles based on the confluence of business, people, and technology we discussed before. The first one is that it's role-based, it's really designed around you, your needs, and how you work in your specific roles. So individual applications, and even the Fiori technical design, is built from the ground up to be role-based. It's adaptive, it is able to easily adapt to different use cases, different devices, it's got to work consistently, and in the same way, no matter where you're interacting with an SAP solution, whether from a device, whether from a screen, or some kind of an audible based interface, it needs to adapt to the way that you work. The third one, simple, is probably one of the most difficult to achieve, because it is so easy to continue to want to add features, and capabilities, and functions to screens. And the art of simplicity around including only what is necessary has to be continuously monitored to make sure that that complexity doesn't creep in. It's got to be coherent, as we mentioned it's got to be intuitive, it's got to reduce user adoption challenges, and increase adoption by enabling individual users to self-train on individual solutions. And the last one, delightful, is one of my favorites, it's got to really make an emotional connection. Like me driving my Jeep over the top of a mountain, the ultimate goal is to have users want to utilize these systems, and often that comes through making an emotional connection. So these are the core design principles of Fiori. One other aspect that was learned from the past, is there used to be different types of user interfaces for different situations, a portal, or SAPgui, or things of that nature, different mobile solutions, and SAP Fiori was really built as a single, consistent point of entry for users, that will then drive you to specific details and capabilities no matter if they're in an on-premises solution, or they're in a cloud solution, or even something built by a third party. So it really is a single point of entry for that. And if we're to really sum up what Fiori then is, it's a role-based, personalized, and a real-time, contextual aggregation point for all apps, and all analytics, across all solutions, and functional areas and technology. So SAP Fiori, think of it as the true realization of our overall user experience strategy, and as really built to bring those five design principles to life. What is the Fiori Apps Library? Selecting transcript lines in this section will navigate to timestamp in the video - [Instructor] Now that we have an understanding of the overall SAP user experience strategy, and how Fiori realizes that strategy, let's take another Fiori Apps Library. So what is the Fiori Apps Library? Well in a nutshell the Fiori Apps Library is a comprehensive library of all available SAP content for the SAP Fiori Launchpad, and in calling back to our Perl module of the SAP Fiori Launchpad is a single point of entry into Fiori applications and a Fiori user experience. It contains key details for every available Fiori app, including an overview, even some screenshots but also all of the technical data that's needed for installation and configuration. A powerful tool within the Fiori Apps Library is the ability to display an aggregated set of installation and configuration requirements, for a selection of apps. Now what that means is there are times that business users let's say financial users will go into the library and identify maybe five to 10 apps that they're interested in having deployed. IT can then take that selection of applications, and create a single page that shows all of the aggregated requirements that they need for installing and configuring that app which grammatically simplifies what they need to do, in order to identify the back end requirements for that. It allows you to navigate directly to related resources such as detailed app documentation, the product availability matrix, which is where you can determine information such as available browsers and browser versions that can be used, and even the maintenance planner as a step towards implementation. You can get Fiori App recommendations, which are recommendations based on the actual applications on usage in your system. And you can even discover Fiori Lighthouse Scenarios, and a Fiori Lighthouse Scenarios are scenarios that are enabled by SAP apps that SAP recommends as a great starting point. For customers implementing S/4HANA, whether in the cloud or on premises. Each scenario offers immediate business benefits to business users over and above an older related SAP GUI transactions in the SAP Business suite. Naturally you also find several innovation scenarios that just simply were even available in business suite. You will also find configuration information required to integrate classic SAP GUI and even web Dynpro applications. The Fiori Launchpad supports technologies such as there is beyond the next generation Fiori technology to provide maximum flexibility and value. So those are some of the key features of your launchpad. Now am taking a look at our main page when you navigate to the URL shown previously. When you first get there if you have not yet signed in, you will be browsing the pages as anonymous user. You'll see in the top left picture here that on the top right where is a sign in we have not authenticated against the application, and as such we don't have full access to all of the capabilities of library on the bottom right you can see that I have logged in and authenticated, and this could be using your SAP ID service such as your service marketplace user. Now when you're authenticated, some things will visibly change, such as on the bottom left you'll see that the the bottom manage profiles and filters that's available for authenticated users. Now the bottom get SAP Fiori App recommendations has not changed between the two. But if you were to select it as anonymous user, you would be required to authenticate before you could perform that function. Now once we've authenticated let's review briefly some of the main aspects of the main page. The top left you'll see a set of categories. Now as we get deeper into the library, we're going to be talking a lot about filters and the ability to filter the library. Think of categories as really just predefined top level filters, that make it easier to get into a specific context such as mySAP business suite user or MS for honey user. So really those are just top level filters that are very convenient app recommendations. If you have them you'll always see the button to get them, but if you already have defined some of them, you'll see an app recommendations category we'll take a look at that shortly. On the bottom left is the ability to drill in and manage filters and profiles. These are really areas that you can predefine filters and other types of lists for convenient use later. On the top right to drill into additional help, you can simply select the question mark icon. And then on the bottom right a couple buttons for getting legal information or even for providing a feedback or sharing a page which can be very convenient to share with your colleagues at your organization. On an app details page, you will see on the left hand side a list of any applications that fit the currently defined filters that you've selected. We're going to go into this in a demo later, but the filtered App list is on the left. For any selected application such as the my inbox app here, there will be a couple of tabs available. Above that you'll see core app details, such as the available product that is available for the type of application Fiori has a couple of categories of applications such as facets and transactional apps. Then if there's a required database type which is important to many customers, and which form factors that works on obviously fury in most cases, is designed to work on any form factor effect Fiori as a design standard is, but if the technology you're reviewing here something older like SAP GUI in the library, that might be actually limited to one or just a few form factors. Now below that the product features is where again you can get an overview of it there may be some screenshots of the application. Here we're showing the implementation Information tab, where you can get a lot of technical details around installation and configuration details. Again we're going to go over all of this later on, but this just gives you a high level view. And at the bottom there are two high level views a detail view like we're looking at here, and then there's a list of view and again we'll take a look at all of these. So that provides a high level overview of what it is. Next we're going to get into it and look at it live. What is the Fiori Apps Library? Selecting transcript lines in this section will navigate to timestamp in the video - [Instructor] Now that we have an understanding of the overall SAP user experience strategy, and how Fiori realizes that strategy, let's take another Fiori Apps Library. So what is the Fiori Apps Library? Well in a nutshell the Fiori Apps Library is a comprehensive library of all available SAP content for the SAP Fiori Launchpad, and in calling back to our Perl module of the SAP Fiori Launchpad is a single point of entry into Fiori applications and a Fiori user experience. It contains key details for every available Fiori app, including an overview, even some screenshots but also all of the technical data that's needed for installation and configuration. A powerful tool within the Fiori Apps Library is the ability to display an aggregated set of installation and configuration requirements, for a selection of apps. Now what that means is there are times that business users let's say financial users will go into the library and identify maybe five to 10 apps that they're interested in having deployed. IT can then take that selection of applications, and create a single page that shows all of the aggregated requirements that they need for installing and configuring that app which grammatically simplifies what they need to do, in order to identify the back end requirements for that. It allows you to navigate directly to related resources such as detailed app documentation, the product availability matrix, which is where you can determine information such as available browsers and browser versions that can be used, and even the maintenance planner as a step towards implementation. You can get Fiori App recommendations, which are recommendations based on the actual applications on usage in your system. And you can even discover Fiori Lighthouse Scenarios, and a Fiori Lighthouse Scenarios are scenarios that are enabled by SAP apps that SAP recommends as a great starting point. For customers implementing S/4HANA, whether in the cloud or on premises. Each scenario offers immediate business benefits to business users over and above an older related SAP GUI transactions in the SAP Business suite. Naturally you also find several innovation scenarios that just simply were even available in business suite. You will also find configuration information required to integrate classic SAP GUI and even web Dynpro applications. The Fiori Launchpad supports technologies such as there is beyond the next generation Fiori technology to provide maximum flexibility and value. So those are some of the key features of your launchpad. Now am taking a look at our main page when you navigate to the URL shown previously. When you first get there if you have not yet signed in, you will be browsing the pages as anonymous user. You'll see in the top left picture here that on the top right where is a sign in we have not authenticated against the application, and as such we don't have full access to all of the capabilities of library on the bottom right you can see that I have logged in and authenticated, and this could be using your SAP ID service such as your service marketplace user. Now when you're authenticated, some things will visibly change, such as on the bottom left you'll see that the the bottom manage profiles and filters that's available for authenticated users. Now the bottom get SAP Fiori App recommendations has not changed between the two. But if you were to select it as anonymous user, you would be required to authenticate before you could perform that function. Now once we've authenticated let's review briefly some of the main aspects of the main page. The top left you'll see a set of categories. Now as we get deeper into the library, we're going to be talking a lot about filters and the ability to filter the library. Think of categories as really just predefined top level filters, that make it easier to get into a specific context such as mySAP business suite user or MS for honey user. So really those are just top level filters that are very convenient app recommendations. If you have them you'll always see the button to get them, but if you already have defined some of them, you'll see an app recommendations category we'll take a look at that shortly. On the bottom left is the ability to drill in and manage filters and profiles. These are really areas that you can predefine filters and other types of lists for convenient use later. On the top right to drill into additional help, you can simply select the question mark icon. And then on the bottom right a couple buttons for getting legal information or even for providing a feedback or sharing a page which can be very convenient to share with your colleagues at your organization. On an app details page, you will see on the left hand side a list of any applications that fit the currently defined filters that you've selected. We're going to go into this in a demo later, but the filtered App list is on the left. For any selected application such as the my inbox app here, there will be a couple of tabs available. Above that you'll see core app details, such as the available product that is available for the type of application Fiori has a couple of categories of applications such as facets and transactional apps. Then if there's a required database type which is important to many customers, and which form factors that works on obviously fury in most cases, is designed to work on any form factor effect Fiori as a design standard is, but if the technology you're reviewing here something older like SAP GUI in the library, that might be actually limited to one or just a few form factors. Now below that the product features is where again you can get an overview of it there may be some screenshots of the application. Here we're showing the implementation Information tab, where you can get a lot of technical details around installation and configuration details. Again we're going to go over all of this later on, but this just gives you a high level view. And at the bottom there are two high level views a detail view like we're looking at here, and then there's a list of view and again we'll take a look at all of these. So that provides a high level overview of what it is. Next we're going to get into it and look at it live.