(New page: {| border="1" align="center" style="text-align:center;" |+ Testing Exercise - document your work on methods used | '''Number''' || '''Requirement tested''' || '''Method used''' || '''Test...) |
|||
| Line 5: | Line 5: | ||
| 0 || || only for students exercising with method guidelines || || || || | | 0 || || only for students exercising with method guidelines || || || || | ||
|- | |- | ||
| − | | 1 || || || || || || | + | | 1 || Reasoning requirement 2 || 2 || mg2.owl || Musicindustry:genre doesn't have a detailed domain; the domain thing is too generic || It could be useful to create a domain - genre - that permit to create an union between "album 1" and "track 1" in order to express, for example, the genre "pop" for the album 1 and not only for the track 1 || |
|- | |- | ||
| 2 || || || || || || | | 2 || || || || || || | ||
| Number | Requirement tested | Method used | Test applied | Error(s) found | Suggestions/ideas for solution | Additional notes |
| 0 | only for students exercising with method guidelines | |||||
| 1 | Reasoning requirement 2 | 2 | mg2.owl | Musicindustry:genre doesn't have a detailed domain; the domain thing is too generic | It could be useful to create a domain - genre - that permit to create an union between "album 1" and "track 1" in order to express, for example, the genre "pop" for the album 1 and not only for the track 1 | |
| 2 | ||||||
| 3 | ||||||
| 4 |
'Ontology Design Patterns'