Using EUREQA for End-User UML Model Development through Design Patterns

Abstract

<p lang="en-US"><span style="color: #000000;"><span style="font-family: 'Times New Roman', serif;"><span style="font-size: x-small;"><span style="font-size: x-small;">This work presents </span><span style="color: #000000;"><span style="font-size: x-small;"><span lang="nb-NO">the EUREQA approach </span></span></span><span style="color: #000000;"><span style="font-size: x-small;">for end-user development. </span></span><span style="color: #000000;"><span style="font-size: x-small;"><span lang="nb-NO">The purpose of the tool is to narrow the cognitive gap between the end-user developer's mental model and the software model. The tool uses design patterns as building blocks allowing end-users to create UML class diagram models that capture their domain knowledge. The EUREQA tool hides from view the complexity of code thereby reducing the cognitive load on end-user developers. EUREQA makes non-functional quality issues a first-class concern allowing end-user developers to consider both functional and non-functional aspects of design alternatives. The tool uses visualization techniques to aid in non-functional quality assesment. The purpose of this paper is to evaluate and assess the opportunities and challenges of EUREQA. A qualitative, </span></span></span><span style="font-size: x-small;"><span lang="en-US">pilot </span></span><span style="font-size: x-small;">evaluation of EUREQA </span><span style="font-size: x-small;"><span lang="nb-NO">shows that the </span></span><span style="font-size: x-small;">visualization techniques work well, whereas there are issues with the abstraction gap between the visualization and class diagram.</span></span></span></span></p

A Comparative Study of the EUREQA Tool for End-User Development

“…The coding schema captures the main concepts of the EUREQA user experiences and was used as a basis for the current coding scheme. It was a refinement of a coding schema utilized in earlier evaluations (Austrem, 2011b). An open coding was done to reveal categories relating to the Visio environment.…”

“…We have identified the following main confounding variables that may affect our study, distribution of skill between participant groups, technical issues with tool(s), category validity. We ensured an equal distribution of skills between the two groups and performed prototype evaluations of EUREQA to ensure technical validity (Austrem, 2011b). The categories used in the analysis were based on two earlier evaluations ensuring validity.…”

Finite Element Analysis Based Design of Mobile Robot for Removing Plug Oil Well

“…4(a). The supporting leg could be simplified to the two-force bar [12][13][14]. The force on the pin A that is contacted with the pipe wall is analyzed in Fig.…”