SuSE Linux on a PowerBook G4 Workstation

While it is possible to develop an architectural design for a network by simply defining a set of components based on experience or typical installations, a robust design will generally be based on an understanding of logical and physical data flows.1 This would normally be expressed in terms like connectivity, bandwidth, protocols, etc. For the purposes of this paper, the approach taken was to generate connectivity requirements by developing data flow diagrams. This required some, mostly implicit, process and organization assumptions to be made. Note that the flows and connectivity solutions selected and described below are not unique; many other variations are possible.