The Future of Software Engineering by 2050

According to the huge criticality of using advanced software systems and the great demands of providing updated and qualified programs, this paper reflects some future perspectives towards the importance of software in managing everything in the world life over the next thirty years. Moreover, the paper presents the challenges which face the recent and the future generations as a result of this huge revolution of technology and automations. In addition to that, the writer would provide some solutions for those obstacles in order to enhance the role of software engineers in 2050. Also the paper reviews the related literature and surveys the point of view of software engineering experts by assigning an online interview with six open ended questions to examine their perspectives towards the future of Internet of things, Artificial intelligence, ubiquitous computing, and system of systems. The majority of ideas reflected the humanity fears of technology and replacing people with robots in the job fields. Furthermore, some experts encouraged the idea of having smart homes, and wearable devices Keywords: advanced Software; system of systems; 3D building printer, internet of things, artificial intelligence, ubiquitous computing, and system of systems. DOI: 10.7176/CEIS/11-2-06 Publication date: April 30th 202

Requirements: The Key to Sustainability

Software's critical role in society demands a paradigm shift in the software engineering mind-set. This shift's focus begins in requirements engineering. This article is part of a special issue on the Future of Software Engineering

The future of software engineering: Visions of 2025 and beyond

In the current technological scenario of the industry and businesses, there has been increasing need of software within systems and also an increasing demand being put onto software-intensive systems. This in effect will lead to a significant evolution of software engineering processes over the next twenty years. This is due to the fact of emerging technological advancements like Industry 4.0 and Internet of Things in the IT field, among other new developments. This paper addresses and tries to analyses the key research challenges being faced by the software engineering field and articulates information that is derived from the key research specializations within software engineering. The paper analyses the past and current trends in software engineering. The future of software engineering is also looked with respect to Industry 4.0 which including emerging technological platforms like Internet of Things. The societal impact aspect of future trends in software engineering is also addressed in this paper

Automatic program generation: future of software engineering

At this moment software development is still more of an art than an engineering discipline. Each piece of software is lovingly engineered, nurtured, and presented to the world as a tribute to the writer's skill. When will this change. When will the craftsmanship be removed and the programs be turned out like so many automobiles from an assembly line. Sooner or later it will happen: economic necessities will demand it. With the advent of cheap microcomputers and ever more powerful supercomputers doubling capacity, much more software must be produced. The choices are to double the number of programers, double the efficiency of each programer, or find a way to produce the needed software automatically. Producing software automatically is the only logical choice. How will automatic programing come about. Some of the preliminary actions which need to be done and are being done are to encourage programer plagiarism of existing software through public library mechanisms, produce well understood packages such as compiler automatically, develop languages capable of producing software as output, and learn enough about the whole process of programing to be able to automate it. Clearly, the emphasis must not be on efficiency or size, since ever larger and faster hardware is coming

One system, two ideologies: integrating the two worlds of software engineering education

In software engineering education, there are two contradicting ideologies. One ideology emphasizes on the popular methods such as object-oriented analysis and design. The other ideology advocates formal methods. Although both have advantages, there are also inherent drawbacks. In view of this, it is advocated that the future of software engineering education lies in integrating these two ideologies.published_or_final_versio

Towards semantic software engineering environments

Software tools processing partially common set of data should share an understanding of what these data mean. Since ontologies have been used to express formally a shared understanding of information, we argue that they are a way towards Semantic SEEs. In this paper we discuss an ontology-based approach to tool integration and present ODE, an ontology-based SEE

The future of AOSE: exploiting SME for a new conception of methodologies

In the last years, the software engineering eld has provided developers with dierent methodologies to support their work. Nevertheless, existing methodologies can hardly meet the requirements of all existing scenarios, which are more and more complex and highly dierentiated. This problem can be faced by applying the Situational Method Engineering (SME) approach, which enables to build appropriate methodologies by composing \fragments" of existing ones. We envision this approach as the future of software engineering in general, and in particular if applied in Agent Oriented Software Engineering (AOSE). This approach has also the valuable advantage of reusing models, solutions, experiences and tools of existing and tested methodologies. In this paper we report three examples of application of the Situational Method Engineering approach in AOSE. We show that this approach can be applied following dierent directions, and in particular: entity-driven, metamodel-driven, and characteristic-driven. To concretely show these directions, we present three examples of methodologies for developing agent systems (one regarding self-organising systems), all constructed composing methodology fragments to meet the scenario requirements