Tag Archive for: Requirements & Requirements Management Page 13
Tag Archive for: Requirements & Requirements Management
Unlocking the Potential: The Importance of Software Defined Vehicles Explained
Introduction
The automotive industry is undergoing a massive transformation, driven by technology. One of the most exciting developments is the concept of Software Defined Vehicles (SDVs). In this blog post, we will explore the importance of SDVs and how they are revolutionizing the automotive landscape.
What is a Software Defined Vehicle?
Software Defined Vehicles are automobiles that rely on software and data to control major functions, such as propulsion, safety systems, and entertainment features.
Unlike traditional vehicles, which heavily rely on hardware, SDVs leverage advanced software algorithms and connectivity to enhance performance, functionality, and user experience.
SDVs offer tremendous flexibility and customization options. Software updates can be deployed remotely, allowing manufacturers to introduce new features or improve existing ones without physical modifications. This not only enhances the vehicle’s performance but also enables personalization according to user preferences.
2. Enhanced Safety and Autonomous Capabilities
SDVs play a crucial role in advancing vehicle safety and autonomy. With software-controlled systems, real-time data can be processed and analyzed more efficiently, enabling the vehicle to make instant decisions and react to various scenarios. From adaptive cruise control to automated emergency braking, SDVs are paving the way for a safer and more autonomous driving experience.
3. Improved User Experience
Software Defined Vehicles provide a seamless and intuitive user experience. Smart infotainment systems, integrated navigation, and connectivity features ensure drivers stay connected and informed on the road. Additionally, software updates can optimize vehicle performance and functionality, ensuring a consistently delightful driving experience throughout the ownership period.
4. Enhanced Sustainability
SDVs contribute to sustainability efforts in multiple ways. By optimizing energy consumption, software algorithms can improve fuel efficiency or increase the range of electric vehicles. Moreover, SDVs enable over-the-air updates, reducing the need for physical recalls and reducing waste associated with hardware replacements.
Challenges and Considerations
1. Cybersecurity
With increasing connectivity and reliance on software, cybersecurity becomes a critical concern. As Software Defined Vehicles become more commonplace, manufacturers and developers need to prioritize security measures to protect vehicles from hacking and unauthorized access.
2. Data Privacy
The extensive use of software in SDVs generates vast amounts of data. It’s crucial to develop robust privacy frameworks to ensure the responsible collection, storage, and use of data, protecting user privacy rights.
3. Regulatory Framework
The emergence of Software Defined Vehicles raises questions about legal and regulatory frameworks. Governments and authorities need to adapt and establish comprehensive regulations to ensure safe and responsible integration of SDVs into existing transportation systems.
Software Defined Vehicles represent a paradigm shift in the automotive industry. By harnessing the power of software and connectivity, SDVs offer unparalleled flexibility, improved safety, enhanced user experience, and sustainability benefits.
However, to fully unlock the potential of SDVs, we must address challenges related to cybersecurity, data privacy, and regulatory frameworks. Embracing this transformative technology will lead us into a future of smarter, safer, and more efficient transportation.
Note: This article was drafted with the aid of AI. Additional content, edits for accuracy, and industry expertise by Matt Mickle, McKenzie Jonsson, and Decoteau Wilkerson.
Stay tuned to our blog for future software defined vehicles content, including more in-depth explanations of how to adapt to these key challenges.
Stay tuned to our blog for future software defined vehicles content, including more in-depth explanations of how to adapt to these key challenges.
https://www.jamasoftware.com/media/2023/09/d38ce0b9-9295-44fc-bed2-a0f1e0d951ae-1.jpeg5121024Jama Software/media/jama-logo-primary.svgJama Software2023-09-12 03:00:572024-01-17 23:18:14Unlocking the Potential: The Importance of Software Defined Vehicles Explained
Best Practices for Verification and Validation in Product Development
In the competitive landscape of modern product development, ensuring the reliability and quality of the product is essential to meet customer – and stakeholder – expectations and regulatory requirements. Verification and validation (V&V) are two crucial processes that play a pivotal role in achieving these goals. V&V are systematic methods that assess a product’s adherence to specifications and its ability to perform as intended. In this article, we will delve into the best practices for verification and validation in product development, exploring the key steps, methodologies, and benefits of each process.
Understanding Verification & Validation
Before delving into the best practices, it is essential to clarify the distinction between verification and validation. Verification focuses on assessing whether a product meets its design specifications, ensuring that each component and feature works as intended. On the other hand, validation is concerned with evaluating whether the product fulfills its intended use and customer needs. In essence, verification confirms if the product is designed correctly, while validation confirms if it is the right product for the intended application.
Incorporating V&V Early in the Development Lifecycle
To maximize the effectiveness of verification and validation, these processes must be integrated into the product development lifecycle from its early stages. By starting V&V activities early, potential issues can be identified and resolved before they escalate, reducing costs and time-to-market. Early involvement also allows for feedback to be incorporated into the design, leading to a more robust and reliable final product.
Clearly Defined Requirements
Well-defined requirements are the foundation of successful verification and validation. During the requirements gathering phase, it is vital to engage stakeholders and subject matter experts to create clear, measurable, and unambiguous specifications. These requirements serve as the baseline against which the product will be verified and validated. Proper documentation and version control are critical to ensure that changes to requirements are tracked effectively. Additionally, the later in the development process that requirements get changed, many times because they weren’t written well the first time, the more costly it is due to downstream impacts such as rework in verification and validation.
Product development teams should employ a mix of V&V techniques to comprehensively assess the product’s quality. Some commonly used methods include:
Testing: Conduct thorough testing, including unit testing, integration testing, system testing, and user acceptance testing, to verify that each component and the product as a whole performs as expected.
Simulation: Use computer simulations to evaluate the product’s behavior in various scenarios, particularly for complex systems or when physical testing is impractical or cost prohibitive.
Prototyping: Building prototypes early in the development process allows for real-world testing, uncovering potential design flaws and usability issues.
Peer Reviews: Encourage regular peer reviews of design documents, code, and other artifacts to catch errors and improve the overall quality of the product.
Model-based Design: Utilize model-based design approaches, such as Model-Driven Architecture (MDA), to create detailed models that can be verified before implementation.
Risk-Based Approach
Incorporate a risk-based approach into V&V activities to focus resources on critical areas. Identify potential risks associated with product failure and prioritize verification and validation efforts accordingly. This approach ensures that resources are allocated efficiently, concentrating on areas with the most significant impact on product performance and safety.
Independent Verification and Validation (IV&V)
Consider engaging external experts or teams for independent verification and validation. External parties can provide an unbiased assessment of the product, uncovering issues that internal teams might overlook due to familiarity or assumptions. Independent verification and validation bring additional expertise and ensure a higher level of confidence in the product’s quality.
Continuous Integration and Continuous Delivery (CI/CD)
Implementing CI/CD practices allows for continuous verification and validation throughout the development process. Automated testing and deployment pipelines can quickly detect regressions and integration issues, ensuring that the product remains stable and reliable throughout its evolution.
Documenting V&V Activities
Comprehensive documentation of all verification and validation activities is essential for compliance, knowledge retention, and continuous improvement. Properly documented V&V processes help maintain a historical record of changes, failures, and resolutions, facilitating future product iterations and troubleshooting.
V & V are integral to successful product development, ensuring that products meet the required specifications and perform as intended. By adopting best practices such as early integration, clear requirements, a mix of v&v techniques, risk-based approaches, and continuous verification, companies can create high-quality, reliable products that customers love and gain a competitive edge in the market. Moreover, investing in verification and validation from the outset of development can save time and resources, prevent costly delays, and lead to higher customer satisfaction and loyalty in the long run.
https://www.jamasoftware.com/media/2023/08/2023-09-07-verification-and-validation-1.jpg512986Jama Software/media/jama-logo-primary.svgJama Software2023-09-07 03:00:172024-01-17 23:19:12Best Practices for Verification and Validation in Product Development
In this video, we demonstrate Review Center capabilities in Jama Connect®
Jama Connect® Features in Five: Review Center
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, Jama Software® subject matter expert Mario Maldari,Director of Solution Architecture, will demonstrate Review Center capabilities in Jama Connect.
VIDEO TRANSCRIPT:
Mario Maldari: Hi. My name is Mario Maldari, and I’m the Director of Solution Architecture here at Jama Software. In this video, we will demonstrate a powerful and easy-to-use feature in Jama Connect, the Review Center.
Reviews play a key role in successful product development. In this video, you will learn how to initiate a review, how to invite participants to a review, how users can complete tasks, provide feedback, and finish a review. You also see how moderators can view review activity, interact with feedback, publish revisions, compare review versions, and more. Now let’s get to the demo.
Anything in Jama Connect can be sent to the review center, individual requirements, or a set of requirements, simply right-click and send for review. This will put you into our, Review Center dialogue where you’ll have a few options to choose from, give the requirement to review a name, a deadline, and a time. You can include related items. Perhaps you want the test cases that are associated with the requirements to be reviewed as well and select those. You have a few additional options.
You can choose to have an electronic signature. You can enable time tracking, and notify when a participant finishes a review. I like that one. In this dialogue, you can add your users and assign them various roles, review approver.
And we’ll have a couple of reviewers here.
Maldari: A very nice feature of our review and approval is the ability to invite users by email. This allows you to invite, participants in your review, that aren’t part of your project, your job or project, or aren’t even part of your company. Perhaps you have, vendors that have given you requirements that you want their feedback on, stakeholders. So you can add them.
They can participate in the review, and you don’t have to add them to the project. So let’s continue on here. This final dialogue is in the details of the email that’ll be sent out to the participants. Customize this as you see fit. And let’s initiate that. Alrighty.
Essentially, the email that your participants will see will look very, very similar to this. It’ll have some instructions. It’ll have the link to the review. Their role and what the deadline is. As soon as they click on this link from their email, it’ll send them into the review. Where they’ll be able to go through and accept or reject, each item as they go through the review. You’ll be able to see the related items here in this case, the test cases because we included that in the review. So very nice to be able to include that as well. So I’ll go through and I will accept.
And perhaps there’s a case where I disagree with something or I’d like to see a change. I can get very granular in terms of my commenting ability. I can select over text. And I can say and I could even @ mention users here as well as an FYI, and I could further qualify the comment. Perhaps, say, I have an issue with it, I can enter my comment. When I’m done with the review, I simply click complete review.
And it gives me a nice summary of what has changed in my review. And at this point, I could either be done, you know, assuming maybe I accepted all the requirements. I was happy with it. In this case, since I rejected one, I’d like to request a new revision after the update is made. So the moderator at this point would get a notification that someone has completed the review. They’d be able to come in and see all of the passing, requirements, but then they could also see the comments on the ones that I would like, to have updated so they could say, okay. It should be more specific. So they can simply go into the requirement. They could edit it.
Maldari: And I can get a little more detail in this case. They could resolve the comment right from here. And they can resolve that comment right on the fly. It could say, save and close, commit, ok. And now at this point, the moderator could publish a new revision, and they could let the reviewers know that there’s a new version of that particular requirement. So let’s publish that after the change that was made.
And now they can actually see that there are two versions. Of the review. You can compare version one to version two, and you can see what’s changed in the requirements between the two versions. So a really nice way of seeing how the requirements evolve over time by virtue of the reviews.
The moderator also has some really nice views here in terms of statistics of the ability to see where the team is in terms of, you know, how far along they are in their review, how many they’ve approved, rejected, the time spent, on the reviews, They can email the participants, send reminders, email the approvers only. A lot of different information and statistics here. They can look at the types of comments that were put as part of the review so they can get a sense of how many changes they may need to make. Maybe there are just some questions and general comments, but if there are proposed changes or issues, you know, that’s that translates to work, the moderator may have to do.
So it’s really good information in terms of statistics here. All of the reviews that are in progress, completed, are stored in the review tab, all the Jama Connect, And so that at any given time, you can go back. You could take a look at your reviews, you know, see how the requirements evolved over time. Maybe a year later, you need to produce an audit report.
Maldari: Jama Connect allows you to create reports off on these reviews with all the comments and the states of the requirements. So very useful, for seeing how your requirements have evolved over time. A very powerful feature of the Review Center, but also as you can see, very easy to use and and very collaborative.
If you would like to learn more about how Jama Connect can optimize your product development processes, please visit our website at www.jamasoftware.com. If you’re already a Jama Connect customer and would like more information on the Review Center, please contact your customer success manager or Jama Software consultant.
https://www.jamasoftware.com/media/2023/08/FIF-Review-Center-1.jpg10801920Mario Maldari/media/jama-logo-primary.svgMario Maldari2023-09-01 03:00:022024-01-17 23:21:15Jama Connect® Features in Five: Review Center
In this blog, we recap our webinar, “Manage by Exception: Data-driven Practices to Improve Product Quality”. Click HERE to watch the entire webinar.
Curious how data-driven practices unlock successful product delivery?
Our recent webinar explores the transformative approach of managing by exception in reducing product failure risk. In this session, we walk through why managing by data is crucial, how data “exceptions” uncover gaps, and real-life examples in product development.
During this informative session, Preston Mitchell, VP, Global Solutions at Jama Software®, offers insights on how Jama Connect® helps teams proactively prevent gaps in requirement quality and traceability to streamline their product delivery process.
Check out this webinar to learn:
Why data-based management is important
The definition of a data “exception” and how it uncovers gaps
Examples of “exceptions” in daily product development and requirements management
How Jama Connect’s unique features, such as Advanced Filters and Dashboards, can help your team manage by exception
How to proactively prevent exceptions using Jama Connect Advisor™ and Live Traceability
Discover how Jama Connect can help your team manage by exception and navigate product development with precision.
Below is an abbreviated transcript of our webinar.
Manage by Exception: Data-driven Practices to Improve Product Quality
Preston Mitchell: Hello everyone and thank you for joining today. My name is Preston.. I’m the VP of our solutions department at Jama Software and I lead our rockstar team that delivers solutions and services for all of Jama Software’s customers. I’ve been with Jama Software for over 10 years and held several positions within the company and over the course of my time here, through hundreds of client engagements to onboard and deploy Jama Connect, I have learned a lot from our customers and our customers really are our inspiration. They’re building next-generation products like self-driving cars, life-saving medical devices, futuristic robots, and the thread that ties all of these customers together is the central theme of how we can make better decisions to improve the success rate of our R&D function or our product development function. So I’m really excited to talk to you all today about the theme of managing through data to do just that. How can we bring measurable improvement to your process?
So for the agenda today, we’re going to talk about the power of data, how Jama Software empowers our customers to use data and exception management, and some key measurements that we prioritize such as requirements quality and the traceability score. And then finally we’ll close out with how you can plan for success in this and just some Q&A from the audience. So we’ll have my colleagues helping out with the chat. Juliet’s going to share some of the questions, so don’t hesitate to use the chat to ask questions.
Mitchell: All right, so it should be obvious to most, but managing through data brings several benefits to your organization. Software is a part of our day-to-day work and it’s enabled an exponential increase in collaboration and visibility. And increasing visibility to that critical data and the workflows allows teams to have a more shared understanding of the goals, the problems, and the action items that all go into making successful products. And rolling up this data allows the R&D and product development leaders to have more real-time metrics and make better business decisions. So when you start to manage through data, this increased visibility really encourages process improvement and also really professional growth. But at the same time, there’s a challenge that comes along with this. This increase in the amount of data that is available often is overwhelming given that the time that you have in a day is really a fixed resource.
We want to make this a little bit interactive. I’d be curious to hear from the audience, how do you use or maybe how do you not use data today in your decision-making with regards to developing new products? So Juliet, why don’t we pull up our first poll? What’s the primary method that your organization uses for major decisions in the development of the products and systems that you build? So we’ll give folks about 20 seconds to answer this.
Okay, and I see some interesting results coming in here so far. Well, I know it’s hard to pick just one primary as the reality is there are likely multiple of these here for really large decisions. I was wondering how many folks would pick the first and the last option. Intuition or just plain not sure. So let’s move forward here.
I have linked a very interesting Harvard Business Review article called Don’t Trust Your Gut. But if I were to summarize it, intuition is often glorified quite a bit in the business world and especially when people are wildly successful. So for example, if you make a big business or a personal bet that pays off, these are often celebrated. But in business, we hear a lot about failures too, and they’re often blamed on things like poor timing, and poor market fit, maybe a lot of it is poor execution, but one adjacent failure symptom is the lack of an alarm to trigger a change. So we often hear the old adage, that it’s better to fail fast than early so you have a chance to course correct.
Mitchell: With the right data and the right alarm triggers, this is possible and for the customers that Jama Software works with, you have smart engineers, product managers, and business analysts, oftentimes biased and emotional. They can play a real role in making bad decisions that eventually lead to some sort of R&D or product development failure. And when your engineering leaders or even yourself don’t have the data on execution progress when your teams are not actually tracing requirements to the why or the need for customer validation. And when we don’t have insight into things like verification coverage, and all that missing data, you’re going to find that we encounter these problems way too late in the development cycle.
And we see this very often in the news, these failures that happen too late. Investigations happen, and recommendations are made, but how can we make data available to the right people so that we can prevent these issues from ever occurring in the first place? That’s what we’re going to talk more about today. And as the famed management guru, Peter Drucker said, “If you can’t measure it, you can’t improve it.” So being able to use data to measure allows your teams to see recurring patterns or anomalies and then individuals can then take care of these before they become a larger problem. Or better yet, how can we create preventative measures and automation to improve the process overall?
So that leads us to the key principle that we’re going to talk about today. Management by exception. So management by exception is a methodology that’s really meant to empower your team with the data around early warning indicators so that you can make smarter and faster decisions. It also allows leadership to focus their time on the exceptions and not micromanaging or intervening with the teams if the majority of the engineering data shows that the product development is going as expected, and I really want to reemphasize that because it’s not meant to micromanage. In fact, it should lessen that. A common hurdle that teams face when you introduce a change where you’re transforming the organization by managing through data is resistance.
https://www.jamasoftware.com/media/2023/08/2023-Webinar-Recap-Med-Update-4.png5121024Preston Mitchell/media/jama-logo-primary.svgPreston Mitchell2023-08-24 03:00:272024-01-17 23:23:29[Webinar Recap] Manage by Exception: Data-driven Practices to Improve Product Quality
MIL-STD-810: Ensuring Quality and Reliability in Challenging Defense Environments
From the desert to swamps to the frozen tundra, the United States Department of Defense (DoD) created the Military Standard 810 (MIL-STD-810) to enforce manufacturers deliver a product that will not fail in operational environments. This compliance regulation outlines environmental engineering considerations for testing equipment’s durability, performance, and quality in challenging and harsh environments. The blog will explain the significance of MIL-STD-810, its purpose, and how it impacts industries and consumers worldwide
Understanding MIL-STD-810
MIL-STD-810, widely used by commercial, non-military entities as well, prescribes a series of tests and procedures that have been created to measure the durability of equipment and its ability to survive in tough conditions.
Initially published in 1962, the standard has been regularly updated to keep up with technological developments and the varying environmental conditions. MIL-STD-810 thus serves as a useful tool for manufacturers, guaranteeing that their products can withstand the toughest circumstances.
The Purpose of MIL-STD-810
Defense contractors and manufacturers are required to meet the requirements outlined in this standard to sell their equipment to the U.S. military. MIL-STD-810 is used to ensure operability of equipment in conditions it may come across during its service life. The standard provides a broad selection of environmental factors and tests to go with them, allowing companies to find any weak points and make the necessary changes. By following this standard, it will help to improve the reliability and robustness of their product, resulting in successful harsh environment operation and a longer life in the field.
Key Environmental Factors Tested under MIL-STD-810
Temperature: Equipment is exposed to a broad range of temperatures, from frigid cold to blazing hot, to make sure its performance and security are up to the task in different climates.
Humidity: Checking the humidity level helps to guard the device from harm and ensure it functions properly in areas with high levels of moisture.
Shock: Devices are tested by subjecting them to mechanical shocks, such as drops and vibrations, to replicate real-world conditions and to evaluate their structural soundness and operation.
Vibration: The MIL-STD-810 outlines a variety of different vibration tests to simulate any transportation or operational movements that may affect the performance or parts of a device.
Sand and Dust: The capability of the equipment to resist being exposed to tiny particles such as sand and dust that are commonly seen in desert and arid areas is appraised.
Altitude: Checking the equipment’s operation at various altitudes determines its capacity in different air pressures, guaranteeing its dependability in high-altitude zones.
Solar Radiation: Evaluating the equipment’s response to solar radiation helps manufacturers understand its performance in outdoor environments with direct sunlight exposure.
Rain: Devices are tested to withstand exposure to rain and water, preventing water intrusion and potential short circuits.
Impact on Industries
Military and Defense: MIL-STD-810 is mandatory for military and defense contractors. Ensuring equipment works well in harsh conditions is vital for military operations. Compliance reduces the risk of equipment failure in critical situations.
Aerospace and Aviation: The aerospace industry uses MIL-STD-810 to make equipment for aircraft and space missions. The standard makes sure that equipment can handle extremes in flight and space conditions.
Consumer Electronics: MIL-STD-810, originally intended for military use, has been embraced by consumer electronics producers. This has resulted in the production of rugged smartphones, tablets, and laptops for those with a fast-paced lifestyle or who do their work in demanding settings.
Industrial Equipment: Industrial equipment and machinery often must endure difficult conditions, such as those found at construction sites and mining operations. By following MIL-STD-810 guidelines, manufacturers are able to produce sturdy and resilient machinery that can endure these types of settings, reducing the need for maintenance and repairs.
The MIL-STD-810 is of major importance in the assurance of the quality and dependability of equipment across myriads of industries. By undergoing multiple environmental examinations, companies can notice and tackle possible problems before their equipment is delivered to customers and stakeholders. This guideline has not only ensured reliability of military devices but has also played a role in the construction and production of commercial electronics and industrial machines.
In a world where technology is more and more ubiquitous, MIL-STD-810 remains a fundamental point of reference in managing the difficulties of hostile and unpredictable environmental conditions. Its impact will remain, prompting manufacturers to construct reliable and rugged devices that meet the requirements of the DoD and commercial customers across the world.
How Can Jama Connect® Help?
Jama Connect®‘s digital engineering strategy is essential for any organization seeking to increase efficiency and reliability. It serves as an essential bridge between teams, optimizing design and engineering processes. With its comprehensive system view and dependable source of information, it is an invaluable asset for achieving success.
Note: This article was drafted with the aid of AI. Additional content, edits for accuracy, and industry expertise by Decoteau Wilkerson and Cary Bryczek.
https://www.jamasoftware.com/media/2023/08/2023-08-08-mil-std-810.png5121024Cary Bryczek/media/jama-logo-primary.svgCary Bryczek2023-08-10 03:00:332024-01-17 23:27:35MIL-STD-810: Ensuring Quality and Reliability in Challenging Defense Environments
In this video, we demonstrate the Baselines feature in Jama Connect®.
Jama Connect Features in Five: Baselines
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 under five minutes.
In this Features in Five video, Jama Software® subject matter expert Julie Goodner, Senior Product Manager, demonstrates Baseline capabilities in Jama Connect.
VIDEO TRANSCRIPT:
Julie Goodner: Hi. My name is Julie Goodner. I’m a Senior Product Manager here at Jama Software. In this video, I will walk you through Baselines in Jama Connect. I’ll cover what a Baseline source is, what Baselines are, when to create one, and some of our new Baseline features.
A Baseline source in Jama Connect is a collection of all versions of the requirements or other items that have been selected for a Baseline. A Baseline in Jama Connect is a snapshot in time and you can create a baseline to capture any milestone. In addition, a Baseline is also automatically captured when a review—or a revision to a review—is created.
A Baseline allows our users to capture the state of their content in alignment with key points in their product development cycle, such as during peer reviews, at key approval gates, or when generating documents from Jama Connect. In addition, utilizing Baselines allows our users to compare items as they change over time.
Goodner: With Baseline sources, you can see if the Baseline or Review contains signatures, see Baseline statuses, quickly navigate to a Review, or do a comparison summary between two Baselines and export the redlined report.
With Baselines, you can add electronic signatures, compare two Baselines with redline edits from within Jama Connect, compare items in your Baseline items to their current state in the project, add a status, and navigate to the Baseline version in the project view.
Goodner: From the Baseline source, you can see high-level information about its corresponding baselines that used to be hidden within a baseline details section. When selecting two Baselines, you can choose to do a comparison. This comparison summary model informs you have any updates that have been changed. You can also export that report and view the red line edit.
From a Baseline in the List View, you can see what relationships, categories, or other metadata were used to associate with the items at the time of the Baseline. When selecting the link in a Baseline, it will take you to the historical view from within the project.
From the Baseline Document View, you can choose to compare and see the differences in redline edit within Jama Connect, no longer needing to download reports.
If you would like to learn more about Jama Connect, how Jama Connect can optimize your product development process. Please visit our website at jamasoftware.com. If you’re already a Jama Connect customer and would like more information about Baselines, please contact your customer success manager or a Jama Software consultant.
https://www.jamasoftware.com/media/2023/07/FIF-Baselines-2.jpg10801920Julie Goodner/media/jama-logo-primary.svgJulie Goodner2023-08-04 03:00:282024-01-18 10:29:06Jama Connect® Features in Five: Baselines
In this blog, we discuss INCOSE’s System Engineering Handbook V5. To download this handbook, click HERE.
Empowering Engineers: Exploring INCOSE Systems Engineering Handbook V5
What is INCOSE?
The International Council on Systems Engineering (INCOSE) was founded as a collaborative effort to bring systems engineers together and provide them with resources to progress in their field. Their mission is to cultivate a strong network of professionals, supply educational materials, and create tools that will help systems engineers be successful. INCOSE is dedicated to elevating the global profile of the systems engineering (SE) profession.
According to INCOSE, the Systems Engineering Handbook “shows what each systems engineering process activity entails in the context of designing for affordability and performance. On some projects, a given activity may be performed very informally (e.g., on the back of an envelope, or in an engineer’s notebook); or, on other projects, a more formal response is required with interim products under formal configuration control.”
The handbook provides assistance for individuals of various backgrounds and experience levels, such as those just beginning their systems engineering journey, engineers from different disciplines needing to apply the principles of systems engineering, and experienced engineers looking for a handy reference.
INCOSE Systems Engineering Handbook V5
The newly released INCOSE Systems Engineering Handbook V5 is a comprehensive guide to the discipline of SE which outlines the current best practices and serves as an informative reference for understanding SE in terms of content and application.
Some of the topics included in the latest handbook include:
Elaboration on the key systems life cycle processes described in ISO/IEC/IEEE 15288:2023;
Chapters covering key systems engineering concepts, system lifecycle processes and methods, tailoring and application considerations, systems engineering in practice; and
Appendices, including an N2 diagram of the systems engineering processes and a detailed topical index.
Applying INCOSE Standards Using Jama Connect Advisor™
System engineers focus on making each of the individual systems work together into an integrated whole that performs as expected across the lifecycle of the product. In order to deliver successful products, they need the right user needs and requirements. Efficient, precise, and professionally written requirements form the foundation of the product development process so that various teams (design, software, and hardware systems) can all work together with a shared and clear understanding of the project goals.
Jama Connect Advisor™ is a state-of-the-art requirements authoring guide and optimizer powered by natural language processing for engineering that helps a system engineer or a product developer write effective, well-organized requirement specifications based on industry-accepted INCOSE rules and the EARS (Easy Approach to Requirements Syntax) notation.
In part two of this two-part video series, will demonstrate the latest solution offerings for Medical Device & Life Sciences in Jama Connect®. Click HERE for part 1 and HERE to watch our related and full-length webinar, “Elevating Your Medical Device and Life Sciences Product Development Processes with Jama Connect.”
Jama Connect Features in Five: Medical Device & Life Sciences Solution 2.0 – Part 2
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 under five minutes.
In part two of this two-part Features in Five video series, Jama Software® subject matter expert Vincent Balgos, Director, Medical Device Solutions, continues his demonstration of the latest solution offerings for Medical Device & Life Sciences in Jama Connect.
Click HERE for part 1 and HERE to watch our related and full-length webinar, “Elevating Your Medical Device and Life Sciences Product Development Processes with Jama Connect.”
VIDEO TRANSCRIPT:
Vincent Balgos: Hi. My name is Vincent Balgos, and I’m the Director of Medical Solutions here at Jama Software. In this video, I’m going to talk about our updates to our Medical Device and Life Sciences Solution 2.0. For the agenda, there are quite a few improvements I’d like to share with you today.
So the first thing I want to show is our Jama Connect Advisor™ example data. Released in 8.80, this new feature enables EARS and INCOSE rules for requirement quality authoring. Additional licenses are required, but wanted to share some of the capabilities examples right out of the box. So as you can see here, what we’ve shown, is, you know, the general use case description, but also an example requirement with the Jama Connect Advisor output. Again, this is a nonfunctional screenshot. We just wanted to share some of the information that you may see when having Jama Connect Advisor. Here’s, for example, for a green status, which means generally a good requirement, but let’s take a look at what a yellow requirement or maybe something that may need some rework and you can see which of the rules, particularly INCOSE, that is now flagged that is, you know, has some potential issues. And then the same is true with our red level of requirements.
So again this is potentially a useful tool to kind of share while authoring requirements for your project.
Balgos: The next use case that we’d like to talk about is the industry standards trace. So in the standards use case, the first thing I want to share is this relationship rule diagram. As you can see here, we have user needs trace to system requirements, which is, you know, aligns with [21 CFR] 820.30, but also we have this new item type called standards reviewed is now traced to system requirements.
If you upload your standards into Jama Connect, what we can see for this particular item type is that we’ve identified now the standard, the clause number, the clause text, and identified does the standard apply for this particular project. What’s nice about once this is in Jama Connect, I can now actually do a trace downstream to the system requirement. Note, this project does not provide any standards due copyright issues, customers won’t need to vision their own standards for use and apply appropriately. The last thing we want to talk about is really the reports on this medical device framework update.
Balgos: What I wanted to share is if I go into the admin area and I take a look at the reports, you can see now that we’ve now had the ability to upload and, you know, manage our own reports, but we’ve provided some additional categories and information to help organize the many reports that we have. As you can see here, we’ve identified some trace reports and some new SaMD reports. So if I go back to the project and let’s take a look at, let’s say, system requirements, I want to show you a new trace report that shows requirements to verification-only events. So for example, let’s say if we go on to, let’s say, our subsystem requirements that we have here I’m gonna pick this one.
I’m going ahead and go at export. Again, this is available now into the Medical Device Framework 2.0. What I want to show you is requirements to verification trace report. So if I go ahead and hit run, create a report, I’m gonna download it, and then what wanna share is this new trace report that we have, which now shows you the requirement, the verification test case associated with the requirement, But in addition, the latest test run and its test result status.
Balgos: So this helps clearly identify the requirement to verification traceability that’s may needed and they may be able to submit to your DHS. We have a similar one called the user needs to validation transport that falls the same above. The other thing we wanted to show is that we’ve added a couple popular and useful GitHub reports to this solution update. These are located up in our run reports area where we actually now included the test results report group by test case and the test result report grouped by test cycles, which are really, really helpful for understanding test management scenarios.
Okay. That’s for the general update for the the standard medical device framework. We have an additional updated solutions such as software as a medical device, research use only, and our new self-guided onboarding framework. So we definitely encourage you to look at that further.
Please contact your Jama success manager or consultant to learn how to implement these new solutions at your organization.
https://www.jamasoftware.com/media/2023/07/FIF-Framework-3.jpg10801920Vincent Balgos/media/jama-logo-primary.svgVincent Balgos2023-07-28 03:00:022024-01-17 23:39:01Jama Connect® Features in Five: Medical Device & Life Sciences Solution 2.0 – Part 2
In this blog, we recap our webinar, “Effectively Managing Cybersecurity in Jama Connect® for Automotive and Semiconductor Industries”. Click HERE to watch the entire thing.
If you’re in the automotive or semiconductor industries – cybersecurity is likely top of mind.
In this webinar, attendees will see exactly how to:
Define cybersecurity goals, requirements, and concepts
Conduct threat analysis and risk assessment
Establish traceability to the architecture design and verification/validation of cybersecurity measures
Document the cybersecurity case and manage changes
Identify and classify assets for the subject of the cybersecurity case
Discover how Jama Connect can help you optimize your cybersecurity processes and stay ahead in the Automotive and Semiconductor industries.
Below is an abbreviated transcript of our webinar.
Effectively Managing Cybersecurity in Jama Connect® for Automotive and Semiconductor Industries
Kevin Dibble: Well, first I’m going to talk about what we’re going to talk about, so these are the topics that we’re going to cover. And without reading this slide, really we’re going to cover the development life cycle of creating, the example we’re going to use is a 48-volt power assist system. You might also think of it as a battery management system. And so I’ll go over the agenda, but what you can see on the is we’re going to cover everything from the planning in the case through the TARA work and down through the left side of the V and some of the right side of the V activities as well. And here’s how we’re going to do it. First, to get everyone oriented to 21434, we’re going to talk about the standard itself briefly and highlight some of the benefits of implementing a cybersecurity case in a tool, in a requirement management tool.
Then we’ve got some workflows to look at, the steps of the development life cycle for 21434 from the perspective of an OEM and then again from the perspective of a tier one. And then Matt is going to show the work products, the traceability, and what we’ve talked about at the beginning actually in the tool in a built-out project for a 40 volt power assist system. And then we’ll finish with some takeaways. So that’s what’s on tap for today. And so I want to make the case for managing cybersecurity and the cybersecurity case and the work products in a requirements management tool. So I’m going to just look at each one of these points. The first item is to improve collaboration between OEMs, tier ones, and tier twos.
Jama Connect supports ReqIF, which can be used for bidirectional communication of requirements, item definitions, et cetera, as well as updates to those assets. And so it supports better collaboration. One thing that Jama promotes is this idea of trace as you go. So traceability is not an afterthought handled by a requirement engineer at the end of the project that takes weeks to implement on a complex project. It’s something that the engineers are doing as they’re creating the requirements tracing to parent requirements, design blocks for requirement allocation, et cetera. And so this tool supports that traces you go methodology along with some views of the progress of tracing.
Dibble: The impact analysis is a powerful tool when you trace as you go and the requirements left and right side V model assets are linked together. Then running impact analysis reports as changes come in midstream in programs, which they do in automotive for sure. You get that as a benefit. Like I mentioned earlier, requirements allocation. So allocating requirements to design blocks or interconnecting the requirement management system to design tools and doing allocation in those tools like Design Architect gives you some powerful analytics like test coverage reports automatically generated. Also connecting the tools through connectors gives you a toolchain view instead of disjointed tool. And finally, Jama Connect offers some analytics that we’ll see some of these in the demo that will give you a very clear indication of where you are in the project, especially in terms of requirements that are allocated, tests that have been covering requirements, and so on and so forth.
So with that, I’m going to orient everybody to 21434 in terms of the V model, which it’s centered on, and two other standards that you may be more familiar with. ISO 26262 and Automotive ASPICE. And so just a couple things here. If you are familiar with these other two standards, you’ll see that 21434 fits nicely alongside and that was intended by the ISO folks that did the standard. They very much aligned it with ISO 26262, and really even in nomenclature. So whereas in safety we have safety goals, in security we have security goals, in safety, we have the HARA, the hazard and risk assessment. In cybersecurity, we have the TARA, threat, and risk assessment, and so on and so forth. And also the common supporting processes like configuration management, change management, project management, document management, even confidence in use of software tools that all of these standards rely on are again repeated and required in 21434.
Dibble: So just some basic organization of the standard in terms of the V model and then we’ll look at it in one more view in terms… this is directly out of ISO. And at Jama, we’ve added some color coding and I’m going to explain that. And so if you’re not familiar with this view, 21434 is oriented by clauses and sub-clauses. And so you can see the clause here like clause five is organizational, that’s policy and tool management and quality management and things. And then clause six, et cetera, and on down, that’s how this is organized. Jama has capabilities that support these sub-clauses. And so we’ve used a color system here to highlight that. The sub-clauses that are colored in green are fully supported and in fact, recommended to implement in Jama. The yellow are optional, they could be implemented in Jama.
And for most of these, we have customers that are implementing these types of things in Jama, but they also use other systems to implement them. And then this kind of yellow-green is partially supported. Jama can support some of the requirements but not all. And then of course red is not recommended for support in Jama and it’s usually house and other tools or things like production tools, et cetera. Okay, so what Jama brings to the table in terms of capabilities to support these green and yellow items are document building and generation. So the document management functionality as well as the exporting functionality. As you’ll see in the demo, you can export what has been entered in a requirements tree or in one view can be exported into a more of a document-style view that perhaps suppliers or other people might want to consume.
It has built-in collaboration tools for reviewing, which is very important because 21434, like 26262 requires review records, and all the work products are reviewed. Traceability and impact analysis, I already talked about. VNV verification and validation with the test manager tool as well as interconnections to other tools and analytics. There’s a nice support for the right side of the V activities. Using a common tool does bring alignment between different engineering disciplines, whether it’s hardware, software in systems, or if it’s QA tests and V&V activities versus development activities. Release planning and coverage through dashboards and status metrics and then of course baselining and reuse and whatnot.
And so this slide shows all of the items from the previous slide that were recommended or are optional and just shows how they would look in a project tree format. Again, Matt’s going to go through most of these items for our 48-volt power assist item that we’ve built out. Okay, one of the important features of Jama Connect as well as any requirement management tool is the ability to develop traceability. Here we’re showing the traceability model, which is their traceability models come with the product, but they also can be customized. And then I’ve got a little animation here to show for cybersecurity, some of those standard parts and tying them back to the standard. So for instance, in the model, I don’t know, it’s small print, but you can probably see cybersecurity asset, attack path, damage scenario, threat scenario. Those all correspond to the TARA and here are the sections that those are discussed in.
https://www.jamasoftware.com/media/2023/07/2023-Webinar-Recap-Med-Update-1.png5121024Matt Mickle/media/jama-logo-primary.svgMatt Mickle2023-07-27 03:00:362024-01-17 23:43:04[Webinar Recap] Effectively Managing Cybersecurity in Jama Connect® for Automotive and Semiconductor Industries
In part two of this two-part blog series, we continue the overview of our recent whitepaper, “How to Achieve Higher Levels of the Capability Maturity Model Integration (CMMI) with Live Traceability™” Click HERE for part one of this blog and HERE to read the entire whitepaper.
How to Achieve Higher Levels of the Capability Maturity Model Integration (CMMI): Part 2
Benefits of Live Traceability™
The main benefits of Live Traceability across best-of-breed tools are as follows:
Reduce the risk of delays, cost overruns, rework, defects, and recalls with early detection of issues through exception management and save 40 to 110 times the cost of issues identified late in the process.
Achieve CMMI Level 2 maturity for Requirements Management with no after-the-fact manual effort.
Eliminate disruption to engineering teams that continue working in their chosen best-of-breed tools with no need to change tools, fields, values or processes.
Increase productivity and satisfaction of engineers with the confidence that they are always working on the latest version, reflective of all changes and comments.
Another core goal of CMMI Level 2 is to involve stakeholders in the requirement review and approval process (see table below). Let’s examine how companies achieve this goal either through meetings or online reviews.
CMMI Level 2 (Managed) Requirements Management
There are two ways to implement this practice: meetings or online reviews. Most engineering organizations still address stakeholder approvals through large and lengthy meetings that involve all relevant engineering disciplines scrolling through the requirements document for feedback. This is a highly inefficient approach that negatively impacts engineering productivity, morale and fails to capture relevant comments, feedback, revisions, and approvals from stakeholders given the format. More mature engineering organizations have brought the review and approval process online to improve the quality and timeliness of feedback, capture all version and approval histories online, and improve engineer productivity and morale. Let’s examine how companies have brought reviews online with Jama Connect® Review Center.
Review Center allows teams to send product requirements for review, define what’s required, invite relevant stakeholders to participate, collaborate, and iterate on resolving issues and approving agreed-upon requirements. By simplifying the revision and approval process, Review Center streamlines reviews and facilitates collaboration, giving stakeholders easy access to provide feedback where required. Jama Connect enables both informal and formal online review processes to support this CMMI best practice.
The formal review process enabled by Review Center is shown below:
Review Center enables teams to define a review, invite participants, gather and incorporate feedback from relevant project stakeholders, iterate, track a review’s overall progress, and monitor progress and capture approval signatures if required. Reviewers can respond to a conversation that’s taking place, as well as mark items as “Approved” or “Rejected” to complete the review. Inside Review Center, reviewers can also add electronic signatures to reviews in order to comply with regulatory standards. Jama Connect captures the date and time of completed reviews for auditing, tying each signature to the document under review.
Informal Reviews
Organizations that still want the quality review aspects of Jama Connect but are not bound by producing formal documents of requirements may take a more iterative approach. A “rolling” review is a review that changes the scope of which requirements are included in each revision. For example, each requirement has a “state” field – Draft, Ready for Review, or Approved. In the project side of Jama Connect, requirement owners will mark requirements they feel are “Ready for Review.” Moderators can also edit requirements directly in the review based on feedback from Approvers. Using a Jama Connect Advanced Filter, a review will be started by pulling in only requirements that are marked “Ready for Review.” Using this methodology, the review is much smaller in scope and can typically be completed faster. On a regular cadence, the moderator will review feedback, make changes to requirements as necessary, or potentially update the requirement status to “Approved” if the required stakeholders have approved the requirement. When publishing a new revision, Jama Connect will pull new requirements into the review and cycle out requirements that are “Approved” (these requirements no longer meet the filter criteria of state = “Ready for Review”). This allows teams to review requirements on a regular cadence — or sprint — and cycle requirements into the review when they are ready for feedback and out of the review when they are “Approved.” Almost any item of content you create in Jama Connect may be sent for a review, including requirements, design, test cases, test plans, and test cycle results.
“Review Center is facilitating communication. It has ensured a shared view of the world and agreement from all stakeholders. There are no surprises anymore. Jama Connect enables us to review documents and make decisions easily with everyone coming to a shared conclusion. If we compare it to reviewing the spreadsheets and Word documents versus doing a review in Jama Connect Review Center, it’s about an 80% reduction in time, for sure.” – Craig Grocott, Head of Systems Engineering
To achieve CMMI Level 2 requires defining a development process and adhering to it. Below is a core goal for CMMI Level 2 – evaluate adherence to requirements management process.
CMMI Level 2 (Managed) Requirements Management
Achieving this goal requires the ability to decompose requirements across engineering disciplines and maintain traceability up and downstream as the project progresses with significant changes and rework. Without an underlying system architecture and common data model, this goal becomes unattainable for most organizations. Attempts to manage through Word and Excel, become unwieldy and unable to meet the requirements for Live Traceability, leading to defects, delays, cost-overruns, and recalls. Below, you can see how easy it is to manage traceability and view up and downstream multiple levels in a trace view of requirements in Jama Connect. Jama Connect’s Traceability Model defines the data model across best-of-breed tools to capture actual behavior for traceability and management by exception.
To achieve CMMI Level 3 requires defining a development process and adhering to it. Below is a core goal for CMMI Level 3 – establishing a verification process and adhering to it.
CMMI Level 3 (Defined) Verification
Companies are achieving this goal through Jama Connect by establishing a Traceability Model that requires test verification for requirements and managing by exception through dashboard reporting to ensure verification happens across all requirements. Below is a sample verification dashboard to achieve this goal with customer-specific info redacted. Here you can see how the Verification Leader manages their function through exception management. Specific widgets on the dashboard track requirements without tests, failed tests, tests without requirements linked to verify, bugs without tests, and risks without upstream or downstream traceability. The Traceability Model established in Jama Connect defines the expected behavior against which all activity can be compared to generate exceptions that can be managed through the dashboard. Without this system architecture and data model, managing by exception becomes extremely manual and productivity killing, if not impossible.
CMMI Level 4 requires organizations to have developed predictive scores and benchmarks that enable management to identify product development risk early and remediate at much lower cost than if not identified until late in the development process or after product release into the market. The table below shows the definition of this core, Level 4 goal.
CMMI Level 4 (Quantitatively Managed) Process Performance
Leading companies are achieving this goal by applying Jama Software’s Traceability Score™ and benchmarking engineering projects internally and externally against peer companies. Jama Software is the first to measure traceability thanks to our clients’ participation in a benchmarking dataset of over 40,000 complex product development projects spanning aerospace, automotive, consumer electronics, industrial, medical device, semiconductor, space systems, and more. All of this is made possible by our core product, Jama Connect®, which enables the largest community of engineers using requirements management SaaS (Software as a Service) in the world.
To formally measure traceability, we have established the Traceability Score. The Traceability Score measures the level of actual process adherence to the expected traceability model and can be used to compare performance across projects, teams, divisions, and companies. This score can also determine impacts to schedule, budget, cycle times, risk, and quality.
Traceability Score = # of established relationships among model elements as specified by the project’s traceability model.
The following diagram provides an illustration for the buildup of the calculation:
At the individual requirement level, we can identify each expected relationship defined in a project’s traceability model (i.e., user needs defined by requirements, further refined by sub requirements, and test cases that should verify the requirement, etc.). We can then identify how many of these relationships have been established to get an individual requirement’s traceability.
As we go one level higher and measure traceability within a particular element type (e.g., user needs, requirements, tests, etc.) we can sum up the number of expected and established relationships across the set of items, giving us traceability at the element type level.
Finally, we can sum up the number of expected and established relationships across all element types, giving us the project’s total Traceability.
Correlations & Hypothesis Test Results
As a process management tool, the value of a Traceability Score is to quantify actual adherence to the specified approach. To determine best practices from the data, statistical tests were run to understand how differing levels of project adherence to Live Traceability can impact desired outcomes. As we have shown, the Traceability Score measures actual adherence to the defined traceability model. The systems engineering discipline, the V model, quality engineering, and more – all rely on the intuition that this approach will yield better results. Anecdotal evidence abounds to support this intuition, but the dataset has been lacking to conduct statistical tests to test this hypothesis. Using our dataset, we were able to determine that Traceability Scores exhibit statistically significant correlations to the following outcomes and rejected the null hypothesis that these correlations were purely random.
1. Faster time to market
The first three tests focus on how Traceability Scores impact cycle time. Do higher Traceability Scores lead to faster test case execution and defect identification? This is a fundamental value asserted by systems engineering and the V-Model – that earlier detection of defects leads to fewer delays and much lower cost to correct. We measured the following times below and noted performance improvements in top versus bottom performers of 2.1X to 5.3X. Higher Traceability scores were found to lead to faster test case execution and defect detection having passed both of our statistical tests.
Median Time to Execute Test Cases (2.6X faster)
Median Time from Test Start to Defect Detection (5.3X faster)
Median Time to Identify the Set of Defects (2.1X faster)
2. Higher quality
The last three tests focus on how Traceability Scores impact quality. Do higher Traceability Scores lead to a higher quality product? This is a fundamental value asserted by systems engineering and the V-Model – that a commitment to test case creation and execution leads to a higher degree of requirement verification and product quality. We measured the following aspects of testing and verification below and noted performance improvements in top versus bottom performers of 1.9X to 2.9X. Higher Traceability scores, having passed both of our statistical tests, led to more tests being completed and a higher percentage of passed tests.
Percent of Requirements with Verification Coverage (1.9X higher)
Percent of Requirements Verified (2.1X higher)
Initial Test Case Failure Rate (2.4X lower)
Final Test Case Failure Rate (2.9X lower)
Conclusion
The CMMI defines its best practices in terms of goals, practices, and artifacts. The CMMI does not address the underlying systems and data architecture required to enable these practices, deliver these artifacts, and achieve these goals. The systems architecture reality for most engineering organizations is highly fragmented with the necessary data to manage the engineering product and process (user needs, system level requirements, approvals, component level requirements, model designs, component requirement decompositions, interface definitions, test cases, test results, risk analysis, validations, traceability analysis, etc.) spread across hundreds of siloed tools, spreadsheets, emails, and chat tools with high degrees of uncertainty that any information reflects the latest version continually updated with all interdependencies.
As we have shown, it is extremely challenging if not impossible to move up the CMMI maturity model without addressing the underlying systems architecture and data model. Carnegie Mellon has chosen to use our software to train their students and leading companies have deployed Jama Connect in the ways noted above to achieve their CMMI objectives.
This has been part two of a two-part blog series overviewing our recent whitepaper, “How to Achieve Higher Levels of the Capability Maturity Model Integration (CMMI) with Live Traceability™” Click HERE to read the entire thing.
https://www.jamasoftware.com/media/2023/07/2023-07-25-cmmi-part2.jpg5121024Marc Osofsky/media/jama-logo-primary.svgMarc Osofsky2023-07-25 03:00:532024-01-17 23:46:09How to Achieve Higher Levels of the Capability Maturity Model Integration (CMMI): Part 2
![[Webinar Recap] Manage by Exception: Data-driven Practices to Improve Product Quality](https://www.jamasoftware.com/media/2023/08/2023-Webinar-Recap-Med-Update-4.png "[Webinar Recap] Manage by Exception: Data-driven Practices to Improve Product Quality")
![[Webinar Recap] Effectively Managing Cybersecurity in Jama Connect® for Automotive and Semiconductor Industries](https://www.jamasoftware.com/media/2023/07/2023-Webinar-Recap-Med-Update-1.png "[Webinar Recap] Effectively Managing Cybersecurity in Jama Connect® for Automotive and Semiconductor Industries")
In part two of this two-part blog series, we continue the overview of our recent whitepaper, “How to Achieve Higher Levels of the Capability Maturity Model Integration (CMMI) with Live Traceability™” Click 
