Context: Software testing is the process of assessing quality of a software product to determine whether it matches with the existing requirements of the customer or not. Software testing is one of the “Verification and Validation,” or V&V, software practices. The two basic techniques of software testing are Black-box testing and White box testing. Black-box testing focuses solely on the outputs generated in response to the inputs supplied neglecting the internal components of the software. Whereas, White-box testing focuses on the internal mechanism of the software of any application. To explore the feasibility of black-box and white-box testing under a given set of conditions, a proper test automation framework needs to be deployed. Automation is deployed in order to reduce the manual effort and to perform testing continuously, thereby increasing the quality of the product. Objectives: In this research, cloud hosted application is automated using TestComplete tool. The objective of this thesis is to verify the functionality of cloud application such as test appliance library through automation and to measure the impact of the automation on release cycles of the organisation. Methods: Here automation is implemented using scrum methodology which is an agile development software process. Using scrum methodology, the product with working software can be delivered to the customers incrementally and empirically with updating functionalities in it. Test appliance library functionality is verified deploying testing device thereby keeping track of automatic software downloads into the testing device and licenses updating in the testing device. Results: Automation of test appliance functionality of cloud hosted application is made using TestComplete tool and impact of automation on release cycles is found reduced. Through automation of cloud hosted application, nearly 24% of reduction in level of release cycles can be observed thereby reducing the manual effort and increasing the quality of delivery. Conclusion: Automation of a cloud hosted application provides no manual effort thereby utilisation of time can be made effectively and application can be tested continuously increasing the efficiency and / AUTOMATION OF A CLOUD HOSTED APPLICATION

Providing means for the development of correct software still remains a central challenge of computer science. In this thesis we present a novel approach to tool-based inspection focusing on the functional correctness of software artifacts. The approach is based on conventional inspection in the style of Fagan, but extended with elements of formal verification in the style of Hoare. In Hoare’s approach a program is annotated with assertions. Assertions express conditions on program variables and are used to specify the intended behavior of the program. Hoare introduced a logic for formally proving the correctness of a program with respect to the assertions. Our main contribution concerns the predicates used to express assertions. In contrast to Hoare, we allow an incomplete axiomatization of those predicates beyond the point where a formal proof of the correctness of the program may no longer be possible. In our approach predicates may be defined in a completely informal manner (e.g. using natural language). Our hypothesis is, that relaxing the requirements on formal rigor makes it easier for the average developer to express and reason about software artifacts while still allowing the automatic generation of relevant, focused questions that help in finding defects. The questions are addressed in the inspection, thus filling the somewhat loosely defined steps of conventional inspection with a very concrete content. As a side-effect our approach facilitates a novel systematic, asynchronous inspection process based on collecting and assessing the answers to the questions. We have adapted the method to the inspection of code as well as the inspection of early designs. More precisely, we developed prototype tools for the inspection of programs written in a subset of Java and early designs expressed in a subset of UML. We claim that the method can be adapted to other notations and (intermediate) steps of the software process. Technically, our approach is working and has successfully been applied to small but non-trivial code (up to 1000 lines) and designs (up to five objects and ten messages). An in-depth industrial evaluation requires an investment of substantial resources over many years and has not been conducted. Despite this lack of extensive assessment, our experience shows that our approach indeed makes it easier to express and reason about assertions at a high level of abstraction.

Java is a major platform for performance sensitive applications. Unit testing of functionality has already become a common practice in software devel- opment; however, the amount of projects employing performance tests is substantially lower. A comprehensive study in combination with a short sur- vey among developers is made in order to examine the current situation in open-source projects written in Java. Results show that suitable tools for measurements exist, but they are hard to use or the outputs are difficult to understand. To improve the situation in favor of performance evaluation a set of user friendly tools for collecting, comparing and visualizing the data is designed, implemented, and verified on a sample Java project. 1

Context: Software testing is the process of assessing quality of a software product to determine whether it matches with the existing requirements of the customer or not. Software testing is one of the “Verification and Validation,” or V&V, software practices. The two basic techniques of software testing are Black-box testing and White box testing. Black-box testing focuses solely on the outputs generated in response to the inputs supplied neglecting the internal components of the software. Whereas, White-box testing focuses on the internal mechanism of the software of any application. To explore the feasibility of black-box and white-box testing under a given set of conditions, a proper test automation framework needs to be deployed. Automation is deployed in order to reduce the manual effort and to perform testing continuously, thereby increasing the quality of the product.   Objectives: In this research, cloud hosted application is automated using TestComplete tool. The objective of this thesis is to verify the functionality of Cloud application known as Test data library or Test Report Analyzer through automation and to measure the impact of the automation on release cycles of the organization.   Methods: Here automation is implemented using scrum methodology which is an agile development software process. Using scrum methodology, the product with working software can be delivered to the customers incrementally and empirically with updating functionalities in it. Test data library or Test Report Analyzer functionality of Cloud application is verified deploying testing device thereby the test cases can be analyzed thereby analyzing the pass or failed test cases.   Results: Automation of test report analyzer functionality of cloud hosted application is made using TestComplete and impact of automation on release cycles is reduced. Using automation, nearly 24% of change in release cycles can be observed thereby reducing the manual effort and increasing the quality of delivery.   Conclusion: Automation of a cloud hosted application provides no manual effort thereby utilization of time can be made effectively and application can be tested continuously increasing the efficiency and the quality of an application. / AUTOMATION OF A CLOUD HOSTED APPLICATION

É possível notar no trabalho diário das empresas que a pressão por diminuir o prazo de entrega dos softwares ainda é uma realidade. Neste contexto, empresas adotam técnicas de desenvolvimento ágil de software, implementando entregas constantes e estabelecendo ciclos iterativos e curtos no processo de desenvolvimento de software. Mas, se por um lado estas técnicas visam inovar e reduzir tempo de desenvolvimento, por outro, as empresas sentem-se pressionadas a adotar a forma tradicional de manter a qualidade de software. Neste ponto, o CMMI se apresenta como um modelo de maturidade de reconhecimento mundial e é classificado na abordagem tradicional por pregar grande formalismo e foco no processo. A abordagem ágil coloca que os indivíduos e suas interações têm maior importância que os processos e as ferramentas e que ser adaptável às mudanças é mais importante do que seguir a rigor o planejado. Ao integrar estes dois modelos de abordagens distintas espera-se que as práticas ágeis possam ajudar organizações maduras a se tornarem mais flexíveis. Com o intuito de averiguar esta integração, utilizou-se o método de pesquisa de estudo de caso, de modo a se aprofundar nas empresas que possuem certificação CMMI e decidiram adotar o modelo de desenvolvimento ágil. O objetivo é levantar como estas empresas resolveram os pontos de conflito da abordagem tradicional e ágil, de modo a se tornarem mais eficazes. O estudo ainda contém um quadro de integração CMMI versus desenvolvimento ágil de modo a elencar os pontos que merecem maior atenção e esforço de adaptação, visando a concretização da integração. / It\'s possible to notice in the daily work of companies that pressure by decreasing the delivery of software is still a reality. It is in this context that companies adopt the techniques of agile software development, implementing and establishing constant deliveries and short iterative cycles in the process of software development. But if on the one hand these techniques aim to innovate and reduce development time, on the other, companies feel pressured to adopt the traditional way of maintaining the quality of software. At this point, the CMMI is presented as maturity model worldwide recognition, classified in the traditional approach for preaching extensive formalism and focus on the process, as the agile approach puts individuals and their interactions is more important than processes and tools, where being adaptable changes is more important than following the strict what was planned. By integrating these two models of different approaches, it is expected that agile practices can help organizations mature to become more flexible. In order to investigate this integration is that this study uses the research method of case study so as to deepen the companies that have decided to adopt CMMI and agile development model. The goal is to raise as these companies solved the trouble spots of the traditional approach and agile in order to become more effective. The study also contain a framework for integrating CMMI vs. Agile development in order to list the points that deserve more attention and effort to adapt in order to achieve integration.

A importância dos sistemas de software segue crescendo para grande parte das organizações. A expansão das funcionalidades viabilizadas com a implantação destes sistemas em produtos manufaturados e a emergência das \"mídias digitais\", que compreendem conteúdo digital, software e múltiplos canais de acesso ao mercado, são exemplos recentes nos quais os sistemas de software assumiram posição central para a estratégia corporativa. Grande parte das pesquisas realizadas sobre software não considera explicitamente os vínculos existentes entre o mercado no qual estas empresas atuam e seus processos organizacionais; como conseqüência, tanto pesquisa como prática em engenharia de software tendem a ser realizadas de forma neutra, e na perspectiva de um desenvolvedor de software, diferentes atividades de desenvolvimento são consideradas como igualmente relevantes para a obtenção dos objetivos corporativos. Este projeto de pesquisa analisa como acontece o alinhamento entre objetivos estratégicos e o processo de desenvolvimento em empresas de software e propõe um método para garantir que o processo de desenvolvimento encontra-se alinhado com os objetivos do negócio. O método inclui a categorização de diferentes companhias de software de acordo com as suas habilidades principais e a customização da técnica Technology Roadmapping para empresas de software. O percurso metodológico desenvolvido para atingir os objetivos propostos não é convencional e envolve diferentes etapas nas quais a recuperação de teorias, de conceitos e de modelos foi mesclada com atividades de pesquisa para o detalhamento, teste e ratificação dos diversos elementos que vêm a constituir o produto acima mencionado. Os resultados obtidos são consistentes com os objetivos propostos e incluem um referencial para análise da indústria de Telecomunicações, um referencial para análise da indústria de software, incorporando questões sobre mercado, objetivos estratégicos, produtos e serviços e processo de desenvolvimento, e um método de alinhamento entre objeticos estratégicos e processo de desenvolvimento em empresas de software. / Software importance is growing fast and consistently for many organizations. The growth of software functionality in manufactured products and the emergence of the digital media, convergent spaces comprehending digital content, software, and multi-channels to the market, are recent examples of organizational changes where software assumed a central position for the corporate strategy. Much of current research about software does not explicitly consider the linkages between the software market and their organizational processes; as a consequence, software engineering practice and research is done in a value-neutral setting, and from a developer point of view, different activities are considered equally important for the achievement of corporate goals. This research project analyzes the alignment between strategic objectives and development process at software companies and presents a method to ensure that the development process is aligned with the corporate capabilities required to exploit future market opportunities. The method includes the categorization of different software companies according to their core capabilities and the customization of the Technology Roadmapping technique for software companies. To achieve the proposed goal it was necessary to develop a different approach, in which theories, concepts and models were tested against empirical initiatives, aiming to validate the different elements that constitute the mentioned result. These obtained results are consistent with the proposed objectives, and include a framework to analyze the telecommunication industry, a framework to analyze the software industry, concerning issues such as market, strategic objectives, products and services and development process, and a method to align strategic objectives and development process at software companies.

A sistematização do PDS (processo de desenvolvimento de software) é reconhecida como um fator chave para o desempenho competitivo das empresas, pois assim garante-se a repetibilidade e a qualidade dos projetos de desenvolvimento. A sistematização do PDS é um dos projetos de mudança que possui um grande impacto na melhoria do processo, uma vez que a definição do processo estabelece o padrão de trabalho, como também as ferramentas de apoio ao processo. Esse projeto de melhoria deve ainda estar inserido no contexto mais amplo da gestão de mudanças das empresas, pois seu impacto pode afetar todas as áreas da empresa. O presente trabalho tem por objetivo apresentar uma metodologia de gestão de mudanças desenvolvida, com ênfase no relato de experiências práticas de sua aplicação, na institucionalização do processo de venda e desenvolvimento de software sob encomenda (PV&DS) de uma empresa desenvolvedora de software, que está inserida em uma rede de colaboração. A metodologia proposta sintetiza as melhores práticas dos seguintes métodos de gestão de mudança: SSM (Soft Systems Methodology); Modelo Ideal (Initiating, Diagnosing, Acting, Establishing e Learning ); DMAIC (Define, Measure, Analyze e Control) do Six Sigma; metodologia de transformação TransMeth; e metodologia de transformação do PDP. Três projetos de mudanças foram implantados: instanciação do PV&DS; implantação da fase de vendas; e implantação da fase planejar projeto. A utilização da metodologia de gestão de mudança proposta mostrou ser uma adequada ferramenta para a implantação de mudanças. Ela serviu como um guia para a customização e institucionalização do novo processo da empresa, proporcionando aos colaboradores um espírito de confiança e otimismo quanto aos resultados da mudança. / Software development process (SDP) systematization is acknowledged as a key factor for the competitive development of companies. It ensures repeatability and quality of development projects. The process of the SDP systematization is a change projects that leads to great improvements in SPD. The definition of the project establishes a work model, as well as the support tools for the SDP. This improvement project must also be incorporated into a wider context of the company’s change management. Because its impact may influence all areas of the company. This work presents a change management method, including a report that describes the practical experiences that were applied to the institutionalization of sales process and software development process (SP&SDP) of a software development company, which is part of a collaboration network. The proposed method synthesizes the best practices of the following change management methods: SSM (Soft Systems Methodology); Ideal (Initiating, Diagnosing, Acting, Establishing and Learning) Model; DMAIC (Define, Measure, Analyze, and Control) of Six Sigma; metodologia de transformação TransMeth; and metodologia de transformação do PDP. Three changes projects, SP&SDP institutionalization; implementation of sales phase; and implementation of project planning phase, were developed. The proposed change method provides an appropriated framework to manage changes by a holistic view. It is reported that the companies' collaborators are motivated and feel confident with the changes.

A importância dos sistemas de software segue crescendo para grande parte das organizações. A expansão das funcionalidades viabilizadas com a implantação destes sistemas em produtos manufaturados e a emergência das \"mídias digitais\", que compreendem conteúdo digital, software e múltiplos canais de acesso ao mercado, são exemplos recentes nos quais os sistemas de software assumiram posição central para a estratégia corporativa. Grande parte das pesquisas realizadas sobre software não considera explicitamente os vínculos existentes entre o mercado no qual estas empresas atuam e seus processos organizacionais; como conseqüência, tanto pesquisa como prática em engenharia de software tendem a ser realizadas de forma neutra, e na perspectiva de um desenvolvedor de software, diferentes atividades de desenvolvimento são consideradas como igualmente relevantes para a obtenção dos objetivos corporativos. Este projeto de pesquisa analisa como acontece o alinhamento entre objetivos estratégicos e o processo de desenvolvimento em empresas de software e propõe um método para garantir que o processo de desenvolvimento encontra-se alinhado com os objetivos do negócio. O método inclui a categorização de diferentes companhias de software de acordo com as suas habilidades principais e a customização da técnica Technology Roadmapping para empresas de software. O percurso metodológico desenvolvido para atingir os objetivos propostos não é convencional e envolve diferentes etapas nas quais a recuperação de teorias, de conceitos e de modelos foi mesclada com atividades de pesquisa para o detalhamento, teste e ratificação dos diversos elementos que vêm a constituir o produto acima mencionado. Os resultados obtidos são consistentes com os objetivos propostos e incluem um referencial para análise da indústria de Telecomunicações, um referencial para análise da indústria de software, incorporando questões sobre mercado, objetivos estratégicos, produtos e serviços e processo de desenvolvimento, e um método de alinhamento entre objeticos estratégicos e processo de desenvolvimento em empresas de software. / Software importance is growing fast and consistently for many organizations. The growth of software functionality in manufactured products and the emergence of the digital media, convergent spaces comprehending digital content, software, and multi-channels to the market, are recent examples of organizational changes where software assumed a central position for the corporate strategy. Much of current research about software does not explicitly consider the linkages between the software market and their organizational processes; as a consequence, software engineering practice and research is done in a value-neutral setting, and from a developer point of view, different activities are considered equally important for the achievement of corporate goals. This research project analyzes the alignment between strategic objectives and development process at software companies and presents a method to ensure that the development process is aligned with the corporate capabilities required to exploit future market opportunities. The method includes the categorization of different software companies according to their core capabilities and the customization of the Technology Roadmapping technique for software companies. To achieve the proposed goal it was necessary to develop a different approach, in which theories, concepts and models were tested against empirical initiatives, aiming to validate the different elements that constitute the mentioned result. These obtained results are consistent with the proposed objectives, and include a framework to analyze the telecommunication industry, a framework to analyze the software industry, concerning issues such as market, strategic objectives, products and services and development process, and a method to align strategic objectives and development process at software companies.

Developing a large software system involves many complicated, varied, and inter-dependent tasks, and these tasks are typically implemented using a combination of defined processes, semi-automated tools, and ad hoc practices. Stakeholders in the development process --- including software developers, managers, and customers --- often want to be able to track the actual practices being employed within a project. For example, a customer may wish to be sure that the process is ISO 9000 compliant, a manager may wish to track the amount of testing that has been done in the current iteration, and a developer may wish to determine who has recently been working on a subsystem that has had several major bugs appear in it. However, extracting the software development processes from an existing project is expensive if one must rely upon manual inspection of artifacts and interviews of developers and their managers. Previously, researchers have suggested the live observation and instrumentation of a project to allow for more measurement, but this is costly, invasive, and also requires a live running project. In this work, we propose an approach that we call software process recovery that is based on after-the-fact analysis of various kinds of software development artifacts. We use a variety of supervised and unsupervised techniques from machine learning, topic analysis, natural language processing, and statistics on software repositories such as version control systems, bug trackers, and mailing list archives. We show how we can combine all of these methods to recover process signals that we map back to software development processes such as the Unified Process. The Unified Process has been visualized using a time-line view that shows effort per parallel discipline occurring across time. This visualization is called the Unified Process diagram. We use this diagram as inspiration to produce Recovered Unified Process Views (RUPV) that are a concrete version of this theoretical Unified Process diagram. We then validate these methods using case studies of multiple open source software systems.

Software development is highly dependent on the use of tools. These tools support and automate activities performed in different sub-domains of software development. However, they don&lsquo / t adequately provide or support integration facilities, and act as &amp / #8213 / islands of automation&amp / #8214 / . This restricts their benefits to only specific parts of the process. To reap the benefits of integration, this thesis provides a process modeling based method named PLETIN to identify and implement software development tool integration-tuples. The method aims to present solutions for issues observed in tool integration for software development organizations by delivering an integrated tool set. The proposed solution approach is based on the idea that if there were no integrations between tools at all, users would perform the necessary actions to cooperate different tools. PLETIN is a method for the identification of the candidate integration situations (integration-tuples) from the interactions of users with the tools. These tuples constitute the requirements used to develop integration facilities. The software development process definitions are used as inputs to create process models and provide actual implementations. The research is supported with case-study work to identify the significance of the problems and the applicability of the method as a solution to issues in tool integration.