Software Engineering Aspects of Continuous Development and New Paradigms of Software Production and Deployment

Author(s):  
Sergey Zykov

Software development is critically dependent on a number of factors. These factors include techno-logical and anthropic-oriented ones. Software production is a multiple party process; it includes customer and developer parties. Due to different expectations and goals of each side, the human factors become mission-critical. Misconceptions in the expectations of each side may lead to misbalanced production; the product that the developers produce may significantly differ from what the customers expect. This misbalanced vision of the software product may result in a software de-livery crisis. To manage this crisis, the authors recommend using software engineering methods. Software engineering is a discipline which emerged from the so-called “software crisis” in the 1960s: it combines technical and anthropic-oriented “soft” skills. To conquer the crisis, this chapter discusses general architecture patterns for software and hardware systems; it provides instances of particular industries, such as oil and gas and nuclear power production.


2018 ◽  
Vol 7 (2.29) ◽  
pp. 772 ◽  
Author(s):  
Muhammad Ali Ramdhani ◽  
Dian Sa’adillah Maylawati ◽  
Abdusy Syakur Amin ◽  
Hilmi Aulawi

Software Engineering (SE) is a discipline, concept, method that focus on all aspects related to software production. SE must adapt organized system and approach in building software. The objective of this article is to discuss needs elicitation in SE, so that the design can be done through utilizing appropriate tools and techniques based on the problem to be solved, restrictions and need that must be met, as well as resource availability. The method used in this article is literature review as a major source of problem analysis. In the next phase, the main topic of the article is clarified, validated, and verified by the model of the Focus Group Discussion (FGD). The respondents of FGD are lecturers of Informatics Department at UIN Sunan Gunung Djati Bandung. Requirements elicitation is in-dept and comprehensive process of finding information from all stakeholders in relation to the built software. The result of requirements elicitation is the explanation from every stakeholder with natural language related to the will and interest of the built software. The mechanism of finding information can be done through observation, questionnaire, interview, and documentary study, which are then tested with data validation and verification in FGD. The product of requirements elicitation is the User Requirement Document (URD) that can be used as an early artifact in software development process. Furthermore, URD is used as a reference in tracking the suitability between the function of software and the needs of stakeholder. This article formulated analysis approach of SE need, so that it is easily modified, adaptive to growing software complexity, and connected with the analysis of hardware. 


2022 ◽  
pp. 59-73
Author(s):  
Denis Pashchenko

Competition in industry of software production as well as in IT sector has special features. Understanding current trends and complex connections between software industry and world economic development gives new ideas about competition in the IT domain. One of the key trends is digital transformation. It is supported by software, but it also has a strong impact on the software development industry and provides the new opportunities in software production and IT business change management. The main idea of the paper is total automation and a focus on measurable processes that give a continual flow of digital data that should be used on different levels of a company's management, business development, production processes, and even client's perception of the software product. Management of those core activities, based on such digital data flows, is becoming sophisticated and more flexible, based on relevant and estimated indicators. In this article, there is a multifactor analysis of digitalization in software engineering and IT business management with a focus on change management. The main results of research are demonstrating how the influence of digitalization could be used in competition.


Author(s):  
Sergey Zykov

Software development is critically dependent on a number of factors. These factors include techno-logical and anthropic-oriented ones. Software production is a multiple party process; it includes customer and developer parties. Due to different expectations and goals of each side, the human factors become mission-critical. Misconceptions in the expectations of each side may lead to misbalanced production; the product that the developers produce may significantly differ from what the customers expect. This misbalanced vision of the software product may result in a software de-livery crisis. To manage this crisis, the authors recommend using software engineering methods. Software engineering is a discipline which emerged from the so-called “software crisis” in the 1960s: it combines technical and anthropic-oriented “soft” skills. To conquer the crisis, this chapter discusses general architecture patterns for software and hardware systems; it provides instances of particular industries, such as oil and gas and nuclear power production.


2021 ◽  
Vol 46 (1) ◽  
pp. 23-24
Author(s):  
Shin Yoo ◽  
Aldeida Aleti ◽  
Burak Turhan ◽  
Leandro L. Minku ◽  
Andriy Miranskyy ◽  
...  

The International Workshop on Realizing Arti cial Intelligence Synergies in Software Engineering (RAISE) aims to present the state of the art in the crossover between Software Engineering and Arti cial Intelligence. This workshop explored not only the appli- cation of AI techniques to SE problems but also the application of SE techniques to AI problems. Software has become critical for realizing functions central to our society. For example, software is essential for nancial and transport systems, energy generation and distribution systems, and safety-critical medical applications. Software development costs trillions of dollars each year yet, still, many of our software engineering methods remain mostly man- ual. If we can improve software production by smarter AI-based methods, even by small margins, then this would improve a crit- ical component of the international infrastructure, while freeing up tens of billions of dollars for other tasks.


2009 ◽  
Vol 5 (2) ◽  
Author(s):  
Giuseppe Cocco ◽  
Gilvan De Oliveira Vilarim

Resumo O artigo discute conceituações sobre a hegemonia do trabalho imaterial, focalizando sua produção cooperativa e a mobilização de subjetividades no capitalismo cognitivo; a produção de software é utilizada para identificar e analisar as características do trabalho imaterial. É feito um retrospecto da criação de software das suas origens até o momento atual da computação em nuvem e do software como serviço. Ressaltam-se as limitações da abordagem industrial para o software e a valorização e resistência de um trabalho vivo capaz de prover inovação nas condições de produção imaterial.Palavras-chave trabalho imaterial; capitalismo cognitivo; engenharia de software; computação em nuvemAbstract The article discusses conceptualizations about the hegemony of immaterial labor, focusing on its cooperative production and mobilization of subjectivities within cognitive capitalism; software production is used to identify and analyze the characteristics of immaterial labor. A historical review of software creation is made, from its origins to the present time of cloud computing and software as a service. We emphasize the limitations of an industrial approach to software and the valorization and resistance of a living labor which is able to provide innovation in terms of immaterial production.Keywords immaterial labor; cognitive capitalism; software engineering; cloud computing


1993 ◽  
Vol 22 (2) ◽  
pp. 155-172 ◽  
Author(s):  
Simon C-H Wong

Educational software developers have been criticized for the lack of software engineering methodologies and principles in their analysis and design and therefore have led to low quality products. This article introduces and demonstrates the “quick” or “rapid” prototyping software engineering paradigm which can be easily employed by causal software designers such as classroom teachers using object-oriented software production tools. Development of an educational software called “The Match-Maker,” a game for learning new words, is used as an example using HyperCard™ and its scripting language, HyperTalk™, for quick prototyping. The flexibility and suitability of the object-oriented hypermedia for quick prototyping are identified. Software engineering principles involved in various development stages are presented. Good programming styles and design principles which can be implemented at ease in the object-oriented environment are also discussed.


Author(s):  
ANTHONY S. KARRER ◽  
WALT SCACCHI

Researchers who create software production environments face considerable problems. Software production environments are large systems that are very costly to develop. Furthermore, software production environments which support particular software engineering methods may not be applicable to a large number of software production projects. These conditions have formed a trend towards research into ways which will lessen the cost of developing software production environments. In particular, the trend has been towards the construction of meta-environments. In this paper, we attempt to categorize current meta-environment approaches. For each of the categories, we review research efforts which illustrate different approaches within that category. We conclude by presenting an emerging common thread of requirements which links this field together.


Sign in / Sign up

Export Citation Format

Share Document