Topic: Documenting of correspondences of business requirements to the code
Whether for a long time wanted to ask such question, generally speaking, I do not know there is such problem in development or it is decided by me, we in firm of developers have not enough and all becomes on storage. Namely: as storage of a binding of requirements and code pieces where these requirements are implemented is organized. If for the requirement the class, apparently, it is possible to conduct a label the requirement-class answers. And if the requirement is spread on triggers and a data access layer. Most likely it is a designing error (or I am not right), but such it is theoretically possible. How process of a coordination of such binding of requirements with the code is under construction? I.e. if I changed the code I should go to correct the document. Whether There is such problem in the modern world of software development? How she dares? If not to conduct a binding in the document, it can be possible to write requirement number to comments in the code and any collector collects the referential documentation? Or when I in in comments can write the requirement identifier. Then in the future I can look at what code is responsible for the requirement under this comment?