Understanding Your Applications - Ray Everhart
1 like175 views
The document discusses application understanding and its importance. It defines application understanding as knowing the data usage and relationships, object dependencies, features and functionality, and unmitigated risks of an application. It notes that without application understanding, investments in applications are at risk. It then outlines legacy and modern approaches to achieving application understanding, including through automated discovery and analysis tools. Finally, it lists benefits of application understanding such as reduced costs, faster development, and identifying risks.
Understanding Your Applications - Ray Everhart
- 1. DALLAS, TX - Nov 3 Presented by:
- 2. Understanding Your Applications Agenda: • What is Application Understanding? • Why is it Important? • How do I get it? • What can I do with it?
- 3. Understanding Your Applications Agenda: • What is Application Understanding? • Why is it Important? • How do I get it? • What can I do with it?
- 4. What is Application Understanding? The things that I need to know in order to make good decisions: 1. Data Usage & Relationships 2. Object Dependencies 3. Features and Functionality 4. Unmitigated Risk
- 5. Understanding Your Applications Agenda: • What is Application Understanding? • Why is it Important? • How do I get it? • What can I do with it?
- 6. Why is it Important? Without application understanding, your investment in the IBM i is at risk due to unfavorable stakeholder perceptions. Symptoms: • Inability to quickly respond to changing business demands • Growing backlog of enhancement requests • Late / Failed Projects • Cost of software maintenance • Increasing Technical Debt
- 7. Understanding Your Applications Agenda: • What is Application Understanding? • Why is it Important? • How do I get it? • What can I do with it?
- 8. How do I get it? The Legacy Approach: “I understand it because I wrote it!” “I’ve been working on this system for years.” “You’ll need to check with Bob.” “Read the documentation.” “Check the source code.”
- 9. How do I get it? Software Engineering Approach: Application discovery and understanding (ADU) is the process of automatically analyzing artifacts of a software application and determining metadata structures associated with the application in the form of lists of data elements and business rules.
- 10. How do I get it? Options: • Home-grown tools • Commercial Software
- 11. Understanding Your Applications Agenda: • What is Application Understanding? • Why is it Important? • How do I get it? • What can I do with it?
- 12. What Can I do with it? • Reduce Software Development & Maintenance Costs • Faster onboarding of new resources • Automated Impact Analysis • Increase Developer Productivity • Automated Documentation • Comprehensive Test planning • Change Management Analysis • Management by Metrics • Metrics based Effort Estimation • Code Quality monitoring and Enforcement • Trends over time • Areas of Unmitigated Risk • Modernization