Internet-speed development: Difference between revisions

Revision as of 15:42, 5 December 2013

Revision as of 22:10, 20 April 2014

Line 22:

The last concept discussed in this entry of internet-speed development is the concept of parallel development. This concept basically means that all the software development is done in parallel as often as possible. This will allow very quick development and it allows the smaller teams to focus on their own feature as much as possible which has a good result on quality. To ensure that the smaller teams do work together to create the final system it is however needed to synchronize their development frequently. This can be done using [[daily build]]s which means that all the developers check their code in at the end of the day after which a build is created which can then be evaluated and tested to monitor progress. After a feature is completed in the build in needs to be tested and refined which is sometimes called the synch-and-stabilize process. The developed features are synchronized with the build and tested. After these tests any bugs will be corrected and the feature can be refined to work better (which is the stabilization part).

Internet-speed development is based on the agile principles and as such it has a lot of similarities with [[Extreme Programming]], [[RUPRational Unified Process]], [[DSDM]] and [[Feature Driven Development]]. Internet-speed development is different however from these methods as it also incorporates a more extensive risk-management planning and has quality as a very important objective of a project.<ref>As shown in the paper of Zuser, Heil and Grechening.</ref> The development phase of Internet-speed development also shows some similarities with the [[open-source software]] development model because many different developers around the globe can be part of the development process because of communication through the Internet and the use of repositories for storing the code and documentation.

==The phases of Internet-Speed Development ==