Conclusion

The master plan is an often overlooked stage in the development of a traceability system. Yet, as we have seen here, it is a crucial link between the IT and functional characteristics of a traceability system. In professional circles, we often hear about the success or failure of this or that software solution. This reduces a company's performance to its product. What about the process? After all, we're in an informal world with real-world consequences. In view of the economic stakes and risks involved, a traceability system needs to be "bordered" as much as possible by analytical approaches to avoid any inconsistencies that could be disastrous for everyone. As the traceability sector is still in its infancy, there is no doubt that the notion of software quality will become an essential criterion in the choice of an IT partner.