Jama Connect MCP™ for AI-Assisted Development and Traceability

Requirements, code, and verification artifacts often live in different systems. Engineers switch between tools to understand requirements, implement functionality, and document traceability. By the time an audit arrives, teams may spend days or weeks proving that what they built matches what was specified.

That gap shows up often in regulated engineering environments. Security requirements span multiple teams, systems, and compliance frameworks, including ISO 26262, DO-178C, IEC 62443, and FDA design controls. The work itself is rarely contained in one place, but the evidence for it still has to hold together.

In this Features in Five demo, Katie Hucket, Product Line Manager, Advisor/AI at Jama Software, demonstrates how Jama Connect MCP™ helps close that gap by bringing governed requirements, traceability, and auditability into the engineering workflow.

Access requirements without leaving the IDE

With Jama Connect MCP, approved requirements in Jama Connect can flow directly into the IDE. Engineers can pull in the requirement, the metadata around it, and the governance state behind it. They can also see relationships to upstream system, safety, and regulatory requirements.

That context matters. It gives the engineer the information needed to implement the work without leaving the development environment, while still keeping the requirement tied to the source of truth in Jama Connect.

A secure authentication example

The demo followed a platform security team working on secure service-to-service authentication across a distributed system. That kind of implementation is common in large programs, where one requirement can touch many services and many teams.

The engineer starts by retrieving the requirement from the IDE. In this case, the requirement traces upstream to a cybersecurity control aligned with IEC 62443. That trace gives the team a direct line from implementation work back to regulatory intent.

The requirement calls for mutual TLS, but the engineering details are still incomplete. Certificate validation rules are missing. Identity extraction is not fully defined. Authorization enforcement is not spelled out. Those gaps create ambiguity, and ambiguity creates risk.

Refine the requirement through a governed process

Instead of handling the gap outside the workflow, the engineer updates the requirement directly from the IDE. The change still goes through Jama Connect governance. It is permission controlled, reviewed, version controlled, and recorded in audit logs.

That updated requirement becomes the trusted reference for the implementation effort. It also gives AI-assisted development tools better context for generating code and tests that match the approved intent.

Use approved requirements in AI-assisted development

The demo showed how governed requirements can support modern AI-assisted development without losing control of the process. Once the requirement is aligned, the engineer completes the implementation with the requirement in view.

The code reflects the updated requirement. A reference to the requirement is embedded in the implementation, and a formal trace relationship is created.

That pattern scales well beyond a single service. In a large program, the same approach can apply across hundreds of services and thousands of requirements, with consistent traceability across the system.

RELATED: AI-Assisted Software Workflow Playbook

Establish traceability during development

Traceability has often been treated as a cleanup task. Teams finish the work, then go back and recreate links after the fact. That usually means extra manual effort, and it often leaves gaps.

Jama Connect MCP changes that rhythm. Traceability is created while the work is happening. Requirements, code, and verification artifacts stay connected as the implementation moves forward.

Jama Connect’s Traceability Information Model gives teams a way to work with more than direct links. They can follow structured relationships across upstream regulatory and system requirements, downstream software components, and verification evidence. If a requirement changes, the impact can be traced through the chain of related work.

Understand the impact of change

The demo also showed how this model helps during change analysis. If a new certificate standard is introduced, teams can identify the requirements, code, and validation work that may be affected.

That is the kind of analysis required by standards like ISO 26262 and FDA design controls. It also gives engineering and compliance teams a clearer view of what needs to be updated, reviewed, and revalidated.

Maintain audit readiness across the lifecycle

When traceability is captured as part of the workflow, teams can check coverage across the code base, confirm alignment between requirements and tests, and review how verification evidence maps back to the original requirement.

That makes audit preparation more straightforward. Teams are not rebuilding the story later. The story is already in the system, tied to the work itself.

Closing the loop

Jama Connect MCP connects governed requirements directly into AI-assisted development workflows. It helps teams use approved requirements in the IDE, create traceability as work happens, and keep requirements, code, and verification aligned throughout the product lifecycle.

For large engineering organizations, that means fewer audit findings, faster change impact analysis, and fewer defects caused by requirement gaps. It also gives teams a way to scale secure, compliant product development without losing control of the process.

Author
Recent Posts

Katie Huckett

Senior Product Manager at Jama Software

One of the things I love about product management and customer experience is the craft of it. Finally, a discipline that allows me to draw from every aspect of my eclectically diverse skill sets and interests.

With 14+ years of Enterprise SaaS experience, I have come across many complex feature requests and use cases. Never one to back down from a good challenge, I enjoy pushing the limits of what is possible while ensuring the big picture aligns with the overall product vision and strategy.

Experienced in:
• Developing product vision, strategy, and goals
• Develop and validate personas
• Creating and maintaining product roadmap
• Gathering product requirements (from user research, market research, user feedback, internal stakeholders, etc.)
• Creating and maintaining product backlog including prioritization
• Leading cross-functional teams across multiple office locations
• Presenting to stakeholders and obtaining buy-in
• Technical, analytical, and strategic thinking
• Managing product lifecycle from concept to end-of-life
• Product marketing to both customers and end-users

Specialties: User Experience, Customer Experience, User Research, Market Research, User Stories, Graphic Design, Data Analysis, Enterprise SaaS, User Champion, Product Lifecycle, Product Strategy, Goal Creation and Tracking, Technical Communication, Value Proposition, Product Marketing, Product Positioning, Training, Product Demonstration, QA Testing, Client Engagement, Business Analysis, Go-to-Market Strategy, Customer Segmentation Analysis, Sales Engineering, Customer Success, Agile Software Development, SCRUM, Value Selling

Tools and Languages: PhotoShop, InDesign, Illustrator, CRM, CMS, Aha!, Trello, InVision, Camtasia, Google Analytics, Zendesk, Sketchbook, SharePoint, Eloqua, Jira, Slack, Scrivner, HTML (some), Markdown

Jama Connect® Features in Five: Jama Connect MCP™ for AI-Assisted Development and Traceability