V.B a l a s u b r a m a n i a Bang Min MaJoonhee Voo I n this .sidebar, we denionstrate the .systematic design pr inciples and methodologies advocated by many of this special section's authors for a Wor Id-Wide Web (WWW) application. We used these approaches to reimplement AC.M SKII,INK'S I.INKBase", containing abstracts from conferences and other hypermedia-related "events." We followed the seven steps of the Relationship Management (RM) methodology [?>]. In the irrst step, entity-relationship design, we identified five entities (Organization, Event, Eventjtem, Person, and Publication) and eight relationships among them. The second step, entity design, involved slicing;m entity's attributes into different (overlapping) subsets, with a head slice connected to the others by structtrr al links [2]. While the RM methodolog)' prescribes guidelines for .slicing a given entity, it does not di.scuss combining slices from different entities for presentation. We added the concept of a cross-entity slicf comhmmg elements from different entities to be pre.sented in a single window. For example, to display details about a confer ence event adequately, we included attributes from the Organization, Person, and Publication entities. We also added the concept of a minimttitt slice-the minimal .set of an entity's attributes to inclirde (as anchors) in slices from other entities. This concept is similar to identifying objects and groups of objects suggested by [1]. These anchors are the starting points of applicative or reference links, while anchors belonging to the same entity (for example, description in Figure 1) are the starting points of structural links [2]. Slicing helped us determine the ajjpropriate chunks of information to be displayed without fragmentation, tlitrs increa.sing local coherence [5]. The third step, navigation design, produced a Relationship V.