Business Analyst - Use Case Problem

GeekInterview.com > Interview Questions > Management > Business Analyst

Go To First | Previous Question | Next Question

Business Analyst | Question 72 of 130

Use Case Problem

If a stakeholder does not want to read your entire use case, what could you do convey the message across?

Total Answers and Comments: 4

Last Update: April 27, 2008 Asked by: agharana

Sponsored Links

Best Rated Answer

—

Submitted by: triptigupta

BA should always have supplementary artifacts such as - flowcharts, wireframes of the screens and so on which explains the entire use case.
So even if the stakeholder does not want to read the entire use case, just by having a glimpse of the poictures provided they should understand what is the use case about.
Rightly said ' A picture speaks a thosand words'

Above answer was rated as good by the following members:
gaganrana

March 10, 2008 19:20:57

zamnet

Member Since: March 2008 Contribution: 2

RE: Use Case Problem

Use UML designing program or SSADM for the convenience of the stakeholder

Is this answer useful? Yes | No

0 1

Overall Rating: -1

March 25, 2008 21:56:33

ciskowitz

Member Since: December 2007 Contribution: 2

RE: Use Case Problem

I would walk him though the use case in person. The client must be made to read the documentation at some point or else he's going to be sorry when he sees the first version and it doesn't work the way he expects. This is a client-management issue and one that you need to learn about early in your career.

I always schedule an in-person meeting to walk-through whatever document I have I just delivered to the client. This goes for both internal and external clients. They almost never read the documents on their own. This is coming from my 20+ years of experience. You need to hold them by the hand walk them through each step and make sure they understand what is written and how the system will function for all alternative cases. Otherwise you're just setting yourself up for failure down the road.

Is this answer useful? Yes | No

April 10, 2008 03:59:28

triptigupta

Member Since: April 2008 Contribution: 1

RE: Use Case Problem

BA should always have supplementary artifacts such as - flowcharts wireframes of the screens and so on which explains the entire use case.
So even if the stakeholder does not want to read the entire use case just by having a glimpse of the poictures provided they should understand what is the use case about.
Rightly said ' A picture speaks a thosand words'

Is this answer useful? Yes | No

1 0

Overall Rating: +1

April 27, 2008 09:27:34

priyankam9

Member Since: April 2008 Contribution: 8

RE: Use Case Problem

Simple thing is to have a Use Case Daigram adjacent to the Use Case the daigram should tell the user what the use case will do so that by looking into that satkeholder will get to knoe the functionality of the usecase instead of going through the whole shit.

Is this answer useful? Yes | No

Go To Top

User Name		Remember Me?
Password

Question Bank