An experimental comparison of reading techniques for defect detection in UML design documents

Laitenberger, Oliver; Atkinson, Colin; Schlich, Maud; Emam, Khaled El

doi:10.1016/s0164-1212(00)00052-2

Cited by 105 publications

(52 citation statements)

References 27 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…-to facilitate the digitising of requirements documents using speech recognition systems or NLP-based interrogation interfaces; -to reveal ambiguities and contradictions in documents describing user needs (see for example, [12,18,19]; -to design questionnaires or interviews, by verifying the ambiguity of the questions; -for automatic analysis of replies to open-ended questions, interpreting and classifying their contents [20]. b) to model requirements by extracting (directly from the text) the descriptions of the elements to include in the conceptual models envisaged by the development method adopted, in particular UML (Unified Modelling Language) 12 diagrams (see Figure 2).…”

Section: The Role Of Natural Language In Requirements Engineeringmentioning

confidence: 99%

“…18 Selection of the contact method The objectives of the research and the characteristics of the tool inherently required a contact method that would permit efficient use of time and resources while at the same time reach the largest number of potential respondents. On this point, to take into account the fact that there is a high level of saturation -due to the large number of such survey requests that the respondents receive -we had initially thought to send the questionnaire to some specialised newsgroups, 19 highlighting the academic nature of the research. In the first phase we identified three newsgroups whose work is related to the research topic (comp.object, comp.software-eng, alt.comp.software-tools); another twentyone newsgroups were later added to the list (the complete list is available at http://online.cs.unitn.it).…”

Section: Identification Of Interview Subjectsmentioning

confidence: 99%

See 1 more Smart Citation

Market research for requirements analysis using linguistic tools

Mich

MariangelaFranch

PierluigiInverardi

2004

Requirements Engineering

123

View full text Add to dashboard Cite

Numerous studies in recent months have proposed the use of linguistic instruments to support requirements analysis. There are two main reasons for this: (i) the progress made in natural language processing, (ii) the need to provide the developers of software systems with support in the early phases of requirements definition and conceptual modelling. This paper presents the results of an online market research intended (a) to assess the economic advantages of developing a CASE tool that integrates linguistic analysis techniques for documents written in natural language, and (b) to verify the existence of potential demand for such a tool. The research included a study of the language -ranging from completely natural to highly restricted -used in documents available for requirements analysis, an important factor given that on a technological level there is a trade-off between the language used and the performance of the linguistic instruments. To determine the potential demand for such tool, some of the survey questions dealt with the adoption of development methodologies and consequently with models and support tools; other questions referred to activities deemed critical by the companies involved. Through statistical correspondence analysis of the responses, we were able to outline two "profiles" of companies that correspond to two potential market niches which are characterised by their very different approach to software development.

show abstract

Section: The Role Of Natural Language In Requirements Engineeringmentioning

confidence: 99%

Section: Identification Of Interview Subjectsmentioning

confidence: 99%

Market research for requirements analysis using linguistic tools

Mich

MariangelaFranch

PierluigiInverardi

2004

Requirements Engineering

123

View full text Add to dashboard Cite

show abstract

“…In one study, the percentage of defects found ranged from 10% by the least effective inspector to 90% by the most effective inspector [3], and in another it ranged study from 20% to 70% [19]. Furthermore, a study measuring the effectiveness of inspection teams showed the least effective team finding 22% of the defects and the most effective team finding 50% of the defects [24].…”

Section: Individual Variation Among Inspectorsmentioning

confidence: 99%

Identifying implicit process variables to support future empirical work

Carver¹,

Basili²

2003

J. Braz. Comp. Soc.

View full text Add to dashboard Cite

“…Paper by Laitenberger et al from 2000 [23] -The paper includes one study with industry participants inspecting design documents. The study results in significant results in favour of perspective-based reading.…”

Section: Illustration Of Modelmentioning

confidence: 99%

An Evidence Profile for Software Engineering Research and Practice

Wohlin

2013

Perspectives on the Future of Software Engineering

View full text Add to dashboard Cite

Evidence-based software engineering has emerged as an important part of software engineering. The need for empirical evaluation and hence evidence has grown in the last couple of decades when developing new models, methods, techniques and tools in research. Furthermore, industrial decision-making ought to become more evidence-based. The objective here is to develop and present an evidence-based profile, which could be used to divide pieces of evidence into different types and hence creating an overall picture of evidence in a specific case. The evidence profile is developed in such a way that it allows evidence to be judged in context. The evidence profile consists of five types of evidence, and the profile is illustrated for perspective-based reading. It is shown how pieces of evidence can be classified into the different types. It is concluded that this type of approach may be useful to capture the evidence with respect to a specific topic and in a specific context. The further work includes applying the evidence profile for evidence collected from different type of studies and contexts.

show abstract

An experimental comparison of reading techniques for defect detection in UML design documents

Cited by 105 publications

References 27 publications

Market research for requirements analysis using linguistic tools

Market research for requirements analysis using linguistic tools

Identifying implicit process variables to support future empirical work

An Evidence Profile for Software Engineering Research and Practice

Contact Info

Product

Resources

About