Submitted by Nayara Passos (nayara.passos@ufpe.br) on 2015-03-12T14:07:25Z No. of bitstreams: 2 TESE Juliana de Albuquerque Gonçalves Saraiva.pdf: 2801469 bytes, checksum: 2f35aeb3fe1c0178a717be10adc01c26 (MD5) license_rdf: 1232 bytes, checksum: 66e71c371cc565284e70f40736c94386 (MD5) / Made available in DSpace on 2015-03-12T14:07:25Z (GMT). No. of bitstreams: 2 TESE Juliana de Albuquerque Gonçalves Saraiva.pdf: 2801469 bytes, checksum: 2f35aeb3fe1c0178a717be10adc01c26 (MD5) license_rdf: 1232 bytes, checksum: 66e71c371cc565284e70f40736c94386 (MD5) Previous issue date: 2014 / FACEPE, INES / Atualmente, Programao Orientada a Objetos (POO) um dos paradigmas mais utilizados. Complementarmente, a manutenibilidade de software considerada um atributo de software que desempenha um papel importante com relao ao nvel de qualidade. Neste contexto, a Manutenibilidade de Software Orientado a Objetos (MSOO) foi estudada atravs de anos e vrios pesquisadores propuseram um elevado nmero de mtricas para a medir. Como consequncia do nmero e da diversidade de mtricas existentes, alm da no padronizao nas definies e nomenclatura, a tomada de deciso sobre quais mtricas podem ser adotadas para realizar estudos em MSOO difcil. Desta forma, um mapeamento sistemtico foi realizado a fim de encontrar quais mtricas so usadas como indicadores de MSOO. Houve uma seleo inicial de 5175 estudos primrios e 138 artigos foram selecionados, resultando em 568 mtricas encontradas. Analisando as 568 mtricas, foram encontradas inconsistncias na nomenclatura destas mtricas, pois havia mtricas com nomes iguais mas significados diferentes (8 casos envolvendo 17 mtricas) e tambm mtricas com nomes diferentes e significados semelhantes (32 casos envolvendo 214 mtricas). Alm disto, uma categorizao destas mtricas foi proposta, sendo identificadas 7 categorias e 17 subcategorias. Estas categorias representam os cenrios de adoo de mtricas de MSOO. Adicionalmente, um portal web de mtricas foi desenvolvido para fornecer informaes sobre as mtricas para outros pesquisadores e tambm gerar catlogos de mtricas de acordo com o contexto da aplicao das mesmas. Este portal tambm pode ser alimentado sistematicamente por outros pesquisadores que lidam com mtricas de MSOO, fazendo com que os resultados deste trabalho possam representar os primeiros passos para padronizao e compreenso destas mtricas. Por ltimo, um quasi-experimento foi realizado para checar o grau de cobertura do catlogo proposto pela abordagem aqui apresentada quando o mesmo comparado com catlogos sugeridos por especialistas. 90% de cobertura foi obtido e este resultado foi confirmado com 99% de grau de confiana usando o Teste de Wilcoxon. De forma complementar, houve uma pesquisa de opinio para checar se os especialistas acharam catlogo gerado usando a nossa abordagem semelhante ou melhor do que o sugerido por eles. Sendo assim, os resultados da anlise da cobertura dos catlogos pode servir como indcios da utilidade da abordagem proposta para a escolha de mtricas na avaliao de MSOO. / Currently, Object-Oriented Programming (OOP) is one of the most used paradigms. Complementarily, the software maintainability is considered a software attribute that plays an important role in quality level. In this context, the Object-Oriented Software Maintainability (OOSM) has been studied through years, and many researchers have proposed a large number of metrics to measure it. As a consequence of the number and diversity of metrics, beyond the no standardization in metrics definition and naming, the decision-making process about which metrics can be adopted in experiments on OOSM, or even their using in software companies is a difficult task. Therefore, a systematic mapping study was conducted in order to find which metrics are used as indicators in OOSM assessments. There was an initial selection of 5175 primary studies and 138 were selected, resulting in 568 metrics found. Analyzing the 568 metrics, inconsistencies in metrics’ naming were found because there were metrics with the same names but different meanings (8 cases involving 17 metrics) and also, there were metrics with different names, however with similar meanings (32 cases involving 214 metrics). Moreover, a metrics’ categorization has been proposed to facilitate decision-making process about which ones have to be adopted, and 7 categories and 17 subcategories were identified. These categories represent the evaluation scenarios where OOSM metrics should be used. Additionally, a metrics’ web portal was developed to provide information about the metrics collected in this research, and to generate metrics’ catalogs according to the context of their adoption. This portal can also be systematically fed by other researchers that work with OOSM metrics, making the results of this work the first steps towards metrics’ standardization, and the improvement of the metrics’ validation. Finally, a quasi-experiment was conducted to check the coverage index of the catalogs generated using our approach over the catalogs suggested by experts. 90% of coverage was obtained and this result was confirmed with 99% of confidential level using the Wilcoxon Test. Complementarily, a survey was conducted to check the experts’ opinion about the catalog generated by the portal when they were compared by the catalogs suggested by the experts. Thus, the coverage evaluation can be the first evidences of the usefulness of the proposed approach for metrics’ choice in OOSM evaluation.

The dissertation deals with the cutting-edge subject of electronic contracts, which have the potential to automatically process and control the access rights for (electronic) goods. The dissertation shows the design and the implementation of a rights expression exchange framework. The framework enables digital rights management systems to exchange electronic contracts with each other and thus, provides DRM system compatibility. The electronic contracts, which are formulated in a standardized rights expression language, serve as exchange format between different DRM systems. The dissertation introduces a methodology for the standardized composition, exchange and processing of electronic contracts respectively rights expressions. (author´s abstract)

在80年代末期與90年代初期所討論的企業運籌管理與企業再造，都是強調在企業本身的流程管理的合理化、標準化與自動化，然而在90年代末期，由於網際網路商業應用的盛行，使得原本在90年代初期學術界所提的供應鏈管理變得更加可行。供應鏈管理重視在企業間的流程整合，使供應鏈能達到整體的流程最佳化，以提供最終使用者一個低成本、高服務品質的產品，其重點即在企業間的流程整合，運用資訊科技以達到此目的是必然的。雖然供應鏈管理被提出已有十多年之久，但是文獻中大部分僅針對管理層面上，對於系統方面卻仍然停留在企業內運籌系統，因此本研究將提出一系統架構，以達成供應鏈管理之目標。 本研究將依據關於供應鏈管理．供應鏈管理系統相關之文獻，根據文獻之結果，設計一套供應鏈管理系統架構之模型，並且使用物件導向軟體開發之技術與UML建立物件模型，最後選擇其中一功能，開發一雛形系統以驗證此架構之可行性。 本研究希望達成以下的目標：1)利用軟體系統以達成供應鏈之流程整合之目標，；2)建立一供應鏈系統架構模型，以輔助資訊廠商或企業開發供應鏈系統時之系統架構參考模型；3)與遺產系統(legacy system)結合，使用XML，與物件導向技術SOAP，提供遺產系統與供應鏈系統一個整合方案；4)降低系統使用障礙，利用WWW為人機介面，可以降低使用者使用進入障礙；5)降低系統導入成本，利用Internet的特性，企業不一定需要將系統購回，可以藉由網路，到供應鏈應用系統提供者，使用系統。 / Supply chain management (SCM) is the integration of business processes from end consumeis through original suppliers that provides product, services and infoimation. By this definition, we know that SCM is a series of management processes across firms forming a supply chain network. Cooper et al. [1] stated that those processes are customer relationship management, customer service management, demand management, order fulfillment, manufacturing flows management, procurement, product development and commercialization. In this paper, we propose an architecture and an object-oriented (00) model of SCM systems. This architecture contains three main components. The first one is "System Portal" , which is an interface between users and the system objects. The second one named "Object Repository" , which is used to store objects of the SCM system, makes the development, management and usage of these objects easier. The third one is "Database" , which is a universal database to store all data of the SCM system. Then, an 00 Model is developed based on this proposed architecture. This 00 model is graphically depicted using Unified Modeling Language (UML). We believe that the proposed architecture and 00 model in this paper can be used as a reference architecture and a reference model to help system developers to easily build their-owned SCM systems.