Archit Kaila
Archit Kaila
A00077698
The Discontinuity in the field of Software Engineering and Software Engineering as a Profession
Research Questions
Over the past twenty years, software engineering has seen numerous changes. The function of software engineering has increasingly shifted from creating corporate programs required to run desktop computers with numerous clients to creating artificial intelligence-powered technology that affects carriers and daily lives. Software engineering is now a highly sought-after profession in Australia and around the world as a result of rising professional utilization across all industries. Therefore, it is imperative to assess the future of software engineering in light of recent technological developments like robotics and AI, which will soon rule the planet. The major inquiries raised by this study are
How will new and upcoming technological breakthroughs affect the profession of software engineering today and in the future?
How has the field of software engineering affected developers' lives and how has it changed?
What conditions must be met to guarantee that jobs in the field of software engineering are successful?
Aims and Objectives
The objective of this research is to understand the conditions and trends of software engineering professionals. The main focus of this study is to understand the software engineering profession from the beginning to the present day. This study will also help us to understand the growth of software engineering as a profession in Australia and around the globe. This study will help us to understand how software engineering is one of the most demanding careers in the world in the modern day. The objectives that came up from this research are
To understand software engineering as a profession with the development of new technology in the future.
Find out the evolution of the software engineering profession and what is its effect on the lives of developers.
To know the main factors necessary to ensure that software engineering professional has achieved optimal outcomes in their careers.
Comparative analysis of research methodology's
Qualitative research methodology
The qualitative research methodology utilizes data that is nonnumerical such as personal experiences or ideas and views which are related to the research topic. Qualitative research is employed when it is intended to get in-depth insights related to a specific issue covered in the studies or when new research questions need to be generated (Jonathan Sillito, 2007). Researchers utilize grounded theory when they want to collect extensive data on a certain subject and inductively created ideas. There is a chest that is used to learn about various tribes' traditions by adding new graffiti. Research is applied when a participant's life experiences are utilized to understand an event or phenomenon. The use of narrative research allows us to evaluate participant accounts of their encounters with the study's issue and the scientists (Seaman, 2008).
The use of qualitative research is advantageous for the software engineering field because it is a source of original creativity or content, provides helpful industry-specific insights, incorporates the human experience of software engineering professionals, and is a low-cost method. The researchers find it simpler to comprehend attitudes in my qualitative study. Focus groups, interviews, secondary research, service learning, and observations are some of the research methodologies used in qualitative studies. Researchers utilize observation to document information they have seen, heard, or encountered during fieldwork, whereas interviews involve one-on-one discussions with software engineering professionals. Open surveys are conducted involving software engineering professionals to gain insights. To learn the answers to research questions, the finest country research comprises acquiring data in written, audio, or fictitious formats. Focus groups also involve good conversation among a group of software engineering professionals.
Qualitative research has several problems, including the reliance on the researcher's experience for accurate results, the likelihood of data loss, the potential for false conclusions, the difficulty of duplicating results, and the lack of a quantifiable method of data collection (Tore Dyb,2011)
Quantitative Research
Quantitative research includes numerical data that can be generated from a computer oh by any mathematical approach. When compared to qualitative research, it is different. Quantitative research data are used to identify trends and averages, explore causal links, generate forecasts, and draw broad generalizations about a sizable population. Due to the meticulous experiment design that goes into quantitative research, it has the benefit of making the data tested and checked, making it more trustworthy and less subject to debate the use of statistical tests and the elimination of error-causing cases leads to a clear analysis using the turn approach. Because it uses intricate statistical techniques and analysis, quantitative research is regarded as a prestige method (Di Penta 2017). Numerous problems exist with this technique, including a misplaced emphasis on statistics, the challenge of constructing a study model, and outcomes that may be deceptive (Tamburri 2017). It might explain the condition of the specific variable that the researcher is using in descriptive research. It offers organized data about the pillar phenomenon. When attempting to understand the relationship between two or more variables using numerical data from correlational research. However, secondary research and surveys may be utilized in both forms of study. The third distinction between quantitative and qualitative research is that one employs numerical data while the other uses non-numeric data, and the research procedures and methods employed in each are likewise different (Sjoberg et al., 2007)
Mixed Research Method
This approach incorporates a philosophy known as assumptions, which is used to guide both qualitative and quantitative research in a single study. Researchers can employ a combination of qualitative and quantitative research methodologies to better understand the research subject they are addressing. Mixed arithmetic thirds, (Easterbrook et al., 2008), offer a significant opportunity to develop novel approaches to fully comprehending the intricacies and interconnections of social experience, enhancing the researcher's capacity to draw social generalizations and provide explanations. When employing both qualitative and quantitative procedures, the software engineering professional may fully and synergistically utilize the data since mixed methods have this benefit. It is simpler for researchers to clarify and confirm the outcomes of one approach with the findings from the other method since the methodologies are complementary. Research findings from one approach are utilized to further the application of the other as a consequence of the usage of mixed methodologies.
Conducting research using mixed techniques has several drawbacks. The difficulty of doing research is one of its drawbacks since it entails several obstacles. To finish the study, a significant amount of time and resourcesincluding moneyare needed. Additionally, since writing qualitative and quantitative descriptions is frequently challenging, researchers employing the approach should possess a wide variety of abilities. A plan for a study. When using this strategy, both types of data are collected and analyzed simultaneously. When the research requires contextualization, trustworthiness, and generalizability, the Mixed Method is acceptable.
Proposed Methodology and methods
The research can be conducted using any of the three ways. Since qualitative research is based on observations and ideas, it provides an in-depth understanding of the subject; quantitative research will produce reliable results, and blended approaches will produce more thorough and reliable results. Quantitative and mixed-method studies, however, take a lot of time and effort. Data accuracy is more in Quantitative analysis.Consequently, qualitative research is suggested. If the appropriate sample and analysis are utilized, the process is straightforward, doesn't take too long, and can produce accurate findings. The study topics are addressed through a methodology that involves asking software engineers about their perceptions on and experiences with their careers. Open-ended surveys are part of the methodology. This methodology also includes one-to-one interviews. Also, focus groups are part of this methodology.
References
Tore Dyb, Rafael Prikladnicki, Kari Rnkk, Carolyn Seaman & Jonathan Sillito. (2011). Qualitative research in software engineering. Empirical Software Engineering, 16, 425429.
Seaman, C. B. (2008). Qualitative methods. Guide to Advanced Empirical Software Engineering, 35-62. https://doi.org/10.1007/978-1-84800-044-5_2Di Penta, M., & Tamburri, D. A. (2017). Combining quantitative and qualitative studies in empirical software engineering research. 2017 IEEE/ACM 39th International Conference on Software Engineering Companion (ICSE-C). https://doi.org/10.1109/icse-c.2017.163Sjoberg, D. I., Dyba, T., & Jorgensen, M. (2007). The future of empirical methods in software engineering research. Future of Software Engineering (FOSE '07)
Easterbrook, S., Singer, J., Storey, M., & Damian, D. (2008). Selecting empirical methods for software engineering research. Guide to Advanced Empirical Software Engineering, 285-311.
Borrego, M., Douglas, E. P., & Amelink, C. T. (2009). Quantitative, qualitative, and mixed research methods in engineering education. Journal of Engineering Education, 98(1), 53-66.
Al-Taani, R. H., & Razali, R. (2016). A framework for requirements prioritization process in an Agile software development environment: Empirical study. International Journal on Advanced Science, Engineering and Information Technology, 6(6), 846.
Lee, A. S., & Liebenau, J. (1997). Information systems and qualitative research. Information Systems and Qualitative Research, 1-8.
Archit Kaila
A00077698
The Discontinuity in the field of Software Engineering and Software Engineering as a Profession
Abstract
From the initial phase of software engineering, this field has developed immensely. There are many obstacles in this field like discontinuity and lag. Also, people from around the world have their strengths in different areas and the same weakness when it comes to the development of the software industry. In software engineering, computer usage is very extensive to complete different tasks. This proposal examines the issues involved in professional software engineering. These problems pan the gamut from fundamental concerns like preventing software disconnects and gaps in software engineering categories and other important elements. By annotating the bibliography, the report will analyze different research.
the programmers and the tech giants must consider the business element or software development. Software engineers are one of the top-paid people around the world but it still depends upon the location common knowledge and experience of the person. A company that employs 30,600 talks very genius and is still looking to grow because of the tremendous demand for software engineering among people. the purpose of this research is to have insight into this profession's direction. this research will also help in understanding how the software engineering field has developed in various areas. This will also highlight the parts of the profession that affect software developers lives.
Research Question
What are the required changes in the field of software engineering to gain the best results in business and teaching careers as well?
Aim
To investigate the impact of discontinuity in various parts of software engineering.
Objectives
The objective of this research is to exhibit the expansion of the software engineering field. This research will show how all the developments in this field will affect the various business activities will stop nowadays any company in the world is dependent on their software developers because they are the one who manages most of the operations of the company like supply chain and others. This study of software engineering will also help in understanding how this profession can help in developing other disciplines.
Annotating Bibliography
R.L. Glass, I. Vessey, V. Ramesh, Research in software engineering: an analysis of the literature, Information and Software Technology, Volume 44, Issue 8, 2014, Pages 491-506, ISSN 0950-5849.
The authors study many facts of software engineering and are affiliated with Indiana University's Kelley School of Business. The authors research focuses on the areas of software management, the software development life cycle, software engineering approaches, software applications, and software reengineering. Developers that studied the caps in each software area between 2008 and 2012 advanced each discussed topic (Glass,2014). Little research was conducted on each software engineering area in 2008, 2009, and 2010, however, this increased significantly in 2011. The study found that there needs to be more research done on software engineering. According to the authors, this sector has greater potential, thus developers should make sure to conduct a more thorough study as part of the software reengineering process.
O'Connor, R. V., Elger, P., & Clarke, P. M. (2017). Continuous software engineeringA microservices architecture perspective. Journal of Software: Evolution and Process, 29(11), e1866.
The authors are from Dublin City University, Glasnevin, Ireland. Their research is based on the harms caused by the disconnects in software engineering. When developers perform main activities that are just development, implementation, and planning, their search done by authors is on top where disconnects and their harm and observed that it results in the performance of tasks which are not happening often like testing releases, integration, and planning. The issues Between software development and development discontinuity are solved by continuous integration as suggested by the research DevOps as suggested by modern developers indicates that software development and operational development are continuous (Elger,2017). Hey, continuity is needed to ensure resilience in the comprehensive data-intensive systems developed in modern times as this connection between business strategy end development is not good. The authors table activities to provide success to the process and they emphasize continuous software engineering. An ongoing software engineering delivery process is suggested in the paper.
Stapic, Z., Lpez, E. G., Cabot, A. G., de Marcos Ortega, L., & Strahonja, V. (2012). Performing systematic literature review in software engineering. In Central European Conference on Information and Intelligent Systems (p. 441). Faculty of Organization and Informatics Varazdin.
The authors are from the University of Zagreb Pavlinska, Varadin, Croatia. The evidence-based software engineering as proposed by the author to accumulate empirical studies and do systematic literature reviews to perform research in software engineering. The author emphasized the use of SLR technology and discussed the SLR end quality assessment of primary studies. The author emphasizes using SLRs in education and the adoption of mapping and scoping studies. It is necessary to recognize the recent direction of software engineering using guidelines for performing SLRs (Lopez,2012). this aspect helps to recognize the recent policies which are needed to amend and use recent knowledge of SLRs in software engineering.
Santos, G., Kalinowski, M., Rocha, A. R., Travassos, G. H., Weber, K. C., & Antonioni, J. A. (2010, September). MPS. BR: A tale of software process improvement and performance results in the Brazilian software industry. In 2010 Seventh International Conference on the Quality of Information and Communications Technology (pp. 412-417). IEEE.
The authors are from the Department of Applied Informatics, the Federal University of the State of Rio de Janeiro (UNIRIO) Rio de Janeiro, Brazil. The paper embodies the concept of software quality in the field of software engineering, which academics focused on in 2010. The author contrasts CMMI with locally produced MPSBR programs. by concentrating on the advancements inside the software sector. Because process engineering and software quality are related The author discussed the factors affecting software quality in the software business. The author concluded that software improvement adheres to the goal and global standards for software quality. The author claims that there is no connection between strategic vision techniques and software engineering paradigms. The primary component of software quality programs and continual software product evolution is strategic planning (Rocha,2010). The majority of studies are required, as the research suggests, to ensure increased visibility of strategic challenges in the software sector. The Brazilian author's research is irksome since it only covers a small portion of the software engineering sector.
Biffl, S., Aurum, A., Boehm, B., Erdogmus, H., & Grnbacher, P. (Eds.). (2006). Value-based software engineering (Vol. 1). Springer-Verlag Berlin Heidelberg.
The authors are from In the institute for Software Technology, Vienna University of Technology, Wien, Austria. When creating software products, the authors take both business and technical considerations into account. Value-based software, which distinguishes itself from other standard software programs, measures the financial effects on business. Different requirements engineering activities enhance the commercial value of software products, and requirement prioritizing is the primary RE decision-making activity (Boehm,2006). For the best business practices, developers should use a variety of methods for prioritizing requirements. These procedures must support the prioritization process for the development of value-based systems. The authors found that the most recent strategies for needs prioritization do not effectively exploit the technical features. Business considerations must be incorporated into value-based systems development for it to be successful, and a multi-aspect requirement prioritizing technique must be introduced for candidate requirements for value-based software development. The authors are concentrating on the novel needs prioritizing methods for value-based systems.
Jazayeri, A., & Bass, E. J. (2020). Agent-oriented methodologies evaluation frameworks: a review. International Journal of Software Engineering and Knowledge Engineering, 30(09), 1337-1370.
The authors are from the Department of Information Science, College of Computing & Informatics, Drexel University, Philadelphia, USA. The authors noted that creating applications in complicated areas necessitates software engineering expertise. The authors' primary focus is on the difficulties of agent-based computing, and they also acknowledge that the discipline has not yet gained widespread acceptance in the profession of software engineering. Additionally, there havent been many efforts put into turning agent-oriented software abstractions into useful tools that can manage the complexity of contemporary application domains (Bass, 2020). The authors divide the problems with agent-based computing into three categories: macro, micro, and mesa skills. These categories are then utilized to provide alternative answers to each problem.
Referencing
R.L. Glass, I. Vessey, V. Ramesh, Research in software engineering: an analysis of the literature, Information and Software Technology, Volume 44, Issue 8, 2014, Pages 491-506, ISSN 0950-5849.
O'Connor, R. V., Elger, P., & Clarke, P. M. (2017). Continuous software engineeringA microservices architecture perspective. Journal of Software: Evolution and Process, 29(11), e1866.
Stapic, Z., Lpez, E. G., Cabot, A. G., de Marcos Ortega, L., & Strahonja, V. (2012). Performing systematic literature review in software engineering. In Central European Conference on Information and Intelligent Systems (p. 441). Faculty of Organization and Informatics Varazdin.
Santos, G., Kalinowski, M., Rocha, A. R., Travassos, G. H., Weber, K. C., & Antonioni, J. A. (2010, September). MPS. BR: A tale of software process improvement and performance results in the Brazilian software industry. In 2010 Seventh International Conference on the Quality of Information and Communications Technology (pp. 412-417). IEEE.
Biffl, S., Aurum, A., Boehm, B., Erdogmus, H., & Grnbacher, P. (Eds.). (2006). Value-based software engineering (Vol. 1). Springer-Verlag Berlin Heidelberg.
Jazayeri, A., & Bass, E. J. (2020). Agent-oriented methodologies evaluation frameworks: a review. International Journal of Software Engineering and Knowledge Engineering, 30(09), 1337-1370.
