Tag Archive for:Requirements & Requirements Management

EU Medical Device Regulation (MDR) and In-Vitro Device Regulation (IVDR)

In this blog, we recap the “An Overview of the EU Medical Device Regulation (MDR) and In-Vitro Diagnostics Regulation (IVDR)” webinar.

Looking to stay ahead of ever-evolving regulations governing medical devices?

In this webinar, we discuss the continual rollout of the EU Medical Device Regulation (MDR) and In-Vitro Device Regulation (IVDR) and the impact they’re having on the medical device industry.

Vincent Balgos, Director of Medical Device Solutions at Jama Software andSaby Agai, Sr. Consultant at Jama Software, provide a high-level overview of the new regulations, along with general industry observations and future considerations for organizations with medical products marketed in the EU market area, including:

  • New classifications, grandfathering clause, and risk management requirements
  • The number of notified bodies, backlog, and remediation efforts for placed products
  • Future considerations regarding the compliance compatibility of IVDR & FDA and traceability
  • Finally, learn how the Medical Device Framework in Jama Connect® can help streamline your compliance efforts and ensure your products meet all the necessary regulatory requirements.
Below is an abbreviated transcript and a recording of our webinar.

为什么它是有道理的存储网络安全风险的人吗agement Items Inside a Requirements Management System

Saby Agai:So, in the first part of the webinar we will talk about the EU medical device regulations. There is a small agenda to that. Basically, we would like to show the key changes and challenges that the MDR means compared to the MDD. We would also like to talk a little bit about what we see as the challenges for the process transformation of the medical device developers and also a bit of discussions with the race on the timeline for the MDR. The second section is on the MDR for the MedDev engineering. So basically, how the engineering teams can do anything with the MDR. We’ll talk about harmonized standardization. How does that fit in the concept of the MDR? And some of the medical device best practices that we would recommend. So the medical device regulations now has quite a bit of history because the MDR is valued also for existing [inaudible 00:04:15] devices and also for all the new devices.

The medical device regulations entered into force historically in May 2017, and there was a bit of extension period in 2020 that the certificates issued under the MDD before the MDR remained valid up to four additional years. So it was a bit of a time extension for manufacturers to migrate the legacy devices to the MDR. Recently 2023, the EU commission had the new rule based on 607 was the number of it on the time extension for the medical device regulations. So there are two-time extension now in force for December 2027 and 2028 for all devices. As part of this modification, the commission removed the sale of period from the original context of the Medicaid device regulation.

Three key area that we would mention that we see as key challenges with the MDR is first is the technical documentation. So because of the legacy medical devices has to be reclassified in a context of the new MDR, those manufacturers highly likely will face it extended set of documentation for market clearances in the EU. It’s particularly true for software as a medical device because, basically the class one level has removed by legislation for all software as a medical device. The other thing on the technical documentation is that the MDR is far more prescriptive about the requirement content of the technical documentation, and it’s particularly true and there are more detailed requirements needed for the quality management system. So the manufacturer will have to ensure that they not only have full access and control for the documentation of the device, but also they should keep the eye on the market and the vigilance market, post-market vigilance area, as well as publication or new common specifications.

RELATED:Buyer’s Guide: Selecting a Requirements Management and Traceability Solution for Medical Device & Life Sciences

Agai:So there is a bit of higher focus on the post-market activities in the context of the MDR. And the technical documentation basically has two key parts in Annex II, annex III it’s detailed. Annex II there is a list of requirements for the technical documentation itself for the device design, and also, in Annex III, we see details or requirements for technical documentation post-market surveillance. So nothing particularly new, only an extended set of expectation and requirements for all these contents. Little note something on the technical documentation. So historically, the technical documentation has a tradition to be seen as a burden on the med tech developers and additional administrative work. And quite often, at the end of the development cycle, there is a massive effort made to make what is documentation available for regulators and also for market clearance. It definitely could require very intense administrative work from the engineering sometimes stress involved and also, the content creation has not much help or not much support for the regional engineering activities, which is the development.

So these content created purely to support the market access activities and it should not necessarily should be a case, though. So, for example, we in Jama has a medical solution. It’s a example proven a tool actually can support both med tech developers to enhance the development efficiency as they develop a new device as well as to support these technical documentation needs at the same time. So it’s a opportunity also for organizations to get most out of using a tool when they thinking about to ease the burden of the medical device regulation technical documentation part.

RELATED:Jama Connect®Validated Cloud Package for Medical Device and Life Sciences

Agai:第三但不是最后,有一个新的particularly in EU requirements for the unique device identifier. So basically, 2021 was a deadline to register an MDR UD MDR devices with the UDI in the [inaudible 00:09:02] framework, and for the IVDR, it’s 2022. Looking into purely on the numbers, we could say that the content of the MDR compared to the MDD is actually four time heavier. So the extent and the legal tax basically is four time more. There are five plus on axis that we can see, and there is a special attention on safety and patient safety particularly because 293 times mentioned the safety word in MDR where in the MDD was the 24. All these numbers also telling that the regulators in EU want to have higher scrutiny compared to the MDD, and they also have more details on that level of expectation that they would like to see from manufacturer. And there is a definite focus on patient safety that we can see.

Two more things to mention is that quite often, in the context of the MDR, the legacy devices should be reclassified into a higher level class. So it means that the quality management process support is more intense, and more support expected. More activities and works are expected from the manufacturer to keep the same device basically on the market. It also could mean that companies should take a step for high-level maturity as an organization and it’s true also for the design and device development activities. So one of the challenge with that is that if we talk about the same device with higher regulatory scrutiny, how do we retain and enhance profitability? Because the administrative burden is definitely something that goes towards the cost part of the profitability. So the design and development goes under higher level of process expectation in that sense, and it goes higher level of design documentation needs as well. So one of the advantages using the tool in general medical device environment that the medical solution can ease actually this work and enable a bit quicker, and the developers can leverage a little bit more help on these challenges.

To watch the entire webinar, visit
An Overview of the EU Medical Device Regulation (MDR) and In-Vitro Diagnostics Regulation (IVDR)


Quality Management System (QMS)

Jama Connect®Features in Five: Using Jama Connect with a Quality Management System (QMS) for Medical Device & Life Sciences

Learn how you can supercharge your systems development process! In this blog series, we’re pulling back the curtains to give you a look at a few of Jama Connect®’s powerful features… in under five minutes.

In thisFeatures in Fivevideo,Steven Pink, Senior Solutions Architectat Jama Software®,will provide insight into how Jama Connect is commonly used in the context of a medical device Quality Management System (QMS.)

In this video, we will:

  • 提供如何Jama连接是我们一般开云官网手机网页版入口ed in the context of a medical device quality management system
  • Demonstrate key features that provide value to those responsible for quality and regulatory matters
  • Offer clear guidance on how Jama Connect – a requirements management solution – supplements a separate quality management system within a cohesive ecosystem of complimentary applications

VIDEO TRANSCRIPT:

Steven Pink:Welcome to this segment of Features in Five. I’m Steven Pink, a senior solutions architect at Jama Software and today I’ll be giving an overview to help provide some insight into how Jama Connect is commonly used in the context of a medical device quality management system.

We’ll demonstrate some of the key features that provide value to those responsible for quality and regulatory matters and clear guidance on how Jama Connect, a requirements management solution supplements a separate quality management system within a cohesive ecosystem of complimentary applications.

We often work with medical device or life science companies that have some form of quality management system whether that be paper-based or an eQMS and they’re working to introduce a requirements management solution like Jama Connect for the first time.

For individuals with a quality and regulatory background that have not yet worked in an environment using a formal requirements management solution, this can seem like a foreign and potentially disruptive change to a well-defined process.

RELATED:Jama Connect®vs. DOORS®: Filters, Search, and Analysis: A User Experience Roundtable Chat

Pink:So before we provide some insight to help address that common concern, we want to provide some context as to why an organization would want to introduce Jama Connect in the first place. Prior to using a formal requirements management solution, engineering and R&D are often left managing requirements related data during development in documents, spreadsheets and tools like Jira, Confluence, or SharePoint that are not designed to support complex requirements management.

In this type of scenario, engineering often finds it difficult to manage and maintain complex traceability as they work. So they often leave it to be completed at the end of a phase or milestone as opposed to maintained in real time. This often leads to gaps or errors being identified late in development which is significantly more costly to address the later they’re identified. In addition to having difficulty maintaining traceability, engineering often struggles to manage change to requirements and understand the full impact of each change.

They’ll find it hard to keep data in sync between requirements stored in documents or spreadsheets and other tools like Jira or Azure DevOps where data resides in silos. They’ll often waste a lot of time or effort compiling documentation for their design history file at the end of a given phase before these artifacts can be signed off and stored as an auditable record in a document control system. As products increase in complexity and regulatory guidelines continue to increase in rigor, these challenges grow exponentially for engineering.

To help address these challenges, Jama Connect provides engineering and product teams with a working environment to manage requirements, risks, tests and the traceability between these items in real time. We call this managing live traceability.

RELATED:Buyer’s Guide: Selecting a Requirements Management and Traceability Solution for Medical Device & Life Science

Pink:从质量和监管的角度来看,贾马有限公司开云官网手机网页版入口nnect’s relationship rule diagram provides a governing structure to ensure that requirement traceability is maintained following proper design controls and quality procedures. This structure makes it simple to manage change, perform impact analysis, and ensure traceability coverage throughout development.

The first thing we see when working on a project in Jama Connect is the dashboard with traceability rules. This makes it easy to understand the expectations for traceability and identify exceptions through dashboard widgets, such as gaps in test coverage or finding unmitigated risks.

With data living and Jama Connect, managing documentation and traceability becomes easier. Once documentation has been authored, it can be sent for a formalized review. Cross-functional teams can utilize the review center to conduct iterative reviews and significantly increase the quality and efficiency of the feedback being given.

Once all items for a given release have been reviewed and approved, these items can automatically transition into an accepted and blocked state, ensuring that changes are not made to approved items unintentionally. When the time comes to generate auditable documentation, Jama Connect allows teams to automatically or manually capture baselines and export these baseline documents out of the system to be signed off in a separate document control system as an auditable record. This process reduces the time spent manually reworking documents as part of the QMS process. And these document export templates can easily be customized to match existing internal quality standards and ensure consistency in the way requirements and other details are documented.

In the end, Jama Connect can help engineering team more easily manage their work and simplify the process of maintaining traceability. As a byproduct of their efforts, quality, and regulatory teams are provided with higher-quality auditable documents without making changes to their existing quality management systems.

RELATED:How to Use Requirements Management as an Anchor to Establish Live Traceability in Systems Engineering

To view more Jama Connect Features in Five topics visit:Jama Connect Features in Five Video Series


Industrial Manufacturing and Consumer Electronic Development

In this blog, we preview whitepaper, “The Top Challenges in Industrial Manufacturing and Consumer Electronic Development” — ClickHEREto read the entire thing.

The Top Challenges in Industrial Manufacturing and Consumer Electronic Development

From supply chain disruptions to digitization – learn more about what development teams are up against and get expert suggestions for how to overcome them

PART I: The Top Challenges in Industrial Manufacturing and Consumer Electronic Development

Industrial manufacturing has always been a cornerstone of economic growth and development worldwide. Over the last few years (or more), the
industrial manufacturing sector has undergone significant transformation; from the introduction of automation and robotics to advanced analytics.

Today, industrial manufacturers are facing a host of new challenges that are forcing teams to rethink their strategies and adapt to changing market influences and demands.

The need to increase operational efficiency while also cutting expenses is one of the most pressing issues facing industrial manufacturing — a challenge not unique to this industry alone. Manufacturers are under a lot of pressure to optimize their processes, cut lead times, and boost product quality due to intense competition and rising customer expectations. Teams must also figure out how to lower production costs and waste while adhering to strict industry regulations. To be boost innovation and optimize operations, teams need to have not only an in-depth knowledge of the production process, but also access to cutting-edge technologies like the internet of things (IoT), artificial intelligence (AI), product development platforms, and machine learning (ML).

In this whitepaper, we’ll explore some of the challenges industrial manufacturing teams are up against and offer expert insights and strategies on how to work through them.

CHALLENGE #1: Supply Chain Disruptions

The industrial manufacturing sector may continue to endure supply chain disruptions as a result of the ongoing COVID-19 epidemic — primarily due to a lack of workers, raw materials, and component parts. Outside of the pandemic, supply chain interruptions are also being caused by trade conflicts and tariffs.

Supply chain disruptions continue to be a complex challenge for industrial manufacturers, and engineers play a critical role in identifying and mitigating these risks. By developing robust supply chain management strategies and leveraging innovative and modern technologies, engineers can help to reduce the impact of disruptions and ensure a more efficient and reliable manufacturing process.

RELATED:IEC 61508 Overview: The Complete Guide for Functional Safety in Industrial Manufacturing

CHALLENGE #2: Environmental Sustainability

As demand for environmentally friendly and sustainable products rises, firms must adopt more sustainable procedures in their business operations. This can entail cutting back on carbon emissions, switching to renewable energy, and reducing waste and pollution.

Consumers in the manufacturing sector have become more and more demanding of environmental sustainability. As the world’s population shifts to be more environmentally concerned, customers are increasingly seeking out goods that were produced using sustainable methods, such as using renewable energy sources, lowering carbon emissions, and limiting waste and pollution.

While environmental sustainability is of vital import for society (and meeting modern ethics standards), it may also be very advantageous to a business’s bottom line. Manufacturers who place a high priority on sustainability can significantly lessen their energy and resource consumption, improve the reputation of their brands, and boost their market share and consumer loyalty.

今天的前卫的工业产品,体制开云足球app下载官网最新版ms, and software developers are embracing a variety of environmentally friendly practices and modern technologies to both optimize production and satisfy this growing demand for environmental sustainability.

CHALLENGE #3: Automation and Digitalization

The industrial sector is changing as a result of the growing use of automation and digital technology, but these changes also bring issues. Manufacturers must upskill their staff, invest in new technology, and manage the risks related to cyber-attacks and data security.

In order to maximize productivity, cut costs, improve product quality, and adapt to changing customer demands, businesses across all sectors, including industrial manufacturing, are automating and digitizing more of their processes. By enabling the automation of production processes and the use of data analytics to enhance operations, automation and digitalization technologies are revolutionizing the
manufacturing sector.

Here’s how manufacturers are leveraging new technology:

  • Robotic automation:It is possible to boost productivity, reduce labor expenses, and improve product quality by using robots and other automated technologies to complete tasks that were previously completed by hand.
  • Digital twin technology:Manufacturing processes are simulated and improved using digital models of physical systems in the real world. By spotting and fixing issues before they arise, manufacturers can increase the quality of their goods while lowering costs.
  • Predictive maintenance:In order to predict when repairs are required and prevent unscheduled downtime, predictive maintenance uses data analytics and machine learning algorithms. This increases equipment dependability and lowers maintenance costs.
  • Internet of Things (IoT):物联网涉及到传感器的使用和其他井斜ces to collect data on processes and equipment. The data can then be used to optimize processes, reduce downtime, and improve product quality.

Automation and digitalization technologies are being adopted in industrial manufacturing for a number of reasons, including efforts to lower costs, increase efficiency, and meet shifting client demands. By lowering the need for human labor and enhancing quality control, this move toward automation can also increase safety.

RELATED:The Complete Guide to ISO/IEC/IEEE 15288:2015 — Systems and Software Engineering and Lifecycle Processes

CHALLENGE #4: Lack of Talent

There is a talent deficit in the industrial manufacturing sector, notably in fields like engineering, computer science, and data analytics. Manufacturers must invest in training and development initiatives to recruit and keep people in order to meet this challenge.

The labor shortage in industrial manufacturing has been an ongoing challenge for many years, and the COVID-19 pandemic only exacerbated it. Several factors play into the labor shortage, including an aging workforce, a lack of skilled workers, and shifting attitudes towards traditional work among younger generations.

To overcome the labor shortage, teams are implementing a range of strategies, including:

  • Investing in automation and robotics:Automation and robotics reduce the need for manual labor. By investing in automation technology, organizations can reduce their reliance on human labor costs and increase productivity.
  • Offering training and upskilling programs for employee attraction and retention:Many organizations are offering programs to their current employees to help them acquire new skills and advance their careers. The cost of replacing an employee is shockingly expensive. In fact, studies show that every time an organization replaces a salaried employee, it costs six to nine months’ salary on average. By investing in their employees, manufacturers can increase employee retention and reduce the need to hire new workers.
  • Implementing flexible working arrangements:组织所有行业正在拖ards more flexible working arrangements, such as remote work and flexible scheduling, to attract and retain workers who are looking for a better work-life balance.
  • Collaborating with educational institutions:Many industrial manufacturing organizations are partnering with educational institutions to create training programs and apprenticeships that prepare students for careers in manufacturing.
  • Offering competitive incentive and benefits packages:Offering competitive compensation and benefits packages to attract and retain workers might include; higher salaries, flexible working environment, competitive health benefits, retirement plans, and other incentives.
This has been a preview of The Top Challenges in Industrial Manufacturing and Consumer Electronic Development whitepaper. ClickHEREto read the entire thing!


Cybersecurity

In this blog, we recap the “Why it Makes Sense to Store Cybersecurity Risk Management Items Inside a Requirements Management System” webinar.

In this webinar, “Why it Makes Sense to Store Cybersecurity Risk Management Items Inside a Requirements Management System”, learn about the implementation of the Threat and Risk Analysis (TARA), the centerpiece of the new Automotive Cybersecurity standard ISO 21434.

许多公司目前使用电子表格来重击op TARAs, which can be challenging when managing large sets of requirements across distributed teams and car line variants. In this webinar, we’ll examine why a requirement management system (RMS) is well-suited to manage the TARA work product and can make a significant impact on managing this data across teams, supporting compliance audits, and assessments.

Attendees will gain insights into TARA’s complexities and how the right tooling solution can make a difference in managing this data across teams, supporting compliance audits and assessments.

Key Takeaways:

  • The Threat and Risk Analysis or TARA is the centerpiece of the ISO 21434 Automotive Cybersecurity standard
  • Overview of TARA
  • ISO 21434 compliance requirements when implementing TARAs
  • Why an RMS is well-suited to manage TARAs

Below is an abbreviated transcript and a recording of our webinar.

为什么它是有道理的存储网络安全风险的人吗agement Items Inside a Requirements Management System

Kevin Dibble:Thanks, Juliet. Okay. I’m going to just go through the agenda and then get right into 21434. I’ll start with a high-level introduction and then get into the focus of our topic today, which is the threat and risk analysis, which is a centerpiece of 21434, also known as the TARA. And then make an argument for the management of a TARA using an RMS or a requirement management tool. And then Steve will take over and talk about what that would look like in Jama software and summarize with some key points of managing TARAs in Jama versus some traditional methods. And then we’ll have time for some questions.

So with that, again, this is going to be a very high-level overview of 21434. I have a feeling that some of you have worked in cybersecurity for some time, others are just brand new to the term. And so, I want to touch on this as a basis for the rest of the discussion.

And so, first, what is 21434? It is the automotive industry standard for developing cyber secure systems. After several years of review, it was approved in August of 2021 as the method for developing cyber secure systems. In terms of the standard itself, it’s structured and uses a lot of the same terminology as the functional safety standard called ISO 26262. So if you’re familiar with functional safety, then this standard will make a lot of sense the way that it’s organized. Some of the terms such as an item definition, a concept phase, a cybersecurity goal, even TARA parallels functional safety terms like functional safety concept, functional safety goals, or the HARA, Hazard and Risk Analysis. And so, that’s just a reference point as you’re learning about this new standard. Now as far as its scope, it covers or it applies to passenger vehicles and cargo vehicles.

So just a little bit different than ISO 262 there, passengers would include buses, commercial or non-commercial. I think even tripods and some of those other types of motorcycle hybrid type of devices are in or vehicles are in scope as well. It applies to series production and it uses a lifecycle that starts at the request for a quotation for an item. And I’ll define that in a little bit and goes all the way through to the end of cybersecurity support. So like functional safety, we’re not talking about supporting the risks and the hazards associated in this case with threats from attackers leading up to SOP, but it extends far past that. In fact, in 21434, instead of using the term SOP or start of production, which is a critical milestone in any automotive product development program, they call that milestone the release to post-development.

RELATED:Functional Safety (FuSA) Explained: The Vital Role of Standards and Compliance in Ensuring Critical Systems’ Safety

Dibble:And I want to camp on that for just a second because it raises a really important point and it’s very relevant to what we’re going to talk about regarding the TARA. Release to post-development. So the automotive industry is under a lot of change and OEMs want to be or are becoming mobility providers and services will be sold after the car is released. And some of those services weren’t even imagined at the time the car was sold. That’s so different than where the automotive industry was even five years ago. And this standard recognizes that and embraces it along with another important concept, which is that the world of cybersecurity and the landscape for threats and the technologies and the tools that are used to attack vehicles is constantly changing. And so, at the release to production, what is assumed to be protected in terms of say a set of cryptographic keys or a communication bus might be more vulnerable in five years than it was when the car was released because of new techniques, new methods, new tricks, new hacks, and other things that have been discovered.

And so, that’s an important concept because it feeds to our idea that we’re going to get into about the TARA as a living document, as a living asset that begins all the way at the concept phase at the beginning of the high-level architectures of the item or the system in the car. And extends all the way until the end of life for cybersecurity support, which is 10, 15 years down the road. Now, the 21434 has both requirements for developing cyber secure systems, is kind of what I’m showing you on the right, but it also has process requirements. And to that end, there is an audit of the process and an assessment of the results of your project according to 21434. That assessment piece is important for our discussion because when we think about the TARA and the pieces of it or the items of the TARA, then we have to think in terms of what are the evidences we need to leave behind and produce in order to pass an assessment, very important consideration.

RELATED:A Guide to Road Vehicle Cybersecurity and Risk Management: Part 1

Dibble:所以,我们审核的过程assessments for the end result. So that’s very brief overview of 21434. I want to make sure I leave you with the… If you remember anything about 21434 besides the TARA, you’ll hopefully remember this, is to manage unreasonable risk of damage to road users due to a malicious attack to a vehicle or a vehicle data, confidentiality, integrity and availability. Let me unpack that for just a second. Unreasonable risk, this is when you get into a car, when you operate a vehicle, you assume some risk. But that risk doesn’t include driving down the highway at 70 miles an hour, turning right and the car going left or the headlights going off while you’re on the highway at night. It applies to road users. That’s the people that use the road, the driver, the passengers, and the people surrounding it.

All of that is our scope for how we’re going to define threats according to 262 and then mitigate them against malicious attack due to… That’s the cyber aspect of this. And then what’s being attacked and what are we protecting? We’re protecting vehicle systems, functions, data, et cetera. We call them assets according to their properties, confidentiality, integrity and availability. There could be more properties, that’s the CIA that we’re protecting. Why is cyber such a hot topic? Well, I would say there’s several reasons, but here’s two of the big ones. On the left of my slide, the advent of the connected car coupled with the automated driving functions. I’m not going to read through all the stats here, but the connected car is here. It’s 2 billion in terms of the market in 2021 to grow to $5.3 billion in 2026. And the connected car is accessible via the internet, accessible via Bluetooth and other network interfaces, which all result in attack services. It also has a lot more software.

To watch the entire webinar, visit
为什么它是有道理的存储网络安全风险的人吗agement Items
Inside an Requirements Management System


Insurance Framework

In this blog, we recap our press release, “Jama Software®Announces Insurance Framework to Simplify Insurance Product Development ” – To read the entire thing, clickHERE

Jama Software®Announces Insurance Framework to Simplify Insurance Product Development

Streamline and Accelerate Insurance Product Development with Jama Connect®

Jama Software®, the industry-leading requirements management and traceability solution provider, has released an insurance framework and dataset that streamlines and simplifies product development for the insurance industry.

With increased challenges and a changing landscape, insurance carriers are facing competitive pressures related to growth and profitability. Carriers can now use Jama Connect®提高产品开发效率开云足球app下载官网最新版和德尔iver high quality products on time and on budget.

“Insurance carriers are facing increased pressure to bring new and competitive products to market, across multiple jurisdictions and lines of business. At Jama Software, we’ve developed a customizable framework to allow our insurance customers to create a scalable and standardized approach to managing their up-front product requirements through downstream systems development. This framework allows carriers to innovate, bring products to market quicker, and ultimately better serve their customers.”

Steven Meadows, Solutions Lead for Insurance Industry, Jama Software

“With the increased complexity associated with developing insurance products, the traditional method of insurance product development is no longer viable.” stated Tom Tseki, Chief Revenue Officer at Jama Software. “The challenges associated with business analysts leveraging spreadsheets to try to ensure everyone is working off a live single source of truth is nearly impossible. Business analysts are constantly chasing development teams to get progress and status updates while trying to manage changes and inform all the upstream and downstream activities/teams of the changes before too much work is completed. This disjointed and out-of-sync approach means a lack of real-time visibility and control which results in significant rework, increased costs, and product delays.” Tseki continued.

“一个真正的解决方案来管理保险产品re开云足球app下载官网最新版quirements and specifications across multiple states, products, and departments has long been overdue. Jama Connect is that solution, bringing business units and IT together on a common requirements platform. It’s intuitive enough for non-technical users, configurable around existing processes and toolsets, and sophisticated enough to support everything from requirements reuse, comparisons, collaboration, change control, integrated test management, and more. As product portfolios get more complex, it’s important to manage requirements so they don’t manage you. The Jama Connect insurance framework places your organization in the driver’s seat – increasing product quality and standardization, speed to market, and scalability. It’s a game changer.”

Allison Roberts, President, Genesis Management Consulting

With effective requirements management andLive Traceability™in Jama Connect, insurance carriers can easily manage new product requirements from ideation through to implementation, enhancement, and revisions — enabling them to meet regulatory requirements, maximize development efficiency, and accelerate speed to market.

If you want to learn more about how Jama Connect can help accelerate insurance product development, please download the datasheet below, orclick hereto speak with one of our experts and book a free trial.

If you want to learn more about how Jama Connect can help accelerate insurance product development,
please refer to our datasheet:Download the Datasheet

About Jama Software

Jama Software is focused on maximizing innovation success for complex development. Numerous firsts for humanity in fields such as fuel cells, electrification, space, autonomous vehicles, surgical robotics, and more all rely on Jama Connect®尽量减少产品失败的风险,延迟,c开云足球app下载官网最新版ost overruns, compliance gaps, defects, and rework. Jama Connect uniquely creates Live Traceability™ through siloed development, test, and risk activities to provide end-to-end compliance, risk mitigation, and process improvement. Our rapidly growing customer base of more than 12.5 million users across 30 countries spans the automotive, insurance, financial services, medical devices, semiconductor, aerospace & defense and industrial manufacturing industries. For more information about how Jama Connect can help Insurance industries, please visit:Jama Software Solutions: Financial Services and Insurance

Read the official press release here:
Jama Software®Announces Insurance Framework to Simplify Insurance Product Development

What is DOORS


Aerospace & Defense

In this blog, we recap the “Launch Your Aerospace & Defense Product Development Processes with Jama Connect®” webinar.

In this webinar, we discuss exciting new features in our updated Jama Connect®for Aerospace & Defense framework. These updates include refreshed solutions for cybersecurity, the DoD Range Safety Requirements Library, and other libraries of standards.

Also, Cary Bryczek, Solutions Director for Aerospace & Defense at Jama Software®, shares best practices in the Jama Connect platform and demonstrates significant new features that can help you further enhance your aerospace and defense product development processes, including:

  • ARP 4761A – Guidelines and Methods for Conducting the Safety Assessment Process on Civil Airborne Systems and Equipment
  • DO-326A – Airworthiness Security Process Specification
  • US CFR Parts 21-57 Pre-imported Libraries and Usage
  • Defense MBSE and Digital Engineering Guidance
  • NASA and Air Force Range Safety Requirements
  • European Cooperate with Space Standards (ECSS) Pre-Imported Libraries

Below is an abbreviated transcript and a recording of our webinar.

Launch Your Aerospace & Defense Product Development Processes with Jama Connect®

Cary Bryczek:让我们开始吧。因此,机载系统解决方法n. So when we say solution, it’s really a complete set of frameworks, example projects and the procedural documentation that goes along with that. It’s really intended to accelerate your implementation of Jama Connect, especially those that are developing Airborne Systems and the Airborne Systems components that are going to live on these aircraft. When you utilize these frameworks, you can either have zero set up time, so we’re developed the solution to align with the standards and you can also tailor it. So your consultant who does team with you could help you tailor it to meet your very specific business needs as well. So it’s really designed for any organization, whether you’re a startup in the Airborne Systems world or whether you’re a longtime developer of aircraft.

The Airborne Systems Solution is really designed to help you ease the path to regulatory compliance, to help the engineers produce the evidence and collect that evidence in coordination with the regulatory requirements and the industry standards that are used that are requiring the acceptable means of compliance. Today’s. In today’s world, there is a lot of new engineers that are being employed in Airborne Systems development. And really this particular template is helpful to them because it really gets them to understand “How am supposed to do development?” We all know that Airborne Systems development has the most onerous and rigorous standards of any industry. And teaching our new engineers is very time-consuming. So having this template with all of the guidance built into it and the procedure guide really helps our new engineers to get started.

有三个组件到机载系统s Solution that what we call the data set, a procedure guide, and the success program. The data set essentially is what you get when you install Jama and it has the templates, it has a ready to use configuration that matches those regulations. It has all of the item types, all of the reports, all of the best practices built right in. And then the procedure guides and the documentation of the reports essentially show you how the Airborne Systems template is meeting the industry standards. So how does it meet ARP4754, how do you use the solution to meet DO-178. That’s sort of a thing.

RELATED:Jama Software®Delivers Major Enhancements to the Jama Connect®for Airborne Systems Solution

Bryczek:And then we also pair our solution with specific consulting. So our consultants already are very familiar with the regulations with working with our customers that have been delivering and developing Airborne Systems already, as well as systems engineering best practices. Some of our customers have interesting supply chain needs. And so they might want to use an additional tool that we package called data exchange. That’s just an add-on to the solution.

So when we look at the framework itself, there are a lot of industry standards that we support. These industry standards are the acceptable means of compliance that the FAA and EASA recognize in order to meet type certifications. So we have those processes that come right out of those standards built right in to the framework. So that framework consists of specially configured item types, pick lists and views of that information. Our relationship rules are aligned to the types of trace matrices these particular standards are calling for. We have workflows and guidance for how you conduct reviews of information as well. We have the libraries of standards, so if you need to comply with the different CFR parts, we actually have those pre imported. This is something new that we’ve added and we’ll talk about that a little bit more. The framework includes these document export templates as well as risk templates and analysis templates and more.

Now this is a company with a procedure guide. So along with not only just the template itself in Jama, we give you the procedure guide. You can take this guide and tailor it to meet your specific needs as well. This procedures guide is updated. So as a subscriber to the Airborne Systems Solution, any updates we make or new releases like what we have right now is included with your subscription. It just makes it easy for everyone to kind of understand “How do I use Jama if I need to meet these industry standards?”

RELATED:Digital Engineering Between Government and Contractors

Bryczek:Also with this particular release is the configuration and update guide. So this is new this time around. This particular guide gives a very detailed description of the entire dataset. It includes all of the types that we’ve defined, all of the pick lists that are defined, all of the relationship rules, all of the workflows. So if you need to update from your existing Airborne Systems Solution and take in aspects of the new release, it makes it really easy for you guys to update as well. This might be something as well… So if you tailor from your existing Jama solution and you want to keep track of that, something like this might be a really great way for you to document your own implementation of Jama itself.

So exciting. This is one of the new things. So we have for cybersecurity, DO-326A is an acceptable means of compliance for doing security analyses. There are a significant number of new item types that have been added to the solution that comprise our cybersecurity solution as well as how do you really do the airworthiness security analysis. Essentially there are seven steps to do this particular type of analysis. This really starts with developing your PSecAC. And for those of you who are maybe new to Airborne Systems development or are not familiar with DO-326 or cybersecurity, it is a process that’s sort of done in tandem with both the system development and safety. But this is different in that this is analyzing the intentional unauthorized electronic interaction. So it’s really designed to find ways that hackers or bad actors might be accessing parts of the Airborne Systems that you don’t want them to.

To watch the entire webinar, visit
Launch Your Aerospace & Defense Product Development Processes with Jama Connect®


Finding Information

Jama Connect®Features in Five: Finding Information

Learn how you can supercharge your systems development process! In this blog series, we’re pulling back the curtains to give you a look at a few of Jama Connect®’s powerful features… in under five minutes.

In thisFeatures in Fivevideo,Carleda Wade, Senior Consultantat Jama Software®,walks viewers through various ways of filtering and finding information within Jama Connect.

In this session, viewers will learn:

  • How to find information within Jama Connect®
  • Use search boxes throughout the application
  • Use facet filters to narrow search results
  • Interact with predefined filters
  • Create and manage new filters

Follow along with this short video below to learn more – and find the full video transcript below!

VIDEO TRANSCRIPT:

Carleda Wade:In this session, we will learn how to find information within Jama Connect, use search boxes throughout the application, use facet filters to narrow search results, interact with predefined filters, and create and manage new filters. So now let’s jump into our Jama instance.

Now we’re going to show you a couple different ways that you can search throughout the software. So here on our homepage we have this search bar. So let’s say I’d like to look for scheduling, since we just did manual scheduling in the previous session.
If I click on submit, you’ll see all these results. These results will show anytime the word scheduling shows up in any of the various projects. As you can see, this is a lot of results. So maybe we want to apply a filter so that we can narrow our list. So here I can click on filter items, and maybe potentially search for a keyword.

但我也可以缩小这通过观察确定project. So we’ve been working in our Jama 101, and then maybe I want to just look at system requirements, and let’s say stakeholder requirements. So here you’ll see are just the items that meet those two requirements. Another way to do this is by an advanced search. If I do an advanced search, first I can create a new filter. So let’s say I want to look for scheduling in my Jama 101 project, and I want to look at system requirements with the keyword of scheduling. When I do this, you can see here that I can preview, and that there will be three results. So if I click on there, it will give me a preview. And I can choose to save my filter. So now, essentially I’ve created a brand new filter.

Next, if I click here from my project explorer on filters, you’ll be able to see all of the various filters that are available. If I click on bookmarks, you’ll see this is the one that I just created, scheduling. And this little icon here indicates that it’s been bookmarked, or it’s become one of my favorites. If I go through the all, you can see other filters that have already been created within the system.

RELATED:Jama Connect®vs. DOORS®: Filters, Search, and Analysis: A User Experience Roundtable Chat

Wade:So let’s take a look at what happens when you right click. So when you right click on a filter. There are a few different options. So I could choose to remove this from my bookmarks if I so to desire. I could also choose to duplicate this. So let’s say for instance, this particular filter houses a lot of good information, and I want to be able to modify that information without changing the original filter. Maybe I would first duplicate this filter, then add onto it. I could also choose to edit the filter and view the criteria. If so desired, I could delete it. Another way to do this is by an advanced search. If I do an advanced search, first I can create a new filter. So let’s say I want to look for scheduling in my Jama 101 project, and I want to look at system requirements with the keyword of scheduling.

When I do this, you can see here that I can preview, and that there will be three results. So if I click on there, it will give me a preview. And I can choose to save my filter. So now, essentially I’ve created a brand new filter. Next, if I click here from my project explorer on filters, you’ll be able to see all of the various filters that are available. If I click on bookmarks, you’ll see this is the one that I just created, scheduling. And this little icon here indicates that it’s been bookmarked, or it’s become one of my favorites. If I go through the all, you can see other filters that have already been created within the system.

So let’s take a look at what happens when you right click. So when you right click on a filter. There are a few different options. So I could choose to remove this from my bookmarks if I so to desire. I could also choose to duplicate this. So let’s say for instance, this particular filter houses a lot of good information, and I want to be able to modify that information without changing the original filter. Maybe I would first duplicate this filter, then add onto it. I could also choose to edit the filter and view the criteria. If so desired, I could delete it.

RELATED:How to Use Requirements Management as an Anchor to Establish Live Traceability in Systems Engineering

Wade:Another really interesting thing to see is if I choose to apply the filter to the explorer. When I do that, you’ll see that only the items that meet the filter requirements show up, instead of the full exploratory like it did before. So that’s pretty interesting.
Going back in, the last option is send for review. So let’s say for instance, for this stakeholder requirements in draft status. If I wanted to go ahead and move these requirements from draft, I could choose right here from the filtered screen to send this for a review. And it would just open up in the review center. Another really interesting thing to see is if I choose to apply the filter to the explorer. When I do that, you’ll see that only the items that meet the filter requirements show up, instead of the full exploratory like it did before. So that’s pretty interesting.

Going back in, the last option is send for review. So let’s say for instance, for this stakeholder requirements in draft status. If I wanted to go ahead and move these requirements from draft, I could choose right here from the filtered screen to send this for a review. And it would just open up in the review center. Another way to be able to search is if we go to our activity stream. So here you can see there’s a little search bar for our activity stream. So let’s say I also typed in scheduling here. Or let’s say I wanted to see what Sarah has done within my stream. Here you can see all of the activities that Sarah has done within my instance here.

Another way to search for information is, let’s go back into our manual scheduling and go to our activities. Here you’ll see we have yet another search function, if we’d like. And then also, we could apply filters here if we so desire. Also, whenever using filters such as either here or any of the locations, we can also use built in operators. So let’s say we wanted to look for intelligent and scheduling in our project. You’ll see here that it comes up.

RELATED:Jama Connect User Guide: Find Content

To view more Jama Connect Features in Five topics visit:Jama Connect Features in Five Video Series


Total Cost of Ownership

Jama Connect®vs. IBM®DOORS®: Total Cost of Ownership: A User Experience Roundtable Chat

Increasing industry challenges and complexities are pushing innovative organizations to consider modernizing the tool(s) they use for requirements management (RM). In this blog series,Jama Connect®vs. IBM®DOORS®: A User Experience Roundtable Chat,we’ll present several information-packed video blogs covering the challenges that teams face in their project management process.

In the10th and final episodeof our Roundtable Chat series,Preston Mitchell–Sr Director, Global Business Consulting at Jama Software®– andSusan Manupelli–Senior Solutions Architect at Jama Software®– discuss the total cost of ownership in product management.

To watch other episodes in this series, clickHERE.

Watch the full video and find the video transcript below to learn more!

VIDEO TRANSCRIPT:

Preston Mitchell:All right. Welcome everybody, to episode 10 in our vlog series. Today, we’re going to be talking about total cost of ownership. I’m Preston Mitchell, the senior director of solutions at Jama Software, and I’m joined by my colleague, Susan Manupelli. Susan, do you want to introduce yourself?

Susan Manupelli:Sure. My name’s Susan Manupelli. I’m a senior solutions architect here at Jama Software, but I came from IBM, where I was a test architect for the last 20 years on some of their requirements management tools, so primarily Rational DOORS Next Generation and RequisitePro actually, before that.

Preston Mitchell:Excellent. Like Susan, I was a former IBM-er as well, so a user of many of those tools. Today, as you can see, we want to talk about kind of three main categories of total cost of ownership, IT infrastructure, so these are things like the actual physical hardware, the FTE administration costs, so like upgrades, maintenance, and then also the opportunity costs of when you do not adopt best-in-breed tools and processes. Why don’t we first start it off with the IT infrastructure costs? You know, Susan, in your experience with other RN tools, what have you found to be the challenges in this area?

Susan Manupelli:Sure. I’ll talk first about DOORS Next Generation. You know, DNG’s part of the ELM suite of products, that’s based on the Jazz architecture. It’s a very complex architecture. There’s a large number of servers you need, or VMs, to be able to stand up the solution. There’s an app server or some version of WebSphere. There’s a DB server for every application. So at a minimum with DNG, in addition to the app and DB server, you also would need a JTS server, an additional reporting server, [inaudible 00:02:08] or Data Warehouse. And if you have configuration management enabled, then there’s two additional servers that come with that, so for the global configuration manager and the LDX server. So-

Preston Mitchell:Interesting.

Susan Manupelli:And then of course, if you use any of the other applications of the ELM suite, there’s a server and database for those.

RELATED:Traceability Score™ – An Empirical Way to Reduce the Risk of Late Requirements

Preston Mitchell:Yeah, that’s quite a contrast to Jama, where we just require one application server and then a database server, which could be shared, actually, with other applications. Of course, that’s as far as self-host customers. Cloud customers really have no IT infrastructure costs at all, and I think that’s one of the biggest benefits of adopting a tool like Jama Connect. Okay, great. Next, I’d love to talk about the human or FTE maintenance costs that go along with tools. Susan, what’s your experience with other requirements management tools around the FTE costs?

Susan Manupelli:Sure. I’ll start off with DOORS Classic, which is an older client-server technology, and what I mean by that is that every user had to have software installed on their computer that was compatible with the server, so it was what we referred to as a thick client. An upgrade or maintenance of that would mean pushing out updates to however many users you have in your organization, potentially could be hundreds. So there was a lot of logistics involved with trying to get that upgrade done.

Preston Mitchell:Got it, and yeah, I imagine that’s downtime for the users, and a lot different than just a web-based tool that I sign in with my browser. The other thing that I know in working with customers that have migrated from DOORS Classic is DXL scripts and customization. Maybe you could talk a little bit about the hidden costs with those things.

Susan Manupelli:Yeah. Basically, any kind of customization that you want to do in DOORS Classic, you had to have somebody that could write a DXL script for it, that’s kind of a specialized skill, so there were costs with maintaining those, and particularly if they were used by across the organization.

Preston Mitchell:Is that any better with DOORS Next Generation?

Susan Manupelli:With DOORS Next Generation, there’s no DXL scripting or anything like that, but the thing that’s challenging with DOORS Next Generation is the upgrades and maintenance. Upgrades were often very complex and time-consuming. There was pretty high risk of failure, and then of course you have the time involved in roll back and trying it again. There’s also the ongoing maintenance of the middleware, would require a highly technical admin with some specialized skills in maybe database optimization, so Oracle or Db2. Also, keeping the system running optimally requires a full-time, highly skilled administrator for the ELM suite.

Preston Mitchell:Really? Full-time just for the backend? Wow.

Susan Manupelli:Yeah.

RELATED:Eight Ways Requirements Management Software Will Save You Significant Money

Preston Mitchell:Yeah, that’s definitely different than kind of what our self-hosted customers experience. I mean, we try to make the self-hosted upgrades very easy and straightforward. It’s a button click in the admin console. And then obviously, for the majority of our customers who use our cloud solution, there’s really no upgrade or maintenance that they have to do at all. We push the upgrades for them. We handle that for them in an automated process, that’s validated and verified. So yeah, definitely different. Well, let’s transition to talk about adoption costs, and I want to bring my screen share up again, because you and I have spoken about really the opportunity costs of not using best-in-breed tools or processes, and it kind of really comes down to measurement. We really believe using Jama Connect, we can reduce the negative product outcomes, because we can help you measure your process performance. As management guru, Peter Drucker, said, “If you can’t measure it, you can’t improvement.” So Susan, maybe you could touch on what I find are the three primary ways that we can help our customers measure their performance.

Susan Manupelli:Sure. First of all, we can measure the quality of the requirements. This means properly define… making sure the requirements are properly defined, that they’re complete and consistent. And we actually have a new product, Jama Connect Advisor, that helps in this area. As far as the digital engineering, we can measure the level of collaboration that’s happening in the tool, the number of reviews, and the output from those reviews. And then also for live traceability. Traceability is one of the key reasons why people use a requirements management tool, and Jama does it better than any other tool that I’ve used. And in addition, we can measure how well you’re actually capturing that traceability.

Preston Mitchell:Yeah. And speaking to that, especially on the live traceability, we have for our cloud customers, this great benchmark, where we anonymize all the data, and you can actually see how you stack up against your peers in the industry with regards to the traceability completeness of your projects. So some really great return on investment by utilizing our cloud offering and being able to see the actual performance compared to your peers in the industry. Ultimately, I think everyone realizes the later you are in a product development lifecycle, it’s much more expensive to actually fix any errors that are found. So our whole goal at Jama Connect is really to lower the total cost of ownership, but really actually make your product development less costly by finding and fixing those errors way earlier in the cycle, in the requirements definition phase. Well Susan, thanks again for the quick chat, and sharing your perspective on cost of ownership. Appreciate it.

Susan Manupelli:Great. Thanks, Preston.

Preston Mitchell:Bye, everybody.

Is your data working for you? A consistent and scalable data model is instrumental for achieving Live Traceability™ and making data readily available across the development lifecycle.

Download ourJama Software® Data Model Diagnosticto learn more!

Thank you for watching our 10th and final episode in this series, Jama Connect vs. IBM DOORS: Total Cost of Ownership. To watch other episodes in this series, clickHERE.

To learn more about available features in Jama Connect, visit:Empower Your Team and Improve Your Requirements Management Process


Scaled Agile Framework (SAFe)

What is a Scaled Agile Framework (SAFe) and How Does it Help with Complex Software Development?

What is a Scaled Agile Framework?

Scaled Agile Framework, or SAFe for short, is a robust framework for managing significant software development projects. It provides guidance on how to organize tasks, manage risk, improve predictability, and maintain the benefits of Agile development.

The SAFe methodology can be used to organize and coordinate large-scale software development projects and is a comprehensive structure that provides guidelines for scaling Agile development methods — from modest, single-team projects to larger, multi-team ones.

SAFe offers a scalable and adaptable approach to task planning and management that reduces risk, boosts predictability, and takes advantage of Agile development’s benefits. The SAFe techniques, roles, and artifacts provide guidance on how to manage dependencies, align teams, and consistently deliver value while enabling teams to work together under a shared framework and language.

SAFe’s essential elements include:

  • Agile Teams:SAFe describes how Agile teams should function as well as the tasks and responsibilities of each team member.
  • Program Backlog:A prioritized list of work that serves as a guide for value delivery.
  • Program Increment:Refers to the time-boxed period of time where teams produce value.
  • Solution Train:The task of coming up with a solution falls under the purview of a multidisciplinary group known as the “Solution Train.”
  • Agile Release Trains (ARTs):A collection of Agile teams working together to create a solution.
  • Value Streams:A series of steps that the organization uses for delivering value to customers.
  • Program Increment (PI) Planning:A regularly scheduled, joint planning session that brings teams in the ART come together to organize and plan tasks, and align on vision, roadmap, and cross-team dependencies.

RELATED:The Easiest Ways to Reduce Product Development Expenses in 2023

What kinds of businesses employ a Scaled Agile Framework?

Organizations that create and deliver complex goods, such as software, often employ the Scaled Agile Framework (SAFe) — particularly in settings where there are many teams, large-scale projects, and numerous stakeholders. SAFe is especially helpful for enterprises that need to manage dependencies, coordinate work across various teams, and consistently deliver value. Organizations across a range of sectors, including technology, finance, healthcare, government, and more, use SAFe.

Due to the fact that SAFe offers a flexible and scalable approach to Agile development, it is employed by both large corporations and smaller companies. The framework is a popular option for firms looking for a complete approach to managing large-scale software development projects, since it can be customized to match the unique demands of each organization.

Do companies have access to software platforms and technologies that facilitate the use of a Scaled Agile Framework in development?

Yes, there are several software platforms and solutions that support Scaled Agile Framework development for businesses. These technologies offer support for a number of SAFe-related features, including as backlog management, value stream mapping, continuous delivery, Agile planning and tracking, and more.

Two popular platforms that support SAFe include:

  • Jira Software:This popular Agile project management tool offers features like backlog management and Agile boards.
  • Azure DevOps (formerly Visual Studio Team Services):A Microsoft solution that offers support for Agile project management, continuous delivery, and more.

These are only a couple of the many tools that businesses using SAFe have access to. The best tool for a company depends on its individual requirements and preferences, and many companies decide to utilize a variety of tools to support various SAFe implementation components.

RELATED:Research Notes: Traceability Score™

How Can Jama Connect®帮助组织采用Ag)ile Framework?

Jama Connect® is a product, systems, and software development platform that can help organizations adopt and implement a Scaled Agile Framework (SAFe), and provides support for various aspects of SAFe, including:

  • Requirements Management:Jama Connect provides a centralized repository for managing requirements and product backlogs, helping organizations align work with their product strategy and vision.
  • Traceability: Jama Connect manages requirements with Live Traceability™ across the end-to-end development process — from requirements to design and implementation — helping organizations manage dependencies and ensure that work is aligned with their goals.
  • Collaboration:Jama Connect provides a platform for teams to collaborate on product development, improving communication and reducing risk.
  • Quality Assurance:Jama Connect offers a platform for managing quality assurance operations, including as test case management, test execution, and defect tracking, to assist businesses make sure that their products fulfill consumer needs.
  • Reporting:Jama Connect offers analytics and reporting tools that help businesses assess their progress, spot potential dangers, and make wise decisions.

Jama Connect integrates with other toolslike开云app官方入口下载安装 and Azure DevOps to offer a complete SAFe solution for businesses. Additionally, due to the platform’s adaptability and configuration options, companies can tailor Jama Connect to their organization’s unique needs and operational procedures.

Jama Connect is the #1 Industry-leading software for requirements management andLive Traceability™. This robust, but easy-to-use platform enables collaboration, quality assurance, and reporting for enterprises looking to build a Scaled Agile Framework (SAFe) and can help businesses boost productivity, generate better products more quickly, and optimize their product development processes.

In conclusion, large-scale software development projects can be managed and coordinated using the Scaled Agile Framework (SAFe) approach. It is a thorough framework that offers instructions on how to scale Agile development processes from small, single-team projects to big, multi-team ones. While maintaining the advantages of Agile development, it offers a scalable and adaptable way to plan and manage work, lowering risk and raising predictability.

To learn how Jama Connect can help your organization adopt a Scaled Agile Framework,contact usto speak with one of our experts!

Note: This article was drafted with the aid of AI. Additional content, edits for accuracy, and industry expertise byKarrie SundbomandJosh Turpen.


requirements-driven testing

Jama Connect®vs. IBM®DOORS®: Requirements-Driven Testing: A User Experience Roundtable Chat

Increasing industry challenges and complexities are pushing innovative organizations to consider modernizing the tool(s) they use for requirements management (RM). In this blog series,Jama Connect®vs. IBM®DOORS®: A User Experience Roundtable Chat,we’ll present several information-packed video blogs covering the challenges that teams face in their project management process.

InEpisode 9of our Roundtable Chat series,Mario Maldari–Director of Solutions Architecture at Jama Software®– andSusan Manupelli–Senior Solutions Architect at Jama Software®– discuss requirements validation, verification, and testing in addition to demonstrating test management in Jama Connect.

To watch other episodes in this series, clickHERE.

Watch the full video and find the video transcript below to learn more!

VIDEO TRANSCRIPT:

Mario Maldari:Hello, welcome to the ninth edition of our vlog series. Today, we’re going to be talking about something that’s very important in requirements management, something that I’m particularly passionate about, and that’s requirements validation, verification, and testing. And I’m joined by my friend and colleague once again, Susan Manupelli. Susan and I have worked together for a long time, 15 years plus testing various requirements management tools using various techniques, and various software. I believe the most recent software you were using was IBM’s enterprise test management tool, something we used to call RQM. Looking back on all those years and all those tools you feel as though have been your biggest challenge.

Susan Manupelli:So talking about the ELM suite where we were talking about rational quality manager and also we were using that to test DNG. Really the issue, the biggest challenge is that they were two separate tools. So even though they were part of the same tool set, the UIs were completely different. They were very inconsistent in how you would use them. The review and approval aspect of RQM wasn’t that great. And again, it was completely different from the review and approval that you would get when you were working with DNG. And also because they were from two separate tools, in order to really get the traceability, that would be a challenge. You’d have to do reports that were outside of the individual tool tools. And then one of the biggest things too was the comparison. Things changed in RQM. It was not easy to find out what changed, even if you compared one test case to another.

Mario Maldari:Yeah, I recall some of those challenges. I think for me, the biggest challenge I had was the UI inconsistencies like you mentioned. Obviously, I was in one tool, I’d go to another. It’s completely different experience, completely different nomenclature. And then having to integrate between the tools and just frankly having to go to a separate tool to do the testing was problematic and challenging sometimes. So I think you hit an important topic in terms of having everything in one tool. And I’d like to show you how Jama does that. Okay. So in Jama, the fact that we have testing integrated into the tool allows you to do some pretty neat things. So as you can see here on my desktop, we have this dashboard, and I can define a relationship rule diagram in Jama where I can define that I want specific requirements to have validation points and test cases associated with them.

And so what that gives me is I can create some dashboard views for requirements, lacking test coverage, or I can even look at test case summaries. Right on the dashboard, I can look at test case progress, the priority of my tests. Jama even allows you when you’re testing to log defects. So I can track my defects here. And so for you and I, we always have to provide test case reports and summaries up through management, up through the development team. And so this allows you to have it all in one spot, which is really nice to have. So the testing itself in Jama, you basically enter it on the test plan tab and very similar to the way you and I worked, we have a concept of a test plan where you can define your test intent, the things you’re going to be testing, your approach, your schedule on your team, your entry criteria, your exit criteria.

从那里,你指出的那样,您可以发送this for a review and you can get an official sign-off from your development team or whomever you need to sign off on your test plan. And then once that’s in place, you can go to your test cases and you can start to group your tests according to functionality or whatever makes sense for your grouping and your organization of your suites of tests. And once they’re grouped, you can come to the test runs and this is where you actually will be doing your execution of your test. So I can click on one of these here and can start an execution and I can start to go through each step and pass or fail as I go through. And the nice thing about Jama, as I mentioned, is that you can actually go ahead and log a defect in real time and I can go ahead and log this defect.

And now when I’m saving this defect, it’s associated with this test execution run, which is associated with my test case, which is associated with multiple levels of requirements upstream. So now if I look at a traceability view, I will see my high level requirements traced all the way down to the defects. When I have logged a defect, I can actually go in and I can take a look at this test run and I can see the defects. And if I have something like an integration to another product like Jira for example, maybe my development team and is working in Jira and they love Jira, it automatically populates the defect in the defect tool like Jira. So a developer can come in here, they can make some changes, they can put in some comments, they can change the priority, the status, and all of that gets reflected back in Jama.

RELATED:Traceability Score™ – An Empirical Way to Reduce the Risk of Late Requirements

Mario Maldari:So really nice integration if you’re using something like Jira. From my perspective too, what would’ve been nice in my past test background is to have this concept of suspect trigger. And so if I look at the relationships for this particular requirement and I see that downstream there’s a validation of a test case, which is validated by length type, I can see that it’s flagged as suspect. So that means that something upstream has changed and my downstream test case is now suspect. And what does that mean? Maybe I need to change it, maybe I don’t. How do I know? I can come to the versions and I can say, “Well, the last time I tested this requirement was in our release candidate one, and what’s different now?” So I can compare our version three to version seven, run our compare tool, and I can see exactly what changed.

So as a tester, this is great to me, it’s not enough to know that something’s changed. I can actually see exactly what changed and maybe it’s just a spelling update and I don’t need to really change it. Or maybe it’s something more substantial like you see here. And at this point I can come in and I can make my change to my test and I can go ahead and I can clear the suspect flag.

So really nice level of granular control. What’s also good with the Jama’s we have these out of the box, and you’ll like this, Sue, out-of-the-box canned reports that have summaries of your tests, how many blocked, how many failed, how many passed executions. So these are canned reports that come with Jama. If you needed any customized reporting for your specific needs of the organization, we have that available as well. So really nice back to your point about having everything in one tool, this is it, and this is the benefit. Now, I know you’ve been at Jama for just about six months now. I’d love to hear your impression of the test management built-in, what your thoughts are there?

RELATED:Telesat Evolves Engineering Requirements Management & Product Development

Susan Manupelli:Oh, sure. Yeah, I do. I definitely love how everything’s in one tool and the ease with which you can just trace, actually verify the testing of your requirements. You can just go from requirements straight down to multiple levels of decomposition to your test cases. So you can see, answer the question, did your requirement are your requirements passing, which is great. And also the ability to display related queries right on the dashboard. I think that’s a huge plus the consistency of the UI between what you do for requirements, creating a test case isn’t any different than creating any other requirements.
So it’s a very familiar UI for both operations, which I think is important. The review and approval piece is really a nice strong point for Jama, and to be able to apply that to reviews for test cases is really great. And I just think it’s a really streamlined UI. It really has everything you need and nothing that you don’t. So I just think it’s a great tool. And then there’s one other aspect that I really like is the impact analysis. You mentioned being able to trace when something’s changed after the fact. It’s also to be able to say, “Hey, we’re looking at making a change here.” There’s one button in Jama, you click that impact analysis and it tells you all of your test cases that you might need to revisit if you make that change.

Mario Maldari:I call that the proactive method.

Susan Manupelli:Yes.

Mario Maldari:Yeah, the impact analysis is extremely important. And if you were a developer in an organization and you changed a requirement or you were about to change a requirement and you knew you had 30 tests that are associated with that, you could run the impact analysis. See all of those, and you could proactively warn your test team, “Hey guys, I’m about to make this change. Here it is. I’ll explain it to you. We can have a separate review and approval.”

So it really contains all of that and controls all of that for you. I’ve often said to people, it’s one thing to have your requirements in a tool, and that’s the first step. Define your requirements, have your traceability. But if you’re not doing your testing and validating those requirements, then how do you know that you built the right thing, right? So extremely important aspect testing to requirements in the supply. So any requirements gathering process so I’m glad we could talk about it today. Sue, glad I could have you to talk to about it. And I’d like to thank everyone for their time and thanks for participating in the vlog series and we’ll see you on the next one.

Is your data working for you? A consistent and scalable data model is instrumental for achieving Live Traceability™ and making data readily available across the development lifecycle.

Download ourJama Software® Data Model Diagnosticto learn more!

Thank you for watching our Episode 9, Jama Connect vs. IBM DOORS: Requirements Driven Testing. To watch other episodes in this series, clickHERE.

To learn more about available features in Jama Connect, visit:Empower Your Team and Improve Your Requirements Management Process