default search action
Google
Google Scholar
Semantic Scholar
Internet Archive Scholar
CiteSeerX
ORCIDDaniel M. Berry
Person information
Refine list
refinements active!
zoomed in on ?? of ?? records
view refined list in
export refined list as
showing all ?? records
2020 – today
- 2024
[c69]Anzira Rahman
, Luiz Marcio Cysneiros, Daniel M. Berry:
An Empirical Study of the Impact of Waterfall and Agile Methods on Numbers of Requirements-Related Defects. SAC 2024: 1143-1152- 2023
- [j76]Luisa Mich, Victoria Sakhnini, Daniel M. Berry:
To group or not to group? Group sizes for requirements elicitation. Inf. Softw. Technol. 160: 107229 (2023) - [c68]Daniel M. Berry, Márcia Lucena, Victoria Sakhnini, Abhishek Dhakla:
Scope Determined (D) and Scope Determining (G) Requirements: A New Categorization of Functional Requirements. REFSQ 2023: 75-84 - 2022
- [c67]Daniel M. Berry:
Requirements Engineering for Artificial Intelligence: What Is a Requirements Specification for an Artificial Intelligence? REFSQ 2022: 19-25 - 2021
- [j75]Daniel M. Berry:
Empirical evaluation of tools for hairy requirements engineering tasks. Empir. Softw. Eng. 26(5): 111 (2021) - [j74]Gaurav Mehrotra, Daniel M. Berry:
How to benefit from newbies' domain ignorance in software development projects. Sci. Comput. Program. 204: 102593 (2021) - [c66]Yetian Wang, Randy Allen Harris, Daniel M. Berry:
An Ontology for Ploke: Rhetorical Figures of Lexical Repetitions. JOWO 2021 - 2020
- [j73]Cristina Ribeiro, Daniel M. Berry:
The prevalence and severity of persistent ambiguity in software requirements specifications: Is a special effort needed to find them? Sci. Comput. Program. 195: 102472 (2020) - [c65]Daniel M. Berry:
The Tenth Anniversary of the CreaRE Workshops: A Look Back and a Look Forward. REFSQ Workshops 2020 - [c64]Johnathan DiMatteo, Daniel M. Berry, Krzysztof Czarnecki:
Requirements for Monitoring Inattention of the Responsible Human in an Autonomous Vehicle: The Recall and Precision Tradeoff. REFSQ Workshops 2020
2010 – 2019
- 2019
- [j72]Irit Hadar, Anna Zamansky, Daniel M. Berry:
The inconsistency between theory and practice in managing inconsistency in requirements engineering. Empir. Softw. Eng. 24(6): 3972-4005 (2019) - [c63]Daniel M. Berry:
The Requirements Engineering Reference Model: A Fundamental Impediment to Using Formal Methods in Software Systems Development. RE Workshops 2019: 109 - [c62]Andrea Herrmann, Daniel M. Berry, Maya Daneva, Eduard C. Groen:
Preface: Eighth International Workshop on Creativity in Requirements Engineering (CreaRE 2019). REFSQ Workshops 2019 - [c61]Andrea Herrmann, Luisa Mich, Daniel M. Berry:
Two Experiments Comparing Two Four-Step EPMcreate-Based Creativity Techniques for Requirements Elicitation. REFSQ Workshops 2019 - [e4]Paola Spoletini, Patrick Mäder, Daniel M. Berry, Fabiano Dalpiaz, Maya Daneva, Alessio Ferrari, Xavier Franch, Sarah Gregory, Eduard C. Groen, Andrea Herrmann, Anne Hess, Frank Houdek, Oliver Karras, Anne Koziolek, Kim Lauenroth, Cristina Palomares, Mehrdad Sabetzadeh, Norbert Seyff, Marcus Trapp, Andreas Vogelsang, Thorsten Weyer:
Joint Proceedings of REFSQ-2019 Workshops, Doctoral Symposium, Live Studies Track, and Poster Track co-located with the 25th International Conference on Requirements Engineering: Foundation for Software Quality (REFSQ 2019), Essen, Germany, March 18th, 2019. CEUR Workshop Proceedings 2376, CEUR-WS.org 2019 [contents] - 2018
- [j71]Andreas Maier, Daniel M. Berry:
Improving the identification of hedonic quality in user requirements: a second controlled experiment. Requir. Eng. 23(3): 401-424 (2018) - [j70]Janna-Lynn (Weber) Dupree, Edward Lank, Daniel M. Berry:
A case study of using grounded analysis as a requirement engineering method: Identifying personas that specify privacy and security tool users. Sci. Comput. Program. 152: 1-37 (2018) - [c60]Andrea Herrmann, Luisa Mich, Daniel M. Berry:
Creativity Techniques for Requirements Elicitation: Comparing Four-Step EPMcreate-Based Processes. EmpiRE@RE 2018: 1-7 - [c59]Daniel M. Berry:
Keynote: Evaluation of NLP Tools for Hairy RE Tasks. REFSQ Workshops 2018 - 2017
- [j69]Ali Niknafs, Daniel M. Berry:
The impact of domain knowledge on the effectiveness of requirements engineering activities. Empir. Softw. Eng. 22(1): 80-133 (2017) - [j68]Victoria Sakhnini, Luisa Mich, Daniel M. Berry:
Group versus individual use of power-only EPMcreate as a creativity enhancement technique for requirements elicitation. Empir. Softw. Eng. 22(4): 2001-2049 (2017) - [c58]Colin M. Werner, Daniel M. Berry:
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. APRES 2017: 15-25 - [c57]Andreas Maier, Daniel M. Berry:
Improving the Identification of Hedonic Quality in User Requirements - A Controlled Experiment. RE 2017: 213-222 - [c56]Daniel M. Berry:
Evaluation of Tools for Hairy Requirements and Software Engineering Tasks. RE Workshops 2017: 284-291 - [c55]Daniel M. Berry, Jane Cleland-Huang, Alessio Ferrari, Walid Maalej, John Mylopoulos, Didar Zowghi:
Panel: Context-Dependent Evaluation of Tools for NL RE Tasks: Recall vs. Precision, and Beyond. RE 2017: 570-573 - [c54]Luisa Mich, Victoria Sakhnini, Daniel M. Berry:
Downsizing EPMcreate to Lighter Creativity Techniques for Requirements Elicitation. REFSQ Workshops 2017 - [e3]Eric Knauss, Angelo Susi, David Ameller, Daniel M. Berry, Fabiano Dalpiaz, Maya Daneva, Marian Daun, Oscar Dieste, Peter Forbrig, Eduard C. Groen, Andrea Herrmann, Jennifer Horkoff, Fitsum Meshesha Kifetew, Marite Kirikova, Alessia Knauss, Patrick Maeder, Fabio Massacci, Cristina Palomares, Jolita Ralyté, Ahmed Seffah, Alberto Siena, Bastian Tenbergen:
Joint Proceedings of REFSQ-2017 Workshops, Doctoral Symposium, Research Method Track, and Poster Track co-located with the 22nd International Conference on Requirements Engineering: Foundation for Software Quality (REFSQ 2017), Essen, Germany, February 27, 2017. CEUR Workshop Proceedings 1796, CEUR-WS.org 2017 [contents] - 2016
- [c53]Janna Lynn Dupree, Richard Devries, Daniel M. Berry, Edward Lank:
Privacy Personas: Clustering Users via Attitudes and Behaviors toward Security Practices. CHI 2016: 5228-5239 - [c52]Anna Zamansky, Irit Hadar, Daniel M. Berry:
Reasoning about Inconsistency in RE - Separating the Wheat from the Chaff. ENASE 2016: 377-382 - [c51]Daniel M. Berry, Krzysztof Czarnecki, Michal Antkiewicz, Mohamed AbdelRazik:
The Problem of the Lack of Benefit of a Document to Its Producer (PotLoBoaDtiP). SwSTE 2016: 37-42 - 2015
- [j67]Leah Goldin, Daniel M. Berry:
Reuse of requirements reduced time to market at one industrial shop: a case study. Requir. Eng. 20(1): 23-44 (2015) - 2014
- [c50]Cyril Mauger, Daniel M. Berry:
Lessons Learned from and for Requirements Engineering and Building Construction: A Case Study of Requirements Engineering for a Synagogue Kitchen with Use Cases and Scenarios. SwSTE 2014: 67-76 - [p1]Daniel M. Berry:
Requirements Elicitation. Computing Handbook, 3rd ed. (1) 2014: 87: 1-17 - [e2]Birgit Penzenstadler, Anne Persson, Andrea Herrmann, Maya Daneva, Jörg Dörr, Anne Hoffmann, Kurt Schneider, Axel Kalenborn, Marcus Trapp, Roel J. Wieringa, Daniel M. Berry, Xavier Franch, Jolita Ralyté, Krzysztof Wnuk, Vincenzo Gervasi:
Joint Proceedings of REFSQ-2014 Workshops, Doctoral Symposium, Empirical Track, and Posters, co-located with the 20th International Conference on Requirements Engineering: Foundation for Software Quality (REFSQ 2014), Essen, Germany, April 7-10, 2014. CEUR Workshop Proceedings 1138, CEUR-WS.org 2014 [contents] - 2013
- [j66]Keith Ellis, Daniel M. Berry:
Quantifying the impact of requirements definition and management process maturity on project outcome in large business application development. Requir. Eng. 18(3): 223-249 (2013) - [j65]Daniel M. Berry:
The essential similarity and differences between mathematical modeling and programming. Sci. Comput. Program. 78(9): 1208-1211 (2013) - [c49]Ali Niknafs, Daniel M. Berry:
An industrial case study of the impact of domain ignorance on the effectiveness of requirements idea generation during requirements elicitation. RE 2013: 279-283 - [c48]Erik Jan Philippo, Werner Heijstek, Bas Kruiswijk, Michel R. V. Chaudron, Daniel M. Berry:
Requirement Ambiguity Not as Important as Expected - Results of an Empirical Evaluation. REFSQ 2013: 65-79 - [c47]Sri Fatimah Tjong, Daniel M. Berry:
The Design of SREE - A Prototype Potential Ambiguity Finder for Requirements Specifications and Lessons Learned. REFSQ 2013: 80-95 - 2012
- [j64]Daniel M. Berry, Xavier Franch:
Introduction to the REFSQ 2011 special issue. Requir. Eng. 17(1): 1-2 (2012) - [j63]Victoria Sakhnini, Luisa Mich, Daniel M. Berry:
The effectiveness of an optimized EPMcreate as a creativity enhancement technique for Web site requirements elicitation. Requir. Eng. 17(3): 171-186 (2012) - [c46]Ali Niknafs, Daniel M. Berry:
The impact of domain knowledge on the effectiveness of requirements idea generation during requirements elicitation. RE 2012: 181-190 - [c45]Daniel M. Berry, Ricardo Gacitúa, Pete Sawyer, Sri Fatimah Tjong:
The Case for Dumb Requirements Engineering Tools. REFSQ 2012: 211-217 - 2011
- [j62]Daniel M. Berry:
Liability issues in software engineering: technical perspective. Commun. ACM 54(4): 98 (2011) - [j61]Daniel M. Berry:
Software requirements and design: the work of Michael Jackson by Bashar Nuseibeh and Pamela Zave. ACM SIGSOFT Softw. Eng. Notes 36(2): 39-40 (2011) - [c44]Daniel Isaacs, Daniel M. Berry:
Developers want requirements, but their project manager doesn't; and a possibly transcendent Hawthorne effect. EmpiRE 2011: 37-44 - [c43]Daniel M. Berry:
Keynote requirements for maintaining web access for hearing-impaired individuals: A ten-year perspective. WSE 2011: 97-98 - [e1]Daniel M. Berry, Xavier Franch:
Requirements Engineering: Foundation for Software Quality - 17th International Working Conference, REFSQ 2011, Essen, Germany, March 28-30, 2011. Proceedings. Lecture Notes in Computer Science 6606, Springer 2011, ISBN 978-3-642-19857-1 [contents] - 2010
- [c42]Daniel M. Berry, Craig S. Kaplan:
Planned programming problem gotchas as lessons in requirements engineering. REET 2010: 20-25 - [c41]Daniel M. Berry, Krzysztof Czarnecki, Michal Antkiewicz, Mohamed AbdelRazik:
Requirements Determination is Unstoppable: An Experience Report. RE 2010: 311-316 - [c40]Victoria Sakhnini, Daniel M. Berry, Luisa Mich:
Validation of the Effectiveness of an Optimized EPMcreate as an Aid for Creative Requirements Elicitation. REFSQ 2010: 91-105 - [c39]Daniel M. Berry, Brian Berenbach:
Ethics Test Results Before and After Ethics Training: A Disturbing Experience. SwSTE 2010: 70-76
2000 – 2009
- 2008
- [j60]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) - [j59]Daniel M. Berry:
The Software Engineering Silver Bullet Conundrum. IEEE Softw. 25(2): 18-19 (2008) - [c38]Daniel M. Berry:
In requirements engineering, everything is an aspect. EA@ICSE 2008: 1-2 - [c37]Sri Fatimah Tjong, Daniel M. Berry:
Can Rules of Inferences Resolve Coordination Ambiguity in Natural Language Requirements Specification? WER 2008 - 2007
- [j58]Andrzej Sobczak, Daniel M. Berry:
Distributed priority ranking of strategic preliminary requirements for management information systems in economic organizations. Inf. Softw. Technol. 49(9-10): 960-984 (2007) - [j57]Davor Svetinovic, Daniel M. Berry, Nancy A. Day, Michael W. Godfrey:
Unified use case statecharts: case studies. Requir. Eng. 12(4): 245-264 (2007) - [c36]Daniel M. Berry:
Ambiguity in Natural Language Requirements Documents. Monterey Workshop 2007: 1-7 - [c35]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 - [c34]Daniel M. Berry:
Requirements Engineering Lessons from House Building. WER 2007: 1 - [c33]Sri Fatimah Tjong, Michael Hartley, Daniel M. Berry:
Extended Disambiguation Rules for Requirements Specifications. WER 2007: 97-106 - [c32]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 - 2006
- [j56]Daniel M. Berry:
Aybüke Aurum and Claes Wohlin (eds): Engineering and managing software requirements. Requir. Eng. 11(2): 152-154 (2006) - [c31]Davor Svetinovic, Daniel M. Berry, Michael W. Godfrey:
Increasing quality of conceptual models: is object-oriented analysis that simple? ROA@ICSE 2006: 19-22 - [c30]Joel So, Daniel M. Berry:
Experiences of Requirements Engineering for Two Consecutive Versions of a Product at VLSC. RE 2006: 216-221 - 2005
- [j55]Isabel Ramos, Daniel M. Berry, João Álvaro Carvalho:
Requirements engineering for organizational transformation. Inf. Softw. Technol. 47(7): 479-495 (2005) - [j54]Isabel Ramos, Daniel M. Berry:
Social Construction of Information Technology Supporting Work. J. Cases Inf. Technol. 7(3): 1-17 (2005) - [j53]Karin Koogan Breitman, Julio César Sampaio do Prado Leite, Daniel M. Berry:
Supporting scenario evolution. Requir. Eng. 10(2): 112-131 (2005) - [j52]Isabel Ramos, Daniel M. Berry:
Is emotion relevant to requirements engineering? Requir. Eng. 10(3): 238-242 (2005) - [j51]Luisa Mich, Cinzia Anesi, Daniel M. Berry:
Applying a pragmatics-based creativity-fostering technique to requirements elicitation. Requir. Eng. 10(4): 262-275 (2005) - [j50]Daniel M. Berry, Erik Kamsties:
The Syntactically Dangerous All and Plural in Specifications. IEEE Softw. 22(1): 55-57 (2005) - [c29]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 - [c28]Daniel M. Berry, Daniela E. 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 - [c27]Claudia Hazan, Daniel M. Berry, Julio César Sampaio do Prado Leite:
É possível substituir processos de Engenharia de Requisitos por Contagem de Pontos de Função?. WER 2005: 197-208 - 2004
- [j49]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) - [j48]Daniel M. Berry, Rick Kazman, Roel J. Wieringa:
Second International Workshop on From SofTware Requirements to Architectures (STRAW'03). ACM SIGSOFT Softw. Eng. Notes 29(3): 1-5 (2004) - [j47]Daniel M. Berry:
Requirements for Maintaining Web Access for Hearing-Impaired Individuals. Softw. Qual. J. 12(1): 9-28 (2004) - 2003
- [j46]Daniel M. Berry:
More requirements engineering adventures with building contractors. Requir. Eng. 8(2): 142-146 (2003) - [j45]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) - [c26]Daniel M. Berry, Rick Kazman, Roel J. Wieringa:
Second International Workshop on From SofTware Requirements to Architectures (STRAW?03). ICSE 2003: 797-799 - [c25]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 - [c24]Christian Denger, Daniel M. Berry, Erik Kamsties:
Higher Quality Requirements Specifications through Natural Language Patterns. SwSTE 2003: 80- - 2002
- [j44]Daniel M. Berry:
The importance of ignorance in requirements engineering: An earlier sighting and a revisitation. J. Syst. Softw. 60(1): 83-85 (2002) - [j43]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) - [c23]Daniel M. Berry:
The Inevitable Pain of Software Development: Why There Is No Silver Bullet. RISSEF 2002: 50-74 - [c22]Isabel Ramos, Daniel M. Berry, João Álvaro Carvalho:
The Role of Emotion, Values, and Beliefs in the Construction of Innovative Work Realities. Soft-Ware 2002: 300-314 - 2001
- [c21]Daniel M. Berry:
Requirements for Maintaining Web Access for Hearing-Impaired Individuals. WSE 2001: 33-41 - 2000
- [j42]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) - [c20]Daniel M. Berry, Erik Kamsties:
The Dangerous 'All' in Specifications. IWSSD 2000: 191-194
1990 – 1999
- 1999
- [j41]Daniel M. Berry:
Stretching letter and slanted-baseline formatting for Arabic, Hebrew, and Persian with ditroff/ffortid and dynamic PostScript fonts. Softw. Pract. Exp. 29(15): 1417-1457 (1999) - [c19]Alon Ravid, Daniel M. Berry:
A Method for Extracting Requirements that a User Interface Prototype Contains. HCI (1) 1999: 900-904 - 1998
- [j40]Daniel M. Berry:
Software and House Requirements Engineering: Lessons Learned in Combating Requirements Creep - Viewpoint. Requir. Eng. 3(3/4): 242-244 (1998) - [j39]Daniel M. Berry, Brian Lawrence:
Guest Editors' Introduction: Requirements Engineering. IEEE Softw. 15(2): 26-29 (1998) - [c18]Daniel M. Berry:
The Safety Requirements Engineering Dilemma. IWSSD 1998: 147-149 - [c17]Daniel M. Berry:
Formal Methods: The Very Idea Some Thoughts About Why They Work When They Work. Monterey Workshop 1998: 10-22 - 1997
- [j38]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) - [j37]Leah Goldin, Daniel M. Berry:
Reply to Commentaries. Autom. Softw. Eng. 4(4): 417-418 (1997) - [c16]Daniel M. Berry, M. Weber:
A Pragmatic, Rigorous Integration of Structural and Behavioral Modeling Notations. ICFEM 1997: 38-49 - 1995
- [j36]Daniel M. Berry:
The importance of ignorance in requirements engineering. J. Syst. Softw. 28(2): 179-184 (1995) - [c15]Jair Jehuda, Gilad Koren, Daniel M. Berry:
A time-sharing architecture for complex real-time systems. ICECCS 1995: 9-16 - [c14]Karin Sequerra-Breitman, Daniel M. Berry:
The Development of Multimedia Hypermedia Applications as Evolutionary, Prototyping-Based Requirements Engineering. SBES 1995: 363-378 - 1994
- [j35]Avner Schwarz, Daniel M. Berry, Edna Shaviv:
Representing and solving the automated building design problem. Comput. Aided Des. 26(9): 689-698 (1994) - [j34]Avner Schwarz, Daniel M. Berry, Edna Shaviv:
On the use of the automated building design system. Comput. Aided Des. 26(10): 747-762 (1994) - [j33]Bijan Arbab, Daniel M. Berry:
Some Comments on "A Denotational Semantics for Prolog". ACM Trans. Program. Lang. Syst. 16(3): 605-606 (1994) - [c13]Leah Goldin, Daniel M. Berry:
AbstFinder, a prototype abstraction finder for natural language text for use in requirements elicitation: design, methodology, and evaluation. ICRE 1994: 84-93 - 1992
- [j32]Johny Srouji, Daniel M. Berry:
Arabic Formatting with DITROFF/FFORTID. Electron. Publ. 5(4): 163-208 (1992) - 1991
- [j31]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) - [j30]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) - 1990
- [j29]Uri Habusha, Daniel M. Berry:
Vi.iv, a Vi-directional Version of the Full-screen Editor. Electron. Publ. 3(2): 65-91 (1990) - [j28]Christine Aguilera, Daniel M. Berry:
The use of a repeated phrase finder in requirements extraction. J. Syst. Softw. 13(3): 209-230 (1990)
1980 – 1989
- 1989
- [j27]Kris K. Abe, Daniel M. Berry:
indx and findphrases, A System for Generating Indexes for Ditroll Documents. Softw. Pract. Exp. 19(1): 1-34 (1989) - [c12]Yoëlle S. Maarek, Daniel M. Berry:
The use of lexical affinities in requirements extraction. IWSSD 1989: 196-202 - 1988
- [j26]Zeev Becker, Daniel M. Berry:
TRIROFF, an Adaptation of the Device-Independent TROFF for Formatting Tri-directional Text. Electron. Publ. 2(3): 119-142 (1988) - 1987
- [j25]Bijan Arbab, Daniel M. Berry:
Operational and Denotational Semantics of Prolog. J. Log. Program. 4(4): 309-329 (1987) - [j24]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. J. Syst. Softw. 7(3): 221-247 (1987) - [j23]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) - [j22]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) - 1985
- [j21]Daniel M. Berry:
A Denotational Semantics for Shared-Memory Parallelism and Nondeterminism. Acta Informatica 21: 599-627 (1985) - [j20]Shahrzade Mazaher, Daniel M. Berry:
Deriving a Compiler From an Operational Semantics Written in VDL. Comput. Lang. 10(2): 147-164 (1985) - [j19]Daniel M. Berry:
An Ina Jo® proof manager for the formal development method. ACM SIGSOFT Softw. Eng. Notes 10(4): 19-25 (1985) - [j18]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) - [j17]Shaula Yemini, Daniel M. Berry:
A Modular Verifiable Exception-Handling Mechanism. ACM Trans. Program. Lang. Syst. 7(2): 214-243 (1985) - [c11]Daniel M. Berry, Jeannette M. Wing:
Specification and Prototyping: Some Thoughts on Why They Are Successful. TAPSOFT, Vol.2 1985: 117-128 - 1983
- [j16]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) - [j15]Daniel M. Berry:
A New Methodology for Generating Test Cases for a Programming Language Compiler. ACM SIGPLAN Notices 18(2): 46-56 (1983) - 1982
- [j14]Daniel M. Berry, Carlo Ghezzi, Dino Mandrioli, Francesco Tisato:
Language Constructs for Real-Time Distributed Systems. Comput. Lang. 7(1): 11-20 (1982) - 1981
- [j13]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 Informatica 15: 83-98 (1981) - [c10]Maria Heloisa (Lolo) Penedo, Daniel M. Berry, Gerald Estrin:
An Algorithm to Support Code-Skeleton Generation for Concurrent Systems. ICSE 1981: 125-135 - 1980
- [j12]Daniel M. Berry, Richard A. Kemmerer, Arndt von Staa, Shaula Yemini:
Toward Modular Verifiable Exception Handling. Comput. Lang. 5(2): 77-101 (1980)
1970 – 1979
- 1979
- [j11]Richard L. Schwartz, Daniel M. Berry:
A semantic view of ALGOL 68. Comput. Lang. 4(1): 1-15 (1979) - [j10]Daniel M. Berry, Richard L. Schwartz:
United and Discriminated Record Types in Strongly Typed Languages. Inf. Process. Lett. 9(1): 13-18 (1979) - [j9]Daniel M. Berry, Richard L. Schwartz:
Type equivalence in strongly typed languages: one more look. ACM SIGPLAN Notices 14(9): 35-41 (1979) - [c9]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 - 1978
- [j8]Daniel M. Berry, Laurian M. Chirica, John B. Johnston, David F. Martin, Arthur Sorkin:
Time required for reference count management in retention block-structured languages. Part 1. Int. J. Parallel Program. 7(1): 11-64 (1978) - [j7]Daniel M. Berry, Laurian M. Chirica, John B. Johnston, David F. Martin, Arthur Sorkin:
On the time required for reference count management in retention block-structured languages. Part 2. Int. J. Parallel Program. 7(2): 91-119 (1978) - [j6]Daniel M. Berry, Arthur Sorkin:
Time required for garbage collection in retention block-structured languages. Int. J. Parallel Program. 7(4): 361-404 (1978) - 1977
- [j5]Daniel M. Berry, Z. Erlich, Carlos José Pereira de Lucena:
Pointers and Data Abstractions in High Level Languages - I: Language Proposals. Comput. Lang. 2(4): 135-148 (1977) - [j4]Daniel M. Berry:
Pointers and Data Abstractions in High Level Languages - II: Correctness Proofs. Comput. Lang. 2(4): 149-170 (1977) - [c8]Daniel M. Berry, Michael Erlinger, John B. Johnston, Arndt von Staa:
Models of Hierarchical Machine Support. Formal Description of Programming Concepts 1977: 557-588 - 1976
- [c7]Daniel M. Berry, John B. Johnston:
SIGPLAN(Tutorial Session). ACM Annual Conference 1976: 387-389 - [c6]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 - 1975
- [j3]Daniel M. Berry:
Structured documentation. ACM SIGPLAN Notices 10(11): 7-12 (1975) - 1974
- [c5]Carlos José Pereira de Lucena, Daniel M. Berry:
Towards a definition of structured programming. ACM Annual Conference (2) 1974: 635-640 - 1973
- [c4]Daniel M. Berry, Laurian M. Chirica, John B. Johnston, David F. Martin, Arthur Sorkin:
On the time required for retention. HLLCA 1973: 165-178 - [c3]Daniel M. Berry:
Towards ISMs for OPSs. SIGPLAN-SIGOPS Interface Meeting 1973: 46-49 - 1972
- [c2]Daniel M. Berry:
The equivalence of models of tasking. Proving Assertions About Programs 1972: 170-190 - 1971
- [j2]Daniel M. Berry:
Introduction to Oregano. ACM SIGPLAN Notices 6(2): 171-190 (1971) - [c1]Daniel M. Berry:
Block Structure: Retention or Deletion? (Extended Abstract). STOC 1971: 86-100 - 1970
- [j1]Daniel M. Berry:
The importance of implementation models in ALGOL 68: or how to discover the concept of necessary environment. ACM SIGPLAN Notices 5(9): 14-24 (1970)
Coauthor Index
manage site settings
To protect your privacy, all features that rely on external API calls from your browser are turned off by default. You need to opt-in for them to become active. All settings here will be stored as cookies with your web browser. For more information see our F.A.Q.
Unpaywalled article links
Add open access links from 
to the list of external document links (if available).
Privacy notice: By enabling the option above, your browser will contact the API of unpaywall.org to load hyperlinks to open access articles. Although we do not have any reason to believe that your call will be tracked, we do not have any control over how the remote server uses your data. So please proceed with care and consider checking the Unpaywall privacy policy.
Archived links via Wayback Machine
For web page which are no longer available, try to retrieve content from the 
of the Internet Archive (if available).
Privacy notice: By enabling the option above, your browser will contact the API of archive.org to check for archived content of web pages that are no longer available. Although we do not have any reason to believe that your call will be tracked, we do not have any control over how the remote server uses your data. So please proceed with care and consider checking the Internet Archive privacy policy.
Reference lists
Add a list of references from 
, 
, and 
to record detail pages.
load references from crossref.org and opencitations.net
Privacy notice: By enabling the option above, your browser will contact the APIs of crossref.org, opencitations.net, and semanticscholar.org to load article reference information. Although we do not have any reason to believe that your call will be tracked, we do not have any control over how the remote server uses your data. So please proceed with care and consider checking the Crossref privacy policy and the OpenCitations privacy policy, as well as the AI2 Privacy Policy covering Semantic Scholar.
Citation data
Add a list of citing articles from and to record detail pages.
load citations from opencitations.net
Privacy notice: By enabling the option above, your browser will contact the API of opencitations.net and semanticscholar.org to load citation information. Although we do not have any reason to believe that your call will be tracked, we do not have any control over how the remote server uses your data. So please proceed with care and consider checking the OpenCitations privacy policy as well as the AI2 Privacy Policy covering Semantic Scholar.
OpenAlex data
Load additional information about publications from 
.
Privacy notice: By enabling the option above, your browser will contact the API of openalex.org to load additional information. Although we do not have any reason to believe that your call will be tracked, we do not have any control over how the remote server uses your data. So please proceed with care and consider checking the information given by OpenAlex.
last updated on 2024-06-03 00:59 CEST by the dblp team
all metadata released as open data under CC0 1.0 license
see also: Terms of Use | Privacy Policy | Imprint
dblp was originally created in 1993 at:
since 2018, dblp has been operated and maintained by:
the dblp computer science bibliography is funded and supported by:
