Jama Connect Platform Archives

In this blog, we recap our “The Inside Story: Data-Model Diagnostic for IBM® DOORS®” webinar.

Organizations make investments in software tools to improve their product development process, but they often forget to invest in their data. A consistent data model is the best way to maximize the benefits of software tooling, but this can only be achieved by spending time on analysis.

Jama Software is well documented on the benefits of a common engineering data-model and the use of diagnostics to understand the true nature of your engineering data.

In this session, we will discuss the production of a return on investment (ROI) for cleaning your IBM® DOORS® data.

You’ll learn more about:

Why a common engineering data-model is important
The aims of a diagnostic tool
The breakdown of the IBM DOORS data-model diagnostic in terms of the measures that can be taken
Calculating the financial impact of cleaning your engineering data

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

The Inside Story: Data-Model Diagnostic for IBM® DOORS®

Richard Watson: Thanks very much. Yeah, I’m excited to be here today. As was said, previously, before Jama Software, I’ve been working with DOORS for a huge amount of time as the product manager for a long time, and I’ve moved to Jama Software. One of the main activities I’ve been working with in Jama is “How do we transform DOOR’s data into a new requirements tool of Jama Connect?” And this presentation is all about trying to understand the diagnostics or understand some diagnostics from your data to be able to understand data shape and size so that we can help see the business case and also help understand how we would transform it to improve the situation.

Let’s start at a very high level. I’ve presented a slide like this repeatedly for all of those 30 whatever years. We know that the earlier in the life cycle that we find a defect or a problem, the cheaper it is to resolve, but in Jama Software, we firmly believe that this is related to traceability. If we have traceability between the artifacts in our engineering process, then we have the ability of finding the information that has an error. For example, if you’ve been working on your needs analysis, and then you start to decompose your requirements, at that stage, if there is a traceability between the requirements definition and the needs analysis, you’ll start to see the errors in the needs at that stage, rather than having to wait all the way around to validation, and then finding out that mistake. And if you wait until the end, we all know that it’s been proven that it’s much more expensive, and there are many sources of this information, but you’ll see a link on the slides to INCOSE.

If we look at the reality of this V model, though, even with tools in place and some integrations in place, we find that there are many different types of silos of information in organizations, and this integration of framework between those different silos is just not established. As you’re documenting the requirements or the system design or the implementation, because you don’t have a viable connection back to the previous assets, you’re not encouraged to find the errors in those previous assets. And so if you work in different silos in this way, you don’t fix those errors. And by the time then you go through to verification, validation, and up that side of the V, then you’ll perhaps start uncovering those problems and it’ll be expensive. Even worse, you won’t find those problems; you’ll go into deployment, and you’ll find it in production, and that’s terribly expensive.

Related: Requirements Traceability – Does My Data Model Matter?

Richard Watson: Here in Jama Software, we believe that our live traceability model has resolved this. Jama Software provides an environment that keeps all of those different assets connected. Requirements actually are the common denominator. Everybody works against some form of specification. Maybe the name changes, maybe it’s a work instruction or a requirement or a project need, or a user expectation, but everybody’s working to something, everybody’s conforming to something. And here in Jama Software, we provide an environment to create your engineering data in something called a model-based framework. You have a model-based systems engineering framework for all of your engineering data, and we keep that data connected directly from the beginning. So rather than waiting to comply or give some sort of statement to say everything’s been covered and creating traceability, later on, we encourage this traceability to be established right from the very beginning.

And we do that in a way that does not force people out of their preferred environments. And so they work in their existing environments establishing traceability, but then we can see the end to traceability in a commonplace. And we can make sure that all the engineering assets are consistent. Jama Connect offers this environment. It offers a way of defining a model-based systems engineering data model over your engineering data and then facilitating which applications should be contributing to those bits of information. Be it Jama Connect for requirements or test and risk, or some other system for defect tracking and other assets in that way.

Great, we’ve got this understanding that information needs to be connected together from the get-go and not at some later stage. And so that would give you a perfect environment, right? But there’s a big but. This data model that we’ve been describing, we can describe it in something like a language. Your engineering data model is the language of your engineers. It’s the way that they create your systems, though the way they specify it, et cetera. But you want to be able to facilitate a common language. If you’ve got separate teams using a different way to engineer your systems, then they can’t communicate between each other effectively. They can’t move between teams effectively. And the cost of integration across that life cycle becomes more and more expensive.

Related: Considering DOORS® for requirements management? There is a more modern solution.

Richard Watson: And so this language needs to become common, but it’s quite difficult because in traditional environments, so if we move the conversation to talk about some of the IBM tooling, so IBM DOORS or IBM DOORS Next, for example, we find that there aren’t many of these silos. IBM DOORS, for example, specifies requirements in what it calls DOORS modules. Each DOORS module stands on its own. Unless your organization have taken steps to try and rigorously make modules consistent with each other, each of those modules would end up being a silo of information. Multiple different sets of user requirements, for example, could be easily inconsistent with each other.

DOORS Next is the same. DOORS Next uses a component model, and each component stands on its own as a silo, and keeping the components consistent with each other is also difficult. Although we’ve got this wish to have a common language across our organization, it’s very easy and quite convenient to end up with lots of silos of organizations, each doing their own particular thing and not being able to communicate. Then that big question. The big question is if you have these silos, how do you move from having a silo-based organization to having a common language or a common engineering data model? And that’s when we should start talking about data-model diagnostics…

To watch the full webinar, visit: The Inside Story: Data-Model Diagnostics for IBM® DOORS®

Why Investing in Requirements Management Software Makes Business Sense During an Economic Downturn

Regardless of the state of the economy, organizations building complex products, systems, and software can always benefit from improved efficiency across the end-to-end development process. Making strategic changes that optimize processes and team productivity will undoubtedly save your organization significant time and money.

And, while it may seem counter-intuitive to invest in new technology during an economic downturn (dare we say the word recession), a modern requirements management tool like Jama Connect^®, can provide a dramatic ROI in short order — making it a smart-sense move to invest in new product development software right now.

During economic uncertainty, spending capital on the right tools can improve product quality and increase productivity, well-positioning your organization to save time and money over the long term. But regardless of what happens with the economy, it is never going to be wasted effort to optimize your product development processes or begin to think about how to weather the impact of an impending economic storm.

RELATED: The Jama Software Guide to Requirements Traceability^®

Invest in Requirements Management Software Now to Save In Both the Short & Long Term

Many of our clients come to Jama Software to help optimize their product development process after experiencing some of the following core frustrations:

Using cumbersome legacy requirements management solutions that have non-intuitive challenging UI/UX
Engineers spending valuable hours of tedious manual documentation across disparate documents and tools
Engineers wasting time on in-efficient workflows that can be streamlined to save upwards of 80%
Insufficient, ineffective cross-team collaboration across various stages of the systems development process starting from requirements, design, development to testing and validation
Inefficient and cumbersome review cycles
Difficulty in easily producing the necessary documentation to prove compliance
Siloed tools and processes that misalign teams and workflows, and leave visibility gaps
Lack of Live Traceability™ which results in finding errors late in the development process which can cost upwards of 100x or more to resolve than if they had been found earlier in the development process
And the list goes on and on…

Think about the corresponding monetary burden these outdated solutions and misaligned processes place on the organization’s shoulders.

Making an investment in a modern requirements management platform isn’t simply about the time and money that will be saved or improving productivity and efficiency for just a few months — it’s about the savings and reduced re-work that will be realized from the moment the application launches and for years beyond. Depending on the organization’s goals, they either save costs with the gained efficiencies or they use it to be competitive, win new contracts, and bring products to market faster and more cost effectively. You may be thinking that now is the time to pause on spending, not invest. To the contrary, we’d like to share how investing in a modern requirements management solution now is the right decision to help your organization protect itself from an economic downturn and increase your ROI.

RELATED: Accelerate, Measure, and Improve the Systems Development Process with Live Traceability in Jama Connect

For Startups: Build Your House on Bricks, Not Sticks

For startups, investing in a modern requirements management solution, like Jama Connect, is a smart idea irrespective of the state of the economy.

While long established large organizations may be able to withstand a period of lowered sales and slow development, startups may not have that option. A startup’s ability to get to market fast – and first – often is a great indicator of success, and on the flip side, failure.

Doing things right the first time is crucial.

While startups might be hesitant to invest in software initially, a great number are investing in Jama Connect in order to reduce rework, speed development, meeting regulatory compliance, and get to the market before their competitors.

And it’s paying off.

For medical device startup, Proprio, VP of Software Engineering, Rama Pailoor knew it was imperative to establish a requirements-driven development process from the very beginning. Pailoor recognized that their existing approach of using only a Quality Management System (QMS) was not capable of supporting the level of complexity needed to develop their product. Like many document and spreadsheet-based processes, the Quality Management System (QMS) Proprio had in place technically supported requirements management at face value, but when it came to complex engineering efforts, the system came up short.

“Establishing a requirements-driven development process helps to formalize the user needs, getting all the stakeholders to come to a common forum, to express the requirements from their perspective, and avoid confusion. The right requirements management solution can facilitate all of that.”
Rama Pailoor, Vice President of Software Engineering – Proprio

For medium to large organizations: Strengthen your foundation by investing in modern tools and digital transformation

While big enterprises have large teams spread across various geographies and different divisions working on multiple projects, there is a strong need to optimize processes and reduce inefficiencies to reduce costs — especially during challenging economic times. Putting resources towards digital transformation and modern software tools (which result in more ROI) will also reduce overall product development costs over the long term. Through these investments, companies can strengthen their foundation to remain competitive and be better able to weather external market forces.

It is also worth re-visiting how enterprises can improve the engineering efficiency of product development by investing in requirements management and traceability tools. Optimizing the systems engineering process by bringing in traceability across your development stages can immediately create a positive impact on cycle times, and faster execution of testing and validation.

Requirements management software, like Jama Connect, can help development teams improve product quality and accelerate time to market. The platform’s robust features coupled with an easy-to-adopt interface aligns people, processes and tooling in one place to provide visibility and actionable insights into the end-to-end product, systems, and software development process.

Tag Archive for: Jama Connect Platform