AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
Back to Blog
Indigo dc2/17/2024 ![]() ![]() Changes in the source code, trigger automated builds to analyze the The next sections describe the development process driven by a change-based strategy, followed by aĬontinuous integration approach. Where they have proved valuable for improving the reliability of software produced in the scientific Software development process of the former European Commission-funded project INDIGO-DataCloud, The following sections describe the quality conventions and best practices that apply to theĭevelopment phase of a software component within the EOSC ecosystem. “RECOMMENDED”, “MAY”, and “OPTIONAL” in this document are to be interpreted as described in RFC 2119 The keywords “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”, “SHOULD NOT”, Providing recommendations on external security assessment. Lower the barriers of software adoption by delivering quality documentation and the utilizationĮncourage secure coding practices and security static analysis at the development phase while Validated by the automated execution of the relevant tests.Īdopt an agile approach to effectively produce timely and audience-specific documentation. Propose a change-based driven scenario where all new updates in the source code are continuously Improve the quality and reliability of software by covering different testing methods at ![]() Promote code style standards to deliver good quality source code emphasizing its readability and Set the base of minimum SQA criteria that a software developed within EOSC development projectĮnhance the visibility, accessibility and distribution of the produced source code through theĪlignment to the Open Source Definition. Upcoming software development efforts within the European research community, and continuouslyĮvolve in order to be aligned with future software engineering practices and security The result is a consolidated Software Quality Assurance (SQA) baseline criteria emanated from theĮuropean Open Science Cloud (EOSC), which aims to outline the SQA principles to be considered in the These guidelines evolved throughout the project’s lifetime and are being extended in theĮOSC-Synergy, as well as the past DEEP-Hybrid-DataCloud and This document has been tailored upon the recommendations and requirements found in the Initial Planįor Software Management and Pilot Services deliverable Received funding from the European Union’s Horizon 2020 research and innovation programme under The INDIGO-DataCloud, DEEP-Hybrid-DataCloud, eXtreme-DataCloud and EOSC-Synergy projects have Copyright NoticeĬopyright © Members of the INDIGO-DataCloud, DEEP Hybrid-DataCloud eXtreme DataCloud andĮOSC-Synergy collaborations, 2015-2021. To conform a Software Quality Assurance plan to serve as a reference within the European researchĮcosystem related projects for the adequate development and timely delivery of software products. The purpose of this document is to define a set of quality standards, procedures and best practices National Institute of Nuclear Physics (INFN) Universitat Politècnica de València (UPV) Laboratory of Instrumentation and Experimental Particle Physics (LIP) Spanish National Research Council (CSIC) Institute of Physics of Cantabria (IFCA) A set of Common Software Quality Assurance Baseline Criteria for Research Projects A set of Common Software Quality Assurance Baseline Criteria for Research ProjectsĪ DOI-citable version of this manuscript is available at.
0 Comments
Read More
Leave a Reply. |