Hi All,
Very often I find user interface sections in SRS/BRD templates,
I feel these sections are for user interface prototyping, but one
questions always haunt me that , just specifying the requirement
model in my SRS by Use case and activity diagrams should I go for
user interface prototyping or not? (by considering user inputs)
Kumar Rohit
Unless you are a UI expert from a previous life, I think you should steer clear of prototyping screen design. This is based primarily on my experiencxe that professional UI people can do so much better then I can, but is backed up my my observation atht there is a broad range of UI issues to consider depending on the product users and environment (eg disability access, cultural colour palettes, etc.)
If you are a UI (or UX) expert then before you start prototyping up screenshots have a discussion with the solutions team and discuss your approach so they don't start taking your sketches as hard line requirements. Imagine a website looking like an excel sheet demo!
Kumar,
It does take a certain experience level to be able to develop a really solid UI design. Ideally, you will have a UI expert, or at least a business analyst who has taken the time to objectively study and consider what "good UI design" is, design your UI interface.
With that said, in my experience, 9 times out of 10 a business analyst with only a minimal amount of UI design experience will do a better job than if you left it to a programmer. This is in no way a jab at our fellow programmers out there. It's just a matter of priorities. The business analyst has the user's best interest at heart and will work hard to acheive a solid UI design. Programmers tend to be much too busy with how to structure their code and accomplish the details of the specific coding task to really come up with a usable UI design.
There are obviously exceptions to the rule, but I suggest you spend at least a small amount of time reading up on good UI design paradigms and then give it your best effort.
I definitely agree with Craig that if you have access to an experienced UI (or UX) designer then you should have them create the prototyping and screen design of the application. However, in many organizations such a resource is not readily available so it is up to the business analyst to perform this activity. Most analysts have been around the block a few times so they have a better understanding of what a good UI should look like then the stakeholders or even the developers. Many business analysts use a prototype to elicit requirements from the stakeholders.
If you don't have experience with UI design, then try to learn as much as you can. Make sure to validate your prototypes: show them to the stakeholders and future users and, without your explanation, ask them to tell you how they would use the system. This would at least give you some feedback if your designs are intuitive to the end users.
- Adrian
I also agree with you. Here are 2 cases I have in mind:
In that way, the analyst can have the wireframes validated by the client, in order for the client to have a general idea of what the screens will look like.
Regards.
N.A.
brought to you by enabling practitioners & organizations to achieve their goals using: