Forums for the Business Analyst

 
  Modern Analyst Forums  Business and Sy...  Requirements  Why is this requirement confusing?
Previous Previous
 
Next Next
New Post 3/28/2019 7:28 AM
Unresolved
User is offline MadiMo
10 posts
10th Level Poster


Why is this requirement confusing? 

When looking at a requirement for a system behaviour that includes system performance, my understanding is that it is non-functional requirement, however, in some ways it is also considered functional requirement. I will share an example below

 

"The system must send an confirmation email after 5 seconds from the User Registration" This is a Non-Functional Requirement, because it involves performance that is measured by time

 

"The password expires after 60 days of inactivity" How come this is a functional requirement when it relates to the System Performance? If it deemed a business rule then the previous example is also a business rule, or am I missing something?

Many thanks for the advice

 
New Post 3/28/2019 4:52 PM
User is offline Kris 03
9 posts
10th Level Poster


Re: Why is this requirement confusing? 

My logic - If any task can be done better, it becomes non functional.

A confirmation email to be sent - Functional requirement

Confirmation email to be sent in 5 seconds - Non functional requirement

Password to be expired - Functional requirement. 

Password expired after 60 days of inactivity is policy (or business rule).

https://www.modernanalyst.com/Community/CommunityBlog/tabid/182/ID/3823/When-is-Security-not-a-Non-Functional-Requirement.aspx

 
New Post 4/15/2019 9:39 AM
User is offline Gildas
2 posts
No Ranking


Re: Why is this requirement confusing? 

Hello. According to me:

1-Business rules are a kind of requirement. From them, we can derive system (product) requirements.

“Password expires after 60 days of inactivity” is a business rule. A derived system requirement could be: “the system shall reset the user’s password after 60 days of inactivity”.

2-Complete (functional) system requirements should be stated as follow:

[If Trigger-Event(s) occur [during Precondition(s),]] the system shall [not] perform Response-Action(s) [resulting in Postcondition(s) [within Quality-Threshold(s)]] (see D. Firesmith).

3-The distinction functional requirement vs non-functional requirement doesn’t really matter when elaborating the requirements. She makes sense later when designing and testing the system.

Hope having helped you,

Gildas

 
Previous Previous
 
Next Next
  Modern Analyst Forums  Business and Sy...  Requirements  Why is this requirement confusing?




Latest Articles

Domain Expertise and the Business Analyst: How Vital Is It?
Sep 15, 2019
0 Comments
The question of how essential domain expertise is to a business analyst is a recurring debate in the BA community. One school of thought maintains tha...
Copyright 2006-2019 by Modern Analyst Media LLC