160 likes | 377 Views
Version Control 101 – The SimCorp Way. Dyalog User Conference 2007 Lars Stampe Villadsen, SimCorp A/S (Denmark). Agenda. Company presentation (short ) Low level parts Implementation Show some code. Business Idea.
E N D
Version Control 101 – The SimCorp Way Dyalog User Conference 2007 Lars Stampe Villadsen, SimCorp A/S (Denmark)
Agenda • Company presentation (short ) • Low level parts • Implementation • Show some code
Business Idea • SimCorp offers integrated software solutions to financial service providers supporting their activities worldwide on the financial markets. Our solutions are firmly based on our high quality standards and our insight into financial theory, methods and practices.
SimCorp History • 2007 SimCorp sells IT2 • 2003SimCorp Dimension • 2000 TMS2000 full STP product • 1999 IT2 acquired to substitute TRACTS • 1998 TMS2000 most important product • 1997 Sale of Actuarial department • Official launch of TMS2000 • 1996 First TMS2000 implementations • 1995 TMS2000 development intensified • Getting Focused • 1991 Risk management modules • 1990 Financial analytics and library • 1985 Building society systems • Money market systems • Pricing models for derivatives • Treasury systems SimCorp Dimension era Customised software
The low level parts • SimCorp Dimension consists of (Version 4.2): • 37.000+ APL functions • 150.000+ APL structures Defining tables, forms, menus ect. • 2.200+ files (exe’s / dll’s / reports / manuals / 2 WS…) • Is developed by (Version 4.2): • 170+ Developers
Contents: We need to know what an application version consists off – i.e. identify the functions (easiest), the database tables, the forms, the menu’s the WS, the exe’s, the dll’s and alike. The low level parts cont.
The low level parts cont. • We need version control:
The low level parts cont. • Each of the 180.000+ elements (or objects as we call them) is version controlled separately i.e. they are assigned a version number. • The SimCorp Dimension repository holds more than 1.800.000 deltas.
The low level parts cont. • Each version of an element (delta) must be assigned to an application version. • A version of an element can be assigned to more than one application version. • (Each version must be assigned to a change request registered in our Change Management System)
How it is implemented (infrastructure) 4.2 4.1 4.0 Release Test Shipped version
v237 v238.1.1 How it is implemented (infrastructure) cont. Release test and Shipped version periods progFilesDir v238
Registered (-9) All develop and CR tasks completed (and no dependencies) Ready for test (-1) All test tasks completed (and no dependencies) Approved (1) All quality control jobs have run without findings (both test and technical) Released (2) How it is implemented (infrastructure) cont. Every 10 min Once a Day Mornings when succesfull
Registered Approved Released Ready for test How it is implemented (infrastructure) cont. Released to customers Start of changes Approved Versions Test and Public Versions Repository/Patch Version
Show some code… • Enough Said… • Lets look at some CODE.