Name
Affiliation
Papers
DANIEL M. BERRY
General Electric Research and Development, Schenectady, New York
103
Collaborators
Citations 
PageRank 
104
1091
148.76
Referers 
Referees 
References 
1878
1134
837
Search Limit
1001000
Title
Citations
PageRank
Year
How To Benefit From Newbies' Domain Ignorance In Software Development Projects10.342021
Empirical Evaluation Of Tools For Hairy Requirements Engineering Tasks10.352021
The Prevalence and Severity of Persistent Ambiguity in Software Requirements Specifications: Is a Special Effort Needed to Find Them?20.362020
Requirements for Monitoring Inattention of the Responsible Human in an Autonomous Vehicle - The Recall and Precision Tradeoff.00.342020
The inconsistency between theory and practice in managing inconsistency in requirements engineering00.342019
Two Experiments Comparing Two Four-Step EPMcreate-Based Creativity Techniques for Requirements Elicitation.00.342019
The Requirements Engineering Reference Model: A Fundamental Impediment to Using Formal Methods in Software Systems Development00.342019
Preface: Eighth International Workshop on Creativity in Requirements Engineering (CreaRE 2019).00.342019
A case study of using grounded analysis as a requirement engineering method: Identifying personas that specify privacy and security tool users.00.342018
Creativity Techniques for Requirements Elicitation: Comparing Four-Step EPMcreate-Based Processes00.342018
Improving the identification of hedonic quality in user requirements: a second controlled experiment.00.342018
Keynote: Evaluation of NLP Tools for Hairy RE Tasks.00.342018
An Empirical Study of the Software Development Process, Including Its Requirements Engineering, at Very Large Organization: How to Use Data Mining in Such a Study.00.342017
Evaluation of Tools for Hairy Requirements and Software Engineering Tasks40.432017
Group versus individual use of power-only EPMcreate as a creativity enhancement technique for requirements elicitation.20.412017
The impact of domain knowledge on the effectiveness of requirements engineering activities.50.402017
Downsizing EPMcreate to Lighter Creativity Techniques for Requirements Elicitation.00.342017
Privacy Personas: Clustering Users via Attitudes and Behaviors toward Security Practices.80.492016
Reasoning about Inconsistency in RE - Separating the Wheat from the Chaff.00.342016
The Problem of the Lack of Benefit of a Document to Its Producer (PotLoBoaDtiP)00.342016
Reuse of requirements reduced time to market at one industrial shop: a case study150.982015
The essential similarity and differences between mathematical modeling and programming00.342013
Requirement ambiguity not as important as expected: results of an empirical evaluation40.482013
An industrial case study of the impact of domain ignorance on the effectiveness of requirements idea generation during requirements elicitation110.652013
The design of SREE: a prototype potential ambiguity finder for requirements specifications and lessons learned270.952013
Quantifying the impact of requirements definition and management process maturity on project outcome in large business application development60.482013
The impact of domain knowledge on the effectiveness of requirements idea generation during requirements elicitation40.462012
The effectiveness of an optimized EPMcreate as a creativity enhancement technique for Web site requirements elicitation120.682012
Introduction to the REFSQ 2011 special issue10.352012
Liability issues in software engineering: technical perspective10.362011
Software requirements and design: the work of Michael Jackson by Bashar Nuseibeh and Pamela Zave10.402011
Keynote requirements for maintaining web access for hearing-impaired individuals: A ten-year perspective.00.342011
Ethics Test Results Before and After Ethics Training: A Disturbing Experience10.352010
Requirements Determination is Unstoppable: An Experience Report90.662010
Planned programming problem gotchas as lessons in requirements engineering.10.342010
Requirements for Tools for Ambiguity Identification and Measurement in Natural Language Requirements Specifications421.952008
Can Rules of Inferences Resolve Coordination Ambiguity in Natural Language Requirements Specification?10.382008
Extended Disambiguation Rules for Requirements Specifications30.452007
Distributed priority ranking of strategic preliminary requirements for management information systems in economic organizations70.582007
Unified use case statecharts: case studies70.492007
Ambiguity in Natural Language Requirements Documents120.752007
Requirements Engineering Lessons from House Building00.342007
Reducing Ambiguities in Requirements Specifications Via Automatically Created Object-Oriented Models331.422007
Aybüke Aurum and Claes Wohlin (eds): Engineering and managing software requirements00.342006
Increasing quality of conceptual models: is object-oriented analysis that simple?60.542006
É possível substituir processos de Engenharia de Requisitos por Contagem de Pontos de Função?00.342005
Social Construction Of Information Technology Supporting Work40.742005
Concept Identification in Object-Oriented Domain Analysis: Why Some Students Just Don"t Get It161.072005
Requirements engineering for organizational transformation190.982005
To do or not to do: If the requirements engineering payoff is so good, why aren"t more companies doing it?90.602005
  • 1
  • 2