PIP: Progressive Implementation Pattern
Srgio Soares, Paulo Henrique Monteiro Borba · 2002
ys in project schedule. . Simplify tests by testing each aspect (persistence, distribution, and concurrency control) separately. This separation allows testing the functional version of the system without the impact of database, network, or concurrent environments errors. In fact, each nonfunctional requirement will also be gradually implemented and tested, which avoids that errors of one aspect a#ects tests of another. # Supported by CAPES. Also a#liated to Catholic University of Pernambuco. Email: [email protected] + Partially supported by CNPq, grant 521994/96--9. Partially supported by Qualiti Software Processes (www.qualiti.com.br). Email: [email protected] 1 . Data storage transparency. This is crucial to initially provide a non-persistent version of the system in order to validate functional requirements without implementing persistence. After that, the system evolves to a persistent version. . Independence of communication API and middleware. Similar to the persistence