Skip to content

Enterprise Architect Integration with Jama and GitHub

Enterprise Architect Integration with Jama and GitHub

Enterprise Architect Integration with Jama and GitHub

Enterprise Architect Integration

The integration of Enterprise Architect (EA) with Jama and GitHub gives real-time visibility to the requirements management team and development team into each other’s work. With this kind of visibility, the coordination between the teams becomes seamless, comprehension of information within the ecosystem becomes easier, and the delivery cycle is accelerated. Further integration of GitHub to these systems helps create complete traceability for all requirements in the ecosystem.

Integration overview

In an Application Lifecycle Management (ALM) ecosystem, the choice of systems and the collaboration between the cross-functional teams play a great role in delivering quality solutions. While the choice of systems impacts the productivity of a team, the cross-functional collaboration enhances seamless communication between teams to take better decisions, faster.

By integrating EA with Jama and GitHub, enterprises can diminish collaboration barriers between development and requirement management teams that otherwise lead to quality issues, delivery delays, and financial loss. It also enables rich traceability of all work-items across the ecosystem.

How Enterprise Architect – Jama – GitHub integration is beneficial for an enterprise

  • Communication on the workitems from the native systems itself
  • Real-time updates when a user story/requirement is completed
  • Rich traceability of all work-items across the ecosystem

With Enterprise Architect + Jama + GitHub integration, enterprises can:

Enterprise Architect Jama GitHub Integration

How OpsHub Integration Manager integrates Enterprise Architect, Jama, and GitHub

OpsHub Integration Manager integrates EA, Jama, and GitHub – each system with one another bi-directionally. It ensures that all data is available to each user, in that user’s preferred system, with full context, in real-time. All requirements from Jama synchronize to EA and all the stories and design screenshots from EA synchronize to Jama. The source repository, GitHub, helps in maintaining traceability of all work-items across the ecosystem.

Popularly synchronized entities

Enterprise Architect Jama GitHub Entities Mapping

Use Case: Enterprise Architect integration with Jama and GitHub

Problem statement: An organization uses Jama for managing requirements, EA for visual design modeling, and GitHub for source code management. The data exchange between these systems happen doesn’t happen in real time, which creates a lot of confusion amongst the teams.

Solution: If Jama, EA, and GitHub are integrated using OpsHub Integration Manager, the teams using these systems will be able to effectively communicate and collaborate with each other. This, in turn, helps in increasing the overall team agility, productivity, and efficiency.

  1. User creates a Stakeholder Requirement in Jama
  2. Stakeholder Requirement in Jama are broken down into User Stories
  3. Stakeholder Requirement synchronizes as a Requirement in EA
  4. Requirement is broken down into Child Requirements in EA
  5. The Child Requirements in EA are detailed and mapped to the User Stories in Jama
  6. The System Architect designs the stories and attaches the design screenshots as attachments to EA Child Requirements
  7. Based on the approved designs, the development team works on the User Stories in Jama
  8. Once all the User Stories in Jama are completed, the development team commits them in GitHub against the correct Stakeholder Requirement id
  9. The commit information also flows back to EA and synchronizes with the respective Requirement
Enterprise Architect Integration with Jama GitHub

Benefits of integration for Enterprise Architect and Jama

EA users

  • Access to the business requirements and associated updates from within EA
  • Visibility into customer issues and priorities
  • No manual efforts needed to keep other teams in the ecosystem updated on updates and alerts

Jama users

  • Traceability for requirements throughout the ALM tool chain
  • Leverage the visual richness of designs synchronizing from EA for better comprehension of data
  • No manual efforts needed to keep other teams in the ecosystem updated on updates and alerts