Intercax
IntercaxIn Part 1 of the blog series on Syndeia-JIRA interface, we described how Syndeia can connect to and browse JIRA repositories, and generate and connect SysML blocks from JIRA issues so that the block’s value properties mirror the issue characteristics like status, last update, etc. In Part 2, we showed how a multi-level SysML structure (e.g.
In Part 1 of this series, we connected individual requirements in DOORS NG to requirements and other elements in SysML. Greater challenges arise when we need to map requirement structure and organization between tools, because different tools organize requirements in significantly different ways. SysML tends to organize requirements in simple tree hierarchies using containment relationships.
Introduction Every system development project has both product-specific and project-specific considerations: Product-specific includes product requirements (market, technical, regulatory), product function and hardware and software design Project-specific includes organization structure, project requirements, and product development methodology The intersection of these two domains is often the Work Breakdown Structure (WBS) which captures the product-specific tasks in the
Of all the use cases potentially supported by Syndeia, links between systems engineering and project management are among the most intriguing. With Syndeia 3.0, a new interface to JIRA’s issue tracking repository offers a window into some of these possibilities. JIRA, widely used in agile software development, is organized by project and issue. As well as
In Part 1 of this series, we explored how Syndeia 3.0 generates global displays of connections between various engineering software tools. While these global displays (e.g. Figure 1) provide a snapshot of graph complexity, some very important use cases require us to trace out chains of individual connections and identify those model elements that may
The Martian by Andrew Weir (2014) is a great read and now a hit movie. The astronaut hero and the expert SysML modeler have several things in common. First, they have the ability to take a complex system and adapt and reuse its components to new purposes. Second, both do careful calculations of system performance
Advanced Model-Based System Engineering MBSE organizations are moving beyond the use of modeling to make “pretty pictures”. SysML parametrics are a way to add spreadsheet-like calculations to descriptive architectural diagrams. And roll-up calculations are among the most common use cases in systems engineering. Starting with a multi-level bill-of-materials or master equipment list, we want to calculate
as turbines are common components in systems for flight and power generation. A whitepaper developed by Dr. Dirk Zwemer (Intercax) and Nidal Kochrad (Université de Sherbrooke) titled “Case Study: A SysML Gas Turbine Parametric Model” illustrates how to model and analyze a gas turbine using SysML. The whitepaper shows the use of SysML parametrics to model
We are proud to announce the launch of SLIM 1.0. This is the first major public release of SLIM, following the beta release in Dec 2013. We take this opportunity to thank all our partners and customers who have made this possible. SLIM 1.0 provides a broad range of capabilities for model-based systems engineering (MBSE).
e are scheduling the next round of our Online SysML 101 and 201 courses in April–May 2013. These courses are delivered live via GoToMeeting sessions. Here are the specifics for this offering. What courses are being offered? We are offering both SysML 101 and 201. Here is a quick summary. Click here to learn more