If you want to model single mechanisms of an embedded C project, UML is a good solution. UML doesn't scale well to model extended projects like eCos or Linux on the whole. In that case, in my opinion, it's better to use "Lightweight Dependency Models" (LDM) (http://www.lattix.com/products/products.php), this can give you an idea of dependency layers and building blocks of the target software.
By the way, if you are interested in UML models of Linux 2.6 components, this is a good link: http://www.softwarerevolution.com/jeneral/open-source-docs.html A good documentation for eCos (with different diagrams) is the book of Anthony Massa: http://www.amazon.com/Embedded-Software-Development-Anthony-Massa/dp/0130354732 Regards, Emilio Monti -- Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
