Software Prototyping
In my recent blog entry on the product development process (way down, near the end of the entry), I wrote the following:
"I continue these sorts of tests, building more and more complexity, until I am satisfied that my circuit is basically functional. Then, using the test code that I have created as a model, I begin to write the real software for my product. As my software grows, to complete the full functionality of my design, I sometime find it useful to drop back to my 'test software' to prove or test some function that I had not previously tested (or completely tested) during the bring up process."
At the time, I failed to drive home the true point of this paragraph, which is; 'Create a software prototype'. A few days after posting this, I picked up the latest issue of "Embedded Systems Design" and read the 'break points' article by Jack G. Ganssle on "Creating software prototypes". His article described, so eloquently, a topic that which I only spent one paragraph on (perhaps I was tired due to the length of my post). Here is a link to that awesome article:
I hope to follow up my prior blog entry with a series of posts further explaining some of the steps in my development process (using illustrations and examples). Having come across this very informative article on 'Software Prototypes", I feel that there is little to more that I can add on this subject.
Happy Embedding!
Gene
- Comments
- Write a Comment Select to add a comment
To post reply to a comment, click on the 'reply' button attached to each comment. To post a new comment (not a reply to a comment) check out the 'Write a Comment' tab at the top of the comments.
Please login (on the right) if you already have an account on this platform.
Otherwise, please use this form to register (free) an join one of the largest online community for Electrical/Embedded/DSP/FPGA/ML engineers:
