The C++ programming language (2nd ed.)
The C++ programming language (2nd ed.)
Design patterns for object-oriented software development
Design patterns for object-oriented software development
The essential distributed objects survival guide
The essential distributed objects survival guide
Object-oriented methods (UML ed., 2nd ed.): a foundation
Object-oriented methods (UML ed., 2nd ed.): a foundation
| Hi-index | 4.10 |
Conventional wisdom holds that building high-end business applications is unavoidably difficult because applications and the technology for implementing them are complex. Empirical evidence from real projects amply reinforces this conclusion. Building business applications requires technical knowledge about database design, entity relationship or object modeling, GUI design, middleware technology, programming languages, operating systems, prototyping tools, and so on. Pulling together a development environment and a knowledgeable team capable of tackling a large application can be a major hurdle in starting a new project. It can be argued that spiraling technical complexity makes it difficult to focus on the application's core business problem. Complicated prototyping tools may help with early rapid iteration, but they result in throwaway mock-ups that quickly lose sync with the application as it evolves. To reach a new level of productivity and quality in application building, we need something better. This article begins with a simple business application and attempts to sketch out what an "ideal" approach to specifying it might be. From this basic example, design and process patterns emerge that allow for the specification of a comprehensive environment that meets these criteria.