---
title: MBSE for Urban Systems – Part 5.1 | Project Management for Urban Systems Modeling
description: In Part 1 of this series, we discussed the importance of supporting collaboration. One aspect of this is providing access to project management information for all members of the team. We can use Syndeia to facilitate this by creating issues in JIRA connected to elements in the other software tools. The JIRA issues contain status,
---

[Intercax - Blog ](https://intercax.com/blog)

# [MBSE for Urban Systems – Part 5.1 | Project Management for Urban Systems Modeling](https://intercax.com/blog/2019/02/26/mbse-for-urban-systems-part-5-1-project-management-for-urban-systems-modeling)

 Written by [Dirk Zwemer](https://intercax.com/blog/author/dirk) | Feb 26, 2019

In [Part 1](https://intercax.com/2019/01/29/mbse-for-urban-systems-part-1-introduction/) of this series, we discussed the importance of supporting collaboration. One aspect of this is providing access to project management information for all members of the team. We can use [Syndeia](https://intercax.com/products/syndeia/) to facilitate this by creating issues in [JIRA](https://www.atlassian.com/software/jira) connected to elements in the other software tools. The JIRA issues contain status, schedule, staffing and recent activity in a readily-available repository.

For our example, we have used Syndeia to drag the top-level [SysML](http://omgsysml.org/) block **Urban_System_02** from MagicDraw into a JIRA project. The multi-level SysML part structure creates 84 separate JIRA Tasks, each connected to a SysML block.

*Figure 1 Syndeia Connections Browser showing SysML Commercial Subsystem block connections to Simulink and JIRA*

We can use the Syndeia dashboard to view and use these connections. In Figure 1, we show two connections below the **Commercial_Subsystem** block. The first is to the JIRA Task just created, the second to the Simulink block created in the previous blog post. If we right-click on the first row, we can open the connected JIRA issue, which appears in our web browser as in Figure 2, assuming we have a JIRA account with access to that project.

*Figure 2 JIRA web interface showing Commercial Subsystem issue created from SysML block of same name*

The JIRA Task dashboard shows us who is assigned to the task, what the status is, schedule, test results and a log of recent activity. It also includes a list of related tasks, which correspond to the blocks immediately above and below **Commercial_Subsystem** in the SysML structure hierarchy.

The connection can also be used to open the JIRA issue directly from the SysML model in MagicDraw. For example, in Figure 3 below, we can right-click the element in a SysML block definition diagram to open the same JIRA issue to enter new status information on this part of the model.

*Figure 3 Using Syndeia connections to open connected elements in other tools*

For effective collaboration, we want to make this same set of issues  
 readily accessible to engineers using other software tools besides SysML. For  
 example, we can use Syndeia to create direct connections from the Simulink  
 blocks to the existing JIRA issues. Now, using the Syndeia Stand-alone client  
 (which does not require the user to have a SysML tool), the Simulink specialist  
 can browse connections originating in the Simulink model and open the connected  
 elements in other models. In Figure 4, the  
 row showing the connection below Commercial_Subsystem.slx shows its connection  
 to a JIRA Task, which can be opened directly from that row.

*Figure 4 Syndeia Connections Browser showing Simulink block reference connections to JIRA*

In the next post, we will use modern graph database information technology to query and navigate the federated urban systems model we have created. In this post, we will merge the alternative Cameo and [Rhapsody](https://www.ibm.com/in-en/marketplace/rational-rhapsody) streams in this series because these SysML models are functionally identical within the graph database. Both SysML models will be made available for download with this final installment of the series.

**Related Posts:**

- [MBSE for Urban Systems – Part 1](https://intercax.com/2019/01/29/mbse-for-urban-systems-part-1-introduction/)
- [MBSE for Urban Systems (Cameo) – Part 2](https://intercax.com/2019/01/31/mbse-for-urban-systems-part-2-managing-requirements-in-sysml-jama-and-doors-ng-cameo/)
- [MBSE for Urban Systems (Cameo) – Part 3](https://intercax.com/2019/02/07/mbse-for-urban-systems-part-3-1-structural-decomposition-of-the-urban-systems-model/)
- [MBSE for Urban Systems (Cameo) – Part 4 ](https://intercax.com/2019/02/12/mbse-for-urban-systems-part-4-1-modeling-flows-within-the-urban-systems-model/)
- MBSE for Urban Systems (Cameo) – Part 5 (this post)  
  [MBSE for Urban Systems – Part 6](https://intercax.com/2019/03/05/mbse-for-urban-systems-part-6-urban-systems-modeling-with-graph-databases/)

[View full post](https://intercax.com/blog/2019/02/26/mbse-for-urban-systems-part-5-1-project-management-for-urban-systems-modeling)

```json
{
  "@context" : "http://schema.org",
  "@type" : "BlogPosting",
  "author" : {
    "@type" : "Person",
    "name" : "Dirk Zwemer"
  },
  "dateModified" : "2025-01-17T10:10:05.334Z",
  "datePublished" : "2019-02-26T10:50:59Z",
  "headline" : "MBSE for Urban Systems – Part 5.1 | Project Management for Urban Systems Modeling",
  "image" : {
    "@type" : "ImageObject",
    "height" : 264,
    "url" : "https://23814759.fs1.hubspotusercontent-na1.net/hubfs/23814759/Imported_Blog_Media/image-4.png",
    "width" : 762
  },
  "mainEntityOfPage" : "https://intercax.com/blog/2019/02/26/mbse-for-urban-systems-part-5-1-project-management-for-urban-systems-modeling",
  "publisher" : {
    "@type" : "Organization",
    "logo" : {
      "@type" : "ImageObject",
      "height" : 60,
      "url" : "/hs/hsstatic/content_shared_assets/static-1.4092/img/default-amp-logo.png",
      "width" : 60
    },
    "name" : "Intercax - Blog"
  }
}
```