Journal articles on the topic 'Software engineering Research Methodology'
To see the other types of publications on this topic, follow the link: Software engineering Research Methodology.
Create a spot-on reference in APA, MLA, Chicago, Harvard, and other styles
Consult the top 50 journal articles for your research 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.
Browse journal articles on a wide variety of disciplines and organise your bibliography correctly.
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
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 textAbstract:
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).
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 textAbstract:
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.
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 textAbstract:
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.
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 textAbstract:
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.
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 textAbstract:
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.
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
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 textAbstract:
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.
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 textAbstract:
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.
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 textAbstract:
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.
11
Noor, Adeeb. "Improving bioinformatics software quality through incorporation of software engineering practices." PeerJ Computer Science 8 (January 5, 2022): e839. http://dx.doi.org/10.7717/peerj-cs.839.
Full textAbstract:
Background Bioinformatics software is developed for collecting, analyzing, integrating, and interpreting life science datasets that are often enormous. Bioinformatics engineers often lack the software engineering skills necessary for developing robust, maintainable, reusable software. This study presents review and discussion of the findings and efforts made to improve the quality of bioinformatics software. Methodology A systematic review was conducted of related literature that identifies core software engineering concepts for improving bioinformatics software development: requirements gathering, documentation, testing, and integration. The findings are presented with the aim of illuminating trends within the research that could lead to viable solutions to the struggles faced by bioinformatics engineers when developing scientific software. Results The findings suggest that bioinformatics engineers could significantly benefit from the incorporation of software engineering principles into their development efforts. This leads to suggestion of both cultural changes within bioinformatics research communities as well as adoption of software engineering disciplines into the formal education of bioinformatics engineers. Open management of scientific bioinformatics development projects can result in improved software quality through collaboration amongst both bioinformatics engineers and software engineers. Conclusions While strides have been made both in identification and solution of issues of particular import to bioinformatics software development, there is still room for improvement in terms of shifts in both the formal education of bioinformatics engineers as well as the culture and approaches of managing scientific bioinformatics research and development efforts.
12
Ilieva, Sylvia, Avram Eskenazi, Aleksandar Dimov, and Irena Pavlova. "An Analysis and Forecast of Software and Services Research in Bulgaria." Serdica Journal of Computing 4, no. 2 (July 20, 2010): 133–58. http://dx.doi.org/10.55630/sjc.2010.4.133-158.
Full textAbstract:
In the last 40 years much has been achieved in Software Engineering research and still more is to be done. Although significant progress is being made on several fronts in Service-Oriented Architecture (SOA), there is still no set of clear, central themes to focus research activity on. A task within the EU FP7 Sister project aimed at defining research priorities for the Faculty of Mathematics and Informatics (Sofia University) in the area of Software and Services. A dedicated methodology was proposed and developed, based on various sources of information. The information accumulated was systematised and processed according to this methodology. The final results obtained are described and discussed here.
13
Sa'adillah, Maylawati, and Ramdhani Ali. "Logical framework of information technology: Systematization of software development research." Telfor Journal 14, no. 1 (2022): 26–32. http://dx.doi.org/10.5937/telfor2201026s.
Full textAbstract:
This article aims to present a comprehensive Logical Framework for Information Technology (IT) Research, specifically for developing customized IT applications or software. The methodology of writing this article uses a content analysis with the main source of literature review, Focus Discussion Group, and also based on the experience and knowledge of the authors as lecturers of Software Engineering and Software Project Management. This article shows that although current IT development approaches or methodologies (especially software development methodology) continue to develop, good IT design is carried out through six main stages, namely planning, analysis, design, construction, implementation, and maintenance. The success of IT implementation depends on the good process of all stages of IT design. The involvement of all actors/ stakeholders in IT design is essential to be accommodated at all stages of IT design. Quality also becomes the main goal and controls every process of IT development.
14
Garcia, Klauss Kleydmann Sabino, and Amanda Amaral Abrahão. "Research Development Using REDCap Software." Healthcare Informatics Research 27, no. 4 (October 31, 2021): 341–49. http://dx.doi.org/10.4258/hir.2021.27.4.341.
Full textAbstract:
Objectives: High-quality clinical research is dependent on adequate design, methodology, and data collection. The utilization of electronic data capture (EDC) systems is recommended to optimize research data through proper management. This paper’s objective is to present the procedures of REDCap (Research Electronic Data Capture), which supports research development, and to promote the utilization of this software among the scientific community.Methods: REDCap’s web application version 10.4.1 released on 2021 (Vanderbilt University) is an EDC system suitable for clinical research development. This paper describes how to join the REDCap consortium and presents how to develop survey instruments and use them to collect and analyze data.Results: Since REDCap is a web application that stimulates knowledge-sharing among the scientific community, its development is not finished and it is constantly receiving updates to improve the system. REDCap’s tools provide access control, audit trails, and data security to the research team.Conclusions: REDCap is a web application that can facilitate clinical research development, mainly in health fields, and reduce the costs of conducting research. Its tools allow researchers to make the best use of EDC components, such as data storage.
15
Tomer, Gunjan, and Sushanta Kumar Mishra. "Professional identity construction among software engineering students." Information Technology & People 29, no. 1 (March 7, 2016): 146–72. http://dx.doi.org/10.1108/itp-10-2013-0181.
Full textAbstract:
Purpose – The purpose of this paper is to explore the process in which the software engineering students construct their professional identities. Design/methodology/approach – The study followed the qualitative method using grounded theory methodology to examine the process of identity construction. Data were collected from final year software engineering students in an iterative manner. Findings – Based on the present study, the study argues that entry-level identities of students are modified and adjusted in response to their experience of identity violations over the course of their academic program. These violations were caused by their unmet expectations from the academic program. The magnitude of these violations is influenced by their perceived value derived from the training they were receiving. Research limitations/implications – This paper explains the process of “identity morphing” as a mechanism by which students resolve the conflict/violation of their identities. The emergence and adaptation of different types of identities were examined. This study can be extended to the employees of IT organizations to draw a holistic picture. Practical implications – The understanding of identity morphing process might enable organizations to enrich their interaction with their employees and thus provide avenues to improve their work-related outcomes. Originality/value – Previous studies have explored professional identity construction among individuals. However, how software professionals construct their professional identity, during their education years, is relatively unexplored. The present study asserts that professional identities are formed among the students even before they join the organization.
16
Subha, R., and Anandakumar Haldorai. "An Efficient Identification of Security Threats in Requirement Engineering Methodology." Computational Intelligence and Neuroscience 2022 (August 18, 2022): 1–14. http://dx.doi.org/10.1155/2022/1872079.
Full textAbstract:
Today, we completely rely on Information Technology (IT) applications for every aspect of daily life, including business and online transactions. In addition to using these IT-enabled applications for business purposes, we also use WhatsApp, Facebook, and a variety of other IT applications to communicate with others. However, there will undoubtedly be a drawback to every benefit. Since everything is linked to the Internet, there are many opportunities for security to be compromised. To address this, we are working to identify security threats early on in the software development process, specifically during the requirements phase. During the requirement engineering process, an engineer can recognize the security specifications in a more structured manner to create threat-free software. In our research work, we suggest the Identification of Security Threats during Requirement Engineering (ISTDRE) technique for detecting security risks throughout the requirement engineering process. The four points that make up this ISTDRE technique are Hack Point (HP), Speculation Point (SP), Trust Point (TP), and Reliable Point (RP). The new ISTDRE methodology will be validated using a case study of an ERP system involving two currently used methodologies: Model Oriented Security Requirements Engineering (MOSRE) and System Quality Requirements Engineering (SQUARE).
17
Chen, Yu Ke, and Tai Xiang Zhao. "Data Collection for Medical Data Warehouse Research." Advanced Materials Research 717 (July 2013): 816–19. http://dx.doi.org/10.4028/www.scientific.net/amr.717.816.
Full textAbstract:
We propose an easy method for data collection and central data warehouse design. This method can be used with or without other software development frameworks.We explain thoroughly those aspects that influenced the methodology building.The methodology is defined by four steps, which can be aligned with various iterative development frameworks. We describe here the alignment of our methodology with the RUP(rational unified process) framework.
18
Karľa, Viktor. "Methodology of Research on Transparent Wood in Architectural Constructions." Selected Scientific Papers - Journal of Civil Engineering 15, no. 2 (December 1, 2020): 29–35. http://dx.doi.org/10.1515/sspjce-2020-0015.
Full textAbstract:
Abstract The article describes methodology of research on transparent wood in architectural constructions which is to be held at Faculty of Civil Engineering at Technical University in Košice. The goal is to set multiple stages of research to be able to obtain samples of transparent wood of different species and to evaluate them and subsequently to design constructions suitable for the properties of the obtained material. The aim is to be for the constructions of façade systems and beams of composite cross-section, possibly with the focus on “I” section beams made of transparent wood, but different approaches will also be considered. First, the designs will be evaluated and adjusted using suitable software and after, they will be built and experimentally tested. As the technology at the university will not allow the production of full scale models, some models in scale shall be produced and evaluated in Košice during the upcoming months.
19
HE, XUDONG, and YI DENG. "SPECIFYING SOFTWARE ARCHITECTURAL CONNECTORS IN SAM." International Journal of Software Engineering and Knowledge Engineering 10, no. 04 (August 2000): 411–31. http://dx.doi.org/10.1142/s0218194000000201.
Full textAbstract:
Software architecture has become one of the most active research topics in software engineering in recent years. One of the distinct features of software architecture research is to explicitly study the interconnections (connectors) among system components. In this paper, we show how to formally specify several well-known general connectors in a software architecture methodology called SAM. Related work is discussed and compared. Our results establish the basis for reusing these defined connectors and for building more sophisticated connectors from them.
20
Zhang, Fang, Jian Ping Chen, Chuan Dong Li, and Yan Juan Wu. "Research on Power Flow Control of UPFC Based on PSASP/UPI." Applied Mechanics and Materials 385-386 (August 2013): 1078–81. http://dx.doi.org/10.4028/www.scientific.net/amm.385-386.1078.
Full textAbstract:
The main objective of power flow control for unified power flow controller (UPFC) is to increase the transmission capacity over the existing transmission corridor or line. This paper presents a practical engineering methodology of embedding the power flow control model of UPFC into the commercial software -- power system analysis software package (PSASP) based on its user program interface (UPI) function. In the proposed methodology, the interface currents of UPFC series side and UPFC shunt side between the UPFC device and the network are used to control the transmission line power flow and UPFC bus voltage, respectively. In UPFC series side, the current of UPFC series branch is calculated from the power target equation of the controlled line. In UPFC shunt side, the shunt reactive current of UPFC is used to control the bus voltage. Simulation results on a practical power system show that the proposed methodology can be efficiently applied to the engineering research and analysis of the real power grid with UPFC with good convergence and only one control parameter needed to be prescribed.
21
Tavera Romero, Carlos Andrés, Jesús Hamilton Ortiz, Osamah Ibrahim Khalaf, and Wadys Montilla Ortega. "Software Architecture for Planning Educational Scenarios by Applying an Agile Methodology." International Journal of Emerging Technologies in Learning (iJET) 16, no. 08 (April 23, 2021): 132. http://dx.doi.org/10.3991/ijet.v16i08.20603.
Full textAbstract:
This paper focuses on research related to the difficulties introduced by academic re-sources management in institutions of Higher Education and specifically in the Fundación Universitaria de Popayán, a private university, where the planning of aca-demic scenarios is performed manually at the beginning of each academic period for an average of 1,776 subjects and suitable location for an average of 8,000 students, which leads to determine the importance of considering a software architecture that theoretically supports software development, physically and logically, allowing de-velopment in a successful and reliable way that reduces errors, costs, and time in the results, specifically for the case study at the Fundación Universitaria de Popayán. Therefore, the research has made it possible to find the need for an architectural vision and a base for the effective development of software, supported by the different views of authors with years of research on the subject. The research itself is supported by the agile design thinking methodology, the basis for meeting the needs of the end user, and where the quality attributes workshop method is included in the prototyping phase, which guarantees to involve stakeholders in advance for the control of quality attributes in the project. This article shows the flaws that arise in the academic scenar-io management process and the importance of establishing, from the architecture and agile methodology, a process that remedies the difficulties of the process performed.
22
Joan O Vicente, Aileen, Tiffany Adelaine G Tan, and Alvin Ray O Yu. "Collaborative Approach in Software Engineering Education: An Interdisciplinary Case." Journal of Information Technology Education: Innovations in Practice 17 (2018): 127–52. http://dx.doi.org/10.28945/4062.
Full textAbstract:
Aim/Purpose: This study was aimed at enhancing students’ learning of software engineering methods. A collaboration between the Computer Science, Business Management, and Product Design programs was formed to work on actual projects with real clients. This interdisciplinary form of collaboration simulates the realities of a diverse Software Engineering team. Background: A collaborative approach implemented through projects has been the established pedagogy for introducing the Software Engineering course to undergraduate Computer Science students. The collaboration, however, is limited to collaboration among Computer Science students and their clients. This case study explored an enhancement to the collaborative approach to project development by integrating other related disciplines into the project development framework; hence, the Interdisciplinary Approach. Methodology: This study adopted the case method approach. An interdisciplinary service innovation activity was proposed to invite other disciplines in the learning process of the computer science students. The agile methodology Scrum was used as the software development approach during project development. Survey data were collected from the students to establish (a) their perception of the interdisciplinary approach to project development; (b) the factors that influenced success or failure of their team to deliver the project; and (c) the perceived skills or knowledge that they acquired from the interdisciplinary approach. Analysis of data followed a mixed method approach. Contribution: The study improved the current pedagogy for Software Engineering education by integrating other related disciplines into the software project development framework. Findings: Data collected showed that the students generally accepted the interdisciplinary approach to project development. Factors such as project relevance, teamwork, time and schedule, and administration support, among others, affect team performance towards project completion. In the case of the Computer Science students, results show that students have learned skills during the experience that, as literature reveal, can only be acquired or mastered in their future profession as software engineers. Recommendations for Practitioners: The active collaboration of the industry with the University and the involvement of the other related courses in teaching software engineering methods are critical to the development of the students, not only in learning the methodology but also as a working professional. Recommendation for Researchers: It is interesting to know and eventually understand the interactions between interdisciplinary team members in the conduct of Software Engineering practices while working on their projects. More specifically, what creative tensions arise and how do the interdisciplinary teams handle the discourse? Impact on Society: This study bridges the gap between how Software Engineering is taught in the university and how Software Engineering teams work in real life. Future Research: Future research is targeted at refining and elaborating the elements of the interdisciplinary framework presented in this paper towards an integrated course module for Software Engineering education.
23
Dawood, Omer Salih, and Abd-El-Kader Sahraoui. "From Requirements Engineering to UML using Natural Language Processing – Survey Study." European Journal of Engineering Research and Science 2, no. 1 (January 23, 2017): 44. http://dx.doi.org/10.24018/ejers.2017.2.1.236.
Full textAbstract:
In the paper process of moving from software requirements to UML diagrams has been studied. It shows the importance of this process and discusses many comparative studies in the field. A questionnaire related to the study was distributed worldwide to many research groups, academia, and industry to know the current status of using requirement management tools, knowledge of using UML in software development, frequently used UML diagrams, and the methodology used to generate UML diagrams from requirements. The paper emphasises that there is a need to do some important research in the area of requirements NLP to obtain UML diagrams, and generalize process of using automatic or semi-automatic methodology to generate UML diagrams from requirements.
24
Dawood, Omer Salih, and Abd-El-Kader Sahraoui. "From Requirements Engineering to UML using Natural Language Processing – Survey Study." European Journal of Engineering and Technology Research 2, no. 1 (January 23, 2017): 44–50. http://dx.doi.org/10.24018/ejeng.2017.2.1.236.
Full textAbstract:
In the paper process of moving from software requirements to UML diagrams has been studied. It shows the importance of this process and discusses many comparative studies in the field. A questionnaire related to the study was distributed worldwide to many research groups, academia, and industry to know the current status of using requirement management tools, knowledge of using UML in software development, frequently used UML diagrams, and the methodology used to generate UML diagrams from requirements. The paper emphasises that there is a need to do some important research in the area of requirements NLP to obtain UML diagrams, and generalize process of using automatic or semi-automatic methodology to generate UML diagrams from requirements.
25
Leyer, Michael, and Jürgen Moormann. "Action learning approach to teaching business engineering methodology." Business Process Management Journal 23, no. 1 (February 3, 2017): 130–54. http://dx.doi.org/10.1108/bpmj-06-2015-0092.
Full textAbstract:
Purpose The business engineering (BE) methodology is used to design process-oriented and customer-centred companies in a systematic and holistic way. However, BE demands a high learning effort with regard to the logical flow, instruments and supporting software. The purpose of this paper is to explore which elements of action learning are most useful regarding BE. Design/methodology/approach To enable students to learn BE, a graduate-level course based on action learning is designed. Within a one-week schedule, participants are guided through the three phases of BE covering 31 learning elements. A post-test measures the learning experience. Regression analysis identifies elements that lead to high learning performance. Findings Results from five courses with 79 students reveal that action learning is useful to obtain declarative and procedural knowledge of BE. Learning elements delivering theoretical input and the use of an exemplary case could be reduced, while more time should be devoted to group work on a self-developed case study. Research limitations/implications The paper is based on a specific course design for the topic of BE, which might limit the results’ transferability to other business process management (BPM) teaching areas. However, it provides implications about the decisive elements for learning how to design process-oriented companies. Practical implications The results can be used by instructors to design more meaningful courses on BE. Originality/value The paper delivers new insights into how issues of BPM should be taught. This area, particularly regarding BE, has received little research attention.
26
Lin, Jun, Han Yu, Zhengxiang Pan, Zhiqi Shen, and Lizhen Cui. "Towards data-driven software engineering skills assessment." International Journal of Crowd Science 2, no. 2 (June 11, 2018): 123–35. http://dx.doi.org/10.1108/ijcs-07-2018-0014.
Full textAbstract:
Purpose Today’s software engineers often work in teams to develop complex software systems. Therefore, successful software engineering in practice require team members to possess not only sound programming skills such as analysis, design, coding and testing but also soft skills such as communication, collaboration and self-management. However, existing examination-based assessments are often inadequate for quantifying students’ soft skill development. The purpose of this paper is to explore alternative ways for assessing software engineering students’ skills through a data-driven approach. Design/methodology/approach In this paper, the exploratory data analysis approach is adopted. Leveraging the proposed online agile project management tool – Human-centred Agile Software Engineering (HASE), a study was conducted involving 21 Scrum teams consisting of over 100 undergraduate software engineering students in multi-week coursework projects in 2014. Findings During this study, students performed close to 170,000 software engineering activities logged by HASE. By analysing the collected activity trajectory data set, the authors demonstrate the potential for this new research direction to enable software engineering educators to have a quantifiable way of understanding their students’ skill development, and take a proactive approach in helping them improve their programming and soft skills. Originality/value To the best of the authors’ knowledge, there has yet to be published previous studies using software engineering activity data to assess software engineers’ skills.
27
EL KHARBOUTLY, REHAB A., SWAPNA S. GOKHALE, and REDA A. AMMAR. "ARCHITECTURE-BASED SOFTWARE RELIABILITY ANALYSIS INCORPORATING CONCURRENCY." International Journal of Reliability, Quality and Safety Engineering 14, no. 05 (October 2007): 479–99. http://dx.doi.org/10.1142/s0218539307002751.
Full textAbstract:
With the growing complexity of software applications and increasing reliance on the services provided by these applications, architecture-based reliability analysis has become the focus of several recent research efforts. Most of the prevalent research in this area does not consider simultaneous or concurrent execution of application components. Concurrency, however, may be common in modern software applications. Thus, reliability analysis considering concurrent component execution within the context of the application architecture is necessary for contemporary software applications. This paper presents an architecture-based reliability analysis methodology for concurrent software applications. Central to the methodology is a state space approach, based on discrete time Markov chains (DTMCs), to represent the application architecture taking into consideration simultaneous component execution. A closed form, analytical expression for the expected application reliability based on the average execution times, constant failure rates, and the average number of visits to the components is derived. The average number of visits to application components are obtained from the solution of the DTMC model representing the application architecture. The potential of the methodology to facilitate sensitivity analysis, identification of reliability bottlenecks, and an assessment of the impact of workload and component changes, in addition to providing a reliability estimate, is discussed. To enable the application of the methodology in practice, estimation of model parameters from different software artifacts is described. The methodology is illustrated with a case study. Finally, strategies to alleviate the state space explosion issue for an efficient application of the methodology are proposed.
28
Fronza, Ilenia, Luis Corral, and Claus Pahl. "End-User Software Development: Effectiveness of a Software Engineering-Centric Instructional Strategy." Journal of Information Technology Education: Research 19 (2020): 367–93. http://dx.doi.org/10.28945/4580.
Full textAbstract:
Aim/Purpose: This work aims to introduce and evaluate an instructional strategy that aids end-users with developing their software products during intensive project-based events. Background: End-users produce software in the labor market, and one of the challenges for End-User Software Engineering (EUSE) is the need to create functional software products without a formal education in software development. Methodology: In this work, we present an instructional strategy to expose end-users to Agile-based Software Engineering (SE) practices and enhance their ability to developing high-quality software. Moreover, we introduce a SE approach for the collection of metrics to assess the effectiveness of the instructional strategy. We conducted two case studies to validate the effectiveness of our strategy; the comprehensive analysis of the outcome products evaluates the strategy and demonstrates how to interpret the collected metrics. Contribution: This work contributes to the research and practitioner body of knowledge by leveraging SE centric concepts to design an instructional strategy to lay the foundations of SE competencies in inexperienced developers. This work presents an instructional strategy to develop SE competencies through an intensive and time-bound structure that may be replicated. Moreover, the present work introduces a framework to evaluate these competencies from a product-centric approach, specialized for non-professional individuals. Finally, the framework contributes to understanding how to assess software quality when the software product is written in non-conventional, introductory programming languages. Findings: The results show the effectiveness of our instructional strategy: teams were successful in constructing a working software product. However, participants did not display a good command of source code order and structure. Recommendations for Practitioners: Our instructional strategy provides practitioners with a framework to lay foundations in SE competencies during intensive project-based events. Based on the results of our case studies, we provide a set of recommendations for educational practice. Recommendation for Researchers: We propose an assessment framework to analyze the effectiveness of the instructional strategy from a SE perspective. This analysis provides an overall picture of the participants’ performance; other researchers could use our framework to evaluate the effectiveness of their activities, which would contribute to increasing the possibility of comparing the effectiveness of different instructional strategies. Impact on Society: Given the number of end-user developers who create software products without a formal SE training, several professional and educational contexts can benefit from our proposed instructional strategy and assessment framework. Future Research: Further research can focus on improving the assessment framework by including both process and product metrics to shed light on the effectiveness of the instructional strategies.
29
Joy Kochumarangolil, Jeevamol, and Renumol V G. "Activity Oriented Teaching Strategy for Software Engineering Course: An Experience Report." Journal of Information Technology Education: Innovations in Practice 17 (2018): 181–200. http://dx.doi.org/10.28945/4116.
Full textAbstract:
Aim/Purpose: This paper presents the findings of an Activity-Oriented Teaching Strategy (AOTS) conducted for a postgraduate level Software Engineering (SE) course with the aim of imparting meaningful software development experience for the students. The research question is framed as whether the activity-oriented teaching strategy helps students to acquire practical knowledge of Software Engineering and thus bridge the gap between academia and software industry. Background: Software Engineering Education (SEE) in India is mainly focused on teaching theoretical concepts rather than emphasizing on practical knowledge in software development process. It has been noticed that many students of CS/IT background are struggling when they start their career in the software industry due to inadequate familiarity with the software development process. In the current context of SE education, there is a knowledge gap between the theory learned in the classroom and the actual requirement demanded by the software industry. Methodology: The methodology opted for in this study was action research since the teachers are trying to solve the practical problems and deficiencies encountered while teaching SE. There are four pedagogies in AOTS for fulfilling the requirements of the desired teaching strategy. They are flipped classroom, project role-play for developing project artifacts, teaching by example, and student seminars. The study was conducted among a set of Postgraduate students of the Software Engineering programme at Cochin University of Science and Technology, India. Contribution: AOTS can fulfil both academic and industrial requirements by actively engaging the students in the learning process and thus helping them develop their professional skills. Findings: AOTS can be molded as a promising teaching strategy for learning Software Engineering. It focuses on the essential skill sets demanded by the software industry such as communication, problem-solving, teamwork, and understanding of the software development processes. Impact on Society: Activity-oriented teaching strategies can fulfil both academic and industrial requirements by actively engaging the students in the SE learning process and thus helping them in developing their professional skills. Future Research: AOTS can be refined by adding/modifying pedagogies and including different features like an online evaluation system, virtual classroom etc.
30
Maglyas, Andrey, Uolevi Nikula, Kari Smolander, and Samuel A. Fricker. "Core software product management activities." Journal of Advances in Management Research 14, no. 1 (February 6, 2017): 23–45. http://dx.doi.org/10.1108/jamr-03-2016-0022.
Full textAbstract:
Purpose Software product management (SPM) unites disciplines related to product strategy, planning, development, and release. There are many organizational activities addressing technical, social, and market issues when releasing a software product. Owing to the high number of activities involved, SPM remains a complex discipline to adopt. The purpose of this paper is to understand what are the core and supporting SPM activities. Design/methodology/approach The authors adopted the research method of meta-ethnography to present a set of techniques for synthesizing individual qualitative studies to increase the degree of conceptualization. The results obtained from three empirical studies were synthesized using the meta-ethnography approach to enhance, rethink, and create a higher level abstraction of the findings. Findings The results show that the study has both theoretical and practical contribution. As the meta-ethnography synthesis has not been widely applied in software engineering, the authors illustrate how to use this research method in the practice of software engineering research. The practical contribution of the study is in the identification of five core and six supporting SPM activities. Originality/value The practical value of this paper is in the identification of core SPM activities that should be present in any company practicing SPM. The list of supporting SPM consists of activities that are not reported to product manager but affect the product success.
31
Kohen, Hanan, and Dov Dori. "Improving Conceptual Modeling with Object-Process Methodology Stereotypes." Applied Sciences 11, no. 5 (March 5, 2021): 2301. http://dx.doi.org/10.3390/app11052301.
Full textAbstract:
As system complexity is on the rise, there is a growing need for standardized building blocks to increase the likelihood of systems’ success. Conceptual modeling is the primary activity required for engineering systems to be understood, designed, and managed. Modern modeling languages enable describing the requirements and design of systems in a formal yet understandable way. These languages use stereotypes to standardize, clarify the model semantics, and extend the meaning of model elements. An Internet of things (IoT) system serves as an example to show the significant contributions of stereotypes to model construction, comprehension, error reduction, and increased productivity during design, simulation, and combined hardware–software system execution. This research emphasizes stereotype features that are unique to Object-Process Methodology (OPM) ISO 19450, differentiating it from stereotypes in other conceptual modeling languages. We present the implementation of stereotypes in OPCloud, an OPM modeling software environment, explore stereotype-related problems, propose solutions, and discuss future enhancements.
32
Fannoun, Sufian, and John Kerins. "Towards organisational learning enhancement: assessing software engineering practice." Learning Organization 26, no. 1 (January 14, 2019): 44–59. http://dx.doi.org/10.1108/tlo-09-2018-0149.
Full textAbstract:
Purpose Issues surrounding knowledge management, knowledge transfer and learning within organisations challenge continuity and resilience in the face of changing environments. While initiatives are principally applied within large organisations, there is scope to assess how the processes are handled within small and medium enterprises and consider how they might be enhanced. This paper aims to present an evaluation of practice within an evolving software development unit to determine what has been learned and how the knowledge acquired has been used to further organisational development. These results provide the basis for the design and implementation of a proposed support tool to enhance professional practice. Design/methodology/approach A small software development unit which has successfully delivered bespoke systems since its establishment a number of years ago was selected for analysis. In-depth interviews were carried out with each member of the unit to elicit an understanding of individual and collective development. Interview data were recorded and transcribed and subjected to qualitative analysis to identify key themes underpinning knowledge acquisition and utilisation. Samples of project documentation were scrutinised to corroborate interview data. After analysing the data, a focus-group meeting was held to validate the results and to generate further insights into learning within the unit. Findings Qualitative analysis of the data revealed key changes in thinking and practice within the unit, as well as insight into the development of individual and collective contextual knowledge, tacit understanding and learning. This analysis informed the proposal of a bespoke, lightweight, Web-based system to support knowledge capture and organisational learning. This approach has the potential to promote resilience and enhance practice in similar small or start-up enterprises. Research limitations/implications Purposeful sampling was used in selecting a small software development unit. This enabled in-depth interviewing of all six members of the organisation. This offered a rich environment from which to derive awareness and understanding of individual and collective knowledge acquisition and learning. Focussing on a single small enterprise limits the extent to which the findings can be generalised. However, the research provides evidence of effective practice and learning and has identified themes for the development of a support tool. This approach can be extended to similar domains to advance research into their learning and development. Practical implications Results of the work undertaken so far have generated promising foundations for the proposed support tool. This offers software developers a potentially useful system within which they can reflect upon, and record, key learning events affecting technical, managerial and professional practice. Originality/value Small enterprises have limited resources to support organisational learning. The qualitative research undertaken so far has yielded valuable insight into the successful development of a single software development unit. The construction of a support tool to enhance knowledge acquisition and learning has the capacity to consolidate valuable, and potentially scarce, expertise. It also has the potential to facilitate further research to determine how the prototype might be extended or revised to improve its contribution to the unit’s development.
33
Prokofyeva, Nataly, and Marina Uhanova. "METHODOLOGY OF GROUP WORK ORGANISATION FOR STUDENT LEARNING PERFORMANCE IMPROVEMENT." Environment. Technology. Resources. Proceedings of the International Scientific and Practical Conference 2 (June 15, 2017): 133. http://dx.doi.org/10.17770/etr2017vol2.2558.
Full textAbstract:
The article describes the methodology of learning programming for students of various engineering disciplines. The course "Algorithmization and Programming of Solutions" is taught to all first-year students of the Faculty of Computer Science and Information Technology in Riga Technical University and provides the basic knowledge of the principles of computational process algorithmization and software creation technology using Java programming language. There are 8 laboratory assignments in the course, where students have to develop a software programme and 2 group work assignments, where the student has to develop some algorithms to solve a given problem, write a programme, evaluate the speed of developed algorithms and prepare a presentation on the results of their research. The article describes the main principles of efficient student group work organisation that lets to increase their interest and motivate them to participate in the course in a responsible way. This paper is focused on research on how group work influences student learning performance.
34
Meruňka, V. "Object-oriented approach in requirement engineering for the analysis of information systems." Journal of Forest Science 51, Special Issue (May 17, 2019): 13–18. http://dx.doi.org/10.17221/11843-jfs.
Full textAbstract:
One of the major issues of all analysis techniques in information engineering is to capture the intelligible description of processes in the modeled problem. This need is very significant for information systems supporting modern industries and also information systems related to the agriculture and hydrology. In this area, process modeling forms the basis of Business Process Reengineering as a pre-step for subsequent information system analysis, design and implementation. It provides an essential tool to enable software developers, consultants and business users to collaborate to ensure that the necessary understanding of the business context is available to the software developers. In this paper, practically used technique and methodology for process modeling arousing out of software development methodologies will be discussed. The main described method – BORM (Business and Object Relation Modeling), is a result of own research supported by the Know-how Fund of the British Council.
35
Zulkifli, S. Filzah, CW Shiang, N. Jali, and M. A. Khairuddin. "Modelling emotion expression through agent oriented methodology." Indonesian Journal of Electrical Engineering and Computer Science 16, no. 2 (November 1, 2019): 972. http://dx.doi.org/10.11591/ijeecs.v16.i2.pp972-977.
Full textAbstract:
<span>This paper presents Modelling Emotion Expression through Agent Oriented Methodology. Considering emotions of the intended users in the software engineering can uncover new requirements to improve and more accepted the system. While emotion is paying much attention nowadays, there is lacking systematic way to model the emotion based system. Without the systematic approach, it is hard to debug, design and develop an emotion based system. Since the emotional requirement of people has not being fully investigated, the research outcome propose the emotion modelling as part of the complete set of agent-oriented modelling for virtual character in eLearning system, The contribution of this paper is to introduce agent oriented modelling to systematic model an emotion based solution for an eLearning system and instructional video design. With the emotion model, it can serve as a guide to design, redesign, and discuss the emotion elements among the software development team. This is important for better debugging and project management especially for emotion led system.</span>
36
Mishra, Debasisha. "A study of business knowledge requirements for software projects." Journal of Global Operations and Strategic Sourcing 14, no. 2 (March 22, 2021): 291–311. http://dx.doi.org/10.1108/jgoss-07-2020-0041.
Full textAbstract:
Purpose This paper aims to explore the expertise level required in various kinds of business knowledge such as regulatory, domain, strategic, operation process and, business process to execute globally distributed software projects for development, re-engineering and maintenance projects in the Indian outsourcing software industry. Design/methodology/approach This study adopted a questionnaire survey method to collect the expert responses for a knowledge management framework which is suggested in the literature for software development work. The questionnaire survey findings were verified by expert interviews. Findings The research shows that there is a lot of similarity between re-engineering and maintenance projects for different kinds of business knowledge expertise requirements for execution. The development projects require higher expertise in all the business knowledge for execution. Research limitations/implications The research work studies the business knowledge required for the execution of development, re-engineering and maintenance projects in Indian outsourcing software projects. However, the project’s characteristics can vary drastically for a single kind of project. So the study cannot be generalized and instead should be used as a tool for learning. Practical implications The research findings can be used by software project managers to get insight into project planning, which can help the division of work between the onsite, offshore team and individual work allocation. Originality/value The research is novel as there are very few previous attempts to find the business expertise needed to execute various kinds of software projects in the Indian outsourcing industry.
37
Guha Biswas, Aniruddha, Raveesh Tandon, and Anurika Vaish. "A CASE Tool Evaluation and Selection Methodology." International Journal of Strategic Information Technology and Applications 4, no. 2 (April 2013): 48–60. http://dx.doi.org/10.4018/jsita.2013040104.
Full textAbstract:
CASE Tools have been considered as the most advanced technique to derive quality products. The cost associated with CASE tools is generally high due to their steep learning curves and is a matter of concern for software engineering houses. This makes it imperative that the right set of CASE tools are evaluated and selected for a particular set of tasks. This research paper proposes a methodology for the purpose of comparison and selection of various CASE tools available in the market. The proposed methodology allows its users to easily identify and select the best CASE tool suited to their purpose. The paper proposes a matrix based model, mapped across parameters and their attributes that produces an optimised score card that supports the decision making process.
38
Liu, Ming, Zhonghai Lu, Wolfgang Kuehn, and Axel Jantsch. "A Survey of FPGA Dynamic Reconfiguration Design Methodology and Applications." International Journal of Embedded and Real-Time Communication Systems 3, no. 2 (April 2012): 23–39. http://dx.doi.org/10.4018/jertcs.2012040102.
Full textAbstract:
FPGA Dynamic Partial Reconfiguration (DPR or PR) technology has emerged and become gradually mature in the recent years. It provides the Time-Division Multiplexing (TDM) capability in utilizing on-chip resources and leads to significant benefits in comparison with conventional static designs. However, the partially reconfigurable design process features additional complexity and technical requirements to the FPGA developers. Hence, PR design approaches are being widely explored and investigated to systematize the development methodology and ease the designers. In this paper, the authors collect several research and engineering projects in this area and present a survey of the design methodology and applications of PR. Research aspects are discussed in various hardware/software layers.
39
STEWART, DAVID B., and PRADEEP K. KHOSLA. "THE CHIMERA METHODOLOGY: DESIGNING DYNAMICALLY RECONFIGURABLE AND REUSABLE REAL-TIME SOFTWARE USING PORT-BASED OBJECTS." International Journal of Software Engineering and Knowledge Engineering 06, no. 02 (June 1996): 249–77. http://dx.doi.org/10.1142/s0218194096000120.
Full textAbstract:
The Chimera Methodology is a software engineering paradigm that enables rapid development of real-time applications through use of dynamically reconfigurable and reusable software. It is targeted towards a distributed shared memory computing environment. The primary contribution of this research is the port-based object model of a real-time software component. The model is obtained by applying the port-automaton formal computational theory to object-based design. A finite state machine, detailed interface specifications, and a C-language template are used to define the port-based object. Tools to support the in-tegration, scheduling, and state variable communication between the objects have been developed and incorporated into the Chimera Real-Time Operating System. Techniques for verifying correctness and analyzing performance are also provided for configuration managers that integrate software designed using the port-based object model.
40
Andreu-Andres, Maria-Angeles, Fernando R. Gonzalez-Ladron-de-Guevara, Amparo Garcia-Carbonell, and Frances Watts-Hooge. "Contrasting innovation competence FINCODA model in software engineering: Narrative review." Journal of Industrial Engineering and Management 11, no. 4 (October 10, 2018): 715. http://dx.doi.org/10.3926/jiem.2656.
Full textAbstract:
Purpose: Innovation competences are expected both in businesses and in higher education. Software organizations, in particular, require engineers that collaborate to deliver better services and products. Staff recruitment and training are human resource management tasks that are crucial to insuring that applicants and job holders have the competences that will facilitate quality output in software development processes.This paper seeks to determine the competences that describe high-performing, innovative professionals in software engineering in order to weigh them against the FINCODA model on innovation competences devised to assess and enhance individuals’ capacity to innovate, a core outcome of the Framework for Innovation Competences Development and Assessment Project.Design/methodology/approach: A review protocol was followed to examine the literature on software engineering to identify the innovation competence and behavioral indicators that are required in individuals.Findings: According to the literature, the innovation competences required of the staff in software companies are creativity, critical thinking, initiative, team work and networking, dimensions that are contained in the FINCODA model. Findings also support the inclusion of the thirty-four behavioral indicators that constitute the five dimensions of the FINCODA model.Originality/value: Business organizations need tools to assess innovation competences in employees. Universities, as well, lack the instruments to measure development of innovation competence in undergraduates that teaching/learning methods should enhance before students reach the workplace. This research sheds light on innovative workplace behaviors of software engineers and on feasible designs of training programs for staff and undergraduates by using the FINCODA model and its behavioral indicators. Future research will focus on ratifying the validation of the model and the online assessment tool derived from it.
41
Lino Ferreira da Silva, Maicon Herverton, Augusto José Da Silva Rodrigues, and Elton César Dos Santos Silva. "A Systematic Literature Review for Multimedia Learning Objects Applied to Stewart Platforms Using Software Engineering Methods." International Journal for Innovation Education and Research 7, no. 1 (January 31, 2019): 01–15. http://dx.doi.org/10.31686/ijier.vol7.iss1.1063.
Full textAbstract:
This article describes a systematic literature review (SLR), a methodology to be used in the survey of articles, monographs, dissertations and theses, in scientific databases, to provide a reference bibliography for the construction of multimedia learning objects applied to Stewart platforms, using Software Engineering methods. The bases existent in the literature between the years of 2009 and 2012 were analyzed. The methodology used was based on the adaptation of a revision protocol that suggests for a good SLR, to follow some steps, being: planning, primary reading, formulation of questions for checking if the work fits the subject and classification. The use of SLR assisted in the bibliographic survey process bringing successful results and relevant publications with high impact factors, thus making a solid basis for several works in the research fields.
42
Baron, Philip. "Owning one’s epistemology in religious studies research methodology." Kybernetes 49, no. 8 (November 18, 2019): 2057–71. http://dx.doi.org/10.1108/k-03-2019-0159.
Full textAbstract:
Purpose There is a lack of epistemological considerations in religious studies methodologies, which have resulted in an on-going critique in this field. In addressing this critique, the researcher’s observer effect needs to be actively accounted for owing to the influence of the researcher’s epistemology in the author’s research. This paper aims to answer the question of why a researcher should address one’s epistemology in the research. Design/methodology/approach Using second-order cybernetics as an approach, observer dependence is exemplified and justified in the context of religious studies research methodology. The research activity is shown as a relational temporal coupling that introduces inter-subjective aspects to the research. The research process is analysed showing the need to provide scope for the researcher’s epistemology in one’s research. Findings A relational observer-dependent approach to research embraces the epistemology of the researcher and the participants providing equality in the relationship. The research results are thus framed according to the nature of the relationship and are thus not detached. This addresses social justice and reduces troubling truth claims. Research limitations/implications This first paper focuses on the question of why epistemology should be included in scholarly research. A detailed framework for how scholars may achieve this goal is to be part of the future study and is not presented in this paper. Practical implications In many positivist approaches there is a motivation to hide the researcher; however, recently there has been a move towards including authors in the first person, realising that science is tied to politics, which does not reach its ideals of objectivity. Cybernetics is presented as an approach to addressing the move from “objective” to “subjective” research. Social implications Researchers cannot get into the minds of their participants and thus an authorial privileged presentation by the researcher of the participant’s experiences is fraught with epistemological weaknesses. Attempting to own one’s own epistemology could address social justice in research by personalising the research and accounting for the observer effect and the inter-subjective attributes of the research relationship. Originality/value The principle of observer dependence in cybernetics is not new; however, a research approach that focuses on the nature of knowing and how this may influence one’s research in religious studies is uncommon. It is thus presented here as a viable option to address the critique of epistemologically weak research methodology in religious studies.
43
Aguilar-Calderón, José-Alfonso, Carolina Tripp-Barba, Aníbal Zaldívar-Colado, and Pedro-Alfonso Aguilar-Calderón. "Requirements Engineering for Internet of Things (loT) Software Systems Development: A Systematic Mapping Study." Applied Sciences 12, no. 15 (July 28, 2022): 7582. http://dx.doi.org/10.3390/app12157582.
Full textAbstract:
The Internet of Things (IoT) paradigm is growing, affecting human life and aiming to solve problems in the real world, i.e., in education, healthcare, smart homes, intelligent transportation, and other areas. However, it is a fact that the development of IoT systems is complicated compared to that of traditional software systems, especially in relation to requirements engineering (RE). The RE of IoT systems is not implemented frequently due to their broad aspects, such as the variety of user needs, making these systems difficult to construct. In this sense, the use of loT-based systems has not been well explored by the research community in order to provide well-planned proposals to improve the quality of their performance. In this work, we present a comprehensive and inclusive review of the RE of loT-based systems. To accomplish this, a systematic mapping study (SMS) is presented to evaluate the use of parameters based on the existing literature. SMS is a methodology used for research in the medical field and has recently been implemented in software engineering (SE) to sort and organize research publications to gain knowledge on progress and identify research gaps. In this article, we aim to classify the existing research publications in the current scientific literature regarding RE proposals for IoT software systems and review their implications for future research. This will make it possible to establish lines of research in order to improve the quality of the development of future IoT systems.
44
Huang, Zhengyu, Lingyu Chen, Lianchao Zhang, Shixun Fan, and Dapeng Fan. "Research on software synchronization method of real-time ethernet distributed motion control system." Assembly Automation 39, no. 5 (November 4, 2019): 904–16. http://dx.doi.org/10.1108/aa-12-2018-0265.
Full textAbstract:
Purpose This paper aims to analyze the key factors influencing the synchronization performance of distributed motion control system and to improve the synchronization performance for peripherals control of this system. Design/methodology/approach This paper deals with the software synchronization problems of distributed motion control system based on real-time Ethernet. First, combined with communication and control tasks, the key factors affecting synchronization performance of system are analyzed. Then, aiming at key factors and considering the synchronization of system bus, protocol conversion and task scheduling, a software synchronization method based on CANopen protocol and real-time Ethernet is proposed. Finally, the feasibility of this method is verified by establishing distributed motion control system and testing the synchronization performance of terminal control signals of slaves. Findings Based on this method, the results show that the synchronization accuracy for peripherals control of all slaves could be about 100 ns. Practical implications This research provides high-precision synchronization method, which could lay a foundation for the application of distributed motion control system in the field of assembly automation, such as multi-axis assembly robots control. Originality/value In distributed motion control system, many factors affect the synchronization performance. At present, there is no synchronization method that could comprehensively consider these factors. This paper not only analyzes the key factors influencing the synchronization performance of system but also proposes a synchronization method. Therefore, the method proposed in this paper has certain theoretical value and engineering significance.
45
Jain, Rachna, and Arun Sharma. "ASSESSING SOFTWARE RELIABILITY USING GENETIC ALGORITHMS." Journal of Engineering Research [TJER] 16, no. 1 (May 9, 2019): 11. http://dx.doi.org/10.24200/tjer.vol16iss1pp11-17.
Full textAbstract:
The role of software reliability and quality improvement is becoming more important than any other issues related to software development. To date, we have various techniques that give a prediction of software reliability like neural networks, fuzzy logic, and other evolutionary algorithms. A genetic algorithm has been explored for predicting software reliability. One of the important aspects of software quality is called software reliability, thus, software engineering is of a great place in the software industry. To increase the software reliability, it is mandatory that we must design a model that predicts the fault and error in the software program at early stages, rectify them and then increase the functionality of the program within a minimum time and in a low cost. There exist numerous algorithms that predict software errors such as the Genetic Algorithm, which has a very high ability to predict software bugs, failure and errors rather than any other algorithm. The main purpose of this paper is to predict software errors with so precise, less time-consuming and cost-effective methodology. The outcome of this research paper is showing that the rates of applied methods and strategies are more than 96 percent in ideal conditions.
46
Simperl, Elena, and Markus Luczak-Rösch. "Collaborative ontology engineering: a survey." Knowledge Engineering Review 29, no. 1 (May 3, 2013): 101–31. http://dx.doi.org/10.1017/s0269888913000192.
Full textAbstract:
AbstractBuilding ontologies in a collaborative and increasingly community-driven fashion has become a central paradigm of modern ontology engineering. This understanding of ontologies and ontology engineering processes is the result of intensive theoretical and empirical research within the Semantic Web community, supported by technology developments such as Web 2.0. Over 6 years after the publication of the first methodology for collaborative ontology engineering, it is generally acknowledged that, in order to be useful, but also economically feasible, ontologies should be developed and maintained in a community-driven manner, with the help of fully-fledged environments providing dedicated support for collaboration and user participation. Wikis, and similar communication and collaboration platforms enabling ontology stakeholders to exchange ideas and discuss modeling decisions are probably the most important technological components of such environments. In addition, process-driven methodologies assist the ontology engineering team throughout the ontology life cycle, and provide empirically grounded best practices and guidelines for optimizing ontology development results in real-world projects. The goal of this article is to analyze the state of the art in the field of collaborative ontology engineering. We will survey several of the most outstanding methodologies, methods and techniques that have emerged in the last years, and present the most popular development environments, which can be utilized to carry out, or facilitate specific activities within the methodologies. A discussion of the open issues identified concludes the survey and provides a roadmap for future research and development in this lively and promising field.
47
Dong, Jian Li, Ning Guo Shi, and Yan Yan Chen. "Research on the Realizing Mechanism of an Industrialized PL-ISEE Database Platform." Advanced Materials Research 490-495 (March 2012): 2897–901. http://dx.doi.org/10.4028/www.scientific.net/amr.490-495.2897.
Full textAbstract:
Using the automation production mode of modern manufacturing industry for reference, a new industrialized PL-ISEE (product line based integrated software engineering environment) model was proposed by us in reference [8]. The middle part of the PL-ISEE architecture is data layer which is composed of the software components bus and core assets database platform to achieve the storage and managements of product line core assets data. In this paper, the architecture and its implementation mechanism of the PL-ISEE database platform is further researched. Whole platform architecture consists of core asset objects management service and assets database system. The data model and database schema as well as database views of the database platform are designed and created by using united product line concept model and data model. So, the database supporting platform’s functions and configuration also well satisfy the requirements of interfaces, tools and data integration as well as product line assembling production in the PL-ISEE. Therefore, the design and realizing ideas of the PL-ISEE database platform will be valuable to research product line engineering and methodology in future.
48
LIU, YUBIN, and GANGFENG LIU. "RESEARCH ON RIGID BODY INVERSE DYNAMICS OF A NOVEL 6-PRRS PARALLEL ROBOT." Journal of Mechanics in Medicine and Biology 18, no. 08 (December 2018): 1840037. http://dx.doi.org/10.1142/s0219519418400377.
Full textAbstract:
A systematic methodology for solving the inverse dynamics of a 6-PRRS parallel robot is presented. Based on the principle of virtual work and the Lagrange approach, a methodology for deriving the dynamical equations of motion is developed. To resolve the inconsistency between complications of established dynamic model and real-time control, a simplifying strategy of the dynamic model is presented. The dynamic character of the 6-PRRS parallel robot is analyzed by example calculation, and a full and precise dynamic model using simulation software is established. Verification results show the validity of the presented algorithm, and the simplifying strategies are practical and efficient.
49
Oanta, Emil, and Cornel Panait. "Aspects Regarding the Hybrid Models in Engineering." Advanced Materials Research 837 (November 2013): 141–46. http://dx.doi.org/10.4028/www.scientific.net/amr.837.141.
Full textAbstract:
Physical phenomena in engineering are studied using several types of research instruments. In the class of the theoretical instruments may be considered the analytic and numeric models and the category of the practical approaches includes the experimental studies. However, complex phenomena require information resulted from several types of studies. The integration of the information may be done using original software applications which offer speed, accuracy and flexibility in the context of that certain project. If the research plan considers right from the beginning the integration of the results of different types of studies in a unique investigation methodology, the model of the phenomenon may be considered hybrid. The paper presents several research projects in engineering, the project dedicated to the strains and stresses in the cylinder block is the most complex one and it required several studies of different types, together with original software employed to integrate the data. It may be considered a relevant example of hybrid model. To conclude, the analysis of the phenomenon to be studied must lead to a certain high overview which offers the grounds of a holistic approach in the design of the research plan. Thus, there must be identified all the sources of experimental data, using various experimental techniques, even the redundant information being useful for cross-checking purposes.
50
Bulyha, Kostiantyn, Olena Bulyha, and Kateryna Kotsiubivska. "Application of Software Engineering Methods in Modeling Business Projects in the Service Sphere." Digital Platform: Information Technologies in Sociocultural Sphere 4, no. 2 (December 17, 2021): 219–27. http://dx.doi.org/10.31866/2617-796x.4.2.2021.247486.
Full textAbstract:
The purpose of the research is to substantiate the prospects for the use of software engineering methods in the development of projects of hotel and restaurant business, as well as to demonstrate the capabilities of modern information technology in the design of large hotel businesses. Research methodology. The method of system analysis, structural modeling, as well as CASE-tools of software engineering, in particular the line of CASE-tools BPwin, AllFusion Process Modeler 7, erwin Data Modeler (Erwin user community 2021), which allows automatically building an IDEF0 model of any complexity, are used. The novelty of the research and the practical significance of the obtained results is the possibilities’ demonstration of software engineering methods during the business projects development in the field of services. Conclusions. Innovations are a decisive factor in determining new management technologies in the hotel and restaurant and tourism business. The development of modern information technologies greatly simplifies the stage of designing business processes through a hierarchical representation of objects in the subject area in the form of graphical structures. This makes it possible to provide group work on the creation of the model with the direct involvement of all analysts and specialists involved in the creation of the project. There are a large number of software products that allow you to automate the construction of graphical models. Today their application in the sphere of services is actual. The article gives an example of using CASE-technology to create a functional model of a modern hotel.