Instructor's Guide: Software Architecture

Rationale

This chapter introduces the notion of software architecture, which is becoming a prominent topic in the Software Engineering literature. It presents a case study, clearly reflecting the author's interests, which nevertheless illustrates some of the complexities that may arise in developing a heterogeneous system. The remainder of this chapter is rather technical, intended to illustrate the issues that arise in glueing different object models together.

Hints

When discussing the material, try not to get stuck in the technical details. The overall picture must remain clear. That is to say, the solutions presented in this chapter are meant to illustrate the issues in bridging, respectively, the paradigm gap and the language gap. This may be done in radically different ways, nevertheless the basic solutions will not be so much different from those presented in this chapter.

Project assignments

As subjects for papers you may recommend your students to study the

the software architecture of actual systems

As a practical assignment, I suggest to let students experiment with

wrapping Java around existing C/C++ code

Comments

One of the hardest parts in understanding the interfacing between different languages is to understand the actual flow of control as it is passed around the various components. Since students seem to be quite fond of practical examples. think of some samll examples to illustrate the issues involved.

[] readme course(s) preface I 1 2 II 3 4 III 5 6 7 IV 8 9 10 V 11 12 afterthought(s) appendix reference(s) example(s) resource(s) _

You may not copy or print any of this material without explicit permission of the author or the publisher. In case of other copyright issues, contact the author.