Tag Archive for: Requirements & Requirements Management
Jama Connect® is Awarded the TrustRadius Triple Crown for Requirements Management Software!
Jama Connect® has gained recognition as an outstanding solution on TrustRadius, solidifying its position as a leading platform for requirements, risk, and test management.
With its intuitive interface, robust features, and exceptional customer support, Jama Connect has received the following prestigious awards in 2023: Best Of, Feature Set, Pricing, and Relationship.
Visit the full report to see why customers love using Jama Connect for product, systems, and software development.
This recognition underscores Jama Software’s unwavering commitment to delivering a reliable and efficient solution that empowers teams to drive innovation and achieve exceptional results.
As the leading provider of requirements management software, Jama Software is proud to receive recognition for our commitment to enabling multidisciplinary engineering organizations developing products, systems, and software to maximize their success. We value the feedback from our clients who have used Jama Connect and are committed to providing them with the best support, resources, and expertise to help them succeed.
“Jama Connect is a solid framework for systems engineering that can integrate many design processes into a single tool. At a fundamental level, it is a great tool for handling requirements management and traceability but offers a variety of other features such as risk management and verification and validation. For someone who works in the medical device industry, the tool also complies with CFR requirements for electronic approvals and can be validated for such use.”
-From review collected and hosted on TrustRadius – User in Engineering, Medical Devices Company
“I’m VERY likely to recommend Jama to a colleague because they’d struggle to get anything done without using it! That’s the tool we’re using for Req Management now, so I recommend to my colleagues that they get amongst it!”
-From review collected and hosted on TrustRadius – Ian Webb, Systems Engineering Technical Writer – Enphase EnergyElectrical & Electronic Manufacturing
From all of us at Jama Software® to all of you, thank you!
https://www.jamasoftware.com/media/2023/11/2023-11-09_trust-radius-1-1.jpg512986Jama Software/media/jama-logo-primary.svgJama Software2023-11-09 06:30:032024-01-17 22:45:16Jama Connect® is Awarded the TrustRadius Triple Crown for Requirements Management Software!
In this blog, we’ll recap our whitepaper, “Cybersecurity in the Air: Addressing Modern Threats with DO-326A” Click HERE to read the entire paper.
Cybersecurity in the Air: Addressing Modern Threats with DO-326A
Introduction
Not long ago, getting on an airplane meant being largely out of touch with everyone on the ground for the duration of one’s flight. Of course, there were in-flight telephones for those who could afford them, and pilots could connect with personnel on the ground in case of emergency, but the rank-and-file passenger had limited options for connecting with the world outside the aircraft.
The 21st century has changed flying from a largely isolated endeavor that exists in a closed loop to one that integrates with ground systems through the miracle of the Internet. For travelers who want to enjoy their own personal entertainment options, conduct business, or take advantage of downtime to do online shopping, accessing the Internet during a flight is a tremendous boon. For air freight carriers and their customers, Internet connectivity improves visibility and streamlines supply chains with better real-time information.
Of course, the advantages of connectivity come with disadvantages as well. The more airborne systems are interconnected with the broader Internet, the more vulnerable systems are to hacking. In 2015, a researcher was kicked off a United Airlines flight after tweeting about security vulnerabilities; the researcher claimed to have accessed in-flight networks multiple times between 2011 and 2014, including one time when he allegedly commandeered the plane. In 2016, the US Department of Homeland Security hacked the system of a Boeing 757 using “typical stuff that could get through security.” And in 2022, Boeing announced a software update to repair a vulnerability that could allow hackers to modify data and cause pilots to miscalculate landing and take-off speeds.
Aviation cybersecurity has become a critical issue across the globe. Not only do millions of passengers depend on airlines to get them safely from point A to point B every day, but manufacturers, shipping services, and militaries rely on aircraft systems to support supply chains and execute missions. Cyberattacks have skyrocketed since the onset of the COVID-19 pandemic; a 2022 report found a 140% increase in cyberattacks against industrial operations — including four attacks that caused flight delays for tens of thousands of passengers.
Clearly, aviation systems can be vulnerable to malicious actors. For developers and manufacturers in the aviation industry, DO-326A provides compliance guidelines to address the vulnerabilities of avionics systems.
Known as the “Airworthiness Security Process Specification,” DO-326A (and its European counterpart, ED-202) is the aviation cybersecurity standard developed jointly by the Radio Technical Commission for Aeronautics (RTCA) and the European Organisation for Civil Aviation Equipment.
The original edition, DO-326, was issued in 2010; its revised version, DO-326A, was issued in 2014. The standard became mandatory in 2019.
The DO-326A/ED-202A set focuses primarily on how to prevent malware that can infect avionics systems during both development and flight operations. A cyberattack on these critical systems can impact how the aircraft works and potentially endanger operators and passengers. DO-326A/ED- 202A describes the Airworthiness Security Process that one should follow.
What is Airworthiness/Airworthiness Security Process?
“Airworthiness security” involves protecting an aircraft from intentional unauthorized electronic interaction, including malware, ransomware, and other cyber threats.
The Airworthiness Security Process (AWSP) is intended to establish that aircraft will remain safely operable if it is subjected to unauthorized interaction.
DO-326A outlines the Airworthiness Security Process in seven steps:
1. Plan for Security Aspects of Certification (Aircraft Level Planning/System Level Planning)
2. Security Scope Definition (Threat Assessment Process)
3. Security Risk Assessment (Threat Assessment Process)
4. Decision Gate (Threat Assessment Process)
5. Security Development (Definition of Security Measures and Requirements)
6. Security Effectiveness Assurance (Verification and Validation of Security Measures and Requirements)
7. Communication of Evidence (PSecAC Summary Reporting)
https://www.jamasoftware.com/media/2023/11/2023-11-07_do-326a.jpg512986Jama Software/media/jama-logo-primary.svgJama Software2023-11-07 03:00:222024-01-17 22:54:09Cybersecurity in the Air: Addressing Modern Threats with DO-326A
In this video, we’ll discuss the reuse & sync capabilities in Jama Connect.
Jama Connect® Features in Five: Reuse & Sync
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 the powerful features in Jama Connect®… in about five minutes.
In this Features in Five video, Zeb Geary – Principal Professional Services Consultant at Jama Software® – will go over the reuse & sync capabilities for requirements management in Jama Connect.
VIDEO TRANSCRIPT
Zeb Geary: Welcome to this segment of Features in Five. I’m Zeb Geary, a Principal Consultant at Jama Software. In this video, I’ll explain how your team can reduce time to market and improve quality by reusing and synchronizing requirements and other content in Jama Connect.
Teams often struggle to build on existing work when requirements and tests are spread across documents and systems. Lacking a live trace, they must manually identify and copy related content, increasing the risk of rework and gaps. Additionally, teams tend to lack visibility across efforts, causing necessary changes to not propagate across reuse content, potentially impacting quality and disconnected product design efforts.
Jama Connect simplifies and enhances the process of reusing requirements and verifications by allowing you to copy selected content with its containers and its traced items. Synchronization ensures visibility and enables key use cases such as parallel product definition, common content libraries, and product variance. Let’s look at reuse and synchronization in Jama Connect.
Geary: Here in Jama Connect, I’m looking at a project that we would consider a library or potentially a platform of 150% of our requirements. For this example, I’ve started building out the requirements and verifications for a new Jama Connect project, but I’ll be incorporating some standard or common requirements from this project. And through reuse, I’ll save time and ensure consistency with the platform.
I want to bring these common display requirements into my project from the platform. I see that these requirements have related verifications, and I want to bring these into my project as well. I’ll go ahead and select to reuse this folder. The reuse window shows me what I’ve selected for reuse and provides me with important options that reveal the significance of this capability. The first option determines if I will enable synchronization. If enabled, Jama Connect will establish a connection between the result of my reuse and its source so that I can monitor them for differences. I have options to include or exclude tags, attachments, and links, and to form a relationship to my source item from the resulting copy.
The final section of options determines how I will handle related content outside of my selection. Recall that the selective requirements have downstream verifications that I want to make sure I bring into my project. I will select the option to include related content and to mirror the relationships in my project. This saves me a lot of time since I will not have to recreate these relationships in the new project and removes the risk of missing verifications related to my selected requirements.
Finally, I indicate where I want to reuse the content to. I’ll select my project and I can have Jama Connect copy the project hierarchy as well into my target project, or I can select an existing location in my project. I selected my location and I will reuse with Sync.
Geary: In my project, the common display requirements have been reused with their related verifications. Here in my project, I can use Sync View to see how my reused items may differ from the library or any other project using these common requirements. Let’s check out this folder called “Scheduling.”
I can see from our sync items view that I’m in sync with the platform, meaning there’s no difference there, but we have a parallel effort that I am out of sync with. In Compare View, I can see exactly how we differ and bring those differences, if necessary, into my project. Sync View provides me with the visibility I need to make sure I’m working with the latest applicable requirements in my project. Here I will update the requirement text and I’ll create the missing requirement in my project. Now my project and this parallel effort are in sync.
As we have seen, reuse and synchronization is a key feature supporting critical requirements and verification activities. A Jama Software consultant can help you properly support your process with reuse and sync. If you have a Success Program with Jama Software, see our offerings under Improving Your Process to request assistance from a consultant. Your customer success manager can help you learn more about Jama Software Success Programs. If you would like to learn more about how Jama Connect can optimize your product development process, please visit our website at www.jamasoftware.com.
https://www.jamasoftware.com/media/2023/10/FIF-Reuse-Sync-1.jpg10801920Zeb Geary/media/jama-logo-primary.svgZeb Geary2023-11-03 03:00:362024-01-17 22:55:21Jama Connect® Features in Five: Reuse & Sync
In this blog, we present a preview of our customer story, ” Global Industry Leading Automotive Application Developer dSPACE Migrates from Legacy Requirements Management Platform to Jama Connect®” – To download the entire story, CLICK HERE
Global Industry Leading Automotive Application Developer dSPACE Migrates from Legacy Requirements Management Platform to Jama Connect®
As part of a global modernization initiative, dSPACE partners with Jama Software® to migrate decades of data, increase collaboration, simplify compliance, and integrate processes across best-of-breed tools.
About dSPACE
Founded: 1988 in Paderborn, Germany (North Rhine-Westphalia)
Expertise: Solutions for automotive applications, including autonomous driving, E-mobility, power trains, V2X and connected services, communication systems, body and comfort electronics, and chassis.
Other Industries Served: On- and off-road commercial vehicles, aerospace, energy, rail, marine, machinery & power tools, and academia.
Mission: Enable technology and mobility pioneers to make life safer, cleaner, and easier.
dSPACE is one of the world’s leading providers of simulation and validation solutions that are used for developing connected, autonomous, and electrically powered vehicles.
Mainly automotive manufacturers and their suppliers use the company’s end-to-end solution range to test the software and hardware components of their new vehicles long before a new model is allowed on the road. dSPACE is not only a sought-after development partner in vehicle development, but engineers also rely on dSPACE’s expertise in aerospace and industrial automation.
dSPACE’s portfolio ranges from end-to-end solutions for simulation and validation to engineering and consulting services as well as training and support. With more than 2,400 employees worldwide, dSPACE is headquartered in Paderborn, Germany; has three project centers in Germany; and serves customers through regional dSPACE companies in the USA, the UK, France, Japan, India, China, Korea, and Croatia.
https://www.jamasoftware.com/media/2023/10/2023-09-26-dspace.jpg5121024Jama Software/media/jama-logo-primary.svgJama Software2023-10-24 03:00:512024-01-17 23:04:38Global Industry Leading Automotive Application Developer dSPACE Migrates from Legacy Requirements Management Platform to Jama Connect®
In this blog, we present a preview of our customer story, “Leading Quantum Computing Company Selects Jama Connect® to Decrease Review Cycles, Reduce Rework, and Improve Communication and Collaboration” – To download the entire story, CLICK HERE
Leading Quantum Computing Company, IonQ, Selects Jama Connect® to Decrease Review Cycles, Reduce Rework, and Improve Communication and Collaboration
With a return on their investment in less than six months, the IonQ team is confident they made the right selection.
About IonQ:
Founded in 2015 by Chris Monroe and Jungsang Kim to “build the world’s best quantum computers to solve the world’s most complex problems.”
Leveraging 25 years of academic research to build the world’s leading quantum computers.
Expanding quantum computing availability to the cloud through partnerships with Microsoft and Amazon Web Services, and Google Cloud Platform.
Headquartered in Maryland.
IonQ, Inc. is a leader in quantum computing, with a proven track record of innovation and deployment. IonQ’s latest generation quantum computer, IonQ Forte, is the latest in a line of cutting-edge systems, boasting an industryleading 29 algorithmic qubits. And IonQ Aria is the most powerful commercially available quantum system, with 25 algorithmic qubits. Along with record performance, IonQ has defined what it believes is the best path forward to scale. IonQ is the only company with its quantum systems available through the cloud on Amazon Braket, Microsoft Azure, and Google Cloud, as well as through direct API access. IonQ was founded in 2015 by Dr. Christopher Monroe and Dr. Jungsang Kim based on 25 years of pioneering research. IonQ began trading on the New York Stock Exchange in 2021, making it the world’s first public pure-play quantum computing company.
CUSTOMER STORY OVERVIEW
Growing fast in an emerging market, IonQ has implemented an ever-growing number of engineering best practices. The company’s team became frustrated managing requirements with Google Sheets and needed to solve core problems, such as linking between levels of requirements without extensive lookup tables. After rigorous evaluation, they selected Jama Connect® and are very pleased with the outcome.
CHALLENGES
Linking between levels of requirements without extensive lookup tables
Lack of clear traceability
Managing complexities across hardware and software
Lengthy review cycles
EVALUATION
Easy-to-use platform with an intuitive interface
Ability to view relationships between requirements
Change control and a review and locking function for requirements
Within budget
OUTCOMES
25% decrease in review cycle time
20% savings of systems engineers’ time (previously spent on manual processes)
25% improvement in communication and collaboration
https://www.jamasoftware.com/media/2023/10/2023-10-19-ionq-customer-story-1.jpg512986Jama Software/media/jama-logo-primary.svgJama Software2023-10-19 03:00:002024-01-17 23:06:01Leading Quantum Computing Company, IonQ, Selects Jama Connect® to Decrease Review Cycles, Reduce Rework, and Improve Communication and Collaboration
In this blog, we recap our webinar, “Application of Systems Engineering in Healthcare”. Click HERE to watch the entire webinar.
When it comes to healthcare, the first to market usually gains 80% of the market share, making development speed one of the most crucial aspects of success – or failure. That’s why many organizations are looking at systems engineering as a way of connecting needs to solutions.
In this webinar, Chris Unger of PracticalSE LLC and Vincent Balgos Director, Medical Device Solutions at Jama Software® have partnered up for an engaging webinar on the application of systems engineering in healthcare.
We invite you to join in as we delve into transformative role systems engineering is playing in the healthcare industry.
What to Expect:
1. The Power of Simplicity:
Discover how focusing on the basics, while maintaining world-class performance levels, can yield astonishing returns. We’ll show you how simplicity can be a game-changer in the complex world of healthcare systems engineering.
2. Market-Driven vs. Contract-Driven:
Intrigued by the difference between market-driven and contract-driven industries? We’ll explore how systems engineering varies in these two landscapes. Learn why “Market Driven” industries emphasize competitive value creation and use cases more than traditional requirements, and how this shift can redefine your approach in healthcare.
3. Striking the Perfect Balance:
Explore the ideal state of systems engineering in healthcare, often a harmonious blend of Agile, Lean Startup, and more traditional systems approaches. Uncover strategies to adapt, innovate, and succeed in this dynamic field.
Don’t miss this opportunity to gain a comprehensive understanding of how systems engineering can revolutionize healthcare. Whether you’re a seasoned professional or just beginning your journey in healthcare systems, this webinar promises valuable takeaways for all.
Below is an abbreviated transcript of our webinar.
Application of Systems Engineering in Healthcare
Chris Unger: We’re going to talk today about systems engineering in the medical industry, particularly medical device development. So the medical device industry faces several challenges. There’s clearly constant time pressure in developing and launching safe and effective products. We’ve got to be faster than the competition with better products. And as you can see from the statistics, this is a challenge. Part of the challenges in delivering things on time is the shifting regulatory landscape. I’m sure everyone’s aware of MDR. There’s software for medical devices. The FDA is going to think about redoing design controls next year. When we were at GE Healthcare, there were like 8,000 regulations we had to monitor. So it’s a very challenging and shifting regulatory landscape. Not only do you have to be compliant with regulations, but you have to ensure your device is safe. And so quality issues, safety and just keeping performance are key elements of delivering on time and that’s getting more and more expensive as you can see here, billions of dollars of financial risk of getting this wrong.
So to make all that harder, there’s a constant increase in complexity. When I first started, there were typical software development teams were 20 to 40 people. It’s now hundreds of people and lots of interactions. So additional things like AI, machine learning, or new technologies, really have to manage a lot of complexity inside of your devices. The organizational structure is getting more and more complex. There’s a heavy focus on acquisition, so you’re integrating new teams, new cultures, and geographically distributed development teams. So that makes it all challenging. So we’re going to talk about how systems engineering can help address some of these particular challenges.
Unger: As I mentioned, a key differentiator is getting to market faster. So the success of a program in a market-driven environment is basically profits. The first mover tends to collect the lion’s share of the profits. We typically have many customers. You don’t have a single customer marketing and product management tells you roughly what they think the competition will be and what differentiates versus in a contract-driven environment, success is satisfying the contract. So within GE Healthcare, the avionics and oil and gas businesses typically had a single customer. We would produce a floating city block to British Petroleum or Shell, go to the North Sea or the Caribbean and you had a contract and you delivered to that contract versus an engine, an aircraft engine, or a medical device, we deliver to the marketplace. We decide the timing, we decide the features.
So the stakeholders and market-driven are internal to the business and you can negotiate budget and time. If you get a really, really cool feature, you can take an extra month or quarter to develop it, versus in a contract-driven, it’s really fixed. So the challenges of market-driven and contract-driven are different. Contract-driven requirements are a key commitment. You’ve got to negotiate a formal design control versus within a market-driven environment they’re critical. You have to deliver validated requirements, but they’re definitely an internal business tool that helps communication across all the business functions.
So what’s the value of systems engineering in a market-driven industry? We basically turn the ambiguous needs that we get from product marketing or product management and turn them into clear and feasible solutions to be implemented by the hardware and software teams. The key value we produce is that those implementations seamlessly integrate into the customer’s workflow and work systems. So they work really well from day one, they reliably meet their needs. They work really well after five years and not just meet their needs, they delight the customer. We really want to deliver something that the customer enjoys using. So we have to make it work day one, we need to make it work day 50. We need to make it work for every single customer. So you have to deal with all the known variability of hardware and process. Every installation and every service event has to produce a uniform, high-quality, high-performing product.
So with those constraints, we want to optimize the business value. So when we have multiple options, marketing will tell us the customer value of these options. The implementation teams will tell us the delivery and product cost of those functions. The role of systems engineering is to make trade-offs between those and really optimize the business impact based on the cost of implementation. So we want to make sure the work done by those implementation teams is tied to the maximum market impact. And associated with that is managing technical risks. If you go down a path and it turns out to be infeasible, while it might’ve been nice if it worked, you just wasted a lot of that work. So that cost has to be scaled by risk.
In doing all those first four bullets, our key value is making sure design decisions are identified and closed predictably, and that the team acts with one voice. So decisions are framed, the options are agreed to, the decision criteria are agreed to and the final decision is closed and stays closed as stakeholders change. So once you have a frozen design, do you want to make sure that actually integrates easily and when you have integration or quality problems, they’re found early and resolved early. When you have time to react, it’s a lot easier to adjust your design in the first half of your program. It’s really hard when you find severe quality issues with a month left before shipping.
Unger: And so really winning products happen when systems thinkers are effective. So clearly there’s going to be a need for some systems engineering process thinkers, but they’re system thinkers across the entire program. And so we want to make sure that everybody’s involved in systems and that the creativity of the entire program is maximized. So getting specific to GE Healthcare, what is systems engineering at GE Healthcare? Well, we have the essential customer-perceived performance. So a lot of our programs are imaging, so we have the image quality. Still, we also have things like maternal-infant care where we deliver the right humidity and temperature around the neonate. In delivering that essential performance, you’ve got to make sure it’s safe and you’ve got to make sure you have regulatory compliance. And I mentioned we really want products that are easy to use and delight the customer. So usability is a critical part of systems engineering. In doing that, we make sure we define the right implementation requirements and the right reliability strategy, and that it can be installed and serviced properly.
So with that being the overall goal, how do we organize? Well, there are a lot of things that are common across all of our product teams. We do have common program milestones. We do have a common systems’ lifecycle. It’s basically the V-cycle with iteration and agile built in. What differs is that different product teams at GE Healthcare have different levels of safety hazards, so FDA risk. We go from anesthesia where you can easily kill somebody down to ultrasound, where it’s non-ionizing equipment, that’s the light handheld probes. You can’t pinch or crush anybody to even service software that has zero patient impact. There are also almost no risks for anybody and we respond to that by adjusting the process rigor so that the higher-risk safety risk modalities have higher process rigor.
Additionally, things vary across the world or we have different locations with different cultures and different sizes of organizations. We have many systems engineers across the company, but the SE team sizes vary from less than 10. In fact, we had some sites with maybe 10 engineers and the systems engineer was half a person to teams that had over a hundred systems engineers. The scale of the programs we work on is less than 10 engineers and months-long programs to many hundred as engineers applied to a program that might last three years and were based on technology developed over the prior decade. And you want some systems engineering thinking even during that basic research decade.
Unger: The organization goes from product centralized, it’s like the SE GM for that hundred engineering group where they all reported to a dotted or solid line, to decentralized in where that team of 10 with one or half a systems engineer, there the manager was a general engineering manager and did not have a lot of systems engineering experience. So I joke that if there is a way of organizing systems engineering, we have one of those within our group somewhere.
But how did we think about tailoring? And so this is a page I put together that was generalized that you might be able to use. Obviously, as I mentioned, higher technical risks including safety risks. One way of measuring that is how many risks there are in your hazard analysis. For things that are a higher risk we looked for a higher level of functional excellence, more process documentation, more process compliance, and higher rigor of the technical design reviews, and maybe more independent reviewers. Team experience. This is subjective to measure, but Joel Goldstein did a very nice study, from Carnegie Mellon, that the value of systems engineering increases with program complexity, but it decreases with a more experienced team if you have a small team that is experiencing the technology and the application, they can get by with less process rigor and while systems engineering excellence delivers some value, it delivers less value.
https://www.jamasoftware.com/media/2023/10/Application-of-Systems-Engineering-in-Healthcare-1.png5121024Chris Unger/media/jama-logo-primary.svgChris Unger2023-10-17 03:00:072024-01-17 23:07:52[Webinar Recap] Application of Systems Engineering in Healthcare
In this blog, we recap our webinar, “Bridging the Gap in Insurance Product Development”. Click HERE to watch the entire webinar.
Looking to bridge the gap in your insurance product development?
Learn how carriers can utilize Jama Connect® to increase efficiency across the development process and more effectively deliver high quality products on time and on budget.
During this informative session, Lianne Warford, Senior Business Analyst at LHW Consulting, and Steven Meadows, Principal Solutions Lead at Jama Software®, discuss how this newly available insurance framework and dataset streamlines and simplifies product development for the insurance industry.
Gain insights into:
Overcoming common insurance industry challenges
Leveraging the benefits of a modern requirements management solution
The new insurance framework available in Jama Connect, with off-the-shelf elements for enhanced workflow and efficiency
Discover how Jama Connect allows carriers to innovate, bring products to market quicker, and ultimately better serve their customers.
Below is an abbreviated transcript of our webinar.
Bridging the Gap in Insurance Product Development
Steven Meadows: Okay, so today, we have a pretty packed agenda. We’re going to be starting off or Lianne’s going to be talking about legacy insurance requirements management. Following that, we’ll be talking about how you can overcome some of the common insurance industry challenges, some of the important considerations for streamlined insurance product development. After that, I’ll be talking about the problem with legacy tools and insurance product development, followed by best practices for an effective development strategy. I’ll then be providing a brief introduction to Jama Connect for Insurance, very high level overview. And then finally, we’ll end with a solution key takeaways and questions. And with that, Lianne, go ahead.
Lianne Watford: All right, thanks Steven so much. I appreciate this opportunity to work with Jama Software. I want to get started today with talking about different scenarios, two main scenarios where requirements are needed in the insurance industry. So we have the policy administration systems that automate the day-to-day operations of an insurance company. And the second area is the new and enhanced insurance products and services that insurance companies want to undertake. So let’s just dive right in. It has a lot of information, so let’s get started. So from the policy administration system, while every insurance company’s unique, processes that all insurance companies share for the day-to-day operations are quite common. And I’d venture to say that you would have to look long and hard to find an insurance company today that doesn’t have some type of policy admin system, whether it be a homegrown system that they’ve done themselves or utilizing some other type of software vendor.
Watford: So if you take a look at the areas that are common, you have your policy administration. So every insurance policy starts with a quote and there’s quite a bit of information that needs to be captured. You’ve got your insured name, address, and contact information among others. You have information about the risk that’s being insured, whether it’s a house, a car, or business. And there are specific details for each types of risks that have to be captured to provide an accurate rate for the policy. You’ve got your coverages that are needed for each of the specific types of risks like property damage and liability coverage, and there’s lots of information that needs to be captured around that as well. And then once the policy is bound and issued, there’s several different types of documents such as declaration pages, rating sheets, etc, that have to be generated and are dependent on specific policy details.
And while those requirements are related to the insured risk and coverages, there’ll be an entirely different set of requirements for the output that describe the information about both the static and the variable data that’s needed to be printed. So that’s a ton of information right there. If you haven’t really captured it, we’ve just hit one bullet point under the policy admin. And then you’re always going to have the need to make a change to the policy at some point. And those are processed as endorsements. And while some of these requirements can be reused from the quote bind and issue process, there’ll also be certain rules for different types of endorsements that’ll need to be captured as separate requirements. And then you also have the output that’s specific to those related endorsements. Again, more stuff. And then you also have the processes around your cancellations and reinstatements for underwriting reasons, and you’re going to have documents that go along with that as well.
Watford: All of those have to have requirements for the related output and downstream effects as well. And then hopefully the insured’s going to be happy with your service at your company and they’ll want to renew the policy for another term. So yep, there goes another set of specific requirements that are associated with the processing of the renewal as well as the output that’s associated. That’s a big mouthful of information. But then the next step you’ve got to do is collect the money for the premium that’s generated on the policy. So you gather requirements for down payments if you require them. You also provide payment plan options to allow them to pay, and installments are all at one time, so there’s lots of requirements around that. Then you also have special rules for nonpayment of premium cancellations and reinstatements that are different from your underwriting cancellations and reinstatements, different set of requirements.
And then you have to process refunds and collections. Again, and there’s all types of outputs that go along with these processes as well that have to be documented. And then of course, the big thing for an insurance company is your annual statement. That’s your accounting for what insurance companies do. And so, there’s all kinds of requirements for your annual statement, annual statement lines, and statistical reporting. Again, a ton of requirements. And then last but not least is your claims administration, which is the reason that you actually have insurance, right? So that if you need to make a claim, so you have your requirements around first notice of loss and then there’s a ton of information that they have to capture, lots of things that they have to do in that area as well. Come out and inspect, assign agents, all different types of processes for your claims.
And then you ultimately want to make a payment to the insured when it’s needed and processing of reinsurance if your company handles reinsurance. So that’s a mouthful of information and lots of requirements that maybe a lot of people don’t think about when it comes to insurance day-to-day operations. And then when you move on to thinking about the company wants to have new and enhanced insurance products and services. So you’ve got new products that you want to offer, you have new states and lines of business and coverages that you want to move into. And then if you want to enhance existing products, you’ve got rate changes, additional coverages you want to provide. And then there’s all kinds of interfaces, imager, quick rater, all types of interfaces into insurance policy admin systems that help integrate your business. And then not to mention, you’ve got to upgrade those existing interfaces because softwares are continuously evolving.
https://www.jamasoftware.com/media/2023/10/Bridging-the-Gap-in-Insurance-Product-Development.png5121024Steven Meadows/media/jama-logo-primary.svgSteven Meadows2023-10-10 03:00:412024-01-17 23:10:34[Webinar Recap] Bridging the Gap in Insurance Product Development
Jama Software® Announces Largest Scale Achieved by Any Requirements Management Software
Jama Connect® 9.5 proven to scale to at least 10 million requirements in a single project to handle the largest product, systems, and software development efforts.
Jama Software®, the industry-leading requirements management and traceability solution provider, has announced that Jama Connect® has set yet another scalability record with over 10 million requirements managed in a single project (within a standard cloud instance) with P75 user interface load times under three (3) seconds. 10 million requirements per project represents a new benchmark in the industry, clearly showing that Jama Connect is able to meet both the current and future scalability needs of our customers. It is also important to note that no project data storage limits were hit during this boundary condition test, so the actual limit has not yet been reached.
Engineering organizations are looking for software partners that can handle large-scale, collaborative projects that span engineering disciplines, customers, and suppliers. This performance benchmark demonstrates Jama Connect’s unique ability to handle the scale required within a single project. Today, our customers work with tens of millions of requirements across projects in a single instance of Jama Connect. This latest single project scalability milestone adds to Jama Connect’s market-leading standing for security, scalability, and performance in the cloud including:
Over 100,000 trailing 90-day active users
Daily users spanning 82 countries
16ms First Input Delay (FID) response times
P75 response times of 2.7 seconds
The only requirements management application that is SOC 2 Type 2 certified at the environment AND application layers
The richest REST API with over 200 separate API functions
Over 600 million API cloud service requests per month
“Jama Software continues to lead the market in performance, security, and usability at scale,” said Josh Turpen, Chief Product Officer at Jama Software. “We are pushing beyond the 10 million threshold and will continue to deliver unmatched cloud capabilities to our customers.”
About Jama Software
Jama Software® is focused on maximizing innovation success in multidisciplinary engineering organizations. Numerous firsts for humanity in fields such as fuel cells, electrification, space, software-defined vehicles, surgical robotics, and more all rely on Jama Connect® requirements management software to minimize the risk of defects, rework, cost overruns, and recalls. Using Jama Connect, engineering organizations can now intelligently manage the development process by leveraging Live Traceability™ across best-of-breed tools to measurably improve outcomes. Our rapidly growing customer base spans the automotive, medical device, life sciences, semiconductor, aerospace & defense, industrial manufacturing, consumer electronics, financial services, and insurance industries.
For more information about Jama Connect services, please visit www.jamasoftware.com
https://www.jamasoftware.com/media/2023/10/2023-10-05-v3-largest-scale-by-rm-software-release.jpg5121024Karrie Sundbom/media/jama-logo-primary.svgKarrie Sundbom2023-10-05 06:30:222023-10-05 11:49:06Jama Software® Announces Largest Scale Achieved by Any Requirements Management Software
In this blog, we recap our webinar, “Compliance Made Easy with Jama Connect® for Automotive and Semiconductor Development”. Click HERE to watch the entire webinar.
Evaluate Your Compliance Against ASPICE, ISO 26262, or ISO 21434 with Diagnostic Services Offerings from Jama Software®
During the webinar, experts Steve Rush, Principal Consultant, and Sampath Yerramalla, Senior Consultant, explored various service offerings within Jama Connect that provide insights into compliance status against these critical automotive standards.
Key takeaways from this webinar:
Learn about available diagnostic offerings in Jama Connect, such as: ASPICE, ISOS26262, and ISO21434
Learn about the benefits of diagnostic offerings, how they will expose risks to compliance, and which one is best for your organization
See firsthand how Jama Connect helps teams reduce unacceptable risks
Discover how Jama Connect can empower Automotive and Semiconductor development teams to evaluate and ensure compliance.
Below is an abbreviated transcript of our webinar.
Compliance Made Easy with Jama Connect for Automotive and Semiconductor Development
Steve Rush: Hi everyone. I’m happy to be here today to take you through the presentation. I wanted to start with a high level agenda and an introduction. We’ll be discussing Automotive compliance in general. To start, we’ll be looking at specific service offerings that you can use to help leverage, to evaluate your compliance against certain Automotive standards.
There are two forces often related that I like to think about when it comes to compliance that really impact the organization as a whole, from engineers to executives and everybody really in between. And those are process and quality. And I like to think about compliance as the intersection of those two often related ideas. Meeting the objectives of these standards may achieve both process and quality, but developing a compliant process and system, this will speed up development by instituting good process and reducing rework. It will help catch and identify defects early in the development process. However, there’s many evolving regulations and standards in this Automotive sector that make the idea of compliance all the more challenging to understand, let alone demonstrate. Perhaps you don’t even know where to start when it comes to achieving compliance in an Automotive system. It might feel like you are building a car while it’s driving.
At the same time tasked with implementing the process and tools to support the process and unsure which should come first. And we want to talk a little bit about this through the lens of compliance and make the case that Jama Connect is a tool well suited to get you up and running quickly, optimized against popular Automotive standards. To assist with this, we’ll discuss the diagnostic that Jama Software offers as a service that’ll help you navigate these important compliance questions. But I fully believe that by meeting the objectives of some of these critical Automotive standards we will discuss today that you’ll balance both process and quality and achieve compliance.
Sam Yerramalla: Today we are highlighting some offerings that will help guide Automotive customers or prospects like you with your compliance process. We feel these diagnostics can be very helpful whether you are a customer of Jama Software or a prospect. If you’re a Jama Software prospect who’s not yet purchased Jama Connect, these diagnostics makes the case that Jama Connect can help you meet the objectives of the Automotive standards. And namely, there are three standards offerings that we provide. One is the ASPICE Diagnostics, the Automotive Functional Safety Diagnostics, and the Cybersecurity Diagnostics. Now these diagnostics can help you navigate the classic process versus tool conundrum. That is if you’re trying to understand whether you should build the process first or buy the tool first, you’ll first see firsthand how Jama Connect will help shape the process. If you’re a Jama Software customer, you can use these diagnostics as a baseline. Oftentimes, we get busy with our day-to-day work and we may drift away from the larger big picture.
And these diagnostics are meant to guide you to bring light into areas that you need improvement or any optimization of your current Jama Connect process. You can also be paired with a Jama Software consultant or a solutions architect who will take you through the diagnostics start to finish. The time commitment for each of these diagnostics is about two to three hours. We feel that’s reasonable considering the benefits you may get out of this. We focus on the outcomes and the objectives and how this will truly help meet your compliance needs by optimizing your Jama Connect usage. If you’re a customer or getting up and running in Jama Connect, if you’re a prospect who’s looking for purchasing Jama, you can see these diagnostics offerings along with other offerings that we provide on the Jama Software Success Program page at Jamasoftware.com/success. Here you’ll see details on the compliance offerings that we just mentioned and a lot more other offerings including offerings on onboarding Jama Connect, improving your process and requirements, quality, traceability, et cetera.
Yerramalla: You can also request an offering if you have a service program with no assigned consultant and our operations team will pair you up with someone. So as far as the Automotive standards and alignments are concerned, the diagnostics offerings that we provide are aligned to the three standards, the Automotive Spice, ISO 26262 and ISO 21434. Only certain areas of those standards are in scope. For example, things like part seven of the ISO 26262 for production and operation and decommissioning are not covered here. But you will see some of these sections here are covered by the diagnostics. So depending on which diagnostics is right for you, the risks that are identified will align to the different areas that you see on the screen. Now, it may be that you want to align to more than one standard. We certainly put you through multiple diagnostics to identify your risks pertaining to each of these standard.
The model which we use is the same, but the recommendation we provide and tailored solution that the diagnostics provides will be custom based on each scenario. And if you don’t know where to get started or you don’t know which of these diagnostics that you need to start first. Some things are obvious, again, that if you’re looking for cybersecurity compliance and that is of the greatest concern for you, then Cybersecurity Diagnostics, the 21434 is right.
And if you’re looking for developing any functional safety products that are used in the Automotive, then the ISO 26262 diagnostics is the correct one to start with. And if you’re looking for any software process improvements or quality management, then ASPICE is the place to start. But sometimes you need both APSICE and functional safety, for example, in which case we suggest the ASPICE Diagnostics first. And the reason is that we rank in the process ASPICE about the functional safety is that if you have a high level of ASPICE maturity or on the other side, if there are several risks that are flagged from the ASPICE Diagnostics, then those will impact your Functional Safety Diagnostics already.
So you would’ve covered those parts of it that as a prerequisite for the functional safety. And then the spirit of ASPICE is really the quality management. And this is important in every engineering organization. So if you’re unsure where to start, then ASPIE Diagnostics is one place. And if you don’t need to prove compliance to the latter, it’s really good because honoring it, the lead benefits in your process.
https://www.jamasoftware.com/media/2023/09/wb-2023-09-27_Compliance-Made-Easy.png5121024Steve Rush/media/jama-logo-primary.svgSteve Rush2023-10-04 03:00:262024-01-17 23:12:38[Webinar Recap] Compliance Made Easy with Jama Connect® for Automotive and Semiconductor Development
Traceable Agile™ – Speed AND Quality Are Possible for Software Factories in Safety-critical Industries
Automotive, aerospace and defense, and industrial companies have largely adopted Agile within rapidly growing software factories to speed time to market in order to stay competitive. These software factories have largely succeeded in speeding up software development for companies within the industries that have adopted it, but maintaining quality is still a key concern. The inability to coordinate development across engineering disciplines has led to product recalls, quality complaints, and has created significant internal challenges to satisfy functional safety requirements from regulators and confidently deliver high-quality software. These challenges — and resulting outcomes — are often so severe that leadership of the software factories have been let go.
Fundamental Questions We Hear
When we ask software factory leaders, “what keeps them up at night?” We consistently hear the following five questions:
How do I know which product requirements have been missed?
How do I know which product requirements are not fully covered by test cases?
How do I know which product requirements have failed to pass tests?
How do I identify rogue development activity?
How do I know if changes have been made at the system and / or hardware level that impact the software team?
These are fundamental questions that should be answerable from leading Agile tooling, but they are not. The reason is that Agile tools focus on tasks (define, assign, status, complete, delete) and have no notion of the current and historical state of the project. Tasks are not tied to any state of the project which often leads to drift from the actual needs and requirements of your customer or end user. As a result, these questions are not answerable with Agile tools like Jira and Azure DevOps. Project management tools like Jira Align answer important questions around staffing, sprint planning, and cost allocation, but do not address the critical questions above focused on the real-time state of the software development effort against the approved requirements.
How do you best speed software and overall product development and still achieve the quality expectations of customers and company leadership? The answer is Traceable Agile. Traceable Agile speeds the FLOW of software development but also maintains the current and historical STATE of the development effort and auto-detects issues early in the software development process. Traceable Agile recognizes that developer activity is best managed as a FLOW using tasks in a tool such as Jira. What is needed to achieve Traceable Agile is to pair a system with Jira that manages the STATE of the development effort at all times. By keeping STATE and FLOW tools separate but integrated, no change is required to software developer process and tools. This is significant. Software leadership can now answer their critical questions without having to undergo a major process and tool change with resistant developers which would slow down development and/or increase staff attrition.
Here is an overview and diagram of Jama Connect® maintaining the STATE of development activity and Jira providing the FLOW.
Task activity continues as normal in Jira and risk is auto-detected in Jama Connect by comparing all user stories and bugs in Jira to the expected development and test activity for each requirement in Jama Connect.
All exceptions are identified —the ones that answer the questions that keep software factory leadership up at night — such as requirements with no user stories, user stories with no requirements, requirements with no test cases or test results, etc.
After the exceptions are inspected in Jama Connect, management can take action and assign corrective tasks in Jira as just another task in the queue for a developer.
This is a fully automated process that leverages automated synchronization of meta data between Jira and Jama Connect via Jama Connect Interchange™. The only metadata that needs to be synchronized from Jira to make Traceable Agile possible is as follows: ID, Created Date, Creator (User), Modified Date, Modifier (User), Title, Status, Link (URL), Relationships. On inspection in Jama Connect of an issue, one simply clicks on the link to go to Jira if more information is required to diagnose.
Many of our leading clients have already implemented Traceable Agile and are significantly improving their Traceability Score™ which we have demonstrated leads to superior performance on quality metrics in our Traceability Benchmark Report.
Feel free to reach out to me to learn more and I will respond.
https://www.jamasoftware.com/media/2023/10/2023-10-04-v2trademarked-traceable-agile-speed-and-quality.jpg512986Marc Osofsky/media/jama-logo-primary.svgMarc Osofsky2023-10-03 03:00:372024-01-17 23:13:45Traceable Agile™ – Speed AND Quality Are Possible for Software Factories in Safety-critical Industries
