An Investigation of Software Development Process Terminology

@inproceedings{Clarke2016AnIO,
  title={An Investigation of Software Development Process Terminology},
  author={Paul M. Clarke and Antoni Llu{\'i}s Mesquida and Damjan Ekert and Joseph J. Ekstrom and Tatjana Gornostaja and Milo{\vs} Jovanovi{\'c} and J{\o}rn Johansen and Ant{\`o}nia Mas Picahaco and Richard Messnarz and Blanca N{\'a}jera Villar and A. O'Connor and Rory V. O'Connor and Michael Reiner and Gabriele Sauberer and Klaus-Dirk Schmitz and Murat Yilmaz},
  booktitle={SPICE},
  year={2016}
}
The practice of software development has evolved considerably in recent decades, with new programming technologies, the affordability of hardware, pervasive internet access and mobile computing all contributing to the emergence of new software development processes. The newer process initiatives, which include those which are sometimes referred to as agile or lean methods, have brought with them new terms, which sometimes reflect the introduction of novel concepts. Other times, new terms… 
Continuous software engineering—A microservices architecture perspective
TLDR
An emerging approach to software development, continuous software engineering (CSE), wherein software of operational quality may be delivered on a very frequent basis, up to many times in a given day, is discussed.
Software Development Context: Critiquing Often Used Terms
TLDR
The findings from the explorations of context are overviewed and the inadmissible terms are presented and the cataloguing of these terms will benefit researchers by supporting discussion and thus a deeper understanding of context for situated software practices.
Evolving a Model for Software Process Context: An Exploratory Study
TLDR
An exploratory stage of evolving a model for context for situated software practices, which has exposed a lack of clarity in the meanings of terms reported in the literature.
Refactoring Software Development Process Terminology Through the Use of Ontology
TLDR
The development of such an ontology would in effect represent a systematic refactoring of the terminology and concepts produced over four decades of software process innovation.
Assessing Application Lifecycle Management (ALM) Potentials from an Industrial Perspective
TLDR
The results indicate that participatory action research is a robust approach to investigate complex software engineering issues and provides guidance for practitioners in tailoring ALM practices from the idea phase through the selection of the underlying toolset.
Exploring Software Process Variation Arising from Differences in Situational Context
TLDR
The role of situational context in deciding upon the software development process is discussed through the analysis of two case studies, finding that both companies have enjoyed sustained business growth and are quite distinct in their processes, this distinction being driven by their different situational contexts.
An ISO/IEC 12207 perspective on software development process adaptation
TLDR
The general findings of this latest case study are consistent with their previous related work, supporting the case that a software development process is dependent on the organizational context, perhaps in a highly complex manner.
In search of the origins and enduring impact of Agile software development
TLDR
It is found that the contemporary use of tooling to automate processes may not be wholly congruent with the manifesto and that many organisations may still rely on business contracts despite calls in the manifesto for greater levels of informal customer collaboration.
Reflections on the Need for Disambiguation of Terminology for Software Process Improvement
TLDR
A bottom-up pragmatic approach for using ontologies and for integrating research and practice is proposed and a framework based on SPI Manifesto values and principles for the disambiguation of terms for continuous process improvement is proposed.
Do We Speak the Same Language? Terminology Strategies for (Software) Engineering Environments Based on the Elcat Model - Innovative Terminology e-Learning for the Automotive Industry
TLDR
The strategy presented in this paper follows the elcat model, an innovative e-learning initiative that focusses on content development of terminology management modules for the automotive industries.
...
...

References

SHOWING 1-10 OF 32 REFERENCES
A Systematic Approach to the Comparison of Roles in the Software Development Processes
TLDR
A systematic comparison of software development models, covering traditional approaches through to agile techniques, finds that based on project specific needs, the roles used in industry vary significantly from the roles defined in literature.
Agile Software Development with SCRUM
TLDR
This book describes building systems using the deceptively simple process, Scrum, a new approach to systems development projects that cuts through the ocmplexity and ambiguity of complex, emergent requiremetns and unstable technology to iteratively and quickly produce quality software.
Exploring the Relationship between Software Process Adaptive Capability and Organisational Performance
TLDR
An exploratory study to concurrently examine software process adaptive capability and organisational performance in 15 software development organisations finds that companies with greater software process Adaptive capability are shown to also experience greater business success.
Adaptive Software Development: A Collaborative Approach to Managing Complex Systems
TLDR
Adaptive Software Development offers a practical, realistic approach to managing high-speed, high-change software development projects and shows readers how to increase collaboration and adapt to uncertainty.
SCRUM Development Process
TLDR
SCRUM is an enhancement of the commonly used iterative/incremental object-oriented development cycle that defines the systems development process as a loose set of activities that combines known, workable tools and techniques with the best that a development team can devise to build systems.
A spiral model of software development and enhancement
TLDR
An outline is given of the process steps involved in the spiral model, an evolving risk-driven approach that provides a framework for guiding the software process and its application to a software project is shown.
A Practical Guide to Feature-Driven Development
From the Publisher: Feature-Driven Development (FDD), created by Peter Coad (Chief Architect), Jeff De Luca (Project Manager), and Stephen Palmer (Development Manager), combines the key advantages
Investigating software process in practice: A grounded theory perspective
An empirical examination of the extent of software process improvement in software SMEs
TLDR
It is found that SMEs initiate a considerable amount of SPI, albeit in varying quantities in different organisations, and the significant majority of SPI in software SMEs is minor or moderate in nature, sometimes leveraging the human capital via improvements in tacit knowledge.
...
...