Software requirements: create system init fragment

[gregshue]

Summary of the changes:

• Fragment document created for a section "System Initialization".

StrictDoc 0.0.53 version is needed for this changeset to work.

[simhein]

Creating empty placeholder fragments isn't a good practice in my opinion. These can be easily forgotten or a duplicated set could be created

[gregshue]

Creating empty placeholder fragments isn't a good practice in my opinion. These can be easily forgotten or a duplicated set could be created

Good point. I have added FREETEXT with a TBD so that it is no longer going to be forgotten.

The point of this commit is to create the fragment file for system initialization requirements PRs to be developed against. If we delay the file creation until the first requirement draft then could end up with competing PRs creating different fragment filenames. We avoid that by defining the fragment file independent of any requirement statement. Please remember that RM and Design/Architecture are top-down activities. The decision that there will be a System Initialization section => file must happen before the contents within that file are determined.

(edited addition) BTW, my preexisting PR on System Requirements already has ~30 requirement statements for review. As soon as the fragment file is merged I will update that PR to populate this file.