• Refine Query
  • Source
  • Publication year
  • to
  • Language
  • 110
  • 76
  • 13
  • 8
  • 4
  • 3
  • 2
  • 2
  • 1
  • 1
  • 1
  • 1
  • 1
  • 1
  • Tagged with
  • 257
  • 257
  • 82
  • 81
  • 69
  • 44
  • 40
  • 39
  • 37
  • 37
  • 36
  • 32
  • 28
  • 27
  • 27
  • About
  • The Global ETD Search service is a free service for researchers to find electronic theses and dissertations. This service is provided by the Networked Digital Library of Theses and Dissertations.
    Our metadata is collected from universities around the world. If you manage a university/consortium/country archive and want to be added, details can be found on the NDLTD website.
161

Modelo de gestão do processo de venda e desenvolvimento de software on-demand para MPE\'s / Management model of selling and on-demand software development process

Andrea Padovan Jubileu 16 December 2008 (has links)
A maioria das micro e pequenas empresas (MPEs) de desenvolvimento de software brasileiras são voltadas para o desenvolvimento de software on-demand. Normalmente, essas MPEs têm dificuldades em formalizar um processo de software padrão. O presente trabalho de pesquisa tem por objetivo apresentar uma proposta de integração de modelos/normas de capacidade de processo com modelos de ciclo de vida de software, em um contexto de gestão de processos de negócio. Como resultado, obteve-se o modelo de gestão do processo de venda e desenvolvimento de software on-demand para MPEs (ProcSoftVD - Gestão), composto pelo método de melhoria de processo de software (ProcSoftVD - Melhoria) e pelo modelo de processo de venda e desenvolvimento de software on-demand para MPEs (ProcSoftVD). O método de melhoria de processo de software foi criado a partir de abordagens existentes e complementares, voltadas às MPEs. O ProcSoftVD foi originado com base no framework unified process, possibilitando a visualização do processo em duas perspectivas - fases e áreas de conhecimento, e nos modelos/normas de capacidade de processo CMMI-DEV e ISO/IEC 15504-5, elaborado em um processo iterativo e evolutivo de pesquisa-ação com a participação de duas MPEs. Um diferencial dessa proposta é a consideração de atividades de comercialização do software junto ao processo de desenvolvimento de software, o que auxilia na delimitação do escopo do projeto de desenvolvimento de software para um acordo contratual. Outro diferencial é o detalhamento das atividades do processo por meio de tarefas, sugestão de papéis desempenhados pelos responsáveis das atividades e disponibilização de templates com exemplos para cada um dos artefatos elaborados na execução da atividade. / The majority of the software development micro and small companies are turned to the development of on-demand software. Usually, for these small companies the formalization of a standard process for software development is very difficult. For that reason the goal of this research is to propose an integration of capability processes models/standards within software life cycle models, in a perspective of business process management. The main result of this research is a management model of selling and on-demand software development process, which embraces the software process improvement method and the selling and on-demand software development process model. The software process improvement method was build from complementary and existents tailored approaches for micro and small companies. The selling and on-demand software development process model was created based on the models/standards of process capability CMMI-DEV and ISO/IEC 15504-5 and on the unified process framework, allowing the process view from two perspectives - phases and knowledge areas. The model was elaborated in an iterative and evolutionary action-research process carried out within two micro and small companies. The originality of this proposal is the consideration of software sale activities jointly with software development process, assisting the scope delimitation of a software development project for contractual agreement. Other aspect of this research which makes it distinctive is the detail of the process activities by mean of tasks, suggestions of people roles for each activities and provision of templates with examples for each artifact created during the activities.
162

Qualidade de Produto de Software: uma abordagem baseada no controle da complexidade / Software product quality: an approach based on complexity control

Marcelo Criscuolo 01 April 2008 (has links)
É rara a preocupação com a qualidade de implementação de software. Pode-se observar que as estruturas internas dos softwares são freqüentemente complexas e desorganizadas, especialmente no caso dos softwares que são ditos orientados a objetos. Essa complexidade afeta diretamente a manutenibilidade e a susceptibilidade a erros, dificultando a alteração e a adição de novas funcionalidades aos softwares. As próprias alterações, inerentes aos softwares, os tornam mais complexos, o que agrava o problema. Neste contexto, acredita-se que o controle da complexidade pode levar a produtos de software de melhor qualidade. Assim, trata-se neste trabalho da manutenção preventiva, implementada por meio de inspeções, refatorações e análise de métricas. São estudadas falhas de manutenibilidade em uma amostra de programas orientados a objetos e, a partir dos resultados, são propostos artefatos de apoio para um processo de inspeção de software e modelos para os produtos de trabalho gerados nesse processo. Propõe-se o uso da técnica de leitura PBR (Leitura Baseada em Perspectivas) como uma maneira de se melhorar a detecção de falhas de manutenibilidade. Finalmente, a proposta deste trabalho foi validada por meio de um estudo de caso / The commitment with the quality of software implemetation is rare. It\'s possible to observe that the software internal structures are frequently complex and disorganized, especially when talking about software that is said to be object-oriented. This complexity directly affects maintainability and error proneness, making it difficult to change and to add new functionalities to software. Changes themselves, that are inherent in software, make it more complex, and that makes the problem more serious. In this context, it\'s believed that the control of complexity can lead to better quality software products. Thus, the subject of this work is the preventive maintenance, implemented by means of inspections, refactoring and metric analysis. Maintenance flaws were studied in a sample of object-oriented programs and, based on the results, support artifacts for an inspection process were proposed, along with models of work products for this process. The use of PBR (Perspective-Based Reading) technique is proposed as a means of improving the detection of maintenance flaws. Finally, the proposal of this work is validated through a case study
163

Aplicação de métricas de software na predição de características físicas de software embarcado / Application of software quality metrics to predict physical characteristics of embedded systems

Corrêa, Ulisses Brisolara January 2011 (has links)
A complexidade dos dispositivos embarcados propõe novos desafios para o desenvolvimento de software embarcado, além das tradicionais restrições físicas. Então, a avaliação da qualidade do software embarcado e seu impacto nessas propriedades tradicionais torna-se mais importante. Conceitos como reúso abstração, coesão, acoplamento, entre outros atributos de software têm sido usados como métricas de qualidade no domínio da engenharia de software. No entanto, elas não têm sido usadas no domínio do software embarcado. No desenvolvimento de sistemas embarcados outro conjunto de ferramentas é usado para estimar as propriedades físicas, tais como: consumo de energia, ocupação de memória e desempenho. Essas ferramentas geralmente envolvem custosos processos de síntese e simulação. Nos complexos dispositivos embarcados atuais deve-se confiar em ferramentas que possam ajudar na exploração do espaço de projeto ainda nos níveis mais altos de abstração, identificando a solução que representa a melhor estratégia de projeto em termos da qualidade de software, enquanto, simultaneamente, atenda aos requisitos físicos. Neste trabalho é apresentada uma análise da correlação entre métricas de qualidade de software, que podem ser extraídas antes do sistema ser sintetizado, e as métricas físicas do software embarcado. Usando uma rede neural nós investigamos o uso dessas correlações para predizer o impacto que uma determinada modificação no software trará às métricas físicas do mesmo software. Esta estimativa pode ser usada para guiar decisões em direção a melhoria das propriedades físicas dos sistemas embarcados, além de manter um equilíbrio em relação às métricas de software. / The complexity of embedded devices poses new challenges to embedded software development in addition to the traditional physical requirements. Therefore, the evaluation of the quality of embedded software and its impact on these traditional properties becomes increasingly relevant. Concepts such as reuse, abstraction, cohesion, coupling, and other software attributes have been used as quality metrics in the software engineering domain. However, they have not been used in the embedded software domain. In embedded systems development, another set of tools is used to estimate physical properties such as power consumption, memory footprint, and performance. These tools usually require costly synthesis-and-simulation design cycles. In current complex embedded devices, one must rely on tools that can help design space exploration at the highest possible level, identifying a solution that represents the best design strategy in terms of software quality, while simultaneously meeting physical requirements. We present an analysis of the cross-correlation between software quality metrics, which can be extracted before the final system is synthesized, and physical metrics for embedded software. Using a neural network, we investigate the use of these cross-correlations to predict the impact that a given modification on the software solution will have on embedded software physical metrics. This estimation can be used to guide design decisions towards improving physical properties of embedded systems, while maintaining an adequate trade-off regarding software quality.
164

Analise comparativa de metodologias para o gerenciamento de projetos de desenvolvimento de software / Comparative analysis of software development project management methodologies

Barbosa, Anderson Luiz 30 June 2006 (has links)
Orientador: Leonardo de Souza Mendes / Dissertação (mestrado) - Universidade Estadual de Campinas, Faculdade de Engenharia Eletrica e de Computação / Made available in DSpace on 2018-08-07T08:44:16Z (GMT). No. of bitstreams: 1 Barbosa_AndersonLuiz_M.pdf: 1069956 bytes, checksum: 60ef78a0bf936295dc98292f61f2a987 (MD5) Previous issue date: 2006 / Resumo: As empresas ao redor do mundo começam a adotar, de forma mais intensa, os padrões internacionais de gerenciamento de projetos (como o PMBoK Guide e a ISO 10006); profissionais são capacitados para atuarem como gerentes de projetos nas mais diversas áreas de atividades. Mundialmente existe a preocupação com o gerenciamento adequado desses projetos a fim de garantir o atendimento às expectativas dos envolvidos e a otimização dos recursos alocados. Na área de software, as preocupações são cada vez maiores com relação a custos, prazos e qualidade em projetos de desenvolvimento de sistemas, forçando um repensar nas práticas até então utilizadas para o gerenciamento destes processos. O presente trabalho aborda as técnicas de engenharia de software que tradicionalmente são aplicadas ao desenvolvimento de projetos, constatando que, na maior parte das vezes, são enfocados apenas os aspectos técnicos; apresenta também uma descrição dos padrões de qualidade de uso genérico (como as normas ISO 9000) que passam a ser utilizados por empresas que desenvolvem software, e descreve a utilização de modelos de qualidade especificamente desenvolvidos para informática, como o CMM/CMMI e o PSP. A partir dos resultados da comparação entre os modelos de qualidade e os modelos de gerenciamento de projetos, é apresentada uma proposta para otimização do gerenciamento de processos de desenvolvimento de software, descrevendo a contribuição de cada um destes modelos, além das adaptações necessárias a fim de contemplar os aspectos específicos de software. Essa proposta é validada com um estudo de caso em um laboratório de desenvolvimento de projetos na área de telecomunicações com ênfase no emprego e desenvolvimento de software / Abstract: International standards of project management (like PMBoK Guide and ISO 10006) have been used by companies around the world; professionals have been qualified to exercise the project management function in most areas of activities. A global concern exists for the appropriate administration of these several projects in order to achieve the expectations of those involved. On the software area, the concern is bigger when related to costs, time and quality in software development. This forces to rethink the practices used on the administration of these processes. This work addresses the techniques of software engineering that are being applied to the development of projects, verifying that most of the time spent is just focused on the technical aspects; it also presents a description of the patterns of quality for generic use (as the norms ISO 9000) that also have been used by companies that develop software, and it specifically describes the use of quality models developed for computer science, like CMM/CMMI and PSP. A proposal is presented for optimizing the management of software development processes, describing the contribution provided by each one of these models, together with the necessary adaptations in order to contemplate the specific aspects of software. The proposal is validate with a case study in a laboratory of telecommunications projects with a real software development project / Mestrado / Telecomunicações e Telemática / Mestre em Engenharia Elétrica
165

Uma pesquisa sobre a influência dos aspectos humanos em programas de melhoria de processo de software / A research about the influence of human aspects in software process improvement programs

Santos, Davi Viana dos 21 July 2011 (has links)
Made available in DSpace on 2015-04-11T14:03:21Z (GMT). No. of bitstreams: 1 Davi Viana dos Santos.pdf: 1879718 bytes, checksum: c5d0d7175f9d9c94ab6c07ac4434fa41 (MD5) Previous issue date: 2011-07-21 / CNPq - Conselho Nacional de Desenvolvimento Científico e Tecnológico / Several factors can influence the success of Software Process Improvement (SPI) programs. Results from previous research have shown that human and social aspects influence these programs in different ways. For this reason, it is important to analyze the human aspects involved on SPI programs to gain a better understanding about their influence on such programs. This thesis presents a research about human aspects influences in software process improvement. In this work, we analyze the major findings of a qualitative research conducted in three different phases to analyze which factors were most influential from view-point of the professionals working in the organizations. Our ultimate goal is to deepen the understanding about how human aspects can influence a SPI program in order to help in the success of future SPI implementation. / Diversos fatores podem influenciar o sucesso de um programa de Melhoria de Processo de Software (MPS). Os resultados de pesquisas anteriores mostram que vários desses fatores são de natureza humana e social. Por esta razão, é importante analisar os aspectos humanos envolvidos a fim de obter uma maior compreensão da influência destes em um programa MPS. Esta dissertação apresenta uma pesquisa sobre a influência dos aspectos humanos em Programas de MPS. Neste trabalho são analisados os principais resultados de uma pesquisa qualitativa conduzida em três diferentes fases para analisar quais fatores tiveram maior influência do ponto de vista dos colaboradores das organizações. O objetivo final é aprofundar a compreensão dos aspectos humanos que podem influenciar um programa de MPS com a finalidade de auxiliar no sucesso de futuros programas de melhoria.
166

Dimensões de qualidade em ambientes virtuais de aprendizagem / Quality dimensions in virtual learning environments

Silvio Carvalho Neto 15 December 2009 (has links)
O desenvolvimento comercial da internet possibilitou o surgimento de sistemas de informação que se apoiam no uso da world wide web como plataforma. Esses sistemas baseados na web (web-based systems) têm aplicações em diversas áreas e setores econômicos. No ramo educacional, eles têm sido aplicados como base para os processos de ensino e aprendizagem via computador (e-learning) e são, comumente, denominados de Ambientes Virtuais de Aprendizagem (AVA). Os AVAs podem ser utilizados tanto para o ensino exclusivamente a distância quanto como apoio ao ensino presencial. O presente trabalho tem como objeto de investigação justamente o emprego de ambientes virtuais como tecnologia de apoio ao ensino presencial tradicional dado em sala de aula em cursos de graduação do ensino superior. O crescente uso de AVAs para tal finalidade leva ao questionamento de quais são as dimensões e características de qualidade destes ambientes e como estas dimensões estão associadas com os seus efeitos, quais sejam, a satisfação, o uso e os benefícios percebidos pelos usuários de tais sistemas? Desta forma, o trabalho tem como objetivo identificar as dimensões de qualidade em AVAs, por meio do estabelecimento de um modelo teórico que evidencie quais são os atributos determinantes em relação à qualidade em ambientes virtuais de ensino e quais são os efeitos e os impactos individuais em torno dos usuários discentes. Para tanto, são realizadas duas pesquisas de campo. A primeira é descritiva-explicativa, de abordagem quantitativa, com o emprego de Modelagem de Equações Estruturais, como método de análise e delineamento da pesquisa. Esta pesquisa foi feita com discentes usuários de um ambiente virtual disponibilizado por uma IES e teve como objetivo a elaboração de um modelo de relações de qualidade em AVAs. A segunda pesquisa consiste em um estudo com abordagem essencialmente descritiva, que tem como objetivo classificar quais são as características de relevância nos AVAs, de acordo com o Modelo Kano de classificação de requisitos. Os principais resultados apontam que a qualidade da informação e a qualidade do sistema influenciam na satisfação e nos benefícios percebidos pelos usuários dos AVAs e que as características destas dimensões são consideradas mais significativas do que as funcionalidades disponíveis nos referidos sistemas. / The commercial development of the internet enabled the birth of information systems that rely on the use of the world wide web as a platform. These web-based systems have applications in various fields and economic sectors. In the education sector, they have been used as basis for computer teaching and learning processes (e-learning) and are commonly called Virtual Learning Environments (VLE). These VLEs can be used both for distance teaching exclusively and as support for students in traditional presential classes. This work investigates the virtual environments use as support technology for students in traditional classroom undergraduate courses in higher education. The growing use of VLEs for this purpose raises the following questions: what are the dimensions and quality characteristics of these environments and how are these dimensions associated with their effects, satisfaction, use, and net benefits perceived by users of such systems? Thus, the study aims to identify the VLEs quality dimensions, through the establishment of a theoretical model showing what the relevant VLE dimensions relating to education quality are and what the effects and individuals impacts are for user-learners. To this end, two researches were conducted. The first one was descriptive-explanatory, with a quantitative approach, using Structural Equation Modeling as analysis method and research design. This research was made with students that use a VLE and had the purpose to elaborate a VLE quality relationship model. The second study is essentially descriptive, and aims to classify which features are most relevant in VLEs, according to the Kano´s Model requirements classification. The main findings indicate that the information quality and system quality influence the satisfaction and net benefits perceived by VLEs users and characteristics of these dimensions are considered more important than the functionality features available in such systems.
167

The impact of maturity, scale and distribution on software quality : An industrial case study

Vaka, Kranthi, Narla, Karthik January 2017 (has links)
Context. In this ever-changing world of software development, the process of organizations adopting distributed development is gaining prominence. Implementing various development processes in such distributed environment is giving rise to numerous issues which affects the quality of the product. These issues could be due to the involvement of architects across national borders during the process of development. In this research, the focus is to improve software quality by addressing the impact of maturity and scale between teams and its affect on code review process. Further to identify the issues behind the distribution between teams separated by geographical, temporal and cultural distances. Objectives. The main objective of this research is to identify how different factors such as maturity on quality of deliverables, scale and distribution that impacts the code review process affecting software quality. Based on code review comments in data set, the factors that were examined in this research are evolvability of defects and difference in the quality of software developed by mature and immature teams within code review process. Later on, the issues related to the impact of geographical, temporal and cultural distances on the type of defects revealed during distributed development are identified. Methods. To achieve these objectives, a case study was conducted at Ericsson. A mixed approach has been chosen that includes, archival data and semi-structured interviews to gather useful data for this research. Archival data is one of the data collection method used for reviewing comments in data set and gather quantitative results for the study. We employed approaches such as descriptive statistics, hypothesis testing, and graphical representation to analyze data. Moreover, to strengthen these results, semi-structured group interview is conducted to triangulate the data and collect additional insights about code review process in large scale organizations. Results. By conducting this research, it is inferred that teams with a lower level of maturity produce more number of defects. It was observed that 35.11% functional, 59.03% maintainability, 0.11% compatibility, 0.028% security, 0.73% reliability, 4.96% performance efficiency, 0.014% portability of defects were found from archival data. Majority of defects were of functional and maintainability type, which impacts software quality in distributed environment. In addition to the above-mentioned results, other findings are related to evolvability of defects within immature teams which shows that there is no particular trend in increase or decrease in number of defects. Issues that occur due to distribution between teams are found out in this research. The overall results of this study are to suggest the impact of maturity and scale on software quality by making numerical assumptions and validating these finding with interviews. Interviews are also used to inquire information about the issues from dataset related to the impact of global software engineering (GSE) distances on code review process. Conclusions. At the end of this research it is concluded that in these type of projects, immature teams produce more number of defects than mature teams. This is because when large-scale projects are distributed globally, it is always harder to share and acquire knowledge between teams, increase group learning and mentor teams located in immature sites. Immature developers have problems of understanding the structure of code, new architects need to acquire knowledge on the scope and real time issues for improving quality of software. Using results presented in this thesis, researchers can find new gaps easily to extend the research on various influences on code review process in distributed environment.
168

Comparison between C# and Java : in implementation of a university desktop app

Sabet, Shahrooz January 2012 (has links)
This thesis is about comparison between C# and Java in implementation of a university desktop application. In .Net world the prominent IDE is MS Visual studio and DB is MS SQL server. In Java domain we have several IDEs and techniques to approach the problem. The knowledge to choose between these techniques to use is as much as important if a programmer can gain it, he can apply it in many other software engineering domains like a personal management system, library system, etc.     Therefore the importance of a descriptive and applied experience is showing itself up. This thesis has started with a discussion to choose NetBeans IDE and application definition, and use case modeling then it goes through comparison and implementation part. The comparison will go in depth for each use case in this project in its implementation in C# and Java and see which techniques are used. This includes comparison between these two apps in Software quality factors.
169

[en] MANAGING SOFTWARE PROJECTS USING AGILE METHODOLOGIES: A CASE STUDY / [pt] GERENCIAMENTO E PLANEJAMENTO DE PROJETOS DE SOFTWARE USANDO METODOLOGIAS ÁGEIS: UM ESTUDO DE CASO

DANIELA MILAGROS QUENAYA MENDOZA 20 June 2011 (has links)
[pt] Hoje em dia, entregar software com qualidade, nos prazos previstos e respeitando os custos é um grande diferencial para empresas dedicadas a esta atividade. A constante procura de produtividade e qualidade em projetos de software originou diversos modelos de gerenciamento que procuram auxiliar esta área com metodologias e formas de organização de trabalho. O modelo mais conhecido na área de gerenciamento de software é o Modelo em Cascata, caracterizado pela rigidez e fases bem definidas nos processos. Uma vez encontrados problemas com os modelos rígidos surgiram como alternativa de gerenciamento os métodos ágeis, caracterizados pela agilidade, iteratividade e adaptabilidade para diversos projetos. Diante isto o presente trabalho analisa o problema do gerenciamento de projetos de desenvolvimento de software, e propõe um modelo de referencia de gerenciamento de projetos de software considerando a abordagem tradicional de gerenciamento de projetos assim como a abordagem ágil. A pesquisa analisa a compatibilidade das metodologias ágeis com o Capability Maturity Model Integration (CMMI) que é um modelo de maturidade nos processos de desenvolvimento de software. Finalmente a pesquisa apresenta um estudo de caso, que permitiu observar as forças e fraquezas dos métodos estudados, concluindo que as praticas ágeis contribuem na melhoria e gerenciamento de projetos de software. / [en] Today, delivering quality software, on time and respecting costs is a key differentiator for companies dedicated to this activity. The constant search for productivity and quality in software project management led to several models that seek to help this area with methods and forms of work organization. The best known model in the area of software management is the Waterfall Model, characterized by stiffness and well-defined phases in the process. Once found problems with rigid models have emerged as alternative management of agile methods, characterized by agility, and adaptability to various iterative projects. Given that this paper analyzes the problem of managing software development projects, and proposes a reference model for managing software projects considering the traditional approach of project management as well as the agile approach. The research examines the compatibility of agile methodologies with the Capability Maturity Model Integration (CMMI) is a maturity model in software development processes. Finally the research presents a case study, which allowed us to observe the strengths and weaknesses of the methods studied, concluding that such practices contribute to improved and agile project management software.
170

Podpora testování v Microsoft Visual Studio / Software testing in Microsoft Visual Studio

Padevět, Daniel January 2007 (has links)
In software development process, there can be misunderstandings, communication problems between individual members of the development team and mistakes when writing code or designing applications. These problems need to be resolved before the application is released into the production environment. To discover these errors it is necessary to properly test the software product. All these activities are engaged in discipline called Software Quality Assurance (SQA), which is an integral part of the software development process. The thesis discusses this discipline and procedures for software testing using the Microsoft Visual Studio 2008. The main objective of this work is to create comprehensive methodology for automated testing of web and Windows applications in Microsoft Visual Studio and to verify that procedures in practice. The reader will learn the theoretical basis of software testing at the beginning of the thesis. In next chapter, there are described various features that Microsoft Visual Studio 2008 offers for software testing. Following chapter describes the applications testing in IBM Rational Functional Tester, which is suitable for Windows applications testing (Microsoft Visual Studio 2008 does not support this kind of tests). In other part of the work -- Case Study -- the reader will learn web and Windows applications testing. Case study can serve as a basis for further methodological manual for teams engaged in software testing. The usage of instruments for testing is explained in real examples. At the end of the work there are set out recommendations for the team collaboration using Microsoft Team Foundation Server, and there are also compared the testing instruments and reviewed functions that will come up with Microsoft Visual Studio 2010.

Page generated in 0.0471 seconds