The subject of the thesis is an process analysis in the company AiP Safe, Ltd. First, theoretical approaches and methods for organization and business process analysis are summarized. The best known modeling notations are also described. For the analysis of AiP Safe, Ltd. was chosen BSP method and for process modeling was chosen BPMN notation. The result of the work is a suggestion to establish strategic goals and strategies to achieve them, change in the organizational structure, optimization of selected processes, introduction of new metrics, introduction of new information system and recommendations based on the SWOT analysis.

Une entreprise doit être capable de décrire et de demeurer réactive face à un événement endogène ou exogène. Une telle flexibilité peut s'obtenir par la gestion des processus d'entreprise (Business Process Management - BPM). Lors d'une démarche BPM, différentes transformations interviennent sur les modèles de processus développés par l'analyste métier et l'expert en technologies de l'information. Un non-alignement se crée entre ces modèles hétérogènes lors de leurs manipulations : il s'agit du "fossé métier-TI" tel que décrit dans la littérature. L'objectif de notre travail est de proposer un cadre méthodologique permettant un meilleur pilotage des processus métier, afin de tendre vers un alignement systématique de leur modélisation à leur implémentation au sein du système cible. A l'aide de concepts issus de l'ingénierie d'Entreprise et des Systèmes d'Informations dirigée par les modèles et des TI, nous définissons une démarche générique assurant une cohérence intermodèle. Son rôle est de conserver et de fournir toutes les informations liées à la structure et à la sémantique des modèles. En permettant la restitution intégrale d'un modèle transformé au sens de l'ingénierie inverse, notre plateforme permet une synchronisation entre modèle d'analyse et modèle d'implémentation. Le manuscrit présente également l'adéquation possible entre l'ingénierie des procédés et le BPM à travers un point de vue multi-échelle. / A company must be able to describe and to remain responsive against endogenous or exogenous events. Such flexibility can be obtained with the Business Process Management (BPM). Through a BPM approach, different transformations operate on process models, developed by the business analyst and IT expert. A non-alignment is created between these heterogeneous models during their manipulation: this is the "business-IT gap" as described in the literature. The objective of our work is to propose a methodological framework for a better management of business processes in order to reach a systematic alignment from their modelling to their implementation within the target system. Using concepts from Model-driven Enterprise and Information System engineering, we define a generic approach ensuring an intermodal consistency. Its role is to maintain and provide all information related to the model structure and semantics. By allowing a full restitution of a transformed model, in the sense of reverse engineering, our platform enables synchronization between analysis model and implementation model. The manuscript also presents the possible match between process engineering and BPM through a multi- erspective scale.

Orientador: Prof. Dr. Francisco de Assis Zampirolli / Dissertação (mestrado) - Universidade Federal do ABC, Programa de Pós-Graduação em Ciência da Computação, 2014. / Métodos e Processos de Engenharia de Software têm se tornado foco de pesquisas científicas, onde a qualidade, estimativa de custos e prazos são trabalhadas como boas práticas em desenvolvimento. A construção de um produto de software envolve algumas etapas, e a mais complexa saber precisamente o que construir. A precisão nesta etapa do projeto é essencial, pois se houver falha na especificação, haverá maior prejuíz ao final doprojeto do sistema de software. A principal razão para as falhas de projeto de software é o gerenciamento inadequado dos requisitos do sistema, gerando custos elevados para serem corrigidos nas fases seguintes ao levantamento de requisitos e insatisfac~ao para todos os envolvidos. Deste modo, produzir software com qualidade é uma tarefa complexa, que demanda entender, planejar e atender, provendo soluc~oes necessárias. Este trabalho tem como objetivo, apresentar uma metodologia para o desenvolvimento de especifícação de requisitos, com uma abordagem orientada ao alinhamento entre TI e Negócio, por meio de um processo de engenharia de requisitos, [integrando diagramas de Caso de Uso como Business Process Modeling Notation (BPMN). Por meio de estudos de caso aplicados a uma empresa operadora de planos privados de assistência a saúde. A metodologia se mostrou ecaz, com melhoria de 69,68% na redução dos custos no orcamento acordado. Alem disso, este trabalho de pesquisa encontra-se em funcionamento na empresa citada,otimizando recursos e atingindo melhores resultados para a organização. / Requirement Engineering Methods and Processes have become a focus point for scientic research, in which quality, cost estimates and time frames are elaborated as good practices in development. Building a software product includes several phases, and the most complex is to know exactly what to build. Precision is essential during this phase of the project, because if the specication fails, there will be greater loss at the end of the software system project. The main reason for software project failures is inept management of system requirements, generating high costs that have to be corrected in the phases following requirement survey, and creating dissatisfaction for all those involved. Thus, producing quality software is a complex task, which demands understanding, planning, and compliance to provide the necessary solutions. This paper presents a methodology for developing requirement specifications, with an approach directed towards aligning IT and Business through a requirement engineering process integrating Use Case with Business Process Modeling Notation. Through case studies presented and applied at a private health care insurance company, the methodology proved to be eective, by reducing exceeding the agreed-upon budget by 69.68%. Additionally, this study is still on-going at the abovementioned company, optimizing resources and reaching better results for the organization.

<p>In electronic commerce, systems development is based on two fundamental types of models, business models and process models. A business model is concerned with value exchanges among business partners, while a process model focuses on operational and procedural aspects of business communication. Thus, a business model defines the what in an e-commerce system, while a process model defines the <i>how</i>. Business process design can be facilitated and improved by a method for systematically moving from a business model to a process model. Such a method would provide support for traceability, evaluation of design alternatives, and seamless transition from analysis to realization. This work proposes a unified framework that can be used as a basis to analyze, to interpret and to understand different concepts associated at different stages in e-Commerce system development. In this thesis, we illustrate how UN/CEFACT’s recommended metamodels for business and process design can be analyzed, extended and then integrated for the final solutions based on the proposed unified framework. Also, as an application of the framework, we demonstrate how process-modeling tasks can be facilitated in e-Commerce system design. The proposed methodology, called BP³ stands for Business Process Patterns Perspective. The BP³ methodology uses a question-answer interface to capture different business requirements from the designers. It is based on pre-defined process patterns, and the final solution is generated by applying the captured business requirements by means of a set of production rules to complete the inter-process communication among these patterns.</p>

In electronic commerce, systems development is based on two fundamental types of models, business models and process models. A business model is concerned with value exchanges among business partners, while a process model focuses on operational and procedural aspects of business communication. Thus, a business model defines the what in an e-commerce system, while a process model defines the how. Business process design can be facilitated and improved by a method for systematically moving from a business model to a process model. Such a method would provide support for traceability, evaluation of design alternatives, and seamless transition from analysis to realization. This work proposes a unified framework that can be used as a basis to analyze, to interpret and to understand different concepts associated at different stages in e-Commerce system development. In this thesis, we illustrate how UN/CEFACT’s recommended metamodels for business and process design can be analyzed, extended and then integrated for the final solutions based on the proposed unified framework. Also, as an application of the framework, we demonstrate how process-modeling tasks can be facilitated in e-Commerce system design. The proposed methodology, called BP3 stands for Business Process Patterns Perspective. The BP3 methodology uses a question-answer interface to capture different business requirements from the designers. It is based on pre-defined process patterns, and the final solution is generated by applying the captured business requirements by means of a set of production rules to complete the inter-process communication among these patterns.

The first steps in the software development life cycle are crucial for a successful software product. In this scenario, modeling activities play an important role in the requirements specification and other activities throughout the Project. Although the modeling activities of business processes and activities related to Requirements Engineering are recognized as important individually, some approaches have considered the integration of these activities. In this context, this master thesis proposes an approach and corresponding guidelines for integration of modeling software requirements with SysML and modeling of business processes and workflows with the support of BPMN. This relationship is represented with both graphical models and tabular format. Therefore, software developers can track business processes and software requirements already during the initial activities of the software development process. The proposed approach has been presented to a group of systems analysts, university professors and master students. These participants answered to a questionnaire based on TAM theory mostly agreeing that integrating BPMN and SysML will contribute positively for documentation , validation and tracking requirements. Despite their interest in learning more about the two languages, they declared di culty in performing integration and the cost to use this proposal in projects in industry. This work has also presented a report of the experience in HU / UFS and a guide to integration of BPMN and SysML to assist the development of a patient’s Electronic Health Record in a public hospital. / Os primeiros passos no ciclo de vida de desenvolvimento de software são cruciais para um produto de software bem sucedido. Neste cenário, as atividades de modelagem desempenham um papel importante na especificação de requisitos e demais atividades em todo o projeto. Embora as atividades de modelagem de processos de negócio e as atividades relacionadas com a Engenharia de Requisitos sejam reconhecidas como importantes individualmente, algumas abordagens têm considerado a integração destas atividades. Neste contexto, este trabalho propõe uma abordagem e orientações correspondentes à integração dos modelos de processos de negócio elaborados com BPMN e modelos de requisitos de software com SysML. Essa relação é representada tanto com modelos gráficos como em formato tabular. Portanto, os desenvolvedores de software podem rastrear os processos de negócio e requisitos de software já durante as atividades iniciais do processo de desenvolvimento de software. A abordagem proposta foi apresentada a um grupo de analistas de sistemas, professores universitários que lecionam a disciplina Engenharia de Software e estudantes de mestrado do curso de Ciência da Computação da Universidade Federal de Sergipe, e respondendo a um questionário baseado na teoria TAM afirmaram que a integração BPMN e SysML irá contribuir positivamente nas atividades de documentação, validação e rastreamento de requisitos. Apesar do interesse em aprender mais sobre as duas linguagens, os participantes na pesquisa declararam a dificuldade em realizar a integração e o custo em utilizar esta proposta em projetos reais. Neste trabalho foi ainda apresentado um relato da experiência no Hospital Universitário da Universidade Federal de Sergipe (HU/UFS) e um guia para integração de modelos elaborados com BPMN e SysML, para auxiliar o desenvolvimento de um prontuário eletrônico do paciente em um hospital público.

Today’s companies are struggling with the competitive environment driven by resource scarcity, technical progress and market demand for increased value and flexibility. For these reasons companies are shifting their focus from selling products to selling need fulfillment. The result-oriented product-service (PSS) is a PSS type that provides value mainly through delivery of services with the premise of the producer taking responsibility over the entire product life cycle. It is highlighted in the literature as a business strategy to generate a high profit and stable the revenue. Despite the new market opportunities related to the provision of PSS, it inherently comes with complexity linked to the extended responsibility. More importantly, very little is mentioned in the PSS literature regarding real case PSS development and how service-oriented PSS contracting impacts Small and Medium-sized Enterprises (SMEs). The objective of this thesis is to examine how result-oriented PSS can create new opportunities for SMEs. It is targeting to explore this topic from a cost and value creation perspective for both the company and customer. To achieve the objective a main research question is stated which answer is given by answering the two sub questions as below. How can a result-oriented product-service system be implemented in small and medium-sized enterprises? 1. What result-oriented PSS solution can be designed for the recycling equipment industry to increase the value for both the manufacturer and the customer? 2. What are the financial implications of a result-oriented PSS? To explore answers for the research questions, a case study inquiry is carried out on MRT (Mercury Recovery Technology) System International AB. It is a small international recycling equipment manufacturer in Karlskrona. A PSS development process resulting in a new concept referred to as “Pay per screen” is developed. The development and analysis of the result-oriented PSS shows that it is more profitable for the company to offer the proposed Pay per screen concept compared to the current product- oriented business. Even the customer has proven to be profitable while providing several advantages such as avoid being responsible for initial investment and maintenance costs. / Dagens företag kämpar med att hantera den konkurrenskraftiga miljön som drivs av resursbrist, teknisk utveckling och efterfrågan av ökat värde och flexibilitet. Av dessa skäl byter företagen fokus från att sälja produkter till att uppfylla behov. Det resultatorienterade produkttjänstesystemet (PSS) är en sorts PSS som ger värde huvudsakligen genom att leverera tjänster med förutsättningen att producenten tar ansvar över hela produktens livscykel. Den framträder i litteraturen som en ny strategisk affärsstrategi som genererar en hög vinst och stabiliserar inkomstflödet. Trots de nya marknadsmöjligheterna i samband med tillhandahållandet av PSS följer komplexitet med det utökade ansvaret. Dessutom nämns mycket lite i PSS-litteraturen om PSS-utveckling i ett verklighetsbaserat fall och hur tjänsteorienterad PSS-koncept påverkar små och medelstora företag. Syftet med detta examensarbete är att undersöka hur resultatorienterade produkttjänstesystem kan skapa nya möjligheter för små och medelstora företag. Det riktar sig till att utforska detta ämne ur ett kostnads- och värdeskapande perspektiv för både företaget och kunden. För att uppnå målet anges en huvudforskningsfråga vilket delvis svaras genom att svara på de två delfrågorna nedan. Hur kan ett resultatorienterat produktservice system genomföras i små och medelstora företag? 1. Vilken resultatorienterad PSS-lösning kan utformas för återvinningsindustrin för att öka värdet för både tillverkaren och kunden? 2. Vilka är de ekonomiska konsekvenserna av ett resultatorienterat PSS? För att utforska svaren på forskningsfrågorna utförs en fallstudie på MRT (Mercury Recovery Technology) System International AB. Det är en liten internationell tillverkare av återvinningsutrustning i Karlskrona. En PSS-utvecklingsprocess som resulterar i ett nytt koncept som kallas "Pay per screen" är utvecklat. Utvecklingen och analysen av resultatorienterad PSS visar att det är mer lönsamt för företaget att erbjuda det föreslagna Pay per screen konceptet. För även kunden har det visat sig vara lönsamt samtidigt som ger en rad fördelar så som att slippa ansvara för investerings- och underhållskostnader.