We look through source code
AVESOR® - Basis for Modernization Projects
Individually developed IT systems grow over decades and are permanently extended and adapted.
This leads to the fact that a system, which in the beginning excellently supported the operational processes, has developed into a monolithic software system with high technical debts.
See here an example of technical debts of a real Cobol software system. It is not surprising that necessary adaptations and extensions of such systems take endless time and cause enormous costs.
An essential success factor for the modernization of monolithic systems is to know the nature of the legacy system, its scope and dependencies.
AVESOR® Sourcecode Assessments evaluate legacy systems in detail and traceably according to 14 measurement criteria. The evaluation is performed in a depth that is impossible to do manually.
Modernization projects thus receive valuable input, not only with regard to the sizes and complexities of the legacy system, but also:
- Dependencies - both of source programs among themselves, but also of files, job controls, etc.
- Dead source programs - inaccessible programs that were never deleted for "security reasons" but no longer fulfill any function and are also inaccessible.
- Duplicates - source programs that were duplicated and slightly modified years ago. However, the original program was never deleted for "security reasons" - and even worse: it can still be reached in exceptional cases.
- Anomalies - detected anomalies in the source programs are marked and described per source program.
Your challenge:
- You have a software system that has grown historically
- Your core system consists of many source programs with many dependencies and enormous complexity Changes take longer and longer - see an example of technical debt of a Cobol software system .
- Only a few developers have - in the best case - an overview of individual subareas
- Developers are close to retirement or have already left the company
- The "truth is in the source code" - time-consuming code analyses are the result
- Recruiting for new talent is extremely difficult
- Programming technology has long since ceased to be taught
- Herculean task for new employees
- It is enormously difficult for new employees to find their way around such grown software structures.
- Technologies (for example Cobol), which have not been taught for a long time, have to be learned and mastered.
- Loss of know-how
- Existing team is already retired or about to retire
Our services:
- Sourcecode Assessment - because: "The truth is always in the source code"
- Kick-off (approx. 1 hour)
- Execution of the assessment - participation of your employees is not necessary
- Quality assurance of the results
- Final meeting and handover
- AVESOR® algorithms for the analysis of Cobol, RPG and PL/1
- Further programming languages in progress and on request
- AVESOR® algorithms can be individually adapted to your specific requirements (e.g. duplicate recognition, anomalies)
- Results
- Identified and measured technical debts
- All measured values of the source programs
- System dependencies
- Dead programs
- Candidates for program duplicates
- Anomalies
- File and DB usage across the entire system
- Result representation in 2D for screen/tablet or, if desired, in 3D virtual reality
- virtual reality
- We are the first - and so far the only one - able to represent the software architecture of legacy systems in virtual reality. Your employees can interactively analyze your system with the VR glasses Oculus GO.
- Film about AVESOR® (2:35 min)
Fact Sheet AVESOR® Explorer
From practice
- System scope: several thousand individual programs, copy files, etc.
- Dependencies and high linkages turn new releases into "nail-biting games“
- "Dead programs" as well as many "nearly" identical programs drive up the time requirement for manual code analyses
- Only very few developers see through parts of the entire system
Benefits / Results (excerpt)
- Identified "dead programs" and nearly identical programs
- Complexity hotspot identified
- Identified programs that can affect the entire system when changed
Execution
- Virtual execution (MS Teams, Webex, Zoom)
- On-site (for special needs)
- Duration: 2 Sprints
Price models
- Pay per use (number of elements examined)
- Annual fee for recurring, periodic tracking of the development of your legacy system