A Good Architecture for Object-Oriented Information Systems
Structures, Designs, and Patterns
Abstract
Without a good architecture, a software system is hard to understand, predict, manage, and optimize. When a project team does not develop and maintain a good architecture, they increase the risk of the project’s failure. Fortunately, almost all commercial Object-Oriented Information Systems can be constructed using a fairly simple, well-structured architecture built with common design patterns. This tutorial presents a simple and good architecture for building an OOIS along with the detailed designs to help implement the system in developed or purchased software. By following this architecture, a project team will overcome one of the major problems that can prevent it from success and it can focus on managing the rest of the project’s high risk areas.
Author
Mark L. Fussell has been developing applications, frameworks, and architectures for information systems for more than ten years. In the last several years he has focused on defining a sound overall architecture and the frameworks needed to support both large project teams building complex OO systems as well as small project teams trying to rapidly develop simpler systems. The types of projects he has worked on include Health Care, Shipping, Social Service, and Political/Military information systems.
Table of Contents
Figures
- Enlargement 1: Final High Level Architecture
- Enlargement 2: Domain to Data binding
- Enlargement 3: Domain through to database
- Enlargement 4: Composition of Canvases and UI models
- Enlargement 5: Domain Adaptor Composition
- Enlargement 6: Detailed System Architecture
- Enlargement 7: Object diagram (top)
- Enlargement 8: Object diagram (bottom)
- Enlargement 9: Module level architecture (frameworks)
- Enlargement 10: Module level architecture (application)
- Enlargement 11: Larger Applications
- Enlargement 12: 3-Tier Distributed UI
- Enlargement 13: 3-Tier Distributed Domain
Other Versions
|
