Modernizing Software
Software is constantly ageing. It ages not only because the technology is constantly evolving, but also because the business environment and thus the demands on the software usually change faster than the software can be further developed. On the other hand, it must be recognised that software has made the company's success possible in the first place.
This training shows tried and tested procedures for modernising existing legacy software. This includes finding out what is particularly important and deciding objectively whether the effort for a measure is worthwhile at all. You will learn both proven approaches to revise existing software and approaches to supplement it with new software, possibly even to replace it completely in the long term.
Learning Objectives
- You can analyse the entrepreneurial and economic context of software
- You master working techniques to modernise existing code
- You know concrete procedures to improve legacy software step by step
Target Audience
Developers and maintainers of existing systems who spend too much time maintaining legacy software and want to implement changes and enhancements more quickly in the future.
Requirements
Attendees should have at least 1-2 years of experience programming with PHP or a similar programming language. They should have experience with procedural and object-oriented programming and be confident in using an IDE and common development tools such as the version control Git.
Modernizing Software 1.199,- EUR
4 Online Sessions á 180 minutes
No date is currently planned for this training.
-
Introduction
Duration: 180 minutes
- Welcoming, introducing and collecting expectations
- The Legacy Dilemma
- Refactor or Rewrite?
- Where the journey is heading: strategy and vision
- Profitability and business value
- Discussion of the work assignment
-
Preserve
Duration: 180 minutes
- Joint review of the work assignments
- Migration up to PHP 7
- Migration after PHP 7
- The chicken and the egg: test automation
- Characterization Tests
- Discussion of the work assignment
-
Replace
Duration: 180 minutes
- Joint review of the work assignments
- Use cases and overweight software
- The framework: Accelerator or brake block?
- Branch by Abstraction
- Left or right?
- Discussion of the work assignment
-
Blueprints
Duration: 180 minutes
- Joint review of the work assignments
- Autoloading
- Explicit Dependencies
- Global State and Immutability
- Decoupling through events
- Feedback and Closing
Ihr Trainer
Stefan Priebsch
inspires with a combination of new ideas and field-tested approaches.
Exclusive and customized?
We are happy to conduct any training exclusively online ("in-house") for you. We adapt the content and focus to your specific wishes and needs and optionally work with examples directly from your code base.