| 词条 | Functional requirement |
| 释义 |
In software engineering and systems engineering, a functional requirement defines a function of a system or its component, where a function is described as a specification of behavior between outputs and inputs.[1] Functional requirements may involve calculations, technical details, data manipulation and processing, and other specific functionality that define what a system is supposed to accomplish.[2] Behavioral requirements describe all the cases where the system uses the functional requirements, these are captured in use cases. Functional requirements are supported by non-functional requirements (also known as "quality requirements"), which impose constraints on the design or implementation (such as performance requirements, security, or reliability). Generally, functional requirements are expressed in the form "system must do As defined in requirements engineering, functional requirements specify particular results of a system. This should be contrasted with non-functional requirements, which specify overall characteristics such as cost and reliability. Functional requirements drive the application architecture of a system, while non-functional requirements drive the technical architecture of a system.[4] In some cases a requirements analyst generates use cases after gathering and validating a set of functional requirements. The hierarchy of functional requirements collection and change, broadly speaking, is: user/stakeholder request → analyze → use case → incorporate. Stakeholders make a request; systems engineers attempt to discuss, observe, and understand the aspects of the requirement; use cases, entity relationship diagrams, and other models are built to validate the requirement; and, if documented and approved, the requirement is implemented/incorporated.[6] Each use case illustrates behavioral scenarios through one or more functional requirements. Often, though, an analyst will begin by eliciting a set of use cases, from which the analyst can derive the functional requirements that must be implemented to allow a user to perform each use case. ProcessA typical functional requirement will contain a unique name and number, a brief summary, and a rationale. This information is used to help the reader understand why the requirement is needed, and to track the requirement through the development of the system.[7] The crux of the requirement is the description of the required behavior, which must be clear and readable. The described behavior may come from organizational or business rules, or it may be discovered through elicitation sessions with users, stakeholders, and other experts within the organization.[7] Many requirements may be uncovered during the use case development. When this happens, the requirements analyst may create a placeholder requirement with a name and summary, and research the details later, to be filled in when they are better known. See also{{Portal|Software}}
References1. ^{{cite book |url=https://books.google.com/books?id=ZQMvDwAAQBAJ&pg=PA89 |chapter=Chapter 4: Requirements - Writing Requirements |title=Airborne Electronic Hardware Design Assurance: A Practitioner's Guide to RTCA/DO-254 |vauthors=Fulton R, Vandermolen R |publisher=CRC Press |pages=89–93 |year=2017 |isbn=9781351831420 |accessdate=15 June 2018}} 2. ^{{cite book |url=http://www.dau.mil/publications/publicationsDocs/SEFGuide%2001-01.pdf |title=Systems Engineering Fundamentals |chapter=Supplement 4-A, A Procedure for Requirements Analysis |publisher=United States Government US Army |year=2001 |ISBN=978-1484120835 |accessdate=18 March 2016 |deadurl=yes |archiveurl=https://web.archive.org/web/20170131231503/http://www.dau.mil/publications/publicationsdocs/sefguide%2001-01.pdf |archivedate=31 January 2017 |df= }} 3. ^{{cite book |chapter=Chapter 4: Requirements Engineering |title=Design Process Improvement: A Review of Current Practice |author=Loucopoulos, P. |veditors=Clarkson J, Eckert C |publisher=Springer-Verlag |pages=116–139 |year=2005 |isbn=9781846280610}} 4. ^1 {{cite book |chapter=3.2 Definitions for Functional and Non-Functional Requirements |title=Non-functional Requirements in Systems Analysis and Design |author=Adams, K.M. |publisher=Springer |pages=45–50 |year=2015 |isbn=9783319183442}} 5. ^{{cite book |chapter=Chapter 6: Impact Analysis |title=Engineering and Managing Software Requirements |vauthors=Jönsson P, Lindvall M |veditors=Aurum A, Wohlin C |publisher=Springer Science & Business Media |pages=117–42 |year=2006 |isbn=9783540282440}} 6. ^{{cite book |url=https://www.mitre.org/publications/technical-papers/the-mitre-systems-engineering-guide |chapter=Requirements Engineering: Eliciting, Collecting, and Developing Requirements |title=The MITRE Systems Engineering Guide |author=MITRE Corporate Communications and Public Affairs |publisher=MITRE Corporation |pages=304–13 |isbn=9780615974422 |accessdate=15 June 2018}} 7. ^1 {{cite book |url=https://books.google.com/books?id=IYdJocLVa8wC&pg=PA97 |chapter=Chapter 6: Software requirements|title=Applied Software Project Management |first1=Andrew |last1=Stellman |first2=Jennifer |last2=Greene |publisher=O'Reilly Media |pages=97–130 |year=2005 |isbn=9780596553821 |accessdate=15 June 2018}} 2 : Software requirements|Systems engineering |
| 随便看 |
|
开放百科全书收录14589846条英语、德语、日语等多语种百科知识，基本涵盖了大多数领域的百科知识，是一部内容自由、开放的电子版国际百科全书。