[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
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)".
