Talk:Functional requirement

message: * The page focuses on software requirements to the exclusion of other domains
* The format of the content is poor
* The content conflates functional requirements with methods
* The requirements taxonomy in general needs improvement and this page has it's part to play
* There are a few instances if circular definitions in here.  
* The definition of a Functional Requirement by contrasting it with a Non Functional requirement presents two problems; 1) The definition of an NFR here is not consistent with the NFR wikipedia page, and 2) the definition needs to be understandable in it's own right
Craigwbrown (talk) 06:35, 12 January 2012 (UTC)
replies: text: I have a few deltas
* functional requirements is requirements generally, not just software. 
* format you should try to improve whatever is bothering you about it
* requirements taxonomy is confused in literature -- many different taxonomies exist
* contrast to NFR seems appropriate in the lexicon I see it's a dichotomy of those are the two classes (the other types of requirements mentioned are just sources or subclasses of either FR or NFR)
Markbassett (talk) 21:24, 28 August 2013 (UTC)
replies: text:  p.s. It may help to look at the requirements mentioned at DO-254 or DO-178C to see it's not just software.  A functional requirement describes what a system should do, while non-functional requirements place constraints on how the system will do so. (here) Functional is just saying to describe what output must be for a given set of inputs, and sometimes that lumps in interface requirements that set the scope of the system of interacting with other systems or the operational enviroment.  Derived requirements are ones not explicitly stated iby customer but inferred by context (e.g. applicable standards, laws, policies, common practice) or by specification choice (e.g. to specify a component, from later analysis of alternatives or trade study) that the originating requirements did not identify.  There are many ways to describe the type of requirement like operational, training, safety, ergonomic, and more than one description may fit.  Markbassett (talk) 17:24, 8 February 2016 (UTC)
thread_title: A list of problems with page content

message: * (I think) The page should be structured around definition, origins, attributes and usage.
* The definition of Functional Requirement needs to be inclusive all all relevant domains, eg,
:*Definition
:Functional Requirements are Requirements a set of behaviours or activities that are required from a product to fulfil a client or customer need. In engineering the work Function has a specific meaning that implies activity of some sort. 
:Examples of functional requirements in software may include calculations, technical details, data manipulation and processing and other specific activity that define what a system is supposed to accomplish.
:Examples of functional requirements in other domains include things like the ability for a door to open without impedance from other objects, the ability for a switch to activate an electronic toy, A controller to change temperature on an air conditioner, etc.
:*Origins
::Can anyone provide an origin story for how Functional Requirements arrived?
::*Any suggestions?
:*Attributes
::What are the essential elements of a functional requirement?
::* Any suggestions
:*Usage
::Functional Requirements are often used to separate requirements into categories such as Functional (performs activities) and non functional (applies standards).
::Anything else?
I just asked these questions at my blog and when/if I get decent answers I'll return to update here. Hopefully in less than a year :) I'd be very happy if anyone else came along and made improvements in the meantime. Craigwbrown (talk) 06:35, 12 January 2012 (UTC)
replies: text: I found this article - Roman (1985) "A taxonomy of Current Issues in Requirements Engineering" Computer April 1985, IEEE http://ieeexplore.ieee.org/stamp/stamp.jsp?tp=&arnumber=1662861, and it references R. T. Yeh, "Requirements Analysis- A Management Perspective," Proc. COMPSAC '82, Nov. 1982, pp. 410-416 as an earlier citation. — Preceding unsigned comment added by Craigwbrown (talk • contribs) 05:33, 16 January 2012 (UTC)
thread_title:  Proposed improvements 

message: I'm thinking the section Origin of Term should be deleted, from not seeing an intended value and the guide of WP:DICT means we shouldn't chase the entymology without a reason.  
As an aside, the section seems also to be missing things.  From Non-functional requirement talk and prior posts here
- Basis: 'Functional requirement' stated as based on inputs, calculations, and outputs seems to be using the  mathematics concept of function later seen in IPO Model.  Math sourcing seems plausible as that concept is widely present in mathematics for centuries, and is a context that would have been fundamental and familiar to engineers.
- History mess:  The cites do convey the presence in taxonomy for at least 30+ years, but ... use of 'functional requirements' started before late 19th century as visible in google docs, and seems from context the language seems to not have changed much
* 1898 re Steam plant and viewpoints of classes of stakeholders is very much like current requirements management
* 1920s contracting for school plant of chairs is very much like current contract usages
* Similar phrase 'function required of it' in analysis of alternatives sense 
**    railway news 1873 at Dartmoor peat performs every function required of coal; 
**    Engineering news 1898 substitution of electricity in place of steam
The use in combination with "non-functional requirements" seems a less frequent and later introduction, more commonly said as 'Quality' requirement. My guess would be that grew out of 1960s 'quality' developing as a separate topic from increased frequency and importance in multiple venues like the environment (water quality) and advanced technology (NASA and nuclear power), then in the 1980s by Japan quality manufacturing and popularity of 'Total Quality Management' in U.S. starting circa 1991.   My impression is that functional/nonfunctional came into software thru structured programming and into systems engineering by way of patent and contract law... but those are my analysis, we have no contemporaneous cite providing backstory.  
So unless someone gives a reason not to, I'll likely come back and delete "Origin of the term" section as purposeless and unresolvably a mystery.  Markbassett (talk) 16:43, 28 October 2013 (UTC)
replies: text: Interesting proposal. I'm not sure how your examples make this a more encyclopedic article. Please remember that Wikipedia is not a how-to manual. Walter Görlitz (talk) 11:16, 20 August 2014 (UTC)

text: I'm sorry to be opaque. Wikipedia is an encyclopedia. Everything we do should be done to create an encyclopedia. Wikipedia is not a manual, guidebook, textbook, or scientific journal. We should not not be listing step-by-step guides on what functional requirements are in real life, we should be offering steps from need to the requirement. Walter Görlitz (talk) 13:59, 20 August 2014 (UTC)
thread_title:  Delete the Origin of Term 

message: Observations
Functional requirements are needed for many things - not just software projects.
I suggest that the "software" bias on this page is removed and replaced by a description of functional requirements that can be applied to all kinds of projects - not just software projects.
   
Whilst I agree with the assertion: 
"The crux of the requirement is the description of the required behavior" 
I find much of the rest of the text to be unclear and biased towards software development. (And it has a fog index of 17.8 which equates to "barely readable")
My proposal is to limit this page to "the functional requirements of a statement of functional requirements". 
The process of "creating functional requirements" is an example of a name for a procedure for solving the problem "We do not know how to create functional requirements".
And there is more than one way of doing this. If the process "How to develop functional requirements" is to be included on this page, then it should be in a separate section with the heading: "How to elicit and write functional requirements"   
My suggestion
Here is my suggestion for a complete restructure and rewrite of this (and related) pages:
This is generic and applies to all statements of requirements - including those for software. 
My aims are simplification and clarification.
1: Someone has some kind of need.
e.g. 
a) I want to put a man on the  Moon and return him safely to the Earth.
This is a Goal - Jules Verne wrote about this goal in 1865.
b) I want to put a man on the  Moon and return him safely to the Earth before this decade is out.
This is an Objective because it adds a due date to the Goal!
Note: An Objective is a Goal with a due date.
2: A task list for meeting the "need" can be expressed by making one or more problem statements:
'''
e.g. 
We do not know which method is best (Direct flight or Orbital rendezvous)
We do not have rocket motors with enough thrust.
We do not have trained astronauts
We do not have materials that can withstand the heat of re-entry.
We don't know enough about the Moon's gravitational anomalies. (mascons)  
     
3: Functional Requirements: (The What) Convert the problem statements into a set of statements that describe the functions that all proposed solutions must exhibit.
e.g. 
The solution must:
- use the most cost-effective method.
- have enough lift-off thrust to get to the Moon (the chosen solution had 7.5 million lbs.)
- use people who have been trained to do (insert list of abilities)
- be able to withstand 3000 degrees centigrade on re-entry.
- be able to adapt to gravitational anomalies on the Moon. (Not known about until 1966)  
 
4: Specify one or more solutions (The How)
It us usually possible to design more than one solution that meets the functional requirements.
For example: 
The requirement: "be in the office by 0800" 
Solution 1: Walk to the office.
Solution 2: Go by car.
Solution 3: Go by bicycle .
Ken Evans 10:51, 20 August 2014 (UTC)
replies: text: Interesting proposal. I'm not sure how your examples make this a more encyclopedic article. Please remember that Wikipedia is not a how-to manual. Walter Görlitz (talk) 11:16, 20 August 2014 (UTC)

text: I'm sorry to be opaque. Wikipedia is an encyclopedia. Everything we do should be done to create an encyclopedia. Wikipedia is not a manual, guidebook, textbook, or scientific journal. We should not not be listing step-by-step guides on what functional requirements are in real life, we should be offering steps from need to the requirement. Walter Görlitz (talk) 13:59, 20 August 2014 (UTC)
thread_title:  Suggestion for Clarification & Rewrite 

message: Hello fellow Wikipedians,
I have just modified one external link on Functional requirement. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:
*Added archive https://web.archive.org/web/20170131231503/http://www.dau.mil/publications/publicationsdocs/sefguide%2001-01.pdf to http://www.dau.mil/publications/publicationsDocs/SEFGuide%2001-01.pdf
When you have finished reviewing my changes, you may follow the instructions on the template below to fix any issues with the URLs.
Cheers.—InternetArchiveBot (Report bug) 22:05, 8 October 2017 (UTC)
thread_title:  External links modified