View webinar recordings conducted by the IBM AI Applications Business Development Team

Connecting IBM Engineering Solutions with Simulink for an ISO 26262 Compliant Test Process

Date: November 12, 2020
Presenters: Nabile Khoury and Thabo Krick of BTC Embedded Systems AG

Standards like ISO 26262 for the development of safety critical systems in the automotive domain require to manage traceability between different types of artifacts in the development process. This traceability is in particular important when it comes to requirements and test cases, so that the following questions can be answered with confidence and accuracy at any project stage:

a. Did we create test cases for every requirement?
b. Which requirement(s) is/are covered by a particular test case?
c. Are there requirements which are not correctly implemented by the software?

One option to connect the different tools could be the use of exchange formats like Excel or ReqIf. But especially as todays embedded software development projects become more agile, these exchange formats are inefficient and error prone, as they introduce many manual import/export which can’t guarentee the consistency of the data.

To solve this problem, IBM has introduced the OSLC standard as part of the IBM Engineering solutions, which allows different development and verification tools to communicate directly with “IBM Engineering Test Management” and “IBM Engineering Requirements Management DOORS Next”.

We will show you how to efficiently perform an ISO 26262 compliant software test within a Model-based development process ensuring full traceability between requirements, test cases and test results.

Listen to November 12 recording here.

Shift left! Verify your requirements sooner using Model Execution and Model-Based Testing

Date: October 15, 2020. 2:30PM EDT
Presenter: Todd Dunnavant of IBM

Early verification of requirements “shifting left” is recognized as a key to delivering projects on time, on budget, with full functionality.  In this session, you’ll learn how you can shift left, proceed with greater confidence, and save time and money by leveraging IBM’s capabilities for animating system models and our unique capabilities for model-based testing.

Listen to October 15th recording here.

Build better requirements! Inject AI into your requirements engineering workflows

Date: October 15, 2020. 2:00PM EDT
Presenter: Rob Truban of IBM

A poorly written requirement is the earliest form of a defect and can be the most expensive to deal with if not caught quickly. Remove the risk of low-quality requirements by leveraging AI and RQA. With RQA, you can automate the requirements review process, saving considerable time while significantly improving your requirements’ quality. In this session we will present requirements management with AI utilizing IBM’s Requirements Quality Assistant.

Listen to October 15th recording here.

How the International Space Station insures reliablity and safety by unitilizing IBM DOORS Next Generation

Date: October 15, 2020. 1:30PM EDT
Presenter: Joveline Ollero and Sierra Matlock (NASA Contractors)

Methods for requirements management have evolved since the International Space Station (ISS) program began over 20 years ago. Requirements databases can provide improved traceability, visibility, and consistency of requirements data, however existing processes are structured around paper documents. The conversion to managing requirements through databases in existing document based projects can be difficult. Learn about how DOORS Next Generation is being leveraged within the long established ISS program as well as the developing Gateway program, and the unique challenges associated with both.

Listen to October 15th recording here.

Insightful Engineering at Enterprise Scale

Date: October 15, 2020. 1:00PM EDT
Presenter: Phil Bardasian of IBM

Teams facing the challenge of designing, developing and engineering sophisticated products that cost less, in shorter periods of time and with fewer resources, must not only engineer new technologies but also integrate new solutions that drive faster time to market at lower cost from trusted vendors. IBM Engineering Lifecycle Management (ELM) is a comprehensive, end-to-end solution that integrates technologies such as the Watson AI-powered Requirements Quality Assistant (RQA) to improve the quality of increasingly complex requirements.

Listen to October 15th recording here.

Testing external code including Simulink code with IBM Engineering Systems Design Rhapsody and TestConductor Add On

Date: October 1, 2020
Presenter: Dr. Hartmut Wittke – Software Engineer for the BTC Embedded Systems AG

In this presentation we show how the behavior of a system under development can be tested even if legacy code is part of the model behavior. The legacy code can be manually developed or coming froma Simulink workflow including auto-code generation with EmbeddedCoder. External code can be “unit tested” in Rhapsody with TestConductor, very similar to the testing of UML or SysML units.But also end-to-end tests can be executed where external codeplays a role as part of a bigger system or software model.

Our Presenter Dr. Hartmut Wittke studied Computer Science at the University of Oldenburg, Germany. He finished 1997 his Diploma. From 1997 to 2005, he worked for OFFIS in Oldenburg and finished with his PhD Thesis on compositional specification verification of complex embedded systems. Since 2005 he develops UML based testing tools as software engineer for the BTC Embedded Systems AG

Listen to October 1st recording here

Streamlining Aviation compliance with IBM ELM

Date: September 24, 2020
Presenter: Eran Gery – WW A&D Industry lead for IBM ELM

Airworthiness certification is becoming more demanded by customers today, way beyond just civil airliners. Today there is growing demand for Airwothiness certification for civil and military UAVs, eVTOL and also military aircraft. It is also well known in the industry that airworthiness certification might incur very significant additional engineering cost – up to doubling the cost of the project.

In this webinar we will briefly discuss the airworthiness compliance stack starting with the SAE ARP 4754a, with a special focus on the most common one DO-178C. We will describe and demonstrate how an effective engineering practice and toolchain can dramatically reduce the cost overhead of the compliance work. We will show how the various certification objectives are streamlined with the IBM ELM solution resulting in significant cost reduction, as well as improved quality and time to delivery.

Listen to September 24th recording here.

Test Driven Development with IBM Engineering Systems Design Rhapsody and TestConductor Add On

Date: September 10, 2020
Presenter: Dr. Hartmut Wittke – Software Engineer for the BTC Embedded Systems AG

In this presentation we show how the behavior of individual components can be developed with a test driven development approach in a model based development context. Given are architecture and sequence diagram specifications referring to the interfaces defined by the architecture. The sequence diagrams are reused as test cases for the component under development. By successively taking the specifications into account, behavior adhering to the specifications is developed and tested in an incremental work flow.

Listen to September10th recording here.

Higher quality and less cost with IBM Engineering Systems Design Rhapsody ‐ TestConductor Add On

Date: August 28, 2020
Presenter: Christian Wachtendorf – Project Leader at BTC Embedded Systems AG

How to achieve and maintain quality by model based testing? In this presentation we show how Rhapsody TestConductor helps verifying the system or software under development meets its requirements with a high degree of automation. Model based development and testing enable traceability between requirements, design and test, allowing impact analysis, coverage measurement, efficient reviews, and reuse of specification data for testing.

Listen to August 28th recording here.

Requirements Based Testing for Rail Projects

Date: August 4, 2020
Presenter: Jim Herron – CTO of Island Training

In this session, you will not only see a demonstration of the IBM capabilities, but more importantly hear from a large rail industry power user speak about how they have benefited from this testing methodology with numerous major rail projects around the world.

Whether you are currently using DOORS/DOORS NG or other tools to manage your requirements, you will learn the benefits of requirements-based testing and how using a test management solution can significantly streamline your testing process

Listen to August 4th recording here.

How Model Based Systems Engineering Can Assist With a Move To a New Product

Jul 30, 2020

Date: July 30, 2020
Presenter: Marty Stolz and Pierre Bentkowski of IBM – Technical Sales

How we reused assets for one design and transformed it to a new product. We identified similar requirements, blocks and Use Cases and used these as the starting point with discussions with our customer. Once we discovered the new requirements, we built the mockup control panel and ran simulations on our Analysis and design to verify our model to validate with the customer. Model-based systems engineering is a systems engineering methodology that focuses on creating and exploiting domain models as the primary means of information exchange between engineers, rather than on document-based information exchange.

Listen to July 30th recording here.

Formal Code Reviews in Engineering Workflow Management

Jul 23, 2020

Date: July 23, 2020
Presenter: Jim Herron of Island Training – IBM Certified Technical Specialist

Use one tool to collaborate across teams, manage code, run standup meetings, plan sprints and track work. Available on premises and on the cloud. IBM Engineering Workflow Management acts as the critical link between required and delivered work by enabling teams to manage plans, tasks and project status. It provides the flexibility to adapt to any process, so companies can adopt faster release cycles and manage dependencies across both small and complex development projects. This webinar you will see a full code review cycle in action.

•Submit code for review
•Open the review to view changes
•Create associated issues
•Make required code modifications and resubmit for review
•Approve modifications and deliver corrected code

Listen to July 23rd recording here.

Leveraging Human Intelligence to Access the Power of Intelligent Systems

Jul 9, 2020

Date: July 9, 2020
Presenter: Dr. Larry Kennedy – President of the Quality Management Institute

Technology applications are trending rapidly toward encouraging dependence upon AI and ML to supplant human responsibility and leadership. “Smart” machines are providing analytical advantages that can forecast trouble, rapidly matrix a response and execute a solution with precision. But is human intelligence keeping pace with the demands AI and ML place upon us for terminal decision-making? What have we learnedfrom the Spassky/Deep Blue challenge? We’ll discuss how to leverage human capacity with the Machine and the human requirements associated with intelligent systems.
Listen to July 9th recording here.

Validating Requirements in Engineering Test Management

Jun 18, 2020

Date: June 18, 2020
Presenter: Jim Herron of Island Training – IBM Certified Technical Specialist

Increase efficiency and quality of systems and software delivery with test planning, workflow control, tracking and metrics reporting. IBM EngineeringTest Management (ETM) is a collaborative, quality management solution that offers end-to-end test planning and test asset management, seamlessly integrated with requirements, requirement coverage, workflow, and test defects.Teams can seamlessly share information and use automation to speed complex project schedules and report on metrics in real time for informed release decisions. In this webinar you will see examples of the four test case execution scenarios available in ETM.


Listen to June 18th recording here.

Requirements Management with DOORS Next and DOORS Classic

Jun 11, 2020

Date: June 11, 2020
Presenter: Richard Watson of IBM – Product Manager for Requirements Management

IBM® Engineering Requirements Management DOORS® (DOORS) is a leading requirements management tool that makes it easy to capture, trace, analyze, and manage changes to information. Control of requirements is key to reducing costs, increasing efficiency, and improving the quality of your products. In this webinar we will present what is new with DOORS Next and DOORS 9.0. Highlights will be on ELM v7.0 of new product names, new banners, and new launchpad.
Listen to June 11th recording here.

Transportation and Construction – Optimizing Requirements Collaboration

Jun 4, 2020

Date: June 4, 2020
Presenter: Eran Gery – Distinguished Engineer of IBM and Jim Herron – CTO of Island Training

No industry sector requires more efficient adherence to Requirements Management than does the Transportation and Construction sector. Today more than ever, major projects must be executed through complex teaming arrangements between business partners, contractors, sub-contractors and providers of systems and subsystems. Requirements flow from customers, be they public or private sector entities, and must be further decomposed, tracked, managed and validated throughout the lifecycle of the project. Failure to comply with critical requirements is a guarantee of project cost overrun.

This webinar will show you several best practices and new capabilities to enhance collaboration, improve project performance and mitigate overall risk.

Listen to June 4th recording here.

Digital Engineering in Practice: Transforming the Engineering Process for Aerospace & Defense

May 26, 2020

Date: May 26, 2020, 12:00 pm
Presenter: Eran Gery of IBM – Distinguish Engineer, A.I. Applications

Today’s products and systems in the Aerospace and Defense industry around the world are becoming more complex with new technologies rapidly disrupting the traditional norms. Disruptive innovations are creating an environment of “art of the possible”, which unfortunately also creates new threats to maintain compliant and safe systems. On this front of A&D there is a call for “digital engineering initiative”, looking at these suppliers to adopt digital techniques that enable a leap in speed and efficiency of bringing new systems from concept to operational state. Similar concepts are being sought in other industries like automotive and medical devices. The IBM engineering lifecycle platform (ELM) offers a set of capabilities that enable such a transformation of the engineering process along the line of the digital engineering initiative. In this talk we will present the core capabilities of the ELM platform and demonstrate how it supports digital engineering practices along the product engineering cycle. We will look at an “end to end” practice from early stakeholder needs to verification and validation, involving advanced approaches such as model based engineering, agile systems engineering and AI to realize the digital engineering vision.
Listen to May 26th recording here.

IBM Engineering Reporting v7.0 (JRS, PUB, ENI)

May 14, 2020

Date: May 14, 2020, 2:00 pm
Presenter: Fariz Saracevic of IBM – Sr. Offering Manager

This session provides an overview of what’s new in IBM Engineering Reporting v7.0 (Jazz Reporting Service (JRS), IBM® Engineering Lifecycle Optimization – Publishing (PUB) and IBM® Engineering Lifecycle Optimization – Engineering Insights (ENI). JRS is an IBM Engineering reporting solution when users want to create traceability and statistical reports. It allows you to quickly and easily consolidate data from a variety of sources across your applications and project areas. PUB automates the generation of document-style reports across your deployed IBM Engineering and third-party tools, whether these reports are needed for formal reviews, contractual obligations, regulatory oversight, or ad hoc use. It allows the creation of high-quality documents in formats like PDF, HTML, Word, Excel, or XSL. ENI helps users visualize, analyze, and gain insight from your engineering lifecycle data. Engineering teams can improve their understanding of the relationships in complex lifecycle data and demonstrate compliance with regulatory and industry standards.
Listen to May 14th recording here.

What’s New in IBM Engineering Lifecycle Management 7.0 Enterprise Deployments

May 7, 2020

Date: May 7, 2020, 2:00 pm
Presenter: Tim Feeney and Paul Ellis of IBM

In addition to all the significant functional enhancements IBM Engineering Lifecycle Management (ELM) v7.0, the release also includes many important changes and improvements related to enterprise deployment. In this session we will highlight these changes and other best practice and guidance updates. With the DOORS Next replatform being one of the more significant architectural changes in this release, we will review the new scale limits and highlight best practices to ensure a successful migration.
Listen to May 7th recording here.

Let IBM Watson Assess Your Requirements with IBM RQA

Apr 30, 2020

Date: April 30, 2020
Presenter: Jim Herron – Technical Professional of Island Training

Your engineering requirements drive development – if they contain errors, so will your products. Add IBM Engineering Requirements Quality Assistant to DOORS Next or DOORS 9 to increase requirement quality during creation. Using Watson Natural Language Service and pre-trained AI, Requirements Quality Assistant has built in quality indicators designed to be consistent with guidelines from the International Council on Systems Engineering (INCOSE) for writing complete, clear and testable requirements to accelerate your review process, increase requirement quality and reduce training for junior requirements engineers. This webinar will show you how IBM RQA will you allow you assess your requirements with Watson AI.
Listen to April 30th recording here.

IBM ELM – What’s New in 7.0 – performance enhancements- features, UI, Reporting

Apr 23, 2020

Date: April 23, 2020
Presenter: Amy Silberbauer – IT Specialist and Solution Architect at IBM

This webinar will introduce the IBM Engineering Lifecycle Management solution version 7.0 and its performance enhancement features including user enhancement features and reporting.
Listen to April 23rd recording here.

Subscribe to our newsletter!

[newsletter_form type=”minimal” lists=”6″ button_color=”undefined”]
Imran Hashmi Canadian Hub for Requirements Management
Imran Hashmi Canadian Hub for Requirements Management

What is the Requirement Management for Infrastructure and Public?

When we speak about Infrastructure and Public, we are typically referring to Architecture, Engineering, Construction (AEC) companies, as well as Federal, State and Local Governments. This includes, but is not limited to, rail, subway and other large complex public/private works projects.Use of Requirements Management in the AEC industry is very limited in comparison to use in the system and software world. There is a lack of identification, management and traceability of the requirements during the project development process in construction projects. AEC firms are seeking ways to improve client satisfaction and improve project performance. Much like our typical client, AEC firm requirements are the basis for every project, defining what the stakeholders need and what the end product must meet in order to satisfy those needs. Requirements are the basis for project planning, risk management, acceptance testing, and more.

Also Checkout:

Imran Hashmi Canadian Hub for Requirements Management

Aerospace/Defence

Embrace transformation and start leveraging the Engineering Lifecycle Management (ELM) portfolio for the Aerospace and Defense (A&D) industry. A&D clients struggle to deliver more function in their products while also responding to the market needs, all while releasing on time, ahead of the competition. In addition to these pressures, they must leverage a solution that allows for better reporting to meet regulatory compliance and sparks collaboration with their suppliers.

https://www.ibm.com/internet-of-things/learn/mbse-smart-paper/

Imran Hashmi Canadian Hub for Requirements Management

Medical Devices

IBM Engineering Lifecycle Management (ELM) is the leading end-to-end engineering solution on the market. ELM aids Medical Device companies with their everyday challenges by reducing their compliance risks. Using the ELM solution allows clients to be fully integrated in their engineering approach so predictability of problems is increased. Medical Device companies use ELM to know what works and what doesn’t, ultimately allowing for them to move more seamlessly, cost effectively and progress in the development lifecycle.

  • Offer products to the market on time by leveraging strategic reuse to drive innovation
  • Ensure compliance with design controls, internal company’s SOP and regulatory/ quality requirements (ISO-13485, IEC-60601, ISO-14971, IEC-62304, IEC-60812, ISO623660)
  • Can easily create, trace, analyze, validate, automate, and deliver products quickly to the market
  • Audit ready: traceability with lifecycle disciplines
  • Build products that are engineered with integrity
  • Leverage software automation
  • Effectively collaborate with the team

IBM Engineering helps medical device companies:

  • Strategically reuse assets and identify changes between variants
  • Collaborate among teams
  • Maintain traceability
  • Faster Time to Market
  • Increased Product Quality for High Complexity
  • Better Reporting and Documentation to Meet Regulatory Compliance
  • Transparency and Visibility across Development teams
  • Shorter Development Cycle Due to Reuse

This article was written by Bartosz (Bart) Chrabski of SmarterProcess – with some minor contributions from yours truly.

You may remember an old western movie titled The Good, the Bad and the Ugly starring Clint Eastwood. Testing can sometimes feel the same way.

Imran Hashmi Canadian Hub for Requirements Management

In today’s dynamic product development arena requirements keep changing and evolving. There is a relationship between three dimensions – namely cost, quality and time.

Ideally, we would have sufficient budget, time, and – product teams would be able to implement a high-quality product. In practice, it’s rarely the case that projects have enough budget and time. Often projects run over budget and experience time constraints. As a result, testing efforts are rushed and the quality of the product suffers.

Verification and validation of products – software and hardware – are some of the most critical steps in the development process and typically consume 30% to 35% or more of the total cost and effort in most projects.

Testing is often the least planned part of the development lifecycle. This lack of rigor can lead to the delivery of lower quality products and applications, which have a negative impact on customer satisfaction.

This article outlines some of the most common challenges encountered in testing efforts and presents several recommended practices. These practices will improve the efficiency and accuracy of your testing processes.

Problems resulting from poor testing processes have many different sources, often from poor planning or execution of testing tasks.

Below are some of the causes we have observed in real world projects.

• Lack of an independent test team
Most small project teams do not have an independent test team. The people who act as testers are at the same time developers, engineers, or analysts – often focused on other responsibilities, which may lead to incomplete or ineffective testing. Depending upon your industry, regulations may require a separate dedicated testing team.

• Limited understanding of the testing process
In small projects, often a project manager also acts as a test manager and may lack of appropriate knowledge and skill to plan and execute test activities – and their responsibilities of the two roles may conflict.

• Poor test planning
Planning the testing process is rarely perfect – testing is often only done to the extent that time is available. Sometimes testing is like an exorcism designed to get rid of evil spirits in a project. Often the person responsible for planning the testing may not be familiar with the testing process and may miss important steps.

• Lack of qualified resources
It can be difficult to find staff with the motivation and skills to do the testing. Since locating the appropriate skills can be challenging, positions are often filled with inexperienced testers, which may lead to incomplete or ineffective testing.

• No test data (no data-driven testing)
In our experience clients often underestimate the importance of good test data. Frequently, test data does not cover all possible conditions occurring in the application. In some cases, no test data is delivered at all. The result is that not all scenarios will be tested, which leads to quality issues.

• Lackluster test environment or product configuration
Some practitioners involved in testing underestimate the importance of getting the test environment and its configuration set up correctly. It’s standard practice to treat development, test, and production systems differently – mostly because they have differing security, data, and privacy controls. Testing in production can lead to corrupted or invalid production data, leaked protected data, overloaded systems and more.

If there is a separate dedicated test environment it may not match the proposed production environment. The wider the gap between test and production, the greater the probability that the delivered product will have more defects. It is common for test teams to clone the production data and use it for testing purposes. This approach can be time-consuming, error-prone and may not meet the data protection policies.

• Poor release management
Many projects do not have a well-documented release management process for testing purposes. This lack of rigor may lead to inconsistencies. Often, we have seen situations where a patch designed to correct a problem injects new ones, which may lead the system to fail.

• Inadequate defect management
In small organizations defects are sometimes not tracked centrally or are manually tracked using spreadsheets or email. This approach leads to inaccuracies or failures to correct defects. Manual operations are also burdened with a considerable amount of work to maintain the process.

• No central repository of test cases
Many legacy products/systems may have been used for years and often a test case repository is not available or maintained. If they are maintained, they usually contain just the latest requested changes and not the complete functionality of the product/system. New team members will struggle to learn the full functionality and to perform tests without reference to past test cases. This can lead to incomplete and error prone testing.

• Incomplete regression tests
When test case repositories do exist they are often outdated or incomplete. As functionality changes test cases should also be maintained and updated to match those changes. Regression tests that are limited to new capability results in poor test coverage and subsequently leads to new defects being injected to a partially tested product.

• Limited testing automation
Often, repetitive testing is performed manually. Automation can aid in creating the test environment building as well as functional regression testing, load testing, coverage testing and release management.
We suggest you evaluate the automation you have available inhouse and from 3rd parties. Assess the value of using automation versus the cost and effort. Is this a product/system that will be around for a long time and the effort of automation will continue to be used? Or is this a short-term fix with a limited life?

• Lack of training
Members of the project teams may not be familiar with the tools that are available to them or may not be trained on how to use them. Consequently, although the organization has tools they are not used. Lack of tool usage/knowledge can result in the limited ability to effectively track errors, supervise the entire process, or define measures and metrics to manage system development effectively.

• Lack of knowledge of available methodologies
Many project teams lack documented and understood testing methodologies and processes. Lack of following existing methodologies/processes or the absence of a documented approach leads to an inefficient testing process. The adopted methodologies and methods do not always have to be written down in the form of official documents, but they must be understood and applied in practice.

• Measures and metrics
Often, organizations collect data on ongoing projects but sometimes do not analyze the testing processes to seek improvements. For example, if it is uncovered that poorly documented or understood requirements are creating testing errors, the need arises to improve requirements elicitation and documentation process. This postmortem analysis provides an opportunity for iterative improvement of the testing phase.
We recommend testing retrospectives to see what the team has learned and what can be done to improve the overall development process.

Best Practices

The following are the best market practices. These practices are recommendations that are not applicable in every test team and not in every organization. Based on our practical experience we suggest:

  • Have an independent test team, whenever possible.
  • Plan the participation of the test team at an early stage of product development. It’s important to have the test team participate in the analysis stage and aid in assessing the functional and non-functional requirements in terms of their validation capabilities and the associated testing workload.
  • Define a strategy for testing the software with the customer.
  • Provide for collaboration among engineers, architects, designers, project managers, developers and testers in planning activities related to the testing process.
  • The preparation of test data should take place together with the construction of test cases. The data created should be subject to versioning and creating base lines.
  • When test environments use production test data, special attention should be paid to disguising or modifying the test data in order to ensure compliance with data protection legislation.
  • Create separate environments for testing and development. The test team should keep the test environment as compatible as possible with production.
  • Focus on the preparation and verification of the test environment before the start of each test phase.
  • Use tools to support configuration management, error tracking and requirements management to facilitate the work and increase its efficiency.
  • Build and maintain a test case repository that can be accessed by the project team.
  • Maintain traceability between tested functionality (requirements) and test cases in a matrix or other method. This provides information on the functionality being retested, limiting the time and scope of testing. Traceability relationships will reduce the number of regression tests by using the ability to track the relationship between requirements and test cases.
  • Maintain a repository for unit tests; use component simulation tools to support team sharing.
  • Use measures and metrics in the project to analyze the results. The data collected should help to improve the software development process and the efficiency of the team.
  • In our experience, a good testing process is one of the most important activities to ensure the delivery of value to both the development team and client.

Regardless of the type of project, testing should be given special attention. Testing must be well planned, executed in a repeatable documented manner by qualified and trained people. Without this supervision it will be difficult to call tests effective.

The IBM Solution

IBM test management solutions can help you avoid common software development traps.

Lack of planning, lack of metrics, and collaboration with stakeholders, ineffective test management, and lack of test automation, all lead to problems. When we don’t measure how we’re doing and do not continually make improvements, the risk escalates and the project can get out of control.

IBM software test management solutions incorporate many best practices that help you avoid these common traps and enjoy the benefits. IBM Test Management is a collaborative, web-based, quality management solution that offers comprehensive test planning and test asset management from requirements to defects. It enables teams to seamlessly share information and use automation to speed project schedules and provides metrics for informed release decisions. It is available both on-premise or as a SaaS solution.

Key capabilities include:

  • Communications support – Support communication among teams that are geographically dispersed using features such as event feeds, integrated chat, review, approval and automated traceability.
  • Automation tools integration – IBM Test Manager integrates with many test automation tools including 3rd party tools, homegrown scripts and more. Execute tests with all kinds of tools and collect test results—all from a central location.
  • Advanced reporting capabilities – Address the needs and concerns of quality managers, business analysts and release management using advanced reporting capabilities – making it easier to assess readiness for delivery.
  • Comprehensive test plans – Provides test plans that clearly describe project quality goals and exit criteria, while tracking responsibilities and prioritized items for verification and validation.
  • Risk-based testing – Provides risk-based testing for prioritizing the features and functions to be tested based on importance and likelihood or impact of failure, supporting risk management best practices.
  • Requirement tools integration – Test Manager works with the IBM Requirements DOORS Next Generation tool. You can link test cases and mark them as suspect whenever requirements are modified.