Difference between revisions of "What Requirements Are"

From CNM Wiki
Jump to: navigation, search
 
Line 1: Line 1:
[[What Requirements Are]]
+
[[File:Cnm-digital.png|400px|thumb|right|[[CNM Cyber]]]][[What Requirements Are]] (hereinafter, the ''Lectio'') is the [[lectio|lesson part]] of the '''[[Digital Transformations]]''' [[lesson]] that introduces its participants to the development of [[CNM Cyber]]. This ''lesson'' belongs to the [[Introduction to CNM Cyber]] session of the [[CNM Cyber Welcome Course]].
  
[[Digital Transformations]]
+
 
 +
==Key terms' outline==
  
 
|3||'''[[CNM Agile]]''', [[project management]], [[Agile methodology]]; '''[[development hub]]''', [[document]], [[computer file]], [[software]]; '''[[requirement]]''', [[product epic]], [[user story]]; '''[[requirements specification]]''', [[CNM Cyber requirements]], [[CNM Cloud requirements]]
 
|3||'''[[CNM Agile]]''', [[project management]], [[Agile methodology]]; '''[[development hub]]''', [[document]], [[computer file]], [[software]]; '''[[requirement]]''', [[product epic]], [[user story]]; '''[[requirements specification]]''', [[CNM Cyber requirements]], [[CNM Cloud requirements]]

Revision as of 23:59, 20 April 2020

What Requirements Are (hereinafter, the Lectio) is the lesson part of the Digital Transformations lesson that introduces its participants to the development of CNM Cyber. This lesson belongs to the Introduction to CNM Cyber session of the CNM Cyber Welcome Course.


Key terms' outline

|3||CNM Agile, project management, Agile methodology; development hub, document, computer file, software; requirement, product epic, user story; requirements specification, CNM Cyber requirements, CNM Cloud requirements

Requirement. An expressed demand, desire, expectation, and/or wish to have or not to have a certain product and/or a certain capability, condition, feature, and/or property. The plural term, requirements, may refer to the aggregate of various requirements that the product owner or another authority for the requested product and/or its development process has approved, verified, and/or validated.
  • Product epic. A detailed description of a proposed product that is designed to make its potential consumer understand what this product shall do. At CNM Cyber, the Epic is any wikipage that describes a desired product.
  • User story. A brief description of a solution requirement to a desired system that is written from the point of view of a customer or end-user of this system. In other words, the story is a high-level, informal, brief, non-technical description of a solution capability that provides value to its stakeholder. The story is typically one or two sentences long and provides the minimum information necessary to allow a developer to estimate the work required to implement it. In order to ..., as a ..., I need to ... or, using another format, In order to [achieve some goal], as a [type of user], I need to [perform some task or execute some function] is a generic example of the story.
Requirements specification. A requirement in a form of technical description of a proposed system.