Emerging technologies are driving product innovation across various sectors, particularly in the automotive industry. While standard frameworks define, implement, and evaluate the processes required for system development, the automotive sector also requires effective communication and cross-team visibility to deliver quality products and achieve positive business outcomes.
Integrations powered by OpsHub Integration Manager (OIM) enable organizations to manage customer requirements and address product complexity through enhanced collaboration. In this video, we demonstrate how OIM integrates Enterprise Architect (EA) and Jama Connect bidirectionally. This integration allows system engineers and product managers to access both historical and real-time cross-functional data in their preferred systems with full context. The traceability between visual modeling and requirements management tools empowers development teams to design and build software and systems accurately, avoiding tedious manual workarounds.
In Jama, a component named “EA Demo” is created, containing two pre-configured sets: one for storing requirements and the other for diagrams. The product manager begins by creating a requirement in Jama, adding details such as name, description, and priority. Fields mapped in OIM’s configuration, including custom fields, automatically synchronize back to Enterprise Architect. For instance, the product manager assigns an EA element type of “Activity” to the first requirement, ensuring it synchronizes to EA as an Activity element. Additional requirements are added with EA types such as Action, Block, and Interface.
Once the requirements are created in Jama, linkages between them can be established. For example, the product manager relates the “Activity” requirement to the “Action” requirement, selects the relationship type, and saves it. The relationship is successfully created in Jama, showing “Activity” as a downstream item of “Action” and vice versa.
In Enterprise Architect, the Systems Architect refreshes the page to view all synchronized elements from Jama. Each element reflects its custom EA type, along with associated details like name, description, and type. Using these elements, the systems architect creates diagrams. For instance, an activity diagram visualizes the established linkage between “Activity” and “Action.” Additional elements, such as new actions and activities, can also be added, related, and synchronized back to Jama.
The systems architect then creates a block definition diagram, incorporating elements synchronized from Jama, such as “Block 1” and “Interface,” alongside native EA elements like an Actor. Relationships are established between these elements, and all updates synchronize back to Jama. Similarly, a sequence diagram is created using native EA elements, and once completed, diagrams are renamed according to their type.
In JAMA, the product manager reviews the synchronized diagrams. The sequence diagram and all its associated details, including name and type, are visible. The block diagram reflects the elements and relationships synchronized from EA. In the activity diagram, all elements and their linkages, initially created in Jama and used in the EA diagram, are displayed. The remote ID field in Jama provides a link to the corresponding EA element ID, while in EA, each requirement reflects the associated Jama ID and link.
This seamless bidirectional integration ensures that teams across systems have complete visibility into design elements, relationships, and requirements, enhancing collaboration and productivity.
That concludes the demo. Thank you for watching!