Books for learning EA / beginners books on UML 2.x

[dana n]

I've been tasked with learning UML 2.x, use case modeling with EA, and systems architecture modeling with EA. My background is in systems administration with some database design (still learning). I have not been tasked with modeling software, nor am I a programmer (I've scripted in Perl and Python to automate administrative tasks, working in Python exclusively these days). I have only a rudimentary understanding of object-orientated programming, but have been told knowing OO programming is not a pre-requisite for learning UML.

I've also been told the best way to learn UML is to read the OMG standards documents. I think it's good to have standards documents as a reference, but think it's beyond me as a beginner to learn UML from standards docs alone--doesn't fit with my learning style (I need examples and interactivity, if nothing else from reading a book from an engaging author).

1) Are there any good books on UML 2.x that use EA? I know there are online tutorials and PDFs for EA, but I prefer "dead tree books" that I can annotate and easily carry around with me.

2) Failing #1, what are some good books on UML 2.x and use case modeling suitable for someone with my background?

3) Is it appropriate for someone with my background to expect to be able to learn UML from the standards documents alone?  

Looking forward to getting started, but feel a bit intimidated with the directive to "Learn UML from the OMG standards documents." The subtext being that all or most UML books are merely interpretations of the standard and might lead me down the wrong path and encourage incorrect practices. True enough, I'm sure some books written by consultants have ideosyncratic ways of "doing UML", and everyone has an opinion, but surely there must be something reasonably faithful to the standards without reading like a phone book.  

Thanks very much.

Dana

[robbierzzz]

For school I had to buy the following book (probably there is already a newer version of it around...)

UML Distilled Third edition, a brief guide to the standard object modeling language - Martin Fowler

ISBN: 0-321-19368-7

[Paul Lotz]

Yikes!  I don't agree that the best place to start learning UML is reading the OMG specifications.

I have read the Fowler book mentioned above but I prefer Learning UML 2.0 by Miles and Hamilton.  I think that is a great place to start.

At a later phase you may want to read Applying UML and Patterns, 3d ed. by Larman.  This has good details on how to use UML but you will probably want some experience with UML first.

Use Case Driven Object Modeling with UML: Theory and Practice (Rosenberg and Stephens) use EA and describes a process (which most UML books don't do).  It also concentrates on use cases, so it might be of interest to you.  Do keep in mind, though, that it offers a somewhat narrow, if effective, perspective on UML.

I just obtained A Practical Guide to SysML: The Systems Modeling Language (Friedenthal, Moore, and Steiner), which I noticed does use EA for some of its diagrams.  If by systems modeling you mean SysML models (which need not be the case) you might check out this book.  Systems Engineering with SysML/UML (Weilkiens) gives a good overview of of SysML but it is not tied in any way to EA.

Finally, if you want to understand the underpinnings of UML and SysML themselves you might want to read UML 2 Certification Guide (Wilkins and Oestereich).  I still think that would be easier than reading the specifications.

Anyway, I really think the Miles and Hamilton book is the best place to start.

Good luck!

Paul

[dana n]

Thanks R. and Paul. I've just ordered Learning UML 2.0 (already been a fan of O'Reilly books). Will see how I do on that one and graduate to the others.

Dana

[dana n]

Here are the books I bought, and some comments:

UML Distilled - My favorite so far. Clear, concise, and had a very nice summary of development process options (e.g. iterative vs. waterfall, adaptive vs. predictive, etc. Many good insights and just the right amount of history of UML (to put it in an appropriate context). Liked that the author wasn't overly pedantic and beholden to the letter of the UML law as it were (e.g. it's ok to deviate and include non-UML diagrams where it's handy to do so). Nice comments on what UML is and what it is not; what it can accomplish and what it can't. A fabulous intro.

Learning UML 2.0 -  Have only gotten to the Use Case chapter, but I've had good luck with O'Reilly books throughout my career.

UML Demystified - I've had good luck with other books in this series, so I picked it up (Databases Demystified is very nice). Am on the Use Case chapter. I like having multiple sources for each concept. It's a bit like the Dummies series but has more content, is more concise, and isn't beholden to all the annoying cutesiness of the Dummies series.

UML 2 for Dummies - Ok, so this is scraping the bottom of the barrel. But it got good reviews on Amazon and I found it cheap. Never know where a breakthrough gem will appear for understanding a particular concept. I like to give myself every opportunity to get it right.

So... that's enough elementary UML books.

I'm looking for a few good books on basic software development (not just OOP). Things like Software Configuration Management--e.g. using concurrent versioning (I use WinCVS at a basic level and don't know much about branching, merging, etc), numbering software releases, etc.

Code Complete by Steve McConnell seems highly recommended. Would that be a good choice for me as a scripter / non-programmer? Rapid Application Development by McConnell, though seemingly long in the tooth edition-wise, also seems highly regarded. But I need to learn as much as I can about Software Configuration Management as I can. Picked up a cheap copy of "Code Leader" and that has a chapter on CVS. But I'd like more info.

For OOP stuff, I found a cheap copy of OOP Demystified and like that so far. I'll check out the other books on OOP recommended here when I'm finished with that one. And I suspect I'll need to read about Patterns at some point--that will come later.

Thanks again for all the great suggestions and help.

Dana

[Paul Lotz]

Head First Software Development by Pilone and Miles has a good chapter on version control and many other relevant topics.  I recommend it.  For version control specifically I found it was enough to read through the TortoiseSVN user guide (which in turn replicates sections of the Subversion user guide) and then just work with it for a while in the context of my daily workflow.  It didn't take long to learn.  (Well, we haven't had to tackle any really difficult version control use cases yet, but everything we have tried has been straightforward enough.)

[dana n]

Head First Software Development by Pilone and Miles has a good chapter on version control and many other relevant topics.  I recommend it.  For version control specifically I found it was enough to read through the TortoiseSVN user guide (which in turn replicates sections of the Subversion user guide) and then just work with it for a while in the context of my daily workflow.  It didn't take long to learn.  (Well, we haven't had to tackle any really difficult version control use cases yet, but everything we have tried has been straightforward enough.)

Thanks Paul. I'll check that out. Heard good things about that series. Evidently they have a good title on OOP and a good one on Patterns as well.

I'm interested in Subversion, but we'll be using WinCVS for the forseeable future.

Dana

[KP]

Code Complete by Steve McConnell seems highly recommended. Would that be a good choice for me as a scripter / non-programmer?

I'm more than happy to recommend it for all programmers ("Best. Book. Ever." as Comic Book Guy might say). For a scripter / non-programmer? Don't know, I'll dig out my copy and try to look at it with a non-programmer's eyes and get back to you. You may find more joy with "The Pragmatic Programmer" by Hunt and Thomas which is very readable and less about programming, more about pragmatism.

[dana n]

Code Complete by Steve McConnell seems highly recommended. Would that be a good choice for me as a scripter / non-programmer?

I'm more than happy to recommend it for all programmers ("Best. Book. Ever." as Comic Book Guy might say). For a scripter / non-programmer? Don't know, I'll dig out my copy and try to look at it with a non-programmer's eyes and get back to you. You may find more joy with "The Pragmatic Programmer" by Hunt and Thomas which is very readable and less about programming, more about pragmatism.

Thanks KP. Which edition of Code Complete should I get? There's a newer, more expensive edition. Then there's an edition that's quite a bit older (probably 8 editions total). I am on a tech book-buying binge-- I like having the "right" books ("best of breed") available in my office when the Spirit Moves Me. Can I get by with the 2nd to last edition of Code Complete?

Somewhere, I've heard good things about the Pragmatic Programmer, so I may pick that up as well (used, hopefully). Pragmatism is good. I don't have the time or inclination to get into the rarefied air of academic / "holy war" debates on these topics. Actually, I do have the inclination to some degree. Just not today anyway in any great measure. :-) I want to build things that work well, but work well enough. Perfection can be found nowhere in reality in any case. Something I constantly need to remind myself of.

Paul, I found a used copy of Head First Software Development, so that one's on its way.

Thanks again guys.

Dana

[dana n]

Bump.

KP, did you determine what edition of Code Complete you have and would recommend?

Thanks.

Dana