Visual Models for Software Requirements (Developer Best Practices) 1st Edition

This is the most comprehensive and understandable implementation of the complete set of BA tools I have ever seen.You can start using the framework immediately because the rules for applying the toolset to the real world environment are very organised but not over-burdened with non-value adding baggage. I have been looking for several months for best practice BA implementation references in order to remove/reduce risk to IT projects. BABoK and several other texts purchased from Amazon have been used as a basis for my research but with the discovery of this text all the information I had picked up before suddenly all came together for me. I am now drafting up a framework for what constitutes best practice in the BA environment and integrating it with how to run a project using PRINCE2. I am amazed at how little thought exists within either PMBoK or PRINCE2 about integrating the BS work into an IT project.

This is another excellent book from Microsoft Press! Software requirements remains one of the greatest challenges in software engineering. Using visual models for software requirements can help a great deal. This book goes over using visual models in detail. In particular, RML is used in this book. RML is powerful in that it takes a more holistic view in modeling software requirements (eg. it takes into account the bigger picture through categorizing requirements around objects, people, systems and data. Unlike UML, RML gives a more complete picture of what you're trying to build and who and what is impacted. Don't get me wrong though, UML is still good to use as a reasonable foundation in defining software requirements. However, if you are concerned about your business stakeholders when defining requirements you may want to give RML a try. I highly recommend this book to anyone involved in software, IT and even engineering.

I used this book as a reference for many months, picking it up when I needed it. Then I decided I would read it end to end. I chipped away at it a little bit at a time with my morning coffee, the Kindle format is great for this! I found it very informative and gave me the insights I was hoping to find. I imagine that I will breeze through it occasionally and look at my highlights/notes when a project is a bit cloudy for my stakeholder or myself.

Simply Excellent - this book is logically structured and directly implementable in meaningful ways. Our organisation used this to implement an Agile requirements elicitation, documentation and delivery methodology without much variation, and it simply worked.

I am new to creating visual modeling with regards to software requirements so I grabbed this to get me started. If you have some software engineering exposure, the concepts presented are on a basic level. The authors did not break any new ground or go into any elaborate real world scenarios. If looking for a starting point, this one is not bad. . ...

This is a great book. It gives general but also detailed insights that are very useful for modeling software requirements.

This was extremely helpful in helping identify visual models that are most beneficial in the software requirements process.

The basic themes of this are good if you take them and apply them to your situation. If you apply them all then you have a very heavy methodology which is not affordable in the current age for most companies. A better approach is to take the ones that work for you and your company and use these as the basis for a sound methodology.Also ignore the obvious plugs for MS Office as I did, this should not influence your judgement as it did not mine.