• Refine Query
  • Source
  • Publication year
  • to
  • Language
  • 3
  • 1
  • 1
  • 1
  • Tagged with
  • 6
  • 6
  • 6
  • 3
  • 3
  • 3
  • 2
  • 2
  • 2
  • 1
  • 1
  • 1
  • 1
  • 1
  • 1
  • 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.
1

[en] RUP-3C-GROUPWARE: GROUPWARE DEVELOPMENT PROCESS BASED ON THE 3C COLLABORATION MODEL / [pt] RUP-3C-GROUPWARE: UM PROCESSO DE DESENVOLVIMENTO DE GROUPWARE BASEADO NO MODELO 3C DE COLABORAÇÃO

MARIANO GOMES PIMENTEL 16 October 2006 (has links)
[pt] Nesta tese é proposto um processo de desenvolvimento de groupware (software para dar suporte ao trabalho em grupo). O processo proposto é resultado de oito anos de experiência com o desenvolvimento dos serviços do ambiente AulaNet, e mais especificamente, dos cinco anos de pesquisa e desenvolvimento de versões do Mediated Chat. As boas práticas aprendidas ao longo destas experiências foram incorporadas no processo: uso do Modelo 3C de Colaboração para guiar o desenvolvimento de groupware, desenvolvimento evolucionário focando um problema por versão num processo investigativo, e desenvolvimento baseado em componentes e orientado ao reuso. O processo aqui proposto, denominado RUP-3C-Groupware consiste na extensão do RUP, Rational Unified Process, na qual foram incorporadas as boas práticas aprendidas. Na tese são apresentados os fluxos de atividades e os artefatos estendidos ou elaborados para o RUP-3C-Groupware. Para investigar o processo proposto, foi realizado um Estudo de Caso onde alunos de Engenheira de Software executaram algumas das atividades produzindo alguns artefatos-chave. Do estudo de caso foram obtidos indícios sobre a repetitividade do processo e de sua adequação para o desenvolvimento de groupware. / [en] A groupware (group work support software) development process is proposed in this thesis. This process is the result of eight years of experience with the development of services for the AulaNet environment, and more specifically of five years researching and developing Mediated Chat tool versions. The good practices learned through these activities were incorporated into the process proposed: the use of the 3C Collaboration Model to guide groupware development, evolutionary development focusing on a single problem per version in an investigative process, and reuse-oriented component- based development. These practices were used to guide the specification of the RUP, Rational Unified Process, resulting in the new process, namely the RUP-3C- Groupware. The new or extended RUP-3C-Groupware workflows and artifacts are presented. This process was investigated through a case-study in which Software Engineering students performed certain activities producing a few key- artifacts. From this case-study some indications regarding process repetitiveness and its suitability to groupware development were obtained.
2

IMPLEMENTING SOFTWARE PROCESS IMPROVEMENTS IN THE T&E COMMUNITY

Posey, Chlotia 10 1900 (has links)
International Telemetering Conference Proceedings / October 23-26, 2000 / Town & Country Hotel and Conference Center, San Diego, California / The Capability Maturity Model (CMM) developed by the Software Engineering Institute is widely promoted as a method to help decrease the volume of error riddled and late software projects. Because of the projected benefits, the 96th Communications Group/SC (SC) at Eglin Air Force Base began an intensive software process improvement effort in late 1997. This effort was rewarded in September 1999 when the group achieved a CMM Level 2 software rating on its first attempt. As of December 1999, 68% of assessed organizations remained at Level 1 on their first or second assessment. The SC success was not only obtained on its first attempt, but also 11 months ahead of the industry standard. The Level 2 rating was accomplished in the volatile environment needed to support the test and evaluation mission. This environment includes frequent requirement changes, short notice modifications, and externally driven schedules. One reason this milestone was possible is close and direct involvement by management. This paper will present additional factors to implementing a successful software process improvement effort.
3

Software development methodology in a Green IT environment / Méthodologie de développement de logiciels dans un environnement informatiquement vert

Acar, Hayri 23 November 2017 (has links)
Le nombre de périphériques mobiles (smartphone, tablette, ordinateur portable, etc.) et les internautes augmentent continuellement. En raison de l'accessibilité du cloud computing, de l'Internet et de l'Internet des Objets (IdO), les utilisateurs utilisent de plus en plus d'applications logicielles qui provoquent un effet croissant sur les émissions de gaz à effet de serre. Ainsi, les TIC (Technologies de l'Information et de la Communication) sont responsables d'environ 2% des émissions mondiales de gaz à effet de serre qui sont équivalentes à celles émises par l'industrie aérienne. Selon des rapports récents, le Groupe d'experts Intergouvernemental sur l'Evolution du Climat (GIEC), les émissions de CO2 dus aux TIC augmentent rapidement. Néanmoins, les TIC, en permettant de résoudre des problèmes complexes dans d'autres secteurs, peuvent grandement et facilement participer pour réduire une partie importante des 98% restants des émissions mondiales de CO2. L'utilisation du logiciel implique des opérations matérielles qui sont physiquement responsables de la consommation d'énergie. Par conséquent, le logiciel est indirectement impliqué dans la consommation d'énergie. Ainsi, nous devons réduire la consommation d'énergie du logiciel tout en conservant les mêmes fonctionnalités pour le logiciel afin de créer des logiciels durables et verts. Premièrement, dans ce travail de thèse, nous définissons les termes «durable et vert» dans le domaine du logiciel afin de créer des logiciels respectant les critères de ces termes. Pour créer un produit logiciel, nous devons suivre un processus d'ingénierie logicielle. Par conséquent, nous décrivons des critères durables et verts à respecter après chaque étape de ce processus afin d'établir un processus d'ingénierie logicielle durable et écologique. En particulier, nous nous concentrons sur l'estimation de la consommation d'énergie du logiciel. De nombreux travaux ont essayé de proposer divers outils pour estimer la consommation d'énergie due aux logiciels afin de réduire l'empreinte carbone. Pendant longtemps, les solutions proposées se sont concentrées uniquement sur la conception du matériel, mais ces dernières années, les aspects logiciels sont également devenus importants. Malheureusement, ces études, dans la plupart des cas, ne considèrent que le CPU et négligent tous les autres composants. Les modèles de consommation d'énergie existants doivent être améliorés en tenant compte de plus de composants susceptibles de consommer de l'énergie pendant l'exécution d'une application. L'écriture d'un logiciel durable, performant et vert nécessite de comprendre le comportement de consommation d'énergie d'un programme informatique. L'un des avantages est que les développeurs, en améliorant leurs implémentations du code source, optimiseront la consommation d'énergie du logiciel. De plus, il existe un manque d'outil d'analyse pour surveiller dynamiquement la consommation d'énergie du code source de plusieurs composants. Ainsi, nous proposons GMTEEC (Méthodologie Générique d'Outil pour Estimer la Consommation Energétique) qui se compose de quatre couches aidant et guidant la construction d'un outil permettant d'estimer la consommation énergétique d'un logiciel. Ainsi, dans notre travail, en respectant les couches de GMTEEC, nous créons TEEC (Outil pour Estimer la Consommation Energétique) qui repose sur une formule mathématique établie pour chaque composant (CPU, mémoire, disque dur, réseau) susceptible de consommer de l'énergie afin d'estimer la consommation totale d'énergie du logiciel composée de la somme de chaque consommation d'énergie par composant. De plus, nous ajoutons à TEEC la capacité de localiser dynamiquement les points chauds qui sont les parties du code source consommant la plus grande quantité d'énergie afin d'aider et guider les développeurs à optimiser leur code source et à créer des logiciels efficaces, durables et verts... [etc] / The number of mobile devices (smartphone, tablet, laptop, etc.) and Internet users are continually increasing. Due to the accessibility provided by cloud computing, Internet and Internet of Things (IoT), users use more and more software applications which cause an increasing effect on gas emission. Thus, ICT (Information and Communication Technologies) is responsible of around 2% worldwide greenhouse gas emissions which is equivalent of that emitted by the airline industry. According to recent reports, the Intergovernmental Panel on Climate Change (IPCC), CO2 emissions due to ICT are increasing widely. Nevertheless, ICT, in allowing to solve complex problems in other sectors, can greatly and easily participate to reduce significant portion of the remaining 98% of global CO2 emissions. The use of software implies hardware operations which are physically responsible of energy consumption. Consequently, software is indirectly involved in the energy consumption. Thus, we need to reduce software energy consumption while maintaining the same functionalities for the software in order to build sustainable and green software. Firstly, in this thesis work, we define the terms sustainable and green in the area of software development. To build a software product, we need to follow a software engineering process. Hence, we define and describe sustainable and green criteria to be respected after each step of this process in order to establish a sustainable and green software engineering process. Then, we focus on the software energy consumption estimation. Many research works tried to propose various tools to estimate the energy consumption due to software in order to reduce carbon footprint. Unfortunately, these studies, in the majority of cases, consider only the CPU and neglects all others components. Existing power consumption methodologies need to be improved by taking into account more components susceptible to consume energy during runtime of an application. Writing sustainable, power efficient and green software necessitates to understand the power consumption behavior of a computer program. One of the benefits is the fact that developers, by improving their source code implementations, will optimize software power consumption. Moreover, there is a lack of analyzing tool to dynamically monitor source code energy consumption of several components. Thus, we propose GMTEEC (Generic Methodology of a Tool to Estimate Energy Consumption) which is composed of four layers assisting developers to build a tool estimating the software power consumption. Hence, in our work, respecting the layers of GMTEEC, we develop TEEC (Tool to Estimate Energy Consumption) which is based on mathematical formula established for each component (CPU, memory, hard disk, network) in order to estimate the total software energy consumption. Moreover, we add in TEEC the capacity to locate dynamically the hotpoints which are the parts of source code consuming the greater amount of energy in order to help and guide developers to optimize their source code and build efficient, sustainable and green software. We performed a variety of experiments to validate the accuracy and quality of the sustainable and green software engineering process and TEEC. The results demonstrate the possibility to save significant quantity of energy and time at limited costs with an important positive impact on environment
4

[en] USING SOFTWARE ENGINEERING CONCEPTS TO DEFINE SOFTWARE DEVELOPMENT PROCESSES / [pt] APLICAÇÃO DA ANÁLISE DE SISTEMAS À DEFINIÇÃO DE PROCESSOS DE DESENVOLVIMENTO DE SOFTWARE

GLORIA MARIA DE PAULA OLIVEIRA 25 August 2008 (has links)
[pt] A qualidade de um produto de software depende fortemente da qualidade do processo de software utilizado em seu desenvolvimento. Para auxiliar na definição de um processo de qualidade, existem diversos modelos de processo, modelos de maturidade e normas de qualidade. Entretanto, a tarefa de elaborar ou melhorar o processo de desenvolvimento de sistemas pode se tornar árdua devido à grande quantidade de informações disponíveis e decisões a serem tomadas. Outro grande problema é o risco de definição de um processo que não seja eficaz, ou seja, não melhore a qualidade dos sistemas ou somente aumente a burocracia no desenvolvimento. Esta dissertação apresenta uma abordagem para definição de processos de desenvolvimento de sistemas baseada nos conceitos da análise de sistemas, ressaltando a analogia existente entre a elaboração de um processo e de um software. Uma das principais características da abordagem é o enfoque na área de Gerência de Riscos, visando o controle dos riscos identificados na definição do processo bem como os possíveis riscos na execução do processo de desenvolvimento. / [en] Software quality depends heavily on the quality of the process used to develop it. In order to assist the definition of an adequate process, there are several process models, maturity models and quality standards. However, creating or improving a software development process may be tough due to the large amount of available information and decisions that have to be made. Another central problem is the risk of defining an ineffective process, that is, one that increases the bureaucracy but doesn`t improve the quality of the systems developed with its support. This dissertation presents an approach for defining software development processes based on the concepts of system analysis, based on the analogy between software and process elaboration. One of the most important attributes of this approach is the focus on Risk Management, considering the identified risks in the process definition as well the possible risks during software process execution.
5

Dokumentace procesů / Process Documentation

Dostalík, Martin Unknown Date (has links)
The goal of this project is the identification with management, analysis and documentation of processes which are used in software development and creating prototype which support these processes. It explains why is important to create new working processes, measure their efficiency and improve them subsequently. Next, it describes the methods which help with the integration of these processes at work and, manage them, especially the Rational Unified Process from the IBM company. Then, I describe the ways how to develop www applications and, consequently, how to work with these applications. The thesis also involves the specification of the requirements and the scheme for the program support application of the process documentation and the description of this application. Another part of the thesis is the system in the active web side form serving to the utilization of a process library in the software projects developing.
6

[en] A FRAMEWORK FOR SOFTWARE ENGINEERING PROCESS REPRESENTATION AND ANALYSIS / [pt] UM FRAMEWORK PARA A REPRESENTAÇÃO E ANÁLISE DE PROCESSOS DE SOFTWARE

LEANDRO RIBEIRO DAFLON 16 August 2004 (has links)
[pt] Diversas organizações buscam por padrões e guias de trabalho para atingir um processo de desenvolvimento maduro. Entretanto, mudanças e evoluções no negócio e na tecnologia implicam constantemente em mudanças e evoluções no processo. Esta dissertação propõe um framework que permite as organizações definirem e analisarem seus processos de desenvolvimento de software no contexto da organização ou projeto. Dessa forma, integração, alteração e evoluções do processo são facilitadas. A definição de um processo está baseada no conceito de Unidades de Processo. As Unidades de Processo representam blocos de construção utilizados na elaboração de novos modelos de processo, podendo utilizar partes de modelos de processos existentes ou não. A análise do processo é baseada em normas de qualidade ou modelos de maturidade, como SW-CMM, CMMI, ISO 12207. / [en] Many organizations search for standards and guidance to achieve a mature process. However, change and evolution of business and technology imply constant change and evolution of development processes. In this dissertation we propose a framework that offers an infrastructure allowing organizations to define and analyze software engineering process at organization level or project level. Besides that, it facilitates integration, change and process evolution. The definition of a process is based on a concept Process Units. These represent building blocks for tailoring integrated development processes, by reusing or not parts of existing process models. The process analysis is based on quality standards or maturity models, such as SW-CMM, CMMI, ISO 12207.

Page generated in 0.0808 seconds