We’re experts in Agile Embedded software development
We took a dare that Agile practices (particularly TDD and Continuous Integration) were impossible to implement in anything but desktop or web environments and languages like Java or C++. We ended up doing pioneering work to bring the value of Agile methods to embedded software development. Ha. Showed them.
Traditional waterfall-like approaches have failed and fail more spectacularly as embedded systems become ever more complex. Go Agile with our resources below.
Gannt Charts and critical path planning were first employed in the factories of the early 1900s—half a century before modern software development. Software teams are not factories, nor is software best managed as a linear production process. See more…
Embedded Test-Driven Development Tools
These tools were originally developed internally for client embedded projects. We’ve evolved them over time and have now made them open source. While geared towards embedded development, these tools are useful for Test-Driven Development in any C project.
The practices and techniques that inspired the development of these tools are addressed in the papers and resources that follow.
Despite a prevalent industry perception to the contrary, the agile practices of Test-Driven Development and Continuous Integration can be successfully applied to embedded software. We present here a set of practices, platform independent tools, and a new design pattern (Model Conductor Hardware – MCH) that together produce: good design from tests programmed first, logic decoupled from hardware, and systems testable under automation. Ultimately, this approach yields an order of magnitude or more reduction in software flaws, predictable progress, and measurable velocity for data-driven project management. We use the approach discussed herein for real-world production systems and have included a full C-based sample project (using an Atmel AT91SAM7X ARM7) to illustrate it. See more… [PDF]
» Mocking the Embedded World: Example Project [ZIP]
(full sample project distributed at Embedded Systems Conference Silicon Valley 2007)
Setup & use instructions (for Windows):
- Unzip the archive. Source files are in the \src directory; all system and unit tests are found in the \test directory.
- Install the Ruby scripting language interpreter by downloading and running the One Click Installer. Version 1.8.5 was used with this example.
- After installing Ruby, run ‘gem install rake’ at a command line to install the Rake tool (Rake is Ruby make).
- Install IAR’s Embedded Workbench for ARM. Version 4.41A (188.8.131.521) was used for this example.
- From the root of the project run ‘rake -T’ at the command line to list all rake tasks; run ‘rake test:units’ to build and run all of the project unit tests.
- The tools we created for unit testing & mocking and building the project are significantly improved today over the tools included in this sample project. Please see links above to download the publicly available, free tools.
- The system tests are viewable in test\system of the sample project. However, without a miniLAB device and an Atmel AT91SAM7X ARM7 demo board, these tests cannot actually be executed. Note, however, that the unit tests are fully executable without hardware.
Top-down design has long been talked about as a very efficient way of developing an embedded system. Although, many attempts at actually implementing a real product in this fashion has led to disaster. We present a design methodology, Feature-Driven Design, that focuses on the implementation of features instead of modules of code that gives way to architectures that evolve naturally and are much easier to understand and maintain. This way of development is fueled by unit test frameworks and automatically generated mocks, so that that designs can materialize from high level ideas and iterative refinement. See more…
Today, quality in embedded software is generally tied to platform-specific testing tools geared towards debugging. We present here an integrated collection of concrete concepts and practices that are decoupled from platform-specific tools. In fact, this approach drives the actual design of embedded software. These strategies yield good design, systems that are testable under automation, and a significant reduction in software flaws. Examples from an 8 bit system with 16k of program memory and 255 bytes of RAM illustrate these ideas. See more… [PDF]
Full Model Conductor Hardware design pattern example code referenced in our paper:
Copyright © Atomic Object LLC. — +1 616 776 6020 — Contact Us