Validata Automated Build & Configuration (ABC)

1. Validata Automated Build & Configuration (ABC) Achieve continuous delivery through automated build and configuration management

2. Agenda 1 Business Challenges Validata Automated Build & Configuration 2 3 Validata Build & Configuration Methodology Validata Build & Configuration Process 4 5 Reporting Capabilities 6 Benefits

3. Business Challenges Controlling source code and artifacts development is a critical part of modern software development. Rarely is software shipped on schedule, on budget, and with the features and stability desired in the original specifications. CIOs face several problems trying to manage their software releases. A detailed picture of the current release process is usually not available whereas a regular release cycle is not established. At the same time the process of developing new releases is usually insufficient since there is an intense need of repeating the cyclic approach until the desirable results are reached. Traditional CM tools are file based and their support for continuous actions of check-in and build introduce new challenges to their design. This continuous integration and build practice, places considerably more stress and load on the CM version control and build systems. Automating and standardizing the Release Management procedure, helps eliminate the repetitive tasks, reduce the required resources and ensure that all inputs and outputs are consistent at all times.

4. Validata Automated Build & Configuration (ABC) Validata ABC, enables IT organizations to automate the process of application upgrades – patches, resulting in shortened release cycles, application configuration alignment, and automated updates across any groups, sites, countries. Unlike traditional solutions, Validata ABC is faster, smarter and more efficient with an underlying infrastructure to support continuous actions of check-in and build. It is a next generation CM tool trulyintegrated with Validata SAS ALM platform. It has the ability to instantly build the application; right after a developer had committed changes to the source code repository. Imagine to immediately know the build was broken and who made the most recent changes, and all packages produced to have an easy way to display version ID on request. Grab the release on its journey from QA to production! Create a ‘release map’ where every piece had a unique identifier build in the code itself that could be retrieved easily – even while it was running and be able to regenerate the ‘release map’ based upon the current code running in production. Compared this to the ‘release map’ that you had packaged, with the release of the time of deployment, that’s when you can find that you had the wrong scripts running in production! Being able to do a CM audit, even while production was live, is where Validata ABC is unique. The product aims in speeding up the process of applying patches and upgrades to T24 servers by up to 40-50%. It allows for even less technical personnel to perform the administration tasks and maintain a number of servers at a time. The comprehensive reports help controlling the overall maintenance process of keeping multiple environments in sync.

5. Configuration Management Build Automation Package and Deployment Automation Validata ABC Capabilities • Role-Based tool supporting workflows, ensuring different teams follow the same processes. • Full history and audit trail of configurations. • Supports parallel development across local and off shore teams. • Environments management and comparison • Configurations Conflict Detection • Ability to merge or branch different version of the same source files and records. • Integrates with the ALM platform and leverages unified central repository and Dashboard • Stores source code and data, requirement documents, specifications, web pages • Build Configurable workflows enforced through the use of Transition Rules • Ability to manage any number of builds through an automatic version and release control for each component • Ability to track the builds, highlighting the status of the work, requirements coverage and source versions • Integrates with other development tools such as Eclipse, Visual studio • Integrated GUI for Driving T24 Compilation and Display of Error Messages • Rollback of Deployed Data Records and Code Objects • Build Management for T24 using Toolbox. • Advanced control over the automated build process flow • Create, store and release deployment packages • Deploys T24 records using OFS messages (Input and Authorize commands) • Referential integrity, code analysis and deployment ordering reporting • Generation of BUILD.CONTROL packages containing all development and necessary settings • Setting Prerequisite Actions and Post Deployment Actions as part of the deployment procedure • Backup procedure for all affected libraries • Generates DL.DEFINE packages

6. Validata ABC Process Flow

7. Validata Build & Configuration Methodology Planning Build Release • Entry Criteria • New Change request has been issued and has been approved by the QA department following the workflow • Activities • Create the development plan and Schedule the related Tasks to the assigned users. Upload the plan in to Validata • Create the Project workspace in to Validata • Inherit existing finished development and upload in to Validata ABC any needed source code and records • Deliverables • Development Monitoring and Reporting with associated tasks per change request • Entry Criteria • New Tasks have been Scheduled and assigned to the developers • Development Work packages have been defined • Activities • Ensure all the related source code to be Checked-in on Validata server • Ensure that all branched versions of the source code have been merged • Run all automated reports to check the build integrity • Deploy the completed development to the testing environments • Create a baseline to include all the development packages • Deliverables • Completed Development reporting with the related tasks, source codes and records • Entry Criteria • Baseline has been planned and content has been confirmed • Baseline impact analysis report has been created and verified • Activities • Deploy the Baseline to QA environment for testing • Deploy the Baseline to Pre-Production environment for Testing • Run the automated environments comparison reports to identify any differences • Cut the Baseline • Update all the related change requests with status closed • Notify the related stakeholders • Deliverables • Change request coverage status • Deployment reporting and environments comparison

8. Validata Best Practices Workflow

9. Build & Configuration Functionality Workflow Validata ABC imports patches from Temenos, allows review and modification, then generates another package with the amendments and deploys it using the BUILD.CONTROL tool. As part of the deployment procedure Validata ABC can do Prerequisite actions as well as Post installation actions. Incoming T24 Patch (BCON Package) DL.DEFINE Import Wizard Validata SAS Project Integrity Checks Modifications BUILD.CONTROL Adapter Prerequisite Actions BUILD.CONTROL Tool in T24 Post Install Actions T24™

10. Multi-Company Deployment and Multi-Country Roll Out Manual Deployment of Upgrades or Patches Automatic Deployment of Upgrades or Patches Vendor Patch Upgrade Vendor Automatic Deployment of the package from Validata ABC Manually Deployment of the package. Issues Verified System Current System Upgraded System Current System Backup Deployment Testing Current System

11. Multi Company Deployment & Multi Country Roll Out In our days the main Base code development gets implemented at the main development site or it is out sourced to the vendor. When ready and tested, gets shared and delivered at the business sites where now it has to be combined with the local developments, get tested and communicate with several interfaces. Base Code • Remote Release Management Capabilities • Fully automated Deployment (records, data, objects, versions) • Role Based • Integrity of the Build • Pre-screening for any potential errors in any environment • Rollback of changes upon failure or at user request • Multiple Catalogues support (Multiple Versions ) • Independent staging area • Benefits • Reduce Deployment errors • Reduce defects and improve consistency in packages across environments • Accuracy during package development, promotion, and deployment across environments. • Reduced deployment costs through increased effectiveness and accuracy • Reduce downtime by ensuring consistency in configurations across multiple environments . • Lower downtime costs through the ability to back out changes on demand or upon failures in any environment. Base Code & Local Code Base Code & Local Code Project Contains Core + Local Development for UK Site Project Contains Core + Local Development for Poland Site

12. Build & Configuration Architecture Lifecycle Stream Support Streams Core Change Management Artifacts Products / Packages Tasks Change Packages Product Baselines Lifecycle Management Artifacts Requirements Activities/ Features Defects Builds Documents Custom Extension Support APIs Third Party tools High Efficiency Architecture Multisite Transaction Engine Workflow Engine Custom Actions Reporting / Comparisons Hybrid database

13. Receive Build Request Plans and Workflows Change Request BPO Build Manager Assigns & Monitors Tasks • The Build manager Gets an alert for a new Change Request • Uploads the Development Planning in to Validata Project Plan Manager Module ( MS Project Integration point) • For this CR he needs to create the related Work Package and the Tasks for development • Then he create the Project and inherits the previous Development. He has the option to import previous development with Completed Tasks, or latest deployments with status Tasks still on going

14. Reports Release Planning report Export to Excel Release Status Report Release Planning report: Release Schedule with live reports of the status of your product, showing how the multiple teams meet the requirements and the deadlines for the active tasks. Traceability Report Releases Streams Overview

15. The Critical Differencies • Efficiency and Quality throughout the project • Reduced Deployment errors, associated with interdependencies between applications, software requirements, work packages, tasks and environments achieving efficiency and quality throughout the project. • Reduced Costs and Effort • The increased effectiveness and accuracy of distributed application rollouts across environments reduce actual deployment costs and effort while enabling faster time to market. • Ensures Higher Product Quality • Granular access controls achieve accuracy during package development, promotion, and deployment across environments, ensuring higher product quality. • Continuous delivery and integration • Supports parallel development, multiple releases maintenance and manages file revisions rather than software versions. It guarantees the integrity of every build • Reduced Downtime • Ensures consistency in configurations across multiple environments actually reduces downtime and related costs.

16. ? Do You Have Any Questions? ? ? We would be happy to help.