![]() ![]() Do you understand the type of every element? (i.e.Again, here are some things to think about: Let's move on to look at the elements in more detail. I'd recommend adding a diagram key/legend for UML and ArchiMate diagrams too, since not everybody will know these visual languages. And while that's not necessarily a bad thing, a diagram key/legend would help readers to understand the notation being used. Well, this looks like an ad hoc collection of "boxes and lines" rather than being UML or ArchiMate. My assumption is that the large box labelled "Risk System" is the scope of the diagram, but a better title would clarify this.Īnd regarding notation. I'd estimate that upwards of 90% of the initial diagrams I see created during my workshops don't have a title! In this case, the diagram does have a title of "Context", but it's not explicit about what it's showing the context of, and what the diagram scope is. ![]() Do you understand what the diagram scope is?.Do you understand what the diagram type is?.Here are a few initial things to think about: Let's start by looking at the diagram as a whole. It's high-level, clean, concise, colourful, and you might even be able to work out what's being described here. On the face of it, this diagram doesn't look too bad. Let's start with a fairly typical example of a whiteboard diagram from one of my workshops. Some diagrams are better than others, but I've noticed that many people struggle to critique a diagram because they're not really sure what to look for. I see hundreds of software architecture diagrams every year, predominantly through my software architecture workshops. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |