As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 11 years ago.
After searching for hours on internet i am not able find sites which gives good material for UML reference.
can any body suggest which site/book is good for UML reference?
Maybe this collection of UML cheat sheets and reference guides is what you´re looking for: http://modeling-languages.com/best-uml-cheat-sheets-and-reference-guides/
First of all, you should bear in mind that UML and object-orientation - at least from point of view of software engineer - go hand in hand. You can't learn UML separate from Object oriented principles. In fact, UML is a way of representing object-oriented modeling.
Therefore, it helps a lot to learn them in parallel, since one helps to clarify the other. The book by Robert Martin, UML for Java Programers, is an excellent book that teaches both, one in light of the other.
If you are looking just for a reference book, then, Martin Fowler's "UML Distilled" is a concise and accessible reference.
Again, using UML to learn Object oriented modeling different from the case where you know OO but need a reference.
UML Distilled by Martin Fowler is the ideal book to start with, i would also recommend Object-Oriented Systems Analysis and Design by Simon Bennett. These two would provide a definitive guide. As well as this there are numerous UML cheat sheets online including
UML Quick Reference Guide
UML Reference Card
UML Cheatsheet
Related
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
I'm trying to find a good, simple introduction to domain driven design, but that is proving to be difficult.
The books I have looked at all share the same problems.
They are massive 300+ pages. I really wish this practice would change with computer books.
They shine in chapter 1, explaining the introductory and basic concepts. Then when it comes down to getting into the material they blaze through the advanced concepts with poor examples and little explanation, then jump to the next concept.
Am I asking too much when I ask is there a book for domain driven design under 300 pages that progresses at a constant pace?
I hate it when books spend so much time on the introductory concepts, yet don't bother explaining the more advanced stuff.
Update
The reason I want a sub 300 page book is because those 500+ page monsters have a lot of fluff in them and can't seem to get to the point (or skip it altogether).
Try this one - available online at InfoQ. On the plus side, it's free. On the downside, it might be too basic for you. If you want an introduction though, surely it's the basic concepts that you want to get to grips with first before delving into the advanced topics?
Domain Driven Design Quickly - 104 pages.
There's also another free download, DDD Step by Step - a really short introduction to DDD, only 34 pages.
(and the corresponding webpage Think DDD)
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
I'm going to start learning and using UML.
I need to know what considerations do you suggest for me? What is the best way to learn effectively it do you think?
Thank you
In a class named SE101- Software Engineering 1A at CPIT in New Zealand.
In my opinion, you'll find that sequence and use case diagrams will be essential for getting ideas across to non-programmers, and class diagrams (and object diagrams, to a lesser extent), for communicating ideas to other code-monkeys.
Plus, many programming books that you may read in the future, Design Patterns, for example, will use UML diagrams (class and object, mostly) to show the structure of the patterns. Knowing UML will make understanding these books a lot easier. Documentation, too, to a lesser extent.
I never did, and I never will. Modelling is not about mastering a type of discipline, good models don't need UML to be understood.
First, get a book/tutorial and try to understand the basics (definitions, models drawing, ...)
then, learn by example and practice, imagine or use a real problem and try to model it.
I started by reading an introductory book - Martin Fowler UML Distilled was quite good. Than I decided I really want to know how to use it, so I read a book about UML2 and UP (Unified Process) by Jim Arlow and Ila Neustadt. Afterward I had opportunity to take software engineering basics lecture at university which made me create simple specification with few diagrams. Afterward I took UML lecture, where I had again to create some UML diagrams. Now I am in the phase when UML is clear and I feel I need more knowledge about OO modeling, so I read a book on object oriented data modeling and object oriented programming and there are Use Cases by Alistair Cockbourne and some analytical patterns ahead for me. In between I read much of the model driven stuff and listened to SE Radio about all UML stuff - http://www.se-radio.net/tags/uml .
UML Distilled by Martin Fowler together with Applying UML And Patterns by Craig Larman, makes you understand the concept of UML and how to use it - as well the whole process with UP and so forth.
http://www.smartdraw.com/resources/tutorials/uml-diagrams/#/resources/tutorials/Getting-Started
This link was very helpful for me to learn modeling with UML.
For open source solutions check out Dia, and dia2code.
I read Martin Fowler's UML Distilled. That's all you need. It's thin, dense book that's unmatched on that topic.
I have several UML books, UML Distilled book from Addison Wesley comes to mind,
then it all gets familiar when you start reading Design Pattern books that illustrates the concepts using UML Diagrams.
I also use UML when I sketch a design.
You can only focus on 2 diagrams and start modeling almost immediately.
Usecase diagrams require reading but class diagram can be done at the same time as the code. It means that in less than 3 hours you can model.
Usecase diagram is simple and will help you to define the scope of your project.
Class diagram will define the physical architecture and can therefore be learned at the same time as codding if you use a tool having live code and model synchronization.
Don't spend time on model driven and code generation from a model because nobody really use it today !!
Inventor.
Sequence diagrams look more like business processes and usecases rather unstandardized.
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
what is a good book to learn fractal programming? I am a programmer, I am looking at a book that will be more algorithmic than mathematical (at least not in the beginning chapters). Should teach me the basics of fractals and different ways to generate them.
You might find the electric sheep project interesting.
It's an open source, distributed programming project that generates fractal animations.
Scott Drave's original paper on the electric sheep algorithm is a nice introduction to the algorithm used, and it concentrates mostly on the algorithmic aspect of creating the fractal image:
http://flam3.com/flame.pdf
When trying to learn the Mandelbrot set, I found this link useful.
http://warp.povusers.org/Mandelbrot/
For more than just Mandlebrot stuff if you can get ahold of "The Science of Fractal Images". It's an old book now (I read it when it was first published in 1988) but it's full of bits and pieces to try out.
A "golden oldie" site is Fractint: http://en.wikipedia.org/wiki/Fractint. Fractint is 20 years old and pioneered some of the ethos in collaborative computing. Some of the algorithms needed to increase precision are not trivial and this group developed integer arithmetic to support fractals.
Worth visiting to get the feel if nothing else.
But also visit http://en.wikipedia.org/wiki/Fractal-generating_software. There's a huge variety.
Note that some fractals such as the Mandelbrot set are "pixel-based" while others such as the "Snowflake curve" can use vector graphics. You'll need both approaches.
Some links
Fractal Programming
Fractal Geometry
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
What is a great way to learn good UML design? How often do you draw diagrams (other than static diagram of classes)? What is the best source for learning it?
I think Martin Fowler's "UML Distilled" is the best book for learning UML syntax. It's succinct and dense with information.
Unfortunately, knowing UML syntax well is not the same thing as knowing how to design.
Practical UML
UML Overview
I dunno, it depends on how big team is. Class/Sequence/Use cases is what mostly used for me I think. The most important thing is not overuse diagraming, couse the main goal is to help comunicate among team, help understand things same way, not just to make some useless diagrams papers and not use them.
However very complex system developed by group of teams, obviously require more diagrams I think, just to make sure everyone knows what they are doing and how things relate in system. There's quite lot good tools these days that help in modeling.
There was one project make I worked on where we used Enterprise Architect to make UML diagrams which we round-tripped (forward- and reverse-engineered) with the C# source code.
It (UML) wasn't good at defining the implementation of each method (using sequence diagrams), but it was OK defining the signatures of interfaces and of classes (i.e. the declarations, not definitions, of methods).
It was useful because you could have:
A diagram which shows how a group of classes interact (whereas with source code you see classes one at a time)
Different diagrams with different groups of classes; and sometimes the same class can appear on more than one diagram.
This was for a project where it was a requirement to create design documentation, with traceability from the use cases though design.
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
Does anyone know of a decent UML standards guide?
My company currently relies on UML 2.0 (rightly or wrongly) to do the majority (read all) of their design work. I have been asked to come up with a draft 'best practice' guide to help other developers develop better models. The main problem I face is that Im slightly biased against UML... I feel that: if a diagram takes more than 5 mins to draw then its too complicated! Im looking for advice predominantly on what sort of standards I should be looking at. Also Im looking for an external source of information that can be used to balence out my irrational loathing of UML-heavy design and act as a 'sanitizer' for my suggestions.
Most of all Im looking to write a useful document rather than one that will sit moulding away in some obscure network directory.
Any ideas?
UML Distilled by Martin Fowler
Like Paul C, I recommend UML Distilled. It is primarily about UML, but it contains a lot of insight about design in general (although it insists a bit too much on index cards IMO), it is short, pleasant to read, and to the point.
I strongly recommend against UML in a Nutshell. It is the worst O'Reilly book I have: insanely dense, hard to read and meandering. Not worth the paper it is printed on.
We are not talking about a book that says how to use UML, but rather a style or standards guide of some sort. Enter, UML profiles... This can get you both the standardization and reduced complexity you are looking for. You can limit the relationships and elements which can be used. You can also require certain things. A large company may choose to focus on the assets and data movement and limit it's standardized diagrams to this view. However, a company making real-time software for tanks might focus on action or flow.
The whole point of UML is that it is not specific and useful for every kind of situation. Martin Fowler and Elements of style books will not reduce diagramming time and increase comprehension. You need standardized profiles or patterns for than. I have seen it work, to the point that the business can read them. Many tools allow you to create a profile which eases learning curve for the designers and reduces drawing time.
MDA Distilled (OMG Press) is a good book if you want to understand the concepts, but it is not needed.
Really, UML Profiles. You don't want a standard because your company or your need is different. A standard for Web Services does not work for real-time or financial services.
Buy everyone a copy of The Elements of UML 2.0 Style. Job done.
For a quick reference on how to compose individual UML diagrams, I heartily recommend The Elements of UML Style 2.0 and I put my money where my recommendation lies by purchasing the 2nd edition to replace my 1st ed.
Apart from this recommendation, I think the most important thing in a company when introducing any style guide is to have a local feedback mechanism where people can post comments on which aspects of the style guide work for them, especially when you're using an official printed guide. A wiki or similar casual repository should suffice for this.
I also suggest highlighting diagrams which were particularly good examples (or bad ones, if the team humor could take it). Consider a framed Diagram of the Week like the Employee of the Week you see in so many stores. That gives a gentle reminder that diagram readability is taken seriously but hopefully with enough fun to get more buy-in to the concept.
I know you probably want an easy to read book for this but from what you are describing I would suggest going with the specs found on OMG itself. They are a bit much to read but would be as complete as you could hope for. They also have lonks to articles and tutorials that may be helpful.
As far as books go I have found that Using UML is quite good since it tackles the software development process as well as the UML tools and methods.