Skip to main content

In the first part of the series, we considered the Concept-of-Operations, identifying the system domain and its primary objectives. We also considered the objectives of a Bad Actor who desires to abuse the system. Finally, we brought requirements into the model. Now we will go ahead and start designing the system, following those requirements. We will design the hardware; we will design the software, and we will also design the system operation, how these components all work together, for example, the logistics of moving information and material between system components. This work will be modeled, in the SysML model and in various hardware and software design environments, as shown in Figure 1.

Figure 1 Total System Model Architecture

We begin with logistics as process and system behavior. In Figure 2, we have a SysML sequence diagram with a step-by-step breakdown of all of the transfers that must occur between the different actors and parts in the system in order to carry out an election. This happens to be the first part of the logistics model, the Election Setup process, that involves many of the parts of the system: the county officials, the county central server, voter registration database, the precinct officials, the precinct central computer the direct recording electric machine. Notice the voter hasn’t shown up because this is the pre-voting setup stage, but the model includes additional diagrams like this to map out the actual voting and the vote aggregation and tabulation parts of the process.

Figure 2 Sequence Diagram in Rhapsody SysML – first phase of elections operations

In a sequence diagram, the horizontal arrows (messages) are read from the top down. The first message, the first transfer of information or materials, is the physical movement of the voting machines from the custody of the county officials to the precinct officials. The second is that a county official is going to create a ballot template, or a set of ballot templates specialized for each precinct, on the county central server. Then the ballot templates are transferred to the precinct officials. Later, the appropriate voter rolls are distributed, and so forth. Each step in the process is captured in a formalized manner in this sequence diagram, from setup to final vote totals.

Figure 3 Internal Block Diagram for Election Domain in Rhapsody SysML

To double check this process, we have created a structural connectivity diagram, the SysML internal block diagram in Figure 3, that describes the distribution channels between the users and parts of the system. These might be physical media, such as paper tape or flash memory cards, or electronic information transfer.  The nature of each channel is captured in an association block, which types each of the connectors in the figure. Each message from the sequence diagrams is allocated to the structural channel that carries it, which insures that there are no gaps in the process and makes it easier to investigate possible vulnerabilities later.

In the models which will be published with the final installments of the series, the complete set of diagrams for the hypothetical election logistics will be included. Before that, we have further aspects of system design and analysis to explore, starting with DRE hardware and software design.

Related Posts:

Tags:
Blog

Related Posts

Model-Based Systems Engineering for Autonomous Vehicles, Part 13 – Digital Reports

A key function of Digital Threads is to be able to answer questions about project status in real-time without the overhead of data collection, status reports and meetings. In this ...
Dirk Zwemer

Model-Based Systems Engineering for Autonomous Vehicles, Part 12 – Digital Projects

In this post, we continue our updating of MBSE for autonomous vehicles in light of the current and upcoming capabilities of Syndeia, the digital thread platform from Intercax. As ...
Dirk Zwemer

Model-Based Systems Engineering for Autonomous Vehicles, Part 11 – Digital Threads

In 2018, I published a ten-part blog series applying MBSE to an autonomous vehicle. That series continues to garner views on our website, but the state-of-the-art has advanced ...
Dirk Zwemer

Syndeia AI Multiple Agents, Part 4

Hello and welcome to a new demonstration of Syndeia AI that shows multiple AI agents in action – SysML v2, Teamcenter, Windchill, Jira, Jama Connect, Teamwork Cloud, and a Digital ...
Manas Bajaj

Fast-Track Digital Thread Training

Intercax is excited to launch a new self-paced training series designed to accelerate your journey into Digital Engineering: Building Digital Threads with Syndeia™. The new ...
Dirk Zwemer

Syndeia AI - Jira Agent, Part 3

We have all been there, trying to write complex query expressions or fill out a form with filters and drop downs to find issues in Jira. But now, you can finally talk with your ...
Manas Bajaj

Syndeia AI - SysML 2.0 Agent, Part 2

Greetings and welcome to an overview of the Syndeia AI - SysML 2.0 Agent. Syndeia AI is a collection of AI agents built on Syndeia Cloud. These AI agents are capable of processing ...
Manas Bajaj

Syndeia AI Agents, Part 1

Hello and welcome to a preview of Syndeia AI, a collection of AI agents that are powered by Syndeia Cloud. These AI agents can take natural language inputs, fetch latest data from ...
Manas Bajaj

Santa’s Mission 2024 with 8.2 billion landings made possible by Digital Threads (Day 5)

Santa has just returned from his whirlwind journey, and the workshop erupts in cheers. Elves spill into the command center, their faces glowing with joy and pride as they take in ...
Manas Bajaj