 | 2008 |
|---|
| 76 |       | Daniel M. Berry:
The Software Engineering Silver Bullet Conundrum.
IEEE Software 25(2): 18-19 (2008) |
| 75 | | Nadzeya Kiyavitskaya,
Nicola Zeni,
Luisa Mich,
Daniel M. Berry:
Requirements for tools for ambiguity identification and measurement in natural language requirements specifications.
Requir. Eng. 13(3): 207-239 (2008) |
| 2007 |
|---|
| 74 | | Daniel M. Berry:
Ambiguity in Natural Language Requirements Documents.
Monterey Workshop 2007: 1-7 |
| 73 | | Daniel Popescu,
Spencer Rugaber,
Nenad Medvidovic,
Daniel M. Berry:
Reducing Ambiguities in Requirements Specifications Via Automatically Created Object-Oriented Models.
Monterey Workshop 2007: 103-124 |
| 72 | | Daniel M. Berry:
Requirements Engineering Lessons from House Building.
WER 2007: 1 |
| 71 | | Nadzeya Kiyavitskaya,
Nicola Zeni,
Luisa Mich,
Daniel M. Berry:
Requirements for Tools for Ambiguity Identification and Measurement in Natural Language Requirements Specifications.
WER 2007: 197-206 |
| 70 | | Sri Fatimah Tjong,
Michael Hartley,
Daniel M. Berry:
Extended Disambiguation Rules for Requirements Specifications.
WER 2007: 97-106 |
| 69 | | Andrzej Sobczak,
Daniel M. Berry:
Distributed priority ranking of strategic preliminary requirements for management information systems in economic organizations.
Information & Software Technology 49(9-10): 960-984 (2007) |
| 68 | | Davor Svetinovic,
Daniel M. Berry,
Nancy A. Day,
Michael W. Godfrey:
Unified use case statecharts: case studies.
Requir. Eng. 12(4): 245-264 (2007) |
| 2006 |
|---|
| 67 | | Joel So,
Daniel M. Berry:
Experiences of Requirements Engineering for Two Consecutive Versions of a Product at VLSC.
RE 2006: 216-221 |
| 66 | | Daniel M. Berry:
Aybüke Aurum and Claes Wohlin (eds): Engineering and managing software requirements.
Requir. Eng. 11(2): 152-154 (2006) |
| 2005 |
|---|
| 65 | | Davor Svetinovic,
Daniel M. Berry,
Michael W. Godfrey:
Concept Identification in Object-Oriented Domain Analysis: Why Some Students Just Don't Get It.
RE 2005: 189-198 |
| 64 | | Daniel M. Berry,
Daniela Damian,
Anthony Finkelstein,
Donald C. Gause,
Robert Hall,
Alan Wassyng:
To do or not to do: If the requirements engineering payoff is so good, why aren't more companies doing it?
RE 2005: 447 |
| 63 | | Claudia Hazan,
Daniel M. Berry,
Julio Cesar Sampaio do Prado Leite:
É possível substituir processos de Engenharia de Requisitos por Contagem de Pontos de Função?.
WER 2005: 197-208 |
| 62 | | Daniel M. Berry,
Erik Kamsties:
The Syntactically Dangerous All and Plural in Specifications.
IEEE Software 22(1): 55-57 (2005) |
| 61 | | Isabel Ramos,
Daniel M. Berry,
João Alvaro Carvalho:
Requirements engineering for organizational transformation.
Information & Software Technology 47(7): 479-495 (2005) |
| 60 | | Karin Koogan Breitman,
Julio Cesar Sampaio do Prado Leite,
Daniel M. Berry:
Supporting scenario evolution.
Requir. Eng. 10(2): 112-131 (2005) |
| 59 | | Isabel Ramos,
Daniel M. Berry:
Is emotion relevant to requirements engineering?
Requir. Eng. 10(3): 238-242 (2005) |
| 58 | | Luisa Mich,
Cinzia Anesi,
Daniel M. Berry:
Applying a pragmatics-based creativity-fostering technique to requirements elicitation.
Requir. Eng. 10(4): 262-275 (2005) |
| 2004 |
|---|
| 57 | | Daniel M. Berry,
Rick Kazman,
Roel Wieringa:
Second International Workshop on From SofTware Requirements to Architectures (STRAW'03).
ACM SIGSOFT Software Engineering Notes 29(3): 1-5 (2004) |
| 56 | | Daniel M. Berry,
Khuzaima Daudjee,
Jing Dong,
Igor Fainchtein,
Maria Augusta V. Nelson,
Torsten Nelson,
Lihua Ou:
User's manual as a requirements specification: case studies.
Requir. Eng. 9(1): 67-82 (2004) |
| 55 | | Daniel M. Berry:
Requirements for Maintaining Web Access for Hearing-Impaired Individuals.
Software Quality Journal 12(1): 9-28 (2004) |
| 2003 |
|---|
| 54 | | Daniel M. Berry,
Rick Kazman,
Roel Wieringa:
Second International Workshop on From SofTware Requirements to Architectures (STRAW?03).
ICSE 2003: 797-799 |
| 53 | | H. Dominic Covvey,
David Zitner,
Daniel M. Berry,
Donald D. Cowan,
Michael A. Shepherd:
Formal Structure for Specifying the Content and Quality of the Electronic Health Record.
RE 2003: 162-168 |
| 52 | | Christian Denger,
Daniel M. Berry,
Erik Kamsties:
Higher Quality Requirements Specifications through Natural Language Patterns.
SwSTE 2003: 80- |
| 51 | | Daniel M. Berry,
Walter F. Tichy:
Comments on "Formal Methods Application: An Empirical Tale of Software Development".
IEEE Trans. Software Eng. 29(6): 567-571 (2003) |
| 50 | | Daniel M. Berry:
More requirements engineering adventures with building contractors.
Requir. Eng. 8(2): 142-146 (2003) |
| 2002 |
|---|
| 49 | | Daniel M. Berry:
The Inevitable Pain of Software Development: Why There Is No Silver Bullet.
RISSEF 2002: 50-74 |
| 48 | | Isabel Ramos,
Daniel M. Berry,
João Alvaro Carvalho:
The Role of Emotion, Values, and Beliefs in the Construction of Innovative Work Realities.
Soft-Ware 2002: 300-314 |
| 47 | | Daniel M. Berry:
The importance of ignorance in requirements engineering: An earlier sighting and a revisitation.
Journal of Systems and Software 60(1): 83-85 (2002) |
| 46 |  | Daniel M. Berry:
Formal methods: the very idea - Some thoughts about why they work when they work.
Sci. Comput. Program. 42(1): 11-27 (2002) |
| 2001 |
|---|
| 45 | | Daniel M. Berry:
Requirements for Maintaining Web Access for Hearing-Impaired Individuals.
WSE 2001: 33-41 |
| 2000 |
|---|
| 44 | | Daniel M. Berry,
Erik Kamsties:
The Dangerous 'All' in Specifications.
IWSSD 2000: 191-194 |
| 43 | | Alon Ravid,
Daniel M. Berry:
A Method for Extracting and Stating Software Requirements that a User Interface Prototype Contains.
Requir. Eng. 5(4): 225-241 (2000) |
| 1999 |
|---|
| 42 | | Alon Ravid,
Daniel M. Berry:
A Method for Extracting Requirements that a User Interface Prototype Contains.
HCI (1) 1999: 900-904 |
| 41 | | Daniel M. Berry:
Formal Methods: The Very Idea Some Thoughts About Why They Work When They Work.
Electr. Notes Theor. Comput. Sci. 25: (1999) |
| 40 | | Daniel M. Berry:
Stretching letter and slanted-baseline formatting for Arabic, Hebrew, and Persian with ditroff/ffortid and dynamic PostScript fonts.
Softw., Pract. Exper. 29(15): 1417-1457 (1999) |
| 1998 |
|---|
| 39 | | Daniel M. Berry,
Brian Lawrence:
Guest Editors' Introduction: Requirements Engineering.
IEEE Software 15(2): 26-29 (1998) |
| 38 | | Daniel M. Berry:
Software and House Requirements Engineering: Lessons Learned in Combating Requirements Creep - Viewpoint.
Requir. Eng. 3(3/4): 242-244 (1998) |
| 1997 |
|---|
| 37 | | Daniel M. Berry,
M. Weber:
A Pragmatic, Rigorous Integration of Structural and Behavioral Modeling Notations.
ICFEM 1997: 38- |
| 36 | | Leah Goldin,
Daniel M. Berry:
AbstFinder, A Prototype Natural Language Text Abstraction Finder for Use in Requirements Elicitation.
Autom. Softw. Eng. 4(4): 375-412 (1997) |
| 35 | | Leah Goldin,
Daniel M. Berry:
Reply to Commentaries.
Autom. Softw. Eng. 4(4): 417-418 (1997) |
| 1995 |
|---|
| 34 | | Jair Jehuda,
Gilad Koren,
Daniel M. Berry:
A time-sharing architecture for complex real-time systems.
ICECCS 1995: 9-16 |
| 33 | | Daniel M. Berry:
The importance of ignorance in requirements engineering.
Journal of Systems and Software 28(2): 179-184 (1995) |
| 1994 |
|---|
| 32 | | Bijan Arbab,
Daniel M. Berry:
Some Comments on ``A Denotational Semantics for Prolog''.
ACM Trans. Program. Lang. Syst. 16(3): 605-606 (1994) |
| 31 | | Avner Schwarz,
Daniel M. Berry,
Edna Shaviv:
On the use of the automated building design system.
Computer-Aided Design 26(10): 747-762 (1994) |
| 30 | | Avner Schwarz,
Daniel M. Berry,
Edna Shaviv:
Representing and solving the automated building design problem.
Computer-Aided Design 26(9): 689-698 (1994) |
| 1992 |
|---|
| 29 | | Johny Srouji,
Daniel M. Berry:
Arabic Formatting with DITROFF/FFORTID.
Electronic Publishing 5(4): 163-208 (1992) |
| 1991 |
|---|
| 28 | | Kar-Wing Edward Lor,
Daniel M. Berry:
Automatic Synthesis of SARA Design Models From System Requirements.
IEEE Trans. Software Eng. 17(12): 1229-1240 (1991) |
| 27 | | Yoëlle S. Maarek,
Daniel M. Berry,
Gail E. Kaiser:
An Information Retrieval Approach For Automatically Constructing Software Libraries.
IEEE Trans. Software Eng. 17(8): 800-813 (1991) |
| 1990 |
|---|
| 26 | | Uri Habusha,
Daniel M. Berry:
Vi.iv, a Vi-directional Version of the Full-screen Editor.
Electronic Publishing 3(2): 65-91 (1990) |
| 25 | | Christine Aguilera,
Daniel M. Berry:
The use of a repeated phrase finder in requirements extraction.
Journal of Systems and Software 13(3): 209-230 (1990) |
| 1989 |
|---|
| 24 | | Kris K. Abe,
Daniel M. Berry:
indx and findphrases, A System for Generating Indexes for Ditroll Documents.
Softw., Pract. Exper. 19(1): 1-34 (1989) |
| 1988 |
|---|
| 23 | | Zeev Becker,
Daniel M. Berry:
TRIROFF, an Adaptation of the Device-Independent TROFF for Formatting Tri-directional Text.
Electronic Publishing 2(3): 119-142 (1988) |
| 1987 |
|---|
| 22 | | Shaula Yemini,
Daniel M. Berry:
An Axiomatic Treatment of Exception Handling in an Expression-Oriented Language.
ACM Trans. Program. Lang. Syst. 9(3): 390-407 (1987) |
| 21 | | Daniel M. Berry:
Towards a Formal Basis for the Formal Development Method and the Ina Jo Specification Language.
IEEE Trans. Software Eng. 13(2): 184-201 (1987) |
| 20 | | Bijan Arbab,
Daniel M. Berry:
Operational and Denotational Semantics of Prolog.
J. Log. Program. 4(4): 309-329 (1987) |
| 19 | | Daniel M. Berry,
Nancy Yavne,
Moshe Yavne:
Application of program design language tools to abbott's method of program design by informal natural language descriptions.
Journal of Systems and Software 7(3): 221-247 (1987) |
| 1985 |
|---|
| 18 | | Daniel M. Berry,
Jeannette M. Wing:
Specification and Prototyping: Some Thoughts on Why They Are Successful.
TAPSOFT, Vol.2 1985: 117-128 |
| 17 | | Cary Buchman,
Daniel M. Berry,
Jakob Gonczarowski:
DITROFF/FFORTID, An Adaptation of the UNIX DITROFF for Formatting Bidirectional Text.
ACM Trans. Inf. Syst. 3(4): 380-397 (1985) |
| 16 | | Shaula Yemini,
Daniel M. Berry:
A Modular Verifiable Exception-Handling Mechanism.
ACM Trans. Program. Lang. Syst. 7(2): 214-243 (1985) |
| 15 | | Daniel M. Berry:
A Denotational Semantics for Shared-Memory Parallelism and Nondeterminism.
Acta Inf. 21: 599-627 (1985) |
| 14 | | Shahrzade Mazaher,
Daniel M. Berry:
Deriving a Compiler From an Operational Semantics Written in VDL.
Comput. Lang. 10(2): 147-164 (1985) |
| 1983 |
|---|
| 13 | | Nancy G. Leveson,
Anthony I. Wasserman,
Daniel M. Berry:
BASIS: A Behavioral Approach to the Specification of Information Systems.
Inf. Syst. 8(1): 15-23 (1983) |
| 12 | | Daniel M. Berry:
A New Methodology for Generating Test Cases for a Programming Language Compiler.
SIGPLAN Notices 18(2): 46-56 (1983) |
| 1982 |
|---|
| 11 | | Daniel M. Berry,
Carlo Ghezzi,
Dino Mandrioli,
Francesco Tisato:
Language Constructs for Real-Time Distributed Systems.
Comput. Lang. 7(1): 11-20 (1982) |
| 1981 |
|---|
| 10 | | Maria Heloisa (Lolo) Penedo,
Daniel M. Berry,
Gerald Estrin:
An Algorithm to Support Code-Skeleton Generation for Concurrent Systems.
ICSE 1981: 125-135 |
| 9 | | Daniel M. Berry:
Remarks on R. D. Tennent's Language Design Methods Based on Semantic Principles: Algol 68, A Language Designed Using Semantic Principles.
Acta Inf. 15: 83-98 (1981) |
| 1980 |
|---|
| 8 | | Daniel M. Berry,
Richard A. Kemmerer,
Arndt von Staa,
Shaula Yemini:
Toward Modular Verifiable Exception Handling.
Comput. Lang. 5(2): 77-101 (1980) |
| 1979 |
|---|
| 7 | | Daniel M. Berry,
Maria Heloisa (Lolo) Penedo:
The Use of a Module Interconnection Specification Capability in the SARA System Design Methodology.
ICSE 1979: 294-307 |
| 6 | | Richard L. Schwartz,
Daniel M. Berry:
A semantic view of ALGOL 68.
Comput. Lang. 4(1): 1-15 (1979) |
| 5 | | Daniel M. Berry,
Richard L. Schwartz:
United and Discriminated Record Types in Strongly Typed Languages.
Inf. Process. Lett. 9(1): 13-18 (1979) |
| 1977 |
|---|
| 4 | | Daniel M. Berry,
Z. Erlich,
Carlos José Pereira de Lucena:
Pointers and Data Abstractions in High Level Languages - I: Language Proposals.
Comput. Lang. 2(14): 135-148 (1977) |
| 3 | | Daniel M. Berry:
Pointers and Data Abstractions in High Level Languages - II: Correctness Proofs.
Comput. Lang. 2(14): 149-170 (1977) |
| 1976 |
|---|
| 2 | | Daniel M. Berry,
Z. Erlich,
Carlos José Pereira de Lucena:
Correctness of Data Representations: Pointers in High Level Languages.
Conference on Data: Abstraction, Definition and Structure 1976: 115-119 |
| 1971 |
|---|
| 1 | | Daniel M. Berry:
Block Structure: Retention or Deletion? (Extended Abstract)
STOC 1971: 86-100 |
