[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
RE: [epf-dev] supporting requirements
|
Generally it's a good idea to separate the usability requirements from
the functional requirements. Place the usability requirements in the
Supporting Requirements artifact.
By separating the requirements you can discuss, design, and agree on
usability independent of functionality. Putting them together often
confuses the issue and people talk about usability when they think they'
re talking about functionality, and vice-versa.
- Jim
____________________
Jim Ruehlin, IBM Rational
RUP Content Developer
Eclipse Process Framework (EPF) Committer www.eclipse.org/epf
email: jruehlin@xxxxxxxxxx
phone: 760.505.3232
fax: 949.369.0720
________________________________
From: epf-dev-bounces@xxxxxxxxxxx [mailto:epf-dev-bounces@xxxxxxxxxxx]
On Behalf Of "Ronaldo r" <ronaldorezende@xxxxxxxxx>
Sent: Tuesday, June 19, 2007 9:27 AM
To: Eclipse Process Framework Project Developers List
Subject: Re: [epf-dev] supporting requirements
Thank you, very much!
In the example below, the usability requirement will be separated from
the related funcional requirement. It's a good idea to put this
usability requirement in a subsection of the funcional requirement?
i.e.:
1. Functional requirements
1.1. A functional requirement
text...
1.1.1 Usability (requirement of 1.1 requirement).
The Submit button is inactive until the following information has been
entered: Name (etc).
In your idea, should I separate all usability requiments in the
usability section?
Att.
Ronaldo.
On 6/19/07, Jim Ruehlin < jruehlin@xxxxxxxxxx> wrote:
...
> Personally, I prefer refining it into a software requirement. It can
> often be the case where a business rule evolves into multiple software
> requirements. In the example above, a functional requirement has been
> identified. A usability requirement can also be defined that states
"The
> Submit button is inactive until the following information has been
> entered: Name (etc)".
>
_______________________________________________
epf-dev mailing list
epf-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/epf-dev
