Two powerful approaches to system modeling, each of which addresses important issues in the system development process, are currently available for use: architecture view sets and domain level object modeling. Each of these techniques is insufficient to architect complex, software intensive systems when used alone - object modeling does not address important physical and low-level architectural concerns and an architecture depiction may violate a smooth object development unintentionally. Additionally, the two approaches are interdependent and interact in conflicting, confusing ways. This is the central nature of the architecture/software design bind. This paper suggests a solution to the architecture/software design bind by including the domain object model in the architecture view set as a full fledged, participating view - the Mission Object View. This allows a controlled and complete relationship between object constructs and architecture entities.
展开▼
