Journal of Software Engineering Research and Development Cover Image

  • Search by keyword
  • Search by citation

Page 1 of 2

Metric-centered and technology-independent architectural views for software comprehension

The maintenance of applications is a crucial activity in the software industry. The high cost of this process is due to the effort invested on software comprehension since, in most of cases, there is no up-to-...

  • View Full Text

Back to the future: origins and directions of the “Agile Manifesto” – views of the originators

In 2001, seventeen professionals set up the manifesto for agile software development. They wanted to define values and basic principles for better software development. On top of being brought into focus, the ...

Investigating the effectiveness of peer code review in distributed software development based on objective and subjective data

Code review is a potential means of improving software quality. To be effective, it depends on different factors, and many have been investigated in the literature to identify the scenarios in which it adds qu...

On the benefits and challenges of using kanban in software engineering: a structured synthesis study

Kanban is increasingly being used in diverse software organizations. There is extensive research regarding its benefits and challenges in Software Engineering, reported in both primary and secondary studies. H...

Challenges on applying genetic improvement in JavaScript using a high-performance computer

Genetic Improvement is an area of Search Based Software Engineering that aims to apply evolutionary computing operators to the software source code to improve it according to one or more quality metrics. This ...

Actor’s social complexity: a proposal for managing the iStar model

Complex systems are inherent to modern society, in which individuals, organizations, and computational elements relate with each other to achieve a predefined purpose, which transcends individual goals. In thi...

Investigating measures for applying statistical process control in software organizations

The growing interest in improving software processes has led organizations to aim for high maturity, where statistical process control (SPC) is required. SPC makes it possible to analyze process behavior, pred...

An approach for applying Test-Driven Development (TDD) in the development of randomized algorithms

TDD is a technique traditionally applied in applications with deterministic algorithms, in which the input and the expected result are known. However, the application of TDD with randomized algorithms have bee...

Supporting governance of mobile application developers from mining and analyzing technical questions in stack overflow

There is a need to improve the direct communication between large organizations that maintain mobile platforms (e.g. Apple, Google, and Microsoft) and third-party developers to solve technical questions that e...

Working software over comprehensive documentation – Rationales of agile teams for artefacts usage

Agile software development (ASD) promotes working software over comprehensive documentation. Still, recent research has shown agile teams to use quite a number of artefacts. Whereas some artefacts may be adopt...

Development as a journey: factors supporting the adoption and use of software frameworks

From the point of view of the software framework owner, attracting new and supporting existing application developers is crucial for the long-term success of the framework. This mixed-methods study explores th...

Applying user-centered techniques to analyze and design a mobile application

Techniques that help in understanding and designing user needs are increasingly being used in Software Engineering to improve the acceptance of applications. Among these techniques we can cite personas, scenar...

A measurement model to analyze the effect of agile enterprise architecture on geographically distributed agile development

Efficient and effective communication (active communication) among stakeholders is thought to be central to agile development. However, in geographically distributed agile development (GDAD) environments, it c...

A survey of search-based refactoring for software maintenance

This survey reviews published materials related to the specific area of Search-Based Software Engineering that concerns software maintenance and, in particular, refactoring. The survey aims to give a comprehen...

Guest editorial foreword for the special issue on automated software testing: trends and evidence

Similarity testing for role-based access control systems.

Access control systems demand rigorous verification and validation approaches, otherwise, they can end up with security breaches. Finite state machines based testing has been successfully applied to RBAC syste...

An algorithm for combinatorial interaction testing: definitions and rigorous evaluations

Combinatorial Interaction Testing (CIT) approaches have drawn attention of the software testing community to generate sets of smaller, efficient, and effective test cases where they have been successful in det...

How diverse is your team? Investigating gender and nationality diversity in GitHub teams

Building an effective team of developers is a complex task faced by both software companies and open source communities. The problem of forming a “dream”

Investigating factors that affect the human perception on god class detection: an analysis based on a family of four controlled experiments

Evaluation of design problems in object oriented systems, which we call code smells, is mostly a human-based task. Several studies have investigated the impact of code smells in practice. Studies focusing on h...

On the evaluation of code smells and detection tools

Code smells refer to any symptom in the source code of a program that possibly indicates a deeper problem, hindering software maintenance and evolution. Detection of code smells is challenging for developers a...

On the influence of program constructs on bug localization effectiveness

Software projects often reach hundreds or thousands of files. Therefore, manually searching for code elements that should be changed to fix a failure is a difficult task. Static bug localization techniques pro...

DyeVC: an approach for monitoring and visualizing distributed repositories

Software development using distributed version control systems has become more frequent recently. Such systems bring more flexibility, but also greater complexity to manage and monitor multiple existing reposi...

A genetic algorithm based framework for software effort prediction

Several prediction models have been proposed in the literature using different techniques obtaining different results in different contexts. The need for accurate effort predictions for projects is one of the ...

Elaboration of software requirements documents by means of patterns instantiation

Studies show that problems associated with the requirements specifications are widely recognized for affecting software quality and impacting effectiveness of its development process. The reuse of knowledge ob...

ArchReco: a software tool to assist software design based on context aware recommendations of design patterns

This work describes the design, development and evaluation of a software Prototype, named ArchReco, an educational tool that employs two types of Context-aware Recommendations of Design Patterns, to support us...

On multi-language software development, cross-language links and accompanying tools: a survey of professional software developers

Non-trivial software systems are written using multiple (programming) languages, which are connected by cross-language links. The existence of such links may lead to various problems during software developmen...

SoftCoDeR approach: promoting Software Engineering Academia-Industry partnership using CMD, DSR and ESE

The Academia-Industry partnership has been increasingly encouraged in the software development field. The main focus of the initiatives is driven by the collaborative work where the scientific research work me...

Issues on developing interoperable cloud applications: definitions, concepts, approaches, requirements, characteristics and evaluation models

Among research opportunities in software engineering for cloud computing model, interoperability stands out. We found that the dynamic nature of cloud technologies and the battle for market domination make clo...

Game development software engineering process life cycle: a systematic review

Software game is a kind of application that is used not only for entertainment, but also for serious purposes that can be applicable to different domains such as education, business, and health care. Multidisc...

Correlating automatic static analysis and mutation testing: towards incremental strategies

Traditionally, mutation testing is used as test set generation and/or test evaluation criteria once it is considered a good fault model. This paper uses mutation testing for evaluating an automated static anal...

A multi-objective test data generation approach for mutation testing of feature models

Mutation approaches have been recently applied for feature testing of Software Product Lines (SPLs). The idea is to select products, associated to mutation operators that describe possible faults in the Featur...

An extended global software engineering taxonomy

In Global Software Engineering (GSE), the need for a common terminology and knowledge classification has been identified to facilitate the sharing and combination of knowledge by GSE researchers and practition...

A systematic process for obtaining the behavior of context-sensitive systems

Context-sensitive systems use contextual information in order to adapt to the user’s current needs or requirements failure. Therefore, they need to dynamically adapt their behavior. It is of paramount importan...

Distinguishing extended finite state machine configurations using predicate abstraction

Extended Finite State Machines (EFSMs) provide a powerful model for the derivation of functional tests for software systems and protocols. Many EFSM based testing problems, such as mutation testing, fault diag...

Extending statecharts to model system interactions

Statecharts are diagrams comprised of visual elements that can improve the modeling of reactive system behaviors. They extend conventional state diagrams with the notions of hierarchy, concurrency and communic...

On the relationship of code-anomaly agglomerations and architectural problems

Several projects have been discontinued in the history of the software industry due to the presence of software architecture problems. The identification of such problems in source code is often required in re...

An approach based on feature models and quality criteria for adapting component-based systems

Feature modeling has been widely used in domain engineering for the development and configuration of software product lines. A feature model represents the set of possible products or configurations to apply i...

Patch rejection in Firefox: negative reviews, backouts, and issue reopening

Writing patches to fix bugs or implement new features is an important software development task, as it contributes to raise the quality of a software system. Not all patches are accepted in the first attempt, ...

Investigating probabilistic sampling approaches for large-scale surveys in software engineering

Establishing representative samples for Software Engineering surveys is still considered a challenge. Specialized literature often presents limitations on interpreting surveys’ results, mainly due to the use o...

Characterising the state of the practice in software testing through a TMMi-based process

The software testing phase, despite its importance, is usually compromised by the lack of planning and resources in industry. This can risk the quality of the derived products. The identification of mandatory ...

Self-adaptation by coordination-targeted reconfigurations

A software system is self-adaptive when it is able to dynamically and autonomously respond to changes detected either in its internal components or in its deployment environment. This response is expected to ensu...

Templates for textual use cases of software product lines: results from a systematic mapping study and a controlled experiment

Use case templates can be used to describe functional requirements of a Software Product Line. However, to the best of our knowledge, no efforts have been made to collect and summarize these existing templates...

F3T: a tool to support the F3 approach on the development and reuse of frameworks

Frameworks are used to enhance the quality of applications and the productivity of the development process, since applications may be designed and implemented by reusing framework classes. However, frameworks ...

NextBug: a Bugzilla extension for recommending similar bugs

Due to the characteristics of the maintenance process followed in open source systems, developers are usually overwhelmed with a great amount of bugs. For instance, in 2012, approximately 7,600 bugs/month were...

Assessing the benefits of search-based approaches when designing self-adaptive systems: a controlled experiment

The well-orchestrated use of distilled experience, domain-specific knowledge, and well-informed trade-off decisions is imperative if we are to design effective architectures for complex software-intensive syst...

Revealing influence of model structure and test case profile on the prioritization of test cases in the context of model-based testing

Test case prioritization techniques aim at defining an order of test cases that favor the achievement of a goal during test execution, such as revealing failures as earlier as possible. A number of techniques ...

A metrics suite for JUnit test code: a multiple case study on open source software

The code of JUnit test cases is commonly used to characterize software testing effort. Different metrics have been proposed in literature to measure various perspectives of the size of JUnit test cases. Unfort...

Designing fault-tolerant SOA based on design diversity

Over recent years, software developers have been evaluating the benefits of both Service-Oriented Architecture (SOA) and software fault tolerance techniques based on design diversity. This is achieved by creat...

Method-level code clone detection through LWH (Light Weight Hybrid) approach

Many researchers have investigated different techniques to automatically detect duplicate code in programs exceeding thousand lines of code. These techniques have limitations in finding either the structural o...

The problem of conceptualization in god class detection: agreement, strategies and decision drivers

The concept of code smells is widespread in Software Engineering. Despite the empirical studies addressing the topic, the set of context-dependent issues that impacts the human perception of what is a code sme...

  • Editorial Board
  • Sign up for article alerts and news from this journal

Software Design and Architecture The once and future focus of software engineering

Ieee account.

  • Change Username/Password
  • Update Address

Purchase Details

  • Payment Options
  • Order History
  • View Purchased Documents

Profile Information

  • Communications Preferences
  • Profession and Education
  • Technical Interests
  • US & Canada: +1 800 678 4333
  • Worldwide: +1 732 981 0060
  • Contact & Support
  • About IEEE Xplore
  • Accessibility
  • Terms of Use
  • Nondiscrimination Policy
  • Privacy & Opting Out of Cookies

A not-for-profit organization, IEEE is the world's largest technical professional organization dedicated to advancing technology for the benefit of humanity. © Copyright 2024 IEEE - All rights reserved. Use of this web site signifies your agreement to the terms and conditions.

Understanding peer review of software engineering papers

  • Published: 17 July 2021
  • Volume 26 , article number  103 , ( 2021 )

Cite this article

  • Neil A. Ernst   ORCID: orcid.org/0000-0001-5992-2366 1 ,
  • Jeffrey C. Carver   ORCID: orcid.org/0000-0002-7824-9151 2 ,
  • Daniel Mendez   ORCID: orcid.org/0000-0003-0619-6027 3 , 4 &
  • Marco Torchiano   ORCID: orcid.org/0000-0001-5328-368X 5  

655 Accesses

6 Citations

2 Altmetric

Explore all metrics

Peer review is a key activity intended to preserve the quality and integrity of scientific publications. However, in practice it is far from perfect.

We aim at understanding how reviewers, including those who have won awards for reviewing, perform their reviews of software engineering papers to identify both what makes a good reviewing approach and what makes a good paper.

We first conducted a series of interviews with recognised reviewers in the software engineering field. Then, we used the results of those interviews to develop a questionnaire used in an online survey and sent out to reviewers from well-respected venues covering a number of software engineering disciplines, some of whom had won awards for their reviewing efforts.

We analyzed the responses from the interviews and from 175 reviewers who completed the online survey (including both reviewers who had won awards and those who had not). We report on several descriptive results, including: Nearly half of award-winners (45%) are reviewing 20+ conference papers a year, while 28% of non-award winners conduct that many. The majority of reviewers (88%) are taking more than two hours on journal reviews. We also report on qualitative results. Our findings suggest that the most important criteria of a good review is that it should be factual and helpful, which ranked above others such as being detailed or kind. The most important features of papers that result in positive reviews are a clear and supported validation, an interesting problem, and novelty. Conversely, negative reviews tend to result from papers that have a mismatch between the method and the claims and from papers with overly grandiose claims. Further insights include, if not limited to, that reviewers view data availability and its consistency as being important or that authors need to make their contribution of the work very clear in their paper.

Conclusions

Based on the insights we gained through our study, we conclude our work by compiling a proto-guideline for reviewing. One hope we associate with our work is to contribute to the ongoing debate and contemporary effort to further improve our peer review models in the future.

This is a preview of subscription content, log in via an institution to check access.

Access this article

Price includes VAT (Russian Federation)

Instant access to the full article PDF.

Rent this article via DeepDyve

Institutional subscriptions

research paper on software engineering pdf

Similar content being viewed by others

research paper on software engineering pdf

Developers perception of peer code review in research software development

Nasir U. Eisty & Jeffrey C. Carver

research paper on software engineering pdf

Rapid Reviews in Software Engineering

research paper on software engineering pdf

An Empirical Analysis of Newcomers’ Contributions to Software-Engineering Conferences

http://tiny.cc/rosefest

A good tutorial on data disclosure when using a double-blind review process is provided by Daniel Graziotin: https://tinyurl.com/DBDisclose .

See, e.g., artifact evaluation track of ICSE 2021 https://doi.org/10.6084/m9.gshare.14123639 or the open science initiative of the EMSE journal https://github.com/emsejournal/openscience

https://github.com/acmsigsoft/EmpiricalStandards

https://github.com/researchart/patterns/blob/master/standards/artifact.md

http://www.icse-conferences.org/reports.html

https://neuripsconf.medium.com/what-we-learned-from-neurips-2020-reviewing-process-e24549eea38f

https://cs.gmu.edu/~offutt/stvr/17-3-sept2007.html

https://peerj.com/articles/cs-111/reviews/

https://openreview.net/forum?id=rklXaoAcFX&noteId=HyeF-4_9hm

https://doi.org/10.6084/m9.gshare.5086357.v1

https://www.slideshare.net/aserebrenik/peer-reviews-119010210

https://reviewqualitycollector.org

http://www.inf.fu-berlin.de/w/SE/ReviewQualityCollectorHome

http://cscw.acm.org/2019/CSCW-2020-changes.html

https://conf.researchr.org/track/icse-2021/icse-2021-papers#Call-for-Papers

Drubin DG (2011) Any jackass can trash a manuscript, but it takes good scholarship to create one (how MBoC promotes civil and constructive peer review). Mol Biol Cell 22(5):525–527. https://doi.org/10.1091/mbc.e11-01-0002

Article   Google Scholar  

Fernandes JM (2014) Authorship trends in software engineering. Scientometrics 101(1):257–271. https://doi.org/10.1007/s11192-014-1331-6

Horbach SPJM, Halffman W (2018) The ability of different peer review procedures to ag problematic publications. Scientometrics 118(1):339–373. https://doi.org/10.1007/s11192-018-2969-2

Kitchenham B, Peeger SL (2002) Principles of survey research: part 1-6. ACM SIGSOFT Softw Eng Notes 27(5):17–20

MacAuley D (2012) The role of the manuscript assessor. In: How to write a paper, chap. 16. https://doi.org/10.1002/9781118488713.ch16 . Wiley, pp 102–114

Mathew G, Agrawal A, Menzies T (2019) Finding trends in software research. IEEE Trans Softw Eng :1–1. https://doi.org/10.1109/tse.2018.2870388

Mendez D, Graziotin D, Wagner S, Seibold H (2020) Open science in software engineering. In: Felderer M, Travassos G-H (eds) Contemporary empirical methods in software engineering. arXiv: 1908.05899 . Springer

Nierstrasz O (1998) Identify the champion. Pattern Languages of Programming (PLoP). WUCS-98-25

Ozkaya I (2021) Protecting the health and longevity of the peer-review process in the software engineering community. IEEE Softw 38(1):3–6. https://doi.org/10.1109/ms.2020.3028681

Peterson DAM (2020) Dear reviewer 2: Go F’ Yourself. Soc Sci Q. https://doi.org/10.1111/ssqu.12824

Petre M, et al. (2020) Reviewing computing education papers. In: Proceedings of the 2020 ACM conference on innovation and technology in computer science education. https://doi.org/10.1145/3341525.3394994 . ACM

Prechelt L, Graziotin D, Mendez D (2018) A community’s perspective on the status and future of peer review in software engineering. Inf Softw Technol 95:75–85. https://doi.org/10.1016/j.infsof.2017.10.019

Price E (2014) The NIPS Experiment. http://blog.mrtz.org/2014/12/15/thenipsexperiment.html . Online; accessed August 2020

Ragone A, Mirylenka K, Casati F, Marchese M (2013) On peer review in computer science: analysis of its effectiveness and suggestions for improvement. Scientometrics 97(2):317– 356. https://doi.org/10.1007/s11192-013-1002-z

Ralph P, Robbes R (2020) The ACM SIGSOFT paper and peer review quality initiative. ACM SIGSOFT Softw Eng Notes 45(2):17–18. https://doi.org/10.1145/3385678.3385681

Schimel J (2011) Writing science: how to write papers that get cited and proposals that get funded. Oxford University Press, Oxford

Google Scholar  

Seeber M, Bacchelli A (2017) Does single blind peer review hinder newcomers?. Scientometrics 113(1):567–585. https://doi.org/10.1007/s11192-017-2264-7

Shaw M (2003) Writing good software engineering research papers: minitutorial. In: Proceedings of the ACM/IEEE international conference on software engineering, pp 726–736

Shepperd M, Ajienka N, Counsell S (2018) The role and value of replication in empirical software engineering results. Inf Softw Technol 99:120–132. https://doi.org/10.1016/j.infsof.2018.01.006

Smith AJ (1990) The task of the referee. Computer 23(4):65– 71

Smith E, Loftin R, Murphy-Hill E, Bird C, Zimmermann T (2013) Improving developer participation rates in surveys. In: CHASE workshop at ICSE

Soldani J, Kuhrmann M, Pfahl D (2020) Pains and gains of peer-reviewing in software engineering. ACM SIGSOFT Softw Eng Notes 45(1):12–13. https://doi.org/10.1145/3375572.3375575

Spier R (2002) The history of the peer-review process. Trends Biotechnol 20 (8):357–358. https://doi.org/10.1016/s0167-7799(02)01985-6

Squazzoni F, Brezis E, Marušić A (2017) Scientometrics of peer review. Scientometrics 113(1):501–502. https://doi.org/10.1007/s11192-017-2518-4.

Storey M-A, Ernst NA, Williams C, Kalliamvakou E (2019) The who, what, how of software engineering research: a socio-technical framework. arXiv: 1905.1284

Tennant JP, et al. (2017) A multi-disciplinary perspective on emergent and future innovations in peer review. In: F1000Research. https://doi.org/10.12688/f1000research.12037.3 , vol 6, p 1151

Terrell J, Kofink A, Middleton J, Rainear C, Murphy-Hill E, Parnin C, Stallings J (2017) Gender differences and bias in open source: pull request acceptance of women versus men. Peer J Comput Sci 3:e111. https://doi.org/10.7717/peerj-cs.111

Theisen C, Dunaiski M, Williams L, Visser W (2017) Writing good software engineering research papers: revisited. In: Proceedings of the ACM/IEEE international conference on software engineering. https://doi.org/10.1109/icse-c.2017.51

Tomkins A, Zhang M, Heavlin WD (2017) Reviewer bias in single- versus double-blind peer review. Proc Natl Acad Sci 114(48):12708–12713. https://doi.org/10.1073/pnas.1707323114

Tung AKH (2006) Impact of double blind reviewing on SIGMOD publication. ACM SIGMOD Record 35 (3):6–7. https://doi.org/10.1145/1168092.1168093

Winslett M, Braganholo V (2016) H V Jagadish speaks out on PVLDB, CoRR and data-driven research. In: SIGMOD Record 42.2

Wolfram D, Wang P, Hembree A, Park H (2020) Open peer review: promoting transparency in open science. Scientometrics 125(2):1033–1051. https://doi.org/10.1007/s11192-020-03488-4

Zerbe WJ, Paulhus DL (1987) Socially desirable responding in organizational behavior: a reconception. Acad Manag Rev 12(2):250. https://doi.org/10.2307/258533

Zong Q, Xie Y, Liang J (2020) Does open peer review improve citation count? Evidence from a propensity score matching analysis of PeerJ. Scientometrics 125 (1):607–623. https://doi.org/10.1007/s11192-020-03545-y.

Download references

Author information

Authors and affiliations.

University of Victoria, Victoria, Canada

Neil A. Ernst

University of Alabama, Tuscaloosa, AL, USA

Jeffrey C. Carver

Blekinge Institute of Technology, Karlskrona, Sweden

Daniel Mendez

fortiss GmbH, Munich, Germany

Politecnico di Torino, Turin, Italy

Marco Torchiano

You can also search for this author in PubMed   Google Scholar

Corresponding author

Correspondence to Neil A. Ernst .

Additional information

Communicated by: Romain Robbes

Publisher’s note

Springer Nature remains neutral with regard to jurisdictional claims in published maps and institutional affiliations.

Rights and permissions

Reprints and permissions

About this article

Ernst, N.A., Carver, J.C., Mendez, D. et al. Understanding peer review of software engineering papers. Empir Software Eng 26 , 103 (2021). https://doi.org/10.1007/s10664-021-10005-5

Download citation

Accepted : 16 June 2021

Published : 17 July 2021

DOI : https://doi.org/10.1007/s10664-021-10005-5

Share this article

Anyone you share the following link with will be able to read this content:

Sorry, a shareable link is not currently available for this article.

Provided by the Springer Nature SharedIt content-sharing initiative

  • Peer review
  • Find a journal
  • Publish with us
  • Track your research

Academia.edu no longer supports Internet Explorer.

To browse Academia.edu and the wider internet faster and more securely, please take a few seconds to  upgrade your browser .

Enter the email address you signed up with and we'll email you a reset link.

  • We're Hiring!
  • Help Center

paper cover thumbnail

Software Engineering Research

Profile image of Jorge Morato

2014, Concepts, Methodologies, Tools, and Applications

Related Papers

Gonzalo Génova

The classical scientific method has been settled through the last centuries as a cyclic, iterative process of observation, hypothesis formulation, and confirmation/refutation of hypothesis through experimentation. This “experimental scientific method” was mainly developed in the context of natural sciences dealing with the physical world, such as Mechanics, Thermodynamics, Electromagnetism, Chemistry and so on. But when we try to apply this classical view of the scientific method to the various branches of Computer Science and Computer Engineering, among which Software Engineering, we find two kinds of obstacles. First, Computer Science is rooted both in formal sciences such as Mathematics and experimental sciences such as Physics, therefore an excessive emphasis on the experimental side is not appropriate to give a full account of this kind of scientific activity. Second, the production of software systems has to deal not only with the behavior of complex physical systems such as c...

research paper on software engineering pdf

Gonzalo Génova , Jorge Morato

IASET US , Kateryna Lavryshcheva

Define the scientifical concepts and fundamental basis of Software Engineering (SE). The scientifically concepts are modules, objects, programs, systems and processes of design program systems. The fundamental basic of the SE are: assembly method of modules; disciplines SE (scientific, engineering, economic, management, etc.); paradigms of programming modules, objects, components, etc.; automatization of Life Cycle (ISO/IEC 12207); theory of technological and production lines, factory programs and App Fabric; new logical-mathematical theory of object-component modeling graph of object model (OM); verification of OM and MF (feature model) and testing ready elements of system and evaluation reliability and quality of systems product. Tool support of scientific basis was represented on the website http://7dragons.ru/ru.

Jim Herbsleb

Abstract From 25.01. 04 to 29.01. 04, the Dagstuhl Seminar 04051``Perspectives Workshop: Empirical Theory and the Science of Software Engineering''was held in the International Conference and Research Center (IBFI), Schloss Dagstuhl. During the seminar, several participants presented their current research, and ongoing work and open problems were discussed. Abstracts of the presentations given during the seminar as well as abstracts of seminar results and ideas are put together in this paper.

Information and Software Technology

Claes Wohlin

Empirical Software Engineering

Norman Fenton

Natalia Juzgado

Javier Andrade

Despite being two very closely linked things, hardware and software have evolved very differently. In actual fact, while hardware evolution has been exponential, software has evolved linearly. One of the fundamental reasons for this mismatch between hardware development and software development is that hardware development is supported by engineering based on science whose scientific theory is very well established, whereas software development is not. The goal of the present work is the analysis of, not only software historic development, but also the current theoretical approaches for software development. The results achieved will be used for proposing new research lines that might help this discipline to advance in the scientific field. It should be then possible to establish the foundations that might enable software advance similarly as hardware does.

IEEE Software

Maya Daneva

General theories of software engineering must balance between providing full under-standing of a single case and providing partial understanding of many cases. In this paper we argue that for theories to be useful in practice, they should give sufficient understanding of a sufficiently large class of cases, without having to be universal or complete. We provide six strategies for developing such theories of the middle range. In lab-to-lab strategies, theories of laboratory phenomena are developed and generalized to other laboratory phenomena. This is a characteristic strategy for basic science. In lab-to-field strategies, theories are developed of artifacts that first operate under idealized laboratory conditions, which are then scaled up until they can operate under uncontrolled field conditions. This is the characteristic strategy for the engineering sciences. In case-based strategies, we generalize about components of real-world cases, that are supposed to exhibit less variation than the cases as a whole. In sample-based strategies, we generalize about the aggregate behavior of samples of cases, which can exhibit patterns not visible at the case level. We discuss three examples of sample-based strategies. Throughout the paper, we use examples of theories and generalization strategies from software engineering to illustrate our analysis. The paper concludes with a discussion of related work and implications for empirical software engineering research.

RELATED PAPERS

Jean-Luc Chatelain

Chemical Ecology of Plants: Allelopathy in Aquatic and Terrestrial Ecosystems

Francisco Antonio Macías Domínguez

Anderson Moncada

Pere Verdes Pijuan

Mahesh Chandra Luitel

ivone silva

RDBCI: Revista Digital de Biblioteconomia e Ciência da Informação

Leandro Innocentini Lopes de Faria

Consolate Kaswera

TELKOMNIKA JOURNAL , Geetha Subbiah , Prasanalakshmi Balaji

Physical Chemistry Chemical Physics

Piotr Paluch

Pandit Deendayal Petroleum University

Hitesh Gujarati

World Journal of Microbiology and Biotechnology

Pranamita Kunda

Journal of Applied Physiology

Thomas Taylor-clark

The Journals of Gerontology: Series B

Larissa McKetton

Ciência Rural

Paulo Rogério B. de Souza

Hans Klapdor-Kleingrothaus

GLOBAL JOURNAL FOR RESEARCH ANALYSIS

anjay kumar

Geological Survey of Denmark and Greenland Bulletin

Kim Esbensen

Journal of Perioperative Practice

Christina Lydon

LJMU毕业证书 利物浦约翰摩尔斯大学毕业证

Parkinsonism & Related Disorders

May Beydoun

Plant Physiology

Jerry Cohen

Shana Poplack

Teksty Drugie

Tomasz Szymon Markiewka

  •   We're Hiring!
  •   Help Center
  • Find new research papers in:
  • Health Sciences
  • Earth Sciences
  • Cognitive Science
  • Mathematics
  • Computer Science
  • Academia ©2024

IMAGES

  1. (PDF) Writing good software engineering research papers

    research paper on software engineering pdf

  2. (PDF) Qualitative research in software engineering

    research paper on software engineering pdf

  3. (PDF) Highly-cited papers in software engineering: The top-100

    research paper on software engineering pdf

  4. (PDF) Guidelines Based Software Engineering for Developing Software

    research paper on software engineering pdf

  5. (PDF) Software engineering

    research paper on software engineering pdf

  6. (PDF) A Review on Search Based Software Engineering

    research paper on software engineering pdf

VIDEO

  1. Software Maintenance (CS)

  2. Software Engineering BCA question Paper 2022 important paper

  3. Final Term Paper Software Engineering II

  4. Research Paper (Software Security Specifications and Design)

  5. 22413 software engineering question paper 2022/23 TY-CO 4th sem MSBTE Board exam question paper

  6. Requirements Engineering (CS)

COMMENTS

  1. (PDF) Current Trends in Software Engineering Research

    ABSTRACT. Software engineering is dynamic disciplines that have continuous growth in research in identifying. new methods, tools and methodologies that have cause vast improvement in software ...

  2. Journal of Software Engineering Research and Development

    They wanted to define values and basic principles for better software development. On top of being brought into focus, the ... Philipp Hohl, Jil Klünder, Arie van Bennekum, Ryan Lockard, James Gifford, Jürgen Münch, Michael Stupperich and Kurt Schneider. Journal of Software Engineering Research and Development 2018 6 :15.

  3. An Analysis of Research in Software Engineering:

    This paper presents a software-aided method for assessment and trend analysis, which can be used in software engineering as well as other research fields in computer science (or other disciplines). The method proposed in this paper is modular and automated compared with the method in prior studies [7, 10-22, 2].

  4. PDF Deep Learning in Software Engineering

    At last, 63 research papers are remained. We take these papers as seeds to search their references and citations. If a new SE research paper about deep learning is found, we recursively examine the new paper. Finally, another 35 research papers are found. Hence, we collect in total 98 published or accepted research papers for analysis.

  5. Software Engineering's Top Topics, Trends, and Researchers

    For this theme issue on the 50th anniversary of software engineering (SE), Redirections offers an overview of the twists, turns, and numerous redirections seen over the years in the SE research literature. Nearly a dozen topics have dominated the past few decades of SE research—and these have been redirected many times. Some are gaining popularity, whereas others are becoming increasingly ...

  6. PDF Research Software Engineering in 2030

    Research Software Engineering in 2030 Daniel S. Katz NCSA & CS & ECE & iSchool University of Illinois Urbana Champaign Urbana, IL, USA ORCID: 0000-0001-5934-7525 ... ORCID: 0000-0002-6809-5195 Abstract—This position paper for an invited talk on the "Fu-ture of eScience" discusses the Research Software Engineering Movement and where it ...

  7. PDF Software Engineering for Data Analytics

    SOFTWARE ENGINEERING (SE) is currently meeting the data-cen-tric discipline of artificial intelli-gence (AI), machine learning (ML), and big data. Almost on a daily ba-sis, we hear about self-driving cars and drones enabled by AI, and com-panies hiring data scientists. Data analytics (DA) is in high demand, and the growth of DA- related hir-ing ...

  8. PDF Writing Good Software Engineering Research Papers

    Minitutorial. Mary Shaw. Carnegie Mellon University [email protected]. Abstract. Software engineering researchers solve problems of several different kinds. To do so, they produce several different kinds of results, and they should develop appropriate evidence to validate these results. They often report their research in conference papers.

  9. Automating Software Re-engineering

    Download conference paper PDF. 1 Introduction. Software Engineering as a discipline and, in particular, as a research field within Computer Science, is still mainly focused on methods, techniques, processes, and tools to develop software from scratch. ... most of all, practically relevant, new direction of research: Automating Software Re ...

  10. software engineering Latest Research Papers

    End To End . Predictive Software. The paper examines the principles of the Predictive Software Engineering (PSE) framework. The authors examine how PSE enables custom software development companies to offer transparent services and products while staying within the intended budget and a guaranteed budget.

  11. PDF Software Engineering for AI-Based Systems: A Survey

    synthesized knowledge on Software Engineering (SE) approaches for building, operating, and maintaining AI-based systems. To collect. and analyze state-of-the-art knowledge about SE for AI-based systems, we conducted a systematic mapping study. We considered. 248 studies published between January 2010 and March 2020.

  12. Current and Future Challenges of Software Engineering for Services and

    This paper summarizes the challenges that the Software Engineering for Services and Applications (SE4SA) cluster is considering as relevant. ... coding patterns, requirements, user behaviours, user profiles, etc. Research challenges for software engineering in this direction include novel tools employing techniques of machine learning and data ...

  13. PDF 1 Introduction to Software Engineering

    1.1. Software and Software Engineering Let us first discuss what we mean by software in the context of software engineering. Software is not merely a collection of computer programs. There is a distinction between a program and a programming systems product. A program is generally complete in itself, and is generally used only by the ...

  14. Software Design and Architecture The once and future focus of software

    The design of software has been a focus of software engineering research since the field's beginning. This paper explores key aspects of this research focus and shows why design will remain a principal focus. The intrinsic elements of software design, both process and product, are discussed: concept formation, use of experience, and means for representation, reasoning, and directing the design ...

  15. Chapter 10: The Application of Artificial Intelligence in Software

    Software, since its earliest stages, aimed to help humans automate processes that require a certain level of 'intelligence'. The process of building software (i.e. Software Engineering), remains primarily a human activity. Within computer science, the field of Software Engineering (SE) is the dominating industrial field [2].

  16. Understanding peer review of software engineering papers

    Techniques such as PDF annotation on a tablet were frequently used by more expert reviewers and may facilitate the review process. ... Shaw M (2003) Writing good software engineering research papers: minitutorial. In: Proceedings of the ACM/IEEE international conference on software engineering, pp 726-736.

  17. (PDF) Software Engineering Research

    View PDF. Software engineering research: the need to strengthen and strengthen and strengthen and broaden the classical broaden the classical scientific method scientific method. Gonzalo Génova, Jorge Morato. Download Free PDF. View PDF. THE SCIENTIFIC BASIS OF SOFTWARE ENGINEERING. IASET US, Kateryna Lavryshcheva.

  18. Papers with Code

    In this paper, we present an empirical study to characterize the research artifacts in SE publications. Specifically, we manually collect 1,487 artifacts from all 2,196 papers published in top-tier SE conferences (ASE, FSE, ICSE, and ISSTA) from 2017 to 2022. We investigate the common practices (e.g., URL location and format, storage websites ...