Child pages
  • ProjectRepository_Scenarios
81 more child pages
Skip to end of metadata
Go to start of metadata

Scenarios

Terminology

The parts of a scenario are:

  • Scenario Name: Should say something about what action the user is trying to accomplish
  • Scenario ID: Short form of project name plus arbitrary identification number
  • Author: The person or people who wrote it
  • Source: The author's organization
  • Date: When the scenario was created (optional)
  • URL: Where the scenario is available online (optional)
  • Description: One or more paragraphs describing the who, what, when, where, and why of the scenario
  • Other Related Information: Space for referring to additional information (optional)

Suggested Content for Scenario Requests

For our Mellon Foundation funded project, A Technology Analysis of Repositories and Services, we are gathering scenarios and transforming them into use cases that we can compare with the functionality of different repositories. We need your help in collecting scenarios related to (name of project).

What is a scenario? A scenario is a brief narrative, or story, that describes the hypothetical use of a system. In one or more paragraphs, a scenario:

  • Tells who is using the system and what they are trying to accomplish.
  • Provides a realistic, fictional account of a user's constraints: when and where they are working, why they are using the system, and what they need the system to do for them.
  • Describes any relevant aspects of the context in which the user is working with the system, including what information the user has on hand when beginning to use the system.
  • Gives the user a fictional name, but it also identifies the user's role, such as student, faculty member, staff, or general public.
  • Indicates what the user regards as a successful outcome of using the system.

Please send us scenarios that encapsulate the range of users and uses of (name of project). In addition to the narratives, please include the name(s) of the author(s), the date of latest modification for the scenario(s), and the name of your organization (if not the Sheridan Libraries). Please give each scenario a title. If you have posted the scenarios online, please send us the URL. Please send your scenarios to us via this email address: <scenarios@dkc.jhu.edu>.

We will use your scenario(s) and others to develop use cases, structured descriptions that are abstracted from scenarios. We will employ these use cases to gather functional requirements for repository applications and interfaces and to compare their capabilities.

Thank you for your help.

(Project staff: When you send out a request for scenarios, you may wish to include the description from SallyOrdersPizza as an example.)

Guidelines

Scenarios describe how a user accomplishes a task using a system. Scenarios describe a particular instance of a use of the system, as opposed to use cases, which describe a generalized interaction with the system. Scenarios contain fictional data such as a professor's name and course name. They tell stories.

Just a reminder: Scenario contributors should send their scenarios to <scenarios@dkc.jhu.edu>.

Storing scenarios in the wiki (project staff only)

Add scenarios below. Don't forget to apply the scenario template. See SallyOrdersPizza. Assign each scenario an ID using a short project name and an arbritrary number.

Scenarios

ID

Name

Being used for analysis

Under evaluation

Revised

Notes

VRC-1

AncientRomanUrbanArchitecture

X

 

 

 

VRC-2

TwoPhotographyCourses

X

 

 

 

VRC-3

ItalianRenaissanceArt

 

X

 

 

VRC-4

17thand18thCenturySpain

X

 

 

 

VRC-5

ArtHistorySurvey

X

 

 

 

Uppsala-01

JournalPublishingWorkflowJRM

X

 

 

 

Uppsala-02

JournalPublishingWorkflowSMT

 

X

 

 

Uppsala-03

PublishingWorkflowUndergradTheses

 

X

 

 

Fowler-1

JHUFacultyUrbanLandscape

X

 

 

 

Fowler-2

PreCollegeStudentBaltimoreNeighborhood

X

 

 

 

Fowler-3

ArchitecturalHistorianNineteenthCentury

X

 

 

 

DLF-1

OnlineResourceList

X

 

 

 

DLF-2

ScholarsBoxImages

X

 

 

 

DLF-3

AssignmentSearchBox

X

 

 

 

UCB-1

WordProcessorIntegration

 

X

 

 

UCB-2

StudentTrackAssignments

X

 

 

 

UCB-3

IntegrateEmail

X

 

 

 

UCB-4

AlternateCharacterSetEditing

 

X

 

 

UCB-5

CalendarLinksToItem

 

X

 

 

UCB-6

StudentGrouping

X

 

 

 

UCB-7

MultilingualMultimediaDictionary

X

 

 

 

UCB-8

WirelessClicker

X

 

 

 

Yale-1

AdHocImageGroupCreation

 

X

 

 

Yale-2

CollaborativeCourseResourcesRecommendation

 

X

 

 

Yale-3

CollaborativeLiteratureReview

X

 

 

 

Yale-4

SocialScienceDataAnalysis

X

 

 

 

Yale-5

NewMaterialsLists

X

 

 

 

Yale-6

AssociatingCourseInformationWithLibraryResources

X

 

 

 

NWU-1

DocumentingEvanstonPublicArtImages

X

 

 

 

NWU-2

AsianBuddhistArt

X

 

 

 

NWU-3

AnnotatingLawrenceLessigAudio

X

 

 

 

NWU-4

FutureOfJournalism

X

 

 

 

NWU-5

AnnotatingSupremeCourtArgumentsOnline

 

X

 

 

UW-1

IntermediateForeignLanguageListeningSkillLessons

X

 

 

 

UW-2

ProblemSolvingWithComputersOnlineLectures

X

 

 

 

UW-3

AnnotationsAsALearningTool

 

X

 

 

UW-4

MovingToANewUniversity

X

 

 

 

UW-5

ImportAndExport

X

 

 

 

UW-6

VirusDetectionDuringImport

X

 

 

 

UW-7

VirusDetectionWhileAuthoring

X

 

 

 

UW-8

PhysicsPaperInPreprintAndCourse

X

 

 

 

UW-9

ChemicalMoleculesInHomeworkAssignments

 

X

 

 

UW-10

TeachingConceptsInOceanicSciences

X

 

 

 

UW-11

InteractiveImages

X

 

 

 

UW-12

PojectCollaborationForOnlineCourseDevelopment

 

X

 

 

SU-1

OnlineResourcesListForHumanitiesSeminar

X

 

 

 

SU-2

AddContentToMultipleTools

 

X

 

 

SU-3

The Humanities 345 Materials

 

X

 

 

Berkeley-1

ImagesOfAngelIslandInEthnicStudies

X

 

 

 

IU-1

Biology101SearchJournals

X

 

 

 

Toronto-1

DiscoveryAndRetrievalOfAlternateTrainingContent

X

 

 

 

Toronto-2

PhysicsCourseWithSynchronizedAudioAndVideo

X

 

 

 

DC-1

SharingContentMultipleInstructors

X

 

 

 

DC-2

AccessingContentViaWebServices

X

 

 

 

DC-3

ContentToExternalLMS

X

 

 

 

DC-4

Dartmouth Jewish Sound Archives

X

 

 

 

DC-5

Lexinomicon Assets

 

X

 

 

PM-1

DownloadingContent

X

 

 

 

PM-2

UniversalAccess

X

 

 

(PM-3 was merged with another scenario)

PM-4

RestrictedAccess

X

 

 

 

PM-5

PayPerCourse

X

 

 

 

PM-6

AccessWithoutAComputer

X

 

 

 

PM-7

FederatedSearching

X

 

 

 

PM-8

CitationLinking

X

 

 

 

PM-9

PersonalResearchAssistant

X

 

 

 

Blog-1

ContextPreservation

X

 

 

 

ETD-1

ETDs

 

X

 

 

Research-1

SharingDataSets

X

 

 

 

EPS-1

UsingGISasDataManagementFramework

 

X

 

 

WRLC-1

TrustedRepositoryForDigitalAssetManagement

X

 

 

 

WRLC-2

RepurposingContent

X

 

 

 

WRLC-3

FormatMigration

X

 

 

 

UVA-1

AccessElectronicTextCollection

 

X

 

 

UVA-2

AccessDigitalArtAndArchitecture

 

X

 

 

UVA-3

Add Scholarly Edition to DL

X

 

 

 

AIHT-1

AihtIngest

X

 

 

 

AIHT-2

AihtFormatMigration

X

 

 

 

AIHT-3

AihtExport

X

 

 

 

UM-1

StagedReleaseOfBothContentAndMetadata

X

 

 

 

UM-2

HarvestableMetadataButTimeReleasedContent

X

 

 

 

UM-3

SomeButNotAllContentRestricted

X

 

 

 

UM-4

AutomaticCollectionMappingAndTopicBrowse

X

 

 

 

UM-5

StreamingAndDownloadableVideo

X

 

 

this is the 83rd scenario

 

add more scenarios here!

 

 

 

 

  • No labels