Registered: Aug 2001
Location: St. Louis, MO
Re: who writes use cases?
Originally posted by SZ
Is this question clear?
7) Which of the following MUST be present to write use cases?
a) Development team
b) Object technology expert
c) Domain expert
d) Requirements decision maker
... from my experience, business analysts could scarcely be bothered with such tedious, mundane work as producing formalized use cases. They will write a word document but anything which seems like it would eventually become code is foreign to them. Thus, it is likely that writing use cases would fall to the object technology experts working together with a domain expert.
Nevertheless, the clue in this question is the word "MUST" in caps. This seems to point to c) and d).
What do you think?
IMHO, this question is vague in that these roles didn't give a definition of what their responsiblities are. Development team? Can't all others also be on the team? Or does that mean a group of programmers?
For many business information systems, you can have business analyst/domain experts, application developers, COTS component developers. But object technology expert? Do they mean someone who developed the kernal for Oracle, MFC, etc. or someone who use applies object technology to solve their problems?? What about your customer from say a high-tech industry like areospace? If your customer has a much higher knowledge level than the developers in his domain or industry, obviously either the customer or the domain expert they hire are the best qualified people to determine the business and application requirements. So the question is "who is a better contributor or source of knowledge?"
Don't let UML or job title draw the border for your knowledge. It really depends on one's training and experience. I'm well versed in both business areas (software goods manufacturing and international trade) and various design methods, both O-O and non O-O (e.g. IDEF0 and SA/SD) and I notice how much UML use case often fails to capture. I consider myself both a domain expert and a developer who can model and code. So your assumption of business analyst lacking that kind of technical savvy may be objectionable. Though I think this is a very BAD question, I too would choose c and d.
Report this post to a moderator | IP: Logged