Agile software development

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

doi:10.1145/1292491.1292504

Cited by 8 publications

(3 citation statements)

References 4 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…There are studies about the applicability of agile development to other standards. Theunissen, Kourie, & Watson (2003) have investigated adaptability of agile methodologies to software development standards laid down by ISO, concentrating on the ISO 12207:1995 standard on software life-cycle processes. Stålhane & Hanssen (2008) have discussed the applicability of agile methods to ISO 9001 standard on certification of quality systems.…”

Section: Related Workmentioning

confidence: 99%

Agile Embedded System Development versus European Space Standards

Rantala

Könnölä

Suomi

et al. 2017

International Journal of Information Systems and Social Change

View full text Add to dashboard Cite

Agile development methods are widely utilized in software development. There is a growing interest and effort to introduce them to other areas of technology, such as development of space systems. Space systems are typically safety- and mission-critical and therefore their development is strongly regulated and standardized. European Cooperation for Space Standardization (ECSS) has created a collection of standards which are extensively followed mainly in European space projects. In this paper, a review and discussion are presented to find out the conflicts between the agile development and the ECSS standards. The presented analysis and discussion show that the ECSS standards do not fully prevent the utilization of agile methods. However, there are aspects to be taken into account in the development methods, contracts and tailoring of standards.

show abstract

Section: Related Workmentioning

confidence: 99%

Agile Embedded System Development versus European Space Standards

Rantala

Könnölä

Suomi

et al. 2017

International Journal of Information Systems and Social Change

View full text Add to dashboard Cite

show abstract

“…4, 5, and 6 we offer our own philosophical thoughts about SE, whereby we emphasise the issue of change and use the philosophers Kuhn and Popper as our initial (though not necessarily final) landmarks for orientation in this difficult intellectual landscape. Those sections are based on two of our computer science symposium papers (Northover et al 2006(Northover et al , 2007 which were well received in the related communities. In Sect.…”

Section: Structure Of This Essaymentioning

confidence: 99%

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

et al. 2008

Self Cite

View full text Add to dashboard Cite

Over the past four decades, software engineering has emerged as a discipline in its own right, though it has roots both in computer science and in classical engineering. Its philosophical foundations and premises are not yet well understood. In recent times, members of the software engineering community have started to search for such foundations. In particular, the philosophies of Kuhn and Popper have been used by philosophically-minded software engineers in search of a deeper understanding of their discipline. It seems, however, that professional philosophers of science are not yet aware of this new discourse within the field of software engineering. Therefore, this article aims to reflect critically upon recent software engineers' attempts towards a philosophy of software engineering and to introduce our own philosophical thoughts in this context. Finally, we invite the professional philosophers of science to participate in this interesting new discourse.

show abstract

“…Incremental development processes (Gilb 1988;Brooks 1995), such as spiral development (Boehm 1988) and iterative enhancement (Basili and Turner 1975) have been proposed to improve productivity. More recently, incremental development has been adopted by modern development methods such as agile and extreme programming (Beck 2000;Copeland 2002;Theunissen, Kourie, and Bruce 2003). In these methods, the release of functionality (or stories, as these releases are sometimes referred to) is influenced by the client's preferences.…”

Section: Literature Reviewmentioning

confidence: 99%

Value‐Driven Creation of Functionality in Software Projects: Optimal Sequencing and Reuse

Liu

Dawande

Mookerjee

2007

Production and Operations Management

View full text Add to dashboard Cite

We study the problem of optimally sequencing the creation of elements in a software project to optimize a time‐weighted value objective. As elements are created, certain parts of the system (referred to as “groups”) become functional and provide value, even though the entire system has not been completed. The main tradeoff in the sequencing problem arises from elements that belong to multiple groups. On the one hand, creating groups with common elements early in the project reduces the effort required to build later functionality that uses these elements. On the other hand, the early creation of such groups can delay the release of some critical functionality. We formulate the element sequencing problem and propose a heuristic to solve it. This heuristic is compared against a lower bound developed for the problem. Next, we study a more general version of the element sequencing problem in which an element requires some effort to be made reusable. When a reusable element is used in another group, some more effort is needed to specialize the element to work as desired in that group. We study reuse decisions under a weighted completion time objective (i.e., the sum of the completion time of each group weighted by its value is minimized), and show how these decisions differ from those under a traditional makespan objective (i.e., only the final completion time of the project is minimized). A variety of analytical and numerical results are presented. The model is also implemented on data obtained from a real software project. A key finding of this work is that the optimal effort on reuse is never increased (typically lowered) when a weighted completion time objective is used. This finding has implications for managing reuse in projects in which user value influences the order in which functionality is created.

show abstract

Agile software development

Cited by 8 publications

References 4 publications

Agile Embedded System Development versus European Space Standards

Agile Embedded System Development versus European Space Standards

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

Value‐Driven Creation of Functionality in Software Projects: Optimal Sequencing and Reuse

Contact Info

Product

Resources

About