Definition: Deployment stamps are a non-functional requirement that refers to the need for a system to have a timestamp or version number associated with each deployment. This allows for easy tracking and identification of different versions of the system, as well as the ability to roll back to a previous version if necessary. Deployment stamps are important for ensuring the stability and reliability of a system, as well as for facilitating efficient and effective maintenance and troubleshooting. Source: TOGAF Source reference: https://pubs.opengroup.org/architecture/togaf9-doc/arch/chap03.html Additional information: According to the TOGAF specification, Deployment stamps are a non-functional requirement that pertains to the deployment of software applications. This requirement specifies that each deployment of the software application must be stamped with a unique identifier that indicates the version of the application that has been deployed. The purpose of this requirement is to ensure that the deployment process is traceable and auditable. By having a unique identifier for each deployment, it becomes easier to track changes and identify any issues that may arise during the deployment process. The deployment stamp should be generated automatically by the deployment tool or system and should be stored in a central repository. This repository should be accessible to authorized personnel who need to track the deployment process. In addition to the unique identifier, the deployment stamp should also include information such as the date and time of the deployment, the environment in which the application was deployed, and any other relevant information that may be useful for tracking and auditing purposes. Overall, the Deployment stamps non-functional requirement is an important aspect of ensuring that the deployment process is traceable and auditable, which is essential for maintaining the integrity and reliability of software applications. Example: Deployment stamps refer to the requirement that each version of the software being deployed must have a unique identifier or timestamp associated with it. This helps to ensure that the correct version of the software is being deployed and that any issues can be traced back to a specific version. For example, a banking application may require deployment stamps to ensure that the correct version of the software is being used to process financial transactions. LOST view: Digital Solution Non-Functional Requirements Catalogue view Identifier: http://data.europa.eu/dr8/egovera/DeploymentStampsRequirement EIRA traceability: eira:DigitalSolutionNonFunctionalRequirementRequirement ABB name: egovera:DeploymentStampsRequirement EIRA concept: eira:ArchitectureBuildingBlock Last modification: 2023-05-16 dct:identifier: http://data.europa.eu/dr8/egovera/DeploymentstampsRequirement dct:title: Deployment stamps Non-Functional Requirement