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: [EMAIL PROTECTED] phone: 760.505.3232 fax: 949.369.0720 ________________________________ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of "Ronaldo r" <[EMAIL PROTECTED]> 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 < [EMAIL PROTECTED]> 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 [email protected] https://dev.eclipse.org/mailman/listinfo/epf-dev
_______________________________________________ epf-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/epf-dev
