Military Embedded Systems Spring 2005 Volume 1 Number 1

Industry Analysis
MILITARY EMBEDDED SYSTEMS Resource Guide
nal envelope (the same I/O connections)
to preserve compatibility and minimize
migration efforts. A and B would be the
same product with the changes restricted
to any major engineering changes needed
for cost reductions, quality and manufacturing
improvements, plus any performance
enhancements that do not impact
the original operational model of the
product.
Year 1 Year 2 Year 3
Revision A
Virtual 10 Years
Year 1 Year 2 Year 3 Year 4
Revision B
Year 1 Year 2 Year 3 Year 4 Year 5
Revision C
This same process is repeated between
release B and C with the exception that
the release B product would have a fouryear
life cycle goal, again with a one
year overlap with revision C. Revision C
would then be the final anticipated release
with a five-year life cycle goal. Allowing
for a one year overlap between releases, a
10-year virtual life cycle is achieved.
The revisions to products should:
■ Have consistent features and
external envelope (pinout) from A to
B to C to eliminate additional system
changes.
■ Primarily focus on changes that do
not impact functionality. Users need
to be aware of what could potentially
change in each product revision so
that effort could be made to minimize
future changes, for example, dependency
on processor clock speed in
timing loops.
■ Have a consistent programming
model. Software impact must be
minimal.
■ Overlap time between products for
qualification and regression testing.
■ Be reasonably planned this way
Figure 1
during product definition; expected
changes should be thought out and
communicated. Stage multiple minor
changes to occur at a major revision
release.
■ Exceed a virtual life cycle of
10 years with the final product endof-life
timing based on technology
and market demand.
Major feature changes and enhancements
would initiate a new product that would
have its own life cycle. In turn, program
managers can evaluate the options of staying
on track or moving to a new product.
A traditional technology roadmap only
highlights the major product. In essence,
a product life cycle roadmap details the
changes anticipated for a product over its
life. A product life cycle roadmap following
this type of mapping would allow program
managers to plan technology refresh
and insertion options that are compatible
with their own program goals.
Jerry Gipper is the editorial director
of Industrial Embedded Systems.
Jerry has held a variety of positions
in systems engineering, sales, product
marketing, business development, and
strategic planning. During his career
at Motorola, he had the leadership
role in the worldwide rollout of more
than 25 major and very successful
product lines. He has written numerous
articles and papers for the industry,
and has spoken at various conferences.
Jerry currently supports VITA
with marketing services. Jerry holds a
Bachelor of Science degree in Computer
Engineering from Iowa State University
and a Master of Science degree in
Computer Engineering from San Jose
State University.
RSC# 10 @www.mil-embedded.com/rsc
For further information, contact Jerry at
jgipper@opensystems-publishing.com.
10 / 2005 MILITARY EMBEDDED SYSTEMS Resource Guide