Pattern-oriented software architecture: a system of patterns
Pattern-oriented software architecture: a system of patterns
Communications of the ACM
Software component quality assessment in practice: successes and practical impediments
Proceedings of the 24th International Conference on Software Engineering
Documenting Software Architectures: Views and Beyond
Documenting Software Architectures: Views and Beyond
The Devil is in the Detail: A Comparison of CORBA Object Transaction Services
OOIS '00 Proceedings of the 6th International Conference on Object Oriented Information Systems
Evaluating the Performance of EJB Components
IEEE Internet Computing
Communications of the ACM - Service-oriented computing
A quality-driven systematic approach for architecting distributed software applications
Proceedings of the 27th international conference on Software engineering
Tool support for just-in-time architecture reconstruction and evaluation: an experience report
Proceedings of the 27th international conference on Software engineering
Tool support for optimization-based architectural evaluation
MPEC '05 Proceedings of the second international workshop on Models and processes for the evaluation of off-the-shelf components
Stability of Feature Selection Algorithms
ICDM '05 Proceedings of the Fifth IEEE International Conference on Data Mining
Capturing and Using Software Architecture Knowledge for Architecture-Based Software Development
QSIC '05 Proceedings of the Fifth International Conference on Quality Software
Glass box: capturing, archiving, and retrieving workstation activities
Proceedings of the 3rd ACM workshop on Continuous archival and retrival of personal experences
Performance prediction of J2EE applications using messaging protocols
CBSE'05 Proceedings of the 8th international conference on Component-Based Software Engineering
| Hi-index | 0.00 |
Understanding an applicationýs functional and non-functionalrequirements is normally seen as essential fordeveloping a robust product suited to client needs. Thispaper describes our experiences in a project that, bynecessity, commenced well before concrete clientrequirements could be known. After a first version of theapplication was successfully released, emergingrequirements forced an evolution of the applicationarchitecture. The key reasons for this are explained,along with the architectural strategies and softwareengineering practices that were adopted. The resultingapplication architecture is highly flexible, modifiable andscalable, and therefore should provide a solid foundationfor the duration of the applicationýs lifetime.