232 posts categorized "Embedded System Engineering"

05/22/2013

Got Ugly Code? Test to See if Quality Runs Deep

In today’s celebrity culture, inner beauty isn’t always a valued trait. But when it comes to embedded software development, beauty is truly on the inside. High quality, well-designed and reliable products necessitate high-quality and highly secure embedded software. Development Testing is one of the most effective ways to achieve this.

Development Testing is a rapidly emerging category, including a set of processes and software, designed to easily find and fix quality and security problems early in the development cycle, as the code is being written. All this serves to dramatically improve time to market, reduce development costs and improve customer satisfaction.

Join us at an exclusive event hosted by Coverity on June 12th in Cambridge, England. ip.access will share some of their experiences implementing advanced testing practices and I will discuss what our research says about the latest trends and techniques in embedded software development and quality assurance.

When: Wednesday, June 12th

Time: 09.30 – 14.00 with presentations between 10.00 and 12.30, followed by lunch.

Location: Fitzwilliam College Storey’s Way, Cambridge CB3 0DG

Register: Click here

04/25/2013

M2M World Congress – London – Highlights from Day 1 of 2

VDC’s CEO Mitch Solomon is participating in M2M World Congress (one of the industry’s larger M2M-centric conferences) this week in London, and sent in the following post from the field.

First off, the event is oversold and is standing room only, a testament to building interest in M2M (…and perhaps the strong promotional efforts of its producer).  The day consisted of roughly a dozen presentations and panels, covering a broad landscape of topics.  Speakers were largely from major wireless carriers, primarily European.  Below are a few key insights (…derived from a much longer list), just hours after the last session of the day:

All speakers believe the much-anticipated M2M future has arrived, and they see rapid scaling in their business (as measured by M2M SIM card sales and deployments).  Most M2M business leaders within large mobile network operators are carrying aggressive growth targets (handed down from corporate), as their companies look to M2M to drive growth that far exceeds what can be achieved in their established voice and data businesses.

The words “complexity” and “challenges” were used almost as much as “the” and “it” during the course of the day.  The difficulties associated with actual M2M deployments were widely acknowledged, often in the same breath as the notion of how large the opportunity is.  Clever solutions to the biggest M2M deployment challenges were elusive (understandably, as silver bullets are usually are hard to come by), though familiar suggestions like “test, test, and re-test” and “standards can help” and “pilot first, then expand” were offered up. 

The only word used more than “complexity” and “challenges” was…”partner.”  Which makes sense.  It often takes partnerships to solve complex technical problems such as M2M applications.  Every carrier was touting its partnerships, some of which extend geographic coverage while others deliver value-added software and services beyond connectivity.  This is the age of M2M promiscuity, as everyone tries to seduce everyone else lest someone be left on the dance floor alone.

For a myriad of reasons, the discussions were largely focused on technology and vendor strategies (particularly carriers’) instead of OEM use cases and customer benefits (…something many audience members were a bit frustrated by).  Some attempts by panel members to address questions related to devices and OEM use cases were made, and some light was shed.  Overall, however a clear impression was made that senior people with M2M on their business cards are still working their own way up the learning curve (like many others in the industry) when it comes to specific examples of how M2M-based applications can benefit their OEM customers.  This knowledge gap could be indicative of carriers and/or senior leaders at carriers being one or two steps removed from OEMs’ application development efforts, rather than a deficiency in an expected area of expertise.

With the second and final day of the event tomorrow, my hope is that panel members will share more about how OEMs are approaching, evaluating, designing, and deploying M2M based systems.  Discussions of the supporting business cases would be particularly valuable.  If so, it will cap off a very worthwhile two days of M2M immersion in London.

04/15/2013

Don't Water-Scrum-Fail.

Agile is a great weapon available to OEMs to fight the challenges inherent in device development today. It is not, however, a silver bullet.

In a recent post, we explored how Agile projects are still finishing behind schedule, despite favorable comparables against standard V-model workflows. The truth of the matter is that Agile projects are subject to many of the setbacks as traditional ones. They can and will fail. It is more important than ever for engineering organizations to recognize what specialized or unique implementation strategies they need to use to increase their chance's for long-term success with Agile.

Many of you have heard the expression - water-scrum-fall in the past. It speaks to the reality that Agile is often implemented in some sort of a hybrid fashion – as in not true “Agile” per the manifesto. This is especially true – and important - in the embedded market. As you know, there are a ton of differences between development for an ISV and an engineering organization. The number of verticals markets, process standards, and multi-engineering domain considerations make some level of hybridization or customization necessary.

Agile hybrid
But customization does not come without its cost. For example:

  1. Light weight Agile project management tools can't cut it alone. Integrated, formal automated tooling is required to manage traceabilty across the lifecycle.
  2. Ongoing training and coaching takes center stage. Embedded engineers are creatures of comfort. Left alone for too long and they will revert to a more primitive state.

Interested in learning what else you should do and consider when implementing Agile in your organization?

Listen in to our webcast:

Tomorrow, April 16th at 12pm ET / 9am PT

How can you register?

http://bit.ly/13u7U9h

03/26/2013

3 Steps to Automate Your Way to Agile

In a recent VDC View, I wrote that "software engineering is broken." Although our industry continues to deliver new and innovative products, too often projects miss the mark. Late. Buggy. Unprofitable. We all hate these words, but hear them repeatedly. Enter Agile.

We all know that Agile enables software organizations to continuously deliver working software faster to customers (internal or external). This helps software teams to not only deliver products faster but also in tune with the changing market needs. In practice however, organizations still struggle to get the full benefits of Agile methodology because they have not fully automated their practices (development, build, test, release). 

Agile_Pies

Listen in on April 16th to hear Ashish Kuthiala, Director of Marketing at Electric Cloud, and I address the fundamental issues and recommendations you should consider as you adopt Agile: 

  1. Understanding the true drivers for adopting Agile
  2. Critical organizational, process and tooling issues to consider and pitfalls to avoid
  3. Recommendations on how to do this right by automating your processes

When is the webcast?

April 16th at 12pm ET / 9am PT

How can you register?

http://bit.ly/13u7U9h

03/18/2013

VDC to Present Embeddy Awards Live at Design West

Want to see the latest technologies and tricks for embedded engineering? Head to Design West next month in San Jose, CA!

Contact us ASAP to schedule a meeting

VDC will be attending the Design West/ESC conference from Tuesday April 23 through Thursday April 25.

At the show, we will be presenting our 9th annual Embeddy Awards. The winners will be announced Live during Thursday's morning keynote session.

So how can your company win the Embeddy award?

To be considered,

First, fill out this on-line form: http://svy.mk/WU0abA

You must also schedule a meeting with VDC to discuss the announcement that you are making at the show. You can arrange a meeting time with VDC by doing one of the following:

For Software and Tools related meetings

Contact Jared Weiner, Analyst, M2M Embedded Software & Tools at:
jweiner@vdcresearch.com or 508.653.9000 x143.

For Hardware related meetings

Contact David Laing, Senior Analyst, M2M Embedded Hardware Platforms at:
dlaing@vdcresearch.com or 508.653.9000 x146.

Haven't decided if you're attending DESIGN West yet?

Please check out the DESIGN West website for more information on the conference program as well as
information on all of the companies that will be exhibiting. You can also click here to register.

We look forward to seeing you at the show!

02/01/2013

Feeling Insecure?

Then come see my presentation on secure device development best practices at Embedded World!

The device development landscape is changing rapidly. The potential cost of security risks looming on the horizon is already causing many OEMs to reevaluate their engineering solutions and processes. I will discuss some of the steps you can take and products you should use when building next generation connected devices.

When: 3:00 pm CET

Where: Embedded World - Nuremberg, Germany

 

Want to meet at Embedded World?

Please contact us if you would like to meet up while in Germany. We are interested in speaking with vendors launching new solutions and engineers looking to share experiences.

 

12/31/2012

Your Health… There’s an App for That

The advent of the smartphone has inexplicably changed the way we live – including how we take care of our physical selves at home. Such technology is making a number of traditionally hospital-only services and extended their availability to the general public at an affordable cost. Smartphones, combined with a peripheral sensor and mobile application, are capable of measuring temperature, heart rate, blood pressure, and other vital parameters. Such solutions make the smartphone a chief contributor to the rising adoption of telehealth systems and away-from-hospital services.

Scandu, a relatively new personalized health electronics company, has developed a product targeted towards fitness enthusiasts, dieters, and data lovers that measures six physiological parameters in about 10 seconds. The Scandu Scout, available in late 2013 and selling for less than $150, takes readings with one small sensor-studded device that transmits data to the smartphone app via Bluetooth. This device is part of a new generation of consumer health tools that enable users to make informed decisions about their health and whether they should see a doctor – further decentralizing medical services.

Another health electronics manufacturer, Zeo Inc., provides consumers with a sleep management solution that records and graphs users’ sleep patterns throughout the night. The Zeo Sleep Manager transmits data via Bluetooth to a nearby iPhone or Android smartphone through three sensors on a headband detecting electrical activity in the skin of the forehead. By knowing how much restorative REM and deep sleep users actually get, they can better manage their health and overall wellness without conducting a professional sleep study.

The smartphone is a flexible medium in which consumers are familiar with and comfortable using. With different connectivity options, growing computing power, and extensive developer communities, smartphone devices will continue to be ideal for consumer health manufacturers in centralizing their solutions. It’s a win-win for end users and manufacturers alike – manufacturers have a steady platform to work off of and end users live healthier lives.

And with our last blog for 2012, VDC would like to wish everyone a safe and happy New Years!

Embedded Security: The Bark is Bigger than the Bite, Part 2

In part one of this blog, we discussed findings showing the limited security actions taken to date in the Industrial Automation and Energy/Power industries. Unfortunately, the gap between stated interest in security and the actions taken to address these concerns is not limited to this vertical. For example, 29% of engineers in military/aerospace and almost 38% of automotive engineers reported their current project involves no security actions.

Google has received a great deal of press about their progress in this area, developing their self-driving car. Aaron Robinson, a columnist with Car and Driver magazine wrote about security issues, as they relate to this notion of an autonomous car.

“But one thing is certain: Throughout human history, safety has typically lagged invention. The wheel came before the brake, the car came before the seatbelt. Likewise, the internet’s innovation continues to outpace its protections” – Aaron Robinson

Now I love many of the advances information technologies have enabled in even just the last few years. But turning over my keys to the IT department of Google or some other tech company, especially since I’ve seen lack of security measures? Suddenly “kernel panic” or the “blue screen of death” take on much more literal meanings.  

Eliminating the security interest-action gap will be one of the primary challenges facing OEMs across several verticals. Embedded solution providers should align their marketing and services initiatives. There is a large opportunity awaiting the vendor(s) able to encourage and then help navigate when OEMs take these important steps to address security.

 

UPCOMING RELATED RESEARCH:

Also in the next couple of weeks, the Embedded Software team here at VDC Research finishes publication of a series of vertical market reports. These studies examine embedded developers’ demand and requirements for commercial OSs and software development tools within key vertical markets.

Volume 1, covering embedded software technologies in the Automotive vertical is available now. Volume 2, available later this week, looks into the Industrial Automation and Control (IAC) and Energy / Power industries. Volumes covering medical devices, military/aerospace, and mobile phones will follow shortly.

Coming in 2013:

VDC’s Voice of the Customer Series: Security & The Internet of Things will give you the information you need to formulate and implement a best-in-class security strategy. From cars to smart-phones to the factory floor, security is becoming an increasingly critical consideration for enterprises, consumers, and the OEMs who provide them with a rapidly expanding range of Internet-enabled devices. This service will help you understand how organizations are approaching the big decisions of security risk management, technology and vendor selection, device deployment, and more. Learn about consumer awareness and perceptions regarding security across a range of device classes. This service is based on extensive primary research of engineering organization, enterprise and consumer behavior.

Embedded Security: The Bark is Bigger than the Bite, Part 1

Security has been top of mind with most executives of leading embedded suppliers who we spoke to in the past year. This should come as little surprise given the growing awareness of the potential impact of security breaches. As today’s devices and systems grow more complex and connected, this threat is growing exponentially. Time and again, we hear of some hacker or industrious engineering student demonstrating, either maliciously or as an educational warning, that a linked network may only be as secure as its most vulnerable element.

In a recent conversation with one of the foremost automated test and verification tool suppliers, an executive warned that while they hear overwhelming interest in security concerns across all verticals, actual investment in addressing the issue is not close to matching this professed concern.

Our findings do indeed confirm that within the Industrial Automation and Control (IAC) and Energy/Power industry, a distressingly high percentage of current projects involve no action to limit potential security issues. 

Security actions take four jpeg

Just over 42% of the engineers responding from IAC and energy/power market indicate no proactive actions have been taken to address security concerns on their current project. The fact that 40% state their current project has no specific security requirements should offer little relief. Our research indicates that many projects without specific security requirements certainly ought to have them. Lack of security prevention or mitigation does not mean no security threat exists. What should also be alarming is the percentage of respondents “very confident” their security requirements would be met on their current project was in the single digits!

This represents a large, potentially lucrative market opportunity for suppliers of security solutions. But it should be unsettling to everyone else with even a passing understanding of the potentially catastrophic impact of vulnerabilities in these markets. Heard of Stuxnet anyone?

 

In the next couple of weeks, the Embedded Software team here at VDC Research finishes publication of a series of vertical market reports. These studies examine embedded developers’ demand and requirements for commercial OSs and software development tools within key vertical markets.

Volume 1, covering embedded software technologies in the Automotive vertical is available now. Volume 2, available later this week, looks into the Industrial Automation and Control (IAC) and Energy / Power industries. Data in the exhibit above is based on findings from this volume.

FOR MORE INFORMATION:

For more information on security findings, including statistics from other verticals, please take a look at part two of this discussion, coming here soon.

12/28/2012

It Gets Better

The same end-of-one-year reflection that inspired our embedded software Top 12 of 2012 (part 1 and part 2), encouraged us to take a look back at a metric we continue to track: schedule performance.

In VDC’s 2012 developers survey, 35.3% of the respondents said their current project was behind schedule. Just last year over 40% reported schedule slippage. So perhaps 35% is an improvement; but it’s hardly a statistic worth boasting. With an average of twenty five embedded engineers per project, any delay can be detrimental to development budgets, not to mention the reputational damage.

Despite an understanding that adherence to schedule is crucial to project success and that management should focus on ensuring execution conforms to it, on-time delivery difficulties persist. In order to get the maximum benefit from minimal effort through the full development lifecycle, engineering organizations need to optimize the efficiency and accuracy of their team and resources.

The good news is our research suggests the schedule adherence improvement of this past year may be the start of a trend rather than an anomaly. We see more and more engineering firms applying the right tools, methodologies, and processes.

Some of our findings showing potential for improved schedule performance include:

  • Embedded suppliers continue to make functional improvements to the software and systems lifecycle management (SSLM) tools they offer. Beyond these advances, there is broader use of SSLM solutions by developers which offers several potential benefits. For example, effective requirements management solutions help avoid misunderstanding and unrealistic expectations while modeling tools can encourage greater code reuse.
  • There is increased adoption of Agile methodologies both in full adherence to the methodology and in a hybrid approach combining iterative aspects with elements from other methods.
  • Improving efficiency in the development of today’s devices which often require a tight coupling of electrical, mechanical, and software elements requires an evaluation of processes across project boundaries. This reinforces the potential benefits of cross-domain engineering integration, which we see is increasing.

These trends are encouraging. Our findings have shown that organizations using SSLM tools are more successful in meeting deadlines. Likewise, less developers using Agile methods (28.8%) or investigating cross-domain integration (26.2%) report being behind schedule than the average for the industry at large (35.3%.)

If embedded suppliers continue to improve their offerings and provide the support to make sure they are implemented appropriately, perhaps our 2013 findings will confirm the schedule improvement value of these solutions.