Archive for category Web maps and Storyboards

Blog Summary – Sami

  • This blog has been categorised according to the mark scheme.

The table below shows which blogs we believe apply to each different area:

Blog List

Blog Posts

Welcome and project brief

A New Intelligent Way of Managing Events – Sami

Analysis of existing similar tools

Analysis of existing similar tools Part 1 – Why our idea has a unique perspective! – Someah & Sami

Analysis of Existing Tools – Part 2 – Sami

Related academic work

Related Academic Work – Sami

Links to related news items in the tech media

Links to Related News Items in the Tech Media: Events Everywhere – Jokha & Sami

Interviews with users or focus groups

Survey Design – Sami

Using a Qualitative Method to get Feedback on our Social Networking Application Idea – Sami & Someah

Survey Results – Sami

Mockups and Ideas

Application Refined Version 2.0 – Sami

Business Model – Jokha & Sami

Application Refined Version 3.0 – Sami

Data Legal Challenges – Someah, Jokha & Sami

System Flow Diagram – Sami

Branding – Sami

Mockups – Sami

Application Refined Version 4.0 – Sami

Application Refined Version 5.0 – Sami

Scenarios and Personas

Business Events – Sami

Pleasure Events – Sami

Business Use Case Scenarios & UML – Sami

Pleasure Use Case Scenarios & UML – Sami

London & Southampton Scenarios – Someah & Sami

Web maps and Storyboards

Storyboard – Jokha

Storyboard 2 – Jokha

Storyboard 3 – Jokha

Tech demos and code snippets

SPARQL & Pseudo Code Example – Sami

UML diagrams

Business Use Case Scenarios & UML – Sami & Someah

Pleasure Use Case Scenarios & UML – Someah & Sami

Overview of standards and protocols

Standards & Protocols Overview – Jokha & Sami

Link to demo software

Mockups – Sami

Video of software in action

Advertising Video – Sami

Testing data

Open Data Within Our Application – Someah, Jokha & Sami

SPARQL & Pseudo Code Example – Sami

Outcomes of usability evaluation

N/A

Overview of pitch to dragons den panel

Overview of Dragons Den Pitch – Sami

 

, , , , , , , , , , , , , ,

No Comments

Storyboard 2 – Jokha

This storyboard illustrates how you don’t need to create an account with Koh.Tu.Me in order to receive event invitations.

Storyboard2-1

Storyboard2-2

Storyboard2-3

Created using: StoryBoardThat.com.

, , , , , , ,

No Comments

StoryBoard – Jokha

This storyboard depicts a scenario of someone using our social networking app.

1 2 3 4 56

, , , , , , ,

No Comments

Business Use Case Scenarios & UML – Sami

This blog post will detail the Use Case Scenarios and UML diagrams for pleasure events.
NB: If you click on the images then they will direct you to a bigger version of that image. 

Conferences
This is the Use Case Scenario and matching UML diagram for a Conference: 

Use Case Scenario

Use Case Section

Comment

Use Case Name

Organise Conference Event

Primary Actor

Conference Attendee

Stakeholders

Conference Attendee wants to get to the Conference.

Conference Organiser wants the attendee’s to get to the Conference.

Preconditions

The Conference must exist and the attendee must know where/when it is.

Success Guarantee

 

Main Success Scenario

 

 

 

 

 

 

 

 

 

Extensions (Other Scenarios of Success or Failure)

The Conference Attendee arrives at the correct Conference at the correct time.

  1. The Conference Attendee wants to / has been invited to attend a Conference.

  2. They know that others of their friends will either be going or might want to go.

  3. They create an event on our social network and invite the relevant people.

  4. A group of people agree to go from various different locations.

  5. They put their travel preferences into the event reply and our travel algorithm organises suggestions for group flights and sharing of a taxi to the conference location. It also suggests how multiple groups of people can share travel to the airport.

Extensions:

  1. The Conference Attendee wants to plan events for his/her guest

  2. The app offers them suggestions of activities plus uses the weather forecast to predict inside/outside activities

 UML Diagram

Screenshot 2014-04-09 15.49.23

 

Business Day Event
This is the Use Case Scenario and matching UML diagram for a Business Day Event:

Use Case Scenario

Use Case Name

Organise Business Day Event

Primary Actor

Business Event Attendee

Stakeholders

Business Event Attendee wants to get to the business event on time.

Business Event Organiser wants the attendees to get to the business event on time.

Preconditions

The Business Event must exist and the attendee must know where/when it is.

Success Guarantee

 

Main Success Scenario

 

 

 

 

 

 

 

 

 

 

Extensions (Other Scenarios of Success or Failure)

The Business Event Attendee arrives at the correct event place at the correct time.

  1. The Business Event Attendee has been invited to attend the event on our social network.

  2. They know that others of their Business friends will either be going or might want to go, although they are new to the business and therefore are unsure of where their colleagues live.

  3. A group of people agree to go from various different locations.

  4. The Business Event Attendee puts in “walking” as their travel preference as they live near the event location.

  5. Our travel algorithm suggests that our Business Event Attendee walks with 3 of their other colleagues that all live in the near vicinity.

Extensions:

  1. The Business Event Attendee wants to know whether or not to walk based on the weather. Our application tells them that there will not be rain at the time they would walk to the event.
  2. Our application however tells the Business Event Attendee that there will be rain by the time they head home, therefore they are able to share a taxi with the people they walked to the event with.

UML Diagram

BusinessEvent

Academic Event
This is the Use Case Scenario and matching UML diagram for an Academic Event:

Use Case Scenario

Use Case Name

Organise Academic Event

Primary Actor

Academic Event Attendees

Stakeholders

Academic Event Attendees want to get to the event location.

Academic Event Organiser wants the attendees to get to the event location.

Preconditions

The event must exist and the attendees must know where/when it is.

Success Guarantee

 

Main Success Scenario

The Attendee arrives at the correct place at the correct time.

  1. An entire Web Science cohort has been invited to an Academic event.

  2. The event occurs after a lecture so everyone will be leaving from Campus and they want to find out the cheapest way for them all to get there together.

  3. Our application provides suggestions for cheap coach offers and group train travel.

  4. The cohort select train travel and our application suggests the best options for combined bus and train travel, taking information from the data.southampton.ac.uk site for bus times and locations.


UML Diagram
Screenshot 2014-04-09 16.00.42

, , , , , ,

No Comments