Instructors' Guide

1. As elements in a software architecture, we can distinguish between processing elements, data elements and connections. See slide Elements. A software architecture description may serve to verify critical properties of the system, including properties such as availability, throughput, and interoperability.
2. See the discussion in section Elements, in particular the definition from  [Practice].
3. Patterns for distributed object architectures range over various levels: framework, application, system, enterprise, and the intra/Internet level. In particular the latter levels require an effort of standardization and agreement on protocols. Patterns on the lower levels are important to make good use of the technology, for example CORBA.
4. A possible example is the architecture for a multimedia information system, of which a sketch is given in section Midi,
5. Simply, the separation of knowledge-level and system-level aspects. For example, business logic would be a suitable candidate. See section Logic.
6. The issues that play a role are listed in slide Objects. The actual solution will, naturally, depend on the language for which the extension is made.
7. The JNI allows for the coupling of functions to (native) object methods. However, the JNI does not provide a standard way to associate Java objects with native C++ objects. See section JNI.
8. The choice for an architectural style is determined by both technological constraints and application requirements. See section Styles.