Software Quality is a key concern for any companies working with software development. This is true due to the fact that the success of any software directly depends on Quality of software. It is expected that the software is of best quality for a long duration of time. With the introduction of Mobile applications the task of maintaining the quality of an application has been difficult and have faced many challenges. Many companies working with mobile application have reformed their process in order to maintain the quality of their application. The introduction of Automation testing in the test process is one such reform that have changed the face of mobile application testing in today’s world. This work deals with the concepts of Automation System testing for the mobile application which is until now a new thing and it has many things yet to be explored. The approach to automation testing is simple yet unique for the department of PT-MT/Quality Management in Robert Bosch GmbH based in Leinfelden, Stuttgart. Over here a selection and implementation of a test framework will be done for Automation testing of the mobile Applications that are being developed. For this a requirement specification document is being created which will form the basis for selecting a framework from the KT Analysis table. Finally, a framework TestComplete will be implemented for the already developed application "PLR measure&go" The implementation will include all the procedure required to set up the test framework as a part of documentation. The framework TestComplete will be used to create System test for iOS and Android operation system. Lastly the execution of test and the Result reporting is being shown as a complete process for Automation testing.

Software testing is a tedious and very expensive undertaking. Automatic test data generation is, therefore, proposed in this research to help testers reduce their work as well as ascertain software quality. The concept of test driven development (TDD) has become increasingly popular during the past several years. According to TDD, test data should be prepared before the beginning of code implementation. Therefore, this research asserts that the test data should be generated from the software design documents which are normally created prior to software code implementation. Among such design documents, the UML state machine diagrams are selected as a platform for the proposed automated test data generation mechanism. Such diagrams are selected because they show behaviours of a single object in the system. The genetic algorithm (GA) based approach has been developed and applied in the process of searching for the right amount of quality test data. Finally, the generated test data have been used together with UML class diagrams for JUnit test code generation. The GA-based test data generation methods have been enhanced to take care of parallel path and loop problems of the UML state machines. In addition the proposed GA-based approach is also targeted to solve the diagrams with parameterised triggers. As a result, the proposed framework generates test data from the basic state machine diagram and the basic class diagram without any additional nonstandard information, while most other approaches require additional information or the generation of test data from other formal languages. The transition coverage values for the introduced approach here are also high; therefore, the generated test data can cover most of the behaviour of the system.

The Open Source Software Development (OSSD) model has launched products in rapid succession and with high quality, without following traditional quality practices of accepted software development models (Raymond 1999). Some OSSD projects challenge established quality assurance approaches, claiming to be successful through partial contrary techniques of standard software development. However, empirical studies of quality assurance practices for Open Source Software (OSS) are rare (Glass 2001). Therefore, further research is required to evaluate the quality assurance processes and methods within the OSSD model. The aim of this research is to improve the understanding of quality assurance practices under the OSSD model. The OSSD model is characterised by a collaborative, distributed development approach with public communication, free participation, free entry to the project for newcomers and unlimited access to the source code. The research examines applied quality assurance practices from a process view rather than from a product view. The research follows ideographic and nomothetic methodologies and adopts an antipositivist epistemological approach. An empirical research of applied quality assurance practices in OSS projects is conducted through the literature research. The survey research method is used to gain empirical evidence about applied practices. The findings are used to validate the theoretical knowledge and to obtain further expertise about practical approaches. The findings contribute to the development of a quality assurance framework for standard OSSD approaches. The result is an appropriate quality model with metrics that the requirements of the OSSD support. An ideographic approach with case studies is used to extend the body of knowledge and to assess the feasibility and applicability of the quality assurance framework. In conclusion, the study provides further understanding of the applied quality assurance processes under the OSSD model and shows how a quality assurance framework can support the development processes with guidelines and measurements.

[pt] Atualmente, um dos principais requisitos de um projeto de desenvolvimento de software é a entrega de um produto de qualidade que obedeça ao prazo e orçamento estipulados e atenda às necessidades do cliente. Utilizando a premissa de que a qualidade do produto desenvolvido está intimamente relacionada à qualidade dos processos utilizados no seu desenvolvimento, muitas organizações investem em programas de melhoria contínua de processos, onde estes processos são constantemente avaliados e melhorados. Este trabalho propõe uma abordagem para a avaliação de processos baseada em análise do risco e da conformidade em processos de desenvolvimento. Esta abordagem é constituída por um método de avaliação em duas etapas e por uma ferramenta de apoio. Na primeira fase do método, uma avaliação em abrangência é realizada para identificar em que áreas se encontram os maiores problemas nos processos. Na segunda fase, uma avaliação mais elaborada e criteriosa é realizada apenas nas áreas críticas, diminuindo o custo e aumentando a eficiência do investimento em melhoria. A ferramenta utiliza um mecanismo de questionários e checklists para verificar o risco e a conformidade dos processos da organização. Estes questionários e checklists estão associados a uma base de conhecimento organizada segundo um modelo de maturidade ou norma de qualidade de referência. Ao final de uma avaliação são gerados relatórios, tabelas e gráficos que apóiam a tomada de decisão e orientam a elaboração de um plano de ação para a melhoria dos processos. A abordagem foi utilizada em três experimentos controlados. / [en] Nowadays, one of the main requirements of a software development project is the delivery of a quality product that conforms to the expected schedule and budget and satisfies customer needs. Using the hypothesis that the quality of the developed product is closely related to the quality of the processes used in its development, many organizations invest in process improvement programs, where the processes are continuously assessed and improved. In this work we propose an approach for process assessment based on risk and process compliance analysis. This approach is composed of a two-step appraisal method and a supporting tool. In the first step of the method, a quick analysis is executed to identify the most problematic areas. In the second one, a more elaborated analysis is performed only in the critical areas, reducing the costs and increasing the effectiveness of the appraisal. The tool uses a mechanism of surveys and checklists to verify the risk and the compliance of the process of the organization. A knowledge base is organized in accordance to a reference quality norm or maturity model. At the end of an assessment, reports, tables and charts support the decision-taking, and they can be used to guide an improvement program. The approach has been used in three case studies.

A Engenharia de Software tem desenvolvido técnicas e métodos para apoiar o desenvolvimento de software confiável, flexível, com baixo custo de desenvolvimento e fácil manutenção. A avaliação da manutenibilidade contribui para fornecer meios para produzir software com alta qualidade. Este trabalho apresenta um experimento controlado para avaliar a manutenibilidade entre as abordagens de web services: RESTful e SOAP-WSDL. Esta avaliação foi conduzida usando 3 programas implementados na linguagem de programação Java e com a mesma arquitetura. Com base na arquitetura projetada, os web services desenvolvidos foram utilizados como objetos em estudos de caso, possibilitando avaliar e comparar a sua manutenibilidade. Os resultados obtidos demonstraram relações entre as informações sobre o custo e a qualidade dos serviços web, que contribuíram para esclarecer os critérios para a obtenção de uma boa relação entre o custo da manutenção e a evolução dos serviços web. Para concluir, os resultados indica que os web services RESTful são mais manuteníveis do lado do servidor, e os web services SOAP-WSDL são mais manuteníveis do lado do cliente. Os estudos realizados no experimento controlado são promissores e podem auxiliar na redução de custo na manutenção dos serviços web, melhorando dessa forma a qualidade do software no geral / Software Engineering has developed techniques and methods to support the development of reliable software, exible, low development cost and easy maintenance. The evaluation of maintainability contributes in this direction, providing the means to produce software with high quality. This paper presents an controlled experiment to evaluate the maintainability between the approaches of web services: RESTful and SOAP-WSDL. This evaluation was conducted using four programs implemented in the Java programming language, using the same architecture. Based on the designed architecture, Web services were developed as objects used in case studies, allowing to evaluate and compare its maintainability. The results showed relationships between the information on the cost and quality of web services, which contributed to clarify the criteria for obtaining a good relationship between the cost of maintenance and evolution of web services. In conclusion, the results indicate the RESTful web services are more maintainable server side in contrast to the SOAP-WSDL web services are more maintainable client side. Studies in controlled experiments are promising and may help reduce the maintenance cost of web services, thus improving overall software quality

As aplicações desenvolvidas com a linguagem JavaScript, vêm aumentando a cada dia, não somente aquelas na web (client-side), como também as aplicações executadas no servidor (server-side) e em dispositivos móveis (mobile). Neste contexto, a existência de ferramentas para identicação de defeitos e code smells é fundamental, para auxiliar desenvolvedores durante a evoluçãp destas aplicações. A maioria dessas ferramentas utiliza uma lista de defeitos predenidos que são descobertos a partir da observação das melhores práticas de programação e a intuição do desenvolvedor. Para melhorar essas ferramentas, a descoberta automática de defeitos e code smells é importante, pois permite identicar quais ocorrem realmente na prática e de forma frequente. Uma ferramenta que implementa uma estratégia semiautomática para descobrir padrões de defeitos através de agrupamentos das mudanças realizadas no decorrer do desenvolvimento do projeto é a ferramenta BugAID. O objetivo deste trabalho é contribuir nessa ferramenta estendendo-a com melhorias na abordagem da extração de características, as quais são usadas pelos algoritmos de clusterização. O módulo estendido encarregado da extração de características é chamado de BugAIDExtract+ +. Além disso, neste trabalho é realizada uma avaliação de vários algoritmos de clusterização na descoberta dos padrõs de defeitos em software JavaScript / Applications developed with JavaScript language are increasing every day, not only for client-side, but also for server-side and for mobile devices. In this context, the existence of tools to identify faults is fundamental in order to assist developers during the evolution of their applications. Most of these tools use a list of predened faults that are discovered from the observation of the programming best practices and developer intuition. To improve these tools, the automatic discovery of faults and code smells is important because it allows to identify which ones actually occur in practice and frequently. A tool that implements a semiautomatic strategy for discovering bug patterns by grouping the changes made during the project development is the BugAID. The objective of this work is to contribute to the BugAID tool, extending this tool with improvements in the extraction of characteristics to be used by the clustering algorithm. The extended module that extracts the characteristics is called BE+. Additionally, an evaluation of the clustering algorithms used for discovering fault patterns in JavaScript software is performed

Appealing features of cloud services such as elasticity, scalability, universal access, low entry cost, and flexible billing motivate consumers to migrate their core businesses into the cloud. However, there are challenges about security, privacy, and compliance. Building compliant systems is difficult because of the complex nature of regulations and cloud systems. In addition, the lack of complete, precise, vendor neutral, and platform independent software architectures makes compliance even harder. We have attempted to make regulations clearer and more precise with patterns and reference architectures (RAs). We have analyzed regulation policies, identified overlaps, and abstracted them as patterns to build compliant RAs. RAs should be complete, precise, abstract, vendor neutral, platform independent, and with no implementation details; however, their levels of detail and abstraction are still debatable and there is no commonly accepted definition about what an RA should contain. Existing approaches to build RAs lack structured templates and systematic procedures. In addition, most approaches do not take full advantage of patterns and best practices that promote architectural quality. We have developed a five-step approach by analyzing features from available approaches but refined and combined them in a new way. We consider an RA as a big compound pattern that can improve the quality of the concrete architectures derived from it and from which we can derive more specialized RAs for cloud systems. We have built an RA for HIPAA, a compliance RA (CRA), and a specialized compliance and security RA (CSRA) for cloud systems. These RAs take advantage of patterns and best practices that promote software quality. We evaluated the architecture by creating profiles. The proposed approach can be used to build RAs from scratch or to build new RAs by abstracting real RAs for a given context. We have also described an RA itself as a compound pattern by using a modified POSA template. Finally, we have built a concrete deployment and availability architecture derived from CSRA that can be used as a foundation to build compliance systems in the cloud. / Includes bibliography. / Dissertation (Ph.D.)--Florida Atlantic University, 2015. / FAU Electronic Theses and Dissertations Collection

by Ng Mei Po Mabel. / Thesis (M.B.A.)--Chinese University of Hong Kong, 1994. / Includes bibliographical references (leave 51-52). / ABSTRACT --- p.ii / TABLE OF CONTENTS --- p.iii / Chapter / Chapter I. --- INTRODUCTION --- p.1 / Chapter II. --- PROBLEM IN FOCUS --- p.3 / Chapter III. --- SCOPE OF STUDY --- p.7 / Chapter IV. --- RESEARCH METHODOLOGY --- p.8 / Chapter V. --- ORGANISATION OF INFORMATION TECHNOLOGY SERVICES DEPARTMENT --- p.8 / Function --- p.8 / Mission --- p.8 / Organisation Structure --- p.8 / Personnel Schedule --- p.8 / Requests for Computerisation --- p.10 / Departmental IS Strategic Planning --- p.10 / Microcomputer Systems and Items --- p.10 / Mainframe Systems and Mid Range Systems --- p.10 / Chapter VI. --- SYSTEMS DEVELOPMENT LIFE CYCLE --- p.12 / Introduction --- p.12 / Detailed Description --- p.15 / What is SSADM+ in ITSD ？ --- p.22 / Implementation of SSADM+ in ITSD --- p.26 / Chapter VII. --- THE ROAD TO ACHIEVE IS09001 --- p.28 / The Principal Concepts and Significance of IS09000 --- p.28 / Why is IS09000 Recommended to be Necessary for ITSD? --- p.29 / Overview of the Feasibility of Applying IS09000 in ITSD --- p.30 / Recommendations --- p.35 / Problems of Study --- p.38 / APPENDIX --- p.39 / BILIOGRAPHY --- p.51

Submitted by Maicon Juliano Schmidt (maicons) on 2015-06-30T12:58:44Z No. of bitstreams: 1 Lizandra Bays dos Santos.pdf: 9244211 bytes, checksum: 5d2cbae0a96db72c10de129513e76403 (MD5) / Made available in DSpace on 2015-06-30T12:58:44Z (GMT). No. of bitstreams: 1 Lizandra Bays dos Santos.pdf: 9244211 bytes, checksum: 5d2cbae0a96db72c10de129513e76403 (MD5) Previous issue date: 2013-01-31 / CAPES - Coordenação de Aperfeiçoamento de Pessoal de Nível Superior / A qualidade do processo de desenvolvimento de software, somente, não garante a qualidade do produto que é desenvolvido, sendo necessário combinar técnicas de qualidade do processo e do produto. Existem diversos esforços na comunidade acadêmica e no mercado para de modelos de certificação de qualidade do processo, e observa-se uma lacuna no que tange à certificação de qualidade de produtos de software. Este trabalho o desenvolvimento de um sistema que visa dar suporte para a certificação de qualidade de produtos de software. Um framework de processo para certificação de produtos é apresentado, o qual é composto de um subprocesso de especialização do modelo de qualidade focado em riscos, um subprocesso de medição da qualidade e um sobprocesso de avaliação da qualidade. Para apoiar estes subprocessos, a arquitetura do sistema desenvolvido faz uso de ontologias para representar o conhecimento envolvido no modelo de qualidade e agentes de software para manipular os indivíduos nas ontologias. / The software development process quality does not assure product quality, being necessary to combine techniques of process quality and product quality. There are several efforts in the academic community and in the market for models of quality certification of the development process, so that there is a gap regarding the quality certification of the product developed. This work presents the development of a system that aims to support the certification of quality software products. A framework of product certification process is showed, which is composed of subprocesses of quality model specialization, quality measurement and quality assessment. To support these subprocesses, the developed system architecture uses ontologies to represent knowledge about the quality model and software agents for handling to individuals in the ontologies.

Made available in DSpace on 2016-04-29T14:23:20Z (GMT). No. of bitstreams: 1 Hebert Bratefixe Alquimim.pdf: 2664407 bytes, checksum: 77eb81380d89e7688a502253778a5265 (MD5) Previous issue date: 2013-06-19 / Within the advent of Internet and its popularization, several Software that allow the creation of electronic questionnaire for a focus on evaluation of educational process in learning, appear as an alternative to the teacher, even if the course is taught in presence meeting, allowing a differentiated evaluation. This research has as aim to describe a methodology for evaluating electronic questionnaire son the Web, using as basis the standard ISO /IEC 9126, which specifies the quality of Software products and the standard ISO /IEC 14598 which describes the evaluation process of the Software product. To perform the evaluation, Webapps were identified for building electronic questionnaires that comply with the criteria established and at the end, the evaluation will have their data analyzed and compared according to the quality of Software / Com o advento e a popularização da Internet, diversos Softwares que permitem a criação de questionários eletrônicos como foco na avaliação de ensino aparecem como uma alternativa para o docente, mesmo que a disciplina lecionada seja presencial, permitindo assim uma forma diferenciada de avaliação. Este trabalho tem por objetivo descrever uma proposta de critério para avaliação de questionários eletrônicos na Web, utilizando como base a norma ABNT NBR ISO/IEC 9126, que especifica as qualidades de produtos de Software e, a norma ABNT NBR ISO/IEC 14598 que descreve o processo de avaliação de produto de Software. Para a realização da avaliação foram identificados Webapps para construção de questionários eletrônicos que estejam de acordo com o critério estabelecido e ao final, terão seus dados analisados e comparados de acordo com as características de qualidade de Software