Tag Archive for: Jama Connect Platform

Jama Connect® Features in Five: Jira Integration

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 Integration Series video, Mario Maldari – Director, Solutions Architecture at Jama Software® – will demonstrate the Jama Connect® to Jira® integration.


Mario Maldari: Hello and welcome to the Features in Five Integration Series. My name is Mario Maldari and I’m the Director of Solution Architecture here at Jama Software. Today, we’ll be walking through the Jama Connect to Jira integration. We make it possible for you to integrate Jama Connect with preferred best-of-breed software to achieve Live Traceability™ across the end-to-end development cycle. Live requirements traceability is the ability for any engineer at any time to see the most up-to-date and complete upstream and downstream information for any requirement, no matter the stage of systems development or how many siloed tools and teams it spans. This enables significant productivity and quality improvements, dramatically reduces the risk of product delays, cost overruns, defects, rework, and recalls, and ultimately results in faster time to market. Let’s get started.

The Jama Connect to Jira integration allows for bidirectional synchronization of data between requirements and tasks. This allows for teams such as software developers to stay in their tool of choice and enjoy the benefit of real-time updates between the two applications. Today, we’ll be covering two core use cases for the integration. We’ll be creating a defect in Jama Connect that will synchronize to Jira, and then we’ll be creating an epic in Jira that’ll synchronize over to Jama Connect. Let’s start by executing a test case at Jama Connect’s Test Center. Let’s start our test run here and we can go through and pass or fail steps accordingly. We get to an issue, we can log a defect right from the test, and we can set things like priority. Go ahead and save that defect. And we can go ahead and save and close this test.

RELATED: How to Achieve Live Traceability™ with Jira® for Software Development Teams

Maldari: Then we can open up the test record here and we can take a look at the relationships. And as expected, we will see a link to a downstream defect that we just created. Let’s take a look and open up that defect. And we can see there’s an integration URL to the corresponding defect over in Jira that was just created. And as a developer, I can see a new defect came in and I can start to work on this defect. I can also change things like priority. I can also add a comment. Any field that’s set up to participate in the integration, such as name, description, comments, priority, all of these things can be modified from Jira and that will be synchronized over into Jama Connect. And now you’ll see that there’s a Jama Connect URL here, and this will take us back to the defect that we just created in Jama Connect.

And we can see that the priority has been set below. We can see that there’s a comment that’s been added to add an attachment, and we can actually go ahead and add an attachment here, a picture of our cracked camera. And we’ll attach that to the item. So conversely, anything in Jama Connect that’s participating in the integration, any field, name, description, priority, all of these changes from the Jama Connect side will also be reflected over on the Jira side. And so if we navigate back over into the Jira defect, we’ll do that by following this URL here, we can see that our attachment came over onto the Jira defect.

Similarly, if we’re in Jira now, we’re working and we want to create an epic, we can go ahead and create an epic. Usability improvement, we can go ahead and create that. And then let’s take a look at that epic that we just created here. Similar to the defect scenario, any field that’s set up and configured in the integration will synchronize between the two applications, and that includes the name, description again, comments, and priority. Any field that’s configured will sync over. Then if I refresh this epic that I just created, you can see now that there’s a Jama Connect URL to the correspondent epic that’s just been created in Jama Connect. So I can go here into Jama Connect and I can add things like tables and further elaborate the description, and ask the development team to fill out the table for me.

RELATED: FORT Robotics Selects Jama Connect® to Replace Google Sheets for Product Development

Maldari: But more importantly, what I can do is start to establish traceability within Jama Connect now. Assuming maybe this usability improvement request came from a particular customer, I can link it to an upstream requirement, or initiative, in this case, usability improvement from the customer. And so I can start to establish traceability now, now that it’s in Jama Connect. All the work is being done in Jira on this epic, but the traceability is being established within Jama Connect. So I’m always getting the latest changes over from the Jira side participating in my traceability within Jama Connect. Let’s take a look back over to the epic in Jira, and we can see the table that I just added from Jama Connect showing up here. You can even see that there’s now an upstream link reference that gives me a reference to the traceability that I just created on the Jama Connect side.

So as you can see, the integration allows teams such as software developers to work in Jira while allowing for real-time status updates to flow over to Jama Connect and be reflected in various traceability views. This way, teams are guaranteed to have the latest status on their projects. Thank you for watching this Future in Five session on the Jira integration for Jama Connect. If you’re an existing customer and want to learn more, please reach out to your customer success manager or consultant. If you’re not yet a client, please go to our website at jamasoftware.com to learn more about the platform and how we can help optimize your development process.

The ‘Square Root’-Process Model for System Engineering

In the rapidly evolving field of systems engineering, the traditional V-model has served as the cornerstone for development, defining system requirements and verification processes. However, the demands of modern engineering necessitate an extension of the V-Model to reduce time-to-market and elevate customer satisfaction. This article introduces the ‘square root’ model that extends the V-model that embeds continuous feedback and integration throughout the product lifecycle. By considering production, operation, support, and end-of-life sustainability from inception, the ‘square root’ model, visually represented in the accompanying diagram, ensures that engineering efforts align with practical constraints and market needs.

Leveraging Jama Connect®‘s advanced features, we will explore how this model fosters collaboration, efficiency, and strategic foresight, setting a new standard for systems engineering excellence.

Throughout this article, when ‘product’ is mentioned, understand that it can also refer to a service, software, or system.

There are aspects in engineering and feedback loops that the V-model implies to improve the engineering assets (mainly Verification and Validation focused) at the same information abstraction level; This article will describe the need to extend the traditional V-model to ensure the estimated time-to-market can be met with ease, customer satisfaction improves each product iteration and create a better tomorrow, using Jama Connect unique features to support your engineering teams to achieve these results.

Where the traditional V-model, starting at ‘Stakeholder Requirements’ and ending at ‘Acceptance Tests’ (or ‘Validation’), describes the engineering’s team involvement in the product being engineered, it is important to understand that this is only a small part in the entire lifecycle of a product. It’s the repeatable part for that product’s new releases and it’s the part that can be used to analyze the impact of changes before that change gets implemented in production.

RELATED: A Path to Model-Based Systems Engineering (MBSE) with Jama Connect®

Design Constraints

The word “constraint” has a negative connotation; Design constraints are limitations on what designers can do with a design. These limitations are usually byproducts of having deadlines, budgets, brand guidelines (and similar guidelines, see below), laws and regulations, finite resources, and limited decision power in terms of tools and processes.

Some product engineers view design constraints in a bad light because they feel like they’re being boxed in by a brick wall, while others embrace design constraints as directional guidelines that open the doors to creativity and strategic problem-solving.

On the surface, having design constraints can indeed feel like a bad thing; however, they can be extremely useful. Being limited to certain choices doesn’t necessarily mean being limited to certain outcomes. Often enough there are alternative options that are, at least, almost as good as what you originally envisioned.

Design constraints can come from various sources, in this article we’ll talk about the constraints that focus on time-to-market, customer satisfaction, and zero waste. In other words, design guidelines come from:

  • Production;
  • Operation and Support;
  • (Ecological) Sustainability; the recycling of your product’s used materials.

These design constraints facilitate engineering with the end in mind. Your team’s early decisions during product definition must include upgradability, serviceability, and for sure: disposal, and sustainability.

Please Note: As these are complex topics by themself and not part of the core business of Jama Software, this article will only emphasize the need for feedback from these product lifecycle phases into the product definition as design constraints. Design constraints might also be known and used as Non-functional Requirements (i.e., the different ‘-bilities’, like producibility, serviceability, etc.)

Production and Manufacturing

When production and manufacturing aren’t involved from the start, your engineering team might waste valuable engineering time and effort on a product that cannot be manufactured with the means your production facilities have at their disposal. This means that the product’s entire time-to-market will need to be extended to re-engineer the product to your current production capabilities; wasting precious time and putting your competitive edge at an unnecessary risk.

As an example, a Printed Circuit Board (PCB) might require that a set of components must be aligned in the same direction and at a specified distance when wave soldered to avoid short-circuits in operation. These wave soldering characteristics can be recorded and maintained in Jama Connect as Design Constraints. Source: https://www.mclpcb.com/blog/wave-soldering-issues/

The other side of this same coin; By knowing what your production facilities can and cannot do at the start of the product definition, your teams are capable of estimating when the new bleeding-/leading-edge product they are developing needs new production means.

These insights, when considered at the beginning of the product definition, will allow your teams to research, develop, and implement the required new production techniques and have them ready when the product hits the factory shop floor. This includes having purchasing ready with new suppliers, their delivery times, required stock levels, and other input required for your factory shop floor to hit the ground running producing your new product when it completes its V-cycle.

Operation and Support

The full value of a system or product is realized in its use and operation during the expected product lifespan. Your customers want to receive a product that meets their expectations, but those expectations extend beyond a product that works on day one. Customer Satisfaction, and thus Customer Lifetime Value, is heavily influenced by the ease and availability of maintenance, servicing, and upgrades that will extend the product’s lifespan. When a customer calculates Return on Investment (ROI), they are not only considering receiving a working product, but they are also factoring in;

  • Mean Time Between Failures (MTBF, a metric for failures in repairable systems);
  • Mean Time to Failure (MTTF, a failures that require system replacement);
  • Mean Time to Repair/Recovery/Respond/Resolve (MTTR, is the average time it takes to repair/recover/respond/resolve a failure in a product, service or system, usually technical or mechanical. It includes both the repair time and any testing time. The clock doesn’t stop on this metric until the system is fully functional again); and
  • Mean Time to Acknowledge (MTTA, a metric useful for tracking your team’s responsiveness and your alert system’s effectiveness).

Reliability represent a series of metrics designed to help customers understand how often incidents occur and how quickly they, in collaboration with your Operation and Support, bounces back from those incidents. Valuable indicators to determine if their investment, and any additional investment to keep it operational, is effective.

Analysis of these reliability, MBTF, MTTF, MTTR and MTTA metrics focused on means to reduce these indicators, lead to product enhancements that improve customer satisfaction for both users (better uptime, improved performance, etc.) and decision makers (value on their investment).

E.g., the accessibility of a repairable component, to improve the MBTF, can be recorded and maintained in Jama Connect as a design constraint.


For sustainability, it all starts with the design. The design decisions for the product contribute 80% to the carbon footprint of the solution! How to make your products and systems ‘green’ from the start, a topic most companies struggle with.

Once your teams start to include sustainability in your product’s mission, you’ll need a structured approach, as several factors will push for different considerations. The most obvious considerations are the choice of materials and the optimizing the production process (reducing carbon emissions).

However, the repairability/serviceability of the product should be considered with a more extended lifetime vision, just like upgradeability and reusing components.

Techniques like Lifecycle Analysis (LCA, shows how much influence a product has on the environment during its entire life cycle: from raw material extraction to waste processing) exist to determine the Design Constraints necessary for the sustainability of the product being developed.

The (material) considerations that come out of an LCA (e.g. switch from fossil fuels to hydrogen) can be recorded and maintained in Jama Connect as a design constraints.

Jama Connect supports the ‘square root’-model

Collaborate with stakeholders from Production, Operation & Support and Environment, Health & Safety

Recording design constraints is not unique to a (Requirements Management, or Product Definition) application like Jama Connect; The ability to collaborate with colleagues in reviews, from the respective product lifecycle phases that normally don’t have to deal with the product definition phase (and thus don’t work in Jama Connect) is unique.

This unique feature allows your teams to engineer your products with the end result in mind, by involving the stakeholders from beyond their own engineering reach, to collaborate and achieve the optimum time-to-market, best customer satisfaction and create a better tomorrow for ourselves and future generations.

These stakeholders don’t require to be Jama Connect users to be invited and collaborate in a review within Jama Connect. Involving those stakeholders into the review process allows these stakeholders to verify their design constraints are adequately and sufficiently addressed by the requirements of your product definition.

RELATED: The Benefits of Jama Connect®: Supercharge Your Systems Development and Engineering Process

First step in sustainability; reuse as much as possible

Not only does reusing and synchronizing requirements reduce your time-to-market and improve quality, but it is also a key strategy for getting your products sustainable. Jama Connect can help reducing the struggle to build on existing work when requirements, and their corresponding test cases, are spread across documents and systems, missing Live Traceability™. Your teams 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 reused 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 container and its traced items. Synchronization ensures visibility and enables key use cases such as parallel product definitions, common content libraries (i.e. reusable component libraries) and product variants.

Further reading
  • INCOSE (International Council on Systems Engineering): INCOSE is a professional organization dedicated to promoting and advancing the field of systems engineering. Their website (www.incose.org) offers a wealth of resources, including publications, articles, and conferences, that cover various topics in systems engineering, including the V-Model.
Other sources used

Empowering Customer Success: The Vital Role of Support and User Communities

Our customers are at the forefront of everything we do. From product roadmaps to website redesigns, all the way to new customer success offerings, we’re listening to our customers and constantly adapting to meet their needs.

One successful way we’ve done so is by establishing a robust user community. In this blog post, we’ll look at our Jama Software® user community, provide a sneak peek at our upcoming community migration, and showcase our new and highly-rated support site. Let’s get started!

What is a customer community and why is it significant?

A customer community is an online platform where customers can interact with each other and a company. Having a customer community is crucial for improving customer satisfaction, fostering engagement and loyalty, promoting innovation, and collecting valuable feedback. It is a vital aspect of contemporary customer experience strategies that helps companies build stronger relationships with their customers, leading to various business advantages.

How does Jama Software user community engagement strengthen the customer experience?

The primary goals of our user community are: to increase engagement with our customers and partners; strengthen the customer experience by enabling support, collaboration, learning, and feedback mechanisms; help users get the most value from the Jama Connect® platform; and foster community and partnership with the company as a whole.

Member of our online community have access to:

  • Peer Support: Jama Software’s online community provides users a platform to connect with peers who may have faced similar challenges or have expertise in specific areas. This peer-to-peer support mechanism allows users to seek advice, share best practices, and troubleshoot issues more effectively, ultimately leading to a smoother experience with the software.
  • Direct Access to Subject Matter Experts: By engaging with the online community, users can directly interact with Jama Software experts, including community managers, support staff, product managers, and consultants. This direct line of communication enables users to receive timely assistance, clarifications on features or functionalities, and insights into the product, enhancing and optimizing their understanding and usage of the software.
  • Feedback and Feature Requests: The online community is a valuable channel for users to provide feedback on their experiences with Jama Software and suggest enhancements or new features they want. By actively listening to customer feedback, Jama Software demonstrates its commitment to continuously improving its products to better meet user needs.
  • Learning and Knowledge Sharing: Jama Software’s online community allows users to access tutorials, training and onboarding documentation, and user-generated content to deepen their understanding of the software and its capabilities. By encouraging learning and knowledge sharing among users, the community fosters a culture of continuous improvement and empowers users to maximize the value they derive from Jama Software.
  • Community Events and Resources: Jama Software may organize community events such as webinars, workshops, or user forums, allowing users to engage with experts, network with peers, and gain insights into industry best practices. These events and resources enrich the user experience and foster community and belonging among Jama Software users.

RELATED: Buyer’s Guide: Selecting a Requirements Management and Traceability Solution

What content and resources are available to community members?

Our community has a mix of public and private areas. The public areas include informational pages, introductory content, and discussion forums where non-members can browse and learn about the community’s topics, values, and conversations.

However, to access all the features in our community, users must register as members and create an account to access the full range of resources and interactive components. This login requirement promotes exclusivity, community ownership, and engagement. This process ensures a balanced approach to community involvement and privacy for our customers.

Once approved, members have access to:

  • Member-Only Content: Once logged in, members typically gain access to member-only content, discussion forums, advanced features, and interactive tools that are not visible to non-members. This exclusive content may include premium resources, private discussion groups, member directories, and personalized features tailored to individual preferences.
  • Enhanced Privacy and Security: Members can feel more confident in sharing sensitive information, discussing proprietary topics, or seeking support for specific issues, knowing that their interactions are protected within a secure environment.
  • Community Building and Engagement: By combining public-facing elements with restricted access, we can introduce new people to Jama Software® and showcase the community’s value to its members. At the same time, our member-only features help to foster deeper relationships, collaboration, and engagement.

How does the company gather feedback and insights from the customer community?

We gather information through our community in a variety of ways, including:

  • Feedback Forms, Polls, and Surveys: Jama Software may periodically distribute feedback forms, polls, and surveys to its customer community to collect structured feedback on specific topics, features, or aspects of the software, services, and overall experience. These surveys may cover user experience, product satisfaction, feature requests, and overall satisfaction with support services.
  • User Groups and Advocate Programs: Jama Software may establish user groups or advisory boards comprising select customers representing different industries, use cases, and user personas. These groups provide a structured forum for in-depth discussions, collaborative problem-solving, and strategic feedback sessions, allowing Jama Software to gain deeper insights into user needs and preferences.
  • Engagement at Events and Conferences: Jama Software engages with its customer community at industry events, conferences, and user meetups, where company representatives can interact directly with users, gather feedback in person, and gain firsthand insights into customer experiences, challenges, and priorities.

How does the customer community contribute to product development and innovation?

The online customer community provides a platform for collaboration between Jama Software and its user community. This platform allows for the exchange of ideas, feedback, experimentation, and validation.

By utilizing its users’ collective intelligence and creativity, Jama Software can accelerate product innovation and deliver solutions that better meet the needs of its customers. This significantly enhances our ability to continuously innovate and stay ahead of competitors so we can provide the best possible product for our customers.

  • Feedback and Feature Requests: Community members provide valuable feedback on their experiences with the software. Their feedback includes suggestions for new features, enhancements, and improvements. We gain insights into user needs, pain points, and priorities by actively listening to the feedback shared within the community. These insights directly inform product development decisions.
  • Co-Creation and Collaboration: The community provides a collaborative environment where both users and representatives from Jama Software can work together to create solutions for everyday challenges and explore innovative ideas.
  • Beta Testing and Early Access Programs: We provide beta testing programs and early access opportunities to community members to allow them to preview and provide feedback on upcoming features, prototypes, or experimental functionalities. By involving users in testing and validation, we gain valuable insights into usability, performance, and user acceptance. These insights help us to refine and iterate on new product offerings before an official release, ensuring a better user experience for everyone.
  • Use Case Exploration and Best Practices Sharing: Our community is a platform where users share their experiences of using the software, including their use cases, workflows, and innovative approaches. Through this platform, we get a much deeper understanding of how customers use the software to address diverse challenges and achieve their goals. This insight helps develop new features and capabilities tailored to specific use cases, improving the product’s overall functionality.
  • Market Research and Trends Analysis: The community is a valuable source of market intelligence for us, providing insights into emerging trends, competition, and customer requirements. By monitoring discussions, analyzing user-generated content, and engaging with community members, we’re able to stay informed about industry developments and market demands, which helps prioritize product development initiatives and identify opportunities for innovation.
  • Customer Advocacy and Validation: Engaged Community members often advocate for Jama Software. They spread the word about the company’s products and services within their networks and endorse new features or improvements based on their positive experiences. Their advocacy and validation play a significant role in driving adoption and retention and provide valuable validation of product direction and innovation efforts.

A new community space is coming soon!

We are excited to announce that our community is undergoing a transformation. Stay tuned for exciting news as we prepare to migrate to a new and improved platform.

RELATED: Revolutionary Surgical Robotics Company, Monogram Orthopedics, Selects Jama Connect® for Its Unique Cloud Based Services and Ease of Use

In what other ways does Jama Software offer support for users of Jama Connect?

We have launched a new Support space. This new space serves as a convenient starting point for visitors to access our extensive user guide, release notes, installation information, knowledge base, and other important resources for existing users. Visitors can also easily navigate to our community space, submit a support ticket, find installation information, and more.

We are so proud to say that since its launch in November 2023, our new Support space has led to an overall 94% satisfaction rating from customers who have opened support tickets.

Recognition of Jama Software’s thorough support has also been acknowledged through the popular software and services review platform, G2®. We’re grateful to our customers for sharing their valuable feedback through G2 on their experiences using Jama Connect. The “Users Love Us” category is a testament to the value our industry-leading requirements management software brings to our customers, and especially for customers who have moved from a document-based approach to complex product, systems, or software development.

“Superb Customer Service with helpful documents, guidelines and support sessions for all Problems around the Software and furthermore the Requirement Management itself” -From review collected and hosted on G2.com, Stephan T. — Mid-Market

“Jama Connect provides a simple platform that enables little training for a user to get started and to be productive using the tool to capture requirements, design, and other program level information. Customer support is also stellar. It is nice having a human to talk to, and the responses are timely and regularly resolve open questions, and comments.” From review collected and hosted on G2.com, Verified User in Renewables & Environment — Mid-Market

RELATED: G2® Once Again Names Jama Connect® the Overall Leader for Requirements Management Software

Customer support plays a vital role in the success of any business. It is built upon empathy and efficiency, which are essential for creating outstanding experiences. To further improve our support services, we are implementing new Support space features such as a chatbot and a federated search on our updated Support website. This will allow our users to easily access information from various sources, including the Product User Guide, our online community, in addition to the Support Knowledge Base.

We are constantly striving to improve and perfect our methods, strive to provide excellence in every interaction, and continuously enhance the overall customer experience. If you are an existing customer and want to learn more, please reach out to your customer success manager or consultant. If you are not yet a client, please visit our website at jamasoftware.com. To learn more about the platform and how we can help optimize your development process.

SOC2 Type2

Streamlining SOC2 Type 2 Compliance: How Jama Connect® Can Help Enable Audit Success

In today’s business landscape, technology and data play a crucial role. Therefore, it is of utmost importance to prioritize the security and privacy of sensitive information. One way to do this is by undergoing a SOC2 Type 2 audit.

A SOC2 audit provides an independent, third-party validation that a service organization’s information security practices meet industry standards stipulated by the AICPA (American Institute of Certified Public Accountants.) During the audit process, a service organization’s non-financial reporting controls as they relate to security, availability, processing integrity, confidentiality, and privacy of a system are tested.

This audit provides customers and partners with trust and assurance regarding an organization’s data security practices. It also helps businesses in regulated industries meet compliance requirements, manage risks by identifying and mitigating security threats, and gain a competitive edge by demonstrating a strong commitment to security. Furthermore, it can drive internal improvements by enhancing policies and procedures related to data protection.

Jama Software® is the only vendor in the requirements management and traceability space that is SOC2 Type 2 compliant both on the application layer and the data center offerings. In this blog post, we’ve invited Jama Software team members Sarah Voget – Team Lead, Project Manager, Jennifer Esposti – Project Manager, and Cooper Graham – Compliance Analyst, to detail their experiences preparing for and passing the SOC2 Type 2 audit and how they will use Jama Connect® to improve future audits.

Preparing for the audit process

Tell us about your experience with SOC2 audits in the past. What tools have you used at other companies? What were some of the challenges or drawbacks to those solutions?

Sarah Voget: The biggest challenge I ran into at previous companies was that no one tool could easily compile and track evidence for recurring audits. Passing an audit requires a company to compile substantial evidence from a variety of sources in a variety of formats. For example, we upload free text answers from subject matter experts (SMEs) to specific audit questions along with supporting screenshots, policy documents, PDF reports, etc. While tools like OneDrive or Excel could keep such information somewhat organized, it was incredibly difficult to have a holistic picture of audit evidence over time. Each year during audit prep, I felt like I had to reinvent the wheel by tracking down audit evidence from a variety of systems and SMEs all over again.

Tell us how you came up with the idea of using Jama Connect® for SOC2 compliance.

Voget: When I first joined Jama Software, I attended an internal presentation about Jama Connect, where I learned about our product’s strength in end-to-end requirements tracking. A lightbulb went off in my head because that’s really what audit prep is all about. An audit is like a list of requirements that we must prove we’re meeting, and each year, we reevaluate our effectiveness at meeting those requirements. It’s critical for us to understand how we met certain requirements in the past and to continuously iterate on our security policies and procedures as they relate to those requirements. Once I made that connection, I realized the potential power of Jama Connect as an internal audit preparation and readiness tool.

Can you provide any information about how you formatted Jama Connect initially to prepare for the audit?

Voget: My first attempt at using Jama Connect for audit prep focused on the big problem I mentioned earlier: compiling huge amounts of evidence in one place where I could easily access it over time.

RELATED: Buyer’s Guide: Selecting a Requirements Management and Traceability Solution

Lessons for future audits

Taking lessons from the first SOC2 audit using Jama Connect – what did you think could be improved on? What were the wins?

Jennifer Esposti: For the initial audit, Jama Connect was used primarily as a content management tool, which allowed us to organize and document the required evidence. This year, we wanted to expand our use to include the monthly, quarterly, and annual maintenance we do as a cross-functional team to ensure we are maintaining the necessary processes for SOC2 compliance.

Cooper Graham: In the first year run-through, we stored some critical information, such as the trust criteria and some information around the auditor questions and requests and our responses in Jama Connect, which limited those resources to those involved in the audit. The primary win was seeing the potential of the Jama Connect application for managing and tracking our SOC2 preparation. Having a foundation in the application that we could build on year-to-year rather than starting from scratch for each year’s preparation. Using additional features and elements in the Jama Connect application for collaboration and organization of our preparation.

What changes have you made from the initial SOC2 audit?

Esposti: From a project management perspective, I use the test management functionality within Jama Connect to organize the monthly, quarterly, and annual check-ins. The test cases provide a clear and consistent process for the project team to follow.

Graham: Using the test management functionality, we were able to organize and track recurring check-ins to ensure we were prepared for the upcoming audit. We were able to document more specific questions and responses that were provided during the previous audit to have a better understanding of the auditor’s asks and wants. It also gives our subject matter and individuals involved in the audit the ability to see what was previously asked to prepare for the upcoming audit.

How is Jama Connect well suited to help teams prove SOC2 compliance?

Graham: As a requirements management product, the ability to identify the requirements, track the associated testing, and include evidence or links to key artifact locations really assists in the organization for the audit and ensures nothing slips through the cracks.

How are you leveraging features in Jama Connect for this year’s audit and beyond?

Esposti: My focus this year is on using the test management functionality to organize our evidence and ensure we are performing the required tasks on a monthly, quarterly, and annual basis. For future audits, I’d like to explore ways we can use Jama Connect to track our progress year-over-year.

Graham: We are utilizing Jama Connect’s Test Management functionality in a new way this year. The ability to organize monthly, quarterly, and annual check-ins and create test plans associated with specific teams ensures that all of the pre-audit due diligence is performed. The ability to create test cases that can be reused ensures consistency for every check-in. Having everything laid out in Jama Connect allows us to identify gaps and potential improvements to test cases and collaborate more effectively with key stakeholders. In the future, we plan to use Live Traceability™ to have a better view of the SOC2 process, from requirements to testing to end results. As the Jama Connect application goes through its releases, new features and functionality are being continuously added. We’re constantly looking to see if there are new elements that would aid us in preparation for future SOC2 audits.

RELATED: Traceable Agile™ – Speed AND Quality Are Possible for Software Factories in Safety-critical Industries


Meeting SOC 2 Type 2 requirements requires careful attention to detail and strong management of organizational processes. A comprehensive solution like Jama Connect can greatly assist teams in navigating this complex terrain. By centralizing and automating requirement management, Jama Connect ensures traceability, transparency, and accountability throughout the development process. Its collaborative features facilitate efficient communication and documentation, which are crucial for meeting SOC 2 Type 2 standards.

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.

Live Traceability enables organizations to meet SOC2 Type 2 standards by effectively tracking data and processes within their systems. By utilizing Live Traceability, companies can demonstrate their compliance with SOC2 Type 2 standards through well-documented information and audit trails. This promotes transparency and accountability. Staying updated with the latest SOC2 Type 2 standards is crucial for maintaining secure operations and reducing risks. Jama Connect remains current by regularly updating its platform to adhere to the latest SOC2 Type 2 standards, ensuring companies remain compliant and secure.










this image portrays someone who may be working on a software factory.

What is a Software Factory?

A software factory is not a physical factory; instead, it’s a metaphorical one, signifying a structured, systematic approach to software development. It’s based on the principles of manufacturing, where standardization, automation, efficiency, and quality control are paramount. In a software factory, software is produced in a manner akin to an assembly line, where each stage of development follows a well-defined process, ensuring consistency and scalability.

RELATED: Loram Rides the Fast Track to Software Safety with Jama Connect®

Key Components of a Software Factory

  • Standardization: Standardized procedures and equipment are the foundation of a software factory. Because of this standardization, the development process is more predictable and controllable since every piece of software is produced using the same set of procedures.
  • Automation: The software factory model’s foundation is automation. Automation tools are used to speed up development, minimize errors, and reduce manual labor from code generation to testing and deployment.
  • Modular Architecture: Software factories employ modular architecture in a similar way to physical factories that use interchangeable parts. Reusable components are made possible by this method, which speeds up and simplifies the development of new features or apps.
  • Quality Control: A software factory must employ continuous integration and deployment (CI/CD) techniques. By using these procedures, code modifications are automatically tested and released, upholding strict dependability and quality criteria.
  • Collaboration and Communication: Coordinating the efforts of the various teams participating in the development process requires the use of effective collaboration tools and processes. By doing this, it is made sure that everyone is in agreement and that the result meets the intended goals.

Benefits of a Software Factory

  • Increased Efficiency: By automating repetitive tasks and standardizing processes, a software factory significantly increases the efficiency of software development.
  • Consistency and Quality: Standardized processes and automated testing lead to more consistent and higher-quality software products.
  • Scalability: The modular approach and automation make it easier to scale the development process, accommodating more features or higher volumes of software production without a proportional increase in resources or time.
  • Faster Time-to-Market: With streamlined processes and automation, software factories can significantly reduce the time it takes to bring a software product from concept to market.
  • Cost-Effectiveness: Although set up requires an initial investment, the long-term benefits of increased efficiency and reduced manual effort result in significant cost savings.

RELATED: Traceable Agile – Speed AND Quality Are Possible for Software Factories in Safety-critical Industries

How Can Jama Connect® Help?

Jama Connect® aids leaders by providing robust requirements and test management, ensuring clarity and alignment throughout the project. With Jama Connect’s Live Traceability™, teams can manage requirements and tests through the systems development process for proven reduction in cycle time and improved product quality.

With the advent of the software factory, software development has undergone a paradigm change from an artisanal, handcrafted approach to one that is more methodical, efficient, and scalable. Organizations can create software more effectively, more cheaply, and with higher quality by adopting the concepts of standardization, automation, modular architecture, quality control, and effective teamwork.

Note: This article was drafted with the aid of AI. Additional content, edits for accuracy, and industry expertise by Steven Meadows, McKenzie Jonsson, and Decoteau Wilkerson.

In this blog, we recap our webinar, “DO-326 Airborne Security Assurance, Threat Modeling, and DevSecOps” – Watch the entire thing HERE.

Cyber vulnerabilities can have a significant impact on safety-critical systems.

Today there is an unprecedented level of digital interconnectivity in everything from vehicle sensors to rovers on the surface of Mars. The aerospace industry has a high degree of cyber connectedness where a negative impact could cause harm to not only aircraft but financial systems, company reputations, international relations, or even physical harm to humans and property.

During this informative session, Cary Bryczek, Director of Aerospace & Defense Solutions at Jama Software®, discusses how Jama Software applies a cybersecure-by-design approach to meeting DO-326A/DO-356A for aircraft systems and how this can be extended to the defense domain.

In this webinar, we covered:

  • Applying the Airworthiness Security Assurance Process
  • Threat (attack) modeling methods
  • Tracing security measures to requirements and tests
  • The role of requirements in DevSecOps tool ecosystems

DO-326 Airborne Security Assurance, Threat Modeling, and DevSecOps

Cary Bryczek: What we’re seeing today is just an unprecedented level of digital interconnectivity in seemingly every system out there. The aviation industry has a high degree of cyber connectedness where a negative impact could really cause harm to not just humans and property, but company reputations, international relations, or financial systems.

What we’re going to see today is how Jama Connect can provide a cyber secure-by-design approach to meeting the many aspects of DO-326 and DO-356, or ED-202 and ED-203 in Europe, the Middle East, and Africa (EMEA.) What we’re going to see is we’re going to apply the airworthiness security process that’s inside of DO-326, and use Jama Connect’s Live Traceability™ to trace security measures to security requirements, trace security requirements to testing, look and see how a threat analysis can all be incorporated into a single platform.

What is Cybersecurity by Design? So one of the things that we see a lot is in the tool ecosystem is a very disconnected set of processes and tools. So whether you’re tracing and using tools that do requirements identification, tracing those to verifications and hardware and software designs, or whether you’re using tools to do aircraft security analysis and tracing those to security architectures and security V&V, we’re noticing the disconnectedness of the processes in the tool ecosystem is causing product delays, cost overruns, product failures, audit failures, late identification of defects, and lack of visibility because the ecosystem is very disconnected, is taking place. There’s poor requirement coordination. Change management is hard between software and hardware, and you have a high degree of manual effort required to produce the traceability that’s required for certification. And you’re seeing this after the fact and Excel is used everywhere. Desktop tools are prevalent in the engineering of these systems, and it’s difficult to integrate desktop tools and Excel files into and across the ecosystem for product development.

RELATED: Jama Connect® Features in Five: Space Systems Framework

Bryczek: So what is Live Traceability? Live Traceability in Jama Connect gives the ability for any engineer at any time to see the most up-to-date upstream and downstream information for any requirement, no matter the stage of the systems development or however many siloed tools it spans. Now, this Live Traceability is important because it’s required by the industry standards like we’ve seen in aviation development and Live Traceability delivers a huge productivity improvement and it reduces the risk and the delay that happens when you have a disconnected tool environment.

So we’re going to talk about DO-326. DO-326 is really a set of standards jointly developed by RTCA and EUROCAE. It came about in 2006. It includes a few separate standards. DO-326 and ED-202 really is about the airworthiness security process specification. It explains the fundamental concepts behind airworthiness cybersecurity. DO-356 and ED-203, the airworthiness security methods and considerations, this explains how to perform cybersecurity investments, how to evaluate threats, and security measures of the system. How do you apply the mitigation measures? DO-355, we’re not going to really talk about that one today, but it’s applicable to if there are changes in an already certified system. So one of the most relevant documents you’re going to start with even before you start down the path for cybersecurity, is creating your product information and security risk assessment document. You’re going to perform an analysis of this, and this analysis should be conducted according to the standards.

So what exactly is airworthiness? So airworthiness security is the protection of the airworthiness of the aircraft from intentional unauthorized electronic interaction. So existing safety processes don’t consider intentional disruption. They look at the faults and failures of an aircraft or the aircraft system on a whole. But DO-326 is specifically looking at intentional human-initiated actions with the potential to affect the aircraft due to some unauthorized access or disclosure or causing some denial or disruption of the information systems, the networks, and the software that’s running on these aircraft systems. So this also might include things like malware or infected devices or the logical effects of any external systems. So the purpose of the airworthiness security process within DO-326 is to establish that when subjected to this unauthorized interaction, the aircraft is going to remain in a condition for safe operation.

So like I said earlier, DO-326 describes the what and DO-356 is the how. I’m sure that you guys have carefully looked at both of these guidelines and these are images from the guidelines. But I just wanted to point out what we’re going to talk about today. We’re going to talk about how the airworthiness security process and threats are mapped in Jama and how you can have security assurance and the risk assessment process from DO-356, how those can be conducted in Jama Connect itself. As you know, DO-326 live in its own. You’re having supporting processes from the development of the aircraft, the development of the system, DO-178, ARP-4754 are all interacting and being conducted at the same time. So there’s no linear, do this first, do this next, do this later. All of these processes are taking place pretty much simultaneously or iteratively as you design and develop the aircraft system.

So the airworthiness security process from a basic level, it’s again, it’s the protection of the aircraft from intentional unauthorized electronic interaction. There are four steps for the basic process. We’re going to first identify the system assets and its parameters. The second step is to identify the threats for all of those assets, identify those risks for each of the threats, so what might happen, and then create controls and mitigations for those risks. You’re going to be adjudicating the degree of harm and assigning a security assurance level, the strongest being SAL3 or the least would be a SAL zero where there’s this limited or protection needs required. So there’s a way to grade those as well.

RELATED: Traceable Agile – Speed AND Quality Are Possible for Software Factories in Safety-critical Industries

Bryczek: The inside of Jama Connect itself, this image describes essentially the architecture of what you’re going to see that what we have in the product. We have a template that you can use to facilitate this. It sits alongside of our template that’s used for ARP-4754, and DO-178, or DO-254. The orange assets essentially is the data model that we’re using to capture the different types of things in the system. So we have assets, we have vulnerabilities. Those are tied to different threat assessments or a threat assessment is performed on these types of objects. We have security measures, we have the security architecture elements, and those feed into the security requirements. This comes pre-configured out of the box. We also have an area where you going to capture the data for that kind of thing.

Having this sort of a data model enables engineers to really perform the analysis to understand, all right, which assets have I not assessed yet? What’s the workflow? Who has reviewed the threat assessment? Have the security measures been satisfied by security requirements? Have we done security testing of the system? So this sort of data model enables the traceability to be instantiated and allows engineers to really more easily create the kind of a content. So one of the benefits you see of using Jama is that the security process is not disconnected from the design and development of the aircraft system itself. It’s done alongside. So that way you have that earlier touch points between the functional aircraft, design engineers and the security engineers. So you’re building in that secure by design approach.

Deep dive into the seven steps of DO-326A compliance in this related whitepaper:
Cybersecurity in the Air: Addressing Modern Threats with DO-326A

In this blog, we recap our eBook, “Buyer’s Guide: Selecting a Requirements Management and Traceability Solution for Aerospace” – To download the entire thing, click HERE.

Buyer’s Guide: Selecting a Requirements Management and Traceability Solution for Aerospace

Use a Single Platform to Accelerate Innovation in Aerospace Systems Development

Consistently meeting product security, reliability and safety requirements proves the top challenge for aerospace systems development lifecycles. Contract complexity, streams of new regulations and policies, in addition to the challenges presented by increasingly networked systems, add to the already onerous development processes. This can lead to unmet technical performance parameters or delayed airworthiness certification reviews which for commercial aviation today takes years, to possibly lengthen out even more.

Effective management of these shifting complexities impacts your ability to meet compliance and ultimately, critical timelines. As a result, your development teams could find themselves:

  • Mired in rework
  • Making trade-offs without context
  • Stuck in unproductive meetings

In this industry, aircraft and space systems development requires strict attention to safety and security requirements, as well as continuous innovation and fast paced development to remain competitive. Ineffective stakeholder collaboration and communication between suppliers, government customers, contractors, and vendors can lead to delivery delays and cost overruns.

Bottom Line: The accelerated development of safe, high-quality aerospace systems, coupled with a highly complex regulatory and contractual environment, create competing challenges, and make it difficult for teams to focus.

What if you didn’t have to compromise?

This Buyer’s Guide incorporates insights from Jama Software’s more than ten years of experience partnering with forward-thinking systems development teams. We’ve designed a platform to help aerospace systems development teams manage the systems engineering data and controls. This allows them to:

  • Align to industry regulations quickly
  • Simplify contract deliverables and certification preparations
  • Accelerate time to market and mission

Use these insights to better understand the challenges you’re up against and thoughtfully consider potential solutions. Plus, learn how to get the buy-in you need to undertake the kind of transformation necessary to succeed with complex systems development.

Making the Case for Change

Jama Connect for aerospace systems development helps organizations to manage systems complexity and replace documents or legacy tools with a single digital platform. When requirements, architecture, V&V, and safety analyses are managed in a centralized location, contract deliverables and certification preparations become a straightforward process and the business impact and value of the platform becomes clear across the organization. That makes executive buy-in easier.

Corrective actions can cost anywhere from $1.6 million for a small change (Gulfstream Model G–1159A and G–1159B airplanes and all Model G–IV and GIV–X airplanes to remediate the ground spoiler actuator installation) to a large corrective action that has indirect costs of lost revenue and diminished market cap at over $20 billion (Boeing 737 MAX). Those costs are especially significant considering the price tag of system development – $75 million in FAA compliance alone—and an average timeline of three to seven years for type certification alone. For a space system, a failure can mean the entire loss of a system or spacecraft; typically there is only a single system created.

Chart showing time-to-market competitive market costs.

If your company is not considering the importance of transitioning to a more streamlined development process, time is not on your side. Failing to act quickly can leave your organization even further behind. But to see the value a positive impact a system can have, stakeholders in an organization have to appreciate the challenges first.

This is where you come in. You can help quantify the problem within your organization and provide data to help make the case for change.

Go through the exercises in the next section using data from your organization to identify your current situation and the size of the potential opportunity.

RELATED: CIMdata: Digital Thread in Aerospace and Defense

Tools to Assess Four Development Pain Points

Throughout the past decade of working with organizations developing complex aerospace systems, four common systems development pain points continuously arise for those who have yet to transform their process.

We’ll provide context around the problems and share equations with examples to help you uncover the savings from a modern systems development solution. Remember to adjust the variables according to your company’s metrics to get a more precise estimate, and rethink how your team functions.

Improving any one of these four aspects of your development process produces real savings. While the calculations on the following pages aren’t cumulative, they impact one another and can add up to significant value for your organization.

This is the potential of using a modern systems development platform. If realized, it can radically change your business and be the competitive edge you need in today’s market.

The Four Common Development Pain Points

  • Unproductive Work Time
  • Lengthy Time-to-Market
  • Rework
  • Defects

Unproductive Work time

Are your days spent in inefficient meetings, sifting through emails and document versions for historical information or waiting for reviews and approvals? You’re not alone. Many teams suffer the repercussions of archaic, siloed development. A modern process maximizes efficiency by tackling the root causes of momentum-killing delays and holdups.

Calculate how much unproductive work time is costing your business and imagine the possibilities of getting that time back. What could you do with one extra hour each day?

PRO TIP: We’ve seen long status meetings shrink or vanish when teams have the right solutions in place. Think about your team’s schedule and adjust the average time saved per person based on the time spent in meetings each week.

Lengthy Time-to-Mark

Time to market or meeting a mission deadline and quality are usually seen as compounding challenges. Understanding the impact of change, capturing decisions, communicating feedback and reusing
existing intellectual property — all aspects that can help speed time-to-market — can be improved with a modern systems development solution.

PRO TIP: Cost savings can certainly be great and have an impact on your bottom line, but don’t forget the qualitative implications. Consider what it would mean for your systems line and brand to be first-to-market with game-changing systems.

RELATED: Tracing Your Way to Success: The Crucial Role of Traceability in Modern Product and Systems Development


In our experience, approximately 30-50% of a given project is rework. Rework is any time spent on extra work — including mid-development changes, incorrect testing or fixing defects — and it costs your company big time. Requirements errors cause the majority of rework. Improving the ability to track requirements from definition through testing to catch changes and adjust scope can ensure
you’re building the right thing and massively reducing overall lifecycle costs.

Complete the equation below to get an understanding of the number of hours your team spends in rework and the value of that in work hours alone.

PRO TIP: If your organization is working on more than one system at a time, repeat this calculation for each and add up the savings for a holistic view.


It’s common for requirements to have a defect at some point between definition and delivery. The important thing is to have a system in place that can quickly and accurately identify defects and
track their impact up and downstream. This provides visibility into the problem as early as possible when it’s less detrimental to fix.

PRO TIP: This calculation factors in personnel hours, but you should also think about the cost of parts, delays, and missed opportunities. Plus, should defects go undetected due to sub-par requirements or testing, releasing lower-quality systems could have devastating consequences.

“A document-centric approach often requires a gatekeeper and really limits collaboration – that creates a bottleneck. With Jama Connect, all our development teams can work together from anywhere with a shared collaboration hub.” – David Cubbage, Director, LEO Satellite Engineering and Production, Telesat

This is a preview of our eBOOK, “Buyer’s Guide: Selecting a Requirements Management and Traceability Solution for Aerospace”
– To download the entire thing, click

In this blog, we recap our webinar, “Effective Strategies and Solutions for Successful SaMD Project Execution”. Click HERE to watch the entire webinar.

Empower your teams with insights and solutions that transcend the challenges of medical device software development.

Navigate the complex terrain of medical device software development and learn crucial insights and practical solutions to propel your projects forward.

In this webinar, Romer De Los Santos, Senior Consultant at Jama Software®, guides you through:

  • The new SaMD Framework, which features ISO-aligned document templates and customization capabilities
  • Variant Management in Jama Connect®, the key concepts required, and how it can revolutionize your workflow
  • Insights into the nuances of navigating complex medical device software projects
  • A brief exploration of the impact of US and EU regulations shaping the software landscape

Below is an abbreviated transcript of our webinar.

Effective Strategies and Solutions for Successful SaMD Project Execution

Romer De Los Santos: During this presentation, I’ll go over the challenges facing development teams working on medical device software, the key features of the Jama Connect SaMD Framework, and how you can use Jama Connect’s categories and reuse and sync features to manage releases and variants. A successful software development project in the medical device industry is a careful balancing act between documentation and development activities. Development teams have tight deadlines that are driven by market conditions. At the same time, they’re responsible for generating the required quality records according to each region where their device will be marketed. Since this isn’t a regulatory discussion, we’ll just focus on the EU and US as examples.

Medical device software development in the EU is governed by IVDR and MDR regulations. The risk classification in some software activities will differ depending on the regulation it falls under. Unlike in the US, there is no specific distinction between SiMD and SaMD software. It’s all considered medical device software. You’ll need to consider if the software you are developing is an accessory to a medical device or if is it a medical device on its own. If it is an accessory, it’ll need its own technical file. If it is sold as an integral part of the system, it should be included in the system’s technical file.

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

De Los Santos: In the US, there is a distinction between software in a medical device and software that is a medical device on its own. With the advent of AI, machine learning, cloud computing, and other innovations, the FDA has been drawing up new guidance to help modernize oversight on software development. The concept of device software functions are a key part of its modernization efforts. Each device software function has its own risk classification. The FDA has indicated that they intend to target their oversight over software that is an extension of one or more medical devices, software that transforms a mobile platform into a medical device by using attachments, displays, sensors, or including functions like a regulated medical device, software that performs patient-specific analysis and provides specific outputs or directives used in the diagnosis, treatment, mitigation, cure, or prevention of a disease or condition.

The Center for Devices and Radiological Health (CDRH) at the FDA created the Digital Health Policy Navigator to help manufacturers determine if their product’s software functions may be the focus of FDA oversight. This past September, the FDA released its new guidance on cybersecurity in medical devices. The guidance encourages the use of a secure product development framework when building software. It specifies some new deliverables such as a security risk analysis that is distinct from and in addition to the safety risk analysis specified in ISO14971.

Manufacturers will need to analyze security risks from the design and development phase through device maintenance and eventually to product end-of-life. Manufacturers are encouraged to use threat modeling to analyze security vulnerabilities in the environment where the device will be used. You’ll also need to consider all interfaces to and from the system and the Off-The-Shelf software (OTS) and Software of Unknown Provenance (SOUP) components that the system depends on. Software Bill of Materials (SBOMs) must be generated and analyzed for potential vulnerabilities. This represents more work for teams but is absolutely required in today’s interconnected world. In addition to all the required documentation for the design history file, developers also need to consider how to manage their fast development iterations, how to handle parallel development and variant and release management, how to properly triage and disposition defects, and how to manage third-party components that are part of their system.

RELATED: Jama Connect® for Digital Health Solution Overview

De Los Santos: The Jama Connect SaMD Framework is intended to alleviate some of the documentation burden while each company has its own procedures. The framework provides basic document templates that comply with requirements specified in IEC62304 and ISO14971. Furthermore, each document template includes a customizable export template for your convenience. It’s designed to keep things as simple as possible by minimizing the number of different item types and fields. The framework is versatile and includes the ability to trace to items outside of Jama Connect. This framework is designed to cover the most common use cases and is intended as a starting point for your own process. Jama Connect can easily be configured so that the tool adapts to your process rather than the other way around.

To watch the entire webinar, visit:
Effective Strategies and Solutions for Successful SaMD Project Execution

this image shows a graduation cap and a clock, indicating this pot will teach visitors quickly on the topic of space systems.

Jama Connect® Features in Five: Space Systems Framework

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, Cary Bryczek – Director, Aerospace & Defense Solution at Jama Software® – we will explore the Space Systems Framework available for Aerospace & Defense teams in Jama Connect.


Cary Bryczek: Hi. I’m Cary Bryczek, Director of Aerospace & Defense Solutions at Jama Software. In this video, I’m going to introduce you to our Space Systems Framework available in Jama Connect. In this video, we will explore the benefits of using our pre-built template to get started with managing requirements, test cases, and architecture using our best practices inspired by industry standards and guidance from organizations like NASA and the European Space Agency.

With space systems exponentially growing in complexity, shortening development timelines due to mission need and customer demand, and cost reductions influencing the capabilities able to be delivered with the final design. Programs need to be able to get started quickly and begin the real work of engineering the system. Development and engineering tools need to be robust enough to tackle that complexity easy enough to deploy and then not get in the way of the real work of engineering the system.

Jama Connect and our Space Framework come preconfigured with a ready-to-use template. The framework is comprised of a requirements data model that provides requirements leveling and decomposition, a verification of validation data model that provides traceability to those requirements, an architecture data model that provides mechanisms to support systems architecture system functions, and allocation of requirements, and a data organization method that follows industry guidance with the best practices of data organization in Jama Connect. Let’s see what this looks like in Jama Connect.

RELATED: Buyer’s Guide: Selecting a Requirements Management and Traceability Solution for Aerospace

Bryczek: The Space Framework comes with two pre-built requirement data models. The one I’m showing now represents a full spacecraft product breakdown structure. The example shows how Jama Connect can handle the complexity of a full NASA or ESA space program. The requirements data model allows needs and requirements to be flowed down and fully traced from the stakeholder expectations, to the concept of operations, to system level requirements, down to segment element subsystem and component requirements.

This trace data model, what Jama calls the relationship model, provides a mechanism to enforce consistency and creation of data as well as a consistent method to trace that data. This allows you to do faster analysis, measurement of expected versus actual traceability, complex filtering, and easy trace matrix generation and reporting.

The left side of the screen is the exploratory and is where the data is organized. The Space Framework comes with this pre-built spec tree ready for users to start authoring content right away. You can see that it too is organized hierarchically from the highest level of abstraction at the mission level and then down to the component level. You can navigate this traceability in the tree as well.

We recognize that not every space system will be developed by a single entity that requires this combined breath of customer implementing requirements and those of the implementing organizations. Your organization might be merely developing only a component of a larger space system. For this, we have a second Space Framework for integrated systems. Let’s look at this one more closely.

RELATED: Traceable Agile – Speed AND Quality Are Possible for Software Factories in Safety-critical Industries

Bryczek: In this CubeSat example that comes with the framework, it’s easy to see how the data is organized in the exploratory in a system, subsystem configuration. Inside each of the subsystems, you can see the specific requirements, their verifications, architecture, and design descriptions. Traceability throughout the entire project can easily be analyzed at any level.

What I’m showing is the traceability from the stakeholder expectations all the way down the decomposition tree. I can see the system requirements verification and validation test cases. I can see the architecture, the subsystem requirements, and even the test runs, these real-time trace views not only show requirements decomposition, but test covers as well as allocation to architecture.

The framework supports, as I said, not just requirements, but architectures, V & V, even risk management and security. We’ve preconfigured the way you organized that here in the tree. So if I wanted to see the system architecture, I am able to see all of the elements that are going into making up the system architecture of this CubeSat I can also see how I’ve organized by system subsystem within the tree itself. That enables me to reuse easily and do variant management in this particular CubeSat security.

So, if you need to have security requirements or if you need to do heavy cyber security and you wanna import things like NIST 800 you can easily do that kind of a thing. Risk management threats and risks moving the development cycle with security earlier in that life cycle is a big deal, or understanding how safety is influencing the design. We easily allow you to track risk management and threat analysis in Jama as well.

The intent of this is to provide ready-to-use solutions based on customer feedback, industry trends, and best practices, such as those of ESA and NASA. This enables engineers to tackle the complexity of space systems develop faster and collaborate at the speed of need. 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 are already a Jama Connect customer and would like more information on the Space Framework, please contact your customer success manager or Jama Software consultant.

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

Co-workers portraying modern requirements management.

In this blog, we re-cap our eBook, “The Strategic Transition: From Word and Excel to Modern Requirements Management” – Download the entire thing HERE.

The Strategic Transition: From Word and Excel to Modern Requirements Management

Unless your organization’s business model is built on a foundation of inefficiency, you should not be using disparate documents for managing requirements. Whether it’s Microsoft Word, Excel, or a combination of both, trying to wrangle your product’s requirements soley in documents carries a lot of risk and will gradually eat away at your company’s bottom line.

There was a time when using disparate documents wasn’t such a problem for managing requirements, but as products grow in complexity, those days are fading. Many companies no longer produce products that contain just hardware or software; today it’s likely a combination of both, increasing development complexity exponentially.

Integrating hardware and software means teams spanning various engineering disciplines all need to stay aligned throughout development, especially when things like safety standards and regulations are involved.

Using documents alone, will simply not be up to the task of meeting today’s complex products, systems, and software development. When you need precision, context, and accountability for your requirements, a modern requirements management solution is really the only answer.

In this eBook, we’ll detail some of the reasons why you’ll want to leave disparate documents for managing requirements in your rearview. You’ll also get an overview of the benefits you’ll gain by moving to a purpose built software solution for requirements management.

What is requirements management?

To level set, requirements management is the process of gathering, analyzing, verifying, and validating the needs and requirements for a given product or system being developed.

Successful requirements management ensures that completed deliverables meet the expectations of the stakeholders.

Learn more

Five Drawbacks of Documents

Microsoft Word and Excel serve many purposes, and have done so for decades. And, in terms of requirements, for early-phase documentation and coordinating simple projects, they still remain effective tools.

As the complexity of product and systems development grows, so does your list of requirements. And teams need solutions that provide simple and streamlined collaboration, not jumbled — often quickly outdated — comments and suggested edits. Teams need to be able to instantly connect to globally distributed colleagues to facilitate real-time feedback and make smarter decisions with full context around requirements. Documents simply aren’t up to the challenge.

Here are some of the key limitations for a document-based approach for storing requirements:

1. Documents are tedious to maintain

Anyone who has ever managed requirements with documents and several collaborators is familiar with the unique pains of this approach. Whether it’s Word documents that are hundreds of pages long or Excel spreadsheets with thousands of lines, keeping them fresh with updates and free of errors is extremely cumbersome and time-consuming.

2. Versioning difficulties

Collaborating on any kind of important documentation can be painstaking, especially when there’s an enormous amount of requirements involved. For instance, when reviewing requirements, it’s incredibly easy for two people to be looking at different versions of the same set of requirements, and not even know it. And even if it’s a cloud-based version of requirements, there are still plenty of opportunities for someone to unintentionally change something without getting prior approval, and that adjustment not being accounted for in future versions. Plus, online/cloud-based documents do not automatically create different IDs and versions for each requirement or highlight the changes between versions.

3. No traceability

There’s so much room for error through email chains and undisclosed updates. It’s incredibly simple, for example, to miss a tiny change that could have critical ramifications upstream or downstream.

4. Reviews are time consuming

Without traceability, review cycles with an enormous document of requirements are extremely long. You’re likely looking at scheduling lengthy meetings or passing around version after version, pulling team members away from other priorities, which is not ideal when you’re focused on getting to market quickly. And if you’re trying to manage reviews asynchronously, collaboration becomes tricky and timelines are likely to get pushed as people’s schedules shift.

5. Exhausting collaboration between teams

Sharing constantly evolving requirements files among multiple stakeholders and different teams throughout the development and testing process is risky, frustrating, and time-consuming. And with your customer demanding a perfect product, system, or software delivered ASAP, you can no longer afford that kind of inefficiency.

In this eBook, The Jama Software® Guide to Requirements Traceability, we’ll highlight the importance of tracing requirements without the headaches and risks of a traceability matrix in Excel, but also how to do so in a way that sets your organization up for future success. Learn how Live Traceability™ helps teams:

    • Reduce the risk of delays, cost overruns, rework, defects, and recalls
    • Comply with industry standards with no after-the-fact manual effort
    • Allows engineering teams that continue working in their chosen best-of-breed tools
    • Increase productivity and satisfaction of engineers

Get it here

Seven Benefits of Using a Requirements Management Solution

Despite rising product complexity and regulation, most development teams do not have a sophisticated requirement management system in place. In fact, according to a recent survey, almost one third of teams have no system in place and rely on formal processes with email, documents, and shared spreadsheets.

Another 52% manage their requirements with a system which is not meant for managing requirements, like Application Lifecycle Management (ALM) or Product Lifecycle Management (PLM) systems. And only 15% have chosen to invest in a formal dedicated requirement management solution.

Using a dedicated requirements management solution allows teams to stop getting bogged down on processes and start innovating. For example MediSync, reports that investing in Jama Connect® has saved 80% of the time that would have otherwise been spent on meetings, sorting through versions of Word documents and emails, and consolidating feedback in review cycles.

Grifols saved around 80 hours per project in medical device development when using the Jama Connect Review Center. And RBC Medical saved around $150,000 per project by improving team collaboration and workflow efficiencies using Jama Connect.

Here are some of the benefits you’ll get from investing in a solid requirements management solution:

1. Version and change management

A solid requirements management solution will maintain a history of each change made to every requirement. You’ll also be able to record the rationale behind each change, and refer back to a previous version of a requirement if necessary. Some solutions contain a change proposal system that links change requests directly to requirements. And, with a formal requirements management solution, you’ll always know you’re looking at the most recent version of the requirements.

2. Requirements attributes

With a strong requirements management solution, you should be able to record several descriptive attributes for each requirement. The right requirements management software should generate several system-defined attributes such as the date the requirement was created, its current version number, and the person on the requirements should be able to view these attributes, even if only a couple of individuals are allowed to update the attributes’ values.

3. Facilitate impact analysis

A requirements management solution enables requirements tracing by letting you define links between different types of requirements, requirements and different subsystems, and individual requirements and related system components (designs, modules, tests, and user documentation). These links help you analyze the impact that the proposed change will have on a specific requirement. It’s also very helpful to have the ability to trace each functional requirement back to its origin or parent so that you know exactly where every requirement came from. And some solutions use a traceability link to raise suspect flags to a linked item whenever a change is made, so you know exactly what needs to be reviewed after a change.

4. Track requirements status

Collecting requirements in a database lets you know how many discrete requirements you’ve specified for the product. And tracking the status of each requirement during development helps communicate how things are coming along to those across the organization. So, a project manager has good insights into prior states if he or she knows that, for example, 55% of the requirements committed to the next release have been verified, 28% have been implemented but not verified, and 70% have not yet been fully implemented. This type of information gives the project manager information to anticipate the project’s progress, and relay the message to stakeholders accordingly.

5. Control access

A requirements management solution should let you bring as many people into the system as possible, and grant them permission to access the specific parts they’re working on. This helps teams across the organization feel more invested in the product being developed and its progress.

What if you didn’t have to compromise? A growing number of organizations are exploring and adopting product development solutions that manage the complexity that comes with designing connected systems. This allows them to:

  • Build higher-quality products
  • Get to market more efficiently
  • Capitalize on opportunities faster

Download this Buyer’s Guide: Selecting a Requirements Management and Traceability Solution to better understand the challenges you’re up against and thoughtfully consider potential requirements and test management solutions. Plus, get tips on how to get the buy-in you need to undertake the kind of change necessary to succeed with complex product development.

Get it here

6. Facilitating communication with stakeholders

A requirements management solution should allow team members to discuss requirements issues electronically through a threaded conversation, in one central location, as opposed to having communication spread out across various platforms. It will automatically trigger email messages and notify effective individuals when a new discussion entry is made or when a specific requirement is modified. And it should allow team members to reach out to each other, but also contact non-project members and external users.

7. Recycling/reusing requirements

Storing requirements in a central database facilitates the reuse of them in multiple projects or sub-projects. And requirements that logically fit into multiple parts of the same product can be stored once and referenced whenever necessary to avoid duplicates. This saves a lot of time and reduces the chance of making errors.