SOFTWARE-PRACTICE & EXPERIENCE

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.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 CategoriesSubmitted 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). 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).ReadershipSoftware engineers and designers · systems programmers and analysts · computer science educators and students

SOFTWARE-PRACTICE & EXPERIENCE期刊中文简介

软件：实践和经验是一种国际上受尊重和严格推荐的工具，用于传播和讨论具有新的和成熟的软件系统和应用技术和工具的实践经验。发表论文的关键标准是，它做出了一项新的贡献，其他从事软件设计和/或实现的研究人员和实践者可能从中受益。我们的读者非常感兴趣的软件和系统设计和实现主题涵盖了对已建立和迅速出现的主题的探索，这些主题包括但不限于：分布式计算范式：服务、云、雾、边缘。特定领域的计算：航空航天、教育、金融、医疗、交通、电力。模型驱动开发：模型转换，自动代码生成。网络：移动计算，物联网。操作系统、运行时支持和虚拟化。程序设计语言和编译器。重复使用：基于组件、模式、产品线。定期提交的捐款：新颖、经过严格验证的技术/工具，有助于解决实际软件设计或编程问题。已完成软件项目的详细说明，可作为同一领域未来工作的“如何做”模型。关于新兴软件设计或编程技术的简短交流，可应用于各种领域。软件设计或编程技术/工具的独特对比分析。正如该杂志的名字所暗示的，重点是软件的实践和经验。文章中所包含的理论或数学内容有助于证明贡献和理解的严格基础，最终导致更好的实际系统的发展。该杂志并没有试图涵盖软件和系统工程的所有方面。侧重于软件过程、软件开发方法、项目管理以及设计和实现以外的工程活动（例如，需求工程、验证和验证中的主题）的手稿不在本杂志的范围之内。请考虑将这些主题的手稿提交给其他期刊，如《软件杂志：进化与过程》、《软件过程杂志：改进与实践》或《软件测试、验证与可靠性杂志》。在这样一个不断演变的领域，杂志的主题焦点必然是流动的。如果不清楚你的手稿是否适合出版，作者可以1）浏览期刊以考虑他们的工作如何与以前的论文相匹配2）检查论文的参考文献以确定提交内容与期刊之间的书目链接或3）联系编辑。文章类别提交的文章通常属于以下五类之一。·研究文章——包含与软件设计和实现直接相关的原始结果；·扩展会议论文-这将是一篇研究文章，但早期版本已经作为会议论文发表；提交此论文的特殊规则适用（请参阅作者指南了解详细信息）。·调查报告——通常会对适合期刊的主题进行简要介绍，并在介绍之后对该主题迄今为止的工作进行批判性分析；或者，调查报告可以采用计算文献中未记载的及时技术教程的形式。·经验报告——可采用以下形式：（1）案例研究，或（2）已完成软件系统项目的详细说明，或（3）关于在学术和工业环境中开发和/或评估软件和软件系统的工具和方法的实际经验的报告。·简短的交流——可以引入一个快速发展的新主题，并提供关于该主题的早期结果；与常规文章相比，它将被给予更高的出版优先级。文章的长度从简短的交流（长达10页）到对大量软件进行全面处理所需的长度（特别是长达40页）。文章的长度从简短的交流（长达10页）到对大量软件进行全面处理所需的长度（特别是长达40页）。读者群软件工程师和设计师·系统程序员和分析师·计算机科学教育家和学生