Towards Development of Complete and Conflict-Free Requirements

Moitra, Abha; Siu, Kit; Crapo, Andrew; Chamarthi, Harsh Raju; Durling, Michael; Li, Meng; Yu, Han; Manolios, Panagiotis; Meiners, Michael A.

doi:10.1109/re.2018.00036

Cited by 23 publications

(20 citation statements)

References 13 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…To find missing and conflicting requirements, Moitra et al [17] described a tool ASSERT™ which was developed by General Electric Company. This tool requires the analysts to define the entities and variables involved in the requirements description using Semantic Application Design Language (SADL) and then automatically validate them using the ACL2 formalism.…”

Section: Related Workmentioning

confidence: 99%

Automated Conditional Statements Checking for Complete Natural Language Requirements Specification

et al. 2021

View full text Add to dashboard Cite

Defects such as the duality and the incompleteness in natural language software requirements specification have a significant impact on the success of software projects. By now, many approaches have been proposed to assist requirements analysts to identify these defects. Different from these approaches, this paper focuses on the requirements incompleteness implied by the conditional statements, and proposes a sentence embedding- and antonym-based approach for detecting the requirements incompleteness. The basic idea is that when one condition is stated, its opposite condition should also be there. Otherwise, the requirements specification is incomplete. Based on the state-of-the-art machine learning and natural language processing techniques, the proposed approach first extracts the conditional sentences from the requirements specification, and elicits the conditional statements which contain one or more conditional expressions. Then, the conditional statements are clustered using the sentence embedding technique. The conditional statements in each cluster are further analyzed to detect the potential incompleteness by using negative particles and antonyms. A benchmark dataset from an aerospace requirements specification has been used to validate the proposed approach. The experimental results have shown that the recall of the proposed approach reaches 68.75%, and the F1-measure (F1) 52.38%.

show abstract

Section: Related Workmentioning

confidence: 99%

Automated Conditional Statements Checking for Complete Natural Language Requirements Specification

et al. 2021

View full text Add to dashboard Cite

show abstract

“…Since especially novice users are not familiar with communicating requirements, which may be rooted in an incomplete understanding of their own needs, the task of uncovering the cause of a need or requirement falls to the interviewer. Otherwise, interviews lead to ambiguous user statements at the wrong level of abstraction [13]. Without uncovering the cause of, or foundation for user needs, the development of disruptive solutions stagnates.…”

Section: A Common Issues In User Elicitation Interviewsmentioning

confidence: 99%

“…However, these tools do not suffice in providing a solution to both challenges introduced: Annotation-based tools primarily enable RE for iteratively improving existing systems; NL tools commonly require a requirements engineer to facilitate the process, hence retaining a bottleneck for wide audience integration [11]; additionally, existing research rarely considers (methodological) guidance for novice end-users. Tools such as FAME [12] and ASSERT [13] cater to novices, but only on the side of a novice analyst, not novice users, hence not enabling self-elicitation. A literature gap remains in extending RE techniques to wide audiences.…”

Section: Introductionmentioning

confidence: 99%

LadderBot: A Requirements Self-Elicitation System

Rietz

Maedche

2019

2019 IEEE 27th International Requirements Engineering Conference (RE)

View full text Add to dashboard Cite

Context] Digital transformation impacts an ever-increasing amount of everyone's business and private life. It is imperative to incorporate user requirements in the development process to design successful information systems (IS). Hence, requirements elicitation (RE) is increasingly performed by users that are novices at contributing requirements to IS development projects.[Objective] We need to develop RE systems that are capable of assisting a wide audience of users in communicating their needs and requirements. Prominent methods, such as elicitation interviews, are challenging to apply in such a context, as time and location constraints limit potential audiences. [Research Method] We present the prototypical self-elicitation system "LadderBot". A conversational agent (CA) enables end-users to articulate needs and requirements on the grounds of the laddering method. The CA mimics a human (expert) interviewer's capability to rephrase questions and provide assistance in the process. An experimental study is proposed to evaluate LadderBot against an established questionnaire-based laddering approach. [Contribution] This work-in-progress introduces the chatbot LadderBot as a tool to guide novice users during requirements self-elicitation using the laddering technique. Furthermore, we present the design of an experimental study and outline the next steps and a vision for the future.

show abstract

“…In our perception, the interest, acceptance, use, and need for formal methods (in the sense of Bjørner & Havelund) in the software industry has rapidly changed in recent years. 1 In the last 10 years, the big internet companies have all established departments that focus on formal analysis of software systems, companies from the aerospace [11] and automotive [12] domain formalise and analyse requirements, and even small companies benefited from formal design models complementing their development process [13]. To best prepare our students of today for their future career in industry or academia, we feel the need to provide our students with a basic and solid understanding of the concept of formal methods, their use, and an overview over advantages and disadvantages.…”

Section: Introductionmentioning

confidence: 99%

On Complementing an Undergraduate Software Engineering Course with Formal Methods

Westphal

2020

2020 IEEE 32nd Conference on Software Engineering Education and Training (CSEE&T)

View full text Add to dashboard Cite

Software systems continue to pervade day-today life and so it becomes increasingly important to ensure the dependability, safety, and security of software. One approach to this end can be summarised under the broad term of formal methods, i.e., the formal analysis of requirements, software models, or programs. Formal methods in this sense are today used in many branches of the software industry, such as the huge internet companies, aerospace, automotive, etc. and even made their way into small to medium sized enterprises. In this article, we argue the opinion that today's students (and tomorrow's engineers) need to be provided with a basic understanding of formal methods in the broad sense (what is it, how does it feel to use it, what are advantages and limitations) already in undergraduate introductions to software engineering. We propose a generic course design that complements (otherwise completely ordinary) undergraduate introductions to software engineering with formal semantics and analyses of (visual) software description languages. We report on five years of teaching an implementation of the course design that indicate the feasibility of teaching without sacrificing classical software engineering topics and without over-straining students wrt. level or workload.

show abstract

Towards Development of Complete and Conflict-Free Requirements

Cited by 23 publications

References 13 publications

Automated Conditional Statements Checking for Complete Natural Language Requirements Specification

Automated Conditional Statements Checking for Complete Natural Language Requirements Specification

LadderBot: A Requirements Self-Elicitation System

On Complementing an Undergraduate Software Engineering Course with Formal Methods

Contact Info

Product

Resources

About