static documents Archives

Tag Archive for: static documents

Product development teams face many challenges in today’s fast-moving and increasingly regulated environment. Potential missteps, however, can create an expensive ripple effect throughout the product development cycle, with the potential for missed deadlines, compliance issues and more.

Real-time collaboration and the need for a single source of truth are critical to product development teams. Outdated tools often don’t deliver on these needs, and a misalignment between what a team needs and what a tool provides can hinder success. Requirements management tools that keep pace with your team’s evolving needs can help mitigate potential risks, improve efficiency and achieve faster results.

If you’re currently using IBM DOORS, understanding the difference between the existing solution and more modern options can help you to determine the best next steps for your organization.

Requirements Management and IBM DOORS

Many organizations adopted IBM DOORS because they needed a requirements management tool for their teams and, at the time, it seemed like the best option. But much has changed since the creation of IBM DOORS, and the tool has quickly become outdated. Today’s teams need the ability to not only collaborate in real time but also to do so remotely. They also need to:

Follow a consistent and common requirements practice.

Create a single source of truth for requirements, ensuring that everyone on the team is working from the same information.
Have easy integration so that requirements management is integrated into both core workflows and business to improve productivity.
Be able to track requirements to develop, test and release new products.

Development teams and critical stakeholders expect the tools they use to be as intuitive as the technology in other areas of their lives. Users of IBM DOORS, however, struggle with usability issues, leading many to not use the solution and opt instead to use outside programs, such as Word or Excel. This creates challenges within workflows, productivity and efficiency, and it introduces potential risks, eliminating the ability to have a single source of truth. But how did IBM DOORS become outdated, and what does it lack?

The Advantages and Disadvantages of IBM DOORS

Organizations are often tempted to maintain an outdated solution, even if it’s underperforming. Why? Because fear and worry exist when it comes to switching to a new solution, users often stay with the existing solution or upgrade to the next offering within the same organization (such as IBM DOORS Next).

The advantage of staying with IBM DOORS is that you don’t need to invest in a new solution and undergo the adoption process that comes with transition. But delaying the switch to a new RM tool only delays the inevitable, because IBM DOORS will eventually go out of support, which will create many challenges, including potential security issues.

A few common misconceptions around the advantages of IBM DOORS include:

Upgrading to IBM DOORS Next is a less-expensive option. IBM DOORS Next is not IBM DOORS, it’s an entirely new tool with a new approach to requirements. In fact, the only thing the two have in common is in the name. Migrating to IBM DOORS Next might seem like the less-expensive option. However, the work that goes into upgrading to IBM DOORS Next and transitioning to an entirely new RM tool is the same. Moreover, selecting a different solution may help you improve efficiency and achieve ROI faster.
Customizations will carry over to IBM DOORS Next. Organizations invested money and resources in IBM DOORS customizations (DXL), and you might believe that you can take these innovations with you when you move on to IBM DOORS Next. However, this isn’t the case, and selecting a different solution could allow for you to use fewer customizations.

Business disruption is more significant with a different RM solution. Eventually, you’ll need to move away from IBM DOORS after the support is discontinued. The right RM solution will help teams more effectively hit deadlines, collaborate with greater ease and improve business outcomes, offsetting any upfront business transition.
The user experience will suffer. Many people refuse to use IBM DOORS due to a challenging user experience; switching to a new RM tool may accelerate concept, design and validation processes, leading to faster times to market.

If you’re considering making a switch, comparing various options can help determine which RM tool is best aligned with your needs. An innovative tool has the potential to reduce risk for project rework, expensive errors and compliance risks.

What is the best alternative to IBM DOORS?

If you want to move away from IBM DOORS, you aren’t constrained by a specific path to migration. So, what is the best alternative to IBM DOORS?

The answer is found in examining both what your team needs most right now and what they may need in the future.

Collaboration is a critical part of the workflow, especially with the increasing number of people working remotely. Organizations need a tool that supports digital transformation, has greater efficiency and is user-friendly enough that people will use it.

Jama Connect is a modern alternative to traditional legacy platforms, such as IBM DOORS, and was named the overall leader (No. 1) in requirements management software on G2, outranking IBM DOORS Next for implementation, time adoption, ROI and market presence. The tool offers users a reliable solution with:

Simplicity. Jama Connect provides an intuitive and modern user experience. Requirements management software supports multiple development methodologies and engineering disciplines to drive cross-team collaboration and alignment.

Flexibility. Customization is a critical factor to product development teams, which ensures that they get the functionality they need most. Jama Connect provides customization, security development and a licensing model that delivers a lower total cost to ownership.

Open. A poor experience is created when an RM tool doesn’t integrate with other tools that your team wants to use. Jama Connect allows for seamless integration with the most commonly used tools across the product development life cycle. You’ll have access to a powerful network of options to get the right technology stack aligned to your unique business needs.

Simplicity, flexibility and the ability to easily integrate with other tools give your team the resources they need to create greater success in all of their projects. As you consider adopting RM tools such as Jama Connect, it helps to have a quick comparison to help guide your decision.

RELATED: Q&A with a Former IBM® DOORS® Evangelist

IBM DOORS vs. Jama Connect — A quick comparison

Adopting a new RM tool involves asking many questions, including the following: What is the implementation process? What are the costs and ROI? How easy is the tool to use? Consider the following as you weigh the advantages and disadvantages of IBM DOORS Next and Jama Connect.

Adoption. Organizations worry that adopting a new solution will take too much time and money, so they often gravitate to a solution such as IBM DOORS Next, primarily because they assume adoption is easier. However, Jama Connect is actually 2.7x faster to adopt than IBM DOORS Next. Additionally, Jama Connect rated 80% in ease of administration, compared with IBM DOORS Next, which rated 71%.

Return on investment. How fast will your investment pay off? This is a critical question for any new solution, and it’s important to note that ROI is achieved 45% faster with Jama Connect compared with IBM DOORS Next.

Usability. Usability is a key reason many people refuse to use IBM DOORS and instead use email communication, Word, Excel or other outside applications. Users expect their RM experience to be as intuitive as applications in their social environment. Jama Connect rated 85% in “ease of doing business,” compared with IBM DOORS Next, which rated 74%.

Supports remote working. The remote working trend is only expected to grow in the future. IBM DOORS lacks cloud capabilities, creating challenges with working anywhere, anytime. IBM Jama Connect creates a single repository so it’s easy for remote teams to gather, review and execute on requirements. Structured reviews and collaboration enable teams to elicit feedback, review product features in real-time with stakeholders, and track critical decisions across teams and locations.

Moving forward with greater confidence

Products, systems and software development are only getting more complex; so not modernizing your requirements management tool creates potential risks, such as negative outcomes in your product development process.

As your team increasingly requires the ability to adopt, innovate and grow, continuing to use IBM DOORS will only become more difficult and potentially introduce risk into your product development process.

Transitioning to a new requirements management tool provides your team with the resources required to innovate, meet deadlines and succeed. You can more effectively define, manage and validate complex system requirements, all while eliminating the risk and inefficiencies associated with outside documents and legacy systems.

magniX chooses Jama Connect for its ease of use, quick deployment, and to help modernize their requirements management program and demonstrate compliance with standards.

Headquartered in Everett, Washington – located just outside of Seattle – magniX is the leading developer of propulsion systems for electric aircraft, including motors, inverters, and motor controllers.

magniX is working to bring affordable, emission-free, and quieter flights to communities around the world.

More about magniX:

Founded in 2009
Expertise: Leading developer of propulsion systems for electric
aircraft, including motors, inverters, and motor controllers
Recent Awards for magniX:
- 2020 Fast Company Most Innovative Company in Energy
- Finalist 2020 GeekWire Innovation of the Year award
- Frost and Sullivan Technology Innovation Leadership Award

With big plans on the horizon, magniX set out to find a modern requirements management solution that could help them make their ideas a reality.

Initially, the team was using Microsoft Excel and Word to manage their requirements, but they quickly realized it was only a temporary solution. The limitations and risks of using static requirements in this manual process were becoming apparent.

As they began their search for a requirements management solution, they knew the following things were most important:

- Moving to a modern, cloud-based RM tool
- Creating a centralized requirements repository
- Demonstrating compliance with aviation standards

While the evaluation process was short and led to the selection of Jama Connect®, the magniX team seriously evaluated multiple systems.

Jama Connect stood out for the following reasons:

Jama Connect was a more modern, easy-to-use solution with the powerful features they required
Jama Connect allowed for the magniX team to easily customize the solution to meet their needs, without requiring complex custom scripts to be written
The interface in Jama Connect was intuitive

“The ability to easily customize Jama Connect to fit our needs without custom scripts is a major advantage over other solutions,” said Carlos Souza, Head of Energy Storage Systems at magniX. “Jama Connect just allows us to achieve more with less work.”

Ease of use and quick deployment

In addition to ease of use and quick deployment, ultimately, the magniX team selected Jama Connect because the solution:

Allows for end-to-end traceability that gives the magniX team the ability to control requirements from the product level down to implementation in one single database
Is powerful, intuitive, and easy-to-use requiring very little training to see wide adoption and ROI
Enables configuration control throughout all stages of development

“One of the main reasons we selected Jama Connect is the ability to provide configuration control for all the requirements and maintain them in one database. It allows everyone in the company to have visibility into the requirements and their status,” said Souza.

Jama Connect helps to form a digital thread through development, test, and risk activities — enabling the magniX team to have end-to-end compliance, risk mitigation, and overall process improvement. Moving from static requirements (in disparate teams, activities, and tools) to Living Requirements™ management was the key to them achieving real-time, cross-team collaboration and coordination. And, because of its easy, intuitive, modern user interface, broad adoption is made simple.

Jama Connect: the Leading Platform for Requirements

Matt Graham: Thanks everybody for joining. So today, before we get into the agenda just to introduce the three products that there are three subject matter experts about. First of all, something near and dear to my heart, the Cadence vManager, verification management platform which is a scalable, reliable and very feature rich verification planning and management solution from Cadence. That sits on top of a number of our verification and provides a sort of roll up capability. And we’ll describe it in a little more detail in a couple of slides. On the OpsHub opposite side, we’ll be looking at the OpsHub integration manager that enables enterprises to integrate their best of breed tools together that are best suited for the various teams and their various roles and connect those two together for integration and collaboration. And then Jama Connect, which is the leading platform for requirements, risk and test management to help provide that sort of end-to-end compliance solution.

Our agenda today. First we’ll look at some of the challenges of the semiconductor and hardware development ecosystem. This is obviously a very fast paced, highly competitive type of environment and there’s a lot of specific challenges that the integration of the tools I just mentioned can help address and solve. We’ll look at how engineers in this space can scale effectively and efficiently utilizing some of these, the tools to address some of the ongoing transformations in that space. And then specific to semiconductor domain, bridging the gap in what has historically been a very siloed development process. And bringing together for efficiency, quality and reliability all of the various tools that I mentioned and giving it a really nice integrated development and verification environment. We’ll then have a specific use case and demo showing how the three tools work in concert and then look at some key takeaways. And as Marie mentioned, some Q and A.

Standards for Requirements such as ISO 26262

Specifically to the semiconductor and hardware ecosystem, there are a developing set of challenges. And of course they’ve always been challenges in this area. First pass design success is critical for hardware development. Just because the tooling costs are so great. We don’t want to have to respurn hardware. It’s not like just releasing more software. It is it requires expense. But that has been the way of hardware development for some time. In the last several years we’ve seen a need creeping into that environment for even stricter compliance, particularly around mission critical domain such as aero and defense, automotive especially as self-driving and autonomous vehicles come in. And adherence to standards like ISO 26262 presents another layer of requirements and need for management and collaboration on top of an already strict set of sort of design parameters.

As I mentioned, this development environment tends to be very siloed in its nature because it is so specialist. You have specialist designers, specialists verification engineers to test the designs, specialists post silicon, specialists layout engineers and so on and so forth. And all of those silos, well somewhat required of the specialty of each of those tasks tends to hinder collaboration, compromise quality and just impact efficiency and velocity overall. In an area where efficiency and quality is critical. We can’t have bugs in semiconductors going to automotive and we need to be able to turn those new cell phones, those new mobile devices as quickly as possible. So turnaround time is just getting compressed and the requirement for quality is increasing at the same time.

RELATED: A Guide to Understanding ISO Standards

All of that sort of siloed nature of the specialties as well as the need for velocity and quality really ends up in poor traceability of results in terms of compliance and quality issues creeping in. Especially when it comes to doing things like audits for ISO and other similar standards that are becoming the requirement across again aero and defense type applications, automotive type applications and even down into the sort of consumer device applications. And really traceability is a watch word now in the ecosystem of hardware and semiconductor development.

So how does the offering from Cadence, vManager fit into and help provide a solution to those challenges that I just mentioned? Well, for a number of years now, in fact, vManager has been around for about 15 years and in that entire time it’s had the key capability of the verification plan. And the verification plan really exists to provide traceability between what is being executed during the testing or verification of your semiconductor or hardware design. And what were the goals of that or the requirements of that testing or verification project. Things like testing interfaces, both internal and external to the semiconductor, testing compliance with standards like ethernet and USB, such as that, things like that. As well as the internal requirements of the device, it must route packets this fast. It must answer phone calls in this manner or whatever it might be.

And the verification plan in vManager really allows the user to enter those requirements and then connect them to the real results that are occurring. We ran these tests, these tests were associated with a given requirement. Those tests passed therefore the requirement is satisfied. And so the V plan becomes a very natural place. And in fact the appropriate place to connect the rest of the ecosystem via OpsHub, two tool requirements coming from Jama Connect so that we can have traceability across the software development, the hardware development, whatever. The mechanical development et cetera ecosystems. And the vManager and the verification plan is really where that hardware verification, that hardware and semiconductor development information enters that ecosystem through the conduit of the verification plan. So let’s look a little bit more on, well what exactly is in that verification plan that vManager provides.

Enabling Digital Transformation: Static Documents Cause Challenges

And the V plan is really what we call, what we refer to in our vManager sort of pitch if you will as an executable verification specification or an executable verification contract. And what that means is that there’s data incoming to that during the creation, the authoring of that verification plan. Not only through connectivity to tools like Jama but also from say static documents like standards specifications, ethernet that I mentioned before, USB those are standard protocols that have very lengthy standards documents and needs to be a way to import, kind of gather the data from that and put it in the verification plan. Another input to the verification plan is other verification plans. So if you think about a system on a chip that is not a single piece of intellectual property, it’s built up of many, many different pieces, a USB piece, a central processing piece, a memory management piece and so on.

And each of those pieces can have their own verification plans for the verification at that sort of lower block level as well as then can sort of conglomerating or aggregating those verification plans into a single sort of system on a chip verification plan. And the vManager, V plan allows that through sort of parameterization and instantiation and really flexible set of sort of reuse capabilities for verification lands. And then of course just engineers authoring their verification plan. Literally writing, typing in here’s a specific requirement et cetera. And then we have the component of mapping those requirements to items that exist in the actual testing environment. Things like we have a test, did it pass or fail? What requirement is that test related to? So there’s mapping the test to a particular requirement and then did that test pass or fail. Those of you familiar with hardware verification know that tests passing and failing is not the only statistic or metric that we track.

There’s other metrics and statistics such as code coverage, functional coverage, assertion coverage, software coverage, all tracking what scenarios and what stimulus were driven to the specific device under test. And what was the reaction of the device under test? And then what percentage of the device has been exercised during that test? It is all basically statistics gathering from the testing effort. All that data can be mapped into the verification plan, directed to the specific requirement or multiple requirements that it may satisfy. And of course, this gives us the ability to not only specify a requirement, but then capture whether that requirement was met. Was it satisfied? And this is the place where I’ll hand over to Jeremy now to talk about what those requirements in those higher level requirements or system level requirements in the general world and how they’re going to connect into this hardware verification, hardware development world.