SIST EN 14160:2004
(Main)Space engineering - Software
Space engineering - Software
This European Standard defines the space software engineering process and its interfaces with the space project management standards (EN 13290) and space product assurance standards (EN 13291) and explains how they apply in the software engineering process.
This Standard is applicable to all the elements of a space system, including the space segment, the launch service segment and the ground segment.
This Standard covers all aspects of space software engineering including requirements definition, design, production, verification and validation, and transfer, operations and maintenance.
The scope of this Standard is the software developed as part of a space project, i.e. "Space system product software". It is not intended to cover software developments out of scope with the system of space standards. An example is the development of commercial software packages, where software is developed for a (large) volume market and not just for a single customer, and the main requirement analysis consists of market analysis, combined with a marketing strategy.
Other classes of software products not covered are: management information systems (e.g. finance, planning), technical information systems (e.g. CAD/CAM, analysis packages) and supporting software products for documentation systems, database systems, spreadsheets. These usually result from the procurement or adaptation of existing commercial products, and not part of the space system development. Such software products are, however, often part of a supporting infrastructure for space systems.
When viewed from the perspective of a specific project context, the requirements defined in this Standard should be tailored to match the genuine requirements of a particular profile and circumstances of a project.
Raumfahrttechnik - Software
Diese Europäische Norm legt den Software-Engineeringprozess für die Raumfahrt sowie seine Schnittstellen mit den Raumfahrtnormen fest, die das Management (EN 13290) und die Produktsicherung (EN 13291) betreffen und erläutert den Umfang, in dem sie für den Engineeringprozess gelten.
Diese Norm gilt für alle Segmente eines Raumfahrtsystems, d. h., sie umfasst das Raumsegment, das Startservicesegment und das Bodensegment.
Diese Norm behandelt alle Aspekte des Software-Engineering für die Raumfahrt wie Anforderungen, Design, Produktion, Verifizierung und Validierung, Übertragung, Betrieb und Softwarepflege.
Diese Norm gilt für Software, wie sie für Raumfahrtprojekte entwickelt wird, d. h. die ?Produktsoftware des Raumfahrtsystems". Sie bezieht sich nicht auf die Entwicklung von Software für Bereiche außerhalb des Normensystems für die Raumfahrt, wie dies zum Beispiel für die Entwicklung von Softwarepaketen für handelsübliche Zwecke gilt, bei denen Software für einen größeren Markt und nicht nur für einen einzelnen Kunden entwickelt wird, wo die Grundanforderungen aus einer Marktanalyse in Verbindung mit einer Marketingstrategie entwickelt werden.
Diese Norm behandelt auch nicht Softwareprodukte wie Managementinformationssysteme (z. B. Finanzen, Planung), technische Informationssysteme (z. B. CAD/CAM, Analysepakete) und unterstützende Softwareprodukte für Dokumentationssysteme, Datenbanksysteme und Tabellenkalkulationsprogramme. Diese werden üblicherweise im Zusammenhang mit der Beschaffung oder Anpassung vorhandener Produkte entwickelt, aber nicht im Rahmen der Entwicklung von Raumfahrtsystemen. Derartige Softwareprodukte werden jedoch häufig zur Unterstützung der Infrastruktur für Raumfahrtsysteme eingesetzt.
Ingéniérie spatiale - Logiciel
La présente Norme européenne définit l'objet du processus d'ingénierie du logiciel spatial ainsi que les interfaces avec les branches Management (EN 13290) et Assurance Produit (EN 13291) du systeme de normes ECSS et explique comment la présente norme s'applique au processus d'ingénierie du logiciel.
La présente norme s'applique a tous les éléments d'un systeme spatial, y compris le segment spatial, le segment de service de lancement et le segment au sol.
La présente norme couvre tous les aspects de l'ingénierie du logiciel spatial y compris la définition des exigences, la conception, la production, la vérification et validation, les opérations de transfert et la maintenance.
L'objet de la présente norme est le logiciel développé dans le cadre d'un projet spatial, c'est-a-dire, le "produit logiciel du systeme spatial". La présente norme n'est pas destinée a couvrir les développements logiciels en dehors du domaine des normes ECSS. Un exemple en serait le développement d'un logiciel commercial visant un (large) volume de marché et non pas un utilisateur unique ; l'analyse de l'exigence principale consisterait en une analyse de marché couplée a une stratégie marketing.
Les autres types de produits logiciels non couverts par la présente norme sont : les systemes d'informations de management (par exemple, finance, planification), les systemes d'informations techniques (par exemple, CFAO, logiciels d'analyse) et les produits logiciels de support des systemes de documentation, des systemes de banques de données et des tableurs. Ces types de produits résultent de l'approvisionnement ou de l'adaptation de produits commerciaux existants et ne sont pas issus d'un développement de systeme spatial. Ces produits logiciels font cependant souvent partie d'une infrastructure de support des systemes spatiaux.
Space engineering - Software
General Information
Relations
Standards Content (Sample)
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.Space engineering - SoftwareRaumfahrttechnik - SoftwareIngéniérie spatiale - LogicielSpace engineering - Software49.140Vesoljski sistemi in operacijeSpace systems and operationsICS:Ta slovenski standard je istoveten z:EN 14160:2001SIST EN 14160:2004en01-maj-2004SIST EN 14160:2004SLOVENSKI
STANDARD
SIST EN 14160:2004
EUROPEAN STANDARDNORME EUROPÉENNEEUROPÄISCHE NORMEN 14160December 2001ICS 49.140English versionSpace engineering - SoftwareThis European Standard was approved by CEN on 11 November 2001.CEN members are bound to comply with the CEN/CENELEC Internal Regulations which stipulate the conditions for giving this EuropeanStandard the status of a national standard without any alteration. Up-to-date lists and bibliographical references concerning such nationalstandards may be obtained on application to the Management Centre or to any CEN member.This European Standard exists in three official versions (English, French, German). A version in any other language made by translationunder the responsibility of a CEN member into its own language and notified to the Management Centre has the same status as the officialversions.CEN members are the national standards bodies of Austria, Belgium, Czech Republic, Denmark, Finland, France, Germany, Greece,Iceland, Ireland, Italy, Luxembourg, Netherlands, Norway, Portugal, Spain, Sweden, Switzerland and United Kingdom.EUROPEAN COMMITTEE FOR STANDARDIZATIONCOMITÉ EUROPÉEN DE NORMALISATIONEUROPÄISCHES KOMITEE FÜR NORMUNGManagement Centre: rue de Stassart, 36
B-1050 Brussels© 2001 CENAll rights of exploitation in any form and by any means reservedworldwide for CEN national Members.Ref. No. EN 14160:2001 ESIST EN 14160:2004
EN 14160:2001 (E)2ContentsForeword.5Introduction.51Scope.62Normative references.63Terms, definitions and abbreviated terms.73.1Terms and definitions.73.2Abbreviated terms.94Space system software engineering.104.1Introduction.104.2Organization of this Standard.104.3Space system software engineering processes.114.3.1General.114.3.2Software requirements engineering process.154.3.3Software design engineering process.154.3.4Software verification and validation (qualification) process.154.3.5Software operations engineering process.164.3.6Software maintenance process.164.4Relation to space project management and space product assurance standards.164.4.1General.164.4.2Software product assurance.164.4.3Software project management.164.5Verification engineering.185General requirements.185.1Introduction.185.2System engineering processes related to software.185.2.1Introduction.185.2.2System requirements analysis.195.2.3System partitioning.195.2.4System level requirements for software verification and validation.205.2.5System level integration of software.205.2.6Software operations.225.3Software management.225.3.1Introduction.225.3.2Software life cycle.235.3.3Interface management.255.3.4Technical budget and margin management.25SIST EN 14160:2004
EN 14160:2001 (E)35.4Software requirements engineering process.265.4.1Introduction.265.4.2Software requirements analysis.265.4.3Software toplevel architectural design.275.4.4Software verification and validation.285.5Software design engineering process.295.5.1Introduction.295.5.2Design of software items.295.5.3Coding and testing.305.5.4Integration.315.6Software verification and validation (qualification) process.335.6.1Introduction.335.6.2Milestones.335.6.3Verification and validation processes.335.6.4Verification process implementation.345.6.5Validation process implementation.355.6.6Verification process.365.6.7Validation process.385.6.8Joint technical review process.405.7Software operations engineering process.405.7.1Introduction.405.7.2Operation process.415.7.3Process implementation.415.7.4Operational testing.415.7.5System operation.425.7.6User support.425.8Software maintenance process.425.8.1Introduction.425.8.2Process implementation.435.8.3Problem and modification analysis.435.8.4Modification implementation.445.8.5Maintenance review and acceptance.445.8.6Software migration.455.8.7Software retirement.466Special requirements.466.1Introduction.466.2Space segment software.466.2.1General.466.2.2Critical functions.466.2.3System interfaces.476.2.4Inflight software modifications.476.3Ground segment software.486.4Software reuse.486.4.1General.486.4.2Developing software for intended reuse.486.4.3Reusing software from other projects.48SIST EN 14160:2004
EN 14160:2001 (E)46.5Manmachine interfaces.496.6Critical software.50Annex A
(normative)
Software documentation.51A.1Introduction.51A.2The requirements baseline (RB).51A.2.1General.51A.2.2Requirements baseline contents at SRR.51A.2.3Interface requirements document (IRD).52A.3Technical specification (TS).53A.3.1General.53A.3.2Interface control document (ICD).54A.3.3Software maintenance plan.54A.3.4Operations manual.54A.4Design justification file (DJF).54A.5Design definition file (DDF).56A.6System level documentation.57A.6.1Introduction.57A.6.2Operations, maintenance, migration and retirement documentation.57Annex B (informative)
Requirement cross references.59Annex C (informative)
References to other space standards.61Bibliography.62FiguresFigure 1 — The recursive customer - supplier model.12Figure 2 — Overview of the software development processes.13Figure 3 — Process constraints.14Figure 4 — Accommodation of different software life cycles.14SIST EN 14160:2004
EN 14160:2001 (E)5ForewordThis European Standard has been prepared by CMC.This European Standard shall be given the status of a national standard, either by publication of anidentical text or by endorsement, at the latest by June 2002, and conflicting national standards shall bewithdrawn at the latest by June 2002.According to the CEN/CENELEC Internal Regulations, the national standards organizations of thefollowing countries are bound to implement this European Standard: Austria, Belgium, Czech Republic,Denmark, Finland, France, Germany, Greece, Iceland, Ireland, Italy, Luxembourg, Netherlands, Norway,Portugal, Spain, Sweden, Switzerland and the United Kingdom.It is based on a previous version1) originally prepared by the ECSS Software Engineering WorkingGroup, reviewed by the ECSS Technical Panel and approved by the ECSS Steering Board. TheEuropean Cooperation for Space Standardization (ECSS) is a cooperative effort of the European SpaceAgency, National Space Agencies and European industry associations for the purpose of developingand maintaining common standards.This Standard is one of the series of space standards intended to be applied together for themanagement, engineering and product assurance in space projects and applications.Requirements in this Standard are defined in terms of what shall be accomplished, rather than in termsof how to organize and perform the necessary work. This allows existing organizational structures andmethods to be applied where they are effective, and for the structures and methods to evolve asnecessary without rewriting the standards.The formulation of this Standard takes into account the existing ISO 9000 family of documents.Annex A is normative. Annexes B and C are informative.This standard includes a Bibliography.IntroductionThis Standard reflects the specific methods used in space system developments, and the requirementsfor the software engineering process in this context. Together with the requirements found in the otherbranches of the European Space Standards, this Standard provides a coherent and complete frameworkfor software engineering in a space project.This Standard is intended to help customers in formulating their requirements and suppliers in preparingtheir response and implementing the work.This Standard is not intended to replace textbook material on computer science or technology, and suchmaterial has been avoided in this Standard. The readers and users of this Standard are assumed topossess general knowledge of computer science.
1) ECSS-E-40A.SIST EN 14160:2004
EN 14160:2001 (E)61ScopeThis European Standard defines the space software engineering process and its interfaces with thespace project management standards (EN 13290) and space product assurance standards (EN 13291)and explains how they apply in the software engineering process.This Standard is applicable to all the elements of a space system, including the space segment, thelaunch service segment and the ground segment.This Standard covers all aspects of space software engineering including requirements definition,design, production, verification and validation, and transfer, operations and maintenance.The scope of this Standard is the software developed as part of a space project, i.e. "Space systemproduct software". It is not intended to cover software developments out of scope with the system ofspace standards. An example is the development of commercial software packages, where software isdeveloped for a (large) volume market and not just for a single customer, and the main requirementanalysis consists of market analysis, combined with a marketing strategy.Other classes of software products not covered are: management information systems (e.g. finance,planning), technical information systems (e.g. CAD/CAM, analysis packages) and supporting softwareproducts for documentation systems, database systems, spreadsheets. These usually result from theprocurement or adaptation of existing commercial products, and not part of the space systemdevelopment. Such software products are, however, often part of a supporting infrastructure for spacesystems.When viewed from the perspective of a specific project context, the requirements defined in thisStandard should be tailored to match the genuine requirements of a particular profile and circumstancesof a project.NOTETailoring is the process by which individual requirements or specifications, standards and relateddocuments are evaluated and made applicable to a specific project by selection, and in some exceptionalcases, modification of existing or addition of new requirements.2Normative referencesThis European Standard incorporates by dated or undated reference, provisions from other publications.These normative references are cited at the appropriate places in the text and the publications are listedhereafter. For dated references, subsequent amendments to or revisions of any of these publicationsapply to this European Standard only when incorporated in it by amendment or revision. For undatedreferences the latest edition of the publication referred to applies (including amendments).EN 13290-1:1999, Space project management — General requirements — Part 1: Policy and principles.EN 13290-2:2001, Space project management — General requirements — Part 2: Project breakdownstructure.EN 13290-3:2001, Space project management — General requirements — Part 3: Project organization.EN 13290-4:2001, Space project management — General requirements — Part 4: Project phasing andplanning.EN 13290-5:2001, Space project management — General requirements — Part 5: Configurationmanagement.EN 13290-6:2001, Space project management - General requirements - Part 6:Information/Documentation management.EN 13290-7:2001, Space project management — General requirements — Part 7: Cost and schedulemanagement.SIST EN 14160:2004
EN 14160:2001 (E)7EN 13291-2:— 2), Space product assurance — General requirements — Part 2: Quality assurance.EN 13292:1999, Space engineering — Policy and principles.EN 13701, Space systems — Glossary of terms.ISO 8402:1994, Quality management and quality assurance — Vocabulary.ISO/IEC 12207:1995, Information technology — Software life cycle processes.ISO 16091:—2), Space project management — Integrated logistic support.ECSS-E-10, Space engineering — System engineering.ECSS-E-40-01 2), Space engineering — Space segment software.ECSS-E-40-03 2), Space engineering — Ground segment software.ECSS-Q-80, Space product assurance — Software product assurance.3Terms, definitions and abbreviated terms3.1Terms and definitionsFor the purposes of this European Standard, the terms and definitions given in EN 13701 and thefollowing apply.3.1.1(toplevel) architecturehighest level(s) structure of the components of a program or system, their interrelationships, andprinciples and guidelines governing their design and evolution over time3.1.2embedded software (deprecated)NOTE 1This term is sometimes used to denote that software, at varying levels, is part of a system.NOTE 2The term is also sometimes used to emphasize that the software in question has extensivehardware interface requirements or realtime requirements. The term is purely descriptive.3.1.3maintainerorganization that performs maintenance activities[ISO/IEC 12207:1995]3.1.4margin philosophyrationale for margins allocated to the performance parameters and computer resources of adevelopment, and how these margins shall be managed during the execution of the project3.1.5migrationporting of a software product to a complete new environment3.1.6singular inputindividual parameter stress testing
2) To be published.SIST EN 14160:2004
EN 14160:2001 (E)83.1.7software componentgeneral term for a part of a software systemNOTEComponents are assembled or decomposed to form new components. In the production phase,components are implemented as modules, tasks or programs, any of which may be configuration items. Thisuse of the term is more general than in ANSI/IEEE parlance, which defines a component as a "basic part ofa system or program"; in this Standard components are not "basic" as they can be decomposed.3.1.8software itemsee 3.1.11, software product3.1.9software intensive systemspace software product where the dominant part of the constituents are software elementsNOTEIn such systems, subsystems consist mainly of software. For this type of system, the majority ofinterfaces are softwaresoftware interfaces.3.1.10software observabilityproperty of a system for which observations of the output variables suffices to determine the initialvalues of status variables3.1.11software productset of computer programs, procedures and possibly associated documentation and data3.1.12software unitseparately compilable piece of code[ISO/IEC 12207:1995]NOTEIn this Standard no distinction is made between a software unit and a database; both are coveredby the same requirements.3.1.13stress testtest that evaluates a system or software component at or beyond the limits of its specified requirements3.1.14validationconfirmation by examination and provision of objective evidence that the particular requirements for aspecific intended use are fulfilled[ISO 8402:1994]NOTEThe validation process (for software): confirmation that the requirements baseline functions andperformances are correctly and completely implemented in the final product.3.1.15verificationconfirmation by examination and provision of objective evidence that specified requirements have beenfulfilled[ISO 8402:1994]SIST EN 14160:2004
EN 14160:2001 (E)9NOTEThe verification process (for software): confirmation that adequate specifications and inputs existfor any activity, and that the outputs of the activities are correct and consistent with the specifications andinput.3.2Abbreviated termsThe following abbreviated terms are defined and used within this European Standard.AbbreviationMeaningARacceptance reviewNOTEThe term SWAR may be used for clarity to denote ARs that solely involvesoftware products.CDRcritical design reviewNOTEThe term SWCDR may be used for clarity to denote CDRs that solelyinvolve software products.CJFchange justification fileCOTScommercial offtheshelf softwareNOTEThis term denotes finished software products, that are procured from thirdparties.CPUcentral processing unitDDFdesign definition fileDJFdesign justification fileICDinterface control documentIRBinterface requirements baselineIRDinterface requirements documentISVindependent software validationISVVindependent software verification and validationMMImanmachine interfaceMOTSmodifiable offtheshelfMPmaintenance planOPoperational planORR operational requirements reviewPDRpreliminary design reviewNOTEThe term SWPDR may be used for clarity to denote PDRs that solelyinvolve software products.QRqualification reviewNOTEThe term SWQR may be used for clarity to denote QRs that solely involvesoftware products.SIST EN 14160:2004
EN 14160:2001 (E)10RBrequirements baselineSDEsoftware development environmentNOTESoftware tools that are supporting the software engineering process.SRRsystem requirements reviewNOTEThe term SWSRR may be used for clarity to denote SRRs that solelyinvolve software products.SWsoftwareTStechnical specification4Space system software engineering4.1IntroductionThis clause introduces the structure of this Standard and the framework of the space softwareengineering process that form its basis.The context of space software engineering is the overall space system engineering process. This clausedefines the general relationships between the software engineering processes and the generalengineering processes of space systems.The software engineering standard differs from the other engineering disciplines covered by theEuropean Space Standards in one important aspect: software does not in itself produce heat, havemass or any other physical characteristics. The software engineering activity is a purely intellectualactivity and a principle output of the activity is documentation. If the software code itself is considered asa specialized form of electronic documents, all visible outputs are in fact documentation.It follows that this Standard focuses on requirements for the structure and content of the documentationproduced.Software can be used for the implementation of highly complex functions. The ability to deal with a highlevel of complexity in a flexible way makes software an essential and increasing part of space segmentand ground segment products. In space systems, software engineering is found at all levels rangingfrom system level functions down to the firmware of a space system part.Therefore the requirements engineering process, in which the software requirements and specificationsare defined, has a special emphasis in this Standard. The software requirements engineering processconsumes a large and often underestimated amount of effort in the development of software for spacesystems.As a result of the complexity of the functional and performance requirements, special measures andemphasis are required for software verification and validation, especially for space segment software.The functions assigned to software can be critical to the space mission.The maintenance of software for space systems also poses special problems, because they implyoperational lifetimes that far exceed what is expected of general computer software products. For thespace segment, this is further complicated by the fact that software in general is the only part of thespace segment that undergoes major maintenance and repair, sometimes even redesign, after launch.In extreme cases, the space system mission itself is redesigned, implementing new space segmentsoftware after launch. Ground segment software is similarly characterized.4.2Organization of this StandardThis Standard is organized in two main parts:SIST EN 14160:2004
EN 14160:2001 (E)11—General requirements. These are the core normative requirements for any space systemsoftware engineering activity.—Special requirements. These are additional requirements for specific application areas. Theserequirements are always applicable, but are only active in developments where the addresseddisciplines or application areas occur. This separation serves to ma
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.