Submitted by Jean Medeiros (jeanletras@uepb.edu.br) on 2017-02-16T18:47:29Z No. of bitstreams: 1 PDF - Eliclenes Porto.pdf: 5725031 bytes, checksum: 8183ce7e099ad97e170841dfd7fd1d5c (MD5) / Approved for entry into archive by Secta BC (secta.csu.bc@uepb.edu.br) on 2017-03-07T16:47:56Z (GMT) No. of bitstreams: 1 PDF - Eliclenes Porto.pdf: 5725031 bytes, checksum: 8183ce7e099ad97e170841dfd7fd1d5c (MD5) / Made available in DSpace on 2017-03-07T16:47:56Z (GMT). No. of bitstreams: 1 PDF - Eliclenes Porto.pdf: 5725031 bytes, checksum: 8183ce7e099ad97e170841dfd7fd1d5c (MD5) Previous issue date: 2016-12-28 / Among the diseases that most concern public health is chronic kidney disease (CKD), considered the great epidemic of this millennium. CKD is neglected at the primary level of attention, since most patients are only aware of their condition in the late stages of the disease. Objective: To describe the functional requirements of a system that will assist the monitoring of chronic kidney disease in primary health care. Methods: It is a research, technological, exploratory, experimental, with a qualitative approach, based on a process of requirements engineering, which aims to specify a future system called Epidemiorim. The methodological path to achieve the objectives was divided into five stages: the first one was the identification of the functional requirements and future users of the system; The second stage corresponded to the documentation of the functional requirements elicited; The third, in the development of a document with the possible screens of the system in paper A4; In the fourth stage, there was negotiation of the requirements and implementation of a prototype; And the fifth and final step consisted in validati ng the main functional requirements of the system. The validation stage occurred after the use of the prototype by professionals of the family health teams of the municipality of Montadas-PB, who enrolled, evaluated and monitored the DRC in 99 patients. The reports generated in the prototype were still analyzed to verify the prevalence of the disease in the studied population, demonstrating that there was a second research coupled in the study being of the observational, transversal and descriptive type with a quantitative approach. Results: The documents developed by the client of the system in the first three stages were enough for the development team to implement a prototype able to both assist the Family health teams to monitor the CKD and generate repo rts with epidemiological data. The finding that the prototype was able to meet these demands occurred after the validation of 16 functional requirements in the fifth and final stage. The analysis of reports generated in the prototype showed that the prevalence of CKD in the sample was of 17.2%, and a second renal evaluation in these patients is still necessary to confirm this index. Conclusion: Based on the Epidemiorim prototype, whose requirements were based on the guidelines of the Ministry of Health regarding the management of CKD in SUS, the research objectives were reached. Thus, the Epidemiorim presented an effective partial system, either for providing the family health teams with the follow-up in their work process of the guidelines that are recommended to them by the Ministry of Health, or as a tool that will contribute to the patient Of risk to have a complete health care, or for the municipal management, that can refer this patient to the nephrologist in a timely manner and will have at his disposal epidemiological reports of the disease for the planning of health actions. / Introdução: Entre as doenças que mais preocupam a saúde pública está a doença renal crônica (DRC), considerada como a grande epidemia deste milênio. A DRC apresenta-se negligenciada no nível primário de atenção, uma vez que a maioria dos pacientes só tem conhecimento de sua condição nos estágios finais da doença. Objetivo: Descrever os requisitos funcionais de um sistema que auxiliará o monitoramento da doença renal crônica na atenção primária à saúde. Métodos: Trata-se de uma pesquisa de natureza tecnológica, exploratória, experimental, com abordagem qualitativa, fundamentada em um processo de engenharia de requisitos, que visa especificar um futuro sistema intitulado de Epidemiorim. O caminho metodológico para atingir os objetivos foi dividido em cinco etapas: a primeira, tratou-se da identificação dos requisitos funcionais e futuros usuários do sistema; a segunda etapa correspondeu a documentação dos requisitos funcionais elicitados; a terceira, no desenvolvimento de um documento com as possíveis telas do sistema em papel A4; na quarta etapa houve a negociação dos requisitos e implementação de um protótipo; e a quinta e última etapa consistiu na validação dos principais requisitos funcionais do sistema. A etapa de validação ocorreu após o uso do protótipo por profissionais das equipes de saúde da família do município de Montadas-PB, que cadastraram, avaliaram e monitoraram a DRC em 99 pacientes adscritos. Os relatórios gerados no protótipo ainda foram analisados para verificar a prevalência da doença na população estudada, demonstrando haver uma segunda pesquisa acoplada nesse trabalho, sendo do tipo observacional, transversal e descritiva com abordagem quantitativa. Resultados: Os documentos desenvolvidos pelo cliente do sistema nas três primeiras etapas foram suficientes para que a equipe de desenvolvimento implementasse um protótipo capaz, tanto de auxiliar as eSF a monitorar a DRC, quanto gerar relatórios com dados epidemiológicos da mesma. A constatação que o protótipo era capaz de atender a essas demandas ocorreu após a validação de 16 requisitos funcionais na quinta e última etapa. A análise de relatórios gerados no protótipo mostrou que a prevalência da DRC na amostra foi de 17,2%, sendo necessária ainda uma segunda avaliação renal nesses pacientes para confirmação desse índice. Conclusão: A partir do protótipo do Epidemiorim, cujos requisitos tiveram por base as diretrizes do Ministério da Saúde quanto ao manejo da DRC no SUS, os objetivos da pesquisa foram alcançados. Sendo assim, o Epidemiorim apresentou-se um sistema parcial eficaz, seja por propiciar às equipes de saúde da família o seguimento no seu processo de trabalho das diretrizes que lhes são preconizadas pelo Ministério da Saúde, seja como uma ferramenta que contribuirá para que o paciente de risco passe a ter um cuidado de saúde integral, seja para a gestão municipal, que poderá referenciar esse paciente ao nefrologista em tempo oportuno e terá a sua disposição relatórios epidemiológicos da doença para o planejamento de ações em saúde.

A preocupação da engenharia de software esteve por muito tempo relacionada a aspectos da funcionalidade do sistema, ou seja, com \"o que\" e \"como\" fazer e não com o \"por que\" fazer. Tais aspectos, envolvidos nos processos existentes, buscam a definição das propriedades desejadas, em lugar de observarem a informação de uma forma mais ampla, começando com as necessidades do próprio negócio, ou dos objetivos dos sistemas nele embutidos. As técnicas de análise estruturadas, diagrama de fluxo de dados e modelagem entidade e relacionamento modelam importantes conceitos para o desenvolvimento de sistemas, mas não buscam por soluções alternativas inovadoras aos problemas da organização. É comum encontrar situações onde o sistema não satisfaz às reais necessidades do negócio, embora esteja tecnicamente correto. O entendimento dos aspectos sociais, organizacionais, técnicos, jurídicos e econômicos é essencial para a realização de um bom trabalho de engenharia de requisitos. Nesse sentido, a modelagem organizacional facilita a compreensão do ambiente empresarial e é reconhecida como uma atividade valiosa pela engenharia de requisitos. O modelo organizacional representa o \"mundo\" onde se aplicam as regras do negócio. O entendimento das regras do negócio é muito importante para a organização ser flexível em um ambiente de crescente competitividade. Com a necessidade de se ter a modelagem dos aspectos relativos à organização para que o sistema atenda as suas reais necessidades, o presente trabalho tem como objetivo investigar o processo de desenvolvimento de software buscando conhecer técnicas ou métodos que atendem aos requisitos organizacionais, enfatizando o uso de regras do negócio com a finalidade de obter a especificação de requisitos. / The software engineering\'s focus were for a long time related to system\'s functionality aspects, or with \"what\" and \"how\" to do, and not with \"why\" to do. Those aspects in the existents process are looking for the definition of the desired proprieties instead observe the information in a more large aspect, beginning with the business needs itself or the systems goals inserted in it. The structure analysis techniques, flux data diagram, and relationship and entity modeling form important concepts for systems development but do not search for innovating alternatives solutions for organization\'s problems. It is very common to find situations were the system does not satisfy the real business needs, thought it is technically correct. The comprehension of social, organizational, technical, juridical and economics aspects are essential for a good realization of requirements in engineering work. In that way the enterprise modeling makes the business environment comprehension easier and is recognized as a value activity by the requirements engineering. The enterprise model represents the \"world\" where the business rules are applied. The comprehension of the business rules is very important so the organization can be flexible in a growing competitive environment. With the necessity to have a modeling of the relative aspects to the organization so the system can accomplish the real needs, this present research has the objective to investigate a software development process trying to find techniques or methods that answer the enterprise\'s requirement, emphasizing the use of business rules to obtain the specifics requirements.

Business process models are an important source of information for the development of information systems. However, changes in the environment can a ect the way business processes are performed. In order to obtain models that re ect the changes it is necessary to continuously check between model and reality. Good business processes need to be up-to-date and automated to represent the organizational environment. Thus, it is of paramount importance to represent adequately variability in Business Process Models. Representing and con guring business processes variability for a speci c organization allows the proper execution of processes. In addition, dynamic environment calls for exible con guration processes that can meet stakeholders' goals. However, selecting a con guration for business process is a challenging activity. Even though current approaches allow the representation of variability of business process models, the selection of business variants in a given context remains a challenging issue. In this proposal, we advocate the use of Non-Functional Requirements (NFR) and context-awareness information to drive the con guration of process models at run-time. We propose a model-driven business process con- guration approach called Business process Variability Con guration with Contexts and NFRs (BVCCoN), approach that keeps the variability representation, con guration knowledge and contextual information separated from the business process models. We illustrate the BVCCoN model and process through examples. The evaluation of our proposal is based on a simulation assessment. / Submitted by João Arthur Martins (joao.arthur@ufpe.br) on 2015-03-12T18:46:21Z No. of bitstreams: 2 Tese Emanuel Santos.pdf: 4118681 bytes, checksum: f565640ea4362fd5c2f2c8f9197b9e47 (MD5) license_rdf: 1232 bytes, checksum: 66e71c371cc565284e70f40736c94386 (MD5) / Made available in DSpace on 2015-03-12T18:46:21Z (GMT). No. of bitstreams: 2 Tese Emanuel Santos.pdf: 4118681 bytes, checksum: f565640ea4362fd5c2f2c8f9197b9e47 (MD5) license_rdf: 1232 bytes, checksum: 66e71c371cc565284e70f40736c94386 (MD5) Previous issue date: 2013-05-10 / Modelos de processos de neg ocios s~ao uma importante fonte de informa c~ao para o desenvolvimento de sistemas de informa c~ao. No entanto, as mudan cas no ambiente podem afetar a forma como os processos de neg ocios s~ao realizados. A m de obter modelos que re etem as mudan cas e necess ario o alinhamento entre o modelo e a realidade. Processos de neg ocios bons precisam ser atualizados e automatizados para representar o ambiente organizacional. Assim, e de suma import^ancia representar adequadamente a variabilidade em Modelos de Processo de Neg ocio. Representar e con gurar a variabilidade em processos de neg ocio de uma organiza c~ao espec ca permite a execu c~ao adequada dos processos. Al em disso, o ambiente din^amico exige processos de con gura c~ao ex veis que possam atender os objetivos das partes interessadas. No entanto, selecionando uma con gura c~ao para o processo de neg ocio e uma atividade desa adora. Mesmo que as abordagens atuais permitam a representa c~ao da variabilidade dos modelos de processos de neg ocios, a sele c~ao de variantes de neg ocios em um determinado contexto continua a ser uma quest~ao a ser explorada. Nesta proposta, defendemos o uso de Requisitos N~ao Funcionais (RNF) e informa c~oes de contexto para conduzir a con gura c~ao de modelos de processos em tempo de execu c~ao. Propomos uma abordagem orientada a modelos para a con gura c~ao de processos de neg ocios chamada BVCCoN, a abordagem mant em a representa c~ao variabilidade, conhecimentos de con gura c~ao e informa c~ao contextual separados dos modelos de processos de neg ocios. A avalia c~ao da proposta baseia-se numa an alise de simula c~ao, assim como uma compara c~ao com algumas outras obras relevantes.

Submitted by Fabio Sobreira Campos da Costa (fabio.sobreira@ufpe.br) on 2016-04-05T15:42:49Z No. of bitstreams: 2 license_rdf: 1232 bytes, checksum: 66e71c371cc565284e70f40736c94386 (MD5) Dissertação - Jean Poul Varela.pdf: 3797900 bytes, checksum: fa011df68d9bf4b963c64b5a5b22c945 (MD5) / Made available in DSpace on 2016-04-05T15:42:49Z (GMT). No. of bitstreams: 2 license_rdf: 1232 bytes, checksum: 66e71c371cc565284e70f40736c94386 (MD5) Dissertação - Jean Poul Varela.pdf: 3797900 bytes, checksum: fa011df68d9bf4b963c64b5a5b22c945 (MD5) Previous issue date: 2015-02-23 / FACEPE / O processo GS2SPL (Goals and Scenarios to Software Product Lines) visa obter, de maneira sistemática, o modelo de features e a especificação de cenários de caso de uso, a partir de modelos de objetivos de uma linha de produto de software (LPS). Além disso, esse processo permite realizar a configuração desses artefatos de requisitos para um produto da LPS, com base no atendimento de requisitos nãofuncionais (RNFs). Contudo, essa configuração é realizada sem considerar o estado do contexto do ambiente no qual a aplicação gerada será implantada. Isso é uma limitação, pois uma configuração pode não atender as necessidades do stakeholders. Por outro lado, o processo E-SPL (Early Software Product Line) permite configurar o modelo de objetivos de um produto visando maximizar o atendimento de RNFs e levando em consideração o estado do contexto. Para superar a limitação do processo GS2SPL, o presente trabalho propõe uma extensão do processo GS2SPL para incorporar a atividade de configuração do E-SPL. O novo processo é chamado de GSC2SPL (Goals, Scenarios and Contexts to Software Product Lines), o qual possibilita a obtenção do modelo de features e cenários de caso de uso, a partir de modelos de objetivos contextuais. O processo também permite realizar a configuração desses artefatos de requisitos com base nas informações sobre o contexto e visando aumentar o atendimento dos requisitos nãofuncionais. O processo é apoiado pela ferramenta GCL-Tool (Goal and Context for Product Line - Tool). O processo foi aplicado à especificação de duas LPS: o Media@ e o Smart Home. / GS2SPL (Goals and Scenarios to Software Product Lines) is a process aimed at systematically obtaining a feature model and the specification of use case scenarios from goal models of a Software Product Line (SPL). Moreover, this process allows configuring specific applications of an SPL based on the fulfillment of non-functional requirements (NFRs). However, this configuration is performed without considering the context state in which the system will be deployed. This is a limitation because a configuration may not meet the needs of stakeholders. On the other hand, E-SPL (Early Software Product Line) is a process that allows configuring a product aimed maximizing the fulfillment of NFRs and taking into account the context state. To overcome the limitation of the GS2SPL process, in this work we propose extension of the GS2SPL process, to incorporate the configuration activity of the E-SPL. The new process is called GSC2SPL (Goals, Scenarios and Contexts to Software Product Lines), which allows obtaining a feature model and use case scenarios from contextual goal models. The process will also allow the configuration of such requirements artifacts based on the information about the context and aiming to maximize the fulfillment of non-functional requirements. The process is supported by the GCL-Tool (Goal and Context for Product Line - Tool). The process was applied to the specification of two LPS: Media@ and the Smart Home.

Abstract At present, collaborative strategies are an important part of developing the capabilities to be able to compete in the 21st Century since knowledge or innovations cannot develop entirely within a single firm. Collaboration provides invaluable resources that a firm cannot create through knowledge transfer mechanisms. The purpose of this doctoral dissertation is to enhance understanding of knowledge transfer in requirements engineering in the context of collaborative product development. The research is qualitative by nature and utilises the case study methodology. Data collection was conducted through interviews and surveys with informants in high-tech enterprises. The results indicate that collaboration in product development is very important and acts as a means of obtaining external resources, especially knowledge. However, collaboration is not an easy practice; it involves many challenges. In order to improve the practice of collaboration, it is necessary to manage and leverage the transfer of knowledge. According to the results, in order to increase the effectiveness of knowledge transfer over enterprise interfaces, each knowledge type needs to be transferred through the suitable transfer channel at the right time. The results also indicate that the individual relationships among buyers and suppliers are an essential element for long-term collaboration and common platforms or tools need to be developed to support collaborative product development over enterprise interfaces. / Tiivistelmä Kiristyvän kilpailun tilanteessa yritykset etsivät keinoja tehostaakseen toimintaansa. Yksi keino tähän on yhteistyökumppanina toimivien yritysten hyödyntäminen tuotekehityksessä. Yhteistyökumppanien hyödyntämisellä yritykset pyrkivät muun muassa tukemaan innovatiivisuutta ja täydentämään tuotekehityksessä tarvittavia kyvykkyyksiä. Tähän pyritään hankkimalla lisää resursseja, erityisesti tietämystä ja osaamista, jota yrityksellä ei itsellään ole tai joka on ulkoistettu aiemmin. Tässä väitöskirjassa perehdytään yritysyhteistyötä hyödyntävään tuotekehitystoimintaan ja tutkimuksen tavoitteena on lisätä ymmärrystä osaamisen siirrosta erityisesti vaatimusten hallinnan prosessissa. Tämä väitöskirjatyö on laadullinen tapaustutkimus. Tutkimuksen empiirinen aineisto on hankittu haastatteluilla ja kyselyillä korkeanteknologian yrityksistä. Tutkimustulosten mukaan yritysten välinen yhteistyö tuotekehityksessä on merkittävässä roolissa moderneissa yrityksissä. Tällöin voidaan puhua ulkopuolisten resurssien, erityisesti ulkoisen osaamisen hyödyntämisestä tuotekehityksessä. Tulosten mukaan on kuitenkin huomioitava, että yritysyhteistyö on varsin monimutkaista ja haastavaa toteuttaa. Yritysten tulee paremmin johtaa osaamisen siirtoa yhteistyökumppaneiden välillä ja panostaa osaamisen siirtoon liittyviin toimintatapoihin ja työkaluihin. Yritysten välisen osaamisen siirron tehokkuuden lisäämiseksi tulee huomioida, että erityyppinen osaaminen tulee siirtää sille ominaisen kanavan kautta juuri oikeaan aikaan. Tulosten mukaan yrityksissä toimivien henkilöiden väliset suhteet ovat keskeisessä roolissa pitkän aikavälin yritysyhteistyölle. Tukeakseen paremmin yritysyhteistyötä tuotekehityksessä yritysten tulisi kehittää yhteisiä alustoja tai työkaluja osaamisen siirtoon.

I det här arbetet har vi undersökt hur man kan generalisera en samling krav för att därigenom generalisera det system som kraven ligger till grund för. På det sättet kan man göra ett system tillämpbart över fler användningsområden än det ursprungligen var avsett för. Vi har utvecklat två artefakter i form av en stegmodell och en prototyp för att uppnå detta.

La phase conceptuelle, basée sur des informations imprécises et incomplètes, est à la base de la satisfaction des clients par le futur système. La programmation architecturale se concentre sur une des premières étapes de cette phase dans le domaine de la construction : la définition des besoins d'un bâtiment. Les pratiques et recherches actuelles en Architecture-Ingénierie-Construction ont tendance à être basées sur l'expérience des programmistes et architectes. Elles sont rapidement orientées vers la production de solutions architecturales et avec une formalisation tardive des besoins métiers en exigences bâtiment. La définition des exigences est bien plus développée dans les autres domaines d'ingénierie (i.e. génie mécanique, industriel et logiciel) au sein de théories, modèles, techniques et outils. Ces travaux de recherche visent à proposer un raisonnement de programmation architecturale basé sur ces connaissances en matière d'ingénierie des exigences dans ces autres domaines. La méthodologie suivie pour développer ce raisonnement s'appuie sur une démarche transdisciplinaire basée sur une combinaison de méthodologies issues des Sciences de la Conception. Outre l'identification de langages de modélisation couvrant différent points de vues associées à la programmation architecturale, un manque est identifié en ce qui concerne les concepts définissant l'objet d'étude : la transition entre les concepts d'activité et d'espace. Le concept de ‘‘méta-espace'' est proposé pour combler ce manque ainsi qu'un langage de modélisation permettant l'exploitation des relations entre ces concept. Une formalisation très en amont de la transition des besoins métiers des clients vers les exigences bâtiment est proposée via une démarche conceptuelle résultant de l'ajout du concept de ‘‘méta-espace''. Cette démarche est présentée étape par étape en s'appuyant sur les divers cas d'études traités au cours de la thèse. / The conceptual phase is based on very fuzzy and incomplete information about clients' needs. It constitutes the core of clients' satisfaction about the future system. Architectural programming, or briefing process, focuses on the early stages of the conceptual phase of construction projects, i.e. the requirements definition. Current practices and research in Architecture-Engineering-Construction tend to be experience-based, solution-oriented, and with a late formalisation of business needs into building requirements. The requirements definition is far more supported by theories, models, tools, and techniques in other engineering disciplines (i.e. Mechanical, Industrial, and Software Engineering). This research aims to propose an architectural programming reasoning based on existing requirements engineering knowledge from these other engineering disciplines. The methodology followed to develop this reasoning is a transdisciplinary approach based on a combination of Design Research Methodology, and Design Science. Besides the identification of modelling languages covering different viewpoints associated with the briefing process, a gap is identified regarding modelling constructs associated with a “meta-space” design artefact. This design artefact and its associated modelling language (i.e. the meta-space diagram) support the formalisation of the transition from activities to space. The resulting conceptual framework proposes a step by step early formalisation of the transition from clients' business needs to building requirements. All along the thesis, different case studies are used to illustrate the proposals.

The world business has been changed tremendously during last thirteen year. This is all due to the revolutionary dot com digital business. The dot com digital business has given big swing to world business. No one now can deny the power and capabilities of the internet technology. However, from 2001 onwards the growth of internet business has declined. Our paper investigates the major reasons behinds this. The focus of our paper is south Asian market because we believe this region has more potential of growth within internet business as compare to any other part of the world. The focal point of our paper is to identify obstacles which are hindering the growth of service based internet commerce in south Asian market. We have also come up with the possible solutions which when applied can create a room for big growth of internet business.

IBM Rational Requirements Composer (RRC) is a tool for software requirements engineering that supports requirements development and requirements management in the proces of software development. IBM RRC is a part of Collaborative Lifecycle Management (CLM) using the Jazz platform. In cooperation with other tools of this solution, especially with IBM Rational Team Concert (RTC), it advances the management of projects with large scope and extended teams. These tools have been developed for agile methodologies. This diploma uses the methodology for small software projects called MMSP for the analysis of IBM RRC's features. The main objective of this diploma thesis is the analysis of IBM RRC's features usable for software requirements engineering and demonstrates how to elevate the software requirements activities for school projects using the methodology MMSP. This diploma also pursues the objective of finding best practices and MMSP tasks to improve the requirements engineering proces. These objectives were achieved by deep analysis of various sources about software tools for requirements management, methodologies of IS/ICT development and information system development projects at the University of Economics in Prague and on using the IBM RRC. The key benefit of this diploma thesis is in raising the number of software tools which can be used for school projects of IS/ICT development using the MMSP methodology.

Requirements Engineering and Software Quality Management is nowadays considered to be one of the important parts of the software development process. This thesis deals with connecting the theoretical concept of requirements engineering and usage of functions offered by Enterprise Architect tool, which should support the requirements engineering and software quality management processes. The main goal is to propose procedures of Enterprise Architect usage during the project in such a way, which will help to raise quality of the final product. The purpose is to offer a systematic and conscious way of implementation Enterprise Architect elements into software development processes, because this tool is able to support the whole cycle of the product. The methodology was designed as a result of theoretical concept, existing requirements engineering approaches and my own experience acquired during working on projects as a business and test analyst. The contribution of the designed methodology is in bringing recommendations, practices and procedures saying how to use Enterprise Architect during the software development process in order to gain the highest possible software quality. The thesis is structured in four sections describing the appropriate theory, analyzed requirement engineering approaches, critical mistakes during this process and the methodology design.