Upload
mahesh22pp
View
218
Download
0
Embed Size (px)
DESCRIPTION
no
Citation preview
2015 SAP SE or an SAP affiliate company. All rights reserved. 1 Public
Week 2 Unit 3: SAP Fiori Decomposition and
Re-composition
2015 SAP SE or an SAP affiliate company. All rights reserved. 2 Public
SAP Fiori Decomposition and Re-composition Transactions vs. Apps
Transactions Apps
2015 SAP SE or an SAP affiliate company. All rights reserved. 3 Public
SAP Fiori Decomposition and Re-composition Transactions: Designed from a System Perspective
BACK END
Transaction
Object (such as sales order)
CONSUMPTION anybody
Transaction
Transaction Transaction
(create, change, query, delete,...)
2015 SAP SE or an SAP affiliate company. All rights reserved. 4 Public
SAP Fiori Decomposition and Re-composition Transactions from a User Perspective Complexity
MEGA TRANSACTION
Overload & Irrelevant
This information is not relevant to me. Why is it on my screen?
Create Sales Order (VA01)
?
2015 SAP SE or an SAP affiliate company. All rights reserved. 5 Public
SAP Fiori Decomposition and Re-composition Transactions from a User Perspective Complexity (Continued)
MD04, MD05, MD06, MD07
TRANSACTION TRANSACTION
These transactions look so similar to me. Which transaction should I use for what?
USER GETS LOST
I have a task
TRANSACTION TRANSACTION
2015 SAP SE or an SAP affiliate company. All rights reserved. 6 Public
Context
SAP Fiori Decomposition and Re-composition Apps Approach: User/Task-Centric
BACK END
CONSUMPTION
App
Task
Purpose-built to support a persona (or
multiple personas with very similar needs) to
complete a task in their use context
Persona
Data mapping to back-end structure
2015 SAP SE or an SAP affiliate company. All rights reserved. 7 Public
SAP Fiori Decomposition and Re-composition Decomposition & Composition
MEGA TRANSACTION
Persona 1 Persona 2 Persona 3
App App
anybody
DECOMPOSITION
App
COMPOSITION TRANSACTION TRANSACTION
TRANSACTION TRANSACTION
I have a task I have a task
2015 SAP SE or an SAP affiliate company. All rights reserved. 8 Public
SAP Fiori Decomposition and Re-composition Create Sales Order Example: Segment, Research, and Storytell
Manufacturing Company X Identify Human Tasks
Purpose
Primary Persona
Trigger Point
Context
Input
Output
Brainstorm and Understand Process
2015 SAP SE or an SAP affiliate company. All rights reserved. 9 Public
SAP Fiori Decomposition and Re-composition Create Sales Order Example: Define, Prioritize, and Design
Customer
Buyer
Sales
Operation
Customer
Service
Agent
Shopping App
Amazon-like self-service
shopping paradigm
Productivity-oriented data
entry paradigm
Sales Rep
Create Sales Order App
Distributor
Buyer
Create Sales Order App
1 2 3
For Create Sales Order the sales rep persona was prioritized first
Prioritize
Customer
Buyer
Sales
Operation
Customer
Service
Agent
Shopping App
Amazon-like self-service
shopping paradigm
Productivity-oriented
data entry paradigm
Sales Rep
Create Sales Order App
Distributor
Buyer
Create Sales Order App
Untrained users
Very often mobile
Only need to specify the buying requirements instead of entering
full order info
Need decision support info like product recommendations
Trained users
Mostly desktop
Need to enter complete order information
Define Apps Based on Tasks & Use Cases
2015 SAP SE or an SAP affiliate company. All rights reserved. 10 Public
SAP Fiori Decomposition and Re-composition Recommended Process to Derive and Design Apps
Market STP
(Segmentation, Targeting, and
Positioning)
Customer Engagement & User
Research
(Personas, Insights, PoVs)
E2E Process Modeling
(Process Model, E2E Storyboard)
1 2 3
Define Apps
(Tasks & Apps Abstraction) Prioritization Design for Individual Apps
4 5 6
2015 SAP SE or an SAP affiliate company. All rights reserved. 11 Public
Thank you
Contact information:
2015 SAP SE or an SAP affiliate company. All rights reserved. 12 Public
2015 SAP SE or an SAP affiliate company. All rights reserved.
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP SE or an SAP affiliate company.
SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE (or an SAP affiliate
company) in Germany and other countries. Please see http://global12.sap.com/corporate-en/legal/copyright/index.epx for additional trademark information and notices.
Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors.
National product specifications may vary.
These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or warranty of any kind, and SAP SE or its
affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP SE or SAP affiliate company products and
services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as
constituting an additional warranty.
In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or any related presentation, or to develop
or release any functionality mentioned therein. This document, or any related presentation, and SAP SEs or its affiliated companies strategy and possible future developments, products, and/or platform directions and functionality are all subject to change and may be changed by SAP SE or its affiliated companies at any time
for any reason without notice. The information in this document is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. All forward-
looking statements are subject to various risks and uncertainties that could cause actual results to differ materially from expectations. Readers are cautioned not to place
undue reliance on these forward-looking statements, which speak only as of their dates, and they should not be relied upon in making purchasing decisions.