Made available in DSpace on 2016-08-17T14:52:42Z (GMT). No. of bitstreams: 1 Marcia Cristina Ferro Carvalho.pdf: 2460660 bytes, checksum: c476e586b0a742bc6474a4ab2ae0396b (MD5) Previous issue date: 2002-03-27 / This work proposes an integration of the approach CREWS L ecritoire based on scenarios with the approach of use cases described by Regnell & al and the Method GBRAM. In this case, the work of Regnell is extended with the notion of Requirement Chunk (RC), strategies for discovering objectives through the relationships AND, OR, and refinement between RCs, as well as extending the model with a physical level where the internal actions of the system are described. On the other side, the approach CREWS L ecritoire is extended with coupling of objective and use case where the scenarios are obtained by applying a strategy of refining use cases, and also with an integration of normal and exceptional scenarios in one synthetic model of use with one unique vision for each actor. The Method GBRAM is extended with the alternative contract dependency, composicional contract dependency, inclusive and exclusive contract dependency, as well it introduzed the use case technique, described by Regnell et al and extended with the notion of scenarios for caracterize exceptionals, variationals and normal situations. With the integration of threes methods, the new method which benefit from the advantages of the approaches of CREWS-L ecritoire, use cases.and goals. The new method proposes a coupling between objective and Use Cases in a top-down decomposition of different levels of abstraction. The method combines the two concepts into a Requirement Chunk (RC). An RC is a pair of <objective, Use Case> related with AND, OR and refinement. These three types of relations between RCs lead to a hierarchic organisation of RCs in three levels of abstractions: functional, behaviour, and physical. / This work proposes an integration of the approach CREWS L ecritoire based on scenarios with the approach of use cases described by Regnell & al and the Method GBRAM. In this case, the work of Regnell is extended with the notion of Requirement Chunk (RC), strategies for discovering objectives through the relationships AND, OR, and refinement between RCs, as well as extending the model with a physical level where the internal actions of the system are described. On the other side, the approach CREWS L ecritoire is extended with coupling of objective and use case where the scenarios are obtained by applying a strategy of refining use cases, and also with an integration of normal and exceptional scenarios in one synthetic model of use with one unique vision for each actor. The Method GBRAM is extended with the alternative contract dependency, composicional contract dependency, inclusive and exclusive contract dependency, as well it introduzed the use case technique, described by Regnell et al and extended with the notion of scenarios for caracterize exceptionals, variationals and normal situations. With the integration of threes methods, the new method which benefit from the advantages of the approaches of CREWS-L ecritoire, use cases.and goals. The new method proposes a coupling between objective and Use Cases in a top-down decomposition of different levels of abstraction. The method combines the two concepts into a Requirement Chunk (RC). An RC is a pair of <objective, Use Case> related with AND, OR and refinement. These three types of relations between RCs lead to a hierarchic organisation of RCs in three levels of abstractions: functional, behaviour, and physical.

Vehicle-to-Everything (V2X) is referred to as the technology enabling communication and data exchange between vehicles and is considered a significant milestone within automotive. By enabling inter-vehicle communication, the vehicles will be more aware of their surroundings—including things outside their current line-of-sight (LOS). The vehicles utilizing this technology are in Europe referred to as Cooperative Intelligent Transport Systems (C-ITS). A single vehicle is referred to as an ITS station (ITS-S). These are the terms presented in the European V2X standard called the ETSI ITS. This thesis considered the ETSI ITS standard since it is one of the most mature within the V2X standardization flora. This thesis investigated some significant V2X use cases and conducted a risk assessment on a selection of these use cases. These significant use cases were discovered by performing semi-structured interviews with five candidates within the field. The conducted risk assessment was performed according to a method called Threat, Vulnerability, and Risk Assessment (TVRA), which ETSI has developed. The results of this thesis work became a set of safety-functional use cases that were considered significant. The cybersecurity risk varied and spanned from critical to minor risk concerning the attacks taken into account. Since security and hardening are critical aspects of automotive connectivity, this thesis provides some future research directions at the end of this thesis. One of these topics is, for example, the privacy perspective on V2X, which was not considered in this thesis.

The goal of this research is to develop a new paradigm integrating the practices of business process modeling and use case modeling. These two modeling approaches describe the behavior of organizations and systems, and their interactions, but rest on different paradigms and serve different needs. The base of knowledge and information required for each approach is largely common, however, so an integrated approach has advantages in efficiency, consistency and completeness of the overall behavioral model. Both modeling methods are familiar and widely used. Business process modeling is often employed as a precursor to the development of a system to be used in a business organization. Business process modeling teams and stakeholders may spend months or years developing detailed business process models, expecting that these models will provide a useful base of information for system designers. Unfortunately, as the business process model is analyzed by the system designers, it is found that information needed to specify the functionality of the system does not exist in the business process model. System designers may then employ use case modeling to specify the needed system functionality, again spending significant time with stakeholders to gather the needed input. Stakeholders find this two-pass process redundant and wasteful of time and money since the input they provide to both modeling teams is largely identical, with each team capturing only the aspects relevant to their form of modeling. Developing a new paradigm and modeling approach that achieves the objectives of both business process modeling and use case modeling in an integrated form, in one analysis pass, results in time savings, increased accuracy and improved communication among all participants in the systems development process. Analysis of several case studies will show that inefficiency, wasted time and overuse of stakeholder resource time results from the separate application of business process modeling and use case modeling. A review of existing literature on the subject shows that while the problem of modeling both business process and use case information in a coordinated fashion has been recognized before, there are few if any approaches that have been proposed to reconcile and integrate the two methods. Based on both literature review and good modeling practices, a list of goals for the new paradigm and modeling approach forms the basis for the paradigm to be created. A grounded theory study is then conducted to analyze existing modeling approaches for both business processes and use cases and to provide an underlying theory on which to base the new paradigm. The two main innovations developed for the new paradigm are the usage process and the timebox. Usage processes allow system usages (use cases) to be identified as the business process model is developed, and the two to be shown in a combined process flow. Timeboxes allow processes to be positioned in time-relation to each other without the need to combine processes into higher level processes using causal relations that may not exist. The combination of usage processes and timeboxes allows any level of complex behavior to be modeled in one pass, without the redundancy and waste of separate business process and use case modeling work. Several pilot projects are conducted to test the new modeling paradigm in differing modeling situations with participants and subject matter experts asked to compare the traditional models with the new paradigm formulations.

The customer concept becomes more intertwined with the provider of products as serviceoriented business models is offered to the customer. This shift is referred as servitization in which innovation occurs in the company processes by shifting focus from providing products to providing product service systems (PSS). However, the servitization of the manufacturing industry has been slow compared to other sectors and there are many barriers to overcome for the transformation. Use phase data could be used as an enabler to resolve barriers to PSS. The collection of use phase data could be done through the usage of automatic identification technologies like QR codes. Despite the promising opportunities with collection of use phase data there are many challenges. Among them are the identification of use cases for the data. This study therefore aimed to identify both use cases and needed use phase data when collecting data using QR codes.  The manufacturing company Bosch Rexroth AB and their service department were chosen as a case study company, to establish their view on the use cases for QR codes. Additionally, a literature review identified the use phase data need for each use cases derived from the theory. The collected data was analyzed through an explanation building analysis in which plausible and rival explanations to the result was brought up. This resulted in five identified use cases for QR codes and from the use cases one identified need for use phase data. The identified use cases mainly providing value to the provider were derivation of new products or services and improvement of current products or services. The identified use cases mainly providing value to the external customer were the offering of predictive maintenance, the assistance in operations and the creation of a digital passport or image. The identified use phase data need was service data but also additional product related data that does not concern use phase of the products was also needed for the use cases.

本論文建立「Web 2.0後設架構分析框架」，可用於開發Web 2.0應用系統的結構化使用個案分析；首先從文獻歸納Web 2.0核心概念，再據之發展為分析框架。此框架包含兩部分，分別為「Web 2.0後設模型」以及兩階段的分析流程：第一階段以Web 2.0後設模型與系統需求產生出「Web 2.0實例模型」，第二階段加入非功能性需求分析，將實例模型轉換為UML使用個案。本論文使用四層之後設資料架構呈現此分析框架，並以股票交易型基金（ETF）之行銷與討論平台為例示範。 / This paper had proposed the “Web 2.0 meta-architecture analysis framework”, a structured use case analysis for Web 2.0 application systems: We first defined Web 2.0 core concepts and develop the analysis framework. The framework includes two parts: the “Web 2.0 meta-model” and a two-step analysis process. In the first step, the process generates “Web 2.0 instance-models” from the Web 2.0 meta-model and system requirements, which can be transformed into UML use cases along with non-functional requirements analysis in the second step. This paper presented this framework under four-layered meta-data architecture, and demonstrated the framework by using the case of ETF marketing and discussion platform.

[pt] Espera-se que o desenvolvimento de suítes de teste a partir de modelos possa contribuir substancialmente para a redução do esforço humano e aumentar a eficácia dos testes gerados. Entende-se por eficácia (ideal) dos testes o percentual de defeitos existentes encontrados a partir desses testes. Uma grande parte dessas técnicas baseia-se em máquinas de estado e quase sempre estão voltadas para o teste de funcionalidade. Entretanto, existe a necessidade de se poder testar sistemas altamente interativos, tais como smartphones e tablets, a partir de uma descrição de sua interface humano-computador. O objetivo da dissertação é efetuar uma primeira avaliação de uma técnica voltada para a geração de suítes de teste visando o teste de interfaces gráficas. Para tal,desenvolvemos e avaliamos a eficácia de uma ferramenta, chamada Easy, que utiliza casos de uso tabulares e máquina de estados para a geração automática da suíte de testes. Os casos de uso são descritos em linguagem natural restrita. A partir dessa descrição, a ferramenta constrói uma máquina de estado e, a seguir, a utiliza para gerar cenários. Por construção os cenários estarão em conformidade com os casos de uso. Cada cenário corresponde a um caso de teste. Os cenários são apresentados ao usuário em linguagem natural restrita, permitindo a visualização destes antes da geração dos scripts finais de testes. Os scripts gerados são destinados a uma ferramenta de execução automatizada voltada para o teste de interfaces gráficas. Neste trabalho, utilizou-se a ferramenta UI Automation, responsável pela execução de testes em aplicações destinadas ao iOS, sistema operacional de iPhone, iPad e iPod Touch. A eficácia do processo foi avaliada em uma aplicação real, disponível na loja virtual de aplicativos App Store. Além disso, foram realizados testes de IHC afim de avaliar a influência no custo da produção da suíte de teste. / [en] It is expected that the development of test suites from models can contribute substantially to reducing the human effort and to increase the effectiveness of the generated tests. Means for tests’ effectiveness (ideal) the percentage of existing defects found by these tests. Most of these techniques is based on state machines and mostly directed to testing the functionality. However, there is a need to be able to test highly interactive systems, such as smartphones and tablets, from a description of its human computer interface. The goal of the dissertation is to make a first evaluation of a technique aimed to generate test suites for test of human computer graphic interface. For this purpose was developed and evaluated its effectiveness, a tool called Easy, using use cases tabular and state machine for the automatic generation of the suite tests. The use cases are described in natural language restricted. From this description, the tool builds a state machine, and then uses this to generate scenarios. By construction scenarios will be in accordance with the use cases. Each scenario corresponds to a test case. The scenarios are presented to the user in natural language, allowing the visualization of them before the generation of the final scripts tests. The generated scripts are intended to a running automated tool geared to testing graphical interfaces. In this work, we used the UI Automation tool, responsible for running tests on applications for the iOS, operational system for iPhones, iPads and iPod touchs. The effectiveness of the procedure was evaluated in a real application, available in the online store applications App Store. In addition, HCI tests were performed in order to evaluate the influence on the cost of production of the test suite.

Esta tese tem o objetivo de definir um processo para análise de requisitos não-funcionais orientado a aspectos denominado PARNAFOA. Este processo utiliza, de maneira integrada, métodos de tratamento de requisitos não-funcionais, baseados no NFR Framework, e métodos orientados a aspectos. Como resultado principal obtém-se um modelo de casos de uso que incorpora novas funções relacionadas aos requisitos não-funcionais. A aplicação do PARNAFOA foi realizada em cinco sistemas de software, com domínios, características e complexidades diversos. A avaliação da aplicação deste processo mostrou que o tratamento dos requisitos não-funcionais, desde as fases iniciais do desenvolvimento dos sistemas de software, complementa o modelo de casos de uso com funções adicionais ou gera restrições de projeto. Se estes requisitos não forem considerados desde o início, a introdução posterior dessas funções pode causar alterações nos modelos consolidados ou as atividades de projeto podem ser realizadas sem considerar as restrições. As aplicações do PARNAFOA e sua conseqüente melhoria, incorporada após sua avaliação, permitiu torná-lo mais flexível do que sua versal inicial. Aplicações futuras, com outros tipos de requisitos não-funcionais, irão permitir o amadurecimento deste processo. / The aim of this thesis is to define an aspect-oriented non-functional requirements analysis process named PARNAFOA. This process applies nonfunctional requirements methods in an integrated manner, based on NFR Framework, and aspect-oriented methods. A use case model that embodies non-functional requirements as new functions is the main result obtained from this process. PARNAFOA application was performed in five software systems, with diverse features, domains and complexities. The evaluation of this process application showed that the treatment of these non-functional requirements, from the early phases of software systems development, complements the use case model with additional new functions or generates project restrictions. If these requirements are not considered from the very beginning, the introduction of these functions at a later phase can generate modifications in consolidated models or project activities, that do not consider these restrictions, can be performed. The PARNAFOA applications and consequent improvement, incorporated after the assessment, allowed it to become more flexible than the initial version. Future applications, with other non-functional requirements types, will provide this process maturity.

Esta tese tem o objetivo de definir um processo para análise de requisitos não-funcionais orientado a aspectos denominado PARNAFOA. Este processo utiliza, de maneira integrada, métodos de tratamento de requisitos não-funcionais, baseados no NFR Framework, e métodos orientados a aspectos. Como resultado principal obtém-se um modelo de casos de uso que incorpora novas funções relacionadas aos requisitos não-funcionais. A aplicação do PARNAFOA foi realizada em cinco sistemas de software, com domínios, características e complexidades diversos. A avaliação da aplicação deste processo mostrou que o tratamento dos requisitos não-funcionais, desde as fases iniciais do desenvolvimento dos sistemas de software, complementa o modelo de casos de uso com funções adicionais ou gera restrições de projeto. Se estes requisitos não forem considerados desde o início, a introdução posterior dessas funções pode causar alterações nos modelos consolidados ou as atividades de projeto podem ser realizadas sem considerar as restrições. As aplicações do PARNAFOA e sua conseqüente melhoria, incorporada após sua avaliação, permitiu torná-lo mais flexível do que sua versal inicial. Aplicações futuras, com outros tipos de requisitos não-funcionais, irão permitir o amadurecimento deste processo. / The aim of this thesis is to define an aspect-oriented non-functional requirements analysis process named PARNAFOA. This process applies nonfunctional requirements methods in an integrated manner, based on NFR Framework, and aspect-oriented methods. A use case model that embodies non-functional requirements as new functions is the main result obtained from this process. PARNAFOA application was performed in five software systems, with diverse features, domains and complexities. The evaluation of this process application showed that the treatment of these non-functional requirements, from the early phases of software systems development, complements the use case model with additional new functions or generates project restrictions. If these requirements are not considered from the very beginning, the introduction of these functions at a later phase can generate modifications in consolidated models or project activities, that do not consider these restrictions, can be performed. The PARNAFOA applications and consequent improvement, incorporated after the assessment, allowed it to become more flexible than the initial version. Future applications, with other non-functional requirements types, will provide this process maturity.

Made available in DSpace on 2016-04-29T14:23:31Z (GMT). No. of bitstreams: 1 Marcus Vinicius Milanez.pdf: 1438354 bytes, checksum: 792d4f5889dafba8c4e2f71a02c050a0 (MD5) Previous issue date: 2014-09-20 / The development of computer programs is a complex activity, characterized by costs and deadlines that are difficult to estimate. Requirements change frequently, resulting in products of variable reliability. Currently, there are no formal theories that completely address these underlying challenges. Several approaches have been used over time to achieve incremental progress, leading to a significant number of programming languages, development processes, and techniques. Test Driven Development (TDD) is a recently-developed approach which extends the human capabilities to develop computer programs by providing tools to mitigate the difficulties mentioned. Although TDD aggregates a set of support and control elements, it does not include mechanisms that directly help developers with deriving implementations from a set of requirements previously captured and analyzed. As result of this absence, difficulties in understanding its nature and to elaborate the software through independent modules can be observed, ultimately limiting the impact of TDD on the reliability of software. The objective of this research is to overcome the shortcomings mentioned, complementing Kent Beck s TDD proposal by introducing a modeling stage guided by Use Cases, following the ideas of Ivar Jacobson and Wirfs-Brock. Through this approach, assessed by a case study conducted together with industry professionals, enhancements in TDD usage experience could be observed, altering the manner in which this proposal is commonly understood, used and evaluated / Desenvolver programa de computador é uma atividade complexa, cujos custos e prazos são difíceis de serem estimados, caracterizada por requisitos mutantes e que resulta em produtos sem garantias plenas de funcionamento. No atual estado de desenvolvimento desta área de pesquisa, ainda não existe teoria que estabeleça as bases dos conhecimentos necessários a prover soluções a estes problemas. Diversas abordagens foram utilizadas ao longo do tempo a fim de encontrar meios que culminassem em avanços, originando um conjunto expressivo de linguagens de programação, processos e técnicas de desenvolvimento. Uma tentativa recente que intenciona estender as capacidades humanas de desenvolver programas de computador, provendo elementos que permitiriam amenizar essas dificuldades, é uma ferramenta intelectual chamada Test Driven Development (TDD). Embora agregue um conjunto de elementos de apoio e controle ao desenvolvimento, TDD não dispõe de mecanismos que auxiliem desenvolvedores a derivar implementações a partir de um conjunto de requisitos previamente capturados e analisados. Como resultado dessa ausência, observam-se dificuldades em avaliar sua natureza e em propor a elaboração do software em módulos independentes, tornando TDD uma ferramenta questionável. O objetivo desta pesquisa reside em superar as lacunas citadas, complementando a proposta de Kent Beck sobre TDD por meio da introdução de uma etapa de modelagem guiada por modelos casos de uso (Use Cases), seguindo as ideias de Ivar Jacobson e Wirfs-Brock. Por meio desta abordagem, avaliada por estudo de caso realizado em conjunto com profissionais da indústria, observou-se um aprimoramento da experiência de utilização de TDD, alterando a maneira pela qual essa proposta é comumente compreendida, utilizada e avaliada

Currently the telecom world is moving towards next generation 5G (5th Generation) technology. Previous generations of mobile networks addressed human communications predominantly for voice & data but apart from human to human communications 5G brings machine to machine communication in a broader way. The possibilities of use cases are endless and 5G is a system of system. The vision for 5G is creating an ultra-connected society. 5G will be the general-purpose technology and 5G will act as a catalyst for the industry disruption. By interconnecting industries using the 5G technology will make them to be cost effective, efficient and more productive by optimally utilizing the infrastructure. It is expected that globally 5G value chain itself will contribute $3.5 trillion in output and provides 22million jobs in 2035. It is expected that 1 Trillion IoT devices by 2035 and will be worthy of $5 trillion. In Taiwan, 5G is expected to create 510,000 Taiwanese jobs and to unleash $134 billion economic value in gross output of goods and services. Apart from monetary benefits 5G is expected to bring social benefits to the human life too in enormous ways. To tap that potential many countries, governments encourage and push the mobile ecosystem to start to build the 5G networks and to launch it. 5G is coming earlier than expected and society needs to adopt to the upcoming disruption.