Compuware Product Managers Jim Liebert and Mark Schettenhelm discuss how much easier working with complex and unfamiliar programs and data is when developers can see how the code and data fit together. Compuware Topaz makes this possible by providing instant visualizations of programs and data relationships across the enterprise, empowering even mainframe-inexperienced developers to improve application quality and speed of delivery.
The document summarizes user testing results for a parking adviser app, finding that while the app features addressed important needs like available spaces and lot status, the implementation lacked satisfaction. Users commented that numbers should always be visible, the map was not fixed, and status colors were unclear. The next version of the app aims to improve the map display and add real data and destination setting by tap.
Java presents a critical opportunity for companies to quickly innovate on the mainframe platform to meet the relentless demands of the digital economy. But how do you develop game-changing solutions on the mainframe while making sure the operational demands of the rest of your enterprise aren’t compromised?
Newly unveiled Topaz for Java Performance aims to help you realize the benefits of Java on z while maintaining the high performance expectations of your mainframe environment.
Compuware Product Managers Steve Kansa and Spencer Hallman join Technical Consultant Glenn Everitt to demo Topaz for Java Performance’s “under the hood” visibility into the behavior of Java on the mainframe including:
- measuring Java Classes CPU performance
- identifying areas for code optimization
- spotting Garbage Collection issues such as memory leaks
- identifying blocked Threads
- seamlessly integrating with Compuware Strobe for full mainframe performance analysis
Go Fast, Go Safe, Go on Vacation - Compuware ISPW Webcast Compuware
This document discusses source code management and release automation capabilities for mainframe applications. Key features include source control, check-in/out workflows, approval processes, impact analysis, automated deployment to test and production environments, rollback capabilities, and mobile approvals. The solution allows for parallel development, flexible lifecycles, end-to-end auditing and works across mainframe, UNIX, Linux and Windows platforms for multi-platform releases.
Compuware product managers Irene Ford, Bill Mackey and Jonathan Manley discuss and demo some of File-AID’s new and notable enhancements, including:
- File-AID for MVS: the use of 64-Bit storage when working with larger datasets; multi-dataset Search/Update functionality; and new Compare functionality designed to allow users to consolidate their Compare needs onto File-AID for MVS.
- File-AID for IMS and DB2: IBM Health Checker for z/OS support; customer requested enhancements that have been implemented in File-AID for IMS and File-AID for DB2; and enhancements to product architecture that address performance and usage of z/OS Unix.
- Test Data Privacy and File-AID/EX: list variable support; new functions in rule logic; disguise of CLOB and XML columns; improved handling of DISTINCT data types; and more.
See the App Performance Future with Predictive Analytics WebcastCompuware
Compuware Product Manager Spencer Hallman and ConicIT VP of Product Management Jacob Ukelson demonstrate how Strobe’s integration with ConicIT provides ops staffs with predictive analytics to help them discover and resolve performance issues before application service levels are impacted.
What's New in Strobe? August 2016 WebcastCompuware
Spencer Hallman, Product Manager at Compuware, will demonstrate how the new enhancements make finding and interpreting the data collected by Strobe simple. Highlights include:
- CICSPlex measurement and reporting
- IMS Transaction Profiling
- DB2 Wait Metrics and SQL Analysis Feature improvements
- Strobe Insight analytics across iStrobe Profile and SMF Data
- Integrations with other solutions
This document outlines new features in Topaz Workbench, an IDE from Compuware. It discusses enhancements to the base functionality of Topaz Workbench including improved file management tools. New functionality is also described for Topaz for Enterprise Data to help users work with databases and files.
This document discusses strategies for achieving simplicity and power in product design. It begins by exploring the tension between simplicity and power, noting that both are important but sometimes at odds. It then provides examples of balancing the two through careful feature selection and presentation. The document also includes a deep dive on how to address challenges through requirements, design, and technical approaches. Specifically, it provides tips on avoiding feature creep in requirements, guidelines for solution architecture, UX design, and balancing workload between users. The goal is to thoughtfully reduce complexity while maintaining powerful functionality.
The document summarizes user testing results for a parking adviser app, finding that while the app features addressed important needs like available spaces and lot status, the implementation lacked satisfaction. Users commented that numbers should always be visible, the map was not fixed, and status colors were unclear. The next version of the app aims to improve the map display and add real data and destination setting by tap.
Java presents a critical opportunity for companies to quickly innovate on the mainframe platform to meet the relentless demands of the digital economy. But how do you develop game-changing solutions on the mainframe while making sure the operational demands of the rest of your enterprise aren’t compromised?
Newly unveiled Topaz for Java Performance aims to help you realize the benefits of Java on z while maintaining the high performance expectations of your mainframe environment.
Compuware Product Managers Steve Kansa and Spencer Hallman join Technical Consultant Glenn Everitt to demo Topaz for Java Performance’s “under the hood” visibility into the behavior of Java on the mainframe including:
- measuring Java Classes CPU performance
- identifying areas for code optimization
- spotting Garbage Collection issues such as memory leaks
- identifying blocked Threads
- seamlessly integrating with Compuware Strobe for full mainframe performance analysis
Go Fast, Go Safe, Go on Vacation - Compuware ISPW Webcast Compuware
This document discusses source code management and release automation capabilities for mainframe applications. Key features include source control, check-in/out workflows, approval processes, impact analysis, automated deployment to test and production environments, rollback capabilities, and mobile approvals. The solution allows for parallel development, flexible lifecycles, end-to-end auditing and works across mainframe, UNIX, Linux and Windows platforms for multi-platform releases.
Compuware product managers Irene Ford, Bill Mackey and Jonathan Manley discuss and demo some of File-AID’s new and notable enhancements, including:
- File-AID for MVS: the use of 64-Bit storage when working with larger datasets; multi-dataset Search/Update functionality; and new Compare functionality designed to allow users to consolidate their Compare needs onto File-AID for MVS.
- File-AID for IMS and DB2: IBM Health Checker for z/OS support; customer requested enhancements that have been implemented in File-AID for IMS and File-AID for DB2; and enhancements to product architecture that address performance and usage of z/OS Unix.
- Test Data Privacy and File-AID/EX: list variable support; new functions in rule logic; disguise of CLOB and XML columns; improved handling of DISTINCT data types; and more.
See the App Performance Future with Predictive Analytics WebcastCompuware
Compuware Product Manager Spencer Hallman and ConicIT VP of Product Management Jacob Ukelson demonstrate how Strobe’s integration with ConicIT provides ops staffs with predictive analytics to help them discover and resolve performance issues before application service levels are impacted.
What's New in Strobe? August 2016 WebcastCompuware
Spencer Hallman, Product Manager at Compuware, will demonstrate how the new enhancements make finding and interpreting the data collected by Strobe simple. Highlights include:
- CICSPlex measurement and reporting
- IMS Transaction Profiling
- DB2 Wait Metrics and SQL Analysis Feature improvements
- Strobe Insight analytics across iStrobe Profile and SMF Data
- Integrations with other solutions
This document outlines new features in Topaz Workbench, an IDE from Compuware. It discusses enhancements to the base functionality of Topaz Workbench including improved file management tools. New functionality is also described for Topaz for Enterprise Data to help users work with databases and files.
This document discusses strategies for achieving simplicity and power in product design. It begins by exploring the tension between simplicity and power, noting that both are important but sometimes at odds. It then provides examples of balancing the two through careful feature selection and presentation. The document also includes a deep dive on how to address challenges through requirements, design, and technical approaches. Specifically, it provides tips on avoiding feature creep in requirements, guidelines for solution architecture, UX design, and balancing workload between users. The goal is to thoughtfully reduce complexity while maintaining powerful functionality.
7 Fatal Mistakes Made When Migrating From SP 2007 to SP 2010Netwoven Inc.
This document summarizes a webinar about the 7 fatal mistakes made when migrating from SharePoint 2007 to SharePoint 2010. It includes an agenda for the webinar with a presentation on the mistakes, as well as a question and answer session. It also advertises a special offer for an architecture design session with Netwoven, the company hosting the webinar, to assess SharePoint environments.
How to boost your workflow, or git rebase for designersAnton Parkhomenko
Increase the speed and quality of your development. Some tools and practices to integrate the design part into development cycle. Hands-on experience, pitfalls and dealing with late-adopters
Doing Analytics Right - Building the Analytics EnvironmentTasktop
Implementing analytics for development processes is challenging. As in discussed in the previous webinars, the right analytics are determined by the goals of the organization, not by the available data. So implementing your analytics solutions will require an efficient analytics and data architecture, including the ability to combine and stage data from heterogeneous sources. An architecture that excludes the ability to gain access to the necessary data will create a barrier to deploying your newly designed analytics program, and will force you back into the “light is brighter here” anti-pattern.
This webinar will describe the technical considerations of implementing the data architecture for your analytics program, and explain how Tasktop can help.
The document discusses common problems faced by software projects, including large budget overruns, missed deadlines, and features not being delivered. It notes that 53% of projects are over budget, over time, or deliver fewer features than planned. Reasons for project failures include unclear requirements, changing requirements, underestimating complexity, and lack of testing. The document contrasts the differences between programming small programs versus engineering large, complex software systems. It emphasizes that software engineering requires a disciplined, systematic approach to developing reliable software on time and on budget.
Saya faham perasaan anda. Untuk memulakan jualan di Agrobazaar, anda boleh mula dengan:
1. Daftar sebagai penjual dengan mengisi maklumat peribadi dan perniagaan asas anda.
2. Unggah gambar produk anda yang jelas beserta maklumat asas seperti nama, harga dan keterangan ringkas.
3. Kategorikan produk anda di bawah kategori yang sesuai seperti makanan, pakaian dan lain-lain.
Adam Ochs presented at the March 2018 Sharepoint Fest D.C. on developing an Office 365 roadmap. He discussed that an Office 365 roadmap should communicate an organization's strategy and path for productivity technologies over major steps. The seven steps to building a successful roadmap included: 1) defining goals and strategy, 2) identifying current user issues, 3) grouping issues into problem areas, 4) evaluating Office 365 technologies, 5) creating the roadmap, 6) developing success criteria, and 7) regularly revisiting and updating the roadmap. Developing a comprehensive roadmap is important for strategic planning and communicating an organization's path for Office 365.
This document outlines the seven steps to developing a successful Office 365 roadmap: 1) Define organizational goals and strategy, 2) Identify current user issues, 3) Group issues into addressable problem areas, 4) Evaluate Office 365 technologies to address problems, 5) Create the roadmap, 6) Develop success criteria, and 7) Revisit the roadmap regularly. The presenter emphasizes starting with goals and current problems, mapping issues to technologies like OneDrive and Teams, and creating measurable success criteria to guide the roadmap.
XPages: You Know the 'How to'. Now Learn the 'Why and What'.Teamstudio
The document summarizes an XPages webinar hosted by TLCC and featuring a presentation by John Kingsley of GreyDuck Technology. The webinar discussed reasons for mobilizing and web enabling existing IBM Notes applications, and provided a process for selecting which applications to prioritize for these efforts. Key points included identifying applications with low complexity, evaluating business criticality, and considering device and connectivity requirements. Contact information was provided for TLCC and the presenter for any additional questions.
This is the presentation that Mark Fries and Guy Bourgault gave at the Intelligent Content Conference in San Francisco, CA on March 24, 2015.
BMC Case Study: How to Take a Content-First Approach and Measure the Success of Your Content Strategy
A behind the scenes look at how BMC Software, one of the world’s largest software companies, approached a large-scale responsive overhaul.
Approaching a major site overhaul is never easy, but it was especially complex for BMC Software with dozens of buyer personas, thousands of employees, and diverse product and service offerings. The talk will provide an inside look at the approach BMC took to overhaul the site and rebrand the company by focusing first on content and customers first.
We will share the processes, tools, and artifacts (from both BMC and its agency partner) used to collaborate with design and development teams to create a scalable framework and deliver a measurable return on investment.
You will learn:
-How to approach a large-scale project with a content-first strategy
-The importance of content modeling in supporting large-scale responsive projects
-How to collaborate effectively with external agency teams
-How content strategists, designers, and user experience team members can move toward more rapid prototyping techniques
-How to measure the success of a content-first redesign strategy
BMC Case Study: How to Take a Content-First Approach and Measure the Success ...Connective DX
This is the presentation that Mark Fries and Guy Bourgault gave at the Intelligent Content Conference in San Francisco, CA on March 24, 2015.
BMC Case Study: How to Take a Content-First Approach and Measure the Success of Your Content Strategy
A behind the scenes look at how BMC Software, one of the world’s largest software companies, approached a large-scale responsive overhaul.
Approaching a major site overhaul is never easy, but it was especially complex for BMC Software with dozens of buyer personas, thousands of employees, and diverse product and service offerings. The talk will provide an inside look at the approach BMC took to overhaul the site and rebrand the company by focusing first on content and customers first.
We will share the processes, tools, and artifacts (from both BMC and its agency partner) used to collaborate with design and development teams to create a scalable framework and deliver a measurable return on investment.
You will learn:
-How to approach a large-scale project with a content-first strategy
-The importance of content modeling in supporting large-scale responsive projects
-How to collaborate effectively with external agency teams
-How content strategists, designers, and user experience team members can move toward more rapid prototyping techniques
-How to measure the success of a content-first redesign strategy
1. The document discusses BMC's transition to a new content strategy to address challenges with their inconsistent branding, product-focused content that did not reflect customer needs, and lack of scalable infrastructure.
2. Their new approach defined business goals, customer needs, and content components to be modular. They designed mobile-first and tested assumptions.
3. The results included increased content creation efficiencies, improved user experience through optimization, and increased engagement through higher organic traffic, data sheet downloads, trial starts, and contact requests, leading to more revenue and pipeline.
Introduction to UX for Mesiniaga AcademyZainul Zain
The document provides an introduction to UX (user experience) design. It begins by distinguishing UX from UI (user interface), noting that UX design is based on thorough user research and testing, while UI focuses only on visual screen elements. The key aspects of UX include user research, prototyping, design, and development with the goal of intuitive, effective experiences. User research, especially getting accurate user requirements, is described as the most important part of UX design to avoid scope creep and ensure projects meet user needs. The document then discusses wireframing as a method for capturing content, organization and interactions before development begins.
SenchaCon 2016: Using Ext JS 6 for Cross-Platform Development on Mobile - And...Sencha
Andrew will share the experience he and his team have gotten from using Ext JS 6 for cross-platform app development on mobile and desktop devices. Having released Ext JS 6 apps for industries including utilities, oil & gas, construction, and transport, Andrew has learned the common pitfalls and gotchas you need to know. Using examples from recent projects, he provides tips for those who aren't yet familiar or experienced with mobile development. By the end of the session, you will know how to think like a mobile developer, develop apps with mobile user experience in mind, make the move from Ext JS 5 or Sencha Touch to Ext JS 6, deploy native apps with Cordova, and manage data on devices with limited resources.
7 reasons why configurator projects fail ebook.pdf'Cincom Systems
The document outlines 7 common reasons why configurator projects fail. Reason 4 is that the configurator project is planned without input from the full user community. This risks making a system that does not adequately meet the needs of the different user groups affected. To avoid this, the planning process should assure input is received from all appropriate groups within the organization to understand their specific needs and allow them ownership over the outcomes. Gathering this input up front increases the chances of the project succeeding.
The document discusses best practices for mobile application development and management. It covers the project life cycle, including initiating, planning, executing, monitoring and controlling, and closing a project. It also discusses managing enterprise mobility through a holistic approach, common challenges such as scheduling concerns, and best practices for use scenarios, prototypes, user interfaces, store submission, and testing. The overall focus is on effective strategies for developing and managing successful mobile applications and projects.
Requirements errors are deficiencies in requirements documentation that can hinder software development if not addressed. There are several types of requirements errors, including errors of omission, commission, clarity/ambiguity, and performance. Requirements errors are costly to fix and can negatively impact stakeholders if the resulting software does not meet real user needs. It is better to prevent requirements errors through techniques like joint application development, quality function deployment, prototyping, requirements inspections, and ensuring domain understanding and stakeholder participation during the requirements engineering process.
IxDA Helsinki meet-up at Smartly.io, Thu, 25th August 2016Pekka Hartikainen
Topics in the meet-up
A Practical Approach to Icon Taxonomy
Teemu Korpilahti, Lead Designer at Crasman
Accept the Imperfectness
Sami Vuori, Visual / UX / UI Designer at Gapps
Losing Control: Design Systems for Complex User Interfaces
Pekka Hartikainen, Design Lead at Smartly.io
The document discusses various phases of systems design, implementation, and operation. It describes the conceptual systems design phase, where design alternatives are evaluated and conceptual design specifications are prepared. This includes output, data storage, input, and processing procedures. The physical systems design phase then translates this conceptual design into detailed specifications for implementation. Key aspects of physical design discussed include output design, file and database design, input design, program design, procedures design, and controls design.
Xpediter 9.4 – Value Today, Essential Tomorrow Webcast Compuware
The document appears to be a presentation about the Xpediter product, which provides debugging and development tools for mainframe applications. It discusses features like STEP INTO/OVER debugging commands, breakpoint retention, monitoring COBOL programs, adding watch variables, and debugging batch jobs across multiple steps. The presentation also introduces the Topaz product for discovering, visualizing, and working with mainframe data in common tools, and empowers next-generation developers without deep mainframe expertise. It notes future innovations will include agile development and quarterly releases of new features to help customers work smarter and faster.
The OnTarget UX team was tasked with redesigning OnTarget's existing mobile app. Their 3-week design plan included discovery, research, and iteration phases. In discovery, they analyzed OnTarget's current app and competitors. Their research involved surveys, interviews, and affinity mapping to identify 3 user personas. They created storyboards, prototypes, and tested designs. Their final high-fidelity prototype focused the app on tasks and communication for easier field use.
SCM Transformation Challenges and How to Overcome ThemCompuware
If your enterprise is focused on continuously improving quality, velocity and efficiency, you’re going to win against those that aren’t. Driving improvements on the mainframe, and in turn throughout the business, requires the transformation of three things: culture, processes and tools. In other words, changing mindsets, implementing modern practices (Agile, DevOps, CI/CD) and replacing outdated technology.
Mainframe source code management is currently a critical area in need of modernization and should be one of the initial tooling changes organizations make when setting out to improve mainframe systems delivery.
During this session, Compuware specialist Lars-Erik Berglund shares the challenges organizations face with mainframe source code management and what you can do to overcome those.
The Importance of Data for DevOps: How TCF Bank Meets Test Data ChallengesCompuware
Generating realistic, privatized test data and delivering it to your teams fast enough to meet the demands of your business is a growing issue at agile organizations.
To help you overcome these challenges, TCF Bank shares how they are innovatively using DevOps-supporting test data management techniques with the help of Compuware to effectively:
• Deliver test data to internal teams with agility
• Develop repeatable processes that fit within two-week sprints
• Privatize data based on nuanced demands from development teams
• Manage an influx of test data requests from internal teams
• Automate processes to ensure test data management aligns with security protocols
• Work across mainframe and distributed teams with their own priorities and deliverables
More Related Content
Similar to What is a Picture Worth? Using Visualizations to Understand Your Applications
7 Fatal Mistakes Made When Migrating From SP 2007 to SP 2010Netwoven Inc.
This document summarizes a webinar about the 7 fatal mistakes made when migrating from SharePoint 2007 to SharePoint 2010. It includes an agenda for the webinar with a presentation on the mistakes, as well as a question and answer session. It also advertises a special offer for an architecture design session with Netwoven, the company hosting the webinar, to assess SharePoint environments.
How to boost your workflow, or git rebase for designersAnton Parkhomenko
Increase the speed and quality of your development. Some tools and practices to integrate the design part into development cycle. Hands-on experience, pitfalls and dealing with late-adopters
Doing Analytics Right - Building the Analytics EnvironmentTasktop
Implementing analytics for development processes is challenging. As in discussed in the previous webinars, the right analytics are determined by the goals of the organization, not by the available data. So implementing your analytics solutions will require an efficient analytics and data architecture, including the ability to combine and stage data from heterogeneous sources. An architecture that excludes the ability to gain access to the necessary data will create a barrier to deploying your newly designed analytics program, and will force you back into the “light is brighter here” anti-pattern.
This webinar will describe the technical considerations of implementing the data architecture for your analytics program, and explain how Tasktop can help.
The document discusses common problems faced by software projects, including large budget overruns, missed deadlines, and features not being delivered. It notes that 53% of projects are over budget, over time, or deliver fewer features than planned. Reasons for project failures include unclear requirements, changing requirements, underestimating complexity, and lack of testing. The document contrasts the differences between programming small programs versus engineering large, complex software systems. It emphasizes that software engineering requires a disciplined, systematic approach to developing reliable software on time and on budget.
Saya faham perasaan anda. Untuk memulakan jualan di Agrobazaar, anda boleh mula dengan:
1. Daftar sebagai penjual dengan mengisi maklumat peribadi dan perniagaan asas anda.
2. Unggah gambar produk anda yang jelas beserta maklumat asas seperti nama, harga dan keterangan ringkas.
3. Kategorikan produk anda di bawah kategori yang sesuai seperti makanan, pakaian dan lain-lain.
Adam Ochs presented at the March 2018 Sharepoint Fest D.C. on developing an Office 365 roadmap. He discussed that an Office 365 roadmap should communicate an organization's strategy and path for productivity technologies over major steps. The seven steps to building a successful roadmap included: 1) defining goals and strategy, 2) identifying current user issues, 3) grouping issues into problem areas, 4) evaluating Office 365 technologies, 5) creating the roadmap, 6) developing success criteria, and 7) regularly revisiting and updating the roadmap. Developing a comprehensive roadmap is important for strategic planning and communicating an organization's path for Office 365.
This document outlines the seven steps to developing a successful Office 365 roadmap: 1) Define organizational goals and strategy, 2) Identify current user issues, 3) Group issues into addressable problem areas, 4) Evaluate Office 365 technologies to address problems, 5) Create the roadmap, 6) Develop success criteria, and 7) Revisit the roadmap regularly. The presenter emphasizes starting with goals and current problems, mapping issues to technologies like OneDrive and Teams, and creating measurable success criteria to guide the roadmap.
XPages: You Know the 'How to'. Now Learn the 'Why and What'.Teamstudio
The document summarizes an XPages webinar hosted by TLCC and featuring a presentation by John Kingsley of GreyDuck Technology. The webinar discussed reasons for mobilizing and web enabling existing IBM Notes applications, and provided a process for selecting which applications to prioritize for these efforts. Key points included identifying applications with low complexity, evaluating business criticality, and considering device and connectivity requirements. Contact information was provided for TLCC and the presenter for any additional questions.
This is the presentation that Mark Fries and Guy Bourgault gave at the Intelligent Content Conference in San Francisco, CA on March 24, 2015.
BMC Case Study: How to Take a Content-First Approach and Measure the Success of Your Content Strategy
A behind the scenes look at how BMC Software, one of the world’s largest software companies, approached a large-scale responsive overhaul.
Approaching a major site overhaul is never easy, but it was especially complex for BMC Software with dozens of buyer personas, thousands of employees, and diverse product and service offerings. The talk will provide an inside look at the approach BMC took to overhaul the site and rebrand the company by focusing first on content and customers first.
We will share the processes, tools, and artifacts (from both BMC and its agency partner) used to collaborate with design and development teams to create a scalable framework and deliver a measurable return on investment.
You will learn:
-How to approach a large-scale project with a content-first strategy
-The importance of content modeling in supporting large-scale responsive projects
-How to collaborate effectively with external agency teams
-How content strategists, designers, and user experience team members can move toward more rapid prototyping techniques
-How to measure the success of a content-first redesign strategy
BMC Case Study: How to Take a Content-First Approach and Measure the Success ...Connective DX
This is the presentation that Mark Fries and Guy Bourgault gave at the Intelligent Content Conference in San Francisco, CA on March 24, 2015.
BMC Case Study: How to Take a Content-First Approach and Measure the Success of Your Content Strategy
A behind the scenes look at how BMC Software, one of the world’s largest software companies, approached a large-scale responsive overhaul.
Approaching a major site overhaul is never easy, but it was especially complex for BMC Software with dozens of buyer personas, thousands of employees, and diverse product and service offerings. The talk will provide an inside look at the approach BMC took to overhaul the site and rebrand the company by focusing first on content and customers first.
We will share the processes, tools, and artifacts (from both BMC and its agency partner) used to collaborate with design and development teams to create a scalable framework and deliver a measurable return on investment.
You will learn:
-How to approach a large-scale project with a content-first strategy
-The importance of content modeling in supporting large-scale responsive projects
-How to collaborate effectively with external agency teams
-How content strategists, designers, and user experience team members can move toward more rapid prototyping techniques
-How to measure the success of a content-first redesign strategy
1. The document discusses BMC's transition to a new content strategy to address challenges with their inconsistent branding, product-focused content that did not reflect customer needs, and lack of scalable infrastructure.
2. Their new approach defined business goals, customer needs, and content components to be modular. They designed mobile-first and tested assumptions.
3. The results included increased content creation efficiencies, improved user experience through optimization, and increased engagement through higher organic traffic, data sheet downloads, trial starts, and contact requests, leading to more revenue and pipeline.
Introduction to UX for Mesiniaga AcademyZainul Zain
The document provides an introduction to UX (user experience) design. It begins by distinguishing UX from UI (user interface), noting that UX design is based on thorough user research and testing, while UI focuses only on visual screen elements. The key aspects of UX include user research, prototyping, design, and development with the goal of intuitive, effective experiences. User research, especially getting accurate user requirements, is described as the most important part of UX design to avoid scope creep and ensure projects meet user needs. The document then discusses wireframing as a method for capturing content, organization and interactions before development begins.
SenchaCon 2016: Using Ext JS 6 for Cross-Platform Development on Mobile - And...Sencha
Andrew will share the experience he and his team have gotten from using Ext JS 6 for cross-platform app development on mobile and desktop devices. Having released Ext JS 6 apps for industries including utilities, oil & gas, construction, and transport, Andrew has learned the common pitfalls and gotchas you need to know. Using examples from recent projects, he provides tips for those who aren't yet familiar or experienced with mobile development. By the end of the session, you will know how to think like a mobile developer, develop apps with mobile user experience in mind, make the move from Ext JS 5 or Sencha Touch to Ext JS 6, deploy native apps with Cordova, and manage data on devices with limited resources.
7 reasons why configurator projects fail ebook.pdf'Cincom Systems
The document outlines 7 common reasons why configurator projects fail. Reason 4 is that the configurator project is planned without input from the full user community. This risks making a system that does not adequately meet the needs of the different user groups affected. To avoid this, the planning process should assure input is received from all appropriate groups within the organization to understand their specific needs and allow them ownership over the outcomes. Gathering this input up front increases the chances of the project succeeding.
The document discusses best practices for mobile application development and management. It covers the project life cycle, including initiating, planning, executing, monitoring and controlling, and closing a project. It also discusses managing enterprise mobility through a holistic approach, common challenges such as scheduling concerns, and best practices for use scenarios, prototypes, user interfaces, store submission, and testing. The overall focus is on effective strategies for developing and managing successful mobile applications and projects.
Requirements errors are deficiencies in requirements documentation that can hinder software development if not addressed. There are several types of requirements errors, including errors of omission, commission, clarity/ambiguity, and performance. Requirements errors are costly to fix and can negatively impact stakeholders if the resulting software does not meet real user needs. It is better to prevent requirements errors through techniques like joint application development, quality function deployment, prototyping, requirements inspections, and ensuring domain understanding and stakeholder participation during the requirements engineering process.
IxDA Helsinki meet-up at Smartly.io, Thu, 25th August 2016Pekka Hartikainen
Topics in the meet-up
A Practical Approach to Icon Taxonomy
Teemu Korpilahti, Lead Designer at Crasman
Accept the Imperfectness
Sami Vuori, Visual / UX / UI Designer at Gapps
Losing Control: Design Systems for Complex User Interfaces
Pekka Hartikainen, Design Lead at Smartly.io
The document discusses various phases of systems design, implementation, and operation. It describes the conceptual systems design phase, where design alternatives are evaluated and conceptual design specifications are prepared. This includes output, data storage, input, and processing procedures. The physical systems design phase then translates this conceptual design into detailed specifications for implementation. Key aspects of physical design discussed include output design, file and database design, input design, program design, procedures design, and controls design.
Xpediter 9.4 – Value Today, Essential Tomorrow Webcast Compuware
The document appears to be a presentation about the Xpediter product, which provides debugging and development tools for mainframe applications. It discusses features like STEP INTO/OVER debugging commands, breakpoint retention, monitoring COBOL programs, adding watch variables, and debugging batch jobs across multiple steps. The presentation also introduces the Topaz product for discovering, visualizing, and working with mainframe data in common tools, and empowers next-generation developers without deep mainframe expertise. It notes future innovations will include agile development and quarterly releases of new features to help customers work smarter and faster.
The OnTarget UX team was tasked with redesigning OnTarget's existing mobile app. Their 3-week design plan included discovery, research, and iteration phases. In discovery, they analyzed OnTarget's current app and competitors. Their research involved surveys, interviews, and affinity mapping to identify 3 user personas. They created storyboards, prototypes, and tested designs. Their final high-fidelity prototype focused the app on tasks and communication for easier field use.
Similar to What is a Picture Worth? Using Visualizations to Understand Your Applications (20)
SCM Transformation Challenges and How to Overcome ThemCompuware
If your enterprise is focused on continuously improving quality, velocity and efficiency, you’re going to win against those that aren’t. Driving improvements on the mainframe, and in turn throughout the business, requires the transformation of three things: culture, processes and tools. In other words, changing mindsets, implementing modern practices (Agile, DevOps, CI/CD) and replacing outdated technology.
Mainframe source code management is currently a critical area in need of modernization and should be one of the initial tooling changes organizations make when setting out to improve mainframe systems delivery.
During this session, Compuware specialist Lars-Erik Berglund shares the challenges organizations face with mainframe source code management and what you can do to overcome those.
The Importance of Data for DevOps: How TCF Bank Meets Test Data ChallengesCompuware
Generating realistic, privatized test data and delivering it to your teams fast enough to meet the demands of your business is a growing issue at agile organizations.
To help you overcome these challenges, TCF Bank shares how they are innovatively using DevOps-supporting test data management techniques with the help of Compuware to effectively:
• Deliver test data to internal teams with agility
• Develop repeatable processes that fit within two-week sprints
• Privatize data based on nuanced demands from development teams
• Manage an influx of test data requests from internal teams
• Automate processes to ensure test data management aligns with security protocols
• Work across mainframe and distributed teams with their own priorities and deliverables
Modernize Your COBOL Testing Processes with Compuware and SonarSource [Webcast]Compuware
This document discusses modernizing COBOL testing processes. It summarizes a presentation by Steve Kansa of Compuware and Olivier Gaudin of SonarSource on adopting DevOps practices and continuous delivery to improve COBOL application development. The presentation promotes tools from Compuware and SonarSource that help bring mainframe development in line with modern practices through features like a mainframe IDE, source control management, and a DevOps toolchain. It addresses challenges like code quality issues and a fractured development ecosystem.
Ignite Mainframe Agility: Fast and Accurate Development with TopazCompuware
Gain insight into igniting mainframe agility at your organization with Compuware’s Agile and DevOps tool, Topaz. Compuware Product Managers Jim Liebert and Steve Kansa narrate the story of Megan, a next-gen mainframe developer persona who completes an urgent task using Topaz to:
- Visualize her application’s execution to learn exactly what happens at runtime
- Bring up ISPW’s Impact Analysis feature to quickly understand copybook/program relationships
- Create a working set of the copybooks/programs to be changed
- Use intuitive program analysis to assist in making a change
- Generate a set of unit tests to ensure her change works without any unintended consequences
- Promote her change and automatically kick off regression testing
You can also peruse the Q&A recap document from the webcast at https://hubs.ly/H09vyxT0 or visit compuware.com/topaz for more details.
What's New in ThruPut Manager [On-demand Webcast]Compuware
Catch up on the latest ThruPut Manager enhancements since Compuware acquired the batch automation product earlier this year. During this webcast, Compuware Product Manager Spencer Hallman and Software Development Manager Nancy DiFilippo will discuss recent innovations, including:
- Separation of production and other workloads
- Integration of ThruPut Manager into the Compuware family of products
- Enhanced functionality for new z/OS 2.3
- Integration with Compuware Strobe
- Ability to compare results of different versions of your Job Action Language (JAL)
Enterprise DevOps and the Modern Mainframe Webcast PresentationCompuware
Compuware and CloudBees demonstrate how you can apply modern DevOps practices to your mainframe applications using Compuware ISPW and Topaz for Total Test with CloudBees Jenkins. Compuware Product Manager Steve Kansa and CloudBees DevOps Evangelist Brian Dawson will:
- Position the mainframe as part of your DevOps and CI/CD journey
- Explain how Jenkins automates mainframe source code management and testing
- Demo a CI/CD workflow on a COBOL application
Watch the full presentation on YouTube: https://www.youtube.com/watch?v=x4MWrPy3bKM.
Detecting Insider Threats with Multi-layered Security Webcast Compuware
When it comes to enterprise security, nothing is more securable than your mainframe, but that doesn’t mean it’s impervious to application-level insider threats. You need tools that collaborate to monitor both mainframe hardware and mission-critical assets.
Learn how mainframe system and application security tools can work together to improve data protection. Compuware Product Manager John Crossno and RSM Technical Director Mark Wilson will:
- Discuss the state of mainframe security today
- Explain how to close mainframe security gaps and reach compliance
- Describe the advantages of leveraging system- and application-level security solutions together
A Day in the Life of Cross-platform, DevOps-enabled Team Compuware
Automation, visibility and integration are key components of successful DevOps and Continuous Delivery transformations. They enable teams to be more productive, in part, by reducing manual steps and hand-offs. But if you're like most large, enterprise organizations, these components also need to apply to your mainframe to get the most from your IT investments. The mainframe’s historically siloed, slow, waterfall culture can often conflict with, and constrain, IT from meeting the needs of the business.
Enter Compuware and XebiaLabs. Together, we mainstream the mainframe to break down organizational silos and create a single, unified DevOps culture. During this webcast, Compuware Product Manager Steve Kansa and XebiaLabs VP of Products Tim Buntel show a day in the life of a fully integrated enterprise DevOps team and how the mainframe is included in a variety of modern software delivery scenarios.
How Busy Is Too Busy? Automating Your System for Maximum Throughput Compuware
Why should you care about CPU utilization? Intuitively, we all know it’s a measure of how “busy” our system is, and we know that this affects how fast things will run. We also know that we don’t want utilization to be too high, but unlimited capacity is certainly not free.
What exactly is “too high”? 80%, 90%, 99%? What is an accurate measurement and how current is it?
During this on-demand webcast, we dive into issues affecting utilization and the key role that Compuware ThruPut Manager plays in optimizing your batch workloads to keep your machine running at the performance sweet spot. Don’t get too busy!
The Do's and Don'ts of Mainframe ModernizationCompuware
A November 2016 study* found 90% of respondents’ mainframe organizations face several challenges accelerating mainframe application development and delivery to support new business initiatives.
Do you have a plan to help your team improve its development speed?
Guest speaker Forrester Principal Analyst Robert Stroud and Compuware FTS Director Reid Boddie provide:
- An exclusive analysis of November 2016 survey* findings, including the biggest challenges organizations face
- Best practices for adopting enterprise DevOps to solve development and delivery challenges
- Case studies demonstrating what experienced leaders need to do to drive a change in culture, processes and tools
* A commissioned study conducted by Forrester Consulting on behalf of Compuware, “Improve Application Development and Delivery with DevOps,” Nov. 2016.
A Day in the Life of an Agile Mainframe Developer: A Naturally Agile Approach...Compuware
Today’s challenges demand an Agile mainframe workforce, so your tools and processes should be too. An Agile/DevOps friendly toolset will enable developers to quickly and confidently understand application code and data, make changes and deliver updates.
During this webcast hosted by IBM Systems Magazine, Compuware Product Manager Mark Schettenhelm and Product Owner Paul Allard demonstrate how Compuware products, including ISPW and Topaz for Total Test, can help improve efficiency and productivity as well as make daily mainframe development tasks easier.
Using Compuware Strobe to Save CPU: 4 Real-life Cases from the Files of CPT G...Compuware
See four real-life examples of how CPT Global--a worldwide IT consulting services firm specializing in capacity planning, performance tuning and testing--uses Compuware Strobe for application performance monitoring and analysis to help customers save CPU by identifying inefficiencies in:
• COBOL code
• VSAM access
• A vendor product
• CICS system settings
Building a Millennial Mainframe Powerhouse: 7 Tips to Attract and Retain Mill...Compuware
How can your mainframe team attract and retain Millennial talent? Compuware and Ensono have been very successful in attracting, training and retaining next-gen IT staff. In our joint webcast, Millennial software developers Noah Al-Armanazi and Andrew Meister join our industry veterans David Rizzo and Ken Harper to discuss:
- Why recruiting and retaining the Millennial generation is important
- Tips for growing and retaining Millennial talent
- What makes the Millennial generation different from Boomers and Gen X
- Why modern tools, processes and culture matter
- Successful recruiting initiatives
- Social media as a recruiting tool
Unified Deployment: Including the Mainframe in Enterprise DevOpsCompuware
During this collaborative webcast, Compuware Product Manager Mark Schettenhelm and XebiaLabs VP of Products Tim Buntel demo and discuss how the integration between Compuware’s ISPW mainframe DevOps solution and XebiaLabs’ XL Release Continuous Delivery technology helps enterprises engage in cross-platform release orchestration and create business agility. Mark and Tim:
- Overview ISPW’s functionality
- Overview XebiaLabs XL Release’s functionality
- Demo the ISPW and XL Release integration
- Explain the importance of two-platform Continuous Release
A Customer's Journey to Mainstreaming the Mainframe Webcast On-demand ReplayCompuware
This document summarizes a presentation about how a company named Ameritas integrated static code analysis tools into their development process for mainframe and Java applications. It discusses the challenges they initially faced due to a lack of visibility into their legacy COBOL code and how tools from SonarSource and Compuware helped provide insights. These tools enabled continuous code quality monitoring, issue tracking, and collaboration between development teams. Their integration led to cultural changes but ultimately improved code quality and created better working relationships between teams.
Don’t Settle for Old-school SCM: Fail Faster? How about Don’t Fail at All?Compuware
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.
Mainstreaming the Mainframe: Can it be Just Another Platform? WebcastCompuware
Code is code—and COBOL is no exception. The obstacles to mainframe application agility aren’t in the COBOL language. They are in archaic waterfall development processes, an inflexible culture and obsolete tools used to manage applications written in that language.
Compuware is working hard to transform the future of mainframe app dev for our customers. We demonstrate how in our “Mainstreaming the Mainframe: Can it be Just Another Platform?” webcast hosted by IBM Systems Magazine. Compuware Product Managers Jim Liebert and Steven Kansa discuss how Compuware Topaz together with technology integrations with leading vendors like SonarSource are enabling agile delivery of quality COBOL code by mainstream development teams.
This document discusses a runtime visualizer tool that allows users to visually see how their code executes. It can dive deeper into code to help with debugging. The tool also enables online projects to connect mainframe source code logically, and provides impact analysis, program analysis and application understanding capabilities. These include seeing what programs call or are called by a given program, a program's structure and logic flow, and data flow. The document encourages that these tools can help overcome challenges in understanding unknown or complex codebases.
BMC and Compuware: Integrating to Improve Mainframe EconomicsCompuware
The document discusses how BMC and Compuware are partnering to integrate their mainframe optimization solutions to help customers reduce mainframe costs. It describes two key use cases: 1) Identifying MLC cost-saving tuning opportunities by directly launching Compuware's iStrobe performance analysis tool from BMC's Cost Analyzer to pinpoint where to focus tuning efforts, and 2) Automating problem identification and analysis by triggering iStrobe analysis when BMC's MainView detects abnormal application activity or when users initiate analysis from MainView. The integration is aimed at helping customers quantify and justify tuning efforts to lower MLC expenses through focused application optimization.
Debunking Four Myths of Agile Development WebcastCompuware
Based on lessons learned at Compuware, many of the myths that are keeping companies from experiencing the transformational benefits of using Agile on the mainframe are dispelled during this presentation. The webcast aims to equip you with the knowledge you need to begin your organization’s journey to Agile.
What is a Picture Worth? Using Visualizations to Understand Your Applications
1. 1
What is a Picture Worth?
Using Visualizations to Understand Your Applications
Jim Liebert, Product Manager
Mark Schettenhelm, Product Manager
May 21, 2015
5. 5
*****************************************************************
* EDIT THE OPERATOR ENTERED MENU SELECTION *
*****************************************************************
PERFORM P03300-EDIT-SELECTION
THRU P03300-EDIT-SELECTION-EXIT.
IF ERROR-FOUND
GO TO P03100-EDIT-SCREEN-EXIT.
*****************************************************************
* IF NO ERRORS -- DETERMINE NEXT PROGRAM TO SCHEDULE BASED *
* ON THE MENU SELECTION *
*****************************************************************
IF SELECTION-IS-DATA-REFRESH
IF PC-CONFIRM = '7'
MOVE 'PDA013' TO PC-NEXT-PGRMID
ELSE
MOVE '7' TO PC-CONFIRM
MOVE -1 TO MENUSELL
MOVE SPACES TO MENUSELO
MOVE PM036-CONFIRM-REFRESH
TO PDAMSGO
END-IF
GO TO P03100-EDIT-SCREEN-EXIT
END-IF.
MOVE SPACES TO PC-CONFIRM.
IF SELECTION-IS-USER-ID-UTILITY
PERFORM P04000-USERID-UTIL
THRU P04000-USERID-UTIL-EXIT.
IF SELECTION-IS-SCENARIO-SELECT
MOVE 'PDA024' TO PC-NEXT-PGRMID
PERFORM P80300-XFER-CONTROL
THRU P80300-XFER-CONTROL-EXIT.
P03100-EDIT-SCREEN-EXIT.
EXIT.
EJECT
The same
is true for
mainframe
programs
and data.
Would
a picture
help you
understand
this?
6. 6
70%
of CIOs are
concerned
that lack of
mainframe
documentation
will hinder
knowledge
transfer and
create risk
2015 Vanson Bourne CIO Survey
7. 7
As a programmer or analyst, you need to
Produce:
• Change estimates
• Change specifications
Produce them:
• Quickly
• Accurately
Then…
• Change code
• Minimize increases in complexity
• Ensure that changes work
• Improve quality
But you are unfamiliar with the code and the platform!
9. 9
Digital Economy
Requirements
• Increased innovation velocity
and optimized performance
• Mobile, analytics, social, cloud
and Internet of Things
driving increased mainframe
demand
• Meet “Age of the Customer”
expectations
10. 10
But the Workforce
is Changing
• New workers are bringing new
expectations
• Shorter development cycles for
continuous delivery
• Need to safeguard the business
logic coded into your applications
Digital Economy
Requirements
• Increased innovation velocity
and optimized performance
• Mobile, analytics, social, cloud
and Internet of Things
driving increased mainframe
demand
• Meet “Age of the Customer”
expectations
12. 12
What Does a Solution Need to Provide?
Application Understanding
• Visualize your application portfolio
and how it’s utilized
• Understand application logic, data
and relationships
Elegant Simplicity in
Design and Usability
• Empower emerging workforce through
collaboration and communication
• Enable collaboration across platforms
and across Dev and Ops
Enable mainframe agility without compromising the virtues of the platform
13. 13
Introducing Topaz
Program Analysis
• Understand complex and
unfamiliar programs faster
Enterprise Data
• Discover, visualize and work
with both mainframe and
non-mainframe data in a
common, intuitive manner
Modern Interface
• IDE for essential mainframe
software development activities
19. 19
Benefits of Program Analysis
• Understand complex and
unfamiliar programs faster
• Improve application quality
and speed of delivery
20. 20
Benefits of Program Analysis
• Understand complex and
unfamiliar programs faster
• Improve application quality
and speed of delivery
• Maintain unfamiliar code
with confidence
21. 21
Benefits of Program Analysis
• Understand complex and
unfamiliar programs faster
• Improve application quality
and speed of delivery
• Maintain unfamiliar code
with confidence
• Transition next-generation to
unfamiliar platform and programs
30. 30
Benefits of Enterprise Data
• Understand complex
data relationships
• Improve test data quality
and speed of delivery
31. 31
Benefits of Enterprise Data
• Understand complex
data relationships
• Improve test data quality
and speed of delivery
• Create test data
with confidence
32. 32
Benefits of Enterprise Data
• Understand complex
data relationships
• Improve test data quality
and speed of delivery
• Create test data
with confidence
• Transition next-generation
to unfamiliar platform and data
Have you ever tried to build a piece of IKEA furniture?
It may look easy, but it’s really not.
Sometimes you are missing a piece and don’t realize it until you’re finished.
Other times there are too many parts and pieces to determine where things go and which piece fits with what. How do you even know where to start?
Those of you who have tried to build a piece of IKEA furniture know that it can be very overwhelming.
Having the instructions and a photo of the finished product helps you better understand how the furniture is put together; allows you to be more successful when you work with the individual pieces.
Having a photo of the finished product is also helpful for mainframe programmers, especially with all of the complexity inherent in mainframe programs and the new expectations and demands that are placed on them.
Imagine this:
You walk into your first day at a new job and you are shown 10,000 lines of code.
You’re asked to produce change specifications and estimates; implement changes quickly while reducing complexity and improving the quality of the code
The code is incredibly complex and you’ve never seen, let alone worked on, a mainframe before.
Plus, these programs don’t have any documentation and have been developed over 20, 30 or even 40 years.
All of the experience colleagues at your company have retired.
If you aren’t well-versed in the application or platform, this can be a very time-consuming task or lead to inaccurate estimates.
So you’ve inherited these programs and are expected to make them work, but you don’t understand how they are built.
This can be very daunting and overwhelming.
What do you do?
Now, as you take a look at these five value attributes, the last step of the whiteboard session that you want to conduct with a customer is to basically be able to cut this into two halves. And these two halves focus on what we call Value Today and what we call Essential Tomorrow.
The reason why we want to cut this picture in half is because when product management comes in to do a roadmap session with the customer, that roadmap will be broken up into a Value Today segment as well an Essential Tomorrow segment. So by conducting this whiteboard session what you’re going to do is draw a connection between the Mainframe Manifesto to the agreement on behalf of that customer to schedule and arrange a product roadmap session for us. The way you’ll make that connect is through these five value attributes for which product management will actually bring those to life as they actually go through our roadmap which scales the next 18 months.
Now, as you take a look at these five value attributes, the last step of the whiteboard session that you want to conduct with a customer is to basically be able to cut this into two halves. And these two halves focus on what we call Value Today and what we call Essential Tomorrow.
The reason why we want to cut this picture in half is because when product management comes in to do a roadmap session with the customer, that roadmap will be broken up into a Value Today segment as well an Essential Tomorrow segment. So by conducting this whiteboard session what you’re going to do is draw a connection between the Mainframe Manifesto to the agreement on behalf of that customer to schedule and arrange a product roadmap session for us. The way you’ll make that connect is through these five value attributes for which product management will actually bring those to life as they actually go through our roadmap which scales the next 18 months.
Speaking Points:
We are focused on 5 core attributes which drive our product strategy:
Application Understanding: which includes things like object visualization and the understanding of your application logic and how that applies to data relationship across your enterprise – a Data GPS if you will to view and understand where data goes to and comes from
IP Advancement: the investment you’ve made in Cobol, our support of Cobol 5.1 and enabling those Cobol calls into web services to be available for digital reuse so they are available in digital/mobile application – extending your current application to the new digital economy
IP Preservation: Continue to invest and protect your current IP portfolio. Things like inventory control logistics, inventory systems, core banking applications we will continue to keep costs down to preserve that investment
Cost/Performance Optimization: Maximizing the performance and the cost of the platform through methods to exploit the platform via specialty engines and reducing costs on workload placement for your 4 hour rolling averages. Enabling our technology with smart metrics that can measure your success in achieving your 4 hour rolling average goals.
Usability: Continue to innovate to help you manage the new demographics, skills, expertise and interests of your workforce. Today it may be eclipse, tomorrow it may be Siri….and then virtual reality…this allows you to unify people, systems of record, and overall enterprise business
Luckily for you, with the introduction of Topaz, Compuware provides a modern tool enabling analysts, programmers and testers to maintain and enhance applications on the mainframe as well as handle data across multiple platforms.
With Topaz it is not important to know the mainframe interface, just how to code and test.
This allows those working on the mainframe to work in an environment that is more familiar and comfortable to them.
Topaz allows you to:
Understand complex and unfamiliar programs faster
Don’t have to read through comments or outdated documentation
Don’t need to rely on experts who may no longer be available (retirement)
Can visually see how programs are designed and the application logic and dependencies that are inherent in the code
Ease the next-generation’s transition to the platform
Improve understanding of highly complex applications quickly and in an intuitive way
Provide elegant simplicity in design and usability
Give them programs that look and feel like the ones they are used to
Improve application quality and speed of delivery
Produce better change specifications
Speed up actual time to change programs
Maintain unfamiliar code with confidence
Topaz provides current information on a program that is updated based on changes made to the code
Extend each program’s value to the company
Further leverage mainframe assets
Easily identify and remove code flaws and dead code
Improve code reviews
Instantly see the impact your changes make on the program
Creating current documentation for other developers to take over seamlessly as needed
Topaz allows you to:
Understand complex and unfamiliar programs faster
Don’t have to read through comments or outdated documentation
Don’t need to rely on experts who may no longer be available (retirement)
Can visually see how programs are designed and the application logic and dependencies that are inherent in the code
Ease the next-generation’s transition to the platform
Improve understanding of highly complex applications quickly and in an intuitive way
Provide elegant simplicity in design and usability
Give them programs that look and feel like the ones they are used to
Improve application quality and speed of delivery
Produce better change specifications
Speed up actual time to change programs
Maintain unfamiliar code with confidence
Topaz provides current information on a program that is updated based on changes made to the code
Extend each program’s value to the company
Further leverage mainframe assets
Easily identify and remove code flaws and dead code
Improve code reviews
Instantly see the impact your changes make on the program
Creating current documentation for other developers to take over seamlessly as needed
Topaz allows you to:
Understand complex and unfamiliar programs faster
Don’t have to read through comments or outdated documentation
Don’t need to rely on experts who may no longer be available (retirement)
Can visually see how programs are designed and the application logic and dependencies that are inherent in the code
Ease the next-generation’s transition to the platform
Improve understanding of highly complex applications quickly and in an intuitive way
Provide elegant simplicity in design and usability
Give them programs that look and feel like the ones they are used to
Improve application quality and speed of delivery
Produce better change specifications
Speed up actual time to change programs
Maintain unfamiliar code with confidence
Topaz provides current information on a program that is updated based on changes made to the code
Extend each program’s value to the company
Further leverage mainframe assets
Easily identify and remove code flaws and dead code
Improve code reviews
Instantly see the impact your changes make on the program
Creating current documentation for other developers to take over seamlessly as needed
Topaz allows you to:
Understand complex and unfamiliar programs faster
Don’t have to read through comments or outdated documentation
Don’t need to rely on experts who may no longer be available (retirement)
Can visually see how programs are designed and the application logic and dependencies that are inherent in the code
Ease the next-generation’s transition to the platform
Improve understanding of highly complex applications quickly and in an intuitive way
Provide elegant simplicity in design and usability
Give them programs that look and feel like the ones they are used to
Improve application quality and speed of delivery
Produce better change specifications
Speed up actual time to change programs
Maintain unfamiliar code with confidence
Topaz provides current information on a program that is updated based on changes made to the code
Extend each program’s value to the company
Further leverage mainframe assets
Easily identify and remove code flaws and dead code
Improve code reviews
Instantly see the impact your changes make on the program
Creating current documentation for other developers to take over seamlessly as needed
So now that I’ve gone through my program to make changes, I need to test it.
To do so, you need to work with the data that drives the programs you manage.
But how do I know which data I need to test?
Topaz Enterprise Data allows you to visualize the relationships between data elements in your programs, allowing you to isolate and use the data you need for testing, without everything you don’t.
Imagine this:
You walk into your first day at a new job and you are shown 10,000 lines of code.
You’re asked to produce change specifications and estimates; implement changes quickly while reducing complexity and improving the quality of the code
The code is incredibly complex and you’ve never seen, let alone worked on, a mainframe before.
Plus, these programs don’t have any documentation and have been developed over 20, 30 or even 40 years.
All of the experience colleagues at your company have retired.
If you aren’t well-versed in the application or platform, this can be a very time-consuming task or lead to inaccurate estimates.
So you’ve inherited these programs and are expected to make them work, but you don’t understand how they are built.
This can be very daunting and overwhelming.
What do you do?
Imagine this:
You walk into your first day at a new job and you are shown 10,000 lines of code.
You’re asked to produce change specifications and estimates; implement changes quickly while reducing complexity and improving the quality of the code
The code is incredibly complex and you’ve never seen, let alone worked on, a mainframe before.
Plus, these programs don’t have any documentation and have been developed over 20, 30 or even 40 years.
All of the experience colleagues at your company have retired.
If you aren’t well-versed in the application or platform, this can be a very time-consuming task or lead to inaccurate estimates.
So you’ve inherited these programs and are expected to make them work, but you don’t understand how they are built.
This can be very daunting and overwhelming.
What do you do?
Imagine this:
You walk into your first day at a new job and you are shown 10,000 lines of code.
You’re asked to produce change specifications and estimates; implement changes quickly while reducing complexity and improving the quality of the code
The code is incredibly complex and you’ve never seen, let alone worked on, a mainframe before.
Plus, these programs don’t have any documentation and have been developed over 20, 30 or even 40 years.
All of the experience colleagues at your company have retired.
If you aren’t well-versed in the application or platform, this can be a very time-consuming task or lead to inaccurate estimates.
So you’ve inherited these programs and are expected to make them work, but you don’t understand how they are built.
This can be very daunting and overwhelming.
What do you do?
Imagine this:
You walk into your first day at a new job and you are shown 10,000 lines of code.
You’re asked to produce change specifications and estimates; implement changes quickly while reducing complexity and improving the quality of the code
The code is incredibly complex and you’ve never seen, let alone worked on, a mainframe before.
Plus, these programs don’t have any documentation and have been developed over 20, 30 or even 40 years.
All of the experience colleagues at your company have retired.
If you aren’t well-versed in the application or platform, this can be a very time-consuming task or lead to inaccurate estimates.
So you’ve inherited these programs and are expected to make them work, but you don’t understand how they are built.
This can be very daunting and overwhelming.
What do you do?
Imagine this:
You walk into your first day at a new job and you are shown 10,000 lines of code.
You’re asked to produce change specifications and estimates; implement changes quickly while reducing complexity and improving the quality of the code
The code is incredibly complex and you’ve never seen, let alone worked on, a mainframe before.
Plus, these programs don’t have any documentation and have been developed over 20, 30 or even 40 years.
All of the experience colleagues at your company have retired.
If you aren’t well-versed in the application or platform, this can be a very time-consuming task or lead to inaccurate estimates.
So you’ve inherited these programs and are expected to make them work, but you don’t understand how they are built.
This can be very daunting and overwhelming.
What do you do?
Imagine this:
You walk into your first day at a new job and you are shown 10,000 lines of code.
You’re asked to produce change specifications and estimates; implement changes quickly while reducing complexity and improving the quality of the code
The code is incredibly complex and you’ve never seen, let alone worked on, a mainframe before.
Plus, these programs don’t have any documentation and have been developed over 20, 30 or even 40 years.
All of the experience colleagues at your company have retired.
If you aren’t well-versed in the application or platform, this can be a very time-consuming task or lead to inaccurate estimates.
So you’ve inherited these programs and are expected to make them work, but you don’t understand how they are built.
This can be very daunting and overwhelming.
What do you do?
Improve code quality
Better testing scenarios
Simplify task of creating complete data extracts for testing purposes
Accurately identify impact of changing a piece of data
Reduce project timelines
Realize greater productivity from developers and testers who are now autonomous
Leverage data for strategic projects
Big Data
Other analytics projects
Less distractions for mainframe-skilled staff
Improve code quality
Better testing scenarios
Simplify task of creating complete data extracts for testing purposes
Accurately identify impact of changing a piece of data
Reduce project timelines
Realize greater productivity from developers and testers who are now autonomous
Leverage data for strategic projects
Big Data
Other analytics projects
Less distractions for mainframe-skilled staff
Improve code quality
Better testing scenarios
Simplify task of creating complete data extracts for testing purposes
Accurately identify impact of changing a piece of data
Reduce project timelines
Realize greater productivity from developers and testers who are now autonomous
Leverage data for strategic projects
Big Data
Other analytics projects
Less distractions for mainframe-skilled staff
Improve code quality
Better testing scenarios
Simplify task of creating complete data extracts for testing purposes
Accurately identify impact of changing a piece of data
Reduce project timelines
Realize greater productivity from developers and testers who are now autonomous
Leverage data for strategic projects
Big Data
Other analytics projects
Less distractions for mainframe-skilled staff
Photos provide a good roadmap for how to accomplish the things that we need to complete. Whether it be a complex mainframe program or a chair from IKEA.