This may seem an odd question, but I'm interested in the views out there.

Strictly speaking, how much design work should the BA allow themself to be drawn into?
Should the BA leave system design to the the dev team and only focus on the requirement analysis and management?

And, if I, for example, design the storyboards of a user interface, am I operating outside of the scope of the definition of the BA role?

Master data management solutions have mostly evolved from the need of large organizations to better manage either their customer data or product data, both of which tend to be in a poor state in most of the companies. However master data goes beyond product and customer, including detailed information such as location, organization, financial information etc. One specific area that has emerged recently is companies specializing in dealing with supplier data in particular. Now of course many generic Master Data Management technologies are perfectly capable of handling supplier data; they may treat a supplier as a "party" and can treat it in a similar way to customer. However, there are aspects of supplier data that mean that some more specific attention is required.

Good day everybody,

As part of a thesis I am writing relating to deriving test cases from UML designs, I require assistance from the Business Analyst community in providing some feedback on the following questions:

1) Do you use any form of UML modelling during your design solution?

2) If you answered No to the above, explain why?

3) If you answered Yes to point no 1, what is the most common form of UML models used.