Amazon’s Send to Kindle Desktop App: Amazon also has a desktop app for both Windows and OS X that lets you send compatible files to your Kindle just by right-clicking on them on your computer and pressing “Send to Kindle”. This is especially handy if you send a lot of PDFs or DOC files.
Chapter five starts the models use cases. I think this is the best model to start with. The diagram can be used to set context and the text can describe a task. While I agree that Use Cases can be used at multiple levels, my understanding is that it was primarily designed to be at a “task” level: a term that is need of a definition. I was a little sad to see that Mr. Daoust doesn’t take that up well. I was also surprised by the use of the terms “Main Success Scenario” and “Extensions”. Those are sucky names and I will need to beat up on my buddies on the UML board if those terms came from those nasty specifications.
Chapter six is Activity Diagrams and that turned out well. I would then skip to chapter 19, Data Models Using Class Diagram Notation as I think that is far more useful to business analysts than Mr. Daoust’s desire to use Class Models (mostly we are talking about the use–or omission in my case–of the methods). Then onto chapter ten on State Diagrams. The rest of the chapters are there because UML says they are there but, while you may use them, you probably won’t. Anyway, you wouldn’t use but the main four with any kind of frequency so you would suck at them and it would probably be better not to try to model it.
an excellent description of Structure Diagrams vs Behavior diagrams (the two main subcategories of UML diagrams).
A nice section that describes “which diagrams do I create and when.”
Good ideas you might not have thought of. For example: use Communication Diagram notation to create Context Diagrams and use Class Diagram notation to create Data Models.
Posted from Diigo. The rest of my favorite links are here.