An Analysis of Research in Software Engineering.

The goal of this paper is to aid software engineering researchers in understanding trends in research question design, research question type, and validation approach by analyzing the abstracts of.

Read (on average) a paper a day! So you should start with these: S. Keshav, How to Read a Paper, ACM SIGCOMM Computer Communication Review, 2007 Philip W. L. Fong, Reading a Computer Science Research Paper, SIGCSE 2009 Amanda Stent, How to Read a Computer Science Research Paper, Technical Report. 6 What is research? Well, some part of it!

Empirical Software Engineering promotes the publication of industry-relevant research, to address the significant gap between research and practice. A forum for applied software engineering research with a strong empirical component. A venue for empirical results relevant to both researchers and practitioners.

What Makes Good Research in Software Engineering? Mary Shaw School of Computer Science, Carnegie Mellon University,. In this paper I attempt to make generally accepted research strategies in software en-gineering explicit by examining research in the area to identify what is widely ac- cepted in practice. 1.1 Software Technology Maturation Redwine and Riddle (5,6) reviewed a number of.

Software Engineering research for mobile apps and to draw a vision for its future. Note that we restrict to just the software engineering topics for mobile apps in this paper, and even that not exhaustively due to space restrictions (we skip topics like usability or performance engineering since an entire paper can be written on each of these.

This paper presents an overview of the field of software systems requirements engineering (RE). It describes the main areas of RE practice, and highlights some key open research issues for the future. 1 Introduction The primary measure of success of a software system is the degree to which it meets the purpose for which it was intended.

F. Brooks: No Silver Bullet—Essence and accident in software engineering (1986) 2 The familiar software project has something of this character (at least as seen by the non-technical manager), usually innocent and straightforward, but capable of becoming a monster of missed schedules, blown budgets, and flawed products. So we hear desperate.

Ranking is based on Impact Factor.Vanity press and poor-quality journals are not listed.

Workshop Aim. The aim of this workshop is to bring together researchers and practitioners to discuss the current state of Software Engineering (SE) research and Industrial Practice (IP), and advance collaboration to reduce the gap between research and practice.

Software Engineering: Principles and Practice challenges the reader to appreciate the issues, design trade-offs and teamwork required for successful software development. This new edition has been brought fully up to date, with complete coverage of all aspects of the software lifecycle and a strong focus on all the skills needed to carry out software projects on time and within budget.

A working conference on software engineering techniques, sponsored by the NATO Science Committee, was held from the 27th to 31st October 1969, near Rome, Italy. The conference was intended as a direct sequel to the NATO conference on software engineering held at Garmisch, Germany, from 7th to 11th October 1968. About sixty people.

Digital Library. The SEI Digital Library provides access to more than 5,000 documents from three decades of research into best practices in software engineering. These documents include technical reports, presentations, webinars, podcasts and other materials searchable by user-supplied keywords and organized by topic, publication type, publication year, and author.