Orientadores: Jose Carlos Maldonado, Mario Jino / Dissertação (mestrado) - Universidade Estadual de Campinas, Faculdade de Engenharia Eletrica e de Computação / Made available in DSpace on 2018-07-24T00:50:52Z (GMT). No. of bitstreams: 1 Ferrari_Sandra_M.pdf: 6980334 bytes, checksum: 7f6be2059ba7b933f1621b36b466e754 (MD5) Previous issue date: 1998 / Resumo: Grande número de ferramentas CASE (Computer-Aided Software Engineering) tem chegado ao mercado. Em geral, essas ferramentas são projetadas para trabalhar de forma isolada, bem como não suportam todas as fases do processo de software. Entretanto, ambientes de engenharia de software abertos oferecem facilidades para que ferramentas possam ser utilizadas de forma integrada e cooperativa. Para integrar ferramentas em um ambiente de engenharia de software aberto, é necessário analisar as dimensões principais de integração: apresentação, controle e dados, tanto do ponto de vista da ferramenta quanto da interface pública de ferramentas utilizada como base do ambiente. Este trabalho tem como objetivo a integração da ferramenta de teste POKETOOL (Potential Uses Criteria Tool for Programing Testing) em um ambiente de engenharia de software baseado em PCTE ( Portable Common Tool Environment). A integração dos dados da POKE-TOOL foi orientada pelo método proposto por Bremeau para projeto de esquemas de dados compartilháveis, baseado nos tipos e nas estruturas de gerenciamento de objetos do PCTE. Uma análise da POKE-TOOL foi realizada para explicitação de seus dados, relacionamentos e processos. Através dessa análise, foram obtidos: um diagrama genérico das atividades do processo de teste mais o diagrama entidade-relacionamento, o diagrama de fluxo de dados e o diagrama de estados da POKE-TOOL. ...Observação: O resumo, na íntegra, poderá ser visualizado no texto completo da tese digital / Abstract: A great number of CASE tools is reaching the market. These tools are usually designed to work isolatedly, in which case they do not support all the phases of the software process. Open software engineering environments provide such facilities that tools can be used in an integrated and cooperative way. In order to integrate a tool into an open software engineering environment, it is necessary to analyse the integration dimensions: presentation, control and data, both from the point of view of the tool and of the public interface used as the basis of the environment. This work aims at integrating a tool for software testing, called POKE-TOOL, into a software engineering environment based on the PCTE standard. The data integration of the POKE-TOOL followed the method proposed by Bremeau for the design of sharable data schemas based on the types and structures of the object management system of PCTE. An analysis of the POKE-TOOL was carried out to elicit its data, relationships and processes. The analysis resulted in: a generic diagram representing the activities of the testing process and the entity-relationship diagram, the data flow diagram and state diagram of the POKE-TOOL. Based on these diagrams, on the object management system of PCTE and on the need to achieve an efficient data sharing (medium granularity), the data of the POKETOOL were mapped to SDSs, which are the main structures for the integration of tools into environments based on PCTE. ...Note: The complete abstract is available with the full electronic digital thesis or dissertations / Mestrado / Engenharia de Computação / Mestre em Engenharia Elétrica

This paper describes the measurement-based software maintenance process defined and implemented at Lockheed-Martin, Moorestown, NJ. The documented process includes extensive data collection, a tightly controlled but highly accessible database, data analysis techniques supported by software tools, and process assessment and improvement activities. The methods and techniques used are presented in a 'how to' fashion so that other organizations can leverage our efforts to define and implement a measurement-based process of their own. Our approach is an evolutionary one, rather than a revolutionary organizational upheaval. We describe the benefits gained from our process, including statistically validated metric results, and the subsequent process improvements implemented. This paper describes solutions to the 'real-world' issues faced by an organization which successfully implemented a measurement-based software maintenance process.

Engineers in diverse fields are able to model their design and experiment with that design to determine how it responds to the environment and how it satisfies the requirements. Design tools for software engineering have become standardized and matured to allow for formal definition of software design. This paper tests the current state of design documentation to determine the quality of design testing available at the early stage of software design. / text

No description available.

No description available.

No description available.

No description available.

This thesis describes a framework for building a distributed concurrent system based on the active object paradigm. An active object is an agent, such as a state machine, that only executes in response to messages it receives, and can only communicate with other agents by sending messages. Steam consists of a programming model, an application programming interface and a concurrent runtime system to support the model. Steam offers an efficient implementation of active objects. The implementation also supports location transparency, dynamic re-configurability, and a form of atomicity. Steam is designed as a generic fi-amework suitable for application in a variety of domains. It can be used directly as a runtime system embedded within an application (eg. in a C program) or as a virtual machine for a concurrent programming language such as COOL.

The business drivers within managed care are mandating that physicians have point-of-care access to medical reference data, patient specific data, formularies, treatment protocols, and billing/coding information. One emerging technology that has the potential to provide this access with little economic investment is the mobile Personal Digital Assistant. The authors address a variety of wireless technologies and security concerns regarding real-time access to patient data. The family practice staff at the Naval Hospital Lemoore explored and contrasted the capabilities of commercially available PDAs, wireless interfaces, and medical software applications to ascertain their value within the Military Health System. A production-ready interface between the Composite Health Care System and the Nutrition Management Information Server demonstrates the potential for eliminating the difficulties associated with documenting patient encounters and capturing charges. Survey tools generate a requirements standard for deployment of this technology within the Military Health System on an enterprise-wide scale with a hybrid approach to packaging based on functionality. The authors recommend the Military Health System embrace this technology as a means to realize its vision of best value health services. / US Navy (USN) author

Software reuse can occur in various places during the software development cycle. Reuse of existing source code is the most commonly practiced form of software reuse. One of the key requirements for software reuse is readability, thus the interest in the use of data abstraction, inheritance, modularity, and aspects of the visible portion of module specifications. This research analyzed the contents of software reuse libraries to answer the basic question of what makes a good reusable software component. The approach taken was to measure and analyze various software metrics as mapped to design characteristics. A related research question investigated the change in the design principles over time. This was measured by comparing sets of Ada reuse libraries categorized into two time periods. It was discovered that recently developed Ada reuse components scored better on readability than earlier developed components. A benefit of this research has been the development of a set of "design for reuse" guidelines. These guidelines address coding practices as well as design principles for an Ada implementation. C++ software reuse libraries were also analyzed to determine if design principles can be applied in a language independent fashion. This research used cyclomatic complexity metrics, software science metrics, and traditional static code metrics to measure design features. This research provides at least three original contributions. First it collects empirical data about existing reuse libraries. Second, it develops a readability measure for software libraries which can aid in comparing libraries. And third, this research developed a set of coding and design guidelines for developers of reusable software. Future research can investigate how design principles for C++ change over time. Another topic for research is the investigation of systems employing reused components to determine which libraries are more successfully used than others.