Requirements Sensemaking Using Concept Maps

Faily, Shamal; Lyle, John; Paul, André; Atzeni, Andrea; Blomme, Dieter; Desruelle, Heïko; Bangalore, Krishna

doi:10.1007/978-3-642-34347-6_13

Cited by 18 publications

(20 citation statements)

References 24 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Concept maps are used for different purposes however in another paper [30] concept maps are proposed for requirement validation also in which requirements are linked with source contents and rationales and both are represented by concept map. The assumption taken here is that analyst may find traces of requirements with its rationale and then validate the requirements.…”

Section: Research Question and Methodologymentioning

confidence: 99%

“…Many tools are proposed for creating such visualized models [31]. However creating such associations and traces is problem of pre-requirement specification traceability pre-RST which is problematic area yet [10,30]. This paper only guides about usage of visualization model for, and emphasized its importance for validation purpose.…”

Section: Research Question and Methodologymentioning

confidence: 99%

See 1 more Smart Citation

Unstructured source artifacts ontology for requirement validation in GDSD

Altaf¹,

Shah²,

Ali³

et al. 2018

IJET

View full text Add to dashboard Cite

Analyst while transformation, may not capture true representation of user opinion thus creating deviation from actual user needs. Role of stakeholder is primary in both requirement elicitation and validation process. In elicitation stage they are initiator whereas in validation stage they are authenticator of their needs. Invalid requirements if verified may not be a deviation from specified behavior but deviation from user needs. Requirement validation process ensure that requirements should be representing all primary and intermediary artifacts as well a shared opinions of their contributors. This highlights the importance of source artifacts without which requirement validation cannot assured. Researchers didn't propose any framework for requirement validation in context of GDSD in which source artifacts grows exponentially, and stakeholders are located in diversified locations. Due to unstructured nature of source artifacts, they are not electronically indexed and versioned controlled and this makes difficulty in preserving them. Requirement validation is not possible when source artifacts are not available along with their contributors. The major contribution of this paper to address problem of requirement validation in GDSD in absence of stakeholder to make it collocating environment. This paper introduced ontological solution of requirement validation in which target artifacts are validated against source artifact using their semantic relationship. This paper proposed an unstructured source artifact based ontological model for requirement validation in GDSD environment.

show abstract

Section: Research Question and Methodologymentioning

confidence: 99%

Section: Research Question and Methodologymentioning

confidence: 99%

Unstructured source artifacts ontology for requirement validation in GDSD

Altaf¹,

Shah²,

Ali³

et al. 2018

IJET

View full text Add to dashboard Cite

show abstract

“…The development team members carried out this activity during project meetings when all team members were present in the same location. The team members found the exercise so useful that, despite other commitments, they decided to hold a subsequent workshop three weeks later to consolidate the requirements concept maps for each area; the consolidated concept map is shown in Figure 4, and the process itself is described in more detail in [13].…”

Section: Sustaining Adoption Through Implementation Requires Creatmentioning

confidence: 99%

“…As the work described in [12], [13] shows in more detail, security and usability design problems often require creative solutions. This study has shown that integrating usability design practices into a project at an early stage, and sensitising team members to some of the techniques necessary to carry out this research, lays the groundwork for carrying out the research necessary for identifying the causes, rather than the symptoms, of design problems as and when they arise.…”

mentioning

confidence: 99%

Usability and Security by Design: A Case Study in Research and Development

Faily¹,

Lyle²,

Fléchais³

et al. 2015

Proceedings 2015 Workshop on Usable Security

Self Cite

View full text Add to dashboard Cite

Abstract-There is ongoing interest in utilising user experiences associated with security and privacy to better inform system design and development. However, there are few studies demonstrating how, together, security and usability design techniques can help in the design of secure systems; such studies provide practical examples and lessons learned that practitioners and researchers can use to inform best practice, and underpin future research. This paper describes a three-year study where security and usability techniques were used in a research and development project to develop webinos -a secure, crossplatform software environment for web applications. Because they value innovation over both security and usability, research and development projects are a particularly difficult context of study. We describe the difficulties faced in applying these security and usability techniques, the approaches taken to overcome them, and lessons that can be learned by others trying to build usability and security into software systems.

show abstract

“…6, the presentation of this application's navigation component can be optimized based on various parameters such as the device's operating system, input modalities screen size, screen orientation, etc. Taking these contextual characteristics into account is necessary in order to ensure the adaptive usability requirements of a multi-device ubiquitous application, but also, e.g., for meeting existing safety regulations regarding user distraction in-vehicle applications [16]. For such an in-vehicle infotainment (IVI) system, adaptation rules can be set to display the application's navigation bar fullscreen (see rule in Listing 1.2).…”

Section: Case Study: Adaptive Navigation Barmentioning

confidence: 99%

An Internet-Based Architecture Supporting Ubiquitous Application User Interfaces

Desruelle

Isenberg

Blomme

et al. 2013

The Future Internet

Self Cite

View full text Add to dashboard Cite

Abstract. Maintaining a viable balance between development costs and market coverage has turned out to be a challenging issue when developing mobile software applications. The diversity of devices running thirdparty developed software applications is rapidly expanding from PC, to mobile, home entertainment systems, and even the automotive industry. With the help of Web technology and the Internet infrastructure, ubiquitous applications have become a reality. Nevertheless, the variety of presentation and interaction modalities still limit the number of targetable devices. In this chapter we present webinos, a multi-device application platform founded on the Future Internet infrastructure. Hereto we describe webinos' model-based user interface framework as a means to support context-aware adaptiveness for applications that are executed in such ubiquitous computing environments.

show abstract

Requirements Sensemaking Using Concept Maps

Cited by 18 publications

References 24 publications

Unstructured source artifacts ontology for requirement validation in GDSD

Unstructured source artifacts ontology for requirement validation in GDSD

Usability and Security by Design: A Case Study in Research and Development

An Internet-Based Architecture Supporting Ubiquitous Application User Interfaces

Contact Info

Product

Resources

About