Analysis of the factors in adopting a company-wide software reuse program in [1], derived from empirical evidence of reuse practices from the survey of projects for the introduction of reuse, outlined, that despite of potential for success, around one-third of projects failed due to not introducing reuse processes or not modifying non-reuse processes, not considering human factors and lack of commitment by top management. Software processes refer to all the tasks necessary to produce and manage software, whereas reuse processes are that subset of tasks necessary for successful software reuse within a company [2]. Being process-driven means that activities are performed in accordance with well defined processes that are enforced through management policies, what is important in order to ensure efficiency, reproducibility, and predictable constraints. A key concept of systematic reuse is the domain [3]. By domain-specific specific reuse we assume, that the reusable assets, the development processes, and the supporting technology are appropriate to the application domain for which the software is being developed.