CLOSED – Actionable Analytics in Software Engineering – Call for Papers

Calls for Papers3 min read
Facebooktwitterredditlinkedinmail

Submission deadline: CLOSED

Publication: Jan./Feb. 2018

Does software analytics work? Software’s increasingly critical roles in modern society intensify the need for better and faster software decision making. Although intensive research on software analytics has been underway for nearly a decade, a repeated complaint in that field is that industrial practitioners have difficulty applying the results generated from data science.

This theme issue aims to document software analytics’ value. Our goal is a catalog of success (or failure) stories in which analytics proved actionable and useful, in some significant way, in an organization. So, we seek industrial experience reports and contributions in modeling and documenting specific, repeatable software development actions that have produced predictable, proven results (positive or negative) related to the impacted development flows’ productivity, efficiency, or agility.

Accordingly, all submissions should be in this format:

  • a description of specific actionable metrics or advice for developers based on software analytics and
  • a summary of the analytics’ impact on an organization. That impact must be substantive.

We do not want submissions that only

  • propose new prediction models with evaluated performance improvement results over existing models,
  • present visualization dashboards with no practical evaluation, or
  • document the status quo.

Specifically, we ask for standard and two-page industrial reports. Example topics include, but aren’t limited to, the following:

  • “State of the art” experience reports. These include case studies or industrial success stories on adopting actionable analytics in software projects, with reflections on the reasons for success. We’re also looking for reports identifying specific areas (for example, a type of artifact, stakeholder, or development process) in which software analytics is particularly useful (or useless) in supporting decisions.
  • New metrics, algorithms, and models that better describe, measure, and mine uncovered information in specific, repeatable software actions; that link software actions with business benefits (for example, improved estimation, reduced defect density, improved delivery rate, or decreased cost per work unit); or that analyze, compare, and recommend analytically based actions for improving software project development, maintenance, and management.
  • Creative analytics methods for visualizing communication interactions within data to business users; for exploring organizational change, including interactions between that change and analytics; and for interpreting complex models of effects in data to users.

For two-page papers, the first page should report the industry context, analytics, successes or failures, lessons learned, and so on. The second page should describe through one or more pictures the tool (or infrastructure) that supports the use of the analytics discussed in the first page.

Theme Issue Guest Editors

  • Tim Menzies, North Carolina State University
  • Ye Yang, Stevens Institute of Technology
  • Jairus Hihn, NASA Jet Propulsion Laboratory
  • Davide Falessi, California Polytechnic State University

Submission Guidelines

Manuscripts must not exceed 3,000 words including figures and tables, which count for 250 words each. Submissions exceeding these limits might be rejected without refereeing. Articles deemed within the theme and scope will be peer reviewed and are subject to editing for magazine style, clarity, organization, and space. We reserve the right to edit the title of all submissions. Be sure to include the name of the theme issue for which you’re submitting.

Articles should have a practical orientation and be written in a style accessible to practitioners. Overly complex, purely research-oriented or theoretical treatments aren’t appropriate. Articles should be novel. IEEE Software doesn’t republish material published previously in other venues, including other periodicals and formal conference or workshop proceedings, whether previous publication was in print or electronic form. For more information, contact the guest editors at software1b-2018@computer.org.

 

For general author guidelines: www.computer.org/software/author.htm

For submission details: software@computer.org

To submit an article: https://mc.manuscriptcentral.com/sw-cs

 
IEEE Software

IEEE Software‘s mission is to be the best source of reliable, useful, peer-reviewed information for leading software practitioners—the developers and managers who want to keep up with rapid technology change. The authority on translating software theory into practice, this bimonthly magazine positions itself between pure research and pure practice, transferring ideas, methods, and experiences among researchers and engineers. Peer-reviewed articles and columns by real-world experts illuminate all aspects of the industry, including process improvement, project management, development tools, software maintenance, Web applications and opportunities, testing, usability, and much more.