Third-Party software will definitely reduce the price will it will lead to a delay in product response time. I should suggest rigorous testing will definetely will lead to management of risk levels and in better controlling.
There are always cases where original product company/owner wont be able to even test the third party software. For example take the case of the new phones that support third party apps. People install third party softwares and that can reduce the performance or battery life of the phone! Just did a search and see what I saw.
I totally agree prabhakar_deosthali! Companies should have a formal and rigorous code goverance policy and prCcess. That process should be adaptable to external developers and be included in the SOW and contract. The FDA already has s/w code governance for medical devices as failure can result in loss of life. Ideally any company with a s/w interest should have the same mindset.
I'm not thrilled with EBN providing Coverity free advertising for their s/w dev services. However, the article has merit if it reminds us code goverance is vital in order to prevent catastrophe.
I would suggest that it is the responsibility of the management team that selected the third party software to test and ensure that said software will not cause problems after the fact. The "lets not test and take our chances" approach can be too costly, why would they adopt such a mind set?
Third party softwares usually makes into the final product without rigorous testing that we expect to happen. The sense of responsibility kind of disappears when software is taken from third party. The attitude becomes like 'Arent they supposed to test it?' . And when things fail in the field then the engineering and testing team kind of blames the senior management for out sourcing! And guess what happens to the senior manager who selected the third party!!
This doesn't make sense to me. Why wouldn't third party code be subjected to rigorous testing? Even if the company providing the code certifies it, the ones incorporating the code in their systems are the ones who are responsible for it. Do they perform rigorous testing once the code is incorporated in their system?
I am amazed at how many companies employing third party software aren't too concerned about integrity and standards. Not only does this make them susceptible to viruses and malware but this could also seriously damage their reputations. I think there should be an across the board standard that all parties need to meet.
Andy, you are right. There could be a chance of threat through third party software. I know certain equipments may exhibit a strange response in critical application, where malware is functioning at bank end. In most cases, the malware is embedding in hardware for spying and data retrieval purposes. In such cases, procuring software through reputed and trusted vendors are the only solutions. Since these malwares have time bound responses, most of the security software may fail to detect them at initial stages.
Normally the purpose of getting a third party to develop part of your software is to reduce that much burden on the internal team. If you select a third party which has its own internal stadards of testing their developed code before they deliver it to you then the duplication of the testing of that code can be avoided. The vendor should self-certify such code and also provide the test vectors and the assciated results. Such kind of self certification is required when you are getting the third part code to integrate into your product.
EBN Dialogue enables and encourages you to participate in live chats with notable leaders and luminaries. Not only editors and journalists, but the entire EBN community is able to comment and ask questions. Listed below are upcoming and archived chats.
Thailand Stages a Comeback Join EBN contributor Jennifer Baljko on Thursday August 23, 2012, at 11:00 a.m. EST for a live chat on how electronic manufacturers in Thailand have shored up their supply chain to reduce the impact of future natural disasters.
Microsoft Surface: Potential Winners & Losers What are the implications for the electronics industry supply chain of Microsoft Corp.'s decision to launch its own tablet PC? Join industry veteran and EE Times' systems and OEM expert Rick Merritt on Tuesday, July 3, at 12:00 pm EDT for a Live Chat on this subject.
Join EBN contributor Jennifer Baljko on Thursday August 23, 2012, at 11:00 a.m. EST for a live chat on how electronic manufacturers in Thailand have shored up their supply chain to reduce the impact of future natural disasters.
Peter Drucker famously said "Trying to predict the future is like trying to drive down a country road at night with no lights while looking out the back window." Yet in the razor's-edge world of electronics—with a lean supply chain and just-in-time demands—the need to know the future is vital.
While no one really can accurately predict the future, we can take guidance from another Drucker saying which is the best way to predict the future is to create it.
You've heard the saying "the No. 1 supply chain risk is your people." That hasn't always been the case. But today's complex global supply chain requires a new type of multitalented employee. It's one who understands, finance, marketing, economics, is savvy with technology, graceful with relationships and can think analytically.
Where are these people? Are universities properly preparing the next generation supply chain professionals? How do train your existing workforce for these new, demanding positions?
Brian Fuller, editor-in-chief of EBN, will lead a 60-minute Avnet Velocity panel discussion that will ask and answer these and other questions swirling around today's supply-chain talent challenges.