2011 26th IEEE/ACM International Conference on Automated Software Engineering (ASE 2011) 2011
DOI: 10.1109/ase.2011.6100126
|View full text |Cite
|
Sign up to set email alerts
|

Generating essential user interface prototypes to validate requirements

Abstract: Generating essential user interface prototypes to validate requirements.

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
4
1

Citation Types

0
9
0

Year Published

2012
2012
2022
2022

Publication Types

Select...
5
2

Relationship

2
5

Authors

Journals

citations
Cited by 23 publications
(9 citation statements)
references
References 15 publications
0
9
0
Order By: Relevance
“…4 shows an example of a user interface prototype (left side in Fig. 4) designed with Balsamiq Mockups [13], which is very similar to the final implementation (right side in Fig. 4).…”
Section: Addition 2: Sprint Designmentioning
confidence: 99%
“…4 shows an example of a user interface prototype (left side in Fig. 4) designed with Balsamiq Mockups [13], which is very similar to the final implementation (right side in Fig. 4).…”
Section: Addition 2: Sprint Designmentioning
confidence: 99%
“…Figure 1 illustrates our previous English language only approach [2,3,4,5]. In our new work, extraction of EUCs from text and consistency checking (steps 1-6) has been extended with essential interaction modelling "abstract interactions" in the Malay language.…”
Section: Introductionmentioning
confidence: 99%
“…These are used to model requirements in the Essential Use Cases (EUCs) methodology. Our work allows the RE to automatically and traceably transform EUC models (Malay or English) to EUI prototypes using a novel EUI pattern library we previously developed [4] (step 7), but which we have extended with new EUI patterns in the Malay language. An example of two Malay essential interactions and their associated abstract interaction and EUI pattern is shown in Table 1.…”
Section: Introductionmentioning
confidence: 99%
See 1 more Smart Citation
“…It is identified that the majority of requirements engineers lack of knowledge and skills on security elements and they always face difficulties to capture and understand the security terms [1] [2]. This situation usually results in the security requirements of a software system to be error-prone, inconsistency and incomplete, leading to unsecured software systems [3] [4].…”
Section: Introductionmentioning
confidence: 99%