مخزنهای نرم افزار واحد و یکپارچه برای ون دلستین 7-X : عناصر جریان کار برای توسعه نرم افزار فیوژن
|کد مقاله||سال انتشار||مقاله انگلیسی||ترجمه فارسی||تعداد کلمات|
|21810||2008||3 صفحه PDF||سفارش دهید||محاسبه نشده|
Publisher : Elsevier - Science Direct (الزویر - ساینس دایرکت)
Journal : Fusion Engineering and Design, Volume 83, Issues 2–3, April 2008, Pages 410–412
Software development for a large project like Wendelstein 7-X (W7-X) requires an appropriate development process to provide a reliable environment supporting the coordinated work of scientific and engineering stakeholders. The first step to achieve this goal was the installation of a central source code management system (SCM). Besides being a code base it provides functions allowing the specification of a release procedure by introducing levels of acceptance specified by appropriate quality criteria. The SCM system serves as a starting point for automatic generation of standard code documentation and for performing automatic testing procedures on standardized integration platforms. In order to provide a universal documentation platform for the multi programming language environment at W7-X the DocSys system has been developed which allows to employ any (language specific) document generator producing html-pages for presentation via internet. An automatic integration testing environment is still being prepared and not yet in standard use.
1. Software development process Software developments for Wendelstein 7-X (W7-X) aim at an integrated software project . Efforts for device control, data acquisition, data analysis, modelling and theory are to be shared to avoid duplicate work and to gain most validated software modules. Development and implementation of the W7-X software project require a well-designed workflow that allows quality, safety, stability, as well as the necessary flexibility to be adequate for every use-case, ranging from operation relevant software to scientific exploration. The workflow for W7-X software developments is not finally settled yet. However, central elements are identified and Fig. 1 shows a possible workflow organization. The private/public paradigm is oriented at similar distinctions at JET, where data are organized to be used, e.g., for development (private) or routine (public) purposes. Here, cf. Fig. 1, the developer is working in a private environment first. This can be an afs directory, a local data medium, or a professional versioning system.A prerequisite for developments to be released for public use is a commissioning process. Directions for the commissioning process were defined  and are going to be extended to be in accordance with respective ISO standards. Up to now, there are development guidelines, specifications of supported programming languages and versioning systems (SVN, CVS) and formal acceptance criteria. A central element are clear responsibilities documented in publicly available documents. In Fig. 1 all changes in the public repository are to be accepted by the commissioning responsible officer. Formal criteria for acceptance cover exhaustive software documentations including application programming interface (API) description, references, user manual, and further application specific information describing the domain of each respective software component. In order to minimize the effort for the developer an automated documentation framework  is part of the concept. The framework generates a unified documentation on basis of in-code comments allowing an inclusion of any free configurable supplementary information. In order to keep all the public software up-to-date, a special framework for a continuous build process is necessary. This is the domain of continuous software integration . Continuous Integration uses a Build SVN repository to test the consistency of the whole software system. The process is supervised by an integration responsible officer (cf. Fig. 1). Currently, this workflow element is under assessment.
نتیجه گیری انگلیسی
A definition of the workflow elements for W7-X software developments is proceeding. Major requirements and actors were figured out and several measures for a workflow installation have been made. This covers software repositories and software documentation in addition to several directions documenting scope and responsibilities. The hitherto gained experience with the implemented elements (SVN, software documentation tools, DocSys) meet the most users expectations and seem to be a good base for further extensions. A completion of standards and the implementation of a software integration workflow are in progress.