A Big-Picture Look at Enterprise Architectures
IT Professional
Domain-Driven Design: Tacking Complexity In the Heart of Software
Domain-Driven Design: Tacking Complexity In the Heart of Software
Enterprise Architecting: Critical Problems
HICSS '05 Proceedings of the Proceedings of the 38th Annual Hawaii International Conference on System Sciences - Volume 08
Architectural improvement by use of strategic level domain-driven design
Companion to the 21st ACM SIGPLAN symposium on Object-oriented programming systems, languages, and applications
Architectural improvement by use of strategic level domain-driven design
Companion to the 21st ACM SIGPLAN symposium on Object-oriented programming systems, languages, and applications
Agile enterprise software development using domain-driven design and test first
Companion to the 22nd ACM SIGPLAN conference on Object-oriented programming systems and applications companion
Role of Process Modeling in Software Service Design
ICSOC-ServiceWave '09 Proceedings of the 7th International Joint Conference on Service-Oriented Computing
The investigation of WEB software system based on domain-driven design
WISM'11 Proceedings of the 2011 international conference on Web information systems and mining - Volume Part I
Hi-index | 0.00 |
Purchasing a Commercial-Off-The-Shelf (COTS) package solution can be a complex and daunting task. Selecting and evaluating the right candidate is difficult, especially when the solution aims at the heart of company business. The company's competitive edge must be maintained, while at the same time ensuring the intended goals such as reduced costs and better functional coverage. A good Enterprise Architecture should be a prime tool when evaluating several solutions against the company's needs.In this paper we will recount the experience and lessons learned when we evaluated three COTS systems to replace a set of legacy oil trading and operations systems. Based on weaknesses in our Enterprise Architecture, we applied strategic domain-driven design principles to extend our Enterprise Architecture during the evaluation. We found that these techniques enabled us to thoroughly analyse our domain with the domain experts and provide answers based on tacit domain knowledge, without going through the cost and effort of performing a full-scale architectural analysis. At the same time, the tacit domain knowledge became explicit and shared, easing the communication with various stakeholders.