軟件：實踐和經(jīng)驗是一種國際上受尊重和嚴格推薦的工具，用于傳播和討論具有新的和成熟的軟件系統(tǒng)和應用技術和工具的實踐經(jīng)驗。發(fā)表論文的關鍵標準是，它做出了一項新的貢獻，其他從事軟件設計和/或實現(xiàn)的研究人員和實踐者可能從中受益。我們的讀者非常感興趣的軟件和系統(tǒng)設計和實現(xiàn)主題涵蓋了對已建立和迅速出現(xiàn)的主題的探索，這些主題包括但不限于：分布式計算范式：服務、云、霧、邊緣。特定領域的計算：航空航天、教育、金融、醫(yī)療、交通、電力。模型驅動開發(fā)：模型轉換，自動代碼生成。網(wǎng)絡：移動計算，物聯(lián)網(wǎng)。操作系統(tǒng)、運行時支持和虛擬化。程序設計語言和編譯器。重復使用：基于組件、模式、產(chǎn)品線。定期提交的捐款：新穎、經(jīng)過嚴格驗證的技術/工具，有助于解決實際軟件設計或編程問題。已完成軟件項目的詳細說明，可作為同一領域未來工作的“如何做”模型。關于新興軟件設計或編程技術的簡短交流，可應用于各種領域。軟件設計或編程技術/工具的獨特對比分析。正如該雜志的名字所暗示的，重點是軟件的實踐和經(jīng)驗。文章中所包含的理論或數(shù)學內(nèi)容有助于證明貢獻和理解的嚴格基礎，最終導致更好的實際系統(tǒng)的發(fā)展。該雜志并沒有試圖涵蓋軟件和系統(tǒng)工程的所有方面。側重于軟件過程、軟件開發(fā)方法、項目管理以及設計和實現(xiàn)以外的工程活動（例如，需求工程、驗證和驗證中的主題）的手稿不在本雜志的范圍之內(nèi)。請考慮將這些主題的手稿提交給其他期刊，如《軟件雜志：進化與過程》、《軟件過程雜志：改進與實踐》或《軟件測試、驗證與可靠性雜志》。在這樣一個不斷演變的領域，雜志的主題焦點必然是流動的。如果不清楚你的手稿是否適合出版，作者可以1）瀏覽期刊以考慮他們的工作如何與以前的論文相匹配2）檢查論文的參考文獻以確定提交內(nèi)容與期刊之間的書目鏈接或3）聯(lián)系編輯。文章類別提交的文章通常屬于以下五類之一。·研究文章——包含與軟件設計和實現(xiàn)直接相關的原始結果；·擴展會議論文-這將是一篇研究文章，但早期版本已經(jīng)作為會議論文發(fā)表；提交此論文的特殊規(guī)則適用（請參閱作者指南了解詳細信息）。·調查報告——通常會對適合期刊的主題進行簡要介紹，并在介紹之后對該主題迄今為止的工作進行批判性分析；或者，調查報告可以采用計算文獻中未記載的及時技術教程的形式。·經(jīng)驗報告——可采用以下形式：（1）案例研究，或（2）已完成軟件系統(tǒng)項目的詳細說明，或（3）關于在學術和工業(yè)環(huán)境中開發(fā)和/或評估軟件和軟件系統(tǒng)的工具和方法的實際經(jīng)驗的報告。·簡短的交流——可以引入一個快速發(fā)展的新主題，并提供關于該主題的早期結果；與常規(guī)文章相比，它將被給予更高的出版優(yōu)先級。文章的長度從簡短的交流（長達10頁）到對大量軟件進行全面處理所需的長度（特別是長達40頁）。文章的長度從簡短的交流（長達10頁）到對大量軟件進行全面處理所需的長度（特別是長達40頁）。讀者群軟件工程師和設計師·系統(tǒng)程序員和分析師·計算機科學教育家和學生

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