Implementing a Web Client for Integrated Data, Role ...€¦ · Implementing a Web Client for...
Transcript of Implementing a Web Client for Integrated Data, Role ...€¦ · Implementing a Web Client for...
Software Engineering for Business Information Systems (sebis)
Department of Informatics
Technische Universität München, Germany
wwwmatthes.in.tum.de
Implementing a Web Client for Integrated
Data, Role, Function, and Task ModellingMaster’s Thesis final presentation
Tobias Schrade, 1st August 2016, Garching
Hybrid Wikis as a tool to model enterprise information systems
Hybrid Wikis are currently missing an integrated user-interface for data,
role, function and task modelling
The prototype implemented during this thesis
Introduction
© sebisMaster’s Thesis final presentation, 1st August 2016 2
Research Objective: Facilitate data, role, function and task modelling
within a hybrid wiki platform with the help of a web based user interface to
provide a way to generate and administrate the above mentioned models.
Research Questions:
Q1: „How does an integrated meta-model for data, role, function and task
models look like?
Q2: „How to design an integrated user interface for the management of
data, role function and task models?“
Research Objective and Questions
© sebisMaster’s Thesis final presentation, 1st August 2016 3
Role Model
© sebisMaster’s Thesis final presentation, 1st August 2016 4
Workspace
1..*
Attribute
has ▼
*
Entity
AttributeDefinition
has ▼
*
EntityTypeis of type ►
is defined by ►
*
0..1*
0..1*
Group User
Principal*
*
«interface»
AccessControlled
Is allowed to read►
Is allowed to edit►
AccessCont.
AccessCont.
Task Model
© sebisMaster’s Thesis final presentation, 1st August 2016 5
Workspace
1..*
◄ contains
Attribute
has ▼
*
Entity
AttributeDefinition
has ▼
*
EntityType
contains ►
is of type ►
is defined by ►
*
0..1*
0..1*
*has ▲
is defined by ►
0..1*
0..1
1..*
has ▲
Task*
0..1
1..*
TaskDefinition
1..*
Stage
has ▲
has ▼
has ▼
AccessCont.
Process
Sentry
MxLDefineable
MxLReferable
Function Model
© sebisMaster’s Thesis final presentation, 1st August 2016 6
«interface»
MxLDefineable
«interface»
MxLReferable
refers to ►
* *
Workspace
1..*
Attribute
has ▼
*
Entity
AttributeDefinition
has ▼
*
EntityTypeis of type ►
is defined by ►
*
0..1*
0..1*
Function
DerivedAttribute
Definition
*
*
MxLDefineable
MxLReferable
MxLReferable
MxLReferable
Integrated Model
© sebisMaster’s Thesis final presentation, 1st August 2016 7
Integrated Model
© sebisMaster’s Thesis final presentation, 1st August 2016 8
Behavioral Model
© sebisMaster’s Thesis final presentation, 1st August 2016 9
Example: Entity Type
Operation Precondition Consequence
Create Admin of Workspace Entity Type created
Read Reader of Workspace
(limited)
Admin of Workspace (full)
none
Update Admin of Workspace name: Entities get Type of new Name
enable free attributes: no new free
attributes, already existing attrs stay
Delete Admin of Workspace Entities of the Type loose their Type
and become a "Text page".
Their attributes are no longer visible.
Prototypical Implementation
© sebisMaster’s Thesis final presentation, 1st August 2016 10
Source: SocioCortex: A social information hub [7]
Prototypical Implementation
© sebisMaster’s Thesis final presentation, 1st August 2016 11
• Important components:
• Angular-material
• UI Component Framework
• Implementation of Googles Material Desing
• Sc-angular
• Access to the SocioCortex REST API
• MxL-angular
• MxL editor
• MxL UML class diagram generation
• Mock-ups by Sirma Gjorgievska
Live Demo
© sebisMaster’s Thesis final presentation, 1st August 2016 12
Evaluation
© sebisMaster’s Thesis final presentation, 1st August 2016 13
• Evaluation Group:
• 3 PhD Students of sebis
• 2 external partners (done)
• 1 external partner (tomorrow)
Introduction
• Think out loud and provide critical feedback
• Not helping immediately, testing system not participant
Scenario
• PhD Student at sebis
• Modelling around a Master‘s Thesis
Tasks
• Tasks concerning Attribute Definitions, Derived Attribute Definitions and Task Definitions
Questionnaire
• 10 SuS questions with a 5 point scale to answer
• 3 qualitative questions
Evaluation
© sebisMaster’s Thesis final presentation, 1st August 2016 14
Question Average SuS (0-4)
I think that I would like to use this system frequently. 2.6
I found the system unnecessarily complex. 3
I thought the system was easy to use. 2.6
I think that I would need the support of a technical person to be
able to use this system.
3
I found the various functions in this system were well integrated. 3
I thought there was too much inconsistency in this system. 2.8
I would imagine that most people would learn to use this system
very quickly.
2
I found the system very cumbersome to use. 2.8
I felt very confident using the system. 3.2
I needed to learn a lot of things before I could get going with this
system.
3.2
Average SuS score (0-100) (score > 68 considered good) 70
Evaluation
© sebisMaster’s Thesis final presentation, 1st August 2016 15
• Further findings
• Some minor design changes could easily improve the
usability as most testers complained about the same
problems
• Expanding cards too complicated
• Logical order of Type and Name of Attribute Definitions
should be changed, Name is more important
• Comparing to Tricia the separation of modeling and
generic client is considered a good step by the testers
• Introducing Tasks and MxL considered useful especially
for practical application
Further Integration Possibilities of MxL
© sebisMaster’s Thesis final presentation, 1st August 2016 16
• MxL for default access rights
• MxL used to define access rights to an entity based on its
attributes
• MxL used to define access rights to an attribute based on
other attributes or dependencies
Further Integration Possibilities of Roles
© sebisMaster’s Thesis final presentation, 1st August 2016 17
• User Roles for Tasks
• Only certain Users can see a Task
• Overview
• Only important things visible
• Only certain Users can complete a Task
• Review Process
• Approval Process
Technische Universität München
Department of Informatics
Chair of Software Engineering for
Business Information Systems
Boltzmannstraße 3
85748 Garching bei München
Tel +49.89.289.
Fax +49.89.289.17136
wwwmatthes.in.tum.de
Tobias Schrade
B.Sc.
Thank you for your attention.
Tel +49 170 8014403
[1] Hauder, Matheus; Kazman, Rick; Matthes, Florian(2015): Empowering End-
Users to Collaboratively Structure Processes for Knowledge Work.
[2] Matthes, Florian; Neubert, Christian; Steinhoff, Alexander (2011): Hybrid Wikis:
Empowering Users to collaboratively structure Information.
[3] Reschenhofer, Thomas; Bhat, Manoj; Hernandez-Mendez, Adrian; Matthes,
Florian (2016): Lessons Learned in Aligning Data and Model Evolution in
Collaborative Information Systems.
[4] Sauro, Jeff (2011): Measuring Usability With The System Usability Scale (SUS)
[5] Bangor, Aaron; Kortum, Philip; Miller, James (2009): Determining What
Individual SUS Scores Mean: Adding an Adjective Rating Scale.
[6] Google (2016): Angular Material. www.material.angularjs.org
[7] sebis (2016): SocioCortex: A social information hub.
http://sebischair.github.io/sociocortex_web/files/160209%20Michel%20SocioCortex
%20Eco-System.pdf
References
© sebisMaster’s Thesis kick-off presentation, 22nd February 2016 19