Development Flow#
The sections below show the lifespline/agile development flow.
Technical Requirements#
Gather information from all the behaviour and behaviour test specifications from all the problem statements and consider the technical requirements of these specifications, establishing a correspondence (TODO: automate this process).
Note
The specificity of the technical requirements is a function of the specificity of the behaviour specifications, i.e., the technical requirements are to be abstracted as much as possible from their implementation.
Example: If the behaviour specification suggests that the data layer will hold different file types, then the technical requirement should detail a technology that accommodates for different file types, otherwise it should abstain from specifying the data persistency technology.
Note
The technical requirements hierarchy establish a correspondence between the technical requirements and the behaviour. It’s important to visualize which technical requirements satisfy behaviour satisfy which problem statement, and which technical requirements satisfy which behaviours, etc., all the way down to who wrote which line of code when: 100% transparency.
System Components#
Gather information from all the technical requirements and consider the architecture components that answer all of them, establishing a correspondence (TODO: automate this process).
Note
The specificity of the technical requirements is a function of the specificity of the behaviour specifications, i.e., the technical requirements are to be abstracted as much as possible from their implementation.
Example: If the behaviour specification suggests that the data layer will hold different file types, then the technical requirement should detail a technology that accommodates for different file types, otherwise it should abstain from specifying the data persistency technology.