ECHA/2020/666  Annex 1 to Tender Specifications  Technical Specifications Restricted  52 (77) P.O. Box 400, FI-00121 Helsinki, Finland | Tel. +358 9 686180 | echa.europa.eu  Deliverable  Description  description, tags, and any scope and/or effort deviation  occurred.  Business and  functional  requirements Document aimed at capturing the desired functions and data of a  system at a high level and its intended users (including legal and  regulatory requirements). This may also include gap analyses of  the functions provided by existing (data) architecture  components, enterprise and conceptual data models, data  glossary and reporting mock-ups.  Technical/  non-functional  requirements Architecture and design documents describing changes or  additions to the (data) architecture, logical data models or the  technology stack of the solution and the non-functional aspects  expected such as availability, performance and security.  Software/data  architecture  document  Updated to reflect design or architectural changes and the  technology stack  Master test plan  document detailing how the requirements will be tested and test  cases including end-to-end. First version further detailed in the  Elaboration phase. (sprint) Release  notes  Details on the released system version, including new features,  changes, enhancements and fixes against the previous version.  Deployment kit and  instructions  Deployment package, scripts, deployment instructions  1. Fully tagged, baselined, code and scripts  2. Packaged binaries of the application components in JAR,  WAR, Docker image, NPM or any other applicable  packaging format, deployed to the appropriate package  repository manager at ECHA.  3. ETL and reporting objects: flows, load plans, topology  files etc.  4. Configuration management code  5. Automation configuration (jobs)  6. Material for scripted installation 7. Comprehensive environment / architectural descriptions  8. Servers with role descriptions and capacity requirements  9. Software requirements (including OS versions, database  and application server release numbers, java  environment requirements, network requirements.)  Set-up scripts and instructions 10. Set-up scripts must be parameterised enabling ECHA to  use the same scripts for all environments  11. Set-up scripts should require a minimal amount of human  intervention, in other words, they should be automated to  the full extent possible;  12. Set-up scripts should be idempotent and re-entrant to the  extent possible (for example, an idempotent script that  updates DB schemas should be written in such a way that  it identifies whether the DB has already been updated. If  it has, the script should exit with no changes made. A re- entrant script will identify a partial update and continue  where e.g. a previously failed execution has stopped). 