English (United Kingdom)

https://curated-unify.zendy.io/wp-json/zendy-region/v1/featured_content/oa?rat=en

https://curated-unify.zendy.io/wp-json/zendy-region/v1/highlighted_journal/

Global: Zendy Tools annual

Presents the keyphrase highlighting as premium feature

Keyphrase Highlighting

Presents the summarisation as premium feature

Summarisation

Insights

Presents the pdf analysis as premium feature

PDF Analysis

Presents the zaia usage as premium feature

ZAIA

Global: Zendy Tools monthly

Global: Zendy Plus monthly

Presents the access of premium content as premium feature

Premium Content

Global: Zendy Plus annual

Global: Zendy Free Plan

An ever shorter technology lifecycle engendered the need for assessing newtechnologies w.r.t. their market readiness. Knowing the Technology readinesslevel (TRL) of a given target technology proved to be useful to mitigate riskssuch as cost overrun, product roll out delays, or early launch failures.Originally developed for space programmes by NASA, TRL became a de factostandard among technology and manufacturing companies and even among researchfunding agencies. However, while TRL assessments provide a systematicevaluation process resulting in meaningful metric, they are one dimensional:they only answer the question if a technology can go into production. Hencethey leave an inherent gap, i.e., if a technology fulfils requirements with acertain quality. This gap becomes intolerable when this metric is appliedsoftware such as technological cybersecurity measures. With legislation such asthe General Data Protection Regulation4 (GDPR) and the Network and InformationSystems Directive5 (NIS-D) making reference to state of the art when requiringappropriate protection measures, software designers are faced with the questionhow to measure if a technology is suitable to use. We argue that there is apotential mismatch of legal aim and technological reality which not only leadsto a risk of non-compliance, but also might lead to weaker protected systemsthan possible. In that regard, we aim to address the gaps identified withexisting Technology Readiness Assessment (TRA)s and aim to overcome these bydeveloping standardised method which is suitable for assessing software w.r.t.its market readiness and quality (in sum maturity).

SMART: a Technology Readiness Methodology in the Frame of the NIS Directive