Data Flow Diagram or UML for systems analysis and design?

[Battousai001]

Hi, I am currently thinking of whats better to learn UML or data flow diagram (DFD) for systems analysis and design? I am currently reading a book about UML and planning on learning it. I have learned DFD back in college but forgot most of the basics of it. I am not sure if UML and DFD should both be learned if you want to just familiarize yourself again on some stuff about systems analysis and design? and is UML part of systems analysis and design or just a prerequisite for object oriented programming? Thanks in advance for any replies!

 

[Markbnj]

In my opinion UML is a "bigger" concept than DFDs. UML tries to prescribe a whole methodology and interrelated set of diagrams to capture different parts of the logical model of a system. So you have class diagrams, message flow diagrams, state transition diagrams, whatever. I doubt anyone not on a government contract has used them all.

You can't go wrong by learning the essential parts of a model at the "brick" level. So knowing what a DFD is and how to interpret one, or an entity relationship model, class diagram, event flow, etc., is a good thing.

 

[trexpesto]

UML, for sure. Some diagram types are always used, some are more rare to see in actual use.

Download the Free community edition of MagicDraw, you have to sign up to download from
http://www.magicdraw.com/main....o&cmd_show_community=1

If you get really into it, check out AndroMDA. Model-Driven-Architecture. You can define your application model in UseCase, Class, and Activity diagrams, with a couple special stereotypes, and autogenerate your application including front and back ends for several target configurations. Very pluggable and extensible code generators.

 

[Battousai001]

Thanks for the replies, I think I will be finishing the UML book I am currently reading although it is an older UML book.