I wrote:
> > Here's a typical [use case]: Under Oregon state law, is extreme emotional
> > disturbance a defense to aggravated murder?
>
Bram wrote:
> And then see how the site performs under such research situation (ie.
> how quickly can the user find what she wants?) To me, that sounds like
> the right way to do a test.
>
> I’m also curious if you have done user tests with law students and
> researcher?
>
Hi Bram,
I totally agree with you --- this would be a great method to apply to
testing the site. I haven't done anything like that, yet. Here's the
context:
I began the site in February, and work on it in my part time. A
couple of my friends and I use it for class and other research: when
we find a bug, or a problem, I fix it. I also get feedback from a
couple of law librarians, and in response to those, I fix and/or
redesign. That's been the methodology so far. :-) Often, this would
produce random junk, but since I'm a law student as well, it's worked
out so far: I'm very focused on getting my tasks (use cases) done.
So I see it as a development by continuous prototyping.
In the long run, I'll have collaborators and more time for it.
By the way, about the legal research task: A complicating factor is
the problem domain (the law) itself: (1) Most of the time, the answer
is, "it depends", for a variety of reasons. The real answer isn't
"yes", or "no", but "how do I best argue [yes/no]?" (2) The statute
is often just a starting point for researching a problem. Case law
needs to be considered, etc. This varies depending on the area of
law.
Thanks for your interest and feedback!
Robb