Software Configuration Management for HP NonStop Ronald van Riet

Size: px

Start display at page:

Download "Software Configuration Management for HP NonStop Ronald van Riet"

Ruby Stewart
6 years ago
Views:

1 1 Software Configuration Management for HP NonStop Ronald van Riet

2 CrossPAC Software B.V The Netherlands Distributor 3rd party software Support and Helpdesk NetWeave PANORAMA XML Thunder PrimeCode

3 NetWeave Communications Middleware Message Passing / Queuing Remote Databases / Transactions HP NonStop UNIX Windows other HW

4 PANORAMA Source Code Analysis Programs / JCL High Level of Detail All platforms Most Languages Windows/UNIX client - UNIX server

5 XML Thunder XML Enable Legacy Applications COBOL and C Native Gaurdian Minimal Program Changes Full XML Implementations XML Enable Apps in hours SEPA Compliant in Weeks

6 Software Configuration Management The process of managing the development, change, distribution and installation of software applications throughout the entire software life cycle.

7 Software Life Cycle Change Change Required Required Change Change Approved Approved Development Development Promotion Promotion Approved Approved QA/ QA/ Test Test Promotion Promotion Approved Approved Production Production Enhancement Request Bug Fix Regulation Amendments New Applications New Releases Create/Modify Source Code Compile Executable ObjectsObject Source Version & Version Build/Modify Release Management Release Management Ends Initial Release Starts Here! Testing Here! Distribute Release Acquire Release Install Release QA Testing Distribute Release Acquire Release Install Release Manage Release

8 Referential Integrity: Develop and Package 1. Create/Modify Source Files multiple versions of each could have dependencies 2. Compile Objects performed by PrimeCode all references known all references/compilers locked 3. Package Release contains objects plus all references include any files types (eg. pics/docs, etc.) Many versions of each source file Package a release using components that include: objects and any other file types Source 001 Ver 1.01 Source 003 Ver 1.02 Additional source files Specific source versions used Object 001 Object 002 Object 003 Release 1.01 All components locked in Referenced source files Object 004 Segmented Source files from DDL Miscellaneous linked files

9 Referential Integrity: Promotion and Distribution 4. Promote Releases custom security access per environment all references/compilers locked 5. Distribute Releases all source/object versions known no missing components from QA DEV TEST QA PRODUCTION STAGING Distribution with audit trail Prod 1 Release 1.3 Release 1.2 Release 1.1 Release 1.0a Prod 2 Release 1.0b Prod 3

10 Managed component structure DDL section section segment segmented source file source 1 source 2 submit to PrimeCode library object 1 object 2 compile external object bind runnable 1 runnable 2

11 Managed component references All references managed automatically; DDL: individual sections; Source references created during submit to PrimeCode; Object references created during compile; Runnable references created during bind; Objects recompiled only when needed; Massive reduction of test time; Impact analysis; User changes.

12 User changes Group source changes; Manage as a single entity, not as many individual sources; Compile / promote / install; Multiple concurrent user changes; Increased manageability of development process

13 Why use SCM? Most outages are caused by planned changes

14 Why use SCM? Audit compliance; Improved reliability; Cost savings/improved productivity; Reduce downtime; Prevent fraud; Facilitates change impact analysis; Manage risk of doing business.

15 Audit Issues Reproducibility of applications; Audit trail of changes; Division of responsibilities; Secured repository access; ENRON spawned Sarbanes-Oxley: SOX gives us a headache ; SocGen to spawn new requirements?

16 Reducing errors Multiple versions: Which is the correct one? Change source: Easy to forget bug fix; Change source: Which applications are affected? Releases: Are the right pieces included? Bug fix: Is it included in Prod & Dev? Changed make file? Can t reproduce object; Multi user fix? May overwrite other s change.

17 Costs savings More efficient through fewer errors/better management; Automated process; Reduce potential for downtime (risk management); Reduce actual downtime: less searching is required, no components to re-create, easier analysis possible.

18 PrimeCode Features Manages ALL Types of Components; Manages Relationship Information; The only End-To-End Solution Specifically Designed for HP NonStop.

19 Product Structure Core system on Guardian ( RMS ); Repository in Enscribe files GUI front end on PC (PrimeCode); Full support for OSS / Integrity; ALL languages supported: COBOL, SCOBOL, C, C++, TAL, Java, ; Guardian security + internal security

20 PrimeCode versions UltraLite includes Source version control only, DDL granularity; Lite also includes Managed compiles, User changes; Full also includes Releases Install / distribute / acquire Smooth upgrade path

21 Optional Modules ACP: Automated Change Policy CRW: Custom Report Writer RTC: low cost, low impact RSC replacement

22 Third Party Applications (Examples) ACI Logica Alerie efunds BASE24 BESS ATLAS ADVANTAGE

23 Major Benefits AUDIT COMPLIANCE Sarbanes-Oxley RELIABILITY of software applications PRODUCTIVITY in development, testing and production support MANAGE RISK of planned software changes

24 PrimeCode European Customers (Partial list) ATOS/Euronext Banksys BBS Belgacom La Caixa Barcelona Caja de Madrid Crédit Agricole Deutsche Bank Equens Euroclear HSBC ING Bank KPN Telecom LloydsTSB Nationwide Rabobank Royal Bank of Scotland Société Générale Swedbank

25 PrimeCode American Customers (Partial list) ABN AMRO Alerie AT&T Bank of America Bank of Nova Scotia Chicago Mercantile Exchange CIBC Comerica Hertz MasterCard New York Board of Trade Sungard Financial Toronto Stock Exchange US Bank Wachovia Wells Fargo

26 PrimeCode versus simple version control Manage objects as well as sources; PrimeCode managed component structure: Versions/states/bugfixes/DDL granularity Users of version control only tools move to PrimeCode due to increased auditing requirements (e.g. Sarbanes-Oxley); With mergers, all mixed environments have converted to PrimeCode; No conversion away from PrimeCode ever.

27 Customer testimonial #1 Top 5 US Brokerage firm; Bi-weekly bug fix releases; Frequent problems with releases proved difficult and time-consuming to analyze and fix; In 2½ years of using PrimeCode, not a single software release problem encountered.

28 Customer testimonial #2 Top 10 US Bank; BASE24 from test to production without full testing; Errors often took weeks to fix; With PrimeCode, problems completely eliminated due to tight QA control over release contents.

29 PrimeCode is for HP NonStop what Endevor is for IBM Mainframes

ITP-PANORAMA. Welcome to our presentatíon at

ITP-PANORAMA. Welcome to our presentatíon at ITP-PANORAMA Welcome to our presentatíon at V4.0_1 ITP-PANORAMA is supportig all Stragegies for Legacy Software Application Mining and Modernization with ITP-PANORAMA Presentation by: Juergen Overhoff