Embed Size (px)
DESCRIPTION
Lonneke Dikmans, Process analysts and developers often make the mistake of equating user interaction with process flow. Analysts tend to model the user interaction in the process and then ask the developers to generate/build a screen for every human task that is modeled. This results in user interfaces that are hard to use, error prone and inflexible and in processes that are very hard to change. Saving money in the project by generating a screen for every human task flow cost money in the long run. A better approach is to design both the process flow and the user experience (user interface(s). This way you will be more flexible and it will result in a better user experience.
Citation preview
1 | 15
Stop generating your User Interface! Start designing IT Lonneke Dikmans Maart 2014| Nieuwegein
2 | 15
Introduction
Agenda ● Generating the UI based on the process design ● Alternative approach ● Result ● Conclusion
About me ● Consultant and Managing partner at Vennster ● Specializing in SOA and BPM ● Oracle Ace Director ● Roots in UX (cognitive science)
3 | 15
Generating the UI | Case 1 Building Permits
Process ● Building permits at the city of Rotterdam ● Combination of automated activities (services) and human tasks
Different roles ● Applicant who wants to build something ● Front office that receives the application and communicates ● Building inspector who reviews the application ● Finance department who sends the invoice ● (External) advisors
4 | 15
Generating the UI | Case 1 Building Permit
Human Task 1
Service Task
Human Task 2 …
Applica'on Received
Applica'on evaluated
BPEL Process
UI
Screen 1 Screen 2 Screen …
5 | 15
The problem | Generating the User interface
Process perspective ● Steps become too fine grained ● Too much data need to be ‘carried’ in the process
User interface perspective ● Organized in terms of the ‘process unit’ (permit application) ● Inflexible for the user, no short cuts, bulk edits ● Too little information, only task data
6 | 15
Agenda
● Generating the UI based on the process design ● Alternative approach ● Result ● Conclusion
7 | 15
Alternative Approach| Case 2. ESS and MSS
Process ● Expense report self service for managers and employees ● Combination of automated tasks and human tasks
Different roles ● Employee who made the expense and enters the report ● Manager who approves the expense ● Finance department who approves and pays the expenses
8 | 15
Alternative Approach | BPM & UX
Design process based on BPMN Method and Style ● Choose the ‘object’ of your process ● Start with high level process map ● High level process
Design Experience based on User Centered Design ● Determine your personas ● Determine the scenarios ● Create interaction design
9 | 15
Agenda
● Generating the UI based on the process design ● Alternative approach ● Result ● Conclusion
10 | 15
Result | Process
11 | 15
Result | User experience
Personas ● Peter - employee ● John – manager of Peter ● Petra – HR employee
Scenarios ● Create an expense report for a meeting out of the office ● Create an expense report for a meal and overtime
12 | 15
Result | UX
13 | 15
Human Task 1 Service Task Human Task
2 …
Start End Process
Human Task 1 Service Task Human Task
2 …
Start End Process
Result | Architecture
EBS 12 Services &
BPM
GUI
DB
REST Services
PL/SQL
web
services
GUI
14 | 15
Interface
Enterprise Service Bus
User Interface Business Process Management
& Case management
Business Rules Engine
IdenJty and Access
Management
Registry and Repository
Policies
Interface
Policies
Interface
Policies
Interface
Policies
Interface
Policies
Evt Evt
Evt Evt Evt
Evt
Implementa'on Impl.
Development Tooling
Design Tooling
Impl.
15 | 15
Agenda
● Generating the UI based on the process design ● Alternative approach ● Result ● Conclusion
16 | 15
Conclusion
Advantages of this approach ● Application appeals to users and satisfies there needs ● Process is monitored and executed in compliance with tax rules ● Parallel execution of different layers, so no delay ● Extra cost in beginning of project, less cost in maintenance • Easy to change • Less need to change
17 | 15
Stop generating your User Interface!Start designing IT Lonneke Dikmans Maart 2014| Nieuwegein
