Submitted by Nadir Basilio (nadirsb@uninove.br) on 2016-07-01T14:26:09Z No. of bitstreams: 1 Paulo Henrique Ribeiro De Oliveira.pdf: 2464979 bytes, checksum: 93b7213ac2b763d9ce75892da0e93cda (MD5) / Made available in DSpace on 2016-07-01T14:26:09Z (GMT). No. of bitstreams: 1 Paulo Henrique Ribeiro De Oliveira.pdf: 2464979 bytes, checksum: 93b7213ac2b763d9ce75892da0e93cda (MD5) Previous issue date: 2016-02-29 / The effort spent in maintaining systems regarded as legacies is relatively higher than that of new projects development effort. Such systems should be kept in place because, in most cases, are difficult to replace, given the complexity of changing the interaction and the impact on the functioning of processes, ie, the system can not stop. Thus, maintenance or modifications represent a sign of success for a Legacy System because it means that it is still useful and worth investing resources to keep it updated and running. However, if changes are carried out due to an emergency on business dynamics, and proper documentation is not completed, problems involving control and management of future maintenance might arise. In this context, it is the Requirements Engineering´s responsibility, as a sub-area of Software Engineering, to improve processes by proposing methods, tools and techniques that promote the development of the Requirement´s documentation, so that the requirements are in accordance with the satisfaction of stakeholders, meeting the business attributes in question. The objective of this work was to apply the Requirements Engineering in Legacy Systems of Management and Costing Methods of Sales Proposals in the stamping industry. Through literature review, document analysis and action research, the study was divided into four phases considering the development of the Sales Proposal Management and Costing Method System and three maintenance stages performed with the application of Requirements Engineering. In the first phase, a group of artifacts was generated expressing all system features. In the second phase, a progressive maintenance incorporated new features based in the system´s backlog with requirements collected in the first phase. The third phase included a new stamping business area that was not present in the initial development. Lastly, the fourth phase included new maintenance adjustments that answered to the needs of the stamping business system. The results of the study phases proved that the processes described in the Requirements Engineering (RE) were present in the information gathering actions, analysis, documentation and verification and validation of requirements, bringing academic and technical knowledge on issues related to legacy systems, ER and Software Engineering. As a result, it was concluded that the Requirements Engineering can be applied to Legacy Systems of Management and Costing Methods of Sales Proposals in stamping company in the industry. / O esforço despendido para a manutenção de sistemas considerados como legado é relativamente maior que o esforço de desenvolvimento de novos projetos. Tais sistemas devem ser mantidos em funcionamento pois, em sua maioria, são de difícil substituição, dada a complexidade de convívio da mudança e o impacto no funcionamento dos processos, ou seja, o sistema não pode parar. Dessa forma, manutenções ou modificações representam um sinal de sucesso para um sistema legado, pois significam que ele ainda é útil e que vale a pena investir recursos para mantê-lo atualizado e em funcionamento. No entanto, se modificações são realizadas emergencialmente devido a dinâmica do negócio, e a devida documentação não é realizada, tem-se instaurado o caos para o controle e gerência de futuras manutenções. Neste contexto, cabe à Engenharia de Requisitos, como sub-área da Engenharia de Software, aperfeiçoar os processos para o gerenciamento do ciclo de vida dos requisitos propondo métodos, ferramentas e técnicas que promovam o desenvolvimento do documento de requisitos, para que os requisitos estejam em conformidade com a satisfação dos stakeholders, atendendo as características do negócio em questão. Assim, o objetivo deste trabalho foi aplicar a Engenharia de Requisitos em Sistema Legado de Gestão e Custeio de Propostas Comerciais em empresa do setor de estamparia. Por meio de levantamento bibliográfico, análise documental e pesquisa-ação, o estudo foi dividido em quatro fases considerando o desenvolvimento do Sistema de Gestão e Custeio de Propostas Comerciais e três manutenções realizadas com a aplicação da Engenharia de Requisitos. Na primeira fase um conjunto de artefatos foi gerado expressando todas as funcionalidades do sistema. Na segunda fase uma manutenção evolutiva incorporou novas funcionalidades no sistema baseada em requisitos de backlog coletados na primeira fase. A terceira fase incluiu uma nova área de negócios da estamparia que não esteve presente no desenvolvimento inicial e a quarta fase contemplou novas manutenções ajustando o sistema as necessidades de negócio da estamparia. Os resultados das fases do estudo possibilitaram identificar que os processos descritos na Engenharia de Requisitos (ER) se fizeram presentes nas ações de levantamento, análise, documentação e verificação e validação de requisitos trazendo conhecimento acadêmico e técnico nos temas relacionados a sistemas legados, ER e Engenharia de Software. Concluiu-se, então, que a Engenharia de Requisitos pode ser aplicada em Sistema Legado de Gestão e Custeio de Propostas Comerciais em empresa do setor de estamparia.

Capturing client’s needs and expectations for a product or service is an important problem in software development. Software requirements are normally captured in natural language and mostly they are unstructured which makes it difficult to automate the process of going from software requirements to the executable code. A big hurdle in this process is the lack of consistency and standardization in software requirements representation. Thus, the aim of the thesis is to present a method for transforming natural language requirement text into ontology. It is easy to store and retrieve information from ontology as it is a semantic model, and it is also easy to infer new knowledge from it. As it is clear from the aim of this work, the main component of our research was software requirements, so there was a need to investigate and decide the types of requirements to define the scope of this research. We selected INCOSE guidelines as a benchmark to scrutinize the properties which we desired in the Natural Language Requirements. These natural language requirements were used in the form of user stories as the input of the transformation process. We selected a combination of two methods for our research i.e. Literature Review and Design Science Research. The reason for selecting these methods was to obtain a good grip on existing work going on in this field and then to combine the knowledge to propose new rules for the requirements to ontology transformation. We studied different domains during literature review such as Requirements Engineering, Ontologies, Natural Language Processing, and Information Extraction. The gathered knowledge was then used to propose the rules and the flow of their implementation. This proposed system was named as “Reqtology”. Reqtology defines the process, from taking the requirements in form of user stories, to extracting the useful information based on the rules and then classifying that information so that it can be used to form ontologies. The workflow consists of a 6-step process which starts from input text in form of user stories and at the end provides us entities which can be used for ontologies formation.

För att bedriva sin verksamhet har företag vanligtvis ett affärssystem till hjälp som integrerar företagets IT och stödjer organisationens centrala processer. Vidareutvecklingen av affärssystem kan se olika ut men handlar till stor del om att utveckla systemet i en riktning som följer användarnas krav och önskemål.  Vi har i denna kvalitativa studie undersökt hur en affärssystemsleverantör arbetar med kravhantering för vidareutveckling av affärssystem där vi ämnar att ta reda på vilka utmaningar som kravhantering kan medföra affärssystemsleverantörer. För att kunna svara på detta har vi tagit del av tidigare litteratur samt genomfört fyra kvalitativa intervjuer med olika roller inom kravhanteringsarbetet hos affärssystemsleverantören Infor. Kravhantering kan beskrivas på olika sätt men syftar till att identifiera krav för att hantera dessa tills en lösning är färdig att implementeras i affärssystemet. Vår slutsats visar att kravhantering utgörs av både affärssystemsleverantörers interna krav på affärssystemet samt externa krav som formuleras av olika intressenter. Vidare visar studien kravhantering tillsammans med det studerade företagets strategi är en drivande faktor för vidareutveckling av affärssystem. Vår slutsats visar även att både kommunikationen med kunder samt att affärssystemsleverantörers interna kommunikation tillsammans med prioritering av krav är utmanande. Det studerade företagets branschanpassade affärssystem medför även att det är en utmaning att förhålla sig till den funktionalitet som ska fungera för alla kunder oavsett bransch och samtidigt erbjuda kunder inom specifika branscher en produkt som täcker just deras centrala processer. / To run their business, companies usually have a helpful Enterprise Resource Planning system that integrates the company's IT and supports the organization's central processes. The further development of ERP systems can look different, but is largely about developing the system in a direction that follows the users requirements and wishes. In this qualitative study, we have investigated how an ERP system supplier works with requirements engineering for the further development of  ERP systems, where we intend to find out what challenges that requirements engineering can entail for ERP system suppliers. To be able to answer this, we have read previous literature and conducted four qualitative interviews with different roles in the requirement engineering process at the ERP system supplier Infor. Requirements engineering can be described in different ways but aims to identify requirements for handling these until a solution is ready to be implemented in the ERP system. Our conclusion shows that requirements engineering consists of both the ERP system suppliers internal requirements for the ERP system as well as external requirements formulated by various stakeholders. Furthermore, the study shows requirements engineering together with the studied company's strategy is a driving factor for further development of ERP systems. Our conclusion also shows that both communication with customers and that ERP system suppliers internal communication together with the prioritization of requirements is challenging. The studied company's industry-specific ERP system also means that it is a challenge to relate to the functionality that should work for all customers regardless of industry and at the same time offer customers in specific industries a product that covers their core processes.

Component failures can result in catastrophic behaviors in safety critical embedded systems, sometimes resulting in loss of life. Component failures can be treated as off nominal behaviors (ONBs) with respect to the components and sub systems involved in an embedded system. A lot of research is being carried out to tackle the problem of ONBs. These approaches are mainly focused on the states (i.e., desired and undesired states of a system at a given point of time to detect ONBs). In this paper, an approach is discussed to detect component failures and critical components of an embedded system. The approach is based on fault tree analysis (FTA), applied to the requirements specification of embedded systems at design time to find out the relationship between individual component failures and overall system failure. FTA helps in determining both qualitative and quantitative relationship between component failures and system failure. Analyzing the system at design time helps in detecting component failures and critical components and helps in devising strategies to mitigate component failures at design time and improve overall safety and reliability of a system.

Le développement des systèmes d’information numériques et plus particulièrement les systèmes interactifs d’aide à la décision (SIAD) orientés données (Application Analytics) rencontre des échecs divers.La plupart des études montrent que ces échecs de projets de développement de SIAD relève de la phase d’analyse des besoins et des exigences. Les exigences qu'un système doit satisfaire sont insuffisamment définies à partir de besoins réels des utilisateurs finaux.D’un point de vue théorique, l’analyse de l’état de l’art, mais également du contexte industriel particulier, conduit donc à porter une attention particulière à cette phase et à élaborer une approche collaborative d’analyse des besoins et des exigences dirigée par les problèmes.Un système d’aide à la décision est avant tout un système d’aide à la résolution de problèmes et le développement de ce type d’artefact ne peut donc se faire sans avoir convenablement identifié en amont les problèmes de décision auxquels font face les utilisateurs décideurs, afin d’en déduire les exigences et le type de SIAD.Cette approche, par un renversement de la primauté implicite de la solution technique par rapport à la typologie des problèmes de décision, a été explicitée et mise en œuvre pour le développement d’une Application Analytics qui a permis d’atteindre l’objectif attendu : un système efficace et qui satisfasse d’un triple point de vue technique, fonctionnel et ergonomique, ses différents utilisateurs finaux. / The design of digital information systems, especially interactive Data-Driven Decision Support System (DSS) (Analytics Application) often misses its target.Most of studies have proven that the sources of most DSS design failures are rooted in the analysis step of the users’ needs and requirements a system has to meet and comply with. From a theoretical point of view, the analysis of the state of art combined with the analysis of specific industrial contexts, leads to focus on this critical step, and consequently to develop a collaborative problem-driven requirements engineering approach.A DSS, first and foremost, is a problem solving support system. It implies that developing such an artefact cannot be performed without an adequate upstream identification of end-users’ decision problems, prior to defining the decision makers’ requirements and the appropriate type of DSS.Characterized by the reversal of the implicit primacy of technical solution versus the typology of decision problems, this approach has been elaborated and implemented to design an Analytics Application. As a result, it allowed to reach the expected objective: An effective system that meets the different end-users’ expectations from a technical, functional and ergonomic standpoint.

No description available.

Kravprioritering är ett av de viktigaste och mest inflytelserika stegen vid tillverkning av en mjukvaruprodukt. Processen är iterativ; den sker under hela produktens agila mjukvaruutvecklingsprocess. Genom kravprioritering beslutas det om vilka krav som ska utvecklas, i vilken ordning och varför.  Målet med denna studie är att undersöka hur mjukvaruutvecklande företag gör för att kravprioritera, samt identifiera vilka prioriteringsmetoder de eventuellt använder sig av. Studiens syfte är att få en förståelse för varför en väl avvägd prioritering är viktig, vilka särskilda prioriteringsfaktorer som ger värde till en produkt och att se hur dessa faktorer är relaterade till resultatet. Syftet är även att undersöka vilka svårigheter som finns i en prioriteringsprocess, samt att skapa en översikt över några av de mest vedertagna prioriteringsmetoderna inom agil mjukvaruutveckling.  Studien utförs i samarbete med mjukvaruföretaget Monitor ERP för att analysera företagets prioriteringsprocesser som används för att utveckla deras affärssystem Monitor. Metoden som används är en kvalitativ undersökning som består av observationer av möten kring prioriteringsarbete och semi-strukturerade intervjuer. Bearbetning av insamlat material skedde genom att organisera, analysera och sammanställa resultat enligt begrepp och kategorier som framkom utifrån litteraturstudien. Resultatet redovisar arbetsprocesser, gemensamma mål, prioriteringsaspekter och utmaningar i prioriteringsarbetet hos Monitor ERP. En väl avvägd prioritering visade sig vara viktigt för att kunna leverera rätt funktionalitet i tid, för att kunna ge trovärdiga estimeringar om utvecklingen och det i sin tur leder till att kunder får förtroende för både produkten och företaget. En rad olika prioriteringsfaktorer som ger värde till programvaran Monitor identifierades, varav många bidrar till att öka kundnöjdheten och kvaliteten på produkten. Monitor ERP använder inte några särskilda prioriteringsmetoder, utan utvecklingsfilosofin Minimum Viable Product används som grund till deras prioriteringsval. Under prioriteringsarbetet upplevdes utmaningar såsom begränsade resurser, oförutsägbara uppgifter, svårigheter med tidsestimering och en utmaning i balansen mellan kundnytta och kundfokus. / Prioritizing requirements is one of the most important and influential steps in the creation of a software product. The process is iterative; it takes place during the entire agile software development. Through prioritizing requirements, it is decided which requirements are to be developed, in which order, and why.  The aim of this study is to investigate how companies that design software prioritize requirements and to identify which prioritization methods they might use during this process. The purpose of this study is to gain an understanding for why a well-balanced prioritization is important, which specific prioritization factors give value to a product, as well as identifying how these factors are related to the result. The purpose is also to investigate the difficulties that exist in a prioritization process, and to create an overview of some of the most used prioritization methods in agile software development.  This study is conducted in collaboration with the software company Monitor ERP in order to analyze the company's prioritization processes used to develop their business management system Monitor. The method used is a qualitative study that consists of observations of meetings about prioritization processes, and semi-structured interviews. Processing of collected material was done by organizing, analyzing, and compiling results according to concepts and categories that emerged from the literature study. The results documents work processes, common goals, prioritization aspects and challenges in the requirements prioritization at Monitor ERP.  A well-balanced prioritization proved to be important to be able to deliver the right functionality on time and to be able to provide dependable estimates of development, which in turn leads to customers gaining confidence in both the product and the company. A number of prioritization factors that give value to the Monitor software were identified, many of which contribute to increasing customer satisfaction and product quality. Monitor ERP does not use any specific prioritization methods, but the development philosophy Minimum Viable Product is used as a basis for their prioritization choices. During the prioritization process, challenges such as limited resources, unpredictable tasks, difficulties with time estimation, and a challenge in balancing customer value and customer focus were experienced.

Low response time is an important factor for any interactive system. However, web-based applications suffer sometimes from bad response times. This fact is not always important but for services depending on a  high degree of interactivity it can be severe. This thesis attempts to give an answer to the question whichi s the requirements engineering for best response time on a highly interactive Web-based application? The research approach is deductive based on a single-case study and using qualitative method. The case system is a web-based system that supports an experimental technique called Wizard-of-Oz. To tackle the research question an extensive review of literature on requirements engineering was made, and, for the case study itself, system requirements documents and interviews were included. The results include information about the specific requirements engineering process for the case system, response time, and quality attributes.The conclusion indicates the importance of response time requirements, hardware and software requirements, testing, but also a demonstration phase for desired interactive behaviour including response time. The latter is not previously identified as a major step in the general literature on requirements engineering but should definitively be noted by researchers and practitioner alike.

Der betriebliche Einsatz von Smart Glasses zur Unterstützung von manuellen Dienstleistungsprozessen bietet viele Vorteile, die mit anderen Technologien nicht erreicht werden können. Insbesondere im Bereich der Logistik kann von der Informationsversorgung bei gleichzeitiger Mobilität Gebrauch gemacht werden. Um dieses Potenzial auszunutzen, bedarf es allerdings Softwarelösungen, die auf die jeweiligen Anforderungen zugeschnitten sind. In dieser Forschungsarbeit wird daher untersucht, wie Smart-Glasses-basierte Informationssysteme zur Unterstützung der Logistik zu gestalten und zu implementieren sind. Die Forschungsarbeit folgt dabei zwei Zielen: (A) Die Unterstützung von Logistikprozessen durch Smart-Glasses-basierte Informationssysteme wird im Hinblick auf Anforderungen, Herausforderungen und Gestaltungsprinzipien untersucht, und (B) wird der Entwicklungsprozess zur Gestaltung und Implementierung von derartigen Informationssystemen im Rahmen eines Forschungsprojekts konzipiert und evaluiert. Das Vorgehen wird durch methodische Betrachtungen von Gestaltungsanforderungen und -prinzipien geleitet und entspricht so dem gestaltungsorientierten Forschungsansatz der Wirtschaftsinformatik. Die genauere Beantwortung der gestellten Forschungsfrage erfolgt in drei Schritten: (1) Methoden zur Initiierung von agilen Softwareprojekten und der Integration von Softwareentwicklung und -betrieb werden basierend auf der Wissensbasis agiler Methoden, Praktiken und Ansätze abgeleitet, (2) Grundlagen zur thematischen Fokussierung auf die Technologie Smart Glasses und die Anwendungsdomäne der Logistik werden durch multimethodische Studien geschaffen, und (3) werden entsprechende Systeme zur Mitarbeiterunterstützung instanziiert, evaluiert und die Forschungsergebnisse in ein Vorgehensframework zur Durchführung von Implementierungsprojekten überführt. Die vorliegende Dissertation trägt somit zur Wissensbasis der gestaltungsorientierten Wirtschaftsinformatik durch die erreichten Erkenntnisse zur Initiierung und Durchführung von Softwareentwicklungsprojekten zur Unterstützung von betrieblichen Prozessen durch Smart-Glasses-basierte Informationssysteme bei. Darüber hinaus bietet die Arbeit durch die bewusst praxisnahe Orientierung mit dem generierten Gestaltungswissen einen Mehrwert für Praktiker aus den betrachteten Bereichen, insbesondere für Stakeholder für die Einführung mobiler Informationssysteme in betrieblichen Umfeldern.

L’objectif principal de l’ingénierie des systèmes est la création d’un ensemblede produits et des services de haute qualité qui permettent l’accomplissement de tâchespour répondre aux besoins des clients. Un projet typique d’ingénierie des systèmes peutêtre divisé en trois phases : la définition, le développement et le déploiement. La phasede définition comprend les activités de capture des exigences et de leur raffinement. Àla fin de la phase de définition du système, nous avons toutes les exigences fonctionnelleset non-fonctionnelles du système. L’un des résultats de la phase de développement est lemodèle de travail initiale du système. La phase de déploiement se compose des activitésliées à (1) l’évaluation opérationnelle du système, à (2) l’utilisation du système et à (3) sonentretien. Dans un cycle de vie du projet, il y a de nombreuses questions qui doivent êtretraitées au cours des différentes phases pour finalement livrer un produit.Nous avons proposé une solution aux problèmes liés à l’ingénierie des exigences et auxtechniques de la détection, de la gestion et de la résolution des conflits entre les partiesprenantes. Cette thèse est basée sur les dernières avancées dans les pratiques industrielleset de recherche dans le domaine de l’ingénierie de conception du système.L’objectif de ce travail de thèse est de proposer une méthodologie de conception novatriceet globale en tenant compte de l’environnement multidisciplinaire et de multiplesintervenants. Nous avons proposé un langage de modélisation des exigences basé sur lestechniques GORE. Nous avons proposé quelques outils pour réduire l’ambiguïté des exigencestels l’utilisation de phrases négatives et de tests á l’aide de négation lorsqu’il s’agitde traiter certaines exigences difficiles à comprendre avec les techniques classiques. Nousavons également proposé des techniques de gestion des exigences pour mieux assurer leurtraçabilité. Concernant la résolution des conflits, nous avons proposé des techniques depondération des critères au cours des différentes étapes du cycle de vie. En utilisant lamême technique de pondération de critères, une méthode de décision multicritères et multiparticipants est proposée pour divers problèmes de décision survenant pendant le cycle devie du projet d’ingénierie systèmes.Enfin, une approche globale de l’ingénierie des systèmes est proposée pour intégrertoutes les contributions faites précédemment et est illustrée sur une étude de cas concernantun projet réel avec la présentation dŠun outil SysEngLab que nous avons développé pourmettre en oeuvre la majorité des méthodes et des techniques proposées au cours de thèse / The primary goal of the systems engineering is the creation of a setof high quality products and services that enable the accomplishment of desiredtasks and needs of the clients or user groups. A typical systems engineering projectcan be divided in to three phases: definition, development, and deployment. Thedefinition phase involves the activities of requirement elicitation and refinement.By the end of system definition phase, we have all the system functional and nonfunctionalrequirements. One of the results of development phase is initial workingmodel of the system. The deployment phase consists of activities of operationalimplementation, operational testing and evaluation, and operational functioning andmaintenance. In a project life cycle there are numerous issues to be sorted out duringthe various phases to finally deliver a successful product. We proposed solution tothe problems of requirements engineering & management, design conflict detection,and stakeholders conflict resolution. This thesis is based on the recent advances inindustrial practices and research in the field of system design engineering.The objective of this thesis work is to propose an innovative and holistic conceptionmethodology taking into account the multidisciplinary environment and multiplestakeholders. We have proposed a requirements modeling language based on theGORE techniques. We have proposed a few of tools for reducing the ambiguity ofrequirements such as: using negation and test cases using negation for contractingdifficult requirements. Requirement management techniques are proposed to providebetter requirements traceability and aid for other systems engineering activities.Few guidelines have been designed to guide the design of traceability policies. Criteriaweighting technique has been designed to better carry out the conflict resolutions,during the various life cycle stages. Using the same criteria weighting technique aflexible multi criteria multi participant decision methodology is proposed for variousdecision problems arising during the life cycle of systems engineering project.Finally, a comprehensive prescriptive systems engineering approach is proposedusing all the previously made contributions and an illustrative case study of a realongoing project is presented developed using the supporting tool SysEngLab, whichimplements majority of the methods and techniques proposed during thesis