[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[List Home]
|
Re: [epf-dev] supporting requirements
|
- From: "Ronaldo r" <ronaldorezende@xxxxxxxxx>
- Date: Tue, 19 Jun 2007 13:26:48 -0300
- Delivered-to: epf-dev@eclipse.org
- Dkim-signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=rutdVQfe2rlZp2wtu1a1L07xiM4/kXuilILMyVjbjGa+z9uZEW8kutJhzlloXtbwDv1BI2RpGcvSB5tvS1NkdJahNdYI7Yacsl5aApoUaj6J+ZaEapHqm98EmGx2DEPWPhAa/q3D+77arJMdJHfpfTFV2X+8LZG9ZPtQ7j3UA5s=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=nDiAF06vPDOVwbig7lhsbXQGaV5YvK+Z2KcBiN1M/cBGu2bTp6CCgMsyggUCGjbXbpi1foXkc4hfI3GAqqJNK4c8uD88FdJitN+ct+5wJjrn+nuPS9LJMZa7EsIMDwyOpnJukwElxQrLkaUZQyC0GWIXcAzWVfKXtGPx9MDnMg0=
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)".