Embodiment for requirements

The great majority of the design methods seems to neglect the importance of the final stages of the design process, where first product architecture and then product details are defined. Nevertheless, almost all the design methods experts agree that details can ruin a good concept, but cannot rescue a poor concept, implicitly recognizing the advantage that will result from anticipating the main embodiment and detail design issues in the early phases of the design process. In order to solve this contradiction, authors have theoretically conceived and practically deployed the architecture of a data management system capable to store, manage and retrieve the practical solutions that are likely to be the more promising for a given specific design or re-design problem. This data management system is deeply rooted in the theories behind the systematic design methods, and, furthermore encompass the data structure defined in the systematic design approach, as well as the software tools nowadays well integrated in the design process, such as PDM and/or PLM systems.