Is Modeling a Treatment for the Weakness of Software Engineering?

View Sample PDF

Author(s): Janis Osis (Riga Technical University, Latvia)and Erika Asnina (Riga Technical University, Latvia)
Copyright: 2015
Pages: 17
Source title: Handbook of Research on Innovations in Systems and Software Engineering
Source Author(s)/Editor(s): Vicente García Díaz (University of Oviedo, Spain), Juan Manuel Cueva Lovelle (University of Oviedo, Spain)and B. Cristina Pelayo García-Bustelo (University of Oviedo, Spain)
DOI: 10.4018/978-1-4666-6359-6.ch017

Keywords: Computer Science & IT / Information Science Reference / Systems & Software Design / Systems and Software Engineering

Purchase

View Is Modeling a Treatment for the Weakness of Software Engineering? on the publisher's website for pricing and purchasing information.

Abstract

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.

The IRMA Community

Research IRM

Is Modeling a Treatment for the Weakness of Software Engineering?

Purchase

Abstract

Related Content

IRMA Sponsors