An MDA Approach for Generating Web Interfaces with UML ConcurTaskTrees and Canonical Abstract Prototypes

Costa, Duarte; Nóbrega, Leonel; Nunes, Nuno

doi:10.1007/978-3-540-70816-2_11

Cited by 8 publications

(8 citation statements)

References 3 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…The Software Architecture is elaborated by means of composing one Aggregation Spaces [14] per each User Task (UT), which architecturally uses the ISs which are associated to the UT, ensuring the application of BRs over identified DEs and ensuring traceability between business and software implementation.…”

Section: Goalsmentioning

confidence: 99%

Bridging Enterprise and Software Engineering Through an User-Centered Design Perspective

Valente

Silva²,

Winckler³

et al. 2016

Web Information Systems Engineering – WISE 2016

View full text Add to dashboard Cite

OATAO is an open access repository that collects the work of Toulouse researchers and makes it freely available over the web where possible. Abstract. The development of Web-based Information Systems is crucial in the quest to maintain and develop the enterprise competiveness. However, capturing requirements from Business Processes (BP) is still an issue, as existing methods mostly focus, or on human aspects and the user interface, or on business concerns as rules and workflow coordination, and therefore do not specify all the Software Architectural components which are relevant for software development. We present the Goals Approach, which analyzes BPs and User Tasks and details them in the process of methodically designing and structuring the User Interface, the Business Logic and the Database of the Information System given a Model-View-Controller (MVC) architectural pattern. In this paper we focus on how to obtain the Goals business model of requirements based on the DEMO method. The approach can be used for in-house software development, and the method is straightforward fitting Small and Medium Enterprises agility needs.

show abstract

Section: Goalsmentioning

confidence: 99%

Bridging Enterprise and Software Engineering Through an User-Centered Design Perspective

Valente

Silva²,

Winckler³

et al. 2016

Web Information Systems Engineering – WISE 2016

View full text Add to dashboard Cite

show abstract

“…Functional usability features (FUFs) are being integrated into models used in Software Engineering, such as the UML (Unified Modeling Language) use case, sequence, and class diagrams [5] [6]. However, those models do not detail the usersystem interaction in terms of user actions, system responses, data validation, and alternative interaction paths [7] [8]. Consequently, even if the usability mechanisms are implemented, the interaction design may not be adequate to support their use of by the application users, causing difficulties at interaction time.…”

Section: Introductionmentioning

confidence: 99%

Defining a notation for usability-oriented interaction and navigation modeling for interactive systems

Marques

Barbosa

Conte

2017

JIS

View full text Add to dashboard Cite

Modeling the interaction and navigation of an interactive system can assist designers in making decisions about how the users will be able to achieve their interaction goals. However, there is a lack of proposals to: (1) deal with interaction and navigation in an integrated way and (2) deal with usability features in interaction and navigation modeling. In this paper, we propose a usability-oriented interaction and navigation model to improve the quality in use of interactive systems. We evaluate the feasibility of the model through a study with three participants with experience in using models in industry, teaching models and carrying out academic research about models. Our main contributions are: (1) a knowledge base about the existing solutions for the problem, (2) the USINN (Usability-oriented Interaction and Navigation) model, (3) a preliminary evaluation about the feasibility of USINN, (4) the evolution of the USINN notation based on the results of the feasibility study, and (5) the definition of the USINN metamodel.

show abstract

“…This can be a UI specification that abstracts from the peculiarities of a real UI, but specifies already the kind of UI (e.g., a graphical UI), and possibly also the kinds of widgets. A higher abstraction can be achieved with so-called task models, e.g., see (Costa et al, 2007;van den Bergh and Coninx, 2007;Pastor et al, 2008;Mori et al, 2002;Paternò et al, 2009;Vanderdonckt, 2008). A more recent approach employs discourse-based models, e.g., see (Falb et al, 2006;Falb et al, 2009).…”

Section: Introductionmentioning

confidence: 99%

Automated Generation of User Interfaces - Based on Use Case or Interaction Design Specifications?

Kaindl¹,

Popp²,

Raneburger³

2012

Proceedings of the 7th International Conference on Software Paradigm Trends

View full text Add to dashboard Cite

Instead of manually creating (graphical) user interfaces (UIs), automatically generating them is desirable, especially since UIs are needed today for diverse devices like PCs and smartphones. The basis for such automated generation can be a UI specification, but most of the related research takes task models as input, which are on a higher level of abstraction. More recently, another modeling language employing discourse-based models for specifying communicative interaction has been proposed, which completely abstracts from specifics of a particular UI and even its type. From such models, UIs can be generated automatically through model transformations. Some research, however, claims that UIs can be generated from use cases. While it would be desirable to utilize such a form of requirements definition without having to create another specification, we found that these approaches actually use additional information attached to the use cases, usually UI-related attachments. In addition to contrasting different kinds of specifications, we propose a synthesis through a combination. In fact, we found that discourse-based models can be also viewed as specifying classes of scenarios, i.e., use cases more precisely than the mainstream approach using UML and use-case reports.

show abstract

An MDA Approach for Generating Web Interfaces with UML ConcurTaskTrees and Canonical Abstract Prototypes

Cited by 8 publications

References 3 publications

Bridging Enterprise and Software Engineering Through an User-Centered Design Perspective

Bridging Enterprise and Software Engineering Through an User-Centered Design Perspective

Defining a notation for usability-oriented interaction and navigation modeling for interactive systems

Automated Generation of User Interfaces - Based on Use Case or Interaction Design Specifications?

Contact Info

Product

Resources

About