I am working on a kernel-related project (specifically related to the TCP/IP stack of the kernel).I need to build some models to describe the functionality and components of my system.Initially I thought about using a Class Diagram, as it can describe the general architecture of my system. But it doesn't make sense since my code is VERY structured (written in standard C).I also thought about DFDs: they'd describe the processes of my system, and how the data is flowing. But they contain something which doesn't really fit in: data-storages.I have no databases here (at all).For the functionality, other team members suggested using Activity and Sequence diagrams, which is kinda okay with me, but what about the system components? So basically my question is: If I want to describe the components of my system, what do you suggest as a meaningful diagram ?Again, the project is a research low-level systems-oriented project with almost no user-interface at all.
How to model the components of a non Information System?
modeling;diagrams
Then, why don't you use UML to build a Component diagram or even a Package diagram? If I understood correctly, you want a bird's eye view of your whole architecture and that's why you don't need a class diagram, right?I guess you could even look at SysML which can provide a more systems-oriented approach.