0% found this document useful (0 votes)
15 views3 pages

Fighter Aircraft MMC Software Overview

Mission Computer Doc

Uploaded by

hameed
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
15 views3 pages

Fighter Aircraft MMC Software Overview

Mission Computer Doc

Uploaded by

hameed
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd

1.

Introduction
The MMC software is the central nervous system of a fighter aircraft, responsible for coordinating
various systems and making real-time decisions during missions. It integrates data from sensors,
weapons, and other subsystems, and provides the pilot with a comprehensive picture of the operational
environment.
 Purpose: The purpose of this document is to define the requirements, architecture, and
implementation strategy for the software of a Fighter Aircraft Mission Management Computer
(MMC).
 Scope: This document covers the high-level functional and non-functional requirements,
software architecture, and implementation methods. The software will be developed in C
language.

2. System Overview
 Mission Management Computer (MMC): The MMC is responsible for managing the
aircraft's mission-critical tasks, including navigation, targeting, communication, and data
processing.
 Operational Environment: The software will run on a real-time operating system (RTOS),
specifically VxWorks, on an Intel Xeon D-1746TER processor.

3. Requirements
3.1 Functional Requirements
FR1: Navigation Management
 The software shall calculate and manage the aircraft's route, including waypoints,
altitude, and speed.
FR2: Targeting System Integration
 The software shall interface with the radar system to identify and track targets.
FR3: Communication Management
 The software shall manage all communication channels, including radio, data link, and
intercom.
FR4: Data Processing
 The software shall process sensor data in real-time, providing situational awareness to
the pilot.
FR5: Mission Planning and Execution
 The software shall allow for mission planning and real-time mission execution
adjustments.
3.2 Non-Functional Requirements
NFR1: Real-Time Performance
 The software shall meet strict real-time constraints, ensuring responses within
microseconds.
NFR2: Reliability
 The software shall achieve 99.999% uptime, with mechanisms for fault tolerance and
redundancy.
NFR3: Scalability
 The software shall be modular to support future upgrades and additional functionality.
NFR4: Security
 The software shall include encryption and secure communication protocols to prevent
unauthorized access.

4. Software Architecture
4.1 Layered Architecture
 Application Layer: Implements mission-specific logic such as navigation, targeting, and
communication management.
 Middleware Layer: Provides services like data handling, inter-process communication (IPC),
and abstraction for hardware interfaces.
 RTOS Kernel Layer: Manages real-time scheduling, task management, and resource
allocation.
 Hardware Abstraction Layer (HAL): Interfaces directly with hardware components like
sensors, actuators, and communication devices.
4.2 Software Modules
 Navigation Module: Manages the aircraft’s flight path and coordinates with the navigation
sensors.
 Targeting Module: Processes radar data and controls targeting systems.
 Communication Module: Handles all communication protocols and data exchange.
 Data Processing Module: Filters, processes, and interprets sensor data.
 Mission Execution Module: Manages mission plans and executes mission tasks in real-time.

5. Implementation Method
5.1 Development Approach
 Agile Methodology: Use an iterative and incremental approach with continuous integration and
testing.
 Modular Design: Implement the software in modular components to enable reuse and easier
maintenance.
 Coding Standards: Follow MISRA C guidelines to ensure safety and reliability in the C
codebase.
5.2 Toolchain
 Compiler: Use GCC with real-time extensions.
 Debugger: Use GDB with support for real-time debugging.
 Build System: Use CMake or Make for build automation.
 Version Control: Use Git for source code management.

6. Software Architecture Diagram


The software architecture is designed in a layered approach, with each layer interfacing with adjacent
layers to ensure modularity and separation of concerns.
1. Application Layer
 Mission Execution
 Navigation
 Targeting
 Communication
 Data Processing
2. Middleware Layer
 IPC
 Data Handling
 Hardware Abstraction
3. RTOS Kernel Layer
 Task Scheduling
 Resource Management
 Real-time Clock
4. Hardware Layer
 Sensors (Radar, GPS)
 Communication Devices (Radio, Data Link)
 Actuators (Flight Control Systems)

Common questions

Powered by AI

The layered architecture of the MMC facilitates separation of concerns by organizing the software into distinct layers, each responsible for different aspects of system functionality. The application layer implements mission-specific logic, while the middleware layer handles data and communication, and the RTOS kernel layer manages real-time tasks and resources . This separation allows for modular design, where changes in one layer do not necessarily affect others, enabling easier upgrades and maintenance .

The MMC ensures real-time decision-making by integrating data from various subsystems such as sensors, weapons, and communication devices. It coordinates these systems through real-time processing facilitated by the VxWorks RTOS on an Intel Xeon D-1746TER processor . The software architecture is layered, with the RTOS Kernel Layer managing real-time scheduling and resource allocation, ensuring timely responses . This architecture supports strict real-time constraints, requiring microsecond-level response times .

The MMC software employs a modular design, which involves implementing the software in separate, reusable components. This design is important because it supports easier maintenance, scalability, and future upgrades . The software's layered architecture further enhances modularity by ensuring separation of concerns, with each layer interfacing with adjacent layers. This approach makes it easier to manage individual components like navigation or communication modules without affecting the entire system .

The MMC architecture supports fault tolerance and redundancy through its layered structure and real-time operating system capabilities. The RTOS kernel manages task scheduling and resource allocation efficiently, allowing the system to maintain functionality even when certain components fail . Reliability is further enhanced by building redundancy into the communication and data processing mechanisms, ensuring the system can maintain 99.999% uptime .

Using MISRA C guidelines in MMC software development ensures safety and reliability in the software codebase. These guidelines provide a set of best practices designed to avoid common programming errors that could lead to unpredictable behavior in safety-critical systems . By following these standards, developers can reduce the risk of software failures, contributing to the overall safety and reliability requirements of the MMC .

The MMC software addresses security by including encryption and secure communication protocols. These measures are critical in preventing unauthorized access and ensuring the integrity and confidentiality of data exchanged between systems. Incorporating these protocols as part of the non-functional requirements highlights the importance of security in mission-critical tasks .

The integration of sensors and communication devices in the MMC enhances situational awareness by allowing real-time data processing and communication. Sensors such as radar and GPS provide critical data about the environment, which the MMC processes to give the pilot a comprehensive operational picture . Communication devices manage data exchange with external systems, ensuring the pilot receives timely and accurate information for decision-making . This integration is crucial for maintaining awareness of dynamic mission conditions.

Agile methodology and continuous integration are crucial in MMC development because they provide flexibility and adaptability to changes, which are vital in complex systems like fighter aircraft software. Agile allows for iterative development and incremental improvements, facilitating frequent testing and validation of new features . Continuous integration ensures that all code changes are automatically tested, which helps in catching defects early and maintaining high software quality .

The key non-functional requirements for the MMC software include real-time performance, reliability, scalability, and security. Real-time performance ensures the software responds within microseconds, crucial for mission-critical operations . High reliability is achieved through fault tolerance and redundancy, with a targeted uptime of 99.999% . Scalability is supported by modular design, enabling future upgrades . Security is maintained with encryption and secure protocols preventing unauthorized access . These requirements collectively ensure operational success in high-stakes environments.

The mission execution module within the MMC meets real-time mission planning and adjustments by managing mission plans dynamically and executing mission tasks in real-time. This functionality relies on the RTOS kernel’s real-time scheduling to prioritize and ensure timely execution of critical tasks . The module interfaces with other modules such as navigation and targeting to adjust plans based on real-time data, providing flexibility and responsiveness during missions .

You might also like