| API | Application Programming Interface | “In computer programming, an application programming interface (API) is a set of routines, protocols, and tools for building software and applications.” Source: Wikipedia: Application programming interface |
| CI | Continuous Integration | “The practice, in software engineering, of merging all developer working copies to a shared mainline several times a day.” Source: Wikipedia: Continuous Integration |
| CT | Continuous Testing | “The process of executing automated tests as part of the software delivery pipeline to obtain immediate feedback on the business risks associated with a software release candidate.” Source: Wikipedia: Continuous Testing |
| CIT | Continuous Integration and Testing | A combination of CI and CT |
| COTS | “Commercial Off the Shelf.” | “Software and services are built and delivered usually from a third party vendor.” Source: Wikipedia:Commercial off-the-shelf |
| HCI | Human-Computer Interface | “... the point of communication between the human user and the computer.” Source: Wikipedia: Human-Computer Interaction |
| REST | Representational State Transfer | “An architectural style consisting of a coordinated set of architectural constraints applied to components, connectors, and data elements, within a distributed hypermedia system.” Source: Wikipedia: REST |
| RI | Research Infrastructure | “A seamless social science data archive service for the whole of the European Research Area (ERA), which is capable of supporting the research needs of the next generation of social scientists wherever in Europe they may be, or beyond.” Source: CESSDA SaW project overview |
| SCM | Source Code Management [system] | A system for “the management of changes to … computer programs.” Source: Wikipedia: Version Control |
| (application) | Application | An engineering view of the collection of Components that make up a Product |
| (application code) | Application code | The software source code that an Application's Components are made up of |
| (component) | Component | an individual part of an Application (e.g. Elasticsearch for CVS, Searchkit for CDC) |
| (product) | Product | A deployed Application (e.g. CDC, CVS, DVS, EQB) |
| (management tool) | Management tool | A third party application used for supporting CESSDA services (eg. Jenkins CI/CD, Prometheus etc) |
| (service) | [software] Service | An overall user experience (e.g. CDC, CVS, DVS, EQB); a User-centric view of an application, including documentation and support |
| (software artefacts) | Software artefacts | Software Products, Applications, Services Components |
| (technical debt) | Technical debt | “Work that needs to be done before a particular job can be considered complete or proper. If the debt is not repaid, then it will keep on accumulating interest, making it hard to implement changes later on.” Source: Wikipedia: Technical debt |
| (usability) | Usability | “The degree to which a product can be used by specified consumers to achieve quantified objectives with effectiveness, efficiency, and satisfaction in a quantified context of use.” Source: Ergonomic Requirements for Office Work with Visual Display Terminals, ISO 9241-11, ISO, Geneva, 1998 |
| (deployment) | Deployment | A particular configuration of an Application running on the CESSDA Technical Infrastructure |