Abstract At present, diagnostic reagent is the most fruitful and important realm in internal biotech product commercialization. Compared to other biotech medicine with the industrial characteristics of complications such as: high investment, high risk, and long-term research and development; diagnostic reagent, relatively, acquires a lower threshold for technique, a short-term research and development, less investment and a short time for feedback. In addition, people gradually acquire the notions of prophylaxis and health care, as a result, the potentiality of diagnostic reagent comes to the market¡¦s notice. The process of diagnostic reagent development can be divided by the mainstream techniques into four phases including: the technology of chemical test, the technology of enzyme test, the technology of immunoassay test, the technology of nuclease molecule test and biochip. From this, we know that the technology of immunity test is still the mainstream in the market, but there is a trend toward the development of the technology of nuclease molecule immunoassay. General Biologicals Corp. is the first built diagnostic reagent manufacture in our country, and, so far, it is the only diagnostic reagent manufacture that meets with the Department of Health¡¦s CGMP standard. The General Biologicals Corp. is the only internal manufacture that produces ELISA and EIA microplate. However, the General Biologicals Corps has less than 1% of six hundred million, and foreign manufactures have it all. The General Biologicals Corps went public in recent years, and the company has a microplate immunoassay diagnostic reagent factory for over twenty years. Those doctors, examiners and sales clerks who used the immunoassay reagent produced by the General Biologicals Corps are all in high positions in this industry. They know this company and also their reagent kits which have a low sensitivity. More important is that the reagent kits are not improved for all these years. The bad impression of the company makes the customers and collaborators have doubts about the quality, the attitude of the personnel and the sincerity of the company. It results in a trust crisis. In light of the five competitiveness analyses in the executive strategies: dynamic competition of the company in enterprise; S.W.O.T competitiveness analysis; smiling curve and bitter smiling curve; red ocean and blue ocean strategy and, finally, the administration of registering examined medical instrument, to see the integral competitiveness of the company in the industrial competitive environment. Can the General Biologicals Corp. seek league and collaboration in the competitors to seize the internal market, and then the overseas market. By these analyses and advises, to reengeneering the General Biologicals Corp. has a new management on the visible foundation. Key Word¡GImmunity Test, Nuclear Molecular Immuno assay. Five Force, Reengeneering

Um método composto de quatro passos para conduzir engenharia reversa orientada a objetos de sistemas desenvolvidos sem usar a tecnologia de orientação a objetos e apresentado. Este método abrangente e detalhado mostrando como fazer engenharia reversa constitui um avanço para o estado da arte, pois não há métodos publicados nesse nível de detalhe ate o momento. A documentação produzida pela engenharia reversa baseada no Método Fusion para desenvolvimento de sistemas orientados a objetos e composta de um Modelo de Objetos, um Modelo de Operação e um Modelo de Ciclo de Vida. Um conjunto de modelos intermediário extraído diretamente do código e dos documentos de interação processo/dados e também incluído com o nome de Modelo de Análise do Sistema Atual. A engenharia reversa de um ambiente de software para projetar sistemas reativos e mostrada em detalhes. Esse software tem 30.000 linhas de código C, divididas em 495 procedimentos agrupados em 36 módulos. Um documento semelhante a um dicionário de dados foi preparado com base na documentação contida em diversas dissertações, artigos e principalmente em seu código fonte. O ambiente de desenvolvimento de sistemas reativos e descrito, bem como sua evolução através de diversas versões e sua aplicação e ilustrada pelo projeto do statechart correspondente a um relógio despertador. Facilidades para especificar atividades associadas aos statecharts foram incorporadas ao ambiente StatSim como parte dos trabalhos desenvolvidos nesta tese e são também discutidas e aplicadas a um exemplo. A simulação de statecharts de controle sujeitos a diferentes eventos possíveis e incluída através de diagramas e \"logs\". Esse exemplo é também usado para ilustrar um procedimento relacionado ao acoplamento de statercharts e diagramas de atividades na especificação de sistemas reativos e para mostrar o uso do ambiente de software para verificar essa especificação. O Método Fusion e comparado a outros métodos de desenvolvimento de sistemas orientados a objetos. O ambiente de desenvolvimento de sistemas reativos baseado em statecharts e posicionado entre outras ferramentas para o desenvolvimento de tais sistemas. / A method composed of four steps to conduct object oriented reverse engineering in systems developed using non object oriented technology is presented. This comprehensive, detailed method showing how to do reverse engineering is an advance to the state of the art as there are no published methods hitherto at this level of detail. The documentation produced by the reverse engineering based on the Fusion Method for object oriented systems development is composed by an Object Model, an Operation Model and a Life Cycle Model. An intermediary set of models directly extracted from the code and from a process/data interaction document is also included with the name of Current Systems Analysis Model. The reverse engineering of a software environment for designing reactive systems is shown in detail. This software comprises 30.000 lines of code in C, spread for 495 procedures grouped in 36 modules. This data dictionary-like document was prepared based on documentation contained in several dissertations and papers and mainly on the code itself. The reactive systems software development environment is described as well as its evolution through several versions, and its application is illustrated by designing the statecharts corresponding to an alarm clock. Facilities to specify activities triggered by the statecharts incorporated to the StatSim environment as part of this thesis\' are also discussed and applied to the example. The simulation of the controlling statecharts subjected to different possible events is included through diagrams and logs. This example is also used to illustrate a procedure devised for coupling statecharts and activity diagrams in the specification of reactive systems and for using the software environment to verify this specification. The Fusion Method is compared to other methods for object oriented systems development. The reactive systems development environment based on statecharts is situated among other tools for the development of such systems.

Um método composto de quatro passos para conduzir engenharia reversa orientada a objetos de sistemas desenvolvidos sem usar a tecnologia de orientação a objetos e apresentado. Este método abrangente e detalhado mostrando como fazer engenharia reversa constitui um avanço para o estado da arte, pois não há métodos publicados nesse nível de detalhe ate o momento. A documentação produzida pela engenharia reversa baseada no Método Fusion para desenvolvimento de sistemas orientados a objetos e composta de um Modelo de Objetos, um Modelo de Operação e um Modelo de Ciclo de Vida. Um conjunto de modelos intermediário extraído diretamente do código e dos documentos de interação processo/dados e também incluído com o nome de Modelo de Análise do Sistema Atual. A engenharia reversa de um ambiente de software para projetar sistemas reativos e mostrada em detalhes. Esse software tem 30.000 linhas de código C, divididas em 495 procedimentos agrupados em 36 módulos. Um documento semelhante a um dicionário de dados foi preparado com base na documentação contida em diversas dissertações, artigos e principalmente em seu código fonte. O ambiente de desenvolvimento de sistemas reativos e descrito, bem como sua evolução através de diversas versões e sua aplicação e ilustrada pelo projeto do statechart correspondente a um relógio despertador. Facilidades para especificar atividades associadas aos statecharts foram incorporadas ao ambiente StatSim como parte dos trabalhos desenvolvidos nesta tese e são também discutidas e aplicadas a um exemplo. A simulação de statecharts de controle sujeitos a diferentes eventos possíveis e incluída através de diagramas e \"logs\". Esse exemplo é também usado para ilustrar um procedimento relacionado ao acoplamento de statercharts e diagramas de atividades na especificação de sistemas reativos e para mostrar o uso do ambiente de software para verificar essa especificação. O Método Fusion e comparado a outros métodos de desenvolvimento de sistemas orientados a objetos. O ambiente de desenvolvimento de sistemas reativos baseado em statecharts e posicionado entre outras ferramentas para o desenvolvimento de tais sistemas. / A method composed of four steps to conduct object oriented reverse engineering in systems developed using non object oriented technology is presented. This comprehensive, detailed method showing how to do reverse engineering is an advance to the state of the art as there are no published methods hitherto at this level of detail. The documentation produced by the reverse engineering based on the Fusion Method for object oriented systems development is composed by an Object Model, an Operation Model and a Life Cycle Model. An intermediary set of models directly extracted from the code and from a process/data interaction document is also included with the name of Current Systems Analysis Model. The reverse engineering of a software environment for designing reactive systems is shown in detail. This software comprises 30.000 lines of code in C, spread for 495 procedures grouped in 36 modules. This data dictionary-like document was prepared based on documentation contained in several dissertations and papers and mainly on the code itself. The reactive systems software development environment is described as well as its evolution through several versions, and its application is illustrated by designing the statecharts corresponding to an alarm clock. Facilities to specify activities triggered by the statecharts incorporated to the StatSim environment as part of this thesis\' are also discussed and applied to the example. The simulation of the controlling statecharts subjected to different possible events is included through diagrams and logs. This example is also used to illustrate a procedure devised for coupling statecharts and activity diagrams in the specification of reactive systems and for using the software environment to verify this specification. The Fusion Method is compared to other methods for object oriented systems development. The reactive systems development environment based on statecharts is situated among other tools for the development of such systems.