User Scenarios

GUEST USER / Scenario 1

Persona (Ertugrul Düldül)

• 23 years old
• Student
• Currently pursuing bachelor’s degree
• Enthusiastic about basketball
• Playing, watching, and thinking about basketball

Goals

• Being an academic basketball researcher
• Learning physics such that he can nail basketball
• Learning mathematics like his mother tongue to be a gambler

Preconditions

• Ertugrul is not a member of the platform.

User story

• Ertugrul is a junior computer engineering student at Bogazici University. He wants to combine his computing and scientific skills with basketball and be the one who rules the whole game. He has been into basketball for as long as he can remember.

Scenario

• Ertugrul first visits the web page to look for a physics paper about the movement of a basketball. He sees he has to register to view content. After that he decides to register, to be able to read posts, comment, see what he has read up to now, publish papers and projects through his profile page, invite people to contribute to them and join academic collaborations; he provides his full name, password, and an e-mail address to register and validate his account. He provides his interest tags, namely engineering and physics. He also specifies his affiliation.

Action List

• 1 . Ertugrul visits the web page.
• 2 . He wants to search content but is unable to do so.
• 3 . He decides to register since all actions require to be registered.
• 4 . He fills the registration form.
• 5 . He searches for "mechanical physic".

Acceptance criteria

• 1.1.1 Users shall be able to search and see public papers or projects
• 1.1.2 Users shall be able to search and view users, public papers and projects
• 1.1.3 Users shall be able to view profile pages of authors, and collaborators of papers and projects
• 1.1.1 Registration
  • • 1.1.1.1 Users shall be able to register by providing name, surname, unique email address and password
  • • 1.1.1.2 Users shall validate the e-mail address for completing the registration phase
  • • 1.1.1.3 Users shall specify the research interests by tags
  • • 1.1.1.4 Users shall provide the information about affiliation

Mockup

• Ertugrul visits the web page.
• He wants to search content but is unable to do so.
• He decides to register since all actions require to be registered.
• He fills the registration form.
• He confirms his account.
• He searches for "mechanical physic".

Registered User / Scenario 2

Persona (Friedrich Nietzsche)

• 34 years old
• Nihilist.
• German philosopher, cultural critic, composer, poet, philologist, and scholar of Latin and Ancient Greek whose work has exerted a profound influence on modern intellectual history.
• Übermensch
• Loves horses

Goals

• Help other people comprehend the world around them
• Publish papers, create projects, and invite people to his research
• Paying respect to and supporting an independent academic platform

Preconditions

• The user has already logged in
• Friedrich Nietzsche is an old member of the platform
• He already has a great portfolio beforehand

User story

• Friedrich Nietzsche is a man who supports the independent academy. He wants to publish ideas/projects/papers on this free platform. He also stands up for every individual's right to feel free in academy and not hesitate to reveal their ideas.

Scenario

• Friedrich Nietzsche is a spirited member of academy but sick of people not appreciating good work. Since he believes his ideas are thrilling and paradigm-shifting, he applies to our platform using the web page to be a registered user so that he can freely publish his ideas/papers/projects. While publishing his new work he sets a topic of research, a deadline and some requirements. He creates a fund request and attaches some documents. He adds a summary part to his work that explains what the work is about and what type of publication it is (paper, project). He states that the project public and clicks publish. He can now see his paper is "in progress" (progress) and "awaiting funding" (status).

Action List

• 1 . Nietzsche is logged in and is looking at his profile page.
• 2 . He realizes it is a good time for creating a new publication and clicks "add" under publications.
• 3 . He fills out the new publication form according to his needs.
  • He sets a topic.
  • He writes a summary that explains what the work is/will be about.
  • He selects the type of publication to be "paper".
  • He skips the add files part.
  • He writes out some requirements.
  • He toggles the switch to apply for a funding.
• 4 . He clicks publish to finish creating the publication.
• 5 . Now back at his profile, he checks the info for the paper.
• 6 . He sees that the paper is in progress and is awaiting for funding.

Acceptance criteria

• 1.1.9.1 Users shall be able to create a new paper.
• 1.1.9.2 Users shall be able to create a new project.
• 1.1.9.3 Users shall be able to see the status of his/her paper(s).
• 1.1.9.4 Users shall be able to see the status of his/her project(s).
• 1.1.9.5 Users shall be able to edit the specifications of his/her paper(s).
• 1.1.9.6 Users shall be able to edit the specifications of his/her project(s).
• 1.1.9.7 Users shall be able to see his/her paper(s) in progress.
• 1.1.9.8 Users shall be able to see his/her project(s) in progress.

Mockup

• Nietzsche is logged in and is looking at his profile page.
• He realizes it is a good time for creating a new publication and clicks "add" under publications.

• He fills out the new publication form according to his needs.
  • He sets a topic.
  • He writes a summary that explains what the work is/will be about.
  • He selects the type of publication to be "paper".
  • He skips the add files part.
  • He writes out some requirements.
  • He toggles the switch to apply for a funding.
• He clicks publish to finish creating the publication.

• Now back at his profile, he checks the info for the paper.
• He sees that the paper is in progress and is awaiting for funding.

Registered User / Scenario 3

Persona (Atakan Kayalar)

• 10 years old
• Kid
• Primary school student
• Part time philosopher
• Enthusiastic about all kinds of books, papers, and projects
• Currently holding the Guinness Record for most books read in 5 months (250)

Goals

• Wants to expand his knowledge about academic philosophy
• Wants to publish papers, create projects, and invite people to his research
• Wants to join other academicians’ research

Preconditions

• The user has already logged in
• Atakan is a new member of the platform
• He has a great portfolio beforehand
• He has many followers who are interested in his research and quotas.
• He linked his Google Scholar account to his profile page.

User story

• Atakan is a primary school student who wants to broaden his academic skills. His main goal is to share his knowledge with the world so that a better world could be established with the academy.

Scenario

• The little philosopher visits his profile page using his android phone. By clicking his google scholar page link he sees that he has 98724 citations. There is an invite button that he can invite someone to his papers/projects. He also has an invitation box wherein he can see all invitations for him. He can accept or reject the invitations.

Action List

• 1 . The little philosopher logs in using his android phone.
• 2 . The little philosopher visits his profile page. He sees that he has 98724 citations.
• 3 . He looks at his pending paper and sees who is invited.
• 4 . He searches for one specific user and invites him.
• 5 . He checks the appliers for his paper.

Acceptance criteria

• 1.1.5 Users shall log in by email and password provided
• 1.1.6 Users shall be able to send a request to join the public papers or projects as collaborators
• 1.1.7 Users, as the owner of the papers or projects, shall be able to accept or reject requests
• 1.1.8 Users shall be able to invite any user to their papers/projects
• 1.1.9 Users shall be able to accept or reject invitations
• 1.1.10 Users shall be able to rate and comment on other users that they have collaborated with during the collaboration and after the project is completed
• 1.1.11 Users shall be able to collaborate on more than one paper/project
• 1.1.12 Users shall be able to have more than one paper/project topic posted
• 1.1.13 Users shall be able to specify a deadline for the paper/project
• 1.1.14 Users shall not be able to delete a paper/project that is in progress
• 1.1.20.2 Users shall be able to link their Google Scholar or ResearchGate accounts.
• 1.1.20.4 Users shall be able to see invitations that are sent from the other users.
• 1.1.23.1 Users shall be able to search; other users, papers, projects, conferences, and journals within the system.
• 1.1.24.1 Users shall be able to see upcoming conferences.

Mockup

• Atakan first logs in with his e-mail and password.

• Then the home page is opened.
• He goes to his profile page by clicking his own profile photo. (After closing the document)

• When he clicks on his own profile photo, his profile page is opened.
• He sees his followers, buttons for linking Google Scholar or ResearchGate Accounts, and information about himself he wrote.
• He looks at his pending papers.
• He invites users by invite button, looks at applicants by appliers button.

• When he clicks invite button, this menu is opened.
• He searches users to invite them.
• He sees who is invited before.
• He invites a user by clicking buttons.

• When he clicks Appliers button, this menu is opened.
• He closes the menu touching the screen. (not on the menu but anywhere else)