Design patterns: elements of reusable object-oriented software
Design patterns: elements of reusable object-oriented software
Software architecture: perspectives on an emerging discipline
Software architecture: perspectives on an emerging discipline
Pattern-oriented software architecture: a system of patterns
Pattern-oriented software architecture: a system of patterns
Software reuse: architecture, process and organization for business success
Software reuse: architecture, process and organization for business success
Software architecture in practice
Software architecture in practice
AntiPatterns: refactoring software, architectures, and projects in crisis
AntiPatterns: refactoring software, architectures, and projects in crisis
Developing Business Objects
Architecture of the San Francisco frameworks
IBM Systems Journal
Enterprise solutions structure
IBM Systems Journal
A standard for architecture description
IBM Systems Journal
Experiences in reusing technical reference architectures
IBM Systems Journal
A standard for business architecture description
IBM Systems Journal
IBM Systems Journal
Experiences in reusing technical reference architectures
IBM Systems Journal
A method for designing secure solutions
IBM Systems Journal - End-to-end security
What is software architecture?
Proceedings of the South African Institute for Computer Scientists and Information Technologists Conference
Hi-index | 0.00 |
Today's approaches to solution development are still primarily based on "handcrafting" and bear little relationship to the asset-based engineering methods so successfully used in other disciplines. In this paper we argue that these handcrafting approaches have passed their "sell-by" dates, and a more disciplined and constrained method of system development is needed. We focus particularly on the definition of technical architectures as the basis for constructing applications. We argue that a constrained set of reference architectures for a given set of problem domains is not only feasible, but mandatory for large-scale enterprise development, and we provide some example fragments of reference architectures for the administrative systems domain. These reference architectures and their successors, harvested and continually refreshed from successful consulting engagements, will form the basis of IBM's asset-based approach to solutions development in the future.