This does not mean that from the Basic Editor is recommended to refuse. The best option yalyaetsya use it to test ideas' supplies and then reprogramming the latest in Windows-program, if the ideas well implemented and the work justifies itself. Analyzing the content of specific requirements, you will notice that only some of them can be fully automatically controlled or implemented. Other requirements include provisions that prevent the possibility of their automatic controls or incarnation because of vagueness or inaccurate statements. This problem may occur also due to the fact that referred to the specific requirements of the project sites or their data are not included in the survey or provided for through changes in components of OLE.
It should be noted that the number of inaccessible, and so more immutable objects and their properties is quite large and the desire to solve completely all the tasks hardly feasible. But with the help of some neopisyvaemyh Mentor Graphics devices can still further the number of minimirovat problems that remain unsolved. Not all the specific requirements for the design of PP suggest that implementing or kotroliruyuschie their implementation tools should communicate with the documents in which these requirements are set out. Typically about half of the requirements can be implemented by specialized "autonomous" instruments associated only with the current project. In order to implement or monitor the implementation of the second half of prescriptions requires communication with the external design documents. As justification for the connection can be given at least two arguments. The first of these – the impossibility of representation of specific requirements in a logical or mathematical form for inclusion in kompyuternuyu program.
The second argument is a consequence of the first: non-translatable into the language of programming requirements should be promptly and in a convenient way to provide PP developer, who must learn them, understand them, implement or monitor compliance. Only the speed and convenience of displaying the specific design requirements hardly justifies need to develop tools, modules syazyvayuschih PADS with other programs. Significant, and perhaps decisive additional positive attribute of such tools is to give them the opportunity to select from untranslatable to the programming language requirements still translated fragments, and using it much easier for developers to implement PP does not accurately or are not specifically set out the requirements. At planning process of integration modules to PADS software environment of an enterprise should from the very beginning to take seriously the question of the organization use a lot of new tools PADS. Otherwise, the developer PP may be easier and faster (although at the expense of quality) to solve the current problem, so to speak, the old-fashioned, manually, rather than spend time searching for a new suitable tool in the form of a program or Windows-Basic Script. Practice shows that one of options for optimum organization use a lot of tools is the correct distribution of functions between the Basic Scripts and Windows-based programs. Taking into account the fast and direct access to Basic Scripts of PADS, it is expedient to use them to create a menu (that contain the word, if necessary, and a brief description of the programs), of which then cause Windows-program. References: 1.PADS Layout Help, PADS Layout 2005 SPac1. 2.Klimenko VS, Development Control and Information tool for PADS,