BEFORE & AFTER MARKET (BAM) BLOG: Jet fighters and the family car will have several things in common in the near future. When a disruptive technology is developed, prior generations of similar technologies are significantly impacted. In the consumer market, customers can generally adopt new technologies rapidly if the price point is right. Conversely, higher-value equipment with long operating life times does not have this luxury. Manufacturers of prior generations of military, space, and aerospace equipment may find their supply chain disrupted as cost-conscious vendors adapt to a more volatile market cycle.
John Rynearson, technical director of VITA, is the first person to be inducted into the newly created VITA Technologies Hall of Fame. The news took him by pleasant surprise, announced during today’s VITA Standards Organization (VSO) meeting in Scottsdale, AZ, in front of his friends and peers in the industry. After the announcement was given by John McHale, editorial director of Military Embedded Systems magazine, the room filled with applause and congratulations.
Before & AfterMarket Blog (BAM). At first glance, having 2,000 component suppliers to choose from -- versus 200 – is a good thing. Competition drives down prices and component selection appears bountiful. In the electronics supply chain, though, things don’t always work that way. In fact, the “2,000 vs. 200” equation is downright dangerous. Almost any vendor can sell a component, but not all vendors are authorized to do so. This is a big distinction.
One of the most common problems executives face is making business decisions about technologies with which they are not familiar. As they survey the crowded marketplace, corporate leaders often rely on information from self-interested vendors, or so-called conventional wisdom.
As the title of this blog implies the recently-approved SAE standard AS6081 is not applicable to authorized component sources such as Rochester Electronics. This standard only applies when the purchased product comes from the non-authorized – also called “independent” or “broker” — market as outlined in section 1.2 of the standard. It should also be [...]
Signal Integrity (SI) is becoming an increasingly critical consideration for designers of OpenVPX systems. While system integrators first confronted some SI issues as the embedded industry made the performance advance from Gen1 at 3.125 Gbaud to Gen2 at 6.25 Gbaud signaling, the current transition to Gen3 >10 Gbaud signaling rates, nearly doubling the bandwidth of Gen2 OpenVPX, requires a significant increase in the level of tools, capability, expertise, and know-how to ensure successful design and implementation of a robust latest generation, OpenVPX system.
Once upon a time, long, long ago, the only kind of dynamic software test was a system functional test. The battle against unreliable software was exclusively fought with complete system test in which an application’s worth was proven by reference to a set of requirements, a set of test data, and expected results. While this [...]
While Ada offers many features that act as safety guards at run time, by raising exceptions when a violation is detected, some of these features may be too complex to guarantee a safe execution before the program is run. This is the case for example of pointers, which may be used to create arbitrarily complex shared data structures in memory. SPARK is a subset of Ada that forbids these features, most notably pointers, in order to be able to provide strong guarantees at compile time. A preview of the next revision of SPARK called SPARK 2014 is already available, as well as the associated verification tools.
So, the software development process is all thought through, planned out, documented, structured, in place. You’ve invested good money in test tools that can generate as many artifacts as you could possibly need. You have reports from static analysis, dynamic analysis, functional test, unit test, object code verification…. Nothing has been left to chance. Everything [...]
In the good old days, before writing software became “software engineering,” code development was a black art practiced by weird nerdy kids straight out of college. For them, coding was by no means a structured discipline. If you managed to get them to communicate, they might tell you that they were hacking code together and using ad hoc test data to see whether it did what it was supposed to do when they executed it.