Embed Size (px)
Citation preview
Definition Paper
SAP Fiori
Document Version: 1.0.1 – 2016-07-26
PUBLIC
Qualities of SAP Fiori apps
2
PUBLIC
© 2016 SAP SE. All rights reserved.
Qualities of SAP Fiori apps
Executive Summary
Typographic Conventions
Type Style Description
Example Words or characters quoted from the screen. These include field names, screen titles,
pushbuttons labels, menu names, menu paths, and menu options.
Textual cross-references to other documents.
Example Emphasized words or expressions.
EXAMPLE Technical names of system objects. These include report names, program names,
transaction codes, table names, and key concepts of a programming language when
they are surrounded by body text, for example, SELECT and INCLUDE.
Example Output on the screen. This includes file and directory names and their paths, messages,
names of variables and parameters, source text, and names of installation, upgrade and
database tools.
Example Exact user entry. These are words or characters that you enter in the system exactly as
they appear in the documentation.
<Example> Variable user entry. Angle brackets indicate that you replace these words and
characters with appropriate entries to make entries in the system.
EXAMPLE Keys on the keyboard, for example, F2 or ENTER .
Qualities of SAP Fiori apps
Executive Summary
PUBLIC
© 2016 SAP SE. All rights reserved. 3
Document History
Version Date Change
1.0 07.07.2016 Initial official version
1.0.1 26.07.2016 Interoperability & Compatibility - process precision: Rules applicable to
stable releases.
Released for public.
4
PUBLIC
© 2016 SAP SE. All rights reserved.
Qualities of SAP Fiori apps
Executive Summary
Table of Contents
1 Executive Summary ................................................................................................................. 5 1.1 Motivation ......................................................................................................................................... 5 1.2 Purpose and Scope of this Document ........................................................................................... 5 1.3 Overview of the qualities and criteria ............................................................................................. 5
2 Definition ................................................................................................................................... 7 2.1 SAP Fiori UX Paradigms .................................................................................................................. 7 2.2 SAP Fiori app Development & Architecture Paradigms ............................................................... 7 2.3 Cloud Ready ..................................................................................................................................... 8 2.4 Mobile Ready .................................................................................................................................... 8 2.5 SAP Fiori System Landscape .......................................................................................................... 9 2.6 SAP Fiori Release & Maintenance strategy ................................................................................... 9
2.6.1 SAP Fiori, cloud edition ................................................................................................. 10 2.6.2 SAP Fiori On-Premise Edition ...................................................................................... 10 2.6.3 General Maintenance Strategy Considerations .......................................................... 11
2.7 Interoperable & Compatible .......................................................................................................... 11 2.8 Extensibility & Flexibility – Manage modification free adoption .................................................12 2.9 Performance....................................................................................................................................12
3 Appendix.................................................................................................................................. 14 3.1 Abbreviation List & Glossary ........................................................................................................ 14
Qualities of SAP Fiori apps
Executive Summary
PUBLIC
© 2016 SAP SE. All rights reserved. 5
1 Executive Summary
1.1 Motivation
When is an app a SAP Fiori app, rather than just an app? Is it enough for an app to look like SAP Fiori, or are
there other aspects which need to be fulfilled? And why should we care?
SAP Fiori is the new, award-winning user experience for SAP software, so it is very important to define a
minimal level of qualities which an app needs to fulfill in order to be called a SAP Fiori app. This is important in
order to safeguard the SAP Fiori reputation, so that expectations are consistently met when deploying and
using SAP Fiori apps. Also, such a definition allows partners to become certified as being able to build SAP
Fiori apps, and also opens the door to allow individual apps to be certified as being SAP Fiori apps.
1.2 Purpose and Scope of this Document
This document is aimed at customers and partners, and defines the qualities which need to be fulfilled by a
SAP Fiori app.
It covers design, technical and implementation criteria, defining qualities to be met beyond SAP product
standards.
It does not provide a comparison of SAP Fiori apps with other applications built by SAP or others.
The SAP Fiori visual theme can be used to enhance the overall user experience for existing applications,
“classic” UIs etc., i.e. for apps which do not fulfill all the criteria of SAP Fiori apps. This document does not
cover criteria for applying the SAP Fiori visual theme to existing applications (“classic” UIs). Examples of such
apps are those built with SAP Web Dynpro, SAP GUI for HTML or SAP GUI for Windows. Similarly, SAP Screen
Personas can be used by customers on top of SAP Fiori themed UIs (SAP Web Dynpro, SAP GUI) to further
simplify and enhance the user experience for customer-specific use cases; these also do not fulfill all the
criteria for SAP Fiori apps.
1.3 Overview of the qualities and criteria
Here is a brief overview of the qualities and main criteria which need to be fulfilled. The rest of the document
explains these in more detail.
Design: SAP Fiori apps need to follow the SAP Fiori user experience design principles (role-based, adaptive,
simple, coherent and delightful). Those delivered by SAP need to follow the design-driven development
process and pass design-gates.
Architecture: The main aspects to highlight here are that SAP Fiori apps are platform-independent web apps
built with SAPUI5, with one dedicated OData service per app. They run in the SAP Fiori launchpad using intent-
based navigation, and can run on mobile and desktop devices.
Cloud readiness: SAP Fiori apps need to be developed in a stack-agnostic way, i.e. call platform capabilities in
a generic way via offered unified shell services, and only use platform-specific functions with an availability
check first. They must run on SAP HANA Cloud Platform and hence require an app descriptor file to configure
its behavior.
Mobile readiness: Every SAP Fiori app must run on mobile devices along the native app paradigm. They can
be consumed via a mobile browser, by SAP Fiori Client and as self-contained native packaged apps.
6
PUBLIC
© 2016 SAP SE. All rights reserved.
Qualities of SAP Fiori apps
Executive Summary
System landscape: SAP Fiori apps must run and be tested in a system landscape which fulfill the System
Landscape Governance Board’s “Landscape Deployment of SAP Fiori front-end server (FES)”.
Release and maintenance strategy: SAP Fiori Apps support the principles of enterprise lifecycle
management, independent of the runtime environment, such as supporting staged development and transport
of applications between stages (development, test, productive), logging and tracing etc.
Compatibility and interoperability – main aspects: Strict compatibility across versions is required,
dependencies to other software component versions must be maintained; synchronous upgrades of software
component versions distributed across multiple systems are not required.
Flexibility and extensibility: SAP Fiori apps allow customers to extend both the UI and the back-end.
SAP Product Standards: Performance – the end-to-end response times must not exceed 1s for simple
interactions and 3s for complex UIs, with not more than one and two round-trips respectively.
Qualities of SAP Fiori apps
Definition
PUBLIC
© 2016 SAP SE. All rights reserved. 7
2 Definition
SAP Fiori apps need to be perceived as consistent from an end user, admin and developer perspective. In the
following chapters key aspects are explained in detail to define what a SAP Fiori app must or should comply
with.
2.1 SAP Fiori UX Paradigms
SAP Fiori apps are implemented so that they are
o Role Based: Define and design as per the needs of business users and provide the person in a certain
role (the persona) with the tools required to perform one’s job.
o Simple: Focuses only on what’s important to the user and hides unnecessary complexities
o Coherent: Provides one fluid, intuitive experience, for any business process and task.
o Adaptive: Supports how and where you work, at any time, with any device.
o Delightful: Makes an emotional connection.
SAP Fiori apps run in the SAP Fiori launchpad, which provides a single source of entry for all applications and
systems, and run platform and device independent. For more details please refer to chapter 2.3.
SAP Fiori apps are designed for people. It is essential to have a thorough understanding of the user, his needs,
and motivation as well as his work context before design starts. This means that the scope and functionality of
an application must not be determined by an existing transaction but by the informational and functional
requirements of the user in a given task. All design efforts should go into the definition of the use case and task
flow to identify potential improvements of efficiency, effectiveness or joy of use (Discover).
SAP Fiori apps are highly interconnected so that a user will interact with several applications during the day or
even within the same process. Applications should therefore look and behave in a similar and predictive
manner. Consistency across applications is essential to usability and learnability of the SAP Fiori app portfolio.
Design guidelines and reviews, standard controls and floor plans are means to achieve such consistency in a
scalable manner. Users will access their apps through different devices and channels and users should have a
coherent experience across all devices. During the design phase all device form factors should be evaluated
for specific requirements that should be taken into account to better adapt the design. (Design).
SAP Fiori apps can be built and designed in many different ways to both allow flexibility as well as support
consistency. Still there are many potential sources of errors or degradations in design and implementation
quality that can occur during the development process. Technical or resource constraints can lead to a change
in scope or in the way the application is implemented. The SAP Fiori product line should always stand for
quality in design and implementation and we need to look into every detail of the implementation to avoid
errors or design glitches in the final product (Develop).
Further information can be found in https://experience.sap.com/fiori-design/.
2.2 SAP Fiori app Development & Architecture Paradigms
The following rules are fundamental for any SAP Fiori app development.
o SAP Fiori apps must have an approved UX design.
8
PUBLIC
© 2016 SAP SE. All rights reserved.
Qualities of SAP Fiori apps
Definition
o SAP Fiori UIs are built with SAPUI5.
o SAP Fiori apps are based on OData services.
o One SAP Fiori app - one dedicated OData service.
o SAP Fiori UIs and OData services must be defined in different software components.
o Every SAP Fiori app is defined by a set of metadata.
o No custom CSS is allowed for SAP Fiori Apps.
o Every SAP Fiori app must run as platform independent web app.
o Every SAP Fiori app must run in the SAP Fiori launchpad and use intent based navigation.
o Every SAP Fiori app must run on mobile devices along the native application paradigm.
The compliance has its foundation in the architecture. Following the rules is essential to enable a sophisticated
orchestration and common behavior of the various SAP Fiori apps. Compliance to these rules ensures e.g. the
software lifecycle of these apps can be managed.
SAP Fiori apps - Golden Rules for Implementation (ICC department)
SAP Fiori Architecture for SAP S/4HANA
2.3 Cloud Ready
SAP Fiori apps are cloud-ready by nature as they are developed in a stack-agnostic way. This means, they are
built in a platform-independent way by using SAPUI5. Hence, the same SAP Fiori app is able to run on an SAP
Fiori front-end server (FES), the SAP HANA Cloud Platform (HCP) or as part of a capsulated hybrid web
application without modifying the app itself. In order to archive this, developers may not use platform-specific
functionality without an availability check.
Platform capabilities like personalization or navigation are called in a generic way via offered unified shell
services. A SAP Fiori app…
o Does not call directly services from sap.ui2 namespace.
o Interacts with the shell UI only using shell services.
o Uses sap.ushell.Container.getService(“[service name]”) to get a proper instance for any shell service.
Moreover, the cloud runtime environment behaves the same as the on premise. Innovative Smart Controls
requiring the SAP Fiori Layered Repository (LRep) work here the same way along with advanced features like
the embedded runtime adaptation (RTA). Extensions by partners and customers can be easily done by
leveraging the integrated SAP Web IDE functionality.
The only thing that needs to be done is adding an application descriptor file that configures the behavior (e.g.
caching or routes) of the HTML5 application on HCP.
2.4 Mobile Ready
SAP Fiori apps are mobile ready by nature.
SAP Fiori apps using the sap.m SAPUI5 library provide adaptivity across various form factors: the same
application can run on a desktop, tablet and smartphone device.
On mobile devices SAP Fiori apps can be consumed via a mobile browser, SAP Fiori Client and as self-
contained native packaged applications. An application specific app descriptor is mandatory for packaging a
SAP Fiori application as a native mobile application.
Furthermore SAP Fiori apps have the capability to make use of native features of a mobile device like camera,
PIM integration assets, location based data, offline usage and many more. In order to integrate these
capabilities a SAP Fiori app developer needs to adopt his front-end coding by using additional exposed APIs
Qualities of SAP Fiori apps
Definition
PUBLIC
© 2016 SAP SE. All rights reserved. 9
from Apache Cordova & SAP Mobile SDK. These so called mobile qualities can be consumed when running
inside the SAP Fiori Client or the app has to be packaged as native mobile app.
For proper mobile behavior every SAP Fiori app must run on mobile devices along the native app paradigm.
Please refer to chapter 2.2 and Guideline Mobilizing SAP Fiori, Integration of SAP Mobile Platform into SAP
Fiori Landscape (on SCN) and Offline Enablement for Decision Makers (on SDN).
2.5 SAP Fiori System Landscape
From a system landscape planning and operations perspective all SAP Fiori apps must run and be tested in a
system landscape which fulfill the System Landscape Governance Board’s “Landscape Deployment of SAP
Fiori front-end server (FES)”, which is officially approved by the System Landscape Governance Board
(SLGB).
Due to the highly agile environment in this area, the recommendations and also the other deployment options
are updated regularly.
The process how to obtain a recommendation or approved option is defined within the UX Explorer :
Landscape Deployment of SAP Fiori front-end server (FES)
2.6 SAP Fiori Release & Maintenance strategy
An SAP Fiori app is considered to be built-once, and can be packaged and deployed to either on premise
runtime environments as well as into SAP cloud based environments fulfilling customers demand for mission
critical software in an enterprise landscape
Therefore SAP Fiori apps support the principles of enterprise lifecycle management, independent of the
runtime environment:
Automatic creation and selection of technical artifacts, like technical names, technical users, etc. with
centrally defined defaults.
Recoverability: resume deployment from the point of failure of a multi-step operation.
Support for staged development and transport of applications between stages
Transactional consistency: a deployment either finishes successfully or fails completely (rollback),
leaving no inconsistent intermediate states.
Logging, tracing and coherent auditability of the entire application lifecycle.
Implement version evolution policies, e.g., to protect against downgrades.
Software source policies: deploy only signed content from certain vendors.
Query interface for application monitoring and support tools (application state, dependencies, version
history, etc.)
10
PUBLIC
© 2016 SAP SE. All rights reserved.
Qualities of SAP Fiori apps
Definition
2.6.1 SAP Fiori, cloud edition
Cloud platforms differ from traditional application servers in the flexible way they support diverse application
runtime technologies. All these parts, UIs, services and data models, must still run as a coherent application.
Cloud platforms hence give weight to an agnostic as well as a coherent deployment model for SAP Fiori apps:
Their dependencies are described in a platform neutral way.
Developed in one coherent development system.
All parts are deployed together, in the right order, automatically.
Module updates are managed without breaking the application.
I.e. SAP Fiori apps are deployed as multi-target applications (MTA) addressing this life-cycle and orchestration
complexity of continuous deployment for cloud platforms. A multi-target application (MTA) is comprised of
multiple parts, created with different technologies and deployed to different targets, but with a single,
common lifecycle.
The delivery is foreseen to be first done into an SAP owned SAP cloud account, where customer accounts can
subscribe to. An actual physical deployment into a customer account does not exist.
Despite the SAP Fiori app itself, the corresponding back-end preparations (OData service implementation
Add-Ons and the cloud connector) need to be put into consideration when talking about the SAP Fiori app life
cycle.
For implementation, the SAP Fiori app Reference Library provides in this respect a systematic overview about
all SAP Fiori apps. The data in the Maintenance Planner allows IT to plan the changes based on the system
compatibility check to update/upgrade their systems.
o Select SAP Fiori apps in the SAP Fiori app Reference Library and navigate to the Maintenance Planner.
o Apply the product change on each system represented in Maintenance Planner to generate a machine
readable xml file describing the targeted systems state and to supply all required software archives to
reach it.
o With the help of Maintenance Planner, trigger the creation a SAP cloud account, adopt your existing
SAP cloud account and/or subscribe to the chosen set of SAP Fiori apps
o Use Software Update Manager (SUM) to do the update/upgrade for the Business Suite back-end
based system consuming the xml file and the downloaded software archives for the OData back-end
add-ons.
Maintenance Planner is the tool for customers to visualize systems with the focus on installed software to plan
and to simulate software changes and to analyze the system impacts. It is hosted at SAP Service Marketplace.
2.6.2 SAP Fiori On-Premise Edition
In the on premise landscapes SAP Fiori apps are delivered as ABAP Add-Ons and the SAP Fiori architecture
allows an upgrade of the SAP Fiori front-end server independent from the SAP Business Suite back-end. SAP
Fiori apps have to adhere to this paradigm.
SAP Fiori apps nevertheless will require a minimum stack to run. This varies from app to app; the SAP Fiori app
Reference Library provides in this respect a systematic overview about all SAP Fiori apps.
The data in the Maintenance Planner allows IT to plan the changes based on the system compatibility check to
update/upgrade their systems.
Qualities of SAP Fiori apps
Definition
PUBLIC
© 2016 SAP SE. All rights reserved. 11
o Apply the product change on each system represented in Maintenance Planner to generate a machine
readable xml file describing the targeted systems state and to supply all required software archives to
reach it.
o Use Software Update Manager (SUM) to do the update/upgrade on each NetWeaver based system
(front-end server and back-end server) consuming the xml file and the downloaded software archives
(SAP Fiori add-ons and OData back-end add-ons).
2.6.3 General Maintenance Strategy Considerations
So the independence of the SAP Fiori front-end server is a big advantage especially when it comes to multiple
back-end systems and the need to upgrade only one front-end server to consume the latest SAP Fiori apps
and UX.
The lifecycle of SAP Fiori apps considers the following approach:
Innovation Stack – Initial phase of a release with quarterly upgrades to next SP level delivering features and
functions. For our customers it is mandatory to upgrade to the next SP level if they want to consume the
Innovation code line and gain the advantages from new features, functions and UX.
Stable Stack – Phase of a release starting after the innovation stack ends. Here SAP delivers fixes only.
2.7 Interoperable & Compatible
The fundamental rules for SAP Fiori apps as described above demand a decoupling with a SAPUI5 based UI
and OData services to access business data in back-end systems. This decoupling not only aims at software
design, but also affects the cut of software components resulting in a split of UI and back-end artefacts into
different software components. As a matter of fact, their concrete software component versions (SWCVs) are
not necessarily co-deployed in the same system but rather distributed across the landscape. For example the
product UIs’ SWCVs could be deployed on a central SAP Fiori front-end server/SAP Gateway hub while each
of the back-end systems connected to the Gateway relies on own software component versions.
Development artefacts and their interface may need to evolve over time. In respect of a distributed system
landscape and potentially lagged deployment of either the UI or service modifications a compatibility of
changes is demanded. Unless synchronous upgrades can be assured (e.g. by a cloud or customer operation
model or by restriction to a single system through front- and back-end co-deployment) a corridor of
compatible changes has to be considered. Ideally, SAP Fiori apps shall accomplish this corridor bi-
directionally, i.e. an older UI shall be interoperable with a newer service and vice versa. At component upgrade
cross-compatibility guarantees business continuity of the regarding application.
Process
In stable releases development has to consider rules for evolving OData services in a compatible way. Changes
are reflected in the services metadata which may be individually interpreted by the UI to establish a compatible
behavior. A grouping of changes is possible by using a service schema version which is again interpreted in
conditional UI logic.
Once the UI and/or service side development has been accomplished cross-compatibility tests should be run
to verify the interoperability.
12
PUBLIC
© 2016 SAP SE. All rights reserved.
Qualities of SAP Fiori apps
Definition
2.8 Extensibility & Flexibility – Manage modification free adoption
Extensibility enables partners and customers to enhance SAP software modification free – both on premise
and in the cloud edition. In the cloud edition, the most important extensibility tasks can be realized by key user
tools.
SAP Fiori apps allow both an enhancement of the UI as well as back-end extensibility. UI extensibility means
modification free changes like logo or theme changes, hiding fields, adding fields or changing the terminology
– all realized by runtime authoring tools directly from the SAP Fiori UI. This is always possible when the UI is
based on Smart Controls or SAP Fiori Elements. Some other UI controls (like Simple Form) also support this
flexibility.
2.9 Performance
We use the well-known UX categorization of a user interaction step (UIS) to define
o the End-to-End Response time KPIs
o the number of sequential roundtrips on the critical path
UIS Category End-to-End
Response
Time [ms]
#
Round-
trips
Description
Instant
Feedback
< 150 0 Typically no WAN request is possible e.g.: processing on
the front-end: mouse over, highlighting of fields,
validations and determinations without server requests
Simple < 1000 1 Majority of user interaction where the application server
has to be involved are expected in this category
Complex < 3000 2 Less than 20% of user interactions are expected in this
category e.g.: analytics, planning
Exceptionally
Complex
KPI has to be set individually by Product Owner.
Typically end user expects an interaction pattern which
signals continuously the progress (e.g. via progress
indicator) and which (optionally) allows to push the
running execution to background (being asynchronously
informed afterwards)
In exceptionally cases the simple interactions “Open application” and “Save operation” may take up to
2000ms. The End-to-End Response times are defined for a desktop browser with LAN-Connectivity (minimum
latency).
End-to-End Response times and number of Roundtrips shall be met under the assumption that all caches
(Client caches, intermediate caches, server caches, and database caches) are filled. In environments with
latency the KPIs are increased with n * latency [ms] (n = # of Roundtrips).
Qualities of SAP Fiori apps
Definition
PUBLIC
© 2016 SAP SE. All rights reserved. 13
Very important for good SAP Fiori app is (last but not least): Check for memory leaks - especially in the
JavaScript code on client side.
Process
Classify the user interaction steps of your SAP Fiori app. Measure the response time and the number of
sequential round trips. Measure the memory consumption on client side. Tools like the chrome developer tool
should be used to measure response time and memory consumption.
14
PUBLIC
© 2016 SAP SE. All rights reserved.
Qualities of SAP Fiori apps
Appendix
3 Appendix
3.1 Abbreviation List & Glossary
Abbreviation
Term
API Application Interface
BSP Business server pages
CSS Custom style sheets
FES SAP Fiori front-end server
FC SAP Fiori Client
FLP SAP Fiori launchpad
GUI Graphical User Interface Technology
HCP SAP HANA Cloud Platform
KPI Key Performance Indicator
LAN Local area network
LRep Layered repository
MTA Multi-target applications
NW SAP NetWeaver
SDK Software development kit
SP Support package
SUM Software Update Manager
SWCV Software component version
UI User Interface
UX User Experience
WAN Wireless area network
www.sap.com/contactsap
© 2016 SAP SE. 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 AG.
The information contained herein may be changed without prior
notice.
Some software products marketed by SAP SE and its distributors
contain proprietary software components of other software
vendors.
Microsoft, Windows, Excel, Outlook, and PowerPoint are registered
trademarks of Microsoft Corporation.
IBM, DB2, DB2 Universal Database, System ads, System i5, System
p, System p5, System x, System z, System z10, System z9, z10, z9,
iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS,
S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise
Server, PowerVM, Power Architecture, POWER6+, POWER6,
POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes,
BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2
Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX,
Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are
trademarks or registered trademarks of IBM Corporation.
Linux is the registered trademark of Linus Torvalds in the U.S. and
other countries.
Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either
trademarks or registered trademarks of Adobe Systems
Incorporated in the United States and/or other countries.
Oracle is a registered trademark of Oracle Corporation.
UNIX, X/Open, OSF/1, and Motif are registered trademarks of the
Open Group.
Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame,
VideoFrame, and MultiWin are trademarks or registered trademarks
of Citrix Systems, Inc.
HTML, XML, XHTML and W3C are trademarks or registered
trademarks of W3C®, World Wide Web Consortium, Massachusetts
Institute of Technology.
Java is a registered trademark of Sun Microsystems, Inc.
JavaScript is a registered trademark of Sun Microsystems, Inc.,
used under license for technology invented and implemented by
Netscape.
SAP, R/3, xApps, xApp, SAP NetWeaver, Duet, PartnerEdge,
ByDesign, SAP Business ByDesign, and other SAP products and
services mentioned herein as well as their respective logos are
trademarks or registered trademarks of SAP SE in Germany and in
several other countries all over the world. All other product and
service names mentioned are the trademarks of their respective
companies. Data contained in this document serves informational
purposes only. National product specifications may vary.
These materials are subject to change without notice. These
materials are provided by SAP SE and its affiliated companies ("SAP
Group") for informational purposes only, without representation or
warranty of any kind, and SAP Group shall not be liable for errors or
omissions with respect to the materials. The only warranties for SAP
Group 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.
