Contenu connexe Similaire à Arguments in favor of a progressive software rewrite (20) Plus de Sylvain Leroy (8) Arguments in favor of a progressive software rewrite 1. Arguments in favor
of a progressive
webapps
Automatic legacy software migration
https://www.byoskill.com
5. 5©2015 – Confidential, metrixware
❖ Software ages
❖ Software becomes irrelevant
❖ Software may have broken concepts
❖ Software without love :-(
❖ Fashion is gone
We help a lot of software
6. 6©2015 – Confidential, metrixware
Our unique
skills
● Source to source refactoring
● Static code analysis
● Code (re) generation
7. 7©2015 – Confidential, metrixware
Our tools
Transform the code and
the architecture automatically
➔ Speed up the upgrade of a software
➔ Replacing outdated technologies
8. 8©2015 – Confidential, metrixware
Your gain
➔ Increase the success-rate of
rewrite projects
➔ Shorten the “out of order” effect
➔ Decrease the cost and risk of
migration
11. 11©2015 – Confidential, metrixware
A common (current) wish :
Transform a monolith application
Into a SaaS/Cloud based solution
13. 13©2015 – Confidential, metrixware
Why a progressive rewrite is possible
1. The team loves its product
2. But would like :
a. To feel more confident when a LOC is about to be changed
b. To provide more efficiently new exciting features
c. To live a better technology experience
d. To solve the main architectural problems
14. 14©2015 – Confidential, metrixware
What we want
➔ Robustness
➔ Simplicity
➔ Softness
➔ Productivity
Katrina Asfardi
18. 18©2015 – Confidential, metrixware
Daily routine
● Instability / Fiability problems
○ Productivity problems (never the developer fault!)
○ Technology mess, requires godlike developers
○ Application: IDE Hostile
● Testable problems
○ Tough debugging
○ Not designed for unit tests
○ Not-so-obvious installation and deployment procedure
● Non-standard way of development and technologies
○ Costly to evolve
○ Tightly coupled to the technologies
20. 20©2015 – Confidential, metrixware
“Cities grow, cities evolve, cities have parts that simply die while others parts flourish ;
each city has to be renewed in order to meet the needs of its populace…
Software-intensive systems are like that…”
- Grady Booch
21. 21©2015 – Confidential, metrixware
TOP 5 Reasons
… to not attempt a big rewrite
1. It's a critical product for XYZ
2. Its featured-rich content is hard to reproduce
3. It will take longer than you think
a. markets change
b. existing customers may become frustrated
4. XYZ is an experienced software
a. many bugs have been found
b. many bugs have been fixed
c. use has been customized for the customer satisfaction
5. A complete frustration for the team during the whole rewrite
22. 22©2015 – Confidential, metrixware
Our suggestion:
● An incremental (smart) approach
● Refactor and improve the existing base in a
big (automated) jump
● Obtain a functional architecture quickly
23. 23©2015 – Confidential, metrixware
A possible Roadmap
Fix the main
issue
Create
functional
modules
Upgrade the
technologies
Create your
Cloud/SaaS
system
Improve the software factory process
24. 24©2015 – Confidential, metrixware
The tasks
1. Fix the main issue
2. Creation of a functional architecture
a. Functional modules
b. Loosely coupled
3. Externalization of the functionalities shared with other products
4. Technology change for Open-source/Standards
5. Improves the software release process to make it
a. less difficult
b. more DevOps friendly
26. 26©2015 – Confidential, metrixware
Our offer
An IDE Tool
To fix the issue with Automation
Time optimization: min 60%
Cost reduction: >50%