The way of designing a simulation software in order to evaluate the economic performance in software development

2017 ◽  
Author(s):  
David Kuhlen ◽  
Andreas Speck
Keyword(s):  
Software Development ◽  
Economic Performance ◽  
Simulation Software ◽  
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.

COGITO: A METHODOLOGY AND SYSTEM FOR FORMAL SOFTWARE DEVELOPMENT

1995 ◽  
Vol 05 (04) ◽  
pp. 599-617 ◽  
Author(s):  
A. BLOESCH ◽  
E. KAZMIERCZAK ◽  
P. KEARNEY ◽  
OWEN TRAYNOR
Keyword(s):  
Software Development ◽  
Support System ◽  
Development Process ◽  
Integrated Methodology ◽  
Formal Development ◽  
Phases Of Development ◽  
The Way

Cogito 1 is the first iteration of a Z-based integrated methodology and support system for formal software development. This paper gives an overview of the Cogito methodology and associated tools. Particular emphasis is placed on the way in which Cogito integrates the various phases of the formal development process and provides comprehensive tools support for all phases of development addressed by the methodology.

Chaste: using agile programming techniques to develop computational biology software

2008 ◽  
Vol 366 (1878) ◽  
pp. 3111-3136 ◽  
Author(s):  
Joe Pitt-Francis ◽  
Miguel O Bernabeu ◽  
Jonathan Cooper ◽  
Alan Garny ◽  
Lee Momtahan ◽  
...  
Keyword(s):  
Computational Biology ◽  
Software Development ◽  
Numerical Algorithms ◽  
Simulation Software ◽  
Advantages And Disadvantages ◽  
Excellent Starting Point ◽  
Starting Point ◽  
Cardiac Modelling ◽  
Agile Programming ◽  
Development Methods

Cardiac modelling is the area of physiome modelling where the available simulation software is perhaps most mature, and it therefore provides an excellent starting point for considering the software requirements for the wider physiome community. In this paper, we will begin by introducing some of the most advanced existing software packages for simulating cardiac electrical activity. We consider the software development methods used in producing codes of this type, and discuss their use of numerical algorithms, relative computational efficiency, usability, robustness and extensibility. We then go on to describe a class of software development methodologies known as test-driven agile methods and argue that such methods are more suitable for scientific software development than the traditional academic approaches. A case study is a project of our own, Cancer, Heart and Soft Tissue Environment, which is a library of computational biology software that began as an experiment in the use of agile programming methods. We present our experiences with a review of our progress thus far, focusing on the advantages and disadvantages of this new approach compared with the development methods used in some existing packages. We conclude by considering whether the likely wider needs of the cardiac modelling community are currently being met and suggest that, in order to respond effectively to changing requirements, it is essential that these codes should be more malleable. Such codes will allow for reliable extensions to include both detailed mathematical models—of the heart and other organs—and more efficient numerical techniques that are currently being developed by many research groups worldwide.

scholarly journals Self - Organizing Teams in Software Development – Myth or Reality

TEM Journal ◽  
2021 ◽  
pp. 1565-1571
Author(s):  
Tarik Zaimovic ◽  
Muharem Kozic ◽  
Amina Efendić ◽  
Amel Džanić
Keyword(s):  
Software Development ◽  
Bosnia And Herzegovina ◽  
Team Performance ◽  
Central Element ◽  
Business Environment ◽  
Team Cohesion ◽  
Individual Member ◽  
Mutual Support ◽  
Effectiveness And Efficiency ◽  
The Way

In an agile business environment, teamwork quality is underlining key element of successful projects and overall team performance. In the Scrum framework, self-managing team is a central element of success. Self-managing teams introduced a new concept of teams and emphasized the importance of individual member effort and the way it affects team performance. The focus of this paper is on teamwork quality in self-managing teams and the way it affects the overall team performance. Teamwork quality is defined by six subconstructs: communication, coordination, balance of member contributions, mutual support, effort, and cohesion, while team performance is defined with effectiveness and efficiency. A survey of 260 respondents from the IT sector in Bosnia and Herzegovina was conducted and in both tested models, our results have confirmed that the highest effect on team effectiveness comes from mutual support, with slightly different – but still significant, impact of team cohesion and effort.

Sign in / Sign up

Export Citation Format

Share Document