2014
DOI: 10.1016/j.scico.2013.07.003
|View full text |Cite
|
Sign up to set email alerts
|

Evolutionary design of user interfaces for workflow information systems

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
2
1

Citation Types

0
5
0

Year Published

2016
2016
2022
2022

Publication Types

Select...
3
2
2

Relationship

0
7

Authors

Journals

citations
Cited by 10 publications
(5 citation statements)
references
References 29 publications
0
5
0
Order By: Relevance
“…Workflow information systems are used to understand content actions, which are an important key condition for effective customisation of ECM systems [2], [12], [14]. WIS are information systems, which are used to solve problems for an enterprise's BPM [15].…”
Section: Introductionmentioning
confidence: 99%
“…Workflow information systems are used to understand content actions, which are an important key condition for effective customisation of ECM systems [2], [12], [14]. WIS are information systems, which are used to solve problems for an enterprise's BPM [15].…”
Section: Introductionmentioning
confidence: 99%
“…Trying to address limitations of current notations to represent agent-based systems [23], hypermedia [24], security [25], workflow [26]. While adding variants to existing notations is useful, some people argue that by doing that, you might kill the original purpose of the notations and overload the cognitive load to understand it [27]. Even worse you are on the risk that the variant proposal to a notation might not be adopted by a community thus it might demand a lot of effort to keep updated, if we develop a software or create a plug-in of an existing software, of new graphical notation.…”
Section: State Of the Artmentioning
confidence: 99%
“…Even worse you are on the risk that the variant proposal to a notation might not be adopted by a community thus it might demand a lot of effort to keep updated, if we develop a software or create a plug-in of an existing software, of new graphical notation. Using the right notation for the right model [27], also represents a challenge when the notation does not exist at all, for instance, how to design an auditory user interface? Or when the notation lacks of expressiveness, for instance, in UML labeling method and class names with Italics to denote abstract Classes is not easy identified, sometimes, not even supported in existing solutions.…”
Section: State Of the Artmentioning
confidence: 99%
“…The evolutionary prototyping model involves: (a) the system requirement collection and analysis, (b) rapid designing, (c) developing the working prototypes, (d) initial customer evaluation, (e) improving the prototypes, (f) implementing the final products, and (g) maintaining the products (Carter et al, 2001;Guerrero-García, 2014;Bai, 2014). The evolutionary prototyping approach improves the flexibility of the system prototypes, helps to save time and effort during software development, allows developers to concentrate on the main functionalities of the system that they understand, and increase user requirement satisfaction since customers are involved throughout the development process (Chen & Huang, 2002;Xiaoshuan et al, 2009;Guerrero-García, 2014;Adarsh et al, 2017). The researchers adopted it because some of the system requirements were unclear and required customer feedback, and it reduces severe and critical flaws during the system testing (Carter et al, 2001).…”
Section: The Transaction Phasementioning
confidence: 99%