BDD is a key item for living documentation but normally BDD describes the behaviours or the system from the user perspective ie in the problem space.
Code is in the solution space, ie actual implementation to meet the needs defined int he problem space.
From a black box perpective the BDD spec typically describes what the black box should do, and the code is inside the box, and needs a white box definition. Hence it is hard to match the 2 together.
But .. that doesn't mean living documentation is a bad thing, but it isn't easy and there is no universal standard or accepted way of doing it. There are a lot of building blocks today but it requires a level of serious intervention to get them all aligned and working.
BDD is a key item for living documentation but normally BDD describes the behaviours or the system from the user perspective ie in the problem space.
Code is in the solution space, ie actual implementation to meet the needs defined int he problem space.
From a black box perpective the BDD spec typically describes what the black box should do, and the code is inside the box, and needs a white box definition. Hence it is hard to match the 2 together.
But .. that doesn't mean living documentation is a bad thing, but it isn't easy and there is no universal standard or accepted way of doing it. There are a lot of building blocks today but it requires a level of serious intervention to get them all aligned and working.
More detailed explanation of Living documentation at medium.com/geekculture/living-docu...