What Requirements Are

CNM Cyber

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

Content

The predecessor lectio is What CNM Agile Is.

Key terms

Requirement. An expressed demand, desire, expectation, and/or wish to have or not to have a certain marketable 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.

• CNM Cyber requirements. The requirements specification for CNM Cyber.
• CNM Cloud requirements. The requirements specification for CNM Cloud.

Script

The requirements represent the visions of what needs to be developed. Creation of requirements is neither an easy nor straightforward process.

Initially, the CNM Cyber Team creates product epics. At CNM Cyber, they are the wikipages that describe the new deliverables that need to be developed. The product epics' category lists of the available epics.

These product epics are helpful to clarify the vision of new deliverables, but they are rarely clear or specific for developers to implement and not useful for the CNM Cyber Team to accept developers' work.

To make the epics usable for the product developers, these epics are chunked in user stories. Every story represents one function or feature and is written from the point of view of an end-user. To create the stories, the CNM Cyber Team uses a simple format, In order to ..., as a ..., I need to .... For instance, In order to develop user stories, as the CNM Cyber Team member, I need to know their format.

For the developers, these stories indicate what needs to be developed. More thorough requirements specifications indicate the rest what the developers need to know. Those specifications include what rules and regulations exist, how the developers shall submit their works, etc. At CNM Cyber, one specification, CNM Cyber requirements, clarifies the overall requirements for the CNM Cyber development, while another, CNM Cloud requirements, does so for the CNM Cloud one.

All of those requirements are created at CNM Wiki to be open to the general public. This policy serves two purposes.

First, the CNM Cyber Team can solicit better feedback in that way.

Second, even pre-entry-level developers can see the complete development process 24 hours a day and 7 days a week.

What CNM Page Be is the successor lectio.

Questions

Lectio quiz

The answer is recorded for the lectio completion purpose:

• Are you interested in working on requirements for CNM Cyber? --Yes/No/I'm not sure/Let me think/Let's move on

Placement entrance exam

True/False questions

• In comparison with user stories, product epics are more clear for developers work.
• To make usable for developers ,product epics are chunked in user stories.
• A user story is (not) written from the point of view of developer.
• A user story is (not) written from the point of view of end-user.
• A product epic is (not) written from the point of view of developer.
• A product epic is (not) written from the point of view of developer.
• user stories are chunked in product epics.
• Every user story (does not) represents one function or feature.
• Every product epic (does not) represents one function or feature.
• In order to ..., as a ..., I need to .... are some phrases used to write user stories at CNM Cyber.
• In order to ..., as a ..., I need to .... are some phrases used to write product epics at CNM Cyber.