Re: [ros-kernel] FURPS

[Jarmo M. <ja...@mu...>]

I was wondering will my message get any feedback. At least one. My
title is "ATK suunnittelija" in Finnish (in English it would mean
"Software Designer"). Nowadays I am keen to more designing than
programming. I'd like others do the programming. At least web UI
things because it's still a mess (VBScript). I hope .NET would be
more OO. I do like programming too, but designing it first a bit
better than before.

OT: I have noticed that many times people (even English speaking)
write "that" when they should write "than". I don't know the
reason. In upper paragraph I wrote "that" two times and corrected
them to "than". Why I wrote "that"???

I have an impression that many ReactOS developers don't design so
much. Have I got it wrong? Does anyone design using UML? Like
drawing class and activity diagrams for example. It would be nice
if ReactOS site would have few UML dialgrams.

Now to the answer. I meant "developer". I wrote "user" instead. I
have made this mistake before.

Usability tests come later when the program is running. Before
that you need UR (usability requirements). If they are very
defined the program could be usable. "Could be" because URs might
be not that good. Think before you do is a good advice.

I visited quickly at http://www.joelonsoftware.com/ and noticed
that they/he have/has very similar bug tracking system than we
have made. We have more fields to fill/to follow. At first it was
built with Centure/SQLWindows (still in use) and now we have a web
based version.

JMu

----- Original Message -----
From: "KJK::Hyperion" <no...@li...>
To: <rea...@li...>
Sent: Sunday, July 21, 2002 12:58 AM
Subject: Re: [ros-kernel] FURPS


> At 08.35 20/07/2002, Jarmo Muukka wrote:
> >I thought that it would be cool idea to have a web page where
users would
> >have a possibility to see and add requirements.
>
> mmmh. I'm not sure. Some good old usability tests would be
better. You can
> look at what the users expect the software to do, which is
important.
> Nobody should ever be forced to face a bug report or feature
request form
>
> >These could be possible to see/add per module. It should be
controlled
> >someway.
>
> can you say "moderation"? last time I saw WinE's list of
supported
> applications, it was a chaotic mess: automatization is cool and
stuff, but
> moderation is sometimes necessary. Better yet: find some
volunteers ("on
> your marks...") for a help desk ("RUN!!!"), that will be the
only people to
> have direct contact with the users, and shield them from the
beautiful hell
> of mailing lists, bug report forms, and all those things that
nobody in
> their right mind would like to be subject to
>
> [...]
> >I hope that you got the point. When you read this you might not
like
> >something, or think that it's too complicated, or there is
something
> >missing, or req is not needed, or it can be implemented later,
etc.
>
> I suggest you (all of you) to have a look at Joel Spolsky's
weblog:
>
> <http://www.joelonsoftware.com/>
>
> He speaks of software management mainly, but also of user
interfaces. He
> has a lot of common sense and humor. A good read. Too bad he
doesn't update
> very often
>
> >I feel that adding detailed requirements before we write a line
of code
> >will pay it back.
>
> definitely agree
>
> >By the way, the reqs are so general that there are no UI
specific things.
>
> This doesn't mean that the UI doesn't require a spec on its own,
of course
>
> >Was this interesting or not?
>
> if not else, at least someone has had the guts to bring this out
>
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> reactos-kernel mailing list
> rea...@li...
> https://lists.sourceforge.net/lists/listinfo/reactos-kernel
>