Definition: Existing IT systems are reused, before deciding upon buying or even building them. Taxpayers money can only be spent once. Reusing existing systems is a lot cheaper that buying new systems or even building them. In most cases, the requirements of public administrations are not very specific, and existing systems are sufficient to support the processes. It may seem that the costs of building new IT systems can be acceptable, but the costs of the maintenance and support of these systems are often forgotten and are much higher than the cost related to the initial development. When requirements for IT support arise, it is first determined whether systems that provide similar functionality are already available in the organization or otherwise in the market.Requirements that are not supported by existing systems are critically analyzed to determine whether they are really essential.Processes are adapted to existing systems or standard systems that are available in the market, when possible and acceptable.Building new IT systems is only considered a last resort when no existing systems exist or cannot fulfil essential requirements.""
Source: Reusability Underlying Principle (4) of the European Interoperability Framework (EIF)
Source reference: https://joinup.ec.europa.eu/collection/nifo-national-interoperability-framework-observatory/glossary/term/reusability
Last modification: 2024-01-17
Identifier: http://data.europa.eu/2sa/elap/reuse-buy-build
LOST view: TVA-Functional Architecture Principles
EIRA concept: eira:ArchitectureBuildingBlock
ABB name: elap:reuse-buy-build
Title: Reuse, before buy, before build
EIF Layer: N/A
skos:broader: eira:EuropeanLibraryofArchitecturePrinciplesPrinciple
|
|
dct:type | elap:reuse-buy-build |
dct:title | Reuse, before buy, before build |
eira:PURI | http://data.europa.eu/2sa/elap/reuse-buy-build |
dct:modified | 2024-01-17 |
eira:definitionSource | Reusability Underlying Principle (4) of the European Interoperability Framework (EIF) |
eira:definitionSourceReference | https://joinup.ec.europa.eu/collection/nifo-national-interoperability-framework-observatory/glossary/term/reusability |
eira:concept | eira:ArchitectureBuildingBlock |
eira:view | TVA-Functional Architecture Principles |
eira:view | SV-Functional Architecture Principles |
eira:view | Architecture Principles view |
eira:eifLayer | N/A |
skos:definition | Existing IT systems are reused, before deciding upon buying or even building them. Taxpayers money can only be spent once. Reusing existing systems is a lot cheaper that buying new systems or even building them. In most cases, the requirements of public administrations are not very specific, and existing systems are sufficient to support the processes. It may seem that the costs of building new IT systems can be acceptable, but the costs of the maintenance and support of these systems are often forgotten and are much higher than the cost related to the initial development. When requirements for IT support arise, it is first determined whether systems that provide similar functionality are already available in the organization or otherwise in the market.Requirements that are not supported by existing systems are critically analyzed to determine whether they are really essential.Processes are adapted to existing systems or standard systems that are available in the market, when possible and acceptable.Building new IT systems is only considered a last resort when no existing systems exist or cannot fulfil essential requirements."" |
skos:broader | eira:EuropeanLibraryofArchitecturePrinciplesPrinciple |