This study has   focused on system development approaches and system development   methodologies. The purpose of the study has been to present a view on the   current situation of different development approaches (agile, traditional,   iterative and hybrid) and methodologies by highlighting the situation from a   number of perspectives. Questions that are answered are: which system   development approaches and methodologies that can be said to be most   frequently used based on the respondents, if the mentioned approaches can be   given certain characteristics based on a selection of factors and the   respondents' attitude towards the approach they practice. The study has been   conducted as a survey where the answers have been obtained via social media.   The result shows that agile methodologies dominate and that they are often   included in various forms of hybrid and agile approaches. Furthermore, it has   not been possible to create an in-depth knowledge of the approaches based on   the selected factors. Finally, it is noted that project members who practice   an agile approach have a great confidence in the approach and have a strong   conviction that it contributes to increase the quality of the software.

Num curto período de tempo, a Web tornou-se o aspecto central de muitas aplicações em diferentes áreas. Rapidamente, cresceu e diversificou seu uso, e diversos setores de negócio realizam suas operações no ambiente da Web. Entretanto, à medida que cresce a extensão de uso de aplicações Web, que se tornam mais complexas, aumenta a preocupação com a maneira como as aplicações são desenvolvidas. Freqüentemente, a abordagem de desenvolvimento é ad hoc, desprovida de técnicas sistemáticas e de metodologias sólidas, resultando em aplicações de baixa qualidade. A fim de alcançar aplicações Web bem sucedidas, há a necessidade de melhores princípios de esenvolvimento que devem considerar as características especiais dessas aplicações. Dessa forma, o objetivo do trabalho é propor Processos de Apoio ao desenvolvimento das aplicações Web, baseando-se nas características dessas aplicações e nos Processos de Apoio da ISO/IEC 12207. Os processos de Apoio visam auxiliar outros processos do ciclo de vida da aplicação a alcançar produtos de qualidade e o sucesso do projeto / Within a short period, the Web has become the central aspect of many applications in different areas. Rapidly, it has grown and diversified in its scope and use. Diverse business sectors improve their operations in Web environment. The Web application has become more complex and it has increased the concern with the way the application is developed. Frequently, the development is ad hoc, unprovide of systematic methods and methodologies, resulting in poor quality applications. In order to have successful Web applications, it is necessary better principles of development that have to consider the characteristics of these applications. The objective of this work is to propose Supporting Process for development Web applications, based on the characteristics of these applications and the Supporting Process of ISO/IEC 12207. The Supporting processes aim to assist other processes of the cycle of life of the application to reach quality products and successful projects

Aplicações sensíveis a contexto utilizam informações de contexto para fornecer serviços adaptados a usuários na realização de suas tarefas. Informação de contexto é qualquer informação considerada relevante para caracterizar entidades de uma interação usuário-computador, como a identidade e a localização de usuários. Esta tese trata a carência de uma abordagem que considere, em termos de processo de software, a complexidade de desenvolvimento de software sensível a contexto. O problema em questão é tratado por meio de três linhas de investigação: modelagem de informação contextual, serviços para tratamento de informação contextual e processo de software para computação sensível a contexto. As contribuições desta tese incluem: (i) o processo de software POCAp (Process for Ontological Context-aware Applications) para apoiar a construção de aplicações sensíveis a contexto baseadas em ontologias; (ii) o modelo de informações de contexto SeCoM (Semantic Context Model) baseado em ontologias e em padrões da Web Semântica; (iii) a infra-estrutura de serviços configuráveis SCK (Semantic Context Kernel) para interpretar informações de contexto apoiadas por modelos ontológicos de informação contextual, como o modelo SeCoM; (iv) uma instanciação do processo POCAp correspondente à extensão de uma aplicação com informações de contexto apoiadas pelo modelo SeCoM, e sua integração com serviços da infra-estrutura SCK; e (v) a identificação de questões de projeto relacionadas à inferência sobre informação contextual ontológica / In order to provide adaptive services according to users? tasks, context-aware applications exploit context information, which is any information used to characterize entities of a user-computer interaction such as user identity or user location. This thesis deals with the lack of a software process-based approach to supporting the inherent complexity of developing context-aware systems. The work reported in this thesis followed three main lines of investigation: context information modeling, services for processing context information, and a software process for context-aware computing. The contributions of this thesis include: (i) the Process for Ontological Context-aware Applications (POCAp) to support the development of context-aware applications based on ontologies; (ii) the Semantic Context Model (SeCoM) based on Semantic Web standards and ontologies; (iii) the Semantic Context Kernel (SCK) services infrastructure for interpreting ontological context information models such as the SeCoM model; (iv) an implementation of the POCAp process for the extension of an application with context information based on the SeCoM model, and its integration with services of the SCK infrastructure; and (v) the identification of design issues related to the inference over ontology-based context information

Submitted by Mario BC (mario@bc.ufrpe.br) on 2017-02-08T14:12:20Z No. of bitstreams: 1 Breno Leonardo Gomes de Menezes Araujo.pdf: 3596044 bytes, checksum: ba04fae7f1924573f14255f9d5e2c44a (MD5) / Made available in DSpace on 2017-02-08T14:12:20Z (GMT). No. of bitstreams: 1 Breno Leonardo Gomes de Menezes Araujo.pdf: 3596044 bytes, checksum: ba04fae7f1924573f14255f9d5e2c44a (MD5) Previous issue date: 2015-07-08 / Innovation driven approaches prescribe principles, practices and tools that are used to develop innovative products or services. Introducing elements of these innovation-driven approaches in the context of software processes allow that aspects related to the business, market and creativity being considered in design an innovative software product. However, there are gaps between innovation processes and software processes. This work seeks to address the relationship between elements of innovation processes and elements of software processes through traceability. Therefore, this work proposed an approach called InnoTrace that aims to enable tracking of innovation requirements toward system requirements and tracking of system requirements backward innovation requirements. The InnoTrace approach consists of: specifying signs to represent innovation requirements and system requirements; specifying a track to represent the relationship between signs through the notation provided by the SysML language; and traces that consist of following the track in the context of cases that demonstrate the application of software processes that incorporate innovation practices and techniques. The main contribution of this work is to provide a method appropriate for documenting traceability relations (cause and effect) between innovation and system requirements and thus mitigate the gaps commonly observed between innovation and software processes. / As abordagens dirigidas à inovação prescrevem princípios, práticas e ferramentas que são utilizados no desenvolvimento de produtos ou serviços inovadores. A introdução de elementos dessas abordagens dirigidas à inovação no contexto de processos de software permite que sejam tratados aspectos relacionados ao negócio, ao mercado, e à criatividade na concepção de um produto de software inovador. Porém, é comum existir lacunas entre os processos de inovação e os processos de software. Este trabalho procura tratar as relações entre elementos dos processos de inovação e de software, através de rastreabilidade. Para tanto, é proposta uma abordagem denominada InnoTrace que visa possibilitar o rastreamento de requisitos de inovação em direção a requisitos de sistema e vice-versa. A abordagem InnoTrace consiste: na especificação de sinais que representam os requisitos de inovação e de sistemas; na especificação de trilha que representa os relacionamentos entre sinais, através de notação fornecida pela linguagem SysML; e em rastros que consistem em seguir a trilha no contexto de casos que demonstram a aplicação de processos de software que incorporam práticas e técnicas de inovação. A principal contribuição deste trabalho é prover um método que permita documentar as relações de rastreabilidade (causa e efeito) entre requisitos de inovação e de sistema e assim mitigar as lacunas comumente observadas entre processos de inovação e de software.

Submitted by Geyciane Santos (geyciane_thamires@hotmail.com) on 2015-06-22T15:16:11Z No. of bitstreams: 1 Tese- Davi Viana dos Santos.pdf: 66326648 bytes, checksum: cb12228bfcdb57bfff784bec8f864b8b (MD5) / Approved for entry into archive by Divisão de Documentação/BC Biblioteca Central (ddbc@ufam.edu.br) on 2015-06-24T18:26:37Z (GMT) No. of bitstreams: 1 Tese- Davi Viana dos Santos.pdf: 66326648 bytes, checksum: cb12228bfcdb57bfff784bec8f864b8b (MD5) / Approved for entry into archive by Divisão de Documentação/BC Biblioteca Central (ddbc@ufam.edu.br) on 2015-06-24T18:39:00Z (GMT) No. of bitstreams: 1 Tese- Davi Viana dos Santos.pdf: 66326648 bytes, checksum: cb12228bfcdb57bfff784bec8f864b8b (MD5) / Made available in DSpace on 2015-06-24T18:39:00Z (GMT). No. of bitstreams: 1 Tese- Davi Viana dos Santos.pdf: 66326648 bytes, checksum: cb12228bfcdb57bfff784bec8f864b8b (MD5) Previous issue date: 2014-03-31 / FAPEAM - Fundação de Amparo à Pesquisa do Estado do Amazonas / Software Process Improvements are frequent activities in software organizations that are willing to increase the quality of their software products. Such organizations believe that software process improvements can serve as a way for improving software quality. Nevertheless, it is necessary to create strategies in order to establish the continuous process improvement and it is necessary to apply efforts in an adequate way. These improvements involve a lot of knowledge that can be new to software practitioners. Additionally, the process improvements need continuous learning by the whole organization rather than by only a few practitioners. Learning is a process to improve people’s actions through comprehension and knowledge, expanding the existing knowledge. The Organizational Learning composes a set of interactions between knowledge adaptation at the individual level (or subgroups) and knowledge adaptation at the organizational level. In that context, the research question that guides this work is: How can we facilitate the organizational learning in software process improvements? To answer our research question, we performed: (a) investigations in organizations engaged in software process improvements and (b) state-ofart investigations looking for empirical evidences regarding organizational learning and knowledge management. As a result, this thesis presents the definition of the KL-SPI (Knowledge and Learning to Facilitate Software Process Improvement) Framework. The KL-SPI framework assists in diagnosing and improving the organizational learning and knowledge management in software process improvements. / Realizar melhorias nos processos de software é uma atividade constante em organizações de software para aumentar a qualidade dos seus produtos. Essas organizações partem da premissa que a qualidade do software pode ser elevada devido ao aumento da qualidade do processo de desenvolvimento. Contudo, é preciso criar estratégias que institucionalizem a melhoria contínua dos processos e utilizem os esforços de forma adequada. Essas melhorias envolvem diversos conhecimentos que podem ser novos para os membros da organização. Além disso, a melhoria de processos não deve ser vista como esforço único, mas sim como algo evolutivo necessitando, assim, de constante aprendizagem por toda a organização. A aprendizagem é um processo de aperfeiçoar ações por meio de compreensão e conhecimento, ampliando os conhecimentos existentes. Adicionalmente, a Aprendizagem Organizacional consiste em uma série de interações entre a adaptação no nível individual (ou de subgrupo) e adaptação no nível organizacional. A questão de pesquisa que norteia este trabalho é: “Como facilitar a Aprendizagem Organizacional visando à Melhoria de Processo de Software?”. Para responder esta questão, foram realizadas investigações da prática em organizações envolvidas com melhorias de processo de software e investigações do estado da arte buscando evidências experimentais da ocorrência da Aprendizagem Organizacional e da Gerência do Conhecimento. Como resultado, esta tese apresenta a definição do Framework KL-SPI (Knowledge and Learning to Facilitate Software Process Improvement) que contém componentes para facilitar diagnóstico e aplicação da Aprendizagem Organizacional e Gerência do Conhecimento em organizações de software que buscam melhorar seus processos.

Submitted by Maria Aparecida (cidazen@gmail.com) on 2017-08-21T13:05:14Z No. of bitstreams: 1 Adriana Leite.pdf: 5184172 bytes, checksum: 6e560c465acfbbc76b4bfc1dd01bd86b (MD5) / Made available in DSpace on 2017-08-21T13:05:14Z (GMT). No. of bitstreams: 1 Adriana Leite.pdf: 5184172 bytes, checksum: 6e560c465acfbbc76b4bfc1dd01bd86b (MD5) Previous issue date: 2009-02-17 / The interest in the agent-oriented paradigm development has increased in recent years. This is due mainly to the increasing complexity of current software that requires new characteristics as autonomy behavior. In the agent-oriented paradigm, the software has no longer a strictly predictable behavior, has from the control over their own behavior and can make decisions based on observations the environment and inferences upon its knowledge base. A set of meth and process have been already proposed for agent-oriented software engineering. Domain Engineering is a process for the development of a reusable application family in a particular domain problem, and Application Engineering, the one for the construction of a specific application in a family based on the reuse of software artifacts in the application family previously produced in the Domain Engineering process. MADAE-Pro is an ontology-driven process for multi-agent domain and application engineering which promotes the construction and reuse of agent-oriented applications families. The process is specified in a formal representation language, thus avoiding ambiguous interpretations. Another differential of MADAE-Pro is the reuse of software support in all levels of abstraction, from the requirements to the deployment. / O interesse pelo paradigma de desenvolvimento orientado a agentes tem aumentado nos últimos anos. Isso se deve principalmente ao crescente aumento da complexidade dos produtos de software atuais que requerem novas características como comportamento autônomo. No paradigma orientado a agentes, o software deixa de ter comportamento estritamente previsível e passa a ter controle sobre seu próprio comportamento, podendo tomar decisões a partir de observações do ambiente e de inferências realizada em sua base de conhecimento. Para guiar o desenvolvimento orientado a agentes tem sido proposto um conjunto de metodologias e processos pela comunidade da Engenharia de Software. Nesse trabalho, apresenta-se MADAE-Pro, um processo para o desenvolvimento de sistemas multiagente com alguns diferenciais em relação aos já propostos pela comunidade. A Engenharia de Domínio é um processo para criação de abstrações de software reusáveis no desenvolvimento de uma família de aplicações em um domínio particular de problema. A Engenharia de Aplicações é um processo para construção de aplicações baseadas no reúso de artefatos de software previamente produzidos no processo da Engenharia de Domínio. O MADAE-Pro é um processo dirigido por ontologias para a Engenharia de Domínio e de Aplicações Multiagente, o qual promove a construção e o reúso de famílias de aplicações. O processo é especificado em uma linguagem de representação de processos formal, evitando assim interpretações ambíguas. Outro diferencial do MADAE-Pro é o suporte ao reúso de software em todos os níveis de abstração, desde os requisitos até a implementação.

<p>Reports of software a development projects that miss schedule, exceeds budget and deliver products with poor quality are abundant in the literature. Both researchers and the industry are seeking methods to counter these trends and improve software quality.</p><p>Software Process Improvement is a systematic approach to improve the capabilities and performance of software organizations. One basic idea is to assess the organizations’ current practice and improve their software process on the basis of the competencies and experiences of the practitioners working in the organization. A major challenge is to create strategies and mechanisms for managing relevant and updated knowledge about software development and maintenance. Insights from the field of knowledge management are therefore potentially useful in software process improvement efforts to facilitate the creation, modification, and sharing of software processes in any organization.</p><p>In the work presented in this thesis, we have made an overview of empirical studies on the effect of knowledge management in software engineering. We have categorized these studies according to a framework and we report findings on the major concepts that have been investigated empirically, as well as the research methods applied within the field. We have also investigated two main strategies for knowledge management, codification and personalization, through the application of four concrete methods in a software process improvement setting: Mentoring, Rational Unified Process, Process Workshops and Post Mortem Analysis.</p><p>We have classified the work in this thesis within three main themes:</p><p>RT1: Previous research on knowledge management in software engineering.</p><p>RT2: Application of knowledge management to improve the software process through codification of knowledge.</p><p>RT3: Application of knowledge management to improve the software process through personalization of knowledge.</p><p>The main contributions are:</p><p>C1: An overview of the research literature on empirical studies of knowledge management in software engineering.</p><p>C2: A method for tailoring the Rational Unified Process to the development process of a software consulting company.</p><p>C3: Improvements of the Process Workshops method by contextualization.</p><p>C4: Improvement of the root-cause analysis phase of the lightweight Post Mortem Analysis for more effective project retrospectives.</p><p>C5: Proposed methods to increase the learning effect of mentor programs in software engineering.</p>

Reports of software a development projects that miss schedule, exceeds budget and deliver products with poor quality are abundant in the literature. Both researchers and the industry are seeking methods to counter these trends and improve software quality. Software Process Improvement is a systematic approach to improve the capabilities and performance of software organizations. One basic idea is to assess the organizations’ current practice and improve their software process on the basis of the competencies and experiences of the practitioners working in the organization. A major challenge is to create strategies and mechanisms for managing relevant and updated knowledge about software development and maintenance. Insights from the field of knowledge management are therefore potentially useful in software process improvement efforts to facilitate the creation, modification, and sharing of software processes in any organization. In the work presented in this thesis, we have made an overview of empirical studies on the effect of knowledge management in software engineering. We have categorized these studies according to a framework and we report findings on the major concepts that have been investigated empirically, as well as the research methods applied within the field. We have also investigated two main strategies for knowledge management, codification and personalization, through the application of four concrete methods in a software process improvement setting: Mentoring, Rational Unified Process, Process Workshops and Post Mortem Analysis. We have classified the work in this thesis within three main themes: RT1: Previous research on knowledge management in software engineering. RT2: Application of knowledge management to improve the software process through codification of knowledge. RT3: Application of knowledge management to improve the software process through personalization of knowledge. The main contributions are: C1: An overview of the research literature on empirical studies of knowledge management in software engineering. C2: A method for tailoring the Rational Unified Process to the development process of a software consulting company. C3: Improvements of the Process Workshops method by contextualization. C4: Improvement of the root-cause analysis phase of the lightweight Post Mortem Analysis for more effective project retrospectives. C5: Proposed methods to increase the learning effect of mentor programs in software engineering.

As a part of the quality management, product defectiveness prediction is vital for small software organizations as for instutional ones. Although for defect prediction there have been conducted a lot of studies, process enactment data cannot be used because of the difficulty of collection. Additionally, there is no proposed approach known in general for the analysis of process enactment data in software engineering. In this study, we developed a method to show the applicability of process enactment data for defect prediction and answered &ldquo / Is process enactment data beneficial for defect prediction?&rdquo / , &ldquo / How can we use process enactment data?&rdquo / and &ldquo / Which approaches and analysis methods can our method support?&rdquo / questions. We used multiple case study design and conducted case studies including with and without process enactment data in a small software development company. We preferred machine learning approaches rather than statistical ones, in order to cluster the data which includes process enactment informationsince we believed that they are convenient with the pattern oriented nature of the data. By the case studies performed, we obtained promising results. We evaluated performance values of prediction models to demonstrate the advantage of using process enactment data for the prediction of defect open duration value. When we have enough data points to apply machine learning methods and the data can be clusteredhomogeneously, we observed approximately 3% (ranging from -10% to %17) more accurate results from analyses including with process enactment data than the without ones. Keywords:

Many software companies face such problems as projects being behind schedule, exceeding the budget, customer dissatisfaction with product quality. Most of the problems arise due to immature software process of the company. The most popular process assessment models worldwide are ISO/IEC 15504 and CMMI. Companies seeking wider official recognition choose between these two models. Companies face the problem that different customers require process assessment according to different models. Therefore, it is important for companies to have an instrument that would transform company’s assessment results according to one process assessment model to another model without actual reassessment each time. The transitional process assessment model proposed in the dissertation allows the companies in the automotive, defence, space, medical, and other industries to have assessment results according to different process assessment models by performing only single process assessment. The presented method for TPAM development could be used developing transitional process assessment models in other domains. For example, service companies could implement a transitional model covering CMMI-SVC and ISO/IEC 15504-8 assessment models, and companies working in other areas could implement a transitional model covering Enterprise SPICE and FAA-iCMM assessment models. / Dauguma programinę įrangą kuriančių įmonių susiduria su problemomis: projektai vėluoja, viršijamas biudžetas, klientai nepatenkinti produktų kokybe. Daugelis problemų kyla dėl nebrandaus programų kūrimo proceso, pagal kurį įmonė įgyvendina projektus. Populiariausi pasaulyje programų kūrimo procesų vertinimo modeliai yra ISO/IEC 15504 ir CMMI. Įmonės, norėdamos būti oficialiai pripažintos platesnėje aplinkoje, renkasi vieną iš šių dviejų modelių. Įmonės susiduria su problema, kad skirtingi užsakovai reikalauja skirtingų procesų vertinimo modelių. Todėl įmonėms yra aktualu turėti instrumentą, kuris atvaizduotų jos vertinimo rezultatus iš vieno procesų vertinimo modelio į kitą, neatliekant kaskart realaus įmonės procesų vertinimo. Disertacijoje pateiktas tarpinis programų kūrimo procesų vertinimo modelis yra instrumentas įmonėms, siekiančioms kurti programų sistemas automobilių, krašto apsaugos, kosmoso, medicinos ir kitose pramonės šakose, gauti vertinimo rezultatus pagal įvairius procesų vertinimo modelius, atliekant vieną procesų vertinimą. Pagal pasiūlytą tarpinio programų kūrimo procesų vertinimo modelio kūrimo metodą galima kurti tarpinius modelius ir kitų sričių procesams vertinti. Pavyzdžiui, galima konstruoti tarpinį modelį paslaugas teikiančioms organizacijoms, apimantį CMMI-SVC ir ISO/IEC 15504-8 vertinimo modelius, arba tarpinį modelį bet kokia veikla užsiimančioms organizacijoms, apimantį Enterprise SPICE ir FAA-iCMM vertinimo modelius.