Don’t Settle for Old-school SCM: Fail Faster? How about Don’t Fail at All?
•Download as PPTX, PDF•
1 like•296 views
Can your Source Code Management (SCM) tool help your business compete in the digital economy? Why settle for old-school SCM when you don’t have to? In this brief webcast, our experts demo a copybook change within ISPW, highlighting: - Impact Analysis with rich visualization. See how a code change might impact the rest of the mainframe environment, saving you from rework. - Topaz integration. With access to Topaz for Program Analysis through the Topaz Workbench, you can dig deeper into code details to better understand complex application logic. Our experts also show how generating, promoting, testing and approving code is made easier and more efficient with ISPW.
Report
Share
Don’t Settle for Old-school SCM: Fail Faster? How about Don’t Fail at All?
- 1. 1 Don’t Settle for Old-school SCM Fail Faster? How about Don’t Fail at All? Jim Liebert, Product Manager Mark Schettenhelm, Product Manager April 28, 2016
- 2. 2 Jim Liebert Product Manager Mark Schettenhelm Product Manager
- 3. 3 Blended Ecosystem Enabling DevOps Across the Enterprise
- 4. 4 Make It Easy to Go Fast Agile Development Continuous Integration Continuous Delivery DevOps Eclipse-based interfaces Advanced Application Analysis Agile Source Code Management Automated Code Quality Dev & Ops Collaboration
- 6. 6 ISPW through Topaz Workbench • Lifecycle visibility • Team collaboration: hover to find out who is working with program Impact Analysis
- 8. 8 DEMO Topaz for Program Analysis
- 12. 12 Data Flow
- 13. 13 DEMO ISPW
- 14. 14 Compare multiple versions of code
- 16. 16 Emergency fixes just can’t wait for approvers to get back to the office, so we added a mobile interface to the existing web approval. Mobile Approvals
- 17. 17 Make It Easy to Go Fast
- 18. 18© 2016 Compuware Corporation. All rights reserved.