In this section we link to a worked example of modeling a system to create a game controlling robot pucks using a brain activity headset. The idea is to enable a quadriplegic to play a robot control game with a friend.
We carry the modeling down to a Logical Architecture level of detail. We chose not to use scenarios but instead concentrate on describing the
use cases using only activity diagrams with swimlanes.
You can trace the development of the model by visiting the diagrams created in sequence. Within each section (Operational Analysis, System Analysis,
and Logical Architecture) we numbered the diagrams in the order they were created. The first diagram created was "OEBD 01 Operational Context".
It took approximately 12 hours to create all of these diagrams.
Aviation Studies Institute System Architecture Documents
Within the Aviation Studies Institute, we use Capella to document the use cases, functions, processes, responsibilities,
and database design for tools developed under the research contract “Rapid Evaluation Tools for an Intelligent Optimization Platform” (Grant Number RS-NRASI-00002).
We follow the Arcadia process of Operational Analysis, System Analysis, and Logical Architecture in defining the requirements for these tools.
You can explore the resulting documents by following the hyperlinks below.
Case Study: ATM Workload Calculator
The purpose of this document is to capture functional requirements for a software tool to assist air traffic flow managers in analyzing sector demand within a user-defined airspace configuration. Using flight schedules, the tool approximates the location of each aircraft by time by sector. The tool then estimates controller workload considering aircrafts at different phases of flight, and whether aircrafts are in close proximity or crossing between sectors. These phases include ascending, descending, cruising, and crossing between sectors. "Close proximity" between two aircrafts is defined by the user. Finally, the tool presents pivot tables, charts and a geospatial animation of sector demand by time for analysis.
The purpose of this document is to capture functional requirements, organized into a logical architecture, for a software tool to assist air traffic planners in rapidly configuring a Terminal Manoeuvring Area (TMA) design and evaluating the design across multiple concerns. The design elements shall include waypoints, SIDS, STARS, runway orientation, holding areas, as well as approach and departure routes. The tool shall evaluate concerns of safety, capacity, delay performance, and fuel efficiency under different flight schedule loading patterns.