Relevant bibliographies by topics / Software engineering Research Methodology

Academic literature on the topic 'Software engineering Research Methodology'

Author: Grafiati
Published: 10 December 2022
Last updated: 28 January 2023

Create a spot-on reference in APA, MLA, Chicago, Harvard, and other styles

Select a source type:

Contents

Consult the lists of relevant articles, books, theses, conference reports, and other scholarly sources on the topic 'Software engineering Research Methodology.'

Next to every source in the list of references, there is an 'Add to bibliography' button. Press on it, and we will generate automatically the bibliographic reference to the chosen work in the citation style you need: APA, MLA, Harvard, Chicago, Vancouver, etc.

You can also download the full text of the academic publication as pdf and read online its abstract whenever available in the metadata.

Journal articles on the topic "Software engineering Research Methodology"

1

Xia, Franck. "What's wrong with software engineering research methodology." ACM SIGSOFT Software Engineering Notes 23, no. 1 (January 1998): 62–65. http://dx.doi.org/10.1145/272263.272279.

Full text
APA, Harvard, Vancouver, ISO, and other styles
2

Sherry, Marion M. "Methodology for Software Documentation Reuse." Proceedings of the Human Factors Society Annual Meeting 36, no. 3 (October 1992): 198–201. http://dx.doi.org/10.1518/107118192786751772.

Full text
Abstract:
This paper describes a documentation writing methodology developed and used by the author to address some of the issues of consistency in documentation and product function, redundancy of research and solution, and product usability (including timeliness of delivery and quality of support) for a software product engineered, developed and deployed in a multi-organizational or corporate environment. The methodology is compatible with technical systems engineering, development and testing documentation requirements, and is applicable to software products for which there are existing or anticipated “user guides”. The method used to accomplish these goals is the incorporation of existing user guide formats, wherever possible, in the documentation of technical specifications for detailed engineering, development and testing requirements. This paper describes the “cycle of documentation” methodology employed, identifies opportunities to use this methodology, and describes some of the benefits derived from using the methodology (both initially intended and later discovered).
APA, Harvard, Vancouver, ISO, and other styles
3

Dong, Jian Li. "Research on Heterogeneous Component Assembly Problems Based on Software Product Line." Advanced Materials Research 765-767 (September 2013): 1324–27. http://dx.doi.org/10.4028/www.scientific.net/amr.765-767.1324.

Full text
Abstract:
With the research and development of software product line and component-based software engineering methodology, it has become key technology how to build component assembly environment and realize heterogeneous component assembly. Thus, a new industrialized product line based integrated software engineering environment (PL-ISEE) model is firstly proposed, and the heterogeneity problems of developed components are analyzed and discussed. For removing components heterogeneity and realizing heterogeneous components assembly, the wrapper wrapping component is studied further. These researches and ideas will play significant role in promoting the formations of component-based software engineering methodology and future industrialized software production technology.
APA, Harvard, Vancouver, ISO, and other styles
4

DeFranco, Joanna F., and Phillip Laplante. "A software engineering team research mapping study." Team Performance Management: An International Journal 24, no. 3/4 (June 11, 2018): 203–48. http://dx.doi.org/10.1108/tpm-08-2017-0040.

Full text
Abstract:
Purpose The purpose of this mapping study has been performed to identify, critically analyze and synthesize research performed in the area of software engineering teams. Teams, in a general sense, have been studied extensively. But the distinctive processes that need to be executed effectively and efficiently in software engineering require a better understanding of current software engineering team research. Design/methodology/approach In this work, software engineering team publications were analyzed and the key findings of each paper that met our search inclusion criteria were synthesized. In addition, a keyword content analysis was performed to create a taxonomy to categorize each paper and evaluate the state of software engineering team research. Findings In software engineering team research, the resulting areas that are the most active are teamwork/collaboration, process/design and coordination. Clear themes of analysis have been determined to help understand how team members collaborate, factors affecting their success and interactions among all project stakeholders. In addition, themes related to tools to support team collaboration, improve the effectiveness of software engineering processes and support team coordination have been found. However, the research gaps determined from the content analysis point toward a need for more research in the area of communication and tools. Originality/value The goal of this work is to define the span of previous research in this area, create a taxonomy to categorize such research and identify open research areas to provide a clear road map for future research in the area of software engineering teams. These results, along with the key finding themes presented, will help guide future research in an area that touches all parts of the software engineering and development processes.
APA, Harvard, Vancouver, ISO, and other styles
5

Mcharfi, Zineb, and Bouchra El Asri. "Towards Efficient Tracing in Software Product Lines: Research Methodology." Computer and Information Science 12, no. 2 (April 30, 2019): 138. http://dx.doi.org/10.5539/cis.v12n2p138.

Full text
Abstract:
Software Product Lines represent a solution for massive development with minimum costs, while assuring product high quality and interesting time to market. In fact, Software Product Lines systems are used for massive productions, and are based on systematic reuse of commun components, while offering the ability to add specific development, in order to satisfy particular users or market needs. However, to maintain such complex and large-scale systems, it is mandatory to adopt a suitable tracing policy that satisfies the system constraints, especially cost and complexity. Unfortunately, tracing is rearly applied in Software Product Lines as it presents several constraints, especially its cost. Through our research work, we tried to come up with elements that would help break this prejudice. Therefore, we worked on a cost and Return on Investment estimation model that helps identify the optimal conditions (phase and policy) for implementing a tracing solution. As a result of our work, we found that implementing specific trace links, in a targeted approach that meets business goals, and starting from the Domain Engineering phase, costs less and presents the most interesting Return on Investment. To conduct this study and reach those findings, we followed the Design Science Research Methodology. In this article, we detail the steps of our research according to this methodology’s phases.
APA, Harvard, Vancouver, ISO, and other styles
6

Venkatraman, Sitalakshmi. "Software Engineering Research Gaps in the Cloud." Journal of Information Technology Research 6, no. 1 (January 2013): 1–19. http://dx.doi.org/10.4018/jitr.2013010101.

Full text
Abstract:
This paper takes a systematic review methodology to unearth the reason for a slow adoption of cloud computing by businesses, despite the user interests and cloud advancements gained recently. The key finding is that the IT industry has taken different modelling approaches to engineer and deliver the cloud services based on the goals of different key cloud players, thereby raising various adoption challenges and concerns. In this context, there is a need for rethinking Software Engineering concepts. This motivates us to question whether the existing Software Engineering theories and modelling principles are sufficient for the new cloud computing paradigm. Due to the paucity of a comprehensive review in literature, the main aim of this review article is to identify such research gaps and insufficiencies in Software Engineering, and to provide recommendations for bridging these gaps. In this work, the systemic review of the state of the art of cloud computing has resulted in identifying four major cloud modelling gaps that require prime attention. The paper discusses these gaps and identifies the key Software Engineering challenges prevalent in addressing each of these gaps. Finally, the author proposes five topmost research recommendations specifically designed for overcoming these gaps/challenges in order to facilitate a sustainable cloud adoption. Overall, the author’s findings have established the need to rethink Software Engineering theories for arriving at a multilateral or distributed cloud modelling approach. With such rethinking, the proposed cloud design automatically incorporates cloud user-roles, interoperability, intelligent automation and trusted cloud infrastructure strategies for achieving a sustainable cloud framework of the future.
APA, Harvard, Vancouver, ISO, and other styles
7

Wohlin, Claes, and Per Runeson. "Guiding the selection of research methodology in industry–academia collaboration in software engineering." Information and Software Technology 140 (December 2021): 106678. http://dx.doi.org/10.1016/j.infsof.2021.106678.

Full text
APA, Harvard, Vancouver, ISO, and other styles
8

Ostberg, Jan-Peter, Daniel Graziotin, Stefan Wagner, and Birgit Derntl. "A methodology for psycho-biological assessment of stress in software engineering." PeerJ Computer Science 6 (August 10, 2020): e286. http://dx.doi.org/10.7717/peerj-cs.286.

Full text
Abstract:
Stress pervades our everyday life to the point of being considered the scourge of the modern industrial world. The effects of stress on knowledge workers causes, in short term, performance fluctuations, decline of concentration, bad sensorimotor coordination, and an increased error rate, while long term exposure to stress leads to issues such as dissatisfaction, resignation, depression and general psychosomatic ailment and disease. Software developers are known to be stressed workers. Stress has been suggested to have detrimental effects on team morale and motivation, communication and cooperation-dependent work, software quality, maintainability, and requirements management. There is a need to effectively assess, monitor, and reduce stress for software developers. While there is substantial psycho-social and medical research on stress and its measurement, we notice that the transfer of these methods and practices to software engineering has not been fully made. For this reason, we engage in an interdisciplinary endeavor between researchers in software engineering and medical and social sciences towards a better understanding of stress effects while developing software. This article offers two main contributions. First, we provide an overview of supported theories of stress and the many ways to assess stress in individuals. Second, we propose a robust methodology to detect and measure stress in controlled experiments that is tailored to software engineering research. We also evaluate the methodology by implementing it on an experiment, which we first pilot and then replicate in its enhanced form, and report on the results with lessons learned. With this work, we hope to stimulate research on stress in software engineering and inspire future research that is backed up by supported theories and employs psychometrically validated measures.
APA, Harvard, Vancouver, ISO, and other styles
9

Badreddin, Omar. "Thematic Review and Analysis of Grounded Theory Application in Software Engineering." Advances in Software Engineering 2013 (October 22, 2013): 1–9. http://dx.doi.org/10.1155/2013/468021.

Full text
Abstract:
We present metacodes, a new concept to guide grounded theory (GT) research in software engineering. Metacodes are high level codes that can help software engineering researchers guide the data coding process. Metacodes are constructed in the course of analyzing software engineering papers that use grounded theory as a research methodology. We performed a high level analysis to discover common themes in such papers and discovered that GT had been applied primarily in three software engineering disciplines: agile development processes, geographically distributed software development, and requirements engineering. For each category, we collected and analyzed all grounded theory codes and created, following a GT analysis process, what we call metacodes that can be used to drive further theory building. This paper surveys the use of grounded theory in software engineering and presents an overview of successes and challenges of applying this research methodology.
APA, Harvard, Vancouver, ISO, and other styles
10

Parthasarathy, Sudhaman, and Maya Daneva. "A Requirements Engineering Framework for Software Startup Companies." Journal of Database Management 32, no. 3 (July 2021): 69–94. http://dx.doi.org/10.4018/jdm.2021070104.

Full text
Abstract:
Requirements engineering (RE) for startups has only recently become an area of intense exploration. This paper provides results of a qualitative study with 45 practitioners from four startup companies in four countries. This research was planned and executed using the design science research (DSR) methodology and yielded a descriptive framework that was subjected to a first evaluation in empirical settings. The authors found that practitioners in startups deploy rapid prototyping practices and user feedback but in a different way than the agile methods assume. This research concludes with discussion on validity threats and some implications for practice and research.
APA, Harvard, Vancouver, ISO, and other styles
More sources

Dissertations / Theses on the topic "Software engineering Research Methodology"

1

Rönkkö, Kari. "Making Methods Work in Software Engineering : Method Deployment - as a Social Achievement." Doctoral thesis, Ronneby : Blekinge Institute of Technology, 2005. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-00264.

Full text
Abstract:
The software engineering community is concerned with improvements in existing methods and development of new and better methods. The research approaches applied to take on this challenge have hitherto focused heavily on the formal and specifying aspect of the method. This has been done for good reasons, because formalizations are the means in software projects to predict, plan, and regulate the development efforts. As formalizations have been successfully developed new challenges have been recognized. The human and social role in software development has been identified as the next area that needs to be addressed. Organizational problems need to be solved if continued progress is to be made in the field. The social element is today a little explored area in software engineering. Following with the increased interest in the social element it has been identified a need of new research approaches suitable for the study of human behaviour. The one sided focus on formalizations has had the consequence that concepts and explanation models available in the community are one sided related in method discourses. Definition of method is little explored in the software engineering community. In relation to identified definitions of method the social appears to blurring. Today the software engineering community lacks powerful concepts and explanation models explaining the social element. This thesis approaches the understanding of the social element in software engineering by applying ethnomethodologically informed ethnography and ethnography. It is demonstrated how the ethnographic inquiry contributes to software engineering. Ethnography is also combined with an industrial cooperative method development approach. The results presented demonstrate how industrial external and internal socio political contingencies both hindered a method implementation, as well as solved what the method was targeted to do. It is also presented how project members’ method deployment - as a social achievement is played out in practice. In relation to this latter contribution it is provided a conceptual apparatus and explanation model borrowed from social science, The Documentary method of interpretation. This model addresses core features in the social element from a natural language point of view that is of importance in method engineering. This model provides a coherent complement to an existing method definition emphasizing formalizations. This explanation model has also constituted the underpinning in research methodology that made possible the concrete study results.
APA, Harvard, Vancouver, ISO, and other styles
2

Eliote, Yvssa Carneiro Desmots. "Implanta??o e an?lise do framework scrum no desenvolvimento da plataforma aberta Nosso Exerc?cio." UFVJM, 2018. http://acervo.ufvjm.edu.br/jspui/handle/1/1817.

Full text
Abstract:
Submitted by Raniere Barreto (raniere.barros@ufvjm.edu.br) on 2018-10-26T19:47:13Z No. of bitstreams: 2 license_rdf: 0 bytes, checksum: d41d8cd98f00b204e9800998ecf8427e (MD5) yvssa_carneiro_desmots_eliote.pdf: 2710883 bytes, checksum: d37c2db27a339449a69986281db2966a (MD5)
Approved for entry into archive by Rodrigo Martins Cruz (rodrigo.cruz@ufvjm.edu.br) on 2018-11-10T11:13:46Z (GMT) No. of bitstreams: 2 license_rdf: 0 bytes, checksum: d41d8cd98f00b204e9800998ecf8427e (MD5) yvssa_carneiro_desmots_eliote.pdf: 2710883 bytes, checksum: d37c2db27a339449a69986281db2966a (MD5)
Made available in DSpace on 2018-11-10T11:13:47Z (GMT). No. of bitstreams: 2 license_rdf: 0 bytes, checksum: d41d8cd98f00b204e9800998ecf8427e (MD5) yvssa_carneiro_desmots_eliote.pdf: 2710883 bytes, checksum: d37c2db27a339449a69986281db2966a (MD5) Previous issue date: 2018
Este estudo prop?e a implementa??o e an?lise do Framework Scrum no desenvolvimento de novas funcionalidade para o website Nosso Exerc?cio. Esta aplica??o web consiste em um dos projetos do Programa de Educa??o Tutorial, PET-UFVJM/Campus do Mucuri situada na cidade de Te?filo Otoni-MG e tem como finalidade o compartilhamento aberto de exerc?cios did?ticos de diversas ?reas do conhecimento. Por solicita??o de seus idealizadores, novas funcionalidades foram demandadas para o Nosso Exerc?cio, por?m, n?o existiam para este projeto metas claras nem um plano de trabalho a ser seguido, os requisitos n?o estavam formalizados e a equipe dispon?vel n?o estava madura nas tecnologias utilizadas. Levando-se em considera??o o desafio enfrentado na gera??o de software de qualidade e o limite de tempo dispon?vel para a realiza??o desta pesquisa, foi proposto o uso de um processo da Engenharia de Software com intuito de se obter maior controle e qualidade do produto final a ser desenvolvido. O m?todo ?gil Scrum foi o escolhido para gerenciar as atividades de desenvolvimento para este software. Assim, o objetivo geral desta pesquisa consistiu em buscar uma resposta para a seguinte pergunta-problema: Quais benef?cios e/ou dificuldades podem ser obtidas atrav?s da aplica??o do Framework Scrum na evolu??o do desenvolvimento da plataforma aberta Nosso Exerc?cio? Seguindo o modelo sugerido por Coughlan e Coghlan (2002), o m?todo de pesquisa-a??o foi utilizado para descrever a din?mica conduzida durante este trabalho. A implanta??o do Scrum no Nosso Exerc?cio ocorreu em duas etapas, a primeira, visou realizar uma capacita??o sobre o Scrum e as ferramentas tecnol?gicas utilizadas no desenvolvimento do Nosso Exerc?cio. J? a segunda, tratou do desenvolvimento das funcionalidades para este website. A an?lise dos resultados mostrou v?rios benef?cios obtidos com a implanta??o do Scrum neste projeto, como: o foco e compromisso do Time durante o seu trabalho, o atendimento ?s reais necessidades do cliente (Product Owner), a flexibilidade do framework em se ajustar ?s condi??es de ambiente e trabalho de cada Time criado; o aprendizado cont?nuo do software e do processo resultante das discuss?es feitas nas Reuni?es de Planejamento, Revis?o e Retrospectiva. O ponto cr?tico do trabalho deu-se sobre a imaturidade com as tecnologias utilizadas para o desenvolvimento do website. As li??es aprendidas com esta pesquisa indicam que ? poss?vel obter benef?cios com a implanta??o do framework Scrum que superem as suas dificuldades, desde que sejam feitas as devidas an?lises do ambiente em que o mesmo for adotado.
Disserta??o (Mestrado Profissional) ? Programa de P?s-Gradua??o em Tecnologia, Sa?de e Sociedade, Universidade Federal dos Vales do Jequitinhonha e Mucuri, 2018.
This study proposes na implementation and analysis of Scrum Framework in the development of new functionalities to ?Nosso Exerc?cio? (Our Exercise) website. This web application consists in one of the Tutorial Education Program Projects, PET-UFVJM/Mucuri Campus, located in Te?filo Otoni city, Minas Gerais state and it has as its objective the open share of teaching exercises of several knowledge areas. At the request of its creators, new functionalities were demanded to ?Nosso Exerc?cio? (Our Exercise), however, there were not clear goals for this project nor a work plan to be followed, the requirements were not formalised and the available team was not mature enough on the tecnologies applied. Considering the challenge faced on the generation of a good quality software and the time limit available for taking this research, the use of a software engineering was proposed aiming to get bigger quality control of the final Product to be developed. The agile method Scrum was the one chosen to manage the developing activities to this software. So, the general goal of this research consisted in searching for an answer to the following question-problem: Which benefits and/or difficulties can be obtained through the apllication of Scrum Framework on the evolution of the development of ?Nosso Exerc?cio? open plataforma? According to the model suggested by Coughlan and Coghlan (2002), the research-action method was used to describe a dinamic conducted during this work. The Scrum implantation on ?Nosso Exerc?cio? occurred in two stages, the first one, aimed to do a training about Scrum and the technological tools used in the development of ?Nosso Exerc?cio?. The second one, dealt with the development of functionalities to this website. The analyses of the results showed many benefits gotten with the implatation of Scrum in this project, like focus and commitment of ?Time? during its work, the attendance to the costumer?s real needs (Product Owner), the framework flexibility in adjusting to environment and work conditions of each ?Time? created, the continuous learning of the software and of the process resulting of the discussions taken on planning, reviewing and retrospecto meetings. The critical work point was about the immaturity with the technologies used for the website development. The learned lessons with this research indicate that it?s possible to get benefits with the implantation of Scrum Framework which overcome the difficulties, as long as the needed analysis of the enviroment where it was adopted be done.
APA, Harvard, Vancouver, ISO, and other styles
3

Vũ, John Huân. "Software Internationalization: A Framework Validated Against Industry Requirements for Computer Science and Software Engineering Programs." DigitalCommons@CalPoly, 2010. https://digitalcommons.calpoly.edu/theses/248.

Full text
Abstract:
View John Huân Vũ's thesis presentation at http://youtu.be/y3bzNmkTr-c. In 2001, the ACM and IEEE Computing Curriculum stated that it was necessary to address "the need to develop implementation models that are international in scope and could be practiced in universities around the world." With increasing connectivity through the internet, the move towards a global economy and growing use of technology places software internationalization as a more important concern for developers. However, there has been a "clear shortage in terms of numbers of trained persons applying for entry-level positions" in this area. Eric Brechner, Director of Microsoft Development Training, suggested five new courses to add to the computer science curriculum due to the growing "gap between what college graduates in any field are taught and what they need to know to work in industry." He concludes that "globalization and accessibility should be part of any course of introductory programming," stating: A course on globalization and accessibility is long overdue on college campuses. It is embarrassing to take graduates from a college with a diverse student population and have to teach them how to write software for a diverse set of customers. This should be part of introductory software development. Anything less is insulting to students, their family, and the peoples of the world. There is very little research into how the subject of software internationalization should be taught to meet the major requirements of the industry. The research question of the thesis is thus, "Is there a framework for software internationalization that has been validated against industry requirements?" The answer is no. The framework "would promote communication between academia and industry ... that could serve as a common reference point in discussions." Since no such framework for software internationalization currently exists, one will be developed here. The contribution of this thesis includes a provisional framework to prepare graduates to internationalize software and a validation of the framework against industry requirements. The requirement of this framework is to provide a portable and standardized set of requirements for computer science and software engineering programs to teach future graduates.
APA, Harvard, Vancouver, ISO, and other styles
4

Vat, Kam Hou. "REALSpace AKE : an appreciative knowledge environment architected through soft systems methodology and scenario-based design." Thesis, University of Macau, 2011. http://umaclib3.umac.mo/record=b2492481.

Full text
APA, Harvard, Vancouver, ISO, and other styles
5

Perez, Luis G. "Development of a Methodology that Couples Satellite Remote Sensing Measurements to Spatial-Temporal Distribution of Soil Moisture in the Vadose Zone of the Everglades National Park." FIU Digital Commons, 2014. http://digitalcommons.fiu.edu/etd/1663.

Full text
Abstract:
Spatial-temporal distribution of soil moisture in the vadose zone is an important aspect of the hydrological cycle that plays a fundamental role in water resources management, including modeling of water flow and mass transport. The vadose zone is a critical transfer and storage compartment, which controls the partitioning of energy and mass linked to surface runoff, evapotranspiration and infiltration. This dissertation focuses on integrating hydraulic characterization methods with remote sensing technologies to estimate the soil moisture distribution by modeling the spatial coverage of soil moisture in the horizontal and vertical dimensions with high temporal resolution. The methodology consists of using satellite images with an ultrafine 3-m resolution to estimate soil surface moisture content that is used as a top boundary condition in the hydrologic model, SWAP, to simulate transport of water in the vadose zone. To demonstrate the methodology, herein developed, a number of model simulations were performed to forecast a range of possible moisture distributions in the Everglades National Park (ENP) vadose zone. Intensive field and laboratory experiments were necessary to prepare an area of interest (AOI) and characterize the soils, and a framework was developed on ArcGIS platform for organizing and processing of data applying a simple sequential data approach, in conjunction with SWAP. An error difference of 3.6% was achieved when comparing radar backscatter coefficient (σ0) to surface Volumetric Water Content (VWC); this result was superior to the 6.1% obtained by Piles during a 2009 NASA SPAM campaign. A registration error (RMSE) of 4% was obtained between model and observations. These results confirmed the potential use of SWAP to simulate transport of water in the vadose zone of the ENP. Future work in the ENP must incorporate the use of preferential flow given the great impact of macropore on water and solute transport through the vadose zone. Among other recommendations, there is a need to develop procedures for measuring the ENP peat shrinkage characteristics due to changes in moisture content in support of the enhanced modeling of soil moisture distribution.
APA, Harvard, Vancouver, ISO, and other styles
6

Naseem, Junaid, and Wasim Tahir. "Study and analysis of the challenges and guidelines of transitioning from waterfall development model to Scrum." Thesis, Blekinge Tekniska Högskola, Avdelningen för programvarusystem, 2009. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-2679.

Full text
Abstract:
Software engineering practices have experienced significant changes over the period of past two decades. Keeping in view the competitive market trends, now is the high time for many organizations to shift from traditional waterfall models to more agile technologies like Scrum [22][23]. A change of this magnitude is often not easy to undertake. The reason that both software engineering techniques are different in many respects, organizations require considerable amount of analysis of the whole transitioning process and possible scenarios that may occur along the way. Small and medium organizations are normally very skeptical to the change of this magnitude. The scale of change is not limited to only software processes, in fact, difficult part is to deal with old attitudes and thinking processes and mold them for the new agile based Scrum development. The process of change therefore need to be understood in the first place and then carefully forwarded to the implementation phase.
APA, Harvard, Vancouver, ISO, and other styles
7

Redfearn, Brady Edwin. "User Experience Engineering Adoption and Practice: A Longitudinal Case Study." BYU ScholarsArchive, 2013. https://scholarsarchive.byu.edu/etd/3762.

Full text
Abstract:
User Experience Engineering (UxE) incorporates subject areas like usability, HCI, interaction experience, interaction design, "human factors", ergonomics", cognitive psychology", behavioral psychology and psychometrics", systems engineering", [and] "computer science," (Hartson, 1998). It has been suggested that UxE will be the main success factor in organizations as we enter the "loyalty decade" of software development, where the repeat usage of a product by a single customer will be the metric of product success (Alghamdi, 2010; Law & van Schaik, 2010, p. 313; Nielsen, 2008; Van Schaik & Ling, 2011). What is relatively unknown in the current academic literature is whether existing UxE methodologies are effective or not when placed in a longitudinal research context (Law & van Schaik, 2010). There is room for the exploration of the effects of long-term UxE practices in a real-world case study scenario. The problem, addressed in this study, is that a lack of the application of UxE-related processes and practices with an industrial partner had resulted in customer dissatisfaction and a loss of market share. A three-year case study was performed during which 10 UxE-related metrics were gathered and analyzed to measure the improvements in the design of the customer's experience that long-term UxE practices could bring to a small corporate enterprise. The changes that occurred from the corporate and customer's point of view were analyzed as the customer's experience evolved throughout this long-term UxE study. Finally, an analysis of the problems and issues that arose in the implementation of UxE principles during the application of long-term UxE processes was performed. First-hand training between the research team and company employees proved essential to the success of this project. Although a long-term UxE process was difficult to implement within the existing development practices of the industrial partner, a dramatic increase in customer satisfaction and customer engagement with the company system was found. UxE processes led to increased sales rates and decreased development costs in the long-term. All 10 metrics gathered throughout this study showed measurable improvements after long-term UxE processes and practices were adopted by the industrial partner.
APA, Harvard, Vancouver, ISO, and other styles
8

McMeekin, David Andrew. "A software inspection methodology for cognitive improvement in software engineering." Thesis, Curtin University, 2010. http://hdl.handle.net/20.500.11937/400.

Full text
Abstract:
This thesis examines software inspections application in a non-traditional use through examining the cognitive levels developers demonstrate while carrying out software inspection tasks. These levels are examined in order to assist in increasing developers’ ability to understand, maintain and evolve software systems.The results from several empirical studies carried out are presented. These indicate several important findings: student software developers find structured reading techniques more helpful as an aid than less structured reading techniques, while professional developers find the more structured techniques do not allow their experience to be applied to the problem at hand; there is a correlation between the effectiveness of a software inspection and an inspector’s ability to successfully add new functionality to the inspected software artefact; the cognitive levels that student developers functioned at while carrying out software inspection tasks were at higher orders of thinking when structured inspection techniques were implemented than when unstructured techniques were applied.From the empirical results a mapping has been created of several software inspection techniques to the cognitive process models they support and the cognitive levels, as measured using Bloom’s Taxonomy that they facilitate. This mapping is to understand the impact carrying out a software inspection has upon a developer’s cognitive understanding of the inspected system.The knowledge and understanding of the findings of this research has culminated in the creation of a code reading methodology to increase the cognitive level software developers operate at while reading software code. The reading methodology distinguishes where in undergraduate and software developer training courses different software inspection reading techniques are to be implemented in order to maximise a software developer’s code reading ability dependent upon their experience level.
APA, Harvard, Vancouver, ISO, and other styles
9

King, Myron Decker. "A methodology for hardware-software codesign." Thesis, Massachusetts Institute of Technology, 2013. http://hdl.handle.net/1721.1/84891.

Full text
Abstract:
Thesis (Ph. D.)--Massachusetts Institute of Technology, Department of Electrical Engineering and Computer Science, 2013.
Cataloged from PDF version of thesis.
Includes bibliographical references (pages 150-156).
Special purpose hardware is vital to embedded systems as it can simultaneously improve performance while reducing power consumption. The integration of special purpose hardware into applications running in software is difficult for a number of reasons. Some of the difficulty is due to the difference between the models used to program hardware and software, but great effort is also required to coordinate the simultaneous execution of the application running on the microprocessor with the accelerated kernel(s) running in hardware. To further compound the problem, current design methodologies for embedded applications require an early determination of the design partitioning which allows hardware and software to be developed simultaneously, each adhering to a rigid interface contract. This approach is problematic because often a good hardware-software decomposition is not known until deep into the design process. Fixed interfaces and the burden of reimplementation prevent the migration of functionality motivated by repartitioning. This thesis presents a two-part solution to the integration of special purpose hardware into applications running in software. The first part addresses the problem of generating infrastructure for hardware-accelerated applications. We present a methodology in which the application is represented as a dataflow graph and the computation at each node is specified for execution either in software or as specialized hardware using the programmer's language of choice. An interface compiler as been implemented which takes as input the FIFO edges of the graph and generates code to connect all the different parts of the program, including those which communicate across the hardware/software boundary. This methodology, which we demonstrate on an FPGA platform, enables programmers to effectively exploit hardware acceleration without ever leaving the application space. The second part of this thesis presents an implementation of the Bluespec Codesign Language (BCL) to address the difficulty of experimenting with hardware/software partitioning alternatives. Based on guarded atomic actions, BCL can be used to specify both hardware and low-level software. Based on Bluespec SystemVerilog (BSV) for which a hardware compiler by Bluespec Inc. is commercially available, BCL has been augmented with extensions to support more efficient software generation. In BCL, the programmer specifies the entire design, including the partitioning, allowing the compiler to synthesize efficient software and hardware, along with transactors for communication between the partitions. The benefit of using a single language to express the entire design is that a programmer can easily experiment with many different hardware/software decompositions without needing to re-write the application code. Used together, the BCL and interface compilers represent a comprehensive solution to the task of integrating specialized hardware into an application.
by Myron King.
Ph.D.
APA, Harvard, Vancouver, ISO, and other styles
10

Moradian, Esmiralda. "Integrating Security in Software Engineering Process: The CSEP Methodology." Doctoral thesis, KTH, Programvaruteknik och Datorsystem, SCS, 2012. http://urn.kb.se/resolve?urn=urn:nbn:se:kth:diva-95393.

Full text
Abstract:
In today’s organizations, a vast amount of existing software systems is insecure, which results in compromised valuable assets and has negative consequences on the organizations. Throughout the years, many attempts have been made to build secure software systems, but the solutions proposed were limited to a few add-on fixes made after implementation and installation of the system.The contribution of the research in this thesis is a software security engineering methodology, called Controlled Security Engineering Process, which provides support to developers when developing more secure software systems by integrating software lifecycle and security lifecycle, and enhancing the control in the engineering process. The proposed methodology implements security in every phase of general software system engineering, i.e., requirement, design, implementation, and testing, as well as operation and maintenance to certify that software systems are built with security in mind.The Controlled Security Engineering Process methodology addresses security problems in the development lifecycle. Construction of a secure software system involves specific steps and activities, which include security requirements specifications of system behavior, secure software design, an analysis of the design, implementation, with secure coding and integration, and operating and maintenance procedures.The methodology incorporates software security patterns and control of the engineering process. The software security patterns can be used as security controls and information sources to demonstrate how a specific security task should be performed or a specific security problem solved. Many patterns can be implemented in an automated way, which can facilitate the work of software engineers.The control of the engineering process provides visibility over the development process. The control assures that authorised developers access legitimate and necessary information and projects’ documents by using authentication, and authorization.To support implementation of automated patterns and provide control over the engineering process, a design of a multi-agent system is provided. The multi-agent system supports implementation of patterns and extracting security information, and provides traceability in the engineering process. The security information is requirements, threats and security mechanisms that are provided by matching project documents, and traceability is achieved by monitoring and logging services.The Controlled Security Engineering Process methodology has been evaluated through interviews with developers, security professionals, and decision makers in different types of organizations but also through a case study which was carried out in an organization.

QC 20120514

APA, Harvard, Vancouver, ISO, and other styles
More sources

Books on the topic "Software engineering Research Methodology"

1

Mora, Manuel. Research methodologies, innovations, and philosophies in software systems engineering and information systems. Hershey, PA: Information Science Reference, 2012.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
2

Reliability in scientific research: Improving the dependability of measurements, calculations, equipment, and software. Cambridge: Cambridge University Press, 2011.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
3

Deb, Dipankar, Rajeeb Dey, and Valentina E. Balas. Engineering Research Methodology. Singapore: Springer Singapore, 2019. http://dx.doi.org/10.1007/978-981-13-2947-0.

Full text
APA, Harvard, Vancouver, ISO, and other styles
4

Software release methodology. Upper Saddle River, N.J: Prentice Hall PTR, 1999.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
5

Ramamoorthy, C. V., Roger Lee, and Kyung Whan Lee, eds. Software Engineering Research and Applications. Berlin, Heidelberg: Springer Berlin Heidelberg, 2004. http://dx.doi.org/10.1007/b97161.

Full text
APA, Harvard, Vancouver, ISO, and other styles
6

Dosch, Walter, Roger Y. Lee, and Chisu Wu, eds. Software Engineering Research and Applications. Berlin, Heidelberg: Springer Berlin Heidelberg, 2006. http://dx.doi.org/10.1007/11668855.

Full text
APA, Harvard, Vancouver, ISO, and other styles
7

Staron, Miroslaw. Action Research in Software Engineering. Cham: Springer International Publishing, 2020. http://dx.doi.org/10.1007/978-3-030-32610-4.

Full text
APA, Harvard, Vancouver, ISO, and other styles
8

Zhang, Lu, and Chang Xu, eds. Software Engineering and Methodology for Emerging Domains. Singapore: Springer Singapore, 2016. http://dx.doi.org/10.1007/978-981-10-3482-4.

Full text
APA, Harvard, Vancouver, ISO, and other styles
9

Li, Zheng, He Jiang, Ge Li, Minghui Zhou, and Ming Li, eds. Software Engineering and Methodology for Emerging Domains. Singapore: Springer Singapore, 2019. http://dx.doi.org/10.1007/978-981-15-0310-8.

Full text
APA, Harvard, Vancouver, ISO, and other styles
10

Association for Computing Machinery. ACM transactions on software engineering and methodology. New York, NY: Association for Computing Machinery, 1992.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
More sources

Book chapters on the topic "Software engineering Research Methodology"

1

Staron, Miroslaw. "Action Research as Research Methodology in Software Engineering." In Action Research in Software Engineering, 15–36. Cham: Springer International Publishing, 2019. http://dx.doi.org/10.1007/978-3-030-32610-4_2.

Full text
APA, Harvard, Vancouver, ISO, and other styles
2

Wieringa, Roel J. "Research Goals and Research Questions." In Design Science Methodology for Information Systems and Software Engineering, 13–23. Berlin, Heidelberg: Springer Berlin Heidelberg, 2014. http://dx.doi.org/10.1007/978-3-662-43839-8_2.

Full text
APA, Harvard, Vancouver, ISO, and other styles
3

Wieringa, Roel J. "Research Design." In Design Science Methodology for Information Systems and Software Engineering, 121–33. Berlin, Heidelberg: Springer Berlin Heidelberg, 2014. http://dx.doi.org/10.1007/978-3-662-43839-8_11.

Full text
APA, Harvard, Vancouver, ISO, and other styles
4

Cain, Andrew, Tsong Yueh Chen, Doug Grant, Pak-Lok Poon, Sau-Fun Tang, and T. H. Tse. "An Automatic Test Data Generation System Based on the Integrated Classification-Tree Methodology." In Software Engineering Research and Applications, 225–38. Berlin, Heidelberg: Springer Berlin Heidelberg, 2004. http://dx.doi.org/10.1007/978-3-540-24675-6_18.

Full text
APA, Harvard, Vancouver, ISO, and other styles
5

Wieringa, Roel J. "Technical Action Research." In Design Science Methodology for Information Systems and Software Engineering, 269–93. Berlin, Heidelberg: Springer Berlin Heidelberg, 2014. http://dx.doi.org/10.1007/978-3-662-43839-8_19.

Full text
APA, Harvard, Vancouver, ISO, and other styles
6

Wieringa, Roel J. "A Road Map of Research Methods." In Design Science Methodology for Information Systems and Software Engineering, 215–23. Berlin, Heidelberg: Springer Berlin Heidelberg, 2014. http://dx.doi.org/10.1007/978-3-662-43839-8_16.

Full text
APA, Harvard, Vancouver, ISO, and other styles
7

Rabinia, Amin, Sepideh Ghanavati, Llio Humphreys, and Torsten Hahmann. "A Methodology for Implementing the Formal Legal-GRL Framework: A Research Preview." In Requirements Engineering: Foundation for Software Quality, 124–31. Cham: Springer International Publishing, 2020. http://dx.doi.org/10.1007/978-3-030-44429-7_9.

Full text
APA, Harvard, Vancouver, ISO, and other styles
8

Mauro, Vincenzo, and Angelo Messina. "AMINSEP-Agile Methodology Implementation for a New Software Engineering Paradigm Definition. A Research Project Proposal." In Proceedings of 4th International Conference in Software Engineering for Defence Applications, 27–33. Cham: Springer International Publishing, 2016. http://dx.doi.org/10.1007/978-3-319-27896-4_3.

Full text
APA, Harvard, Vancouver, ISO, and other styles
9

Zieris, Franz. "Understanding How Pair Programming Actually Works in Industry: Mechanisms, Patterns, and Dynamics." In Ernst Denert Award for Software Engineering 2020, 275–93. Cham: Springer International Publishing, 2022. http://dx.doi.org/10.1007/978-3-030-83128-8_13.

Full text
Abstract:
AbstractDuring pair programming (PP), two software developers work closely together on a technical task on one computer. Practitioners expect a number of benefits, such as faster progress, higher quality, and knowledge transfer. Much of prior research focused on directly measurable effects from laboratory settings, but could not explain the large variations observed. My research follows the Grounded Theory Methodology and is aimed at understanding how PP actually works by uncovering the underlying mechanisms to ultimately formulate practical advice for developers. The main findings from my qualitative analysis of recordings of 27 industrial PP sessions are: Task-specific knowledge about the software system is crucial for pair programming. Pairs first make sure they have a shared understanding of the relevant parts before they acquire lacking knowledge together. The transfer of general software development knowledge plays a rather small role and only occurs after the pair dealt with its need for system knowledge. Pairs who maintain a shared understanding may have short, but highly-productive Focus Phases; if their Togetherness gets too low, however, a Breakdown of the pair process may occur.
APA, Harvard, Vancouver, ISO, and other styles
10

Altuwaijri, Fahad S., and Maria Angela Ferrario. "Investigating Agile Adoption in Saudi Arabian Mobile Application Development." In Agile Processes in Software Engineering and Extreme Programming – Workshops, 265–71. Cham: Springer International Publishing, 2020. http://dx.doi.org/10.1007/978-3-030-58858-8_27.

Full text
Abstract:
Abstract Mobile app development has been considered as one of the fastest growing segments of the software industry both worldwide and in Saudi Arabia. Due to their pervasiveness, mobile applications call for consideration of complex and rapidly changing requirements given the diversity of their environments. Therefore, agile is considered the most suitable methodology for developing mobile apps. However, little research has investigated agile adoption in mobile app development in the real context. Therefore, the purpose of this PhD is to investigate the factors that have a significant impact on agile adoption in mobile app development by small and medium-size software organisations in Saudi Arabia. The expected key contribution of this research will be a deep insight into agile adoption in mobile app development, and the design and development of tools and techniques that may support agile adoption within Saudi context.
APA, Harvard, Vancouver, ISO, and other styles

Conference papers on the topic "Software engineering Research Methodology"

1

Jedlitschka, Andreas. "Session details: Research methodology." In ISESE06: ACM-IEEE International Symposium on Empirical Software Engineering 2006. New York, NY, USA: ACM, 2006. http://dx.doi.org/10.1145/3245561.

Full text
APA, Harvard, Vancouver, ISO, and other styles
2

Jimenez-Hernandez, Erendira M., Hanna Oktaba, Mario Piattini, Frida Diaz-Barriga Arceo, Alan M. Revillagigedo-Tulais, and Sergio V. Flores-Zarco. "Methodology to Construct Educational Video Games in Software Engineering." In 2016 4th International Conference in Software Engineering Research and Innovation (CONISOFT). IEEE, 2016. http://dx.doi.org/10.1109/conisoft.2016.25.

Full text
APA, Harvard, Vancouver, ISO, and other styles
3

Cereci, Ibrahim, and Ziya Karakaya. "Need for a Software Development Methodology for Research-Based Software Projects." In 2018 3rd International Conference on Computer Science and Engineering (UBMK). IEEE, 2018. http://dx.doi.org/10.1109/ubmk.2018.8566613.

Full text
APA, Harvard, Vancouver, ISO, and other styles
4

Kawaminami-Garcia, Ivan R., Oscar M. Rodriguez-Elias, Sonia R. Meneces-Mendoza, and Maria J. Velazquez-Mendoza. "ROKA: A Software Development Methodology for Industrial Automation." In 2018 6th International Conference in Software Engineering Research and Innovation (CONISOFT). IEEE, 2018. http://dx.doi.org/10.1109/conisoft.2018.8645873.

Full text
APA, Harvard, Vancouver, ISO, and other styles
5

Brooks, Andrew, and Louise Scott. "A Methodology from Software Engineering Inspection which Supports Replicable Mental Models Research." In 6th IEEE International Conference on Cognitive Informatics. IEEE, 2007. http://dx.doi.org/10.1109/coginf.2007.4341882.

Full text
APA, Harvard, Vancouver, ISO, and other styles
6

Yuan, Hanning, Yanni Han, and Jun Hu. "Research on Agile Development Methodology of Service-Oriented Personalized Software." In 2008 International Conference on Computer Science and Software Engineering. IEEE, 2008. http://dx.doi.org/10.1109/csse.2008.1452.

Full text
APA, Harvard, Vancouver, ISO, and other styles
7

Boulanger, Jean-Louis, and Van Quang Dao. "Requirements engineering in a model-based methodology for embedded automotive software." In 2008 IEEE International Conference on Research, Innovation and Vision for the Future in Computing and Communication Technologies. IEEE, 2008. http://dx.doi.org/10.1109/rivf.2008.4586365.

Full text
APA, Harvard, Vancouver, ISO, and other styles
8

Rahimian, Vahid, and Raman Ramsin. "Designing an agile methodology for mobile software development: A hybrid method engineering approach." In 2008 Second International Conference on Research Challenges in Information Science (RCIS). IEEE, 2008. http://dx.doi.org/10.1109/rcis.2008.4632123.

Full text
APA, Harvard, Vancouver, ISO, and other styles
9

Kim, Jeong Ah, and Seung Young Choi. "Evaluation of Ontology Development Methodology with CMM-i." In 5th ACIS International Conference on Software Engineering Research, Management & Applications (SERA 2007). IEEE, 2007. http://dx.doi.org/10.1109/sera.2007.86.

Full text
APA, Harvard, Vancouver, ISO, and other styles
10

Zhang Xinlan, Huang Zhifang, Wei Guangfu, and Zhang Xin. "Information Security Risk Assessment Methodology Research: Group Decision Making and Analytic Hierarchy Process." In 2010 Second World Congress on Software Engineering (WCSE 2010). IEEE, 2010. http://dx.doi.org/10.1109/wcse.2010.55.

Full text
APA, Harvard, Vancouver, ISO, and other styles

Reports on the topic "Software engineering Research Methodology"

1

Markova, Oksana M., Serhiy O. Semerikov, Andrii M. Striuk, Hanna M. Shalatska, Pavlo P. Nechypurenko, and Vitaliy V. Tron. Implementation of cloud service models in training of future information technology specialists. [б. в.], September 2019. http://dx.doi.org/10.31812/123456789/3270.

Full text
Abstract:
Leading research directions are defined on the basis of self-analysis of the study results on the use of cloud technologies in training by employees of joint research laboratory “Сloud technologies in education” of Kryvyi Rih National University and Institute of Information Technology and Learning Aids of the NAES of Ukraine in 2009-2018: cloud learning technologies, cloud technologies of blended learning, cloud-oriented learning environments, cloud-oriented methodological systems of training, the provision of cloud-based educational services. The ways of implementation SaaS, PaaS, IaaS cloud services models which are appropriate to use in the process of studying the academic disciplines of the cycles of mathematical, natural science and professional and practical training of future specialists in information technology are shown, based on the example of software engineering, computer science and computer engineering. The most significant advantages of using cloud technologies in training of future information technology specialists are definite, namely, the possibility of using modern parallel programming tools as the basis of cloud technologies. Conclusions are drawn; the direction of further research is indicated: designing a cloud-oriented learning environment for future specialists in computer engineering, identifying trends in the development of cloud technologies in the professional training and retraining of information technology specialists, developing a methodology for building the research competencies of future software engineering specialists by using cloud technologies.
APA, Harvard, Vancouver, ISO, and other styles
2

Blum, Bruce I. Evaluation Methodology for Software Engineering. Fort Belvoir, VA: Defense Technical Information Center, May 1988. http://dx.doi.org/10.21236/ada198398.

Full text
APA, Harvard, Vancouver, ISO, and other styles
3

Blum, Bruce I. Evaluation Methodology for Software Engineering. Fort Belvoir, VA: Defense Technical Information Center, December 1989. http://dx.doi.org/10.21236/ada218474.

Full text
APA, Harvard, Vancouver, ISO, and other styles
4

Moore, Andrew, Eather Chapman, David Kim, Eric Klinker, and Kenneth Hayman. External COMSEC Adaptor Software Engineering Methodology. Fort Belvoir, VA: Defense Technical Information Center, August 1995. http://dx.doi.org/10.21236/ada298090.

Full text
APA, Harvard, Vancouver, ISO, and other styles
5

Galassi, Mark. Modern Software Engineering and Research. Office of Scientific and Technical Information (OSTI), October 2020. http://dx.doi.org/10.2172/1699404.

Full text
APA, Harvard, Vancouver, ISO, and other styles
6

Morris, J., and M. Shaw. Software Sciences and Engineering Research. Fort Belvoir, VA: Defense Technical Information Center, May 2000. http://dx.doi.org/10.21236/ada380208.

Full text
APA, Harvard, Vancouver, ISO, and other styles
7

Basili, Victor R., John D. Gannon, and Marvin V. Zelkowitz. Research in Programming Languages and Software Engineering. Fort Belvoir, VA: Defense Technical Information Center, September 1992. http://dx.doi.org/10.21236/ada256341.

Full text
APA, Harvard, Vancouver, ISO, and other styles
8

Basili, Victor R., John D. Gannon, and Marvin V. Zelkowitz. Research in Programming Languages and Software Engineering. Fort Belvoir, VA: Defense Technical Information Center, January 1990. http://dx.doi.org/10.21236/ada217765.

Full text
APA, Harvard, Vancouver, ISO, and other styles
9

Sims, Benjamin. Research software engineering: Professionalization, roles, and identity. Office of Scientific and Technical Information (OSTI), February 2022. http://dx.doi.org/10.2172/1845242.

Full text
APA, Harvard, Vancouver, ISO, and other styles
10

McDonnell, Marshall, Addi Thakur Malviya, Gregory Shutt, Suhas Somnath, Dale Stansberry, and Olga Kuchar. Research Software Engineering Efforts for DataFlow: FY2021 Developments. Office of Scientific and Technical Information (OSTI), September 2021. http://dx.doi.org/10.2172/1820765.

Full text
APA, Harvard, Vancouver, ISO, and other styles
You might also be interested in the extended bibliographies on the topic 'Software engineering Research Methodology' for particular source types:
Journal articles Dissertations / Theses Books
We offer discounts on all premium plans for authors whose works are included in thematic literature selections. Contact us to get a unique promo code!

To the bibliography