{"id":37276,"date":"2016-09-08T09:52:00","date_gmt":"2016-09-08T14:52:00","guid":{"rendered":"https:\/\/kenscourses.com\/tc1019fall2016\/?guid=c6faa20b3d196b926baf8d6588c4517d"},"modified":"2016-09-08T13:15:28","modified_gmt":"2016-09-08T18:15:28","slug":"nonfunctional-is-worthy-too","status":"publish","type":"post","link":"https:\/\/kenscourses.com\/tc1019fall2016\/syndicated\/nonfunctional-is-worthy-too\/","title":{"rendered":"Nonfunctional is worthy, too."},"content":{"rendered":"
Okay, so you\u2019ve most certainly heard about requirements before. At least you\u2019ve read about it on my blog (please? ?). And probably you don\u2019t have the full mental image of actual requirements, because most requirements definitions only focus on functional requirements, actually. <\/span><\/div>
<\/b>
These so called functional requirements are based on the expected functioning of the product\/service. This is typically represented in features such as menus or buttons. Here is where you want to think about potential use scenarios. For most cases, though, if you fail to identify some nonfunctional requirements, you\u2019ll have some trouble later. Trust me.<\/span><\/div>
<\/span>A milk container has the functional requirement of being capable to contain fluid without leaking. Of course, milk containers can also be used for other things:<\/span><\/div>