Modelling collaborative product development using axiomatic design principles: application to software industry

Abstract

Even though collaborative product development (CPD) is considered as a strategic business plan to maintain competitive advantage, the literature lacks a systematic and detailed model of CPD from a strategic point of view. This article aims to develop a CPD model based on an axiomatic design technique by offering a system perspective in the context of software development (SD). Software industry is characterised by a dynamic and innovative nature and it gives a suitable application area in order to detail the proposed model in industry. Three main dimensions of CPD derived from the literature are defined in strategic level: partnership process, collaboration process and PD/SD. These three dimensions are detailed into hierarchy through business feedback and by experts from software industry. The model is evaluated and verified through two interviews. A case study is then conducted to observe the performance of the model. The conceptual model offers a guideline for CPD practitioners to increase effectiveness in collaborative efforts in the development process. The proposed model incorporates the main success factors of CPD in general, collaborative SD in specific, and it can be used as a performance evaluator in collaborative projects.

Using extended Axiomatic Design theory to reduce complexities in Global Software Development projects

“…Arsenyan and Bü yü kö zkan [2] presented an AD-based collaboration model in the context of the software industry. They proposed a model structure for collaborative software development, as well as strategies and methodologies that influence the successful execution of collaborative efforts in software development.…”

The effect of knowledge-based information technology tools on the new product development processes in software companies

“…The development of software is comprised of several related stages of analysis, system requirements, designing, programming, testing, maintenance and optimisation (Aramand, 2008). Arsenyan and Buyukozkan (2014) define SD as a combined process of research, development, modification, re-use, reengineering, maintenance and similar activities that result in software products. There are four successive steps in SD process, which includes necessity and requirement phase, designing phase, programming phase and testing phase.…”

An Axiom Based Metamodel for Software Process Formalisation: An Ontology Approach

“…In this regard, their accuracy doesn't need to be proven [37] and can be used as a basis for argument or inference. Axioms have been used widely in providing foundations for theoretical works [38,39] in SE. In here, we use these axioms to provide a theoretical foundation for the essential metamodel concepts for process formalisation.…”