BibSLEIGH — Daniel_M

Travelled to:

1 × Australia
1 × Brazil
1 × France
5 × Germany
6 × USA

Collaborated with:

A.Niknafs M.H.(.Penedo S.F.Tjong J.So A.Ravid L.Goldin ∅ J.M.Wing V.Sakhnini L.Mich D.Svetinovic M.W.Godfrey G.Estrin R.Gacitua P.Sawyer K.Czarnecki M.Antkiewicz M.AbdelRazik E.J.Philippo W.Heijstek B.Kruiswijk M.R.V.Chaudron H.D.Covvey D.Zitner D.D.Cowan M.A.Shepherd D.Damian A.Finkelstein D.C.Gause R.Hall A.Wassyng

Talks about:

requir (13) prototyp (4) elicit (4) generat (3) specif (3) finder (3) effect (3) domain (3) design (3) engin (3)

Person: Daniel M. Berry

DBLP: Berry:Daniel_M=

Facilitated 1 volumes:

Contributed to:

2013

2012

2010

2006

2005

2003

1999

1994

1981

1979

1971

1985

Wrote 17 papers:

RE-2013-NiknafsB #case study #effectiveness #elicitation #generative #idea #industrial #requirements: An industrial case study of the impact of domain ignorance on the effectiveness of requirements idea generation during requirements elicitation (AN, DMB), pp. 279–283.
REFSQ-2013-PhilippoHKCB #ambiguity #empirical #evaluation: Requirement Ambiguity Not as Important as Expected — Results of an Empirical Evaluation (EJP, WH, BK, MRVC, DMB), pp. 65–79.
REFSQ-2013-TjongB #ambiguity #design #lessons learnt #prototype #requirements #specification: The Design of SREE — A Prototype Potential Ambiguity Finder for Requirements Specifications and Lessons Learned (SFT, DMB), pp. 80–95.
RE-2012-NiknafsB #effectiveness #elicitation #generative #idea #requirements: The impact of domain knowledge on the effectiveness of requirements idea generation during requirements elicitation (AN, DMB), pp. 181–190.
REFSQ-2012-BerryGST #requirements #tool support: The Case for Dumb Requirements Engineering Tools (DMB, RG, PS, SFT), pp. 211–217.
RE-2010-BerryCAA #case study #experience #requirements: Requirements Determination is Unstoppable: An Experience Report (DMB, KC, MA, MA), pp. 311–316.
REFSQ-2010-SakhniniBM #effectiveness #elicitation #requirements #validation: Validation of the Effectiveness of an Optimized EPMcreate as an Aid for Creative Requirements Elicitation (VS, DMB, LM), pp. 91–105.
RE-2006-SoB #case study #experience #requirements: Experiences of Requirements Engineering for Two Consecutive Versions of a Product at VLSC (JS, DMB), pp. 216–221.
RE-2005-BerryDFGHW #question #requirements #why: To do or not to do: If the requirements engineering payoff is so good, why aren’t more companies doing it? (DMB, DD, AF, DCG, RH, AW), p. 447.
RE-2005-SvetinovicBG #analysis #concept #identification #object-oriented #student #why: Concept Identification in Object-Oriented Domain Analysis: Why Some Students Just Don’t Get It (DS, DMB, MWG), pp. 189–198.
RE-2003-CovveyZBCS #health #quality #specification: Formal Structure for Specifying the Content and Quality of the Electronic Health Record (HDC, DZ, DMB, DDC, MAS), pp. 162–168.
HCI-EI-1999-RavidB #prototype #requirements #user interface: A Method for Extracting Requirements that a User Interface Prototype Contains (AR, DMB), pp. 900–904.
ICRE-1994-GoldinB #abstraction #design #elicitation #evaluation #natural language #prototype #requirements: AbstFinder, a prototype abstraction finder for natural language text for use in requirements elicitation: design, methodology, and evaluation (LG, DMB), pp. 84–93.
ICSE-1981-PenedoBE #algorithm #concurrent #generative: An Algorithm to Support Code-Skeleton Generation for Concurrent Systems (MH(P, DMB, GE), pp. 125–135.
ICSE-1979-BerryP #design #specification #using: The Use of a Module Interconnection Specification Capability in the SARA System Design Methodology (DMB, MH(P), pp. 294–307.
STOC-1971-Berry #question: Block Structure: Retention or Deletion? (DMB), pp. 86–100.
CSE-1985-BerryW #prototype #specification #why: Specification and Prototyping: Some Thoughts on Why They Are Successful (DMB, JMW), pp. 117–128.