Systems Engineering with SysML/UML - review

A few weeks ago a colleague mentioned the SysML modelling language to me. I was interested because it claimed to extend the software focussed UML into the wider world of systems engineering. I've also found UML to be good but have struggled to describe a complete system, which is what I am normally interested in. This includes not only the deployment model but also areas such as requirements and context.

I did a little reading (good presentation here) and decided that I needed to get some detail. Looking on Amazon there are only a few books available on the subject so after "extensive" research I went for Systems Engineering with SysML/UML

The book takes us through a case study which is a good approach as it helps to develop an understanding of the subject. The danger with this approach is that the study can sound corny, and unfortunately in this case we fall into that trap. The subject is reasonable enough but the little diary entries just grated on my nerves. The other issue I find with these case studies is that, a little like most software demonstrations, they just don't ring true. I know that they are trying to demonstrate a point but anyone who has been involved in a real IT project will be all too aware of the pain and misery that many requirements management activities turn out to be. At this stage the book appears to be trying to describe a whole project approach, but doesn't quite make it.

Putting the case study to one side there is a good explanation of the basics of requirements management, although again it is not enough to be a definitive guide in its own right. The extensive use of activity models is good as I've never really got my head around these. I now understand them much better and will be looking to use them more in the future.

A small point but one that does annoy me slightly is that the grammar and spelling are not great. I fully appreciate that the authors first language is probably not English (and I certainly couldn't write a book in German)but a quick read through by an editor would have made life a bit easier for the reader.

As we get more into the flow of the SysML things improve and we are soon seeing some more meaningful examples.

Further on we find a perfectly adequate reference guide for UML; something that is not always easy to come by. The explanation of SysML is equally good and written in precise, clear language. I can see myself returning to this section again and again as I get the hang of SysML and even for the more familiar UML.

The bottom line though is will I be using SysML on future projects? At this stage I'm really not sure. I still buy into the concept but it is going to need a big slice of perseverance and practice to get the hang of it; and will this investment pay off? That is the key question and I still can't answer it.

If you have any practical experience with SysML I would be very interested to hear about it and will publish feedback on the site.

To purchase this book click on one of the links below

If you are in the UK - Systems Engineering with SysML/UML

If you are in the US - Systems Engineering with SysML/UML