DESIGN GATE 1 SAP FIORI FOR IOS INSERT

DESIGN GATE 1 SAP FIORI FOR IOS INSERT NAME OF THE PROJECT INSERT NAME(S) OF THE DESIGNER(S) INSERT TODAYS DATE APP SUMMARY ENTER A QUICK, ONE-LINE HEADLINE HERE This text section should provide an overview of the most important aspects of the app. Elements to touch upon include: the target user(s), details about the use case, where the app will be used (indoors, outdoors, etc.), which device(s) the app has been designed for, and the kinds of data or information the user will consume or act upon with the app (e.g., entering text, capturing images, scanning barcodes, listening to audio, etc.). In terms of format, the App Summary should be written in present

tense (e.g., The Project Assistant app provides team managers with at-a-glance notifications and relevant action items for on-the-go work situations.). The summary does not need to be longer than one to two paragraphs. Be sure that it does, however, cover the tasks and individual screens content shown later in this document. Insert name of the project / Insert name(s) of the designer(s) / Insert date SAP Design / D Gate 1 / App Summary KEY SCREENS COMPACT SCREEN 1 NAME Insert name of the project / Insert name(s) of the designer(s) / Insert date SCREEN 2 NAME

SCREEN 3 NAME SAP Design / D Gate 1 / Key Screens KEY SCREENS REGULAR SCREEN 1 NAME Insert name of the project / Insert name(s) of the designer(s) / Insert date SAP Design / D Gate 1 / Key Screens INFORMATION ARCHITECTURE UNDERSTANDING CONTENT SECTIONS AND HIERARCHY

TITLE Insert a diagram that illustrates the main sections of the app and the relationships CONTENT 1 CONTENT 2 CONTENT 3 between them. It should make clear whether the apps navigation paradigm is flat, hierarchical, or a blend of the two. Each box should include a screen title TITLE TITLE

TITLE CONTENT 1 CONTENT 2 CONTENT 3 CONTENT 1 CONTENT 2 CONTENT 3 CONTENT 1 CONTENT 2 CONTENT 3 and the main content sections found on the screen. These content sections should be high-level for instance, contacts or attachments.

TITLE CONTENT 1 CONTENT 2 CONTENT 3 Insert name of the project / Insert name(s) of the designer(s) / Insert date SAP Design / D Gate 1 / Information Architecture GOLDEN THREAD ENTER THE PERSONAS NAME, JOB TITLE 1.This text should describe the ideal scenario where the app in question is solving the users daily challenges. The Golden Thread should touch upon some of the key goals, responsibilities, needs, and pain points the persona experiences during a typical day. It should be fairly detailed, but does not need to go into every single detail of the

1.Please note that the purpose of the Golden Thread is to highlight when and how the app helps to make the personas work life easier. It should be told as a narrative, and should not just resemble a list of app features. personas day only the most important aspects. 2.A new paragraph goes here, and it describes more key details of the 2.The narrative can start at the beginning of the personas day or just before the workday begins, and it can end at the end of the workday personas ideal work day. Details that are relevant to the story would go here. More details would go here. or when the persona goes to bed whatever makes the most sense for the context of the project. Listing the times of events is optional. 3.In terms of format, the Golden Thread should be written in present tense (e.g., Sam sits down in the conference room and receives

another message notification). Each new subject can be discussed in a new paragraph to make it easy for the reader to follow the story, and key points can be highlighted in medium/bold text. Insert name of the project / Insert name(s) of the designer(s) / Insert date SAP Design / D Gate 1 / Golden Thread GOLDEN THREAD (EXAMPLE) MICHAEL, IT PROJECT MANAGER 1. Michael is an IT Project Manager currently managing two remote projects. During breakfast, he is notified of several issues that arose overnight and require his immediate attention. 2. One of Michaels team members, Thilo, hasn't updated one of his tasks. The task is due by the end of the week and is in danger of delaying a work package. Michael requests an update from Thilo for

1. As the issue is time sensitive, Michael decided to reveal it on his timeline to keep track of it and ensure its solved in time. 2. Michael realizes that one of the Work Packages is due soon and has a few Issues and decides to add Sean as a Delegate to the Work Package and get it back on track. more information, and subscribes to all updates on the Task. 3. At the end of the day, Michael knows that everything for this project 3. Michael is preparing for an on-site meeting with his team members. Based on the status of tasks, issues and deadlines he creates a new is on track. He gives his manager a quick informal update on budget remaining and the teams current burndown. Meeting with selected Agenda talking points and sends it to the team. 4.Later that day, Michael is sees an issue related to the task he had asked Thilo to update him on earlier. Thilo needs additional help from someone with specific experience to complete the task. Michael

assigns one of the suggested members. Insert name of the project / Insert name(s) of the designer(s) / Insert date SAP Design / D Gate 1 / Golden Thread TASK FLOWS SAP Design / D Gate 1 / Task Flows INSERT NAME OF TASK #1 INSERT A BRIEF DESCRIPTION EXPLAINING THE TASK. (THE FLOW NEEDS TO BE END-TO-END.) Insert name of the project / Insert name(s) of the designer(s) / Insert date SAP Design / D Gate 1 / Task Flows EXAMPLE: REQUEST UPDATE

ONE OF MICHAELS TEAM MEMBERS, THILO, HASN'T UPDATED ONE OF HIS TASKS. THE TASK IS DUE BY THE END OF THE WEEK AND IS IN DANGER OF DELAYING A WORK PACKAGE. Insert name of the project / Insert name(s) of the designer(s) / Insert date SAP Design / D Gate 1 / Task Flows INSERT NAME OF TASK INSERT NAME OF TASK #1 #1 INSERTAABRIEF BRIEFDESCRIPTION DESCRIPTIONEXPLAINING EXPLAINING THE TASK. (THE FLOW

NEEDS END-TO-END.) INSERT THE TASK. (THE FLOW NEEDS TOTO BEBE END-TO-END.) Insert Insert name nameofofthe the project project

/ Insert / Insert name(s) name(s) of the of the designer(s) designer(s) / Insert / Insert datedate SAPDesign Design// DDGate Gate 11 // Task Task Flows Flows SAP

INSERT NAME OF TASK #1 INSERT A BRIEF DESCRIPTION EXPLAINING THE TASK. (THE FLOW NEEDS TO BE END-TO-END.) Insert name of the project / Insert name(s) of the designer(s) / Insert date SAP Design / D Gate 1 / Task Flows INDIVIDUAL SCREENS SAP Design / D Gate 1 / Individual Screens INSERT SCREEN NAME IF THE SCREEN IS TALLER THAN THE FRAME, INCLUDE AN IMAGE AT FULL HEIGHT. Insert name of the project / Insert name(s) of the designer(s) / Insert date

SAP Design / D Gate 1 / Individual Screens OVERVIEW (EXAMPLE) Insert name of the project / Insert name(s) of the designer(s) / Insert date SAP Design / D Gate 1 / Individual Screens