Core Point Evolution: A Waterwave Model of Software Development Process

Software development methodology is a proposition that is used to structure, plan, and control the process of developing a system. However, traditional methods, such as waterfall-like model, component-based programming, software architecture method and agile method, have encountered more fundamental difficulties in processing complex system development. To address this challenge, we have witnessed that the thought of waterwave model origins from the evolution of water wave when a stone is threw into the water. In this paper, we have proposed a waterwave model of software development process with loosely-coupled correlated core point evolution. The development of a complex system is translated into the evolution of core points. With the persistent evolution thought of waterwave, the development process has strong expansibility and flexible reusability.

[1]  Mei Hong,et al.  Progress of Research on Software Architecture , 2006 .

[2]  Kun Ma,et al.  A Template-based Model Transformation Approach for Deriving Multi-Tenant SaaS Applications , 2012 .

[3]  Orit Hazzan,et al.  Introduction to Agile Software Development , 2008 .

[4]  Zhoujun Li,et al.  A New Component-Oriented Programming Language with the First-Class Connector , 2006, JMLC.

[5]  Bernhard Rumpe,et al.  Limitations of Agile Software Processes , 2014, ArXiv.

[6]  Gustav Pomberger,et al.  Prototyping-Oriented Software Development - Concepts and Tools , 1991, Struct. Program..

[7]  Mary Shaw,et al.  Continuing Prospects for an Engineering Discipline of Software , 2009, IEEE Software.

[8]  Barry W. Boehm,et al.  A spiral model of software development and enhancement , 1986, Computer.

[9]  Bo Yang,et al.  A Relational Approach to Model Transformation with QVT Relations Supporting Model Synchronization , 2011, J. Univers. Comput. Sci..

[10]  David Garlan,et al.  A formal basis for architectural connection , 1997, TSEM.

[11]  W. W. Royce,et al.  Managing the development of large software systems , 1970 .

[12]  Douglas C. Schmidt,et al.  Ultra-Large-Scale Systems: The Software Challenge of the Future , 2006 .

[13]  Tao Xie,et al.  Internetware: A Software Paradigm for Internet Computing , 2012, Computer.

[14]  Steven D. Tripp,et al.  Rapid prototyping: An alternative instructional design strategy , 1990 .

[15]  Tudor Dumitras,et al.  MEAD: support for Real‐Time Fault‐Tolerant CORBA , 2005, Concurr. Pract. Exp..

[16]  Kung-Kiu Lau,et al.  Exogenous connectors for software components , 2005, CBSE'05.

[17]  Farhad Arbab,et al.  Abstract Behavior Types: a foundation model for components and their composition , 2002, Sci. Comput. Program..

[18]  Alfonso Fuggetta,et al.  Software process: a roadmap , 2000, ICSE '00.

[19]  Jan Bosch,et al.  Software Architecture: The Next Step , 2004, EWSA.

[20]  James E. Tomayko,et al.  Integrating the Architecture Tradeoff Analysis Method (ATAM) with the Cost Benefit Analysis Method (CBAM) , 2003 .

[21]  Robert C. Martin.  Agile Software Development, Principles, Patterns, and Practices , 2002 .

[22]  Ivica Crnkovic,et al.  Component-based development process and component lifecycle , 2005, 27th International Conference on Information Technology Interfaces, 2005..

[23]  Khashayar Niki Maleki,et al.  A brief survey of software architecture concepts and service oriented architecture , 2009, 2009 2nd IEEE International Conference on Computer Science and Information Technology.