I have noticed the same thing in the book. The whole thing seems unwieldy and not in an easily understandable format. Like many things in the book, it seems to be a suggestion as to good practice rather than what should be followed. For my current client, I have been recording requirements using SSM and putting the information into a spreadsheet, with the columns representing the different ways in which a requirement can be categorised, through BOSCAR, analysis 1, analysis 2 and analysis 3, PESTLE, levels of authority, influence etc. Doing it this way means I can shove in the requirements as they appear and then just quickly do a sort on the spreadsheet on a given set of columns to get the type of information I need for a specific part of the project. I don't know if my choice of elements to categorise on is standard or correct, but I would surmise so, as all of the models that are used in a business analysis project have outputs which must be taken account of. And a spreadsheet seems like a modern (as opposed to 'caveman') way of doing things.