When you get to the top levels you will have tested, well documented code. When you have all the bottom levels written and tested, start on the next level up, incorporating the lower levels and make sure that they work together and do not interfere with each other. Test each bottom level function independently using real inputs or dummy data. ![]() make each function independent of all of the others, defining the inputs and outputs. Take each bottom level block and write a function that will do what is required. When you start writing the code, do it from the bottom up. standard interfaces, etc, include them in the diagram at the appropriate levels. If you have existing libraries of some of the functions, e.g. At each level, define the inputs and outputs of each function. Continue to add more detailed levels until you can not simplify each one any more. Include flow and timing diagrams as needed. ![]() Then break each block down one level at a time by splitting it into more detailed functions. ![]() operator interface, data input, data processing, output functions, etc. In other words, start with a few broad functional blocks, e.g. Then start designing a block diagram of the software from the top down. ![]() When you are designing functional software, start with a detailed specification of what the software is supposed to do (not how it will do it). I recently ran across this post on AllAboutCircuits, and liked it so much the tab has been open ever since!
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |