M A X - P L A N C K - G E S E L L S C H A F T Bericht des Partnerinstituts Sabine Krott 1.0 Pilotentreffen im Harnack-Haus, 8. Juni 2006 Distribution: pilots Filename: Revision History: VersionDateAuthorComment

M A X - P L A N C K - G E S E L L S C H A F T 2 Filename, last changed: dd.mm.yyyy Übersicht Validierung Warum Validierung? Validierungsprozeß Beispiele Submission UC Diagramm UC Spezifikation Storyboard

M A X - P L A N C K - G E S E L L S C H A F T 3 Filename, last changed: dd.mm.yyyy Validierung Validierung der Use Cases

M A X - P L A N C K - G E S E L L S C H A F T 4 Filename, last changed: dd.mm.yyyy Validierung Warum Validierung? Use Cases wurden auf der Grundlage der Usage Scenarios geschrieben Usage Scenarios und Use Cases müssen einander entsprechen alle Use Cases müssen einzeln geprüft werden auf: Vollständigkeit Korrektheit Konsistenz Use Cases müssen in ihrer Gesamtheit geprüft werden auf: Vollständigkeit (Funktionalitätsumfang) Referenz zu offenen Fragen in Bugzilla

M A X - P L A N C K - G E S E L L S C H A F T 5 Filename, last changed: dd.mm.yyyy Just in Time UC Validierung Setup development Validierung UC Rel 0.1 Validierung UC Rel 0.5 Validierung UC Rel 0.3 Design Build Test Deploy Rel. 0.1 Design Build Test Deploy Rel. 0.3 Design Build Rel. 0.5 …… System Design FW Rel 0.1 FW Rel 0.3 Feedback Piloten Rel. 0.1 Feedback Piloten Rel. 0.3 SMC & ZIM SMC ZIM FIZ Legende

M A X - P L A N C K - G E S E L L S C H A F T 6 Filename, last changed: dd.mm.yyyy Validierungsprozeß Klärung offener Fragen aus Bugzilla Validierungsphase UC 1 +n = USC 1 UC 2 +n = USC 2 UC n+n = USC n Übergabe UC an ZIM Abnahme UC durch ZIM überarbeitete USC + Δ-Dokument Bugzilla ZIM + SMC

M A X - P L A N C K - G E S E L L S C H A F T 7 Filename, last changed: dd.mm.yyyy Beispiele Beispiel Submission

M A X - P L A N C K - G E S E L L S C H A F T 8 Filename, last changed: dd.mm.yyyy Beispiel Use Case Diagramm

M A X - P L A N C K - G E S E L L S C H A F T 9 Filename, last changed: dd.mm.yyyy Beispiel Use Case Spezifikation 2 UC_PM_SM_01 create item The user creates a new item and provides item data. 2.1 Triggers The user wants create a new item. 2.2 Actors Depositor 2.3 Pre-Conditions None. 2.4 Flow of Events 1.The user chooses to create an item. 2.The system displays a list of all collections for which the user has the privileges as Depositor. 3.The user selects a collection and confirms the choice. 4.Extension point: fetch metadata

M A X - P L A N C K - G E S E L L S C H A F T 10 Filename, last changed: dd.mm.yyyy Beispiel Use Case Spezifikation (Forts.) a)If the user wants to harvest metadata from an external system include use case UC_PM_SM_04 fetch metadata from external system with selected collection as target collection. b)If the user wants to get metadata from an existing item include use case UC_PM_SM_05 fetch metadata from template item 5.The system creates a new item with the user as the owner in the selected collection. The item is in state pending and default values for attributes and metadata values are inherited from the metadata set and/or the collection settings. 6.Continue with use case UC_PM_SM_02 edit item with the new item as selected item. The use case ends successfully. 2.5 Alternatives 1.The user selects an item as template for a new item. a)The system creates a new item in state pending. The collection and default values for attributes and metadata values are inherited from the item used as template. b)Continue with Flow of Events step Post-Conditions / Results A new item with the user as the owner has been created.

M A X - P L A N C K - G E S E L L S C H A F T 11 Filename, last changed: dd.mm.yyyy Beispiel Storyboard

M A X - P L A N C K - G E S E L L S C H A F T 12 Filename, last changed: dd.mm.yyyy Validierung Sabine Krott 089/ (München) 0331/ (Golm) Fragen? Vielen Dank!