SOA : LES IMPACTS SUR LE CYCLE DE VIE DU PROJET DE DÉVELOPPEMENT LOGICIEL

Conceptualisée par le Gartner Group, leader mondial dans la fourniture de recherches et d’analyses dans l’industrie des technologies de l’information (TI), la notion d’architecture axée sur les services (notée SOA pour Service Oriented Architecture) est présentée comme le bon modèle pour le développement des applications d’entreprise, aujourd’hui et dans le futur (Marks et Bell, 2006). D’après la littérature, le développement d’applications d’entreprise fondées sur SOA présente de nouveaux défis : apparition de nouvelles activités, de nouveaux rôles et de nouvelles tâches au niveau de l’entreprise ; nécessité d’avoir de nouveaux outils de support au développement ; incapacité des méthodes de développement traditionnelles à soutenir le développement axé sur les services ; etc. Des ajustements doivent donc être apportés au cycle de vie du projet de développement logiciel (CVP) pour pouvoir s’adapter à cette nouvelle façon de construire les applications d’entreprise, et permettre, par conséquent, une gestion de projet plus efficace. \ud L’objectif de notre recherche est de savoir si la mise en œuvre d’une SOA par une organisation apporte des changements aux rôles et aux tâches du CVP. Pour atteindre son objectif, notre recherche prend en considération les aspects spécifiques soulignés dans la littérature SOA, ainsi que les résultats d’une étude de cas exploratoire menée auprès de deux organisations ayant entamé une initiative SOA

Services for Business Processes in EA – Are They in Relation?

Business services arguably play a central role in service-based information systems as they would fill in the gap between the technicality of Service-Oriented Architecture and the business processes captured in Enterprise Architecture. Business services have distinctive features that are not typically observed in plain Web services. The representation of business services requires that we view human activity and human-mediated functionality through the lens of computing and systems engineering. We give insights into the modeling of business services and relationships between them. This work sheds light on the analysis, design and reusability of business-aware services that business owners, entrepreneurs and business architects alike would find useful when dealing with their service ecosystem

On Business Services Representation – The 3 x 3 x 3 Approach

The increasing popularity and influence of service-oriented computing give rise to the need of representational and methodological supports for the development and management of business services. From an IT perspective, there is a proliferation of methods and languages for representing Web services. Unfortunately, there has not been much work in modeling high-level services from a business perspective. Modeling business services should arguably capture their inherent features, along with many other representational artifacts. We propose a novel approach for business services representation featuring a three-dimensional representational space of which dimensions stand for the service consumer, service provider and service context. We also discuss how the proposed representation approach provides methodological supports to the area of service orientation. Finally, we present in-progress work on the application of our approach

The two cultures and the internet revolution

The service-orientation paradigm has not only become prevalent in the software systems domain in recent years, but is also increasingly applied on the business level to restructure organisational capabilities. In this paper, we present the results of an extensive literature review of 30 approaches related to service identification and analysis for both domains. Based on the consolidation of a superset of comparison criteria for service-oriented methodologies found in related literature, we compare and evaluate the different characteristics of service engineering methods with a focus on service analysis. Although a close business and IT alignment is regarded as one of the core beneficial promises of service-orientation, our analysis suggests that there is a lack of unified, comprehensive methodology for service identification and analysis integrating and addressing both domains. Thus, we discuss how our results can inform directions for future research in this area

Service-oriented design of environmental information systems

Service-orientation has an increasing impact upon the design process and the architecture of environmental information systems. This thesis specifies the SERVUS design methodology for geospatial applications based upon standards of the Open Geospatial Consortium. SERVUS guides the system architect to rephrase use case requirements as a network of semantically-annotated requested resources and to iteratively match them with offered resources that mirror the capabilities of existing services

Um modelo de capacidade e maturidade para melhoria de processo de software para SaaS colaborativo

Tese (doutorado) - Universidade Federal de Santa Catarina, Centro Tecnológico, Programa de Pós-Graduação em Engenharia de Automação e Sistemas, Florianópolis, 2013.Atualmente, o cenário de desenvolvimento e disponibilização de software se mostra altamente exigente e dinâmico. SaaS (Software-as-a-Service) traz consigo uma série de vantagens que atraem provedores e clientes para tirarem proveito do cloud computing. Esses novos paradigmas permitem (com mais facilidade) a terceirização das soluções de TI e a colaboração entre provedores de serviços de software, tentando buscar novas oportunidades se beneficiando das alianças. As formas como as novas tecnologias e conceitos se relacionam, mudam e surgem, são muito dinâmicas, gerando grande cobrança nas empresas provedoras de serviço de software, para que elas acompanhem essas mudanças. A confiança na contratação dos serviços SaaS é uma necessidade que surge junto a essa mudança de paradigma computacional. Existem diversas frentes que vêem apoiar uma possível resolução deste problema, e uma delas é a adoção de melhoria de processo de software nesses provedores de serviços, cujas premissas da Engenharia de Software já são bastante difundidas, como fazem a norma ISO/IEC 15504 e o CMMI-DEV. Porém, os atuais modelos de referência e normas que norteiam essa necessidade são voltadas para o desenvolvimento de software tradicional, não cobrindo totalmente um ambiente de desenvolvimento SaaS e colaboração. Alguns modelos voltados para serviços também já estão disponíveis, como o CMMI for services e o MPS.br guia geral de serviços, porém, eles apresentam "serviços" como sendo um serviço atendimento ao cliente, e não como serviço de software, como é trazido nesta tese. Com isso, nesta tese de doutorado foi desenvolvido um Modelo de Capacidade e Maturidade para Melhoria de Processo de Software para Software-as-a-Service e para Colaboração. Esse Modelo é um repositório de boas práticas de processos (de desenvolvimento de serviços de software e colaboração), baseados na engenharia de software e princípios de gestão do processo. Ele é organizado em níveis de capacidade e maturidade, projetado para melhorar os processos. Esse Modelo vem oferecer uma possibilidade de adequação às exigências de qualidade para os provedores, oferecendo mais argumentos positivos em sua contratação e potencializando a colaboração entre os provedores. Abstract : Nowadays, the scenario of software development and availability hasshown highly demanding and dynamic. Software-as-a-Service (SaaS)brings a lot of advantages that is attracting providers and customers whoare already familiar with the facility coming from cloud computing.These new paradigms allow (more easily) outsourcing of IT solutionsand collaboration among providers (trying to reach new opportunities tobenefit from alliances). The ways in which this new technologies andconcepts are related, emerge and change are very dynamic, generating ahuge demand to software development providers. Trustworthiness in thehiring of SaaS services is a necessity that comes close to this paradigmshift. There are several options that support this problem, and one ofthem is implement software process improvement of services providers,whose premises the Software Engineering are already known, likeISO/IEC 15504 standard and CMMI-DEV. However, current referencemodels and standards available are geared towards the development oftraditional software, do not completely covering SaaS developmentenvironment. Some models focused to services are available like CMMIfor services and MPS.br general guide for services, but they introducethe term ?service? like a customer service, differently that term softwareservice that is assumed in this thesis. Thus, in this doctoral thesis wasdeveloped a Capability and Maturity Model for Software ProcessImprovement for Collaborative Software-as-a-Service. This Model is arepository of best practices to Services Development Processes (SaaS)and Collaboration. Based on software engineering and managementprinciples of the process, it is organized into capability and maturitylevels, designed to improve processes. This Model can offer a chance toadapt to the quality demands for providers, offering more positivearguments in its hiring and supporting the collaboration among providers

Metodologia para desenvolvimento de soluções baseadas em arquitetura orientada a serviços para força de trabalho terceirizada

Dissertação (mestrado)–Universidade de Brasília, Faculdade de Tecnologia, Departamento de Engenharia Elétrica, 2013.Para que os sistemas baseados em SOA obtenham os benefícios esperados, os princípios conhecidos da engenharia de software tradicional precisam ser adaptados para desenvolvimento orientado a serviços. São necessárias abordagens sistemáticas para a concepção, desenvolvimento e manutenção de sistemas orientados a serviços. Essa abordagem é conhecida como Engenharia de Software Orientada a Serviços - SOSE. A impossibilidade de utilização de metodologias de desenvolvimento SOA existentes, quer seja pela ausência de informações detalhadas ou, principalmente, pela desconsideração de forças de trabalho terceirizadas no processo, foi fator determinante para a elaboração deste trabalho. Para atingir o objetivo de criar uma metodologia de desenvolvimento de soluções baseadas em SOA, foram realizadas pesquisas bibliográficas e estudos de caso, tanto para sua elaboração como para sua validação em situação real de execução. A base da metodologia proposta é constituída de três pilares: a definição de unidades funcionais, onde são agrupadas tarefas e atividades técnicas relacionadas, definindo escopos claros de terceirização e responsabilidades; perfis profissionais, que explicitam as competências necessárias requeridas em cada etapa e; os processos e artefatos, que definem as atividades que devem ser realizadas e seus entregáveis. ______________________________________________________________________________ ABSTRACTFor systems based on SOA obtain the expected benefits, the known principles of traditional software engineering need to be adapted to service-oriented development. Systematic approaches are needed for the design, development and maintenance of service-oriented systems. This approach is known as Software Engineering Service Oriented - SOSE. The impossibility of using existing SOA development methodologies, either by lack of detailed information or mainly by disregard of outsourced workforces in the process, was the determining factor for the development of this work. To achieve the objective of creating a development methodology for SOA-based solutions, literature searches and case studies were conducted, for both its development and validation in the real implementation. The basis of the proposed methodology consists of three pillars: the definition of functional units, where tasks and technichal related activities are grouped, defining outsourcing and responsibilities clear scopes; professional profiles, that explain the skills required at each stage and; processes and artifacts, that define the activities that must be performed and their deliverables

SOA : les impacts sur le cycle de vie du projet de développement logiciel

Conceptualisée par le Gartner Group, leader mondial dans la fourniture de recherches et d'analyses dans l'industrie des technologies de l'information (TI), la notion d'architecture axée sur les services (notée SOA pour Service Oriented Architecture) est présentée comme le bon modèle pour le développement des applications d'entreprise, aujourd'hui et dans le futur (Marks et Bell, 2006). Selon une étude effectuée par le Gartner Group, plus de 75 % des projets d'entreprise, à partir de 2008, reposeront sur les principes de SOA. Ce chiffre donne une idée sur l'ampleur du « phénomène » SOA, qui suscite tant d'intérêt de la part des chercheurs. Cependant, d'après la littérature, le développement d'applications d'entreprise fondées sur SOA présente de nouveaux défis: apparition de nouvelles activités, de nouveaux rôles et de nouvelles tâches au niveau de l'entreprise; nécessité d'avoir de nouveaux outils de support au développement; incapacité des méthodes de développement traditionnelles à soutenir le développement axé sur les services; etc. Des ajustements doivent donc être apportés au cycle de vie du projet de développement logiciel pour pouvoir s'adapter à cette nouvelle façon de construire les applications d'entreprise, et permettre, par conséquent, une gestion de projet plus efficace. L'objectif de notre recherche est de savoir si la mise en oeuvre d'une SOA par une organisation apporte des changements aux rôles et aux tâches du cycle de vie du projet de développement logiciel. Pour atteindre son objectif, notre recherche prend en considération les aspects spécifiques soulignés dans la littérature SOA, ainsi que les résultats d'une étude de cas exploratoire menée auprès de deux organisations ayant entamé une initiative SOA. La conclusion à laquelle nous sommes parvenus est que SOA introduit de nouvelles pratiques au niveau de l'organisation qui refaçonnent, lors des projets de développement logiciel, les rôles existants et les tâches qui leurs sont associées. ______________________________________________________________________________ MOTS-CLÉS DE L’AUTEUR : Architecture axée sur les services, Développement axé sur les services, Cycle de vie du projet de développement logiciel, Rôles