Transcript PowerPoint Template

Validata Automated Build & Configuration (ABC)
Achieve continuous delivery through automated build and configuration management
Agenda
1
Business Challenges
2
Validata Automated Build & Configuration
3
Validata Build & Configuration Methodology
4
Validata Build & Configuration Process
5
Reporting Capabilities
6
Benefits
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.
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 truly
integrated 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 4050%. 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.
Validata ABC Capabilities
Configuration
Management
• 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 Automation
• 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
Package and Deployment
Automation
• 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
Validata ABC Process Flow
Administration
Business
Requirements
Gathering
Software
Requirements
Gathering
Validata Setup
Synchronize per
T24 environment
Define
Release Stream
Release Iterations
Business Change
Requests
Gathering
Project Setup
Define
Development
Project Plan
Define Software
Change Requests
Access Rights,
Users and Roles
Define
Development
Requirements
Defects Gathering
Testing Results
Testing Process
Transition rules /
Workflow
processes
Assign
Development
Tasks
Validata
Connectivity with
the WorkStations
Development
Unit Testing
Deployment
Functional Testing
QA Testing
Release
Management
Validata Build & Configuration Methodology
Planning
Build
Entry Criteria
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
 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
 Development Monitoring and
Reporting with associated tasks per
change request
Deliverables
 Completed Development reporting
with the related tasks, source codes
and records
Release
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
Validata Best Practices Workflow
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
Integrity Checks
Validata SAS Project
BUILD.CONTROL Adapter
Prerequisite Actions
BUILD.CONTROL Tool in T24
Post Install Actions
T24™
Modifications
Multi-Company Deployment and Multi-Country Roll Out
Manual Deployment
Automatic
DeploymentofofUpgrades
UpgradesororPatches
Patches
Vendor
Patch
Upgrade
Current
System
Vendor
Automatic Deployment
Manually Deployment
of the package from
of the package.
Validata ABC
Backup
Current
System
Current
System
Deployment
Upgraded
System
Testing
Verified
Issues
System
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.
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 )
Base Code
&
Local
Independent staging area
Code
Project
Contains Core + Local
Development for UK Site
Benefits
Base
 Reduce Deployment errors
 Reduce defects and improve
Code
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 configurationsPoland
across
multiple environments
.
Base Code
&
Local
 Lower downtime costs through the
ability to back Code
out changes on demand
or upon failures in any environment.
Project
Contains Core + Local
Development for Poland Site
Build & Configuration Architecture
Lifecycle
Stream
Support
Streams
Core Change
Management
Artifacts
Products / Packages
Lifecycle
Management
Artifacts
Requirements
Tasks
Activities/
Features
Custom
Extension
Support
High
Efficiency
Architecture
Change Packages
Defects
Product Baselines
Builds
Documents
Reporting /
Comparisons
Hybrid
database
APIs Third Party tools
Multisite
Transaction
Engine
Workflow
Engine
Custom
Actions
Receive Build Request
Plans and
Workflows
BPO
Change
Request
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
Reports
Release
ReleasePlanning
Planningreport
report: Export to Excel
Release
Report
ReleaseStatus
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
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.
Do You Have
Any Questions?
We would be happy to help.