Design patterns: elements of reusable object-oriented software
Design patterns: elements of reusable object-oriented software
Pattern-oriented software architecture: a system of patterns
Pattern-oriented software architecture: a system of patterns
The OPEN process specification
The OPEN process specification
Process patterns: building large-scale systems using object technology
Process patterns: building large-scale systems using object technology
The Unified Modeling Language user guide
The Unified Modeling Language user guide
N degrees of separation: multi-dimensional separation of concerns
Proceedings of the 21st international conference on Software engineering
Proceedings of the 21st international conference on Software engineering
The Rational Unified Process: an introduction
The Rational Unified Process: an introduction
The unified software development process
The unified software development process
Extreme programming explained: embrace change
Extreme programming explained: embrace change
On the criteria to be used in decomposing systems into modules
Communications of the ACM
Software Engineering: A Practitioner's Approach
Software Engineering: A Practitioner's Approach
The Java Language Specification
The Java Language Specification
ECOOP '01 Proceedings of the 15th European Conference on Object-Oriented Programming
A Note on Distributed Computing
MOS '96 Selected Presentations and Invited Papers Second International Workshop on Mobile Object Systems - Towards the Programmable Internet
A product line enhanced unified process
SPW/ProSim'06 Proceedings of the 2006 international conference on Software Process Simulation and Modeling
| Hi-index | 0.00 |
This chapter introduces an extension of the Rational Unified Process (RUP) with a method that supports the progressive, and separate, implementation of three different aspects: persistence, distribution, and concurrence control. This complements RUP with a specific implementation method, called Progressive Implementation Method (Pim), and helps to tame the complexity of applications that are persistent, distributed, and concurrent. By gradually and separately implementing, testing, and validating such applications, we obtain two major benefits: the impact caused by the requirements changes during development is reduced and testing and debugging are simplified. In addition, the authors hope to contribute to solving the lack of a specific implementation method in RUP.