Be the first to like this
When working with Agile, you need to control architecture, satisfy non-functional requirements, and reduce technical debt in short iterations. Even more challenging, non-functional, structural flaws are notoriously difficult to detect with test cases. Since these application-level defects are typically investigated during acceptance testing at the end of an iteration or sprint, problems are detected when it is often too late to make corrections before release. Consequently, these flaws become technical debt to be remediated in future iterations.
In this paper find out how the CAST Application Intelligence Platform (AIP) can be incorporated into a continuous integration environment to evaluate if newly integrated components:
• Violate rules of good architectural and coding practice affecting security, robustness, changeability, performance efficiency, and maintainability
• Create unintended side effects in other layers of the application
• Adhere to the application’s architectural rules
• Have structural problems that create technical debt