Towards a Philosophy of Software Development: 40 Years after the Birth of Software Engineering

Northover, Mandy; Kourie, Derrick G.; Boake, Andrew; Grüner, Stefan; Northover, Alan

doi:10.1007/s10838-008-9068-7

Cited by 13 publications

(7 citation statements)

References 32 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…It is indeed the responsibility of the IT management in a company to fully appreciate that software testing is de-facto the most scientific of all software engineering activities, whereas other software engineering activities still resemble much of an 'art' or 'craft' [35]. However, the 'power of science' cannot be unleashed if IT managers are not aware of it.…”

Section: Test Repeatability and Environmentsmentioning

confidence: 99%

Software Testing in Small IT Companies: A (not only) South African Problem

Grüner¹,

Zÿl²

2011

SACJ

Self Cite

View full text Add to dashboard Cite

Small software companies make for the majority of software companies around the world, but their software development processes are often not as clearly defined and structured as in their larger counterparts. Especially the test process is often the most neglected part of the software process. This contribution analyses the software testing process in a small South African IT company, here called X, to determine the problems that currently cause it to deliver software fraught with too many defects. The findings of a survey conducted with all software developers in company X are discussed, and several typical problems are identified. We also discuss two prevalent test process improvement models that can be used to reason about the possibilities of process improvement. Solutions to those (or similar) problems often already exist, but a major part of the problem addressed in this contribution is the unawareness, or unfamiliarity, of many small industrial software developers and IT managers as far as the scientific literature on software science and engineering, and especially in our case: software testing, is concerned.

show abstract

Section: Test Repeatability and Environmentsmentioning

confidence: 99%

Software Testing in Small IT Companies: A (not only) South African Problem

Grüner¹,

Zÿl²

2011

SACJ

Self Cite

View full text Add to dashboard Cite

show abstract

“…The philosophy behind this pattern is analogous to the philosophy behind SDLC incremental model (Larman and Basil, 2003;Olsen, 2006;Northover et al, 2008;Lindblom, 1959). The roots of incrementalism, in turn, are in the epistemology of pragmatism (Halton, 2004).…”

Section: Incremental Collaboration Patternmentioning

confidence: 95%

Advanced Planning and Scheduling Systems: Modeling and Implementation Challenges

Lupeikienė¹,

Dzemyda²,

Kiss³

et al. 2014

Informatica

View full text Add to dashboard Cite

The paper summarizes the results of research on the modeling and implementation of advanced planning and scheduling (APS) systems done in recent twenty years. It discusses the concept of APS system-how it is thought of today-and highlights the modeling and implementation challenges with which the developers of such systems should cope. Some from these challenges were identified as a result of the study of scientific literature, others-through an in-depth analysis of the experience gained during the development of real-world APS system-a Production Efficiency Navigator (PEN system). The paper contributes to APS systems theory by proposing the concept of an ensemble of collaborating algorithms.

show abstract

“…Northover et al [11], reinforced by de Vasconcelos [17], state that the challenge of building software is to be able to accommodate upon design the changes coming from the most varied sources of pressure-whether they are technological, economic, social, or even ideological-at whatever moments they arise. However, even if we recognize this pressure for modifying the definition of things-names and meanings-in a business domain, we still need to capture these things, requiring some level of stability of their names and meanings in order to properly compute them, as pointed out by Rayside and Campbell [19].…”

Section: Metadata Interpretation Driven Developmentmentioning

confidence: 99%

“…Despite the investment for development of above paradigms, their success when used together or separately has been up to now relatively limited [11]. In this regard, Jalender et al [12] claim that componentization is the principle that synthesizes a desperate need of the software industry and, because of that, it will be fulfilled.…”

Section: Introductionmentioning

confidence: 99%

Metadata Interpretation Driven Development

da Costa,

Petta,

Xavier-de-Souza

2021

Preprint

View full text Add to dashboard Cite

Context: Despite decades of engineering and scientific research efforts, separation of concerns in software development remains not fully achieved. The ultimate goal is to truly allow code reuse without large maintenance and evolution costs. The challenge has been to avoid the crosscutting of concerns phenomenon, which has no apparent complete solution. Objective: In this paper, we show that business-domain code inscriptions play an even larger role in this challenge than the crosscutting of concerns. We then introduce a new methodology, called Metadata Interpretation Driven Development (MIDD) that suggests a possible path to realize separation of concerns by removing functional software concerns from the coding phase. Method: We propose a change in the perspective for building software, from being based on object representation at the coding level to being based on object interpretation, whose definitions are put into layers of representation other than coding. The metadata of the domain data is not implemented at the level of the code. Instead, they are interpreted at run time. Results: As an important consequence, such constructs can be applied across functional requirements, across business domains, with no concerns regarding the need to rewrite or refactor code. We show how this can increase the (re)use of the constructs. Furthermore, the execution of a single interpreter, due to its semantic disconnection from the domain, suggests that it can simultaneously serve different business domains. Conclusions: Although high-reuse software construction is considered a relatively mature field, changes in the software services scenario demand relevant solutions. The emergence of new software architectures, such as serverless computing, reinforces the need to rethink software construction. This approach is presented as a response to this need.

show abstract

Towards a Philosophy of Software Development: 40 Years after the Birth of Software Engineering

Cited by 13 publications

References 32 publications

Software Testing in Small IT Companies: A (not only) South African Problem

Software Testing in Small IT Companies: A (not only) South African Problem

Advanced Planning and Scheduling Systems: Modeling and Implementation Challenges

Metadata Interpretation Driven Development

Contact Info

Product

Resources

About