Market research for requirements analysis using linguistic tools

Mich, Luisa; MariangelaFranch,; PierluigiInverardi,

doi:10.1007/s00766-003-0179-8

Cited by 123 publications

(37 citation statements)

References 14 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…In typical software development practice, majority of the requirement documents created in the early phase of a project, are written in natural language [10]. Such a specification is therefore inherently imprecise, ambiguous, and a potential source of contradictions.…”

Section: Introductionmentioning

confidence: 99%

Verifying Temporal Properties of Use-Cases in Natural Language

Šimko

Hauzar

Bureš

et al. 2012

Formal Aspects of Component Software

View full text Add to dashboard Cite

Abstract. This paper presents a semi-automated method that helps iteratively write use-cases in natural language and verify consistency of behavior encoded within them. In particular, this is beneficial when the use-cases are created simultaneously by multiple developers. The proposed method allows verifying the consistency of textual use-case specification by employing annotations in usecase steps that are transformed into temporal logic formulae and verified within a formal behavior model. A supporting tool for plain English use-case analysis is currently being enhanced by integrating the verification algorithm proposed in the paper.

show abstract

Section: Introductionmentioning

confidence: 99%

Verifying Temporal Properties of Use-Cases in Natural Language

Šimko

Hauzar

Bureš

et al. 2012

Formal Aspects of Component Software

View full text Add to dashboard Cite

show abstract

“…Studies of requirements engineering (RE) practice show that the majority of requirements are written in natural language [62]. However, the textual artifacts can be cumbersome to comprehend and analyze.…”

Section: Requirements Engineering Visualizationmentioning

confidence: 99%

Visual analytics for software requirements engineering

Reddivari

2013

2013 21st IEEE International Requirements Engineering Conference (RE)

View full text Add to dashboard Cite

For many software projects, keeping requirements on track needs an effective and efficient path from data to decision. Visual analytics creates such a path that enables the human to extract insights by interacting with the relevant information. While various requirements visualization techniques exist, few have produced end-to-end values to practitioners. In this dissertation, we advance the literature on visual requirements analytics by characterizing its key components and relationships in a framework. We follow the goal-question-metric paradigm to define the framework by teasing out five conceptual goals (user, data, model, visualization, and knowledge), their specific operationalizations, and their interconnections. The framework allows us to not only assess existing approaches, but also create tool enhancements in a principled manner.We evaluate our enhanced tool supports both qualitatively and quantitatively. First, we evaluate our tool supports qualitatively through a case study where massive, heterogeneous, and dynamic requirements are processed, visualized, and analyzed. Working together with practitioners on a contemporary software project within its real-life context leads to the main ending that visual analytics can help tackle both open-ended visual exploration tasks and well-structured visual exploitation tasks in requirements engineering. In addition, the study helps the practitioners to reach actionable decisions in a wide range of areas relating to their project, ranging from theme and outlier identification, over requirements tracing, to risk assessment. Overall our work illuminates how the data-to-decision analytical capabilities could be improved by the increased interactivity of requirements visualization.Although many new visual analytics tools, techniques and methods are being developed, still there is a lack of understanding of how to evaluate the performance of such tools. We conducted an experiment to assess the performance (time and correctness) of our visual analytics tool support in solving requirements engineering tasks. Our study provides initial evidence and insights for visual analytics in requirements engineering and sheds light on many challenging open questions.

show abstract

“…In addition, it provides an easier means of linking requirements specification to other artifacts like test artifacts [97]. Hence, it is of no surprise that such UML based modelling for requirements has been found to be the most widely used based on a survey conducted by [72] and is recommended by several software development approaches like Unified Software Development Process for requirements specification [59]. Yet, generating scenarios for testing from the use case based requirements specification is still labour intensive with lack of adequate tool support [98].…”

Section: Comparative Analysis Based On Scientific Literaturementioning

confidence: 99%

“…This is due to its ease of adoption and lack of need of any special skills which implies low cost of implementation [73]. Attempts have been made to address and enhance completeness and unambiguity of natural language textual requirements by providing guidelines and metrics for measuring and improving completeness [71] [73] and by extending adequate tool support [72]. Yet, such natural language textual requirements, irrespective of the level of abstraction of the system or software they define, have been found in ample of cases to still be prone to misinterpretation, ambiguity, inconsistencies and inaccuracy [74] [96].…”

Section: Comparative Analysis Based On Scientific Literaturementioning

confidence: 99%

“…Such informal methods have been found to contribute to 79% of specifications in software engineering [72] and also most commonly used in systems engineering [73]. The semi-formal methods are based on using either structured natural language through forms and templates [72] or use-case based requirements engineering [59]. Lastly, the formal methods are based on using formalized language in the form of mathematical notations and formal logic [74].…”

Section: Requirements Specificationmentioning

confidence: 99%

See 1 more Smart Citation

An Effective Verification Strategy for Testing Distributed Automotive Embedded Software Functions: A Case Study

Chunduri

Feldt

Adenmark

2016

Product-Focused Software Process Improvement

View full text Add to dashboard Cite

Context. The share and importance of software within automotive vehicles is growing steadily. Most functionalities in modern vehicles, especially safety related functions like advanced emergency braking, are controlled by software. A complex and common phenomenon in today's automotive vehicles is the distribution of such software functions across several Electronic Control Units (ECUs) and consequently across several ECU system software modules. As a result, integration testing of these distributed software functions has been found to be a challenge. The automotive industry neither has infinite resources, nor has the time to carry out exhaustive testing of these functions. On the other hand, the traditional approach of implementing an ad-hoc selection of test scenarios based on the tester's experience, can lead to test gaps and test redundancies. Hence, there is a pressing need within the automotive industry for a feasible and effective verification strategy for testing distributed software functions. Objectives. Firstly, to identify the current approach used to test the distributed automotive embedded software functions in literature and in a case company. Secondly, propose and validate a feasible and effective verification strategy for testing the distributed software functions that would help improve test coverage while reducing test redundancies and test gaps. Methods. To accomplish the objectives, a case study was conducted at Scania CV AB, Södertälje, Sweden. One of the data collection methods was through conducting interviews of different employees involved in the software testing activities. Based on the research objectives, an interview questionnaire with open-ended and close-ended questions has been used. Apart from interviews, data from relevant artifacts in databases and archived documents has been used to achieve data triangulation. Moreover, to further strengthen the validity of the results obtained, adequate literature support has been presented throughout. Towards the end, a verification strategy has been proposed and validated using existing historical data at Scania. Conclusions. The proposed verification strategy to test distributed automotive embedded software functions has given promising results by providing means to identify test gaps and test redundancies. It helps establish an effective and feasible approach to capture function test coverage information that helps enhance the effectiveness of integration testing of the distributed software functions.

show abstract

Market research for requirements analysis using linguistic tools

Cited by 123 publications

References 14 publications

Verifying Temporal Properties of Use-Cases in Natural Language

Verifying Temporal Properties of Use-Cases in Natural Language

Visual analytics for software requirements engineering

An Effective Verification Strategy for Testing Distributed Automotive Embedded Software Functions: A Case Study

Contact Info

Product

Resources

About