Conferencia realizado del 12 al 14 de setiembre en Lima, Peru del 2012 en el marco del 15º Simposio Internacional de Tesis y Disertaciones Electrónicas (ETD 2012). Evento aupiciado por la Universidad Nacional Mayor de San Marcos (UNMSM) y la Universidad Peruana de Ciencias Aplicadas (UPC). / Title: Trends in Use of Citation Management Tools in Theses and Dissertations Authors: Charles J. Greenberg, Special Projects Librarian, Cushing/Whitney Medical Library, Yale University Length of presentation: 20 minutes Objective: Citation Management (CM) tools for scholarly writing predate the web browser. The advantages of current cloud-based tools, either free or subscription, support the expectation that every academic candidate for an advanced degree has an opportunity to use CM tools. CM improves the efficiency of scholarly writing and improves the formatted appearance of the electronic thesis or dissertation (ETD). The expanding range of desktop and cloud-based CM alternatives may demand student attention and potentially detract from the completion process. Do universities with ETD programs use their academic libraries to support the CM selection process, or do universities limit choices? How have universities supporting ETDs reacted to the emergence of new credible CM applications that offer attractive options for certain disciplines or devices? Methods: A brief survey was distributed to the ETD support community and social networks to ascertain the impact of burgeoning choices in CM for both students and the ETD administrative staff. Results: Pending survey and analysis Conclusions: Pending survey and analysis

Thesis (M.S.) -- Central Connecticut State University, 2007. / Title from electronic t.p. Special project advisor: Marianne D'Onofrio. Special project submitted for approval in partial fulfillment of the requirements for the degree of Master of Science, Computer Information Technology. Includes bibliographical references.

Der in der Literatur verwendete Wissensbegriff ist vielschichtig. In dieser Arbeit werden sechs Facetten des Begriffes Wissen aus Sicht der Software-Entwicklung herausgearbeitet: Träger, Güte, Ausdrücklichkeit, Sprachbezug, Abstraktionsebene und Inhalt. Während traditionelle, schwergewichtige Software-Entwicklungsprozesse primär explizites und formal-sprachliches Wissen fokussieren, das sich bspw. in Anforderungsdokumenten oder Quelltexten widerspiegelt, betonen leichtgewichtige Prozesse neben dem formal-sprachlichen Wissen auch implizites und nicht-sprachliches Wissen, das durch Konzepte wie Pair-Progamming oder Planspiele bei der Projektplanung stimuliert wird. Bei einer Untersuchung des V-Modells und des Extreme Programming werden weitere Unterschiede alternativer Vorgehensweisen bei der Software-Entwicklung aus Sicht des Wissensmanagements dargestellt. Abgeschlossen wird die Arbeit mit einer Zusammenstellung spezieller Anforderungen an ein Wissensmanagement in der Software-Entwicklung.

Thesis (M.Eng.) Carleton University, 2006. / Includes bibliographical references (p. 115-123). Also available in electronic format on the Internet.

Thesis (Ph. D.)--University of Alabama at Birmingham, 2006. / Description based on contents viewed Jan. 26, 2007; title from title screen. Includes bibliographical references (p. 200-214).

Despite documented best practices and specialized tools, software organizations struggle to deliver quality software that is on time, within budget, and meets customer requirements. Managers seeking improved software project outcomes face two dominant software paradigms which differ in their emphasis on upfront planning, customer collaboration, and product documentation: plan-driven and agile. Rather than promoting one approach over the other, this research advocates improving software management practices by developing the organization’s ambidextrous capability. Ambidextrous organizations have the ability to simultaneously succeed at two seemingly contradictory capabilities (e.g. discipline and agility) which leads to enhanced organizational performance. Overall, this study asks the question: How can an ambidextrous perspective facilitate improvement in software practices? Driven by this question, and based on a two year action research study at a small software firm, TelSoft, the objectives of this research are to: 1. Identify dualities involved in improving software practices 2. Design interventions based on these dualities to improve software practices 3. Explore the process of becoming an ambidextrous software organization The resulting dissertation consists of a summary and four papers that each identify and address particular dualities encountered during software process improvement. The first paper asserts that both process-driven and perception-driven inquiry should be used during assessment of software practices, presents a model that shows how this combination can occur, and demonstrates the use of this model at TelSoft. The second paper explicates two theories for understanding and resolving issues in requirements engineering practice – repeat-ability and response-ability – and argues for the need to negotiate between the two. The third paper identifies a tension between managing legacy and current processes and proposes a model for software process reengineering, a systematic process for leveraging legacy processes created during prior SPI efforts. Finally, the fourth paper applies the theoretical lens of ambidexterity to understand the overall change initiative in terms of the tension between alignment and adaptability. The study used a variety of data sources to diagnose software practices, including semi-structured interviews, software process documents, meeting interactions, and workshop discussions. Subsequently, we established, facilitated, and tracked focused improvement teams in the areas of customer relations, requirements management, quality assurance, project portfolio management, and process management. Furthermore, we created and trained two management teams with responsibility for ongoing management of SPI and project portfolio management respectively. We argue that these activities improved software practices at TelSoft and provided a stronger foundation for continuous improvement. Keywords: Ambidexterity, software process improvement (SPI), action research, requirements engineering assessment, action planning, software process reengineering, software management.

Context: Over the recent years, ‘Lean Software Development’ (LSD) has been emerging as a significant practice in the Software Industry. The inherent nature of ‘Lean’ to efficiently handle frequently changing customer needs by minimizing ‘Waste’ is a major success factor in practicing it in the context of ‘Software Engineering’. In simple words, Lean Software Development is the true translation of Lean Manufacturing and Lean IT principles to Software Engineering. This work presents an in-depth analysis on the implication of lean methodologies from both ‘State of Art’ and ‘State of Practice’ in the context of Software Engineering. Objectives: The prime objective of the study is to investigate what methodologies were considered & adopted under lean philosophy and to present relevant evidence on the implication of lean methodologies in reference to what defines ‘lean’ in Software Engineering. An extensive literature review was aimed to find the existing challenging factors that negatively influenced the success of software projects and the respective lean mitigation methodologies that were employed by various software organizations to appease their negative impact. Industrial interviews were conducted by interviewing lean experts, with a motive to find the current state of lean implementation in software industry. The outcomes from the systematic literature review (State of Art) and the industry (State of Practice) are comparatively analysed to explore the similarities and differences on the state of lean implication. Finally, a set of guidelines are recommended that would benefit an Industrial Practitioner/Stakeholder/Academic Researcher in practicing the appropriate lean methodology in the context of software engineering. Methods: We conducted a ‘Systematic literature review’ (SLR) by systematically analyzing relevant studies and then interviewed industrial experts to validate our findings. The systematic literature review was conducted according to the guidelines proposed by Dr. Barbara Kitchenham stated in ‘Guidelines for performing Systematic Literature Reviews’ article. The thorough review helped us in identifying various challenging factors that negatively influenced the success of software projects and the respective lean mitigation methodologies that were practiced in the context of software engineering. The associated benefits of practicing the lean methodologies are also presented. The extensive review included peer reviewed articles from electronic databases such as IEEE Explore, Inspec, Scopus and ISI. In addition to this, we conducted snowball sampling on the references of the selected articles to avoid the potential risk of losing relevant and valuable information. Also, other potential sources of information such as books, theses/dissertations, white papers and website/blog articles are included as a part of Grey Literature. In this study, the articles related to the implication of lean methodologies in the context of software engineering were considered. The review included 72 primary studies published between 1993 and 2012. The primary studies were selected based on the following criteria: If they presented the challenging factors that negatively influenced the success of software projects. If they depicted the implication of lean mitigation methodologies (Tool/ Technique/ Method/ Process/ Practice/ Principle) that appeased the negative impact of the identified challenging factors that hampered the success of software projects. If they depicted the implication of lean methodologies (Tool/ Technique/ Method/ Process/ Practice/ Principle) in general or for a specific development/ Management/ Maintenance improvement activities that lead to the success of software projects in the context of software engineering. If they presented the benefits of practicing lean methodologies in the context of software engineering. The study quality assessment was done based on the quality criteria defined in the ‘Quality assessment criteria checklist’. The data such as Article ID, Article Title, Literature type (Peer- reviewed, Non-peer reviewed), Context of validation of the lean methodology (Industry/Academia), Subjects considered for the study (Researchers/students, Industrial practitioners), Type of article publication (Conference/ Journal/ Books/ Thesis Reports/ Doctoral dissertations/ Other), Research method used in the study (Case Study/ Experiment/ Experience Report/ Not stated/ Secondary Data Analysis/ Literature Review), Context of conducting the research (Industry/ Academia/ Not stated/ Both), Context of validation of the study (Strong/ Medium/ Weak), Publication date & year, Source of the publication, are extracted as a part of Quantitative analysis. The secondary data analysis for both ‘State of Art’ (Systematic literature review) and ‘State of Practice’ (Industry) was carried by performing a generic data analysis designed to answer our research questions. The more specific data such as the challenging factors that negatively influenced the success of software projects, the type of lean contribution presented i.e., the methodology being a Tool, Technique, Practice, Principal, Process or a Method, along with the benefits associated on their implication that helped us to answer our research questions are extracted as a part of qualitative analysis from the selected studies. The industrial interviews were conducted by interviewing potential lean experts who had decent experience in lean software development, to find the current state of lean implication in the software industry. In the end, a comparative analysis was performed to clearly understand the state of convergence and divergence between the results from extensive literature review and the industry with respect to the implication of lean methodologies in the context of software engineering. Results: A total of 72 primary articles were selected for data extraction. 56 articles were selected from the electronic databases that clearly depicted lean implementation in the context of software engineering. 9 articles were selected by conducting snowball sampling i.e. by scrutinizing the references of the selected primary studies and finally the grey literature resulted in 7 articles. Most of the articles discussed about lean implication in the context of software engineering. The depicted lean methodologies were validated in either Industry or Academia. A few articles depicted regarding lean principles and their benefits in the context of software engineering. Most of the selected articles in our study were peer- reviewed. Peer reviewing is a process of evaluating one’s work or performance by an expert in the same field in order to maintain or enhance the quality of work or performance in the particular field. This indicates that the articles considered for data extraction have been reviewed by potential experts in the research domain. Conclusions: This study provided a deeper insight into lean implication in the context of software engineering. The aim of the thesis is to find the challenging factors that negatively influenced the success of software projects. A total of 54 challenges were identified from the literature review. The 72 primary articles selected from various resources yielded 53 lean methodologies. The lean methodologies were grouped into Principles, practices, tools and methods. Mapping between the identified challenges and the mitigation lean methodologies is presented. Industrial interviews were conducted to find the current state of lean implication in software engineering. A total of 30 challenges were identified from the industry. A total of 40 lean methodologies were identified from the interviews. Comparative analysis was done to find the common challenges and mitigation lean methodologies between the State of art and State of practice. Based on the analysis a set of guidelines are presented at the end of the document. The guidelines benefit an industrial practitioner in practicing the appropriate lean methodology. Keywords: Lean Methodology, Lean software development, lean software management, lean software engineering, Systematic literature review, literature review. / Context: Over the recent years, ‘Lean Software Development’ (LSD) has been emerging as a significant practice in the Software Industry. The inherent nature of ‘Lean’ to efficiently handle frequently changing customer needs by minimizing ‘Waste’ is a major success factor in practicing it in the context of ‘Software Engineering’. In simple words, Lean Software Development is the true translation of Lean Manufacturing and Lean IT principles to Software Engineering. This work presents an in-depth analysis on the implication of lean methodologies from both ‘State of Art’ and ‘State of Practice’ in the context of Software Engineering. Objectives: The prime objective of the study is to investigate what methodologies were considered & adopted under lean philosophy and to present relevant evidence on the implication of lean methodologies in reference to what defines ‘lean’ in Software Engineering. An extensive literature review was aimed to find the existing challenging factors that negatively influenced the success of software projects and the respective lean mitigation methodologies that were employed by various software organizations to appease their negative impact. Industrial interviews were conducted by interviewing lean experts, with a motive to find the current state of lean implementation in software industry. The outcomes from the systematic literature review (State of Art) and the industry (State of Practice) are comparatively analysed to explore the similarities and differences on the state of lean implication. Finally, a set of guidelines are recommended that would benefit an Industrial Practitioner/Stakeholder/Academic Researcher in practicing the appropriate lean methodology in the context of software engineering. Methods: We conducted a ‘Systematic literature review’ (SLR) by systematically analyzing relevant studies and then interviewed industrial experts to validate our findings. The systematic literature review was conducted according to the guidelines proposed by Dr. Barbara Kitchenham stated in ‘Guidelines for performing Systematic Literature Reviews’ article. The thorough review helped us in identifying various challenging factors that negatively influenced the success of software projects and the respective lean mitigation methodologies that were practiced in the context of software engineering. The associated benefits of practicing the lean methodologies are also presented. The extensive review included peer reviewed articles from electronic databases such as IEEE Explore, Inspec, Scopus and ISI. In addition to this, we conducted snowball sampling on the references of the selected articles to avoid the potential risk of losing relevant and valuable information. Also, other potential sources of information such as books, theses/dissertations, white papers and website/blog articles are included as a part of Grey Literature. In this study, the articles related to the implication of lean methodologies in the context of software engineering were considered. The review included 72 primary studies published between 1993 and 2012. The primary studies were selected based on the following criteria: If they presented the challenging factors that negatively influenced the success of software projects. If they depicted the implication of lean mitigation methodologies (Tool/ Technique/ Method/ Process/ Practice/ Principle) that appeased the negative impact of the identified challenging factors that hampered the success of software projects. If they depicted the implication of lean methodologies (Tool/ Technique/ Method/ Process/ Practice/ Principle) in general or for a specific development/ Management/ Maintenance improvement activities that lead to the success of software projects in the context of software engineering. If they presented the benefits of practicing lean methodologies in the context of software engineering. The study quality assessment was done based on the quality criteria defined in the ‘Quality assessment criteria checklist’. The data such as Article ID, Article Title, Literature type (Peer- reviewed, Non-peer reviewed), Context of validation of the lean methodology (Industry/Academia), Subjects considered for the study (Researchers/students, Industrial practitioners), Type of article publication (Conference/ Journal/ Books/ Thesis Reports/ Doctoral dissertations/ Other), Research method used in the study (Case Study/ Experiment/ Experience Report/ Not stated/ Secondary Data Analysis/ Literature Review), Context of conducting the research (Industry/ Academia/ Not stated/ Both), Context of validation of the study (Strong/ Medium/ Weak), Publication date & year, Source of the publication, are extracted as a part of Quantitative analysis. The secondary data analysis for both ‘State of Art’ (Systematic literature review) and ‘State of Practice’ (Industry) was carried by performing a generic data analysis designed to answer our research questions. The more specific data such as the challenging factors that negatively influenced the success of software projects, the type of lean contribution presented i.e., the methodology being a Tool, Technique, Practice, Principal, Process or a Method, along with the benefits associated on their implication that helped us to answer our research questions are extracted as a part of qualitative analysis from the selected studies. The industrial interviews were conducted by interviewing potential lean experts who had decent experience in lean software development, to find the current state of lean implication in the software industry. In the end, a comparative analysis was performed to clearly understand the state of convergence and divergence between the results from extensive literature review and the industry with respect to the implication of lean methodologies in the context of software engineering. Results: A total of 72 primary articles were selected for data extraction. 56 articles were selected from the electronic databases that clearly depicted lean implementation in the context of software engineering. 9 articles were selected by conducting snowball sampling i.e. by scrutinizing the references of the selected primary studies and finally the grey literature resulted in 7 articles. Most of the articles discussed about lean implication in the context of software engineering. The depicted lean methodologies were validated in either Industry or Academia. A few articles depicted regarding lean principles and their benefits in the context of software engineering. Most of the selected articles in our study were peer- reviewed. Peer reviewing is a process of evaluating one’s work or performance by an expert in the same field in order to maintain or enhance the quality of work or performance in the particular field. This indicates that the articles considered for data extraction have been reviewed by potential experts in the research domain. Conclusions: This study provided a deeper insight into lean implication in the context of software engineering. The aim of the thesis is to find the challenging factors that negatively influenced the success of software projects. A total of 54 challenges were identified from the literature review. The 72 primary articles selected from various resources yielded 53 lean methodologies. The lean methodologies were grouped into Principles, practices, tools and methods. Mapping between the identified challenges and the mitigation lean methodologies is presented. Industrial interviews were conducted to find the current state of lean implication in software engineering. A total of 30 challenges were identified from the industry. A total of 40 lean methodologies were identified from the interviews. Comparative analysis was done to find the common challenges and mitigation lean methodologies between the State of art and State of practice. Based on the analysis a set of guidelines are presented at the end of the document. The guidelines benefit an industrial practitioner in practicing the appropriate lean methodology. Keywords: Lean Methodology, Lean software development, lean software management, lean software engineering, Systematic literature review, literature review. / 0091-8375920473

Der in der Literatur verwendete Wissensbegriff ist vielschichtig. In dieser Arbeit werden sechs Facetten des Begriffes Wissen aus Sicht der Software-Entwicklung herausgearbeitet: Träger, Güte, Ausdrücklichkeit, Sprachbezug, Abstraktionsebene und Inhalt. Während traditionelle, schwergewichtige Software-Entwicklungsprozesse primär explizites und formal-sprachliches Wissen fokussieren, das sich bspw. in Anforderungsdokumenten oder Quelltexten widerspiegelt, betonen leichtgewichtige Prozesse neben dem formal-sprachlichen Wissen auch implizites und nicht-sprachliches Wissen, das durch Konzepte wie Pair-Progamming oder Planspiele bei der Projektplanung stimuliert wird. Bei einer Untersuchung des V-Modells und des Extreme Programming werden weitere Unterschiede alternativer Vorgehensweisen bei der Software-Entwicklung aus Sicht des Wissensmanagements dargestellt. Abgeschlossen wird die Arbeit mit einer Zusammenstellung spezieller Anforderungen an ein Wissensmanagement in der Software-Entwicklung.

Submitted by Taciano Moraes (tacianomm@gmail.com) on 2017-09-29T16:36:46Z No. of bitstreams: 2 license_rdf: 0 bytes, checksum: d41d8cd98f00b204e9800998ecf8427e (MD5) BR Version - Original.pdf: 4465890 bytes, checksum: 59080162de336729aeb135f1d903423a (MD5) / Approved for entry into archive by Raphael Vilas Boas (raphaelboas@ibict.br) on 2017-09-29T19:18:38Z (GMT) No. of bitstreams: 2 license_rdf: 0 bytes, checksum: d41d8cd98f00b204e9800998ecf8427e (MD5) BR Version - Original.pdf: 4465890 bytes, checksum: 59080162de336729aeb135f1d903423a (MD5) / Made available in DSpace on 2017-09-29T19:18:39Z (GMT). No. of bitstreams: 2 license_rdf: 0 bytes, checksum: d41d8cd98f00b204e9800998ecf8427e (MD5) BR Version - Original.pdf: 4465890 bytes, checksum: 59080162de336729aeb135f1d903423a (MD5) Previous issue date: 2015 / CAPES / Em um mundo onde a tecnologia modifica cada detalhe de nossa sociedade em uma velocidade cada vez maior, é preocupante que a forma como desenvolvemos nossos líderes esteja melhorando tão devagar. Apesar de inúmeros estudos mostrarem que a liderança é um dos fatores que mais influenciam o sucesso de projetos e de mais de U$ 14 bilhões serem gastos anualmente com desenvolvimento de liderança, mais da metade das organizações acredita que não o esteja fazendo de forma eficaz. Uma das metodologias mais eficientes para o desenvolvimento de liderança dentro das organizações é a Aprendizagem Experiencial, proposta por David Kolb, mas ainda se observa pouca padronização no modo como ela é utilizada, com diversas abordagens diferentes e resultados muito variados. Por esta razão, este estudo propõe um modelo padronizado para o uso de dinâmicas de grupo como um meio para ajudar alunos de tecnologia a praticar habilidades de liderança. Um primeiro piloto foi executado com resultados e feedback bastante positivos, que indicam o potencial de sua aplicação para outras habilidades e contextos. / In a world where technology is changing every single detail of our societies, schools, and organizations in a skyrocketing speed, it is worrying that the way we develop our leaders is improving so slowly. With numerous studies showing that leadership is one of the factors that impact the most on software projects’ success, it is worrying that more than $14B are spent yearly with leadership development and, still, most organizations believe they are not being effective. One of the most efficient methodologies for leadership development inside companies is the Experiential Learning from David Kolb, but it still has some problems in gaining traction inside universities due to their difficulty of simulating practical experiences. Many different approaches have been tried with various results and little standardization is perceived on the way they are used. For this reason, this study proposes a framework for using group activities as a means to help technology students practice leadership skills. A first pilot was executed with pleasant results and feedback from students, but more experiments are necessary to ensure its application for other skills and contexts.

Submitted by Fabio Sobreira Campos da Costa (fabio.sobreira@ufpe.br) on 2016-10-31T12:26:44Z No. of bitstreams: 2 license_rdf: 1232 bytes, checksum: 66e71c371cc565284e70f40736c94386 (MD5) DISSERTACAO_RAONI_MONTEIRO_DE_OLIVEIRA.pdf: 5342727 bytes, checksum: e90a018631808e7172edd33660941802 (MD5) / Made available in DSpace on 2016-10-31T12:26:44Z (GMT). No. of bitstreams: 2 license_rdf: 1232 bytes, checksum: 66e71c371cc565284e70f40736c94386 (MD5) DISSERTACAO_RAONI_MONTEIRO_DE_OLIVEIRA.pdf: 5342727 bytes, checksum: e90a018631808e7172edd33660941802 (MD5) Previous issue date: 2016-03-03 / Historicamente, o mundo dos negócios tem reconhecido o planejamento da estratégia de negócios, e a seleção de projetos como as responsabilidades dos administradores das empresas, enquanto julgam que o planejamento e a execução dos projetos devem ser realizados pelos gerentes de projeto e suas equipes. Em muitos casos, estes processos não estão alinhados e, como resultado, as organizações podem ter dificuldades em garantir a execução de seus projetos. Em uma pesquisa realizada pela PricewaterhouseCoopers, foi verificado que noventa e sete por cento dos respondentes concorda que o gerenciamento de projetos é crítico para o desempenho do negócio, crescimento e sucesso da organização. No contexto da estratégia de negócios, Business Process Management (BPM) tem sido considerado prioridade para as organizações que querem sobreviver em ambientes de mercados altamente competitivos. Para lidar com estas novas perspectivas globais, as Pequenas e Médias Empresas (PMEs) e/ou as organizações que possuem características similares a estas estão recorrendo a abordagens gerenciais consolidadas, principalmente no âmbito da gestão de projetos e, mais recentemente, da gestão por processos de negócio. Tendo como base o escopo do BPM e da gestão de projetos, este trabalho propõe o Framework de Gestão de Processo e Projeto (GP2). Criado a partir de uma pesquisa-ação e da realização de experimentos em uma organização com características similares a de uma Pequena e Média Empresa (PME), o GP2 baseia-se no Corpo Comum de Conhecimento em BPM (CBOK), bem como no Project Management Body of Knowledge (PMBok), e nos princípios do manifesto ágil, visando a integração destas disciplinas e buscando a aplicabilidade em PMEs. / Historically, the world of business has recognized business strategy planning, and the project selection as the responsibilities governed by senior managers and project planning and execution processes as the activities performed by project managers and their project teams. In many cases, these processes are not aligned; As a result, organizations may fail to tie their projects either to their business strategy, which may cause them to terminate the project or to continue implementing projects that do not contribute to the organization’s goals. In the survey conducted by PricewaterhouseCoopers, it was verified that ninety-seven percent of respondents agree that the project management is critical to business performance, growth and success of the organization. On the other hand, Business Process Management (BPM), has also been considered a priority for organizations that want to survive in the highly competitive market environments. To deal with these new global perspectives, Small and Medium Enterprises (SMEs) are resorting to consolidated management approaches, especially in the context of project management and, more recently, the management of business processes. Based on the scope of BPM and project management, this paper proposes the Framework Process and Project Management (GP2). Created from an action research and of conducting experiments in an organization similar to a small and Medium Enterprise (SMEs), the GP2 is based on the Common Body of Knowledge in BPM (CBOK) as well as in the Project Management Body of Knowledge (PMBOK) in practices, originating of the lean and of the agile project management aiming at merging of these disciplines and seeking applicability in SMEs.