Slashdot Mirror

← Back to Stories (view on slashdot.org)

Software Diagramming In Embedded Systems?

Posted by timothy on 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?"

2 of 52 comments (clear)

  1. Real Time UML by H0p313ss · · Score: 2, Interesting

    There are a number of commercial UML solutions for embedded and real-time systems. e.g. Rhapsody which with IBM's acquisition of telelogic becomes the natural upgrade path for system development with UML.

    --
    XML is a known as a key material required to create SMD: Software of Mass Destruction
  2. Ditch diagrams. I'm serious. by Cyberax · · Score: 4, Interesting

    Ditch your diagrams. They're far too often used to:
    1) As a thing to show boss that you're working.
    2) Unnecessary cruft which no one uses.

    About the only case where diagrams are helpful are FSM diagrams.