I'm happy to announce I have a book coming out in early 2007 tentatively titled Beyond Agile. My co-author Dr. Hong Li and I are working on a full lifecycle book that looks at what works and what doe

This is a promo. Please feel free to use it to promote this podcast on your Website, blog, podcast, forum or anywhere else. Daryl Kulak is the host of UML in Seven Minutes. This is a weekly lesson

Are package diagrams really diagrams? Not really. But packages are a useful way to hide complexity, to make the other diagrams easier to read. Resources: My book is ?Use Cases: Requirements in Co

We at the ?UML in Seven Minutes? podcast support our troops. Deployment diagrams are the friends of the technical architect. Whether you need to communicate a network diagram, or show an application

Component diagrams are useful for making an inventory of your components and showing the interfaces. Components are coarse-grained pieces of functionality in an application or architecture. Consider

The activity diagram is a flowchart, plain and simple. You can use activity diagrams to show the logic of an individual object, with if-then-else's, loops and method calls. You can also use them to

The state machine diagram shows interesting behavior about one particular object. The boxes are states, the arrows are transitions. Use it only for those objects that have more than 1 or 2 states, an

The communication diagram (formerly known as collaboration diagram) is a twin of the sequence diagram. They both show the dynamic nature of software, but communication diagrams are better suited to m

One of the most popular dynamic diagrams in UML is the Sequence Diagram (where business systems are concerned anyway). See below for an example of a sequence diagram. Next week: Collaboration Diagra

Static diagrams, like the Class Diagram, show how things are, with attributes and relationships. Dynamic diagrams, like the Sequence Diagram, show action, like one object calling another object. Re