Welcome to the InfoSci Platform
Reference Hub3
Is Modeling a Treatment for the Weakness of Software Engineering?

Is Modeling a Treatment for the Weakness of Software Engineering?

Janis Osis, Erika Asnina
Copyright: © 2011 |Pages: 14
ISBN13: 9781616928742|ISBN10: 1616928743|EISBN13: 9781616928766
DOI: 10.4018/978-1-61692-874-2.ch001
Cite Chapter Cite Chapter

MLA

Osis, Janis, and Erika Asnina. "Is Modeling a Treatment for the Weakness of Software Engineering?." Model-Driven Domain Analysis and Software Development: Architectures and Functions, edited by Janis Osis and Erika Asnina, IGI Global, 2011, pp. 1-14. https://doi.org/10.4018/978-1-61692-874-2.ch001

APA

Osis, J. & Asnina, E. (2011). Is Modeling a Treatment for the Weakness of Software Engineering?. In J. Osis & E. Asnina (Eds.), Model-Driven Domain Analysis and Software Development: Architectures and Functions (pp. 1-14). IGI Global. https://doi.org/10.4018/978-1-61692-874-2.ch001

Chicago

Osis, Janis, and Erika Asnina. "Is Modeling a Treatment for the Weakness of Software Engineering?." In Model-Driven Domain Analysis and Software Development: Architectures and Functions, edited by Janis Osis and Erika Asnina, 1-14. Hershey, PA: IGI Global, 2011. https://doi.org/10.4018/978-1-61692-874-2.ch001

Export Reference

Mendeley
Favorite

Abstract

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.

Request Access

You do not own this content. Please login to recommend this title to your institution's librarian or purchase it from the IGI Global bookstore.