- \n
- A system must send an email whenever a certain condition is met (e.g. an order is placed, a customer signs up, etc).<\/li>\n<\/ul>\n
A related non-functional requirement<\/strong> for the system may be:<\/p>\n
- \n
- Emails should be sent with a latency of no greater than 12 hours from such an activity.<\/li>\n<\/ul>\n
<\/p>\n
now we talk about the diferences between them:<\/p>\n
In other words, a functional requirement will describe a particular behaviour of function of the system when certain conditions are met, for example: <\/span>\u201cSend email when a new customer signs up<\/span>\u201d or \u201cOpen a new account<\/span>\u201d.<\/p>\n
A functional requirement for an everyday object like a cup would be: <\/span>\u201cability to contain tea or coffee without leaking<\/span>\u201d.<\/p>\n
Typical functional requirements include:<\/span><\/p>\n
- \n
- Business Rules<\/span><\/li>\n
- Transaction corrections, adjustments and cancellations<\/span><\/li>\n
- Administrative functions<\/span><\/li>\n
- Authentication<\/span><\/li>\n
- Authorization levels<\/span><\/li>\n
- Audit Tracking<\/li>\n
- External Interfaces<\/li>\n
- Certification Requirements<\/span><\/li>\n
- Reporting Requirements<\/span><\/li>\n
- Historical Data<\/span><\/li>\n
- Legal or Regulatory Requirements<\/span><\/li>\n<\/ul>\n
<\/p>\n
In other words, a non-functional requirement will describe how a system should behave and what limits there are on its functionality.<\/span><\/p>\n
Non-functional requirements generally specify the system<\/span>\u2019<\/span>s quality attributes or characteristics, for example: <\/span>\u201cModified data in a database should be updated for all users accessing it within 2 seconds.<\/span>\u201d<\/p>\n
A non-functional requirement for the cup mentioned previously would be: <\/span>\u201ccontain hot liquid without heating up to more than 45 <\/span>\u00b0C\u201d.<\/p>\n
Typical non-functional requirements include:<\/span><\/p>\n
- \n
- Performance <\/span>\u2013 for example: response time, throughput, utilization, static volumetric<\/span><\/li>\n
- Scalability<\/span><\/li>\n
- Capacity<\/span><\/li>\n
- Availability<\/span><\/li>\n
- Reliability<\/span><\/li>\n
- Recoverability<\/span><\/li>\n
- Maintainability<\/span><\/li>\n
- Serviceability<\/span><\/li>\n
- Security<\/span><\/li>\n
- Regulatory<\/span><\/li>\n
- Manageability<\/span><\/li>\n
- Environmental<\/span><\/li>\n
- Data Integrity<\/span><\/li>\n
- Usability<\/span><\/li>\n
- Interoperability<\/span><\/li>\n<\/ul>
<\/a>
![\"\"](\"https:\/\/pixel.wp.com\/b.gif?host=diegograciasite.wordpress.com&blog=115273869&%23038;post=258&%23038;subd=diegograciasite&%23038;ref=&%23038;feed=1\")
","protected":false},"excerpt":{"rendered":"First we need to define each one: An example of a functional requirement would be: A system must send an email whenever a certain condition is met (e.g. an order is placed, a customer signs up, etc). A related non-functional requirement for the system may be: Emails should be sent with a latency of no … Continue reading Functional and non functional requirements<\/span><\/a><\/p>\n","protected":false},"author":16,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[5,4],"tags":[44],"class_list":["post-38229","post","type-post","status-publish","format-standard","hentry","category-blogs","category-syndicated","tag-sin-categoria"],"_links":{"self":[{"href":"https:\/\/kenscourses.com\/tc1019fall2016\/wp-json\/wp\/v2\/posts\/38229","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/kenscourses.com\/tc1019fall2016\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/kenscourses.com\/tc1019fall2016\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/kenscourses.com\/tc1019fall2016\/wp-json\/wp\/v2\/users\/16"}],"replies":[{"embeddable":true,"href":"https:\/\/kenscourses.com\/tc1019fall2016\/wp-json\/wp\/v2\/comments?post=38229"}],"version-history":[{"count":1,"href":"https:\/\/kenscourses.com\/tc1019fall2016\/wp-json\/wp\/v2\/posts\/38229\/revisions"}],"predecessor-version":[{"id":38230,"href":"https:\/\/kenscourses.com\/tc1019fall2016\/wp-json\/wp\/v2\/posts\/38229\/revisions\/38230"}],"wp:attachment":[{"href":"https:\/\/kenscourses.com\/tc1019fall2016\/wp-json\/wp\/v2\/media?parent=38229"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/kenscourses.com\/tc1019fall2016\/wp-json\/wp\/v2\/categories?post=38229"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/kenscourses.com\/tc1019fall2016\/wp-json\/wp\/v2\/tags?post=38229"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
- Scalability<\/span><\/li>\n
- Transaction corrections, adjustments and cancellations<\/span><\/li>\n
- Business Rules<\/span><\/li>\n
- Emails should be sent with a latency of no greater than 12 hours from such an activity.<\/li>\n<\/ul>\n