Technical Software Development Process in the XML Domain

  • Authors:

  • Liming Zhu;Tu Tak Tran;Mark Staples;Ross Jeffery

  • Affiliations:

  • NICTA, Eveleigh, Australia and School of Computer Science and Engineering, University of New South Wales, Australia;NICTA, Eveleigh, Australia and School of Computer Science and Engineering, University of New South Wales, Australia;NICTA, Eveleigh, Australia and School of Computer Science and Engineering, University of New South Wales, Australia;NICTA, Eveleigh, Australia and School of Computer Science and Engineering, University of New South Wales, Australia

  • Venue:
  • ICSP '09 Proceedings of the International Conference on Software Process: Trustworthy Software Development Processes
  • Year:
  • 2009

Quantified Score

Hi-index 0.00

Visualization

Abstract

Background: A Technical Development Process (TDP) is a development process for a particular technology, such as XML, service orientation, object orientation or a programming language. Unlike software development life-cycle processes, TDPs provide concrete and detailed guidance to software engineers working in a particular technology domain. TDPs are currently not well understood in terms of description, modelling and interactions with life-cycle processes. Aim: In this paper, we investigate what are TDPs in the XML domain and how can TDPs be modelled using existing development process modelling notations and tools. Method: We extracted XML specific TDPs from literatures, interviews and internal documentation within software development organizations and conducted systematic verifications and validations. Results: We identify different types of TDPs in the XML domain and propose mechanisms to model TDPs using Software Process Engineering Meta-models (SPEM) in the Eclipse Modelling Framework (EPF). Conclusion: The results demonstrate the feasibility of explicitly identifying and modelling of TDPs in the context of software process modelling and how they are used in software development. The results help further bridge the gap between macro-processes (life-cycle and management-centred processes) and micro-processes (e.g. developer-centred TDPs).