"... In PAGE 66: ... All these models give us the state structure model of a Simple Music Management System. At this point we can create an Alloy code (see Table8 ) that reflects the composition of the two roles and ... In PAGE 66: ... We have to reflect in the Alloy code new relations between the AtristTracks and UserTrack types and between the Album and UserAlbumTrack types. To make a new relation between two already specified attributes in the current version of Alloy, we have to extend existing types: UserTrack and UserAlbum (lines 7-8 in Table8 ). To ensure that new attributes (UserTrack1 and UserAlbum1) and their predecessors participate in the same relations we created two facts (line 9-10 in Table 8).... In PAGE 66: ... To make a new relation between two already specified attributes in the current version of Alloy, we have to extend existing types: UserTrack and UserAlbum (lines 7-8 in Table 8). To ensure that new attributes (UserTrack1 and UserAlbum1) and their predecessors participate in the same relations we created two facts (line 9-10 in Table8 ). Line 11 in Table 8 specifies the multiplicity invariant.... In PAGE 66: ... Line 11 in Table 8 specifies the multiplicity invariant. Note that this multiplicity is specified in the context of one user (as it is shown in a diagram from Table8 ): we require that for any artist album there is only one user album in the context of a given user music. When we create an Alloy code, we have to take into account possible conceptual cycles .... In PAGE 67: ... 5.4 Analysis of the Composed Model Based on the Alloy code from Table8 , several instance diagrams can be generated. One of these diagrams is shown in Figure 29.... ..."

"... In PAGE 7: ...73 Ludacris 6.93 The similarity distances for the artists of the songs used as examples earlier are shown in Table3 . Note that artists of similar genres and styles are closer together.... ..."

"... In PAGE 7: ...73 Ludacris 6.93 The similarity distances for the artists of the songs used as examples earlier are shown in Table3 . Note that artists of similar genres and styles are closer together.... ..."

"... In PAGE 5: ... The two integrations described above resulted in three versions of the LayoutManager: the original, SkyBlue, and Amulet ver- sions. These are listed as LayoutManager versions 1, 2, and 3 in Table1 . Two versions each of the PaletteADT, Pal- etteArtist, ChuteArtist, and WellArtist were created as well: original components maintaining local constraints with in- line code (versions 1 of the four components in Table 1) and components whose constraints were managed elsewhere in the architecture (versions 2 of the four components in 4.... In PAGE 5: ... These are listed as LayoutManager versions 1, 2, and 3 in Table 1. Two versions each of the PaletteADT, Pal- etteArtist, ChuteArtist, and WellArtist were created as well: original components maintaining local constraints with in- line code (versions 1 of the four components in Table1 ) and components whose constraints were managed elsewhere in the architecture (versions 2 of the four components in 4. This may seem like unnecessary work.... In PAGE 6: ... VIII. Plug and Play The four versions of PaletteADT and PaletteArtist, two versions of ChuteArtist and WellArtist, and six versions of the LayoutManager, described in Table1 , could potentially be used to build 384 different variations of the KLAX archi- tecture. Three such variations were described in Section III (using versions 1 of all five components), Section V (using versions 2 of the five components), and Section VI (replac- ing LayoutManager-2 with LayoutManager-3 in the archi- tecture from Section V).... In PAGE 7: ... In a component-based style, such as C2, the number of possible architectures grows combinatorially as the number of behaviorally related components increases.7 Thus, the 18 components depicted in Table1 can generate 384 distinct versions of KLAX. Of course, every possible architecture is neither meaningful (e.... ..."

"... In PAGE 7: ... The two integrations described in the previous section resulted in three versions of LayoutManager: the original, SkyBlue, and Amulet versions. These are listed as Layout- Manager versions 1, 2, and 3 in Table1 . Two versions each of PaletteADT, PaletteArtist, ChuteArtist, and WellArtist were created as well: original components maintaining local constraints with in-line code (versions 1 of the four compo- nents in Table 1) and components whose constraints were managed elsewhere in the architecture (versions 2 of the four components in Table 1).... In PAGE 7: ... These are listed as Layout- Manager versions 1, 2, and 3 in Table 1. Two versions each of PaletteADT, PaletteArtist, ChuteArtist, and WellArtist were created as well: original components maintaining local constraints with in-line code (versions 1 of the four compo- nents in Table1 ) and components whose constraints were managed elsewhere in the architecture (versions 2 of the four components in Table 1).8 7.... In PAGE 7: ... VIII. Building a Program Family The four versions of PaletteADT and PaletteArtist, two versions of ChuteArtist and WellArtist, and six versions of LayoutManager, described in Table1 , could potentially be used to build 384 different variations of the KLAX architec- ture, i.... In PAGE 11: ... In a component-based style, such as C2, the number of possible architectures grows combinatorially as the number of behaviorally related components increases. Thus, the 18 components depicted in Table1 can generate 384 distinct versions of KLAX. Of course, every possible architecture is not necessarily meaningful (e.... ..."

"... In PAGE 6: ... In our experiments, we used styles and moods that included 50 or more songs, which amounted to 32 styles and 100 moods. See Table2 for a list of the most popular moods and styles. Due to the diversity of the 18 artists chosen for evalu- ation, some moods contain identical categorizations of our music, leaving 78 distinct moods out of the original 100.... ..."