Embed Size (px)
Citation preview
Babis ThanopoulosAgro-Know
19-06-2015Rhodes, Greece, 2015
Community requirements
THE PROCESS
the process
• step 1: define the targeted personas of end users
• step 2: specify the content that is already used & the desired content for each use case
• step 3: top validated challenges for each of the targeted personas of the use case
• step 4: design & validate the features of the solution, adopting the OpenMinTeD services
• step 5: workflow for the integration / use of the text & data mining services
the process
• step 1: define the targeted personas of end users
• step 2: specify the content that is already used & the desired content for each use case
• step 3: top validated challenges for each of the targeted personas of the use case
• step 4: design & validate the features of the solution, adopting the OpenMinTeD services
• step 5: workflow for the integration / use of the text & data mining services
the process
• step 1: define the targeted personas of end users
• step 2: specify the content that is already used & the desired content for each use case
• step 3: top validated challenges for each of the targeted personas of the use case
• step 4: design & validate the features of the solution, adopting the OpenMinTeD services
• step 5: workflow for the integration / use of the text & data mining services
What is persona?• Persona: archetypal users of a service that
represent the needs of larger groups of users, in terms of their goals and personal characteristics
• Persona includes demographic, behavior patterns, goals, skills, attitudes & environment
the process
• step 1: define the targeted personas of end users
• step 2: specify the content that is already used & the desired content for each use case
• step 3: top validated challenges for each of the targeted personas of the use case
• step 4: design & validate the features of the solution, adopting the OpenMinTeD services
• step 5: workflow for the integration / use of the text & data mining services
What is persona?• Persona: archetypal users of a service that
represent the needs of larger groups of users, in terms of their goals and personal characteristics
• Persona includes demographic, behavior patterns, goals, skills, attitudes & environment
the process
• step 1: define the targeted personas of end users
• step 2: specify the content that is already used & the desired content for each use case
• step 3: top validated challenges for each of the targeted personas of the use case
• step 4: design & validate the features of the solution, adopting the OpenMinTeD services
• step 5: workflow for the integration / use of the text & data mining services
What is persona?• Persona: archetypal users of a service that
represent the needs of larger groups of users, in terms of their goals and personal characteristics
• Persona includes demographic, behavior patterns, goals, skills, attitudes & environment
the process
• step 1: define the targeted personas of end users
• step 2: specify the content that is already used & the desired content for each use case
• step 3: top validated challenges for each of the targeted personas of the use case
• step 4: design & validate the features of the solution, adopting the OpenMinTeD services
• step 5: workflow for the integration / use of the text & data mining services
the process
• step 1: define the targeted personas of end users
• step 2: specify the content that is already used & the desired content for each use case
• step 3: top validated challenges for each of the targeted personas of the use case
• step 4: design & validate the features of the solution, adopting the OpenMinTeD services
• step 5: workflow for the integration / use of the text & data mining services
content that is used now in service & used from other external sourcese.g. for AGRIS use case
other content would like to include• research data• figures / images• socio economic data• researchers’ profiles• organisations profiles
the process
• step 1: define the targeted personas of end users
• step 2: specify the content that is already used & the desired content for each use case
• step 3: top validated challenges for each of the targeted personas of the use case
• step 4: design & validate the features of the solution, adopting the OpenMinTeD services
• step 5: workflow for the integration / use of the text & data mining services
the process
• step 1: define the targeted personas of end users
• step 2: specify the content that is already used & the desired content for each use case
• step 3: top validated challenges for each of the targeted personas of the use case
• step 4: design & validate the features of the solution, adopting the OpenMinTeD services
• step 5: workflow for the integration / use of the text & data mining services
conduct problem validation interviews for users’ & data requirements elicitation through• f2f meetings• online survey• focused workshops
the process
• step 1: define the targeted personas of end users
• step 2: specify the content that is already used & the desired content for each use case
• step 3: top validated challenges for each of the targeted personas of the use case
• step 4: design & validate the features of the solution, adopting the OpenMinTeD services
• step 5: workflow for the integration / use of the text & data mining services
conduct problem validation interviews for users’ & data requirements elicitation through• f2f meetings• online survey• focused workshops
the process
• step 1: define the targeted personas of end users
• step 2: specify the content that is already used & the desired content for each use case
• step 3: top validated challenges for each of the targeted personas of the use case
• step 4: design & validate the features of the solution, adopting the OpenMinTeD services
• step 5: workflow for the integration / use of the text & data mining services
the process
• step 1: define the targeted personas of end users
• step 2: specify the content that is already used & the desired content for each use case
• step 3: top validated challenges for each of the targeted personas of the use case
• step 4: design & validate the features of the solution, adopting the OpenMinTeD services
• step 5: workflow for the integration / use of the text & data mining services
the process
• step 1: define the targeted personas of end users
• step 2: specify the content that is already used & the desired content for each use case
• step 3: top validated challenges for each of the targeted personas of the use case
• step 4: design & validate the features of the solution, adopting the OpenMinTeD services
• step 5: workflow for the integration / use of the text & data mining services
Wireframe example
the process
• step 1: define the targeted personas of end users
• step 2: specify the content that is already used & the desired content for each use case
• step 3: top validated challenges for each of the targeted personas of the use case
• step 4: design & validate the features of the solution, adopting the OpenMinTeD services
• step 5: workflow for the integration / use of the text & data mining services
the process
• step 1: define the targeted personas of end users
• step 2: specify the content that is already used & the desired content for each use case
• step 3: top validated challenges for each of the targeted personas of the use case
• step 4: design & validate the features of the solution, adopting the OpenMinTeD services
• step 5: workflow for the integration / use of the text & data mining services
the process
• step 1: define the targeted personas of end users
• step 2: specify the content that is already used & the desired content for each use case
• step 3: top validated challenges for each of the targeted personas of the use case
• step 4: design & validate the features of the solution, adopting the OpenMinTeD services
• step 5: workflow for the integration / use of the text & data mining services
the process
• step 1: define the targeted personas of end users
• step 2: specify the content that is already used & the desired content for each use case
• step 3: top validated challenges for each of the targeted personas of the use case
• step 4: design & validate the features of the solution, adopting the OpenMinTeD services
• step 5: workflow for the integration / use of the text & data mining services
the process
• step 1: define the targeted personas of end users
• step 2: specify the content that is already used & the desired content for each use case
• step 3: top validated challenges for each of the targeted personas of the use case
• step 4: design & validate the features of the solution, adopting the OpenMinTeD services
• step 5: workflow for the integration / use of the text & data mining services
HOW TO COLLECT REQUIREMENTS
1. dedicated sessions @Kick-off meeting
• work in groups - one group / research community– Life sciences, Agriculture / Biodiversity, Social
sciences and Scholarly communication• each group should include representatives of
the community and text mining services providers/developers
• select one use case / research community & define the:– personas characteristics, content requirements, key
information challenges and features of the solution
2. focused workshops & interviews / each use case • to define the users’ & content requirements
– tools: • focus groups meetings/discussions• selected interviews• online survey (set up by Agro-Know)
• user persona analysis & requirements (interviews + profile of user)– tools: interviews
• development of user personas + usage scenarios + wireframes• focus group• interviews with representatives of the research community, in order to
validate the features of the solution (wireframes)• reporting the activity• guidelines by Agro-Know, incl. instructions on how to organise the
workshop & report the activity
COMMUNITY REQUIREMENTS SESSION (@KICK-OFF MEETING)
1. split in 4 groups (one group for each researches’ community)
2. focus on one use case per science/community
3. define the personas characteristics, content requirements, key information challenges and features of the solution
1. split in 4 groups (one group for each researches’ community)
2. focus on one use case per science/community
3. define the personas characteristics, content requirements, key information challenges and features of the solution
1. split in 4 groups (one group for each researches’ community)
2. focus on one use case per science/community
3. define the personas characteristics, content requirements, key information challenges and features of the solution
VISIONING THE NEW INFO SERVICE
1. draw screen / wireframe of each use case powered by text & data mining service
2. Identify the workflow – put the wireframes in logical order
1. draw screen / wireframe of each use case powered by text & data mining service
2. Identify the workflow – put the wireframes in logical order
1. draw screen / wireframe of each use case powered by text & data mining service
2. Identify the workflow – put the wireframes in logical order
1. draw screen / wireframe of each use case powered by text & data mining service
2. Identify the workflow – put the wireframes in logical order
