Deliverables

You are here:

Like all publicly funded research projects, we from AI4SWEng will produce a number of “deliverables” throughout our project, typically in the form of written reports. We will make many of these reports available publicly and you will be able to access them directly from this page once they are ready.

NumberNameLead PartnerDue DateStatus
D2.1Systematic protocol for AI-based software developmentIdenerM12in progress
D2.3Needs re-elicitation and governance organisationErgTechM16planning
D2.4Requirements and report for data preparation activitiesForthM05completed
D2.6Functional and non-functional requirements and use-case requirementsInnova IntegraM12in progress
D3.1Data provenance, preprocessing, curation and cleaning, data privacy and security protectionCEAM28scheduling
D3.5AI-based software performance monitoringITCLM36scheduling
D4.1AI-powered tools and frameworkForthM36scheduling
D4.2Unit testing toolsETCHM36scheduling
D5.3Validation of tools use-cas scenarios for prototypical application domainsEurecomM36scheduling
D5.4Use-case implementations, evaluation, validation and KPI assessmentATTPharmaM36schedulnig
D6.1Evaluation of AI-powered tools and model performanceBitnetM40scheduling
D6.3Optimisation of tools based on evaljuation resultsITCLM36scheduling
D6.4Report for ethical, legal and social impact assessment and AI auditUniversity of ReadingM40scheduling
D7.1The initial plan for communication, dissemination and exploitation of results (PCDER)ErgTechM1completed
D7.2The final plan for communication, dissemination and exploitation of results finalErgTechM18planning
D7.3Exploitation and business planning (initial)CEAM12planning
D7.4Exploitation and business planning (mid)CEAM24scheduling
D7.5Exploitation and business planning (final)UniBZM42scheduling
D7.6Report of D&C&E activities (initial)Innova IntegraM12in progress
D7.7Report on D&C&E activities (final)Innova IntegraM42scheduling
D7.8Software developer training reportUniversity of ReadingM42scheduling
D7.9Road-mapping AI-supported developmentUniBZM42scheduling

Some explanations about the table: each of our deliverables has a unique “D” number (first column), a title (second column), an organisation from our consortium that is responsible for getting the deliverable completed on time (third column), a due date (shown here in “months after the start of the project” in the fourth column) and a current status (fifth column).

We usually have to wait with releasing our deliverable documents to the public until they have been officially “approved” by our European and Swiss funding bodies, which means that sometimes “completed” deliverables will not yet be available for download. If you notice that, please check back at a later time and you should be able to access the document then.