Cloud Computing is the next step in the evolution of the Internet. It provides seemingly unlimited computation and storage resources by abstracting the networking, hardware, and software components underneath. However, individual cloud service providers do not have unlimited resources to offer. Some of the tasks demand computational resources that these individual cloud service providers can not fulfill themselves. In such cases, it would be optimal for these providers to borrow resources from each other. The process where different cloud service providers pool their resources is called Cloud Federation. There are many aspects to Cloud Federation such as access control and interoperability. Access control ensures that only the permitted users can access these federated resources. Interoperability enables the end-user to have a seamless experience when accessing resources on federated clouds. In this thesis, we detail our project named GENI-SAVI Federation, in which we federated the GENI and SAVI cloud systems. We focus on the access control portion of the project while also discussing the interoperability aspect of it. / Graduate / 0984 / panjwani.riz@gmail.com

Thesis (MEng)--Stellenbosch University, 2014. / ENGLISH ABSTRACT: The main on-board computer in a satellite is responsible for ensuring the correct operation of the entire system. It performs this task using flight software. In order to reduce future development costs, it is desirable to develop generic software that can be re-used on subsequent missions. This thesis details the design and implementation of a generic flight software application for CubeSats. A generic, modular framework is used in order to increase the re-usability of the flight software architecture. In order to simplify the management of the various on-board processes, the software is built upon the FreeRTOS real-time operating system. The Consultative Committee for Space Data Systems’ telemetry and telecommand packet definitions are used to interface with ground stations. In addition, a number of services defined in the European Cooperation for Space Standardisation’s Packet Utilisation Standard are used to perform the functions required from the flight software. The final application contains all the command and data handling functionality required in a standard CubeSat mission. Mechanisms for the collection, storage and transmission of housekeeping data are included as well as the implementation of basic fault tolerance techniques. Through testing it is shown that the FreeRTOS scheduler can be used to ensure the software meets hard-real time requirements. / AFRIKAANSE OPSOMMING: Die hoof aanboordrekenaar in ’n satelliet verseker die korrekte werking van die hele stelsel. Die rekenaar voer hierdie taak uit deur van vlugsagteware gebruik te maak. Om toekomstige ontwikkelingskostes te verminder, is dit noodsaaklik om generiese sagteware te ontwikkel wat hergebruik kan word op daaropvolgende missies. Hierdie tesis handel oor die besonderhede van die ontwerp en implementering van generiese vlugsagteware vir ’n CubeSat. ’n Generiese, modulêre raamwerk word gebruik om die hergebruik van die sagteware te verbeter. Ten einde die beheer van die verskillende aanboordprosesse te vereenvoudig, word die sagteware gebou op die FreeRTOS reëletyd bedryfstelsel. Die telemetrie- en telebevelpakket definisies van die “Consultative Committee for Space Data Systems” word gebruik om met grondstasies te kommunikeer. Daarby is ’n aantal dienste omskryf in die “Packet Utilisation Standard” van die “European Cooperation for Space Standardisation” gebruik om die vereiste funksies van die vlugsagteware uit te voer. Die finale sagteware bevat al die bevel en data-hantering funksies soos wat vereis word van ’n standaard CubeSat missie. Meganismes vir die versameling, bewaring en oordrag van huishoudelike data is ingesluit sowel as die implementering van basiese fouttolerante tegnieke. Toetse het gewys dat die FreeRTOS skeduleerder gebruik kan word om te verseker dat die sagteware aan harde reëletyd vereistes voldoen.

This thesis describes the primary goal of the HelenOS microkernel multiserver operating system. The primary goal of the HelenOS project is to create a comprehensive research and development platform in the domain of general-purpose operating systems that would support state-of-the-art approaches and methods (such as verification of correctness) while at the same time focusing on practical relevance. The text of the thesis describes what specific means in terms of design (based on software components), implementation, development process and verification are used to achieve the primary goal. The thesis also evaluates the current state of HelenOS. Powered by TCPDF (www.tcpdf.org)

Gérer l'évolution des logiciels est une tâche complexe mais nécessaire. Tout au long de son cycle de vie, un logiciel doit subir des changements, pour corriger des erreurs, améliorer ses performances et sa qualité, étendre ses fonctionnalités ou s’adapter à son environnement. A défaut d’évoluer, un logiciel se dégrade, devient obsolète ou inadapté et est remplacé. Cependant, sans évaluation de leurs impacts et contrôle de leur réalisation, les changements peuvent être sources d’incohérences et de dysfonctionnements, donc générateurs de dégradations du logiciel. Cette thèse propose une approche améliorant la gestion de l'évolution des logiciels dans les processus de développement orientés composants. Adoptant une démarche d’ingénierie dirigée par les modèles (IDM), cette approche s’appuie sur Dedal, un langage de description d’architecture (ADL) séparant explicitement trois niveaux d’abstraction dans la définition des architectures logicielles. Ces trois niveaux (spécification, configuration et assemblage) correspondent aux trois étapes principales du développement d’une architecture (conception, implémentation, déploiement) et gardent la trace des décisions architecturales prises au fil du développement. Ces informations sont un support efficace à la gestion de l’évolution : elles permettent de déterminer le niveau d’un changement, d’analyser son impact et de planifier sa réalisation afin d’éviter la survenue d’incohérences dans la définition de l’architecture (érosion, dérive, etc.). Une gestion rigoureuse de l’évolution nécessite la formalisation, d’une part, des relations intra-niveau liant les composants au sein des modèles correspondant aux différents niveaux de définition d’une architecture et, d’autre part, des relations inter-niveaux liant les modèles décrivant une même architecture aux différents niveaux d’abstraction. Ces relations permettent la définition des propriétés de consistance et de cohérence servant à vérifier la correction d’une architecture. Le processus d’évolution est ainsi décomposé en trois phases : initier le changement de la définition de l’architecture à un niveau d’abstraction donné ; vérifier et rétablir la consistance de cette définition en induisant des changements complémentaires ; vérifier et rétablir la cohérence globale de la définition de l’architecture en propageant éventuellement les changements aux autres niveaux d’abstraction.Ces relations et propriétés sont décrites en B, un langage de modélisation formel basé sur la théorie des ensembles et la logique du premier ordre. Elles s’appliquent à des architectures définies avec un adl formel écrit en B dont le méta-modèle, aligné avec celui de Dedal, permet d’outiller la transformation de modèles entre les deux langages. Cette intégration permet de proposer un environnement de développement conjuguant les avantages des approches IDM et formelle : la conception d’architectures avec l’outillage de Dedal (modeleur graphique); la vérification des architectures et la gestion de l’évolution avec l’outillage de B (animateur, model-checker, solver). Nous proposons en particulier d’utiliser un solver B pour calculer automatiquement des plans d’évolution conformes à notre proposition et avons ainsi défini l’ensemble des règles d’évolution décrivant les opérations de modification applicables à la définition d’une architecture. Le solver recherche alors automatiquement une séquence de modifications permettant la réalisation d’un changement cible tout en préservant les propriétés de consistance et de cohérence de l’architecture. Nous avons validé la faisabilité de cette gestion de l’évolution par une implémentation mêlant optimisation et génie logiciel (search-based software engineering), intégrant notre propre solver pourvu d’heuristiques spécifiques qui améliorent significativement les temps de calcul, pour expérimenter trois scénarios d’évolution permettant de tester la réalisation d’un changement à chacun des trois niveaux d’abstraction. / Managing software evolution is a complex task. Indeed, throughout their whole lifecycle, software systems are subject to changes to extend their functionalities, correct bugs, improve performance and quality, or adapt to their environment. If not evolved, software systems degrade, become obsolete or inadequate and are replaced. While unavoidable, software changes may engender several inconsistencies and system dysfunction if not analyzed and handled carefully hence leading to software degradation and phase-out.This thesis proposes an approach to improve the evolution management activity in component-based software development processes. The solution adopts a Model-Driven Engineering (MDE) approach. It is based on Dedal, an Architecture Description Language (ADL) that explicitly separates software architecture descriptions into three abstraction levels: specification, configuration and assembly. These abstraction levels respectively correspond to the three major steps of component-based development (design, implementation and deployment) and trace architectural decisions all along development. Dedal hence efficiently supports evolution management: It enables to determine the level of change, analyze its impact and plan its execution in order to prevent architecture inconsistencies (erosion, drift, etc.). Rigorous evolution management requires the formalization, on the one hand, of intra-level relations linking components within models corresponding to different architecture abstraction levels and on the other hand, of the formalization of inter-level relations linking models describing the same architecture at different abstraction levels. These relations enable the definition of the consistency and coherence properties that prove necessary for architecture correctness analysis. The evolution process therefore consists of three steps: First, change is initiated on an architecture description at a given abstraction level; then, the consistency of the impacted description is checked out and restored by triggering additional changes; finally, the global coherence of the architecture definitions is verified and restored by propagating changes to other abstraction levels.Relations and properties are expressed in B, a set-theoretic and first-order logic language. They are applied on B formal ADL, the meta-model of which is mapped to Dedal's and helps automatic model transformations. This integration enables to implement a development environment that combines the benefits of both MDE and formal approaches: Software architecture design using Dedal tools (graphical modeler) and architecture analysis and evolution management using B tools (animator, model-checker, solver).In particular, we propose to use a B solver to automatically calculate evolution plans according to our approach. The solver explores a set of defined evolution rules that describe the change operations that can apply on architecture definitions. It automatically searches for a sequence of operations that both changes the architecture as requested and preserves architecture consistency and coherence properties. The feasibility of the evolution management approach is demonstrated through the experimentation of three evolution scenarios, each addressing a change at different abstraction level. The experimentation relies on an implementation of a search-based software engineering approach mixing software engineering and optimization and integrates our own solver with specific heuristics that significantly improve calculation time.

In algorithmic computing, the program follows a predefined set of rules – the algorithm. The analyst/designer of the program analyzes the intended tasks of the program, defines the rules for its expected behaviour and programs the implementation. The creators of algorithmic software must therefore foresee, identify and implement all possible cases for its behaviour in the future application! However, what if the problem is not fully defined? Or the environment is uncertain? What if situations are too complex to be predicted? Or the environment is changing dynamically? In many such cases algorithmic computing fails. In such situations, the software needs an additional degree of freedom: Autonomy! Autonomy allows software to adapt to partially defined problems, to uncertain or dynamically changing environments and to situations that are too complex to be predicted. As more and more applications – such as autonomous cars and planes, adaptive power grid management, survivable networks, and many more – fall into this category, a gradual switch from algorithmic computing to autonomic computing takes place. Autonomic computing has become an important software engineering discipline with a rich literature, an active research community, and a growing number of applications.

Submitted by Johnny Rodrigues (johnnyrodrigues@ufcg.edu.br) on 2018-08-29T17:04:59Z No. of bitstreams: 1 RODRIGO REBOUÇAS DE ALMEIDA - DISSERTAÇÃO PPGCC 2005..pdf: 815922 bytes, checksum: fdb76afed4f4ef1c3cadf3bafe4d740f (MD5) / Made available in DSpace on 2018-08-29T17:04:59Z (GMT). No. of bitstreams: 1 RODRIGO REBOUÇAS DE ALMEIDA - DISSERTAÇÃO PPGCC 2005..pdf: 815922 bytes, checksum: fdb76afed4f4ef1c3cadf3bafe4d740f (MD5) Previous issue date: 2005-02-01 / A competitividade das empresas, que há alguns anos era ditada pela sua capacidade de vender mais e pelo menor preço, hoje está relacionada à capacidade de negociar no mercado globalizado, de vender produtos sem a limitação de fronteiras geográficas. Este contexto incentiva o crescimento das grandes empresas multinacionais e leva as pequenas e médias empresas a perderem mercado por sua incapacidade de competirem sozinhas com as grandes marcas. Para solucionar este problema, as pequenas e médias empresas têm se organizado em rede, interagindo com seus fornecedores e clientes mais próximos geograficamente e recebendo apoio dos organismos de desenvolvimento local, criando o que chamamos de Arranjos Produtivos Locais, ou APLs. Até então as soluções de TI não estavam preparadas para atender a este novo tipo de organização de empresas, onde prevalece a cultura de compartilhamento de informação, colaboração com concorrentes para atender a mercados maiores e interação entre as empresas e as entidades de desenvolvimento. Este trabalho propõe uma arquitetura de software para APLs, que busca atender aos requisitos desta organização de empresas e criar um modelo que expresse as preocupações técnicas com o projeto de uma solução de TI para este domínio de negócios. Um conjunto de empresas e especialistas em APLs fizeram parte do levantamento de requisitos e avaliação da arquitetura proposta. A arquitetura foi avaliada através da interação com os envolvidos no projeto, usando um método baseado em cenários. Por fim, um protótipo foi desenvolvido. / A few years ago, the competitiveness of an enterprise was dictated by its capacity to sell more and at lower price. Today it is defined by its capacity to negotiate on a global market, to sell products without geographic limitation. This context promotes the growth of big enterprises and forces small ones to lose market share because they cannot compete against the big brands. To solve this problem, small enterprises are working through networks, interacting with suppliers and customers which are close geographically, and receiving support from local development agencies. This kind of enterprise network is what we call Enterprise Clusters. Until now, IT solutions were not prepared to support this new kind of enterprise organization - where the culture of information sharing and collaboration with competitors to attend big markets prevails. This work proposes a software architecture for enterprise clusters. The architecture aims to attend cluster requirements, supporting a model that reflects technical requirements. A group of enterprises and cluster specialists participated on requirement elicitation and architectural review activities. Architecture evaluation was carried by a scenario based methodology. A prototype was developed.

A utilização de sistemas de gerência de documentos e de sistemas de gerência de workflow vem crescendo de forma expressiva nos últimos anos, motivados pela expectativa de obter-se benefícios organizacionais importantes, como o maior compartilhamento da informação e o aumento da eficiência dos processos. Pelo fato de a maioria dos processos organizacionais envolver a manipulação de documentos, é necessário, em grande parte das vezes, que esses sistemas trabalhem em conjunto. No entanto, a maioria das integrações entre tais produtos são proprietárias, causando prejuízos como a redução da liberdade de escolha dos usuários, a maior dificuldade de integração com sistemas legados e o aumento da dependência em relação aos fornecedores dos produtos. Para solucionar esse problema, este trabalho propõe uma arquitetura aberta de integração entre sistemas de gerência de documentos e sistemas de gerência de workflow. O fundamento dessa arquitetura está na utilização de dois padrões emergentes da indústria: o padrão DMA, proposto pela AIIM, e o padrão WAPI, proposto pela WfMC. O padrão DMA consiste de uma API, a ser invocada pelos aplicativos clientes de documentos, de uma SPI, a ser implementada e oferecida pelos sistemas de gerência de documentos, e de um middleware, responsável pela conexão entre os clientes e servidores de documentos. O padrão WAPI consiste de uma linguagem padrão para a definição de processos e de uma API, a ser invocada pelo aplicativo cliente de workflow e implementada pelo sistema de gerência de workflow. A arquitetura proposta compõe-se de três elementos. Primeiramente, um mecanismo integrado para a modelagem de documentos e workflow. Assim, é possível definir quais documentos serão manipulados pelo processo, e que operações cada participante poderá executar sobre ele. Esse mecanismo baseia-se exclusivamente nos padrões oferecidos pela WAPI e pela DMA. Em segundo lugar, é definido e implementado, na linguagem Java, um módulo de software denominado camada de serviços, oferecendo serviços integrados de gerência de documentos e gerência de workflow. Os métodos dessa camada invocam os métodos WAPI e DMA necessários à sua execução. Assim, qualquer DMS aderente à DMA pode ser integrado a qualquer WFMS aderente à WAPI, de forma completamente transparente. Por final, é desenvolvido um aplicativo cliente, também em linguagem Java, que acessa os métodos da camada de serviços, oferecendo uma interface gráfica para o usuário. Os resultados demonstram a viabilidade de uma integração aberta entre sistemas de gerência de documentos e sistemas de gerência de workflow. Ainda, mostram a importância de uma modelagem integrada de documentos e workflow. / The document management systems and the workflow management systems areas have been facing an impressive growth in the last years, driven by the desire to achieve important organizational benefits, as an increased information sharing and more efficient processes. Since most business processes involve document manipulation, it is often needed that these systems work together. However, most products are integrated in a proprietary way, therefore reducing user's freedom of choice, increasing the difficulty of legacy systems integration and rising the dependency from product vendors. In order to overcome this problem, this work proposes an open architecture for document management systems and workflow management systems integration. The architecture's fundamentals is the usage of two emerging industry standards: DMA, proposed by AIIM, and WAPI, proposed by WfMC. DMA consists of an API, to be invoked by client document applications, of an SPI, to be implemented and offered by document management systems, and of a middleware, responsible for connecting clients to document servers. WAPI consists of a standard process definition language and of an API, to be invoked by workflow client applications and implemented by workflow management systems. The proposed architecture is composed by three elements. First, an integrated mechanism for document and workflow modeling is defined. Therefore, it is possible to define which documents will be used in the process, and which operations each workflow participant will be allowed to execute over them. This approach is based exclusively on DMA and WAPI standards. Second, it is defined an implemented a software module called services layer, offering integrated document management and workflow management services, using the Java language. This layer's methods invoke the WAPI's and DMA's methods necessary for their execution. Therefore, any DMAcompliant DMS can be integrated to any WAPI-compliant WFMS, in a totally transparent way. Finally, a client application to access services layer's methods and offer the user a graphical interface is developed, also using the Java language. The results demonstrate the viability of an open integration between document management systems and workflow management systems. They also show the importance of an integrated document and workflow modeling.

Computer systems gain more space day by day in the lives of individuals, causing the demand for computerized solutions more and more sophisticated and accurate, become increasing. Thus, there is a requirement of effective quality assurance for software produced, checked by monitoring of quality attributes. However, the main current monitoring techniques are turning mainly to service-based systems, setting aside a large number of software. In this context, this work aims to discuss about the monitoring of quality attributes referenced by ISO/IEC 9126 standard. Decision trees will be set relating to the architectural elements monitoring issues, and also a tool that uses the concepts of Aspect-Oriented Programming to automate the process of monitoring the reliability and efficiency requirements by generating aspects-monitors intended for logging and recording exceptions given target system. Still be observed the case study disposal structured by the Goal/Question/Metric (GQM) paradigm, conducted with the purpose of analyze the feasibility of the developed solution which is a simplified way for architects and software developers to define monitors to measure quality attributes in their systems. / Coordenação de Aperfeiçoamento de Pessoal de Nível Superior / Os sistemas computacionais ganham dia a dia mais espaço na vida dos indivíduos, fazendo com que a demanda por soluções computadorizadas, cada vez mais sofisticadas e precisas, seja crescente. Assim, há a exigência de efetivas garantias de qualidade aos softwares produzidos, conferidas pela monitoração dos atributos de qualidade. Contudo, as principais técnicas de monitoração atuais voltam-se, sobretudo, aos sistemas baseados em serviços, deixando de lado uma grande parcela de softwares. Neste contexto, o presente trabalho possui como objetivo discutir acerca da monitoração dos atributos de qualidade referenciados pela norma ISO/IEC 9126. Serão definidas árvores de decisão, que relacionarão os elementos arquiteturais às questões de monitoração, e ainda uma ferramenta que utilizará conceitos da Programação Orientada a Aspectos para automatizar o processo de monitoração dos requisitos confiabilidade e eficiência, através da geração de aspectos-monitores destinados ao logging e registro de exceções de determinado sistema-alvo. Ainda será observada a disposição de estudo de caso estruturado pelo paradigma Goal/Question/Metric (GQM), realizado com a finalidade de analisar a viabilidade da solução desenvolvida que representa uma maneira simplificada para que arquitetos e desenvolvedores de softwares definam monitores para aferir atributos de qualidade em seus sistemas.

Coordenação de Aperfeiçoamento de Pessoal de Nível Superior / In the documentation of software architecture, it must be considered two relevant points: i) the architecture is composed by several visions, and ii) each vision identifies a set of components and interactions which allows a better understanding between developers and system programmers. The documentation of the components, when treating reusability, must present a set of information concerning its functionality and applicability in order to adapt them in applications of same domain. When we think of interaction among components, the information concerning the communication messages must be well identified so that the process of working may be clearly understood. This work shows the creation of a catalog of documentation patterns for the architecture of image processing and analysis systems approaching on the concept of design patterns and architecture visions of UML which will be used as the base for designing the Patterns. Through its use, the developers will be more sure of which is necessary to document and safer when reusing components previously tested and documented. It is also shown in this work the development of templates environment of the Patterns in the tool MoinMoinWiki aiming at creating a scenery for collaborative work and also a repository of information on documentation of systems architecture and frameworks within image domain. / Na documentação da arquitetura de software deve ser considerado dois pontos relevantes: i) a arquitetura é composta por várias visões, e ii) cada visão identifica um conjunto de componentes e interações, permitindo melhor compreensão entre desenvolvedores e projetistas do sistema. A documentação dos componentes, quando se tratando de reusabilidade, deve apresentar um conjunto de informações referente a sua funcionalidade e aplicabilidade a fim de adaptá-los em aplicações de mesmo domínio. Quando pensando em interação entre componentes, as informações relacionadas às mensagens de comunicação devem ser bem identificadas, para que o processo de funcionamento seja claramente entendido. Este trabalho apresenta a criação de um catálogo de Padrões de Documentação da Arquitetura de sistemas e frameworks para processamento e análise de imagens, abordando o conceito de design patterns e visões arquiteturais da UML, as quais servirão de base para elaboração dos padrões. Através do uso desses, os desenvolvedores sentirão mais clareza do que é necessário documentar e mais seguros em reusar componentes previamente testados e documentados. Apresenta-se também neste trabalho, o desenvolvimento de um ambiente de templates dos Padrões na ferramenta MoinMoinWiki, com o objetivo de criar um cenário para o trabalho colaborativo, e também um repositório de informações sobre a documentação da arquitetura de sistemas e frameworks no domínio de imagens.

A utilização de sistemas de gerência de documentos e de sistemas de gerência de workflow vem crescendo de forma expressiva nos últimos anos, motivados pela expectativa de obter-se benefícios organizacionais importantes, como o maior compartilhamento da informação e o aumento da eficiência dos processos. Pelo fato de a maioria dos processos organizacionais envolver a manipulação de documentos, é necessário, em grande parte das vezes, que esses sistemas trabalhem em conjunto. No entanto, a maioria das integrações entre tais produtos são proprietárias, causando prejuízos como a redução da liberdade de escolha dos usuários, a maior dificuldade de integração com sistemas legados e o aumento da dependência em relação aos fornecedores dos produtos. Para solucionar esse problema, este trabalho propõe uma arquitetura aberta de integração entre sistemas de gerência de documentos e sistemas de gerência de workflow. O fundamento dessa arquitetura está na utilização de dois padrões emergentes da indústria: o padrão DMA, proposto pela AIIM, e o padrão WAPI, proposto pela WfMC. O padrão DMA consiste de uma API, a ser invocada pelos aplicativos clientes de documentos, de uma SPI, a ser implementada e oferecida pelos sistemas de gerência de documentos, e de um middleware, responsável pela conexão entre os clientes e servidores de documentos. O padrão WAPI consiste de uma linguagem padrão para a definição de processos e de uma API, a ser invocada pelo aplicativo cliente de workflow e implementada pelo sistema de gerência de workflow. A arquitetura proposta compõe-se de três elementos. Primeiramente, um mecanismo integrado para a modelagem de documentos e workflow. Assim, é possível definir quais documentos serão manipulados pelo processo, e que operações cada participante poderá executar sobre ele. Esse mecanismo baseia-se exclusivamente nos padrões oferecidos pela WAPI e pela DMA. Em segundo lugar, é definido e implementado, na linguagem Java, um módulo de software denominado camada de serviços, oferecendo serviços integrados de gerência de documentos e gerência de workflow. Os métodos dessa camada invocam os métodos WAPI e DMA necessários à sua execução. Assim, qualquer DMS aderente à DMA pode ser integrado a qualquer WFMS aderente à WAPI, de forma completamente transparente. Por final, é desenvolvido um aplicativo cliente, também em linguagem Java, que acessa os métodos da camada de serviços, oferecendo uma interface gráfica para o usuário. Os resultados demonstram a viabilidade de uma integração aberta entre sistemas de gerência de documentos e sistemas de gerência de workflow. Ainda, mostram a importância de uma modelagem integrada de documentos e workflow. / The document management systems and the workflow management systems areas have been facing an impressive growth in the last years, driven by the desire to achieve important organizational benefits, as an increased information sharing and more efficient processes. Since most business processes involve document manipulation, it is often needed that these systems work together. However, most products are integrated in a proprietary way, therefore reducing user's freedom of choice, increasing the difficulty of legacy systems integration and rising the dependency from product vendors. In order to overcome this problem, this work proposes an open architecture for document management systems and workflow management systems integration. The architecture's fundamentals is the usage of two emerging industry standards: DMA, proposed by AIIM, and WAPI, proposed by WfMC. DMA consists of an API, to be invoked by client document applications, of an SPI, to be implemented and offered by document management systems, and of a middleware, responsible for connecting clients to document servers. WAPI consists of a standard process definition language and of an API, to be invoked by workflow client applications and implemented by workflow management systems. The proposed architecture is composed by three elements. First, an integrated mechanism for document and workflow modeling is defined. Therefore, it is possible to define which documents will be used in the process, and which operations each workflow participant will be allowed to execute over them. This approach is based exclusively on DMA and WAPI standards. Second, it is defined an implemented a software module called services layer, offering integrated document management and workflow management services, using the Java language. This layer's methods invoke the WAPI's and DMA's methods necessary for their execution. Therefore, any DMAcompliant DMS can be integrated to any WAPI-compliant WFMS, in a totally transparent way. Finally, a client application to access services layer's methods and offer the user a graphical interface is developed, also using the Java language. The results demonstrate the viability of an open integration between document management systems and workflow management systems. They also show the importance of an integrated document and workflow modeling.