Standardization and Innovation
0Discussion of software engineering specification in general, and legacy modernization in particular, often generates controversy about standardization versus innovation. The apposition is supposedly between software engineering and standardization efforts on the one hand, and proprietary, innovative vendor approaches on the other. The argument is made that standardization …
Read More
Seeing the Forest and the Trees
Understanding the complexities of a legacy application requires a top-down, bottom-up approach. This is one of a series of blogs connecting the principles described in the Use Case 2.0 eBook to agile legacy modernization. The principles are: Keep it simple by telling stories Understand the big picture …
Read More
Why Legacy Code is Not Enough
As applications evolve over time, knowledge is lost and a comprehensive overview of the business purpose and use of a system may no longer exist. The code itself is one source of information, but by itself is not adequate for understanding a legacy application. Because …
Read More-
Build the Abstract Models
Use case modeling is an effective way to reverse engineer a legacy system and build an abstract view for stakeholder validation of functionality. Agile development advice would be to model ‘just enough’, and avoid ‘modeling for modeling’s sake’. While this is still good advice for …
Read More
