Theory Driven Modeling as the Core of Software Development

Author(s):  
Janis Osis ◽  
Erika Nazaruka (Asnina)

Some experts opine that software is built in a primitive way. The role of modeling as a treatment for the weakness of software engineering became more important when the principles of Model Driven Architecture (MDA) appeared. Its main advantage is architectural separation of concerns. It showed the necessity of modeling and opened the way for software development to become an engineering discipline. However, this principle does not demonstrate its whole potential power in practice because of lack of mathematical accuracy in the very initial steps of software development. The sufficiency of modeling in software development is still disputable. The authors believe that software development in general (and modeling in particular) based on mathematical formalism in all of its stages and together with the implemented principle of architectural separation of concerns can become an important part of software engineering in its real sense. They propose the formalism by topological modeling of system functioning as the first step towards engineering.

Author(s):  
Janis Osis ◽  
Erika Nazaruka (Asnina)

Some experts opine that software is built in a primitive way. The role of modeling as a treatment for the weakness of software engineering became more important when the principles of Model Driven Architecture (MDA) appeared. Its main advantage is architectural separation of concerns. It showed the necessity of modeling and opened the way for software development to become an engineering discipline. However, this principle does not demonstrate its whole potential power in practice because of lack of mathematical accuracy in the very initial steps of software development. The sufficiency of modeling in software development is still disputable. The authors believe that software development in general (and modeling in particular) based on mathematical formalism in all of its stages and together with the implemented principle of architectural separation of concerns can become an important part of software engineering in its real sense. They propose the formalism by topological modeling of system functioning as the first step towards engineering.


Author(s):  
Janis Osis ◽  
Erika Asnina

Experts' opinions exist that the way software is built is primitive. The role of modeling as a treatment for Software Engineering (SE) became more important after the appearance of Model-Driven Architecture (MDA). The main advantage of MDA is architectural separation of concerns that showed the necessity of modeling and opened the way for Software Development (SD) to become engineering. However, this principle does not demonstrate its whole potential power in practice, because of a lack of mathematical accuracy in the initial steps of SD. The question about the sufficiency of modeling in SD is still open. The authors believe that SD, in general, and modeling, in particular, based on mathematical formalism in all its stages together with the implemented principle of architectural separation of concerns can become an important part of SE in its real sense. They introduce such mathematical formalism by means of topological modeling of system functioning.


2018 ◽  
pp. 310-327
Author(s):  
Janis Osis ◽  
Erika Asnina

Experts' opinions exist that the way software is built is primitive. The role of modeling as a treatment for Software Engineering (SE) became more important after the appearance of Model-Driven Architecture (MDA). The main advantage of MDA is architectural separation of concerns that showed the necessity of modeling and opened the way for Software Development (SD) to become engineering. However, this principle does not demonstrate its whole potential power in practice, because of a lack of mathematical accuracy in the initial steps of SD. The question about the sufficiency of modeling in SD is still open. The authors believe that SD, in general, and modeling, in particular, based on mathematical formalism in all its stages together with the implemented principle of architectural separation of concerns can become an important part of SE in its real sense. They introduce such mathematical formalism by means of topological modeling of system functioning.


Author(s):  
Janis Osis ◽  
Erika Asnina

Experts' opinions exist that the way software is built is primitive. The role of modeling as a treatment for Software Engineering (SE) became more important after the appearance of Model-Driven Architecture (MDA). The main advantage of MDA is architectural separation of concerns that showed the necessity of modeling and opened the way for Software Development (SD) to become engineering. However, this principle does not demonstrate its whole potential power in practice, because of a lack of mathematical accuracy in the initial steps of SD. The question about the sufficiency of modeling in SD is still open. The authors believe that SD, in general, and modeling, in particular, based on mathematical formalism in all its stages together with the implemented principle of architectural separation of concerns can become an important part of SE in its real sense. They introduce such mathematical formalism by means of topological modeling of system functioning.


Author(s):  
Janis Osis ◽  
Erika Asnina

The authors share with some other experts the opinion that the way software is built is primitive. Therefore, this chapter discusses a role of modeling as a treatment for software engineering. The role of modeling became more important after appearance of principles proposed by Model Driven Architecture (MDA). The main advantage of MDA is architectural separation of concerns that showed necessity of modeling and opened the way to software development to become engineering. However, the weakness is that this principle does not demonstrate its whole potential power in practice, because of a lack of mathematical formalism (or accuracy) in the very initial steps of software development. Therefore, the question about the sufficiency of modeling in software development is still open. The authors believe that software development in general, and modeling in particular, based on mathematical formalism in all its stages together with the implemented principle of architectural separation of concerns can become Software Engineering in its real sense. The authors introduce such mathematical formalism by means of topological modeling of system functioning.


Author(s):  
Mirna Muñoz

Software has become the core of organizations in different domains because the capacity of their products, systems, and services have an increasing dependence on software. This fact highlights the research challenges to be covered by computer science, especially in the software engineering (SE) area. On the one way, SE is in charge of covering all the aspects related to the software development process from the early stages of software development until its maintenance and therefore is closely related to the software quality. On the other hand, SE is in charge of providing engineers able to provide technological-base solutions to solve industrial problems. This chapter provides a research work path focused on helping software development organizations to change to a continuous software improvement culture impacting both their software development process highlighting the human factor training needs. Results show that the implementation of best practices could be easily implemented if adequate support is provided.


Author(s):  
Daniel M. Brandon

Software engineering is vital for the proper planning of IT projects, although it is not a formal part of project management. The software engineering embedded in the acquired products will significantly affect long-term project success factors, even for IT projects that primarily involve software acquisition and integration instead of software development,. In this chapter I review software engineering and its relation to IT project management.


Author(s):  
Gordon Deline ◽  
Fuhua Lin ◽  
Dunwei Wen ◽  
Dragan Gaševic ◽  
Kinshuk N/A

This article presents a case study of ontology-driven development of intelligent educational systems. Following a review of literature related to ontology development, ontology-driven software development, and traditional software engineering, we developed an ontology-driven software development methodology appropriate for intelligent ontology-driven systems which have ontologies as key execution components, such as e-Advisor, and which is biased toward an integration of incremental and iterative ontology development and downstream Model Driven Architecture for development of software components.


2020 ◽  
Vol 17 (9) ◽  
pp. 4635-4642
Author(s):  
Mudita ◽  
Deepali Gupta

Software Engineering is the fundamental methodology used in the process of developing the software. Software Development Life Cycle (SDLC) is the backbone of software engineering. SDLC is emerging in several forms to support software development at different phases. SDLC plays as a role of guide for engineers that are involved from traditional desktop application development to much trending development. The new emerging technologies accelerate the process of software engineering, resulting in saving time and resources and enhance the quality of software systems. This paper focuses on technologies used to accelerate the process of software engineering in solving problems associated with its phases. The first section of this paper contains an introduction to Software Engineering (SE) and Artificial Intelligence (AI). The next section describes the aspects of emerging technologies in software engineering. After this, the role of AI in SE is discussed followed by a conclusion in the last section.


Sign in / Sign up

Export Citation Format

Share Document