scholarly journals Dezyne: Paving the Way to Practical Formal Software Engineering

2021 ◽  
Vol 338 ◽  
pp. 19-30
Author(s):  
Rutger van Beusekom ◽  
Bert de Jonge ◽  
Paul Hoogendijk ◽  
Jan Nieuwenhuizen
Keyword(s):  
Software Engineering ◽  
The Way

Read this and change the way you feel about software engineering

1996 ◽  
Vol 38 (2) ◽  
pp. 77-87 ◽  
Author(s):  
Janet Low ◽  
Jim Johnson ◽  
Pat Hall ◽  
Fiona Hovenden ◽  
Janet Rachel ◽  
...  
Keyword(s):  
Software Engineering ◽  
The Way

Is Modeling a Treatment for the Weakness of Software Engineering?

2017 ◽  
pp. 1977-1994
Author(s):  
Janis Osis ◽  
Erika Asnina
Keyword(s):  
Software Engineering ◽  
Software Development ◽  
Mathematical Formalism ◽  
Separation Of Concerns ◽  
Model Driven ◽  
Topological Modeling ◽  
System Functioning ◽  
Mathematical Accuracy ◽  
The Way

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.

Is Modeling a Treatment for the Weakness of Software Engineering?

2018 ◽  
pp. 310-327
Author(s):  
Janis Osis ◽  
Erika Asnina
Keyword(s):  
Software Engineering ◽  
Software Development ◽  
Mathematical Formalism ◽  
Separation Of Concerns ◽  
Model Driven ◽  
Topological Modeling ◽  
System Functioning ◽  
Mathematical Accuracy ◽  
The Way

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.

Positive and Negative Innovations in Software Engineering

2012 ◽  
pp. 252-263
Author(s):  
Capers Jones
Keyword(s):  
Software Engineering ◽  
Software Development ◽  
Productivity Costs ◽  
Software Applications ◽  
Project Outcomes ◽  
The World ◽  
Development Methods ◽  
Software Development Methods ◽  
The Way

The software engineering field has been a fountain of innovation. Ideas and inventions from the software domain have literally changed the world as we know it. For software development, we have a few proven innovations. The way software is built remains surprisingly primitive. Even in 2008 major software applications are cancelled, overrun their budgets and schedules, and often have hazardously bad quality levels when released. There have been many attempts to improve software development, but progress has resembled a drunkard’s walk. Some attempts have been beneficial, but others have been either ineffective or harmful. This article puts forth the hypothesis that the main reason for the shortage of positive innovation in software development methods is due to a lack of understanding of the underlying problems of the software development domain. A corollary hypothesis is that lack of understanding of the problems is due to inadequate measurement of quality, productivity, costs, and the factors that affect project outcomes.

Teaching Agile Software Development Quality Assurance

2009 ◽  
pp. 2700-2713
Author(s):  
Orit Hazzan ◽  
Yael Dubinsky
Keyword(s):  
Quality Assurance ◽  
Software Engineering ◽  
Software Development ◽  
Software Quality ◽  
Agile Software Development ◽  
Specific Teaching ◽  
Quality Issues ◽  
Agile Software ◽  
Software Development Environments ◽  
The Way

This chapter presents a teaching framework for agile quality—that is, the way quality issues are perceived in agile software development environments. The teaching framework consists of nine principles, the actual implementation of which is varied and should be adjusted for different specific teaching environments. This chapter outlines the principles and addresses their contribution to learners’ understanding of agile quality. In addition, we highlight some of the differences between agile software development and plan-driven software development in general, and with respect to software quality in particular. This chapter provides a framework to be used by software engineering instructors who wish to base students learning on students’ experiences of the different aspects involved in software development environments.

Μίνθα

2014 ◽  
pp. 1119-1141
Author(s):  
Jörn Guy Süß ◽  
Neil Robinson ◽  
David Carrington ◽  
Paul Strooper
Keyword(s):  
Software Engineering ◽  
Software Development ◽  
Object Oriented ◽  
Safety Critical ◽  
Development Framework ◽  
Code Generators ◽  
Application Logic ◽  
The Cost ◽  
Framework Development ◽  
The Way

Implementation of railway controller application logic is a highly safety-critical and time-consuming task carried out individually for each client and station by specialised signalling engineers, with corresponding high costs. Μίνθα is a software development framework designed to create code generators for application logic for the client railway companies of Ansaldo STS that use the Microlok II controller to lower the cost and increase repeatability. This chapter describes the evolution of Μίνθα from prototype to framework, and introduces the software engineering approaches of object-oriented meta-modelling and framework development along the way. It also presents known limitations and further application areas of the framework.

Software Engineering in Australasia

2021 ◽  
Vol 46 (2) ◽  
pp. 16-17
Author(s):  
Sherlock A. Licorish ◽  
Christoph Treude ◽  
John Grundy ◽  
Kelly Blincoe ◽  
Stephen MacDonell ◽  
...  
Keyword(s):  
New Zealand ◽  
Software Engineering ◽  
Software Development ◽  
Current Position ◽  
Engineering Community ◽  
Development Methods ◽  
Software Development Methods ◽  
The Way

Six months ago an important call was made for researchers globally to provide insights into the way Software Engineering is done in their region. Heeding this call, we hereby outline the position Software Engineering in Australasia (New Zealand and Australia). This article first considers the software development methods, practices and tools that are popular in the Australasian software engineering community. We then briefly review the particular strengths of software engineering researchers in Australasia. Finally, we make an open call for collaborators by reflecting on our current position and identifying future opportunities.

Sign in / Sign up

Export Citation Format

Share Document