Editing contact

Show | All Contacts

Please provide your contact information

Your name *
Email address *
Company name
Company location
Company website
Office phone
Mobile phone
How did you find us? *	- Please choose - Web search Referred by a colleague Referred by another company Attended training by James Grenning James Grenning's book on TDD Read a paper or presentation by James Saw James speak at a conference Linked In X.com Link from James Blog Link from another website Other
What is your interest? *	- Please choose - Test-Driven Development Training - Self-paced Test-Driven Development Training - Self-paced - with Review Sessions Test-Driven Development Training - Live on-site for my team Test-Driven Development Training - Live on-line for my team Test-Driven Development Training - Live on-line for me Remote Delivered Legacy Code Workshop Publicly offered Test-Driven Development Training To talk to James to better understand why TDD is important I want to get started with Agile for embedded To invite you to speak at a company event I want to submit a TDD experience story I'm an alumni and would like access to video refresher materials To report a problem with your website I'm skilled at agile and TDD embedded and interested in teaching and coaching others Other
What is your time frame? *	- Please choose - Immediate 1-2 Months 3-6 months Next year Other

You can leave a detailed message here:
Scott Ambler suggested I reach out to you. I am being challenged to apply TDD to a new embedded product design. I have read multiple articles and I am investing in a variety of books on the subject but I am stymied by one aspect of TDD that never does seem to be addressed. I believe the reason it is not being addressed is because all of the examples that I have been exposed to so far have focused on software development. As an embedded designer I am very much involved in physical stimulus, i.e. inputs from digital input pins, ADC’s, etc. and my outputs will be digital outputs, PWM signals, maybe some motor controls, etc. The actual physical product will not be available for ~6 months. I am being provided operational scenarios for how the product needs to operate and I am conceptually visualizing the various tests to developed, but what I am realizing is that I am needing to develop an emulator for the hardware that this product code will need to run against in order to create the tests for the product code needing to be developed. From an embedded perspective, is this the correct thinking for TDD development? When I broached the idea of needing emulation prior to TDD development, they were surprised that such a thing was needed. Is there another thought process concerning embedded TDD that is out there that I haven’t been able to locate? And if so, can you point me in the right direction? Any insight would be grateful. Regards, Brett Davis Sr. Electronics Design Engineer ASSA Abloy EMS&OEM Group 10027 S. 51st Street, Suite 102 Phoenix, AZ 85044 623.582.4626 ext 7176

Remote delivery timezones

Number of people

Initial contact date

Next follow up date

Notes

Show | All Contacts