Using an object-oriented software life-cycle model in the software engineering course

Author(s):  
Arturo I. Concepcion
2021 ◽  
pp. 115-128
Author(s):  
G. Mirskikh ◽  
◽  
V. Vasyuk ◽  
T. Knizhka ◽  
I. Krisak ◽  
...  

The paper is devoted to the analysis of the software life cycle of engineering objects. To implement the processes and relevant procedures aimed at ensuring, as well as maintaining proper management of the level of software quality at the stages of the life cycle, it is proposed to use the life cycle model as a methodological basis for achieving the goal - achieving the proper level of consumer quality of the final product, taking into account the conditions and circumstances. exploitation.. The considered model of the life cycle in the framework of software engineering is a structure that determines the sequence of implementation and relationships of processes and procedures of a different nature that may arise when performing any actions in relation to software, from the emergence of a need for this software and ending with its final withdrawal from use. If necessary, the life cycle model has a relationship with the content, scale and complexity of the corresponding project, on the characteristics of the conditions and circumstances under which a particular software is created and operated. At the same time, the existence of a life cycle model, carefully developed at the same time, adequate to the existing conditions and circumstances, is the basis for the implementation of general quality management within the framework of a program project, which at this point in time is stipulated as a methodological basis for obtaining a project at the output of an object that meets the presented requirements and modern quality standards. The main reasons for the need to pay special attention to modeling the life cycle of the software being developed and the component of the environment surrounding the software at different stages of its life cycle, taking into account the life cycle of material engineering objects, are presented. Taking into account the presented concept of the life cycle implementation in some virtual enterprise, the software sequentially performs the transition from one state to the next, from consumer properties specified by the customer to an already finished software product and quite real consumer properties supported by the corresponding characteristics, this software is in operation to moral aging, and also goes into a state characterized by the modernization or removal of this software from use. Key words: software, engineering object, software life cycle model, software development, engineering activities


Author(s):  
Chuyang Dong ◽  
Haihong Fang ◽  
Hongjie Zhang ◽  
Yuexi Wang ◽  
Xianqing Ling

Author(s):  
Abad Shah

Today, the Internet and the Web are the most amazingly and dynamically growing computer technologies. The number of users accessing the Web is growing exponentially all over the world. The Web has become a popular environment for new generation of interactive computer applications called Web (or hypermedia) application. The Web applications (WAs) have special characteristics that have made them different from other traditional applications. Hence, many design methodologies for the development of WAs have been proposed. However, most of these methodologies concentrate on the design aspects of applications, and they often do not strictly follow any software development life-cycle model such as the WaterFall software development life-cycle model. In this chapter, we propose an object-oriented design methodology for the development of WAs. The main features of this proposed methodology are that it follows WaterFall model and captures the operations in objects of the applications; thus making the methodology an object-oriented methodology.


Author(s):  
F. ALONSO ◽  
N. JURISTO ◽  
J. PAZOS

The ten-year gap between the emergence of Software Engineering (SE) and Knowledge Engineering (KE) has led to the two disciplines developing along different methodological lines. In this paper, we point out that, after having passed through a period during which they ignored each other, followed by a competitive phase, the two disciplines have now reached a meeting point. We see the need for a life-cycle model for systems that integrate traditional and knowledge-based software. Besides, software development in the 21st century will entail open requirements and technological tools that will evolve during the life-cycle. Finally, the paper discusses a proposal for a conical-type spiral life-cycle model that seeks to meet all those needs.


2018 ◽  
Vol 6 (1) ◽  
pp. 42-48
Author(s):  
S. J. Kalayathankal ◽  
◽  
J. T. Abraham ◽  
J. V. Kureethara ◽  
◽  
...  

Sign in / Sign up

Export Citation Format

Share Document