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
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).

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,


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

Community Blog - Latest Posts

Dan Tasker
Dan Tasker
  In Part 1 of this series it was stated that the overall objective of these articles is to improve the quality of requirements produced by business analysts. Following the adage that “Context is Everything” it established that a number of different contexts...
7 Responses
Alice Bolingeryn
Alice Bolingeryn
Clearly, the most important step in getting a job is being selected for an interview, and a key part in that process is having a resume that stands out from others.   For many people, creating a good enough resume is an obstacle in achieving this, and so one way to address this problem may be to get a professional to create one for you. J...
0 Responses
It may sound routine, but the importance of operational decisions cannot be underestimated. After all, not a day goes by without even the smallest business making dozens, if not hundreds of operational decisions that may affect the bottom line. Elevate these to large scale companies and we are talking thousands, if not millions of actions that impa...
0 Responses

Upcoming Live Webinars

Latest Articles

Top 10 Most Common Reasons People Fail the CBAP Exam
Jul 14, 2019
Many professionals approach us after being unsuccessful in CBAP so we thought of doing some analysis to come up with the most common reasons of failur...
Copyright 2006-2019 by Modern Analyst Media LLC