As developer, I should easily link any requirement identifier (e.g security, architecture, functional id) into software source code's documentation via annotation anywhere in code #153
Labels
line:mvf
Action or item managed via the MVF production line dedicated to prototypes delivery
priority:high
High priority for treatment
Milestone
Goal & need: a link between an instruction, a method, a class or a rule implemented in a software source code should be linked to the cause that motivate is existence. For example, in a section of implemented rules of the software, a link to one or many REQ_XXXX, SEC_XXX, ARC_XXX requirements (e.g inventory of requirements manager in Notion) is mentioned in the source code via annotation like @why(requirement = { "REQ_XXX", "SEC_XXX", "ARC_XXX"}, threat = { "CVE_YYY", "CVE_ZZZ" }). The annotation should be visible in standard tool of language documentation (e.g javadoc, jsdoc).
A quality check (e.g convention, norm regarding level of documentation required) can be developed to control the level of documentation of source codes in terms of dependencies (for easy future maintenance) supporting future need of impact analysis based on requirements.
FOR HELP
Java source code:
Javascript source code:
The text was updated successfully, but these errors were encountered: