Well, I normally just have a section called "Non-Functional
Requirements". Then I divide them into sections just as you have for
the features, for example PERFORMANCE and SECURITY and USABILITY and
then add requirements under there, for example
PERFORMANCE
PER-1 Must provide reasonable response time. Goal is 2 seconds or
under, but no more than 10 seconds
PER-2 Must support up to five concurrent users (which begs the question
of how you handle concurrent writes)
SECURITY
SEC-1 Administrators must be authenticated
SEC-2 Password must not be sent in clear-text over the network
etc.
It takes some thought, but this is where a lot of important constraints
on the architecture arise.
David
Sanket Sharma (JIRA) wrote:
[ http://issues.apache.org/jira/browse/DERBY-1387?page=comments#action_12416047 ]
Sanket Sharma commented on DERBY-1387:
--------------------------------------
David,
Can you please tell me more about non functional requirements? " Things like performance (response time, thorughput, number of concurrent users), security, ease of use, etc " - how exactly can I put them in a requirements doc?
Add JMX extensions to Derby
---------------------------
Key: DERBY-1387
URL: http://issues.apache.org/jira/browse/DERBY-1387
Project: Derby
Type: New Feature
Reporter: Sanket Sharma
Assignee: Sanket Sharma
Attachments: Requirements for JMX Updated.html, Requirements for JMX.html,
Requirements for JMX.zip
This is a draft requirement specification for adding monitoring and management
extensions to Apache Derby using JMX. The requirements document has been
uploaded on JIRA as well as the Derby Wiki page at
http://wiki.apache.org/db-derby/_Requirement_Specifications_for_Monitoring_%26_Management_Extensions_using_JMX
Developers and Users are requested to please look at the document (feature list
in particular) and add their own rating to features by adding a coloumn to the
table.
Comments are welcome.
