SystemEngineering

TMADesignProposeLocal

SystemEngineering

TMADesignProposeLocal > TMADesignProposeLocal

Terminal Maneuvering Area Design Tool (TMA Design Tool)

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 Maneuvering 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.

The  flow of the document follows the ARCADIA system design process from Operational Analysis, through System Analysis, to Logical Architecture. We do not consider Physical Architecture as this is purely a software tool.

Operational Analysis

Operational Analysis is a high level view of the stakeholders, their concerns, and their generic workflows (operations). 

System Analysis

In System Analysis, we take the generic workflows from Operational Analysis and detail how the system (the TMA Design Tool) will support those workflows. Some tasks and decisions remain with the user (a particular stakeholder) but other tasks can be handled by the system. A high level system functional architecture emerges from this analysis. We also suggest detailed supporting data structures as class diagrams.

At this point in the analysis we recognize that the TMA Designer needs to be provided with advanced interactive design view and editing tools with structural feedback. We introduce a use case (system capability) to capture these needs and discover additional functional requirements.

The System Analysis is not complete yet but we can provide a partial functional architecture

We continue with activity analysis with a focus on simulating trajectories consistent with airspace design and flight schedule scenarios.

Here is a system functional architecture ignoring user functions and ancillary services:

Logical Architecture

In Logical Architecture, we identify major subsystems of functionality within the system (the TMA Design Tool) and further detail the workflows from System Analysis to show how the subsystems communicate to achieve each workflow. As part of this stage we also formalize data requirements into a database design.

Here is the overall structure diagram and architecture diagrams for major use cases.

We continue to detail the workflow and supporting data structures for the "Respond to TMA Restriction Event" use case.

 

Version Updates

 

Content