Software Diagramming In Embedded Systems?

Posted by timothy on Wednesday June 25, 2008 @08:01AM from the can't-be-completely-obscure dept.

afd100 writes "I work for a medium-sized company building embedded systems using C. As of yet, we do not have a great design methodology, but it is something we're working on. For the last 7 years now, we've been documenting our embedded software in an IEEE'esque Software Detailed Design, and using a very cryptic block diagram to explain our software. What does the embedded software community at large currently use to graphical represent their software or do they even try this? Since the programming is functionally decomposed, is UML the right way to go?"

1 of 52 comments (clear)

Min score:

Reason:

Sort:

Unique diagrams by JCSoRocks · 2008-06-25 08:20 · Score: 3, Funny

Personally, I just refer to this diagram. It's the 42 of diagrams. You don't need any others.

--
You are using English. Please learn the difference between loose and lose; they're, there, and their; your and you're.