24.11.2014 Views

Military Embedded Systems Spring 2005 Volume 1 Number 1

Military Embedded Systems Spring 2005 Volume 1 Number 1

Military Embedded Systems Spring 2005 Volume 1 Number 1

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Software<br />

MILITARY EMBEDDED SYSTEMS Resource Guide<br />

environment. That means access to more<br />

technologies for these developers without<br />

having to learn a new development environment,<br />

as well as the ability to develop,<br />

debug, and deploy devices employing<br />

heterogeneous operating systems.<br />

MIL EMBEDDED: How is the topic<br />

of “safety-critical software” affecting<br />

designers’ COTS choices?<br />

FANELLI: Development of safety-critical<br />

software is undergoing a shift as well.<br />

Before, we had federated systems deployed<br />

on a single hardware element, using a<br />

COTS or home-grown OS. Today, we<br />

see consolidation of applications onto an<br />

ARINC- 653 platform using a COTS OS.<br />

An example is the Boeing 787 program<br />

where multiple vendors will build applications<br />

on Wind River’s ARINC-653<br />

platform that meets DO-178B Level A<br />

certification. Now safety critical developers<br />

can also achieve the goals of portability,<br />

reusability, and modularity for their<br />

applications.<br />

MIL EMBEDDED: Wind River recently<br />

endorsed the Eclipse development environment<br />

and community. What does<br />

this mean to the military user?<br />

FANELLI: Obviously, we believe Eclipse<br />

is strategic, otherwise we wouldn’t be<br />

investing in it. Thus far, Eclipse has<br />

gained remarkable traction in the enterprise<br />

market, so now is the time to focus<br />

on repeating this success in the broader<br />

aerospace and defense industry. Wind<br />

River Workbench, with third party plugins,<br />

is being applied across many different<br />

programs and RTOSs (from VxWorks to<br />

Linux to third-party OSs) for both enterprise<br />

and embedded development. Primes<br />

will be able to standardize on tools/middleware<br />

and increase their efficiencies,<br />

while federated programs and software<br />

solutions will fade.<br />

all available technology (hardware bringup,<br />

build, configuration and verification<br />

tools, software interoperability and reusability,<br />

post deployment support) across<br />

the whole development life cycle is provided<br />

on a common, open foundation.<br />

This is the military’s vision and it marries<br />

well with Wind River’s vision of how the<br />

world is moving away from embedded<br />

systems design to a new frontier.<br />

MIL EMBEDDED: As systems shrink<br />

to boards, and boards to chips, how<br />

can this trend continue, and how will<br />

it manifest itself in future defense<br />

systems? Secondly, what effect does<br />

this have on the systems’ software?<br />

FANELLI: Certainly we will see more<br />

handheld devices as well as a paradigm<br />

shift in CONOPS (Concept of Operations)<br />

as processing starts occurring in real time<br />

in areas that were previously post analyzed.<br />

For example, airborne reconnaissance<br />

image exploitation will move from<br />

ground-based systems to the airborne<br />

vehicles and be processed in real time. A<br />

soldier on the ground can have a vehicle<br />

scan a road over a hill and alert them of<br />

potential improvised explosive devices that<br />

were placed there in the last few hours.<br />

By analyzing changes in the roadside over<br />

the last few hours in real-time, the soldier<br />

can then “rewind” the information to see<br />

where the vehicle came from that placed<br />

the device. This change in processing<br />

power will bring forth a whole new wave<br />

of thinking in operations. The software<br />

will not change dramatically, but the type<br />

of application will evolve to take advantage<br />

of these new capabilities.<br />

MIL EMBEDDED: How will the<br />

disconnect between commercial and<br />

military technology cycles be solved?<br />

FANELLI: Making COTS technology<br />

more standards based will make it interchangeable<br />

and flexible. This enables<br />

technology upgrades to be more easily<br />

accomplished and at a lower cost.<br />

MIL EMBEDDED: Explain how<br />

your company addresses obsolescence<br />

mitigation.<br />

FANELLI: Wind River has a well-defined<br />

product life cycle strategy. For the most<br />

part, we work to provide upgrade compatibility<br />

to new technology for our customers.<br />

This allows systems to stay current<br />

and customers to plan migration (such as<br />

time and dollars) to avoid obsolescence.<br />

Retirement is the final phase of the product<br />

life cycle and there is never a predefined<br />

time to declare that a product is retired.<br />

Instead, the choice to retire a product is<br />

driven by a number of factors, including<br />

market adoption of newer technologies,<br />

customer needs, and Wind River’s<br />

overall product strategy. When a product<br />

is retired, we inform our customers well<br />

in advance and also work with them to<br />

address individual program needs. In fact,<br />

we’ve addressed custom support for retired<br />

products with a number of aerospace<br />

customers.<br />

MIL EMBEDDED: What are the<br />

“hottest” military programs right now?<br />

FANELLI: The UAV programs are currently<br />

the hottest military programs.<br />

There is a lot of excitement, funding, and<br />

new ideas being fielded in the air, on the<br />

ground, and on underwater UAVs.<br />

MIL EMBEDDED: What are the least<br />

likely types of programs and applications<br />

to use COTS software technology<br />

and civilian embedded electronics?<br />

FANELLI: High-assurance programs may<br />

have issues using COTS software technology<br />

as the costs of application software,<br />

OS, Board Support Package (BSP), and<br />

MIL EMBEDDED: What impact does<br />

the DOD’s Global Grid and “system<br />

of systems” have upon the future and<br />

architecture of embedded systems?<br />

FANELLI: This initiative forces a move<br />

from conventional embedded systems<br />

design such as single board, single application,<br />

or meeting a specific project<br />

need, to what we call Device Software<br />

Optimization (DSO). DSO means that<br />

“We actually think the Linux and<br />

greater Open Source community<br />

will have a large impact on military<br />

and associated programs...”<br />

34 / <strong>2005</strong> MILITARY EMBEDDED SYSTEMS Resource Guide

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!