Concurrent Subsystem-Component Development Model (CSCDM) for Developing Adaptive E-Commerce Systems

  • Liangtie Dai
  • Wanwu Guo
Part of the Lecture Notes in Computer Science book series (LNCS, volume 4707)


The waterfall and incremental models are widely used for guiding E-commerce system development. In some cases where clients demand a quick solution to maximise their business benefit, these models are not fully fit in directing such projects. This is because the client’s prioritisation of system requirements is determined by immediate business benefit whereas the developer’s is based on the long-term system usability and reliability. The concurrent subsystem-component development model (CSCDM) proposed in this paper is an alternative approach for guiding system development, especially for client-driven business systems. Its waterfall-based framework is easy to follow and understand by the developers. Its component-based stream only iterates over the Implementation, Testing, and Deployment stages. Since the design for the overall system and prototypes is done at the same stage, all the prototypes can be fully or partly absorbed into the corresponding system groups, and/or modified to fit into the system design. The local iterations realise the business needs separately using prototyping without interference with the progression of the overall system development, which ensures the quick deployment of a prototype. The case of WCE Pizza online system proves that CSCDM is an effective approach to guide the development of client-driven E-commerce systems.


Electronic commerce Waterfall model Incremental model Prototyping Concurrent subsystem-component development model (CSCDM) 


Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.


  1. 1.
    Goldman, J.E., Rawles, P.T., Mariga, J.R.: Client/server information systems: a business-oriented approach. Wiley, Chichester (1999)Google Scholar
  2. 2.
    Ince, D.: Developing distributed and E-commerce applications. Addison-Wesley, Reading (2004)Google Scholar
  3. 3.
    Tanenbaum, A., van Steen, M.: Distributed systems: principles and paradigms. Prentice Hall, Englewood Cliffs (2002)Google Scholar
  4. 4.
    Coulouris, G., Dollimore, J., Kindberg, T.: Distributed systems: concepts and design. Addison-Wesley, Reading (2001)Google Scholar
  5. 5.
    Sommerville, I.: Software engineering. Addison-Wesley, Reading (2001)Google Scholar
  6. 6.
    Futrell, R.T., Shafer, D.F., Shafer, L.I.: Quality software project management. Prentice Hall, Englewood Cliffs (2002)Google Scholar
  7. 7.
    McManus, J., Wood-Harper, T.: Information systems project management. Prentice Hall, Englewood Cliffs (2003)Google Scholar
  8. 8.
    Royce, W.W.: Managing the development of large software systems. In: IEEE Proceedings WESCON, pp. 1–9 (1970)Google Scholar
  9. 9.
    Parnas, D.: Designing software for ease of extension and contraction. IEEE Transactions on Software Engineering, 128–138 (1979)Google Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 2007

Authors and Affiliations

  • Liangtie Dai
    • 1
  • Wanwu Guo
    • 2
  1. 1.Institute of Human Resources Management, Jinan University, Guangzhou, Guangdong ProvinceChina
  2. 2.School of Computer and Information Science, Edith Cowan University, 2 Bradford Street, Mount Lawley, Western Australia 6050Australia

Personalised recommendations