Aims and Scope

Software: Practice and Experience is an internationally respected and rigorously refereed vehicle for the dissemination and discussion of practical experience with new and established techniques and tool for both software systems and applications.  The key criterion for publication of a paper is that it makes a novel contribution from which other researchers and practitioners engaged in the design and/or implementation of software might benefit. Submissions must be original manuscripts that have not been previously published and not under consideration for publication elsewhere.

Software and system design and implementation topics of strong interest to our readership span the exploration of established and rapidly emerging topics, which include but are not limited to:

       Distributed Computing Paradigms: Service, Cloud, Fog, Edge.
       Domain Specific Computing: Aerospace, Education, Finance, Healthcare, Transportation, Power.   
       Model-driven Development: Model Transformations, Automated code generation.
       Networking: Mobile computing, IoT.
       Operating Systems, Run-time Support, and Virtualization.
       Programming Languages and Compilers.
       Re-use: Component-based, Patterns, Product Lines.

Contributions regularly present:

    Novel, rigorously validated techniques/tools that aid in solving practical software design or programming problems.
    Detailed accounts of completed software projects that can serve as ‘how-to-do-it’ models for future work in the same field.
    Brief communications on emerging software design or programming technique that can be applied in a wide variety of domains. 
    Unique comparative analyses of software design or programming techniques/tools.

As the journal’s name suggests, the focus is on the practice and experience with software. The theoretical or mathematical content included in the articles serves to demonstrate the rigorous foundation of the contribution and its understanding, which ultimately leads to the development of better practical systems.

The journal does not attempt to cover all aspects of software and systems engineering.  Manuscripts with a focus on software processes, software development methodologies, project management, and engineering activities beyond design and implementation (e.g., topics in requirements engineering, validation and verification) are outside this journal’s scope. Please consider submitting manuscripts on these topics to alternative journals such as the Journal of Software: Evolution and Process, Journal of Software Process: Improvement and Practice, or the Journal of Software Testing, Verification and Reliability. 

In a constantly evolving field such as this, the journal’s topical focus is necessarily fluid. If it is unclear whether your  manuscript is appropriate for publication authors may  1) browse the journal to consider how their work fits in with prior papers 2) check the references of papers to determine a bibliographic link between the submission and the journal or 3) contact the editors.

Article Categories

Submitted articles normally fall within one of the following five categories.

·         Research Article – which contains original results that are directly relevant to software design and implementation;
·         Extended conference paper – this would be a research article, but where an early version has already been published as a conference paper; special rules apply for submitting this form of paper (please refer to the Author Guidelines for details).
·         Survey paper – which would typically provide a brief introduction to a topic appropriate for the journal and follow that introduction with a critical analysis of work to date on the topic; alternatively, a survey paper can take the form of a timely tutorial on techniques not previously documented in the computing literature.
 ·         Experience report – which might take the form of a (1) case study, or (2) a detailed account of a completed software-system project, or (3) a report on practical experience with tools and methods for development and/or evaluation of software and software systems in both academic and industrial environments.
 ·         Short Communication – which can introduce a rapidly developing new topic and provide early results on that topic; it will be given higher priority for publication than a regular article.

Articles range in length from a Short Communication (up to ten pages) to the length required to give full treatment to a substantial piece of software (exceptionally up to 40 pages). 

Readership

Software engineers and designers · systems programmers and analysts · computer science educators and students

Keywords

software implementation, software tools, compilers, run-time systems, systems programming, system software, debugging, programming techniques, algorithms, code generation