SIST-TP CLC/R217-007:2004
(Main)Recommendations on necessary concepts to model behavioural semantics
Recommendations on necessary concepts to model behavioural semantics
D116/196: TC 217 disbanded * D122/065: Withdrawn
Tehnike izločanja parametrov za evropski mini preskusni čip
General Information
Standards Content (Sample)
SLOVENSKI SIST-TP CLC/R217-007:2004
STANDARD
september 2004
Tehnike izločanja parametrov za evropski mini preskusni čip
Recommendation on necessary concepts to model behavioural semantics
ICS 35.080 Referenčna številka
SIST-
...
This May Also Interest You
This Handbook provides recommendations for the implementation of an Agile approach in space software projects complying with EN 16603-40 (based on ECSS-E-ST-40) and EN 16602-80 (based on ECSS-Q-ST-80).
This handbook is not an Agile development book, though it provides an Agile reference model based on Scrum and also covers other major Agile methods and techniques. Scrum has been selected as reference because of its widespread application in industry and its flexibility as a development framework to introduce or merge with other Agile methods and techniques. In relation to the EN 16603-40 and EN 16602-80, this handbook does not provide any tailoring of their requirements due to the use of the Agile approach, but demonstrates how compliance towards ECSS can be achieved. This handbook does not cover contractual aspects for this particular engineering approach, although it recognises that considering the approach of fixing cost and schedule and making the scope of functionalities variable, the customer and supplier need to establish specific contractual arrangements. Furthermore, it does not impose a particular finality for the use of Agile, either as a set of team values, project management process, specific techniques or supporting exploration by prototypes.
- Technical report105 pagesEnglish languagesale 10% offe-Library read for×1 day
This Handbook provides advice, interpretations, elaborations and software engineering best practices for the implementation of the requirements specified in EN 16603-40 (based on ECSS-E-ST-40C). The handbook is intended to be applicable to both flight and ground. It has been produced to complement the EN 16603-40 Standard, in the area where space project experience has reported issues related to the applicability, the interpretation or the feasibility of the Standard. It should be read to clarify the spirit of the Standard, the intention of the authors or the industrial best practices when applying the Standard to a space project.
The Handbook is not a software engineering book addressing the technical description and respective merits of software engineering methods and tools.
- Standard198 pagesEnglish languagesale 10% offe-Library read for×1 day
This handbook defines methods for process assessment and improvement that may be used to meet the requirements on
process assessment and improvement of the EN16602-80 (equivalent to ECSS-Q-ST-80C) subclause 5.7. These methods constitute a clear and proven w ay of implementing those requirements. Alternative methods can be used provided that they meet the detailed instructions provided in this handbook for recognition of software process assessment schemes and results and process improvement.
This handbook provides a detailed method for the implementation of the requirements of the EN16602-80 for software process assessment and improvement. It also establishes detailed instructions for alternative methods intended to meet the same EN16602-80 requirements.
The process assessment and improvement scheme presented in this handbook is based on and conformant to the ISO/IEC 15504 International Standard. In designing this process assessment and improvement scheme the ISO/IEC 15504 exemplar process assessment model w as adopted and extended to address specific requirements.
The methods provided in this handbook can support organizations in meeting their business goals and in this context they can be tailored to suit their specific needs and requirements. How ever w hen used to claim compliance with relevant requirements in EN16602-80 only the steps and activities explicitly marked as recommended in this handbook may be omitted or modified.
- Technical report122 pagesEnglish languagesale 10% offe-Library read for×1 day
- Draft122 pagesEnglish languagesale 10% offe-Library read for×1 day
This handbook provides assessors with a number of instruments needed to perform software process capability assessments using the assessment method described in EN 17603-80-11 (equivalent to ECSS-Q-HB-80-02 Part 1). It also provides instruments that help assessors to carry out their activities when performing assessments and supporting the implementation of software process improvement initiatives using the method for process improvement described in Part 1.
The instruments provided are:
• The Process Assessment Model (PAM) required to perform assessments including process descriptions and process attribute indicators
• Conformance statement to the requirements in ISO/IEC 15504 Part 2
• A definition of the Process Reference Model (PRM) on which TR 17603-80-11 and TR 17603-80-12 (equivalent to ECSS-Q-HB-80-02 Part 1 and 2) PAM are based (defined in TR 17603-80-11)
• Detailed traces from base practices in the PAM to standard clauses and from work products to expected outputs.
- Technical report129 pagesEnglish languagesale 10% offe-Library read for×1 day
- Draft129 pagesEnglish languagesale 10% offe-Library read for×1 day
The scope of this Handbook is the software metrication as part of a space project, i.e. a space system, a subsystem including hardware and software, or ultimately a software product. It is intended to complement the EN 16602-80 (equivalent to ECSS-Q-ST-80) with specific guidelines related to use of different software metrics including their collection, analysis and reporting. Tailoring guidelines for the software metrication process are also provided to help to meet specific project requirements.
This Handbook provides recommendations, methods and procedures that can be used for the selection and application of appropriate metrics, but it does not include new requirements w ith respect to those provided by EN 16602-80 (equivalent to ECSS-ST-Q-80).
The scope of this Handbook covers the following topics:
• Specification of the goals and objectives for a metrication programme.
• Identification of criteria for selection of metrics in a specific project / environment (goal driven).
• Planning of metrication in the development life cycle.
• Interface of metrication with engineering processes.
• Data collection aspects (including use of tools).
• Approach to the analysis of the collected data.
• Feedback into the process and product based on the analysis results.
• Continuous improvement of measurement process.
• Use of metrics for process and product improvement.
This Handbook is applicable to all types of software of all major parts of a space system, including the space segment, the launch service segment and the ground segment software.
- Technical report100 pagesEnglish languagesale 10% offe-Library read for×1 day
- Draft100 pagesEnglish languagesale 10% offe-Library read for×1 day
This handbook provides recommendations, methods and procedures that can be used for the selection and reuse of existing software in space software systems.
This handbook is applicable to all types of software of a space system, including the space segment, the launch service segment and the ground segment software (including EGSEs) whenever existing software is intended to be reused within them.
This handbook covers the following topics:
• Software reuse approach including guidelines to build the Software Reuse File
• Techniques to support completion of existing software qualification to allow its reuse in a particular project
• Tool qualification
• Risk management aspects of reusing existing software Existing software can be of any type: Purchased (or COTS), Legacy-Software, open-source software, customer-furnished items (CFI's), etc.
NOTE Special emphasis is put on guidance for the reuse of COTS software often available as-is and for which no code and documentation are often available.
Legal and contractual aspects of reuse are in principle out of scope; how ever guidelines to help in determine the
reusability of existing software from a contractual point of view is provided in [ESA/REG/002].
Any organization with the business objective of systematic reuse may need to implement the organizational reuse processes presented in [ISO12207]. These processes w ill support the identification of reusable software products and components within selected reuse domains, their classification, storage and systematic reuse within the projects of that organization, etc. But these processes are out of scope of this handbook as the handbook is centred on the specific project activities to reuse an existing software product, not part of those organizational reuse processes more oriented to ‘design for reuse’ processes.
In addition, this handbook provides guidelines to be used for the selection and analysis of tools for the development, verification and validation of the operational software.
- Technical report58 pagesEnglish languagesale 10% offe-Library read for×1 day
- Draft58 pagesEnglish languagesale 10% offe-Library read for×1 day
This Handbook provides guidance on the application of the dependability and safety requirements relevant to software defined in EN 16602-80 (equivalent of ECSS-Q-ST-80).
This Handbook provides support for the selection and application of software dependability and safety methods and techniques that can be used in the development of software-intensive space systems.
This Handbook covers all of the different kinds of software for which EN 16602-80 (equivalent of ECSS-Q-ST-80) is applicable. Although the overall software dependability and safety workflow description is mainly targeted to the development of spacecraft, the described approach can be adapted to projects of different nature (e.g. launchers, ground systems).
The methods and techniques described in the scope of this Handbook are limited to assessment aspects, not including development and implementation techniques for dependability and safety (e.g. fault tolerance techniques, or development methods like coding standards, etc.).
Although dependability is a composite term, including reliability, availability and maintainability, this Handbook addresses in particular the reliability aspects. Software maintainability and availability are not covered in depth by this handbook, because the relevant methods and techniques are still undergoing improvement. Nevertheless, whenever a link can be made to either of these two characteristics, it is explicitly mentioned in the corresponding section.
- Technical report43 pagesEnglish languagesale 10% offe-Library read for×1 day
- Draft43 pagesEnglish languagesale 10% offe-Library read for×1 day
This European Technical Specification will provide a set of requirements for developers of health and wellness apps, intending to meet the needs of health care professionals, patients, carers and the wider public. It will include a set of quality criteria and cover the app project life cycle, through the development, testing, releasing and updating of an app, including native, hybrid and web based apps, those apps associated with wearable, ambient and other health equipment and apps that are linked to other apps. It will also address fitness for purpose and the monitoring of usage. The specification will inform the development of health and wellness apps irrespective of whether they are placed in the market, and including free of charge.
The specification will not cover the processes or criteria that an app developer or publisher follow to establish whether a health and wellness app is subject to regulatory control (e.g. as a medical device, or related to information governance).
- Technical specification87 pagesEnglish languagesale 10% offe-Library read for×1 day
This document specifies essential features of terminology management systems, regardless of specific software engineering paradigms, user interface and user assistance design principles, and specific data models. These features enable maximum efficiency and quality in terminology work and, thus, support creating, processing, and using high quality terminology. The intended audiences of this document are software engineers/developers as well as terminologists, technical communicators, translators, interpreters, language planners, and subject field experts.
This document describes all features needed for recording, editing, maintaining, exchanging, and presenting terminological data. Term extraction features used to identify new terms are out of the scope of this document.
- Standard17 pagesEnglish languagesale 10% offe-Library read for×1 day
- Standard17 pagesEnglish languagesale 10% offe-Library read for×1 day
- Standard12 pagesEnglish languagesale 15% off
- Draft17 pagesEnglish languagesale 10% offe-Library read for×1 day
This document provides model, high-level functional requirements and associated guidance for software applications that are intended to manage digital records (including digital copies of analogue source records), either as the main purpose of the application or as a part of an application that is primarily intended to enable other business functions and processes.
It does not include:
— functional requirements for applications that manage analogue records;
— generic design requirements such as reporting, application administration and performance;
— requirements for the long-term preservation of digital records in a dedicated preservation environment;
NOTE The model requirements are intended to encourage the deployment of applications that do not hinder long-term preservation of records. As such, some of the requirements support long-term digital preservation outcomes.
— implementation guidance for applications that manages analogue and/or digital records. Such guidance can be found in ISO/TS 16175-2:—[1].
[1] Under development. Stage at the time of publication: ISO/DTS 16175-2:2020.
- Standard44 pagesEnglish languagesale 10% offe-Library read for×1 day
- Standard37 pagesEnglish languagesale 15% off
- Standard40 pagesFrench languagesale 15% off
- Draft40 pagesEnglish languagesale 10% offe-Library read for×1 day
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.