Learn which project types are available at ASAM.
The core of ASAM is to carry out Standard development projects with the goal to create new standards and to update existing standards in accordance with the demands of ASAM members and market requirements. ASAM defines four types of Standard development projects, depending on the expected magnitude of changes to the Standard:
They all have in common that the primary output of the project is a Standard. The upper limit for subsidiary funding from ASAM is 25% of the total required project budget.
New Standard Development
A new Standard is developed from the outset. There is no predecessor in the ASAM Standard portfolio, or the predecessor has been declared as 'depricated'. A new ASAM Standard can be a transfer from another organization or an extension of a Standard from another standardization organization.
Major Version Development
A major version development project introduces significant changes to the Standard, e.g. the addition of a new major feature or significant changes to existing features. It is expected that the implementation of the new version will require significant development or migration efforts by tool vendors and end users alike. A new major version of an ASAM Standard does not have to be backward-compatible to its predecessor.
Minor Version Development
A minor version development project introduces changes to existing features on a smaller scale or introduce new features that are rather small relative to the rest of the Standard. It is expected that the implementation of the new version will require low development or migration efforts by tool vendors and end users. A minor version of an ASAM Standard shall be backward-compatible to its immediate predecessor. Exceptions are allowed, require approval from the TSC and must be documented in the Standard.
A maintenance project resolves technical issues of the Standard, i.e. corrects errors, removes ambiguities, adds clarifications to existing descriptions, makes editorial improvements or changes examples. It is expected that the implementation of the new version will require low development or migration efforts by tool vendors and end users. Maintenance versions cannot include new features. A maintenance version of an ASAM Standard is always backward-compatible.
An implementation project has the purpose to create a supplementary product that supports the implementation or application of an ASAM Standard in the industry. The result of an implementation project can be a tool or source code. Examples for tools are checkers for file formats and APIs, add-ons or plug-ins for de-facto Standard IDEs (e.g. MATLAB, Simulink, Eclipse, etc.), importers, exporters or reference implementations. Source code is typically an implementation of the Standard and can be used as a reference for software development or is directly used as compilable software components in COTS products. Source code shall ensure a high degree of Standard-compliance and significantly reduce software development efforts at ASAM tool vendor companies, where otherwise each of the them would have to develop the software by themselves.
Deliverables of an implementation project have product-quality. They are professionally developed by a contractor in accordance with customary industry quality guidelines. A project group must always exist to define requirements for the product and review the results of the contractor's work. Funding for implementation projects can be up to 100% of the project's required budget.
Concept projects have the purpose to prepare the further development of existing ASAM standards or to prepare the development of new ASAM standards. The goals of concept projects are to propose specific content for ASAM standards and/or to provide justification for the usefulness, practicability and feasibility of the proposed content. For this purpose, a concept project can include:
• a feasibility study
• a requirements evaluation
• a technology survey
• the development of a prototype
• performance benchmarks.
Concept projects are typically chosen, when a Standard development project shall lead the market (not follow the market) and hence create new interfaces or methodologies that do not yet exist. Concept projects are also the right choice, when the content of the envisioned Standard is complex and requires significant resources to even develop a sound and solid project proposal.
The minimum deliverable of a concept project is a concept paper. ASAM supports concept projects with funds of up to 75% of the total required project budget.
Study projects provide members an organizational structure to study or analyze specific aspects of ASAM standards in a collaborative way. Study projects have the overall goal to enhance the understanding of ASAM standards, to promote their application in member companies and to create change requests for the further development of ASAM standards. This project type is specifically intended for members in regions, where ASAM standards are not well known.
Study projects have no expected deliverables other than a final report. The Standard development process does not apply for study projects in case that either no budget or a small budget is needed. Study projects are open to all ASAM members, i.e. also to members in a 'passive' membership class. ASAM may provides funding up to the limit for small budget projects.