May 26

BASK LOGO

Team BASK LOGO

May 26

By Amir Sezavar Keshavarz

A student would like to ask a question about a topic of one of his modules he is studying in this semester. Easily, he can login into the system and navigate to academic section. In this section, he can register his field of study and all modules he is studying in this semester. Then he can create a module thread for a question. I this module thread, he can ask a question and wait for other students to respond. Other students can find this question by searching or navigating to all available module threads, find this question, and answer it. Students also have the opportunity to add this module to their interests so they get updates whenever there is an activity in that module.

May 26

By Amir Sezavar Keshavarz

Once a person is offered a place to study and he/she accepts that offer, he/she is able to register for university email address and apply for accommodation. However the choice of accommodation is very frustrating as it is going to be his/her accommodation for one-year.

The problem is that there is not enough information about accommodation on the University website making it a little harder to find a suitable accommodation.

In our proposed system, students login and then navigate to accommodation area. They can see all accommodation, reviews of them, rankings of them, and a photo gallery consisting a lot of photos. All of these features have been provided by university students. Furthermore they have the opportunity to talk to students and find more information.

After they have registered for an accommodation, they can register their information into the system, and our proposed system will recommend friends who are actually their flatmate. So, even prior to their arrivals, they have the opportunity to know their flatmates better and get prepared.

May 17

By: Amir Sezavar Keshavarz

1 - LoginPage

1 – LoginPage


2 - Profile Page

2 – Profile Page


3 - Public Profile Page

3 – Public Profile Page


4 - Search Result Page

4 – Search Result Page


5 - Module Thread Page

5 – Module Thread Page


6 - Accommodation Page

6 – Accommodation Page


7 - Accommodation Review Page

7 – Accommodation Review Page


8 - Event Page

8 – Event Page


9 - Group Page

9 – Group Page


10 - Group Specific Page

10 – Group Specific Page


11 - Messages Page

11 – Messages Page


12 - LogoutPage

12 – LogoutPage

Mar 24

This document, Prototype Version 3, is available to download from DropBox. In case of any modification, please update all the versions. You have to update word document, PDF document in DropBox Folder and Also this post.

By Boton Li
Posted By Amir Sezavar Keshavarz

Prototype Idea
Mar 21

This document, Prototype Version 2, is available to download from DropBox. In case of any modification, please update all the versions. You have to update word document, PDF document in DropBox Folder and Also this post.


By Taekyun Kim
Posted By Amir Sezavar Keshavarz

Introduction

This artefact is aimed to discuss different aspects and rationale of the proposed GUI prototype for the SOTON Student Connect application.

There are three part of explanation.

Main page, Personal profile and Accommodation,

Main page is the only we can see before we logged in. and the others are similar page but following which option we choose after log in.

Screen shots

1. Main Page

Main

Main

Features.

From the top, There is a logo but it has not been chosen the placement. Possibly left side or middle side, But not good for right side.

Main menu bar has 6 menu which we discussed before,

Main login page is placed on the left side.  If we are connected with School Database then we do not need join button in Login form otherwise, we will need.

Notice board page is placed on the right side.

This will construct with frameworks so after coding, We just need to modify the middle section

Where Login page and notice page.

2. Personal Profile (After Login Page)

Personal Profile

Personal Profile

Features

As you can read above in main page. Top side is same as before.

After login, You could see personal information on the Left side. You can log out,

Read a message, possibly can see the friends.

The right side is more detail for Personal Profile, Name, Hobbies, Introducing.

The thing is if we are conneced with school database it will come up automatically, and we will modify or add information on our projcect site.

3. Accommodation (After Login Page)

Accommodation

Accommodation

Features

This is another page of menu.

Left side is same as the other page.(of course if we need to modify this page, easily re coding fot only this side)

Right side is information about accommodation.

As you can see, if we choose one of the option of menu then we could see where we are through between menu and main section. This is same as other option of menu.

Strengths

The strengths of the proposed prototype can be listed as follows:

1. Taking advantage of the rich user interface design

2. Easy to use.

3. Easy to coding because of separated page with frameworks

4. quick and instant access to the most important features of the system

Weaknesses

A number of weaknesses can be listed for the offered prototypes as below:

1. Design cannot be changed by user.

2. Administrator should be mange at least a day

Mar 19

This document, Prototype Version 1, is available to download from DropBox. In case of any modification, please update all the versions. You have to update word document, PDF document in DropBox Folder and Also this post.


By Shahin Jahromi
Posted By Amir Sezavar Keshavarz

Introduction

This artefact is aimed to discuss different aspects and rationale of the proposed GUI prototype for the SOTON Student Connect application.

The document will start by including the main screen shots of the prototype along with a full discussion on the rationale for each section and then proceeds to offer the rationale of the design by discussing a number of typical user stories. Finally the strengths and weaknesses of the design will be listed.

Screen shots

1. Home Page

Index

Index

Figure 1

Highlights

Figure 1 depicts the starting page of the system. The design includes a three column paradigm with a banner at the top and a footer to indicate the end of the page. The banner includes the system’s logo, application’s name and the status of the user currently viewing the page. From the status bar user can see whether she has signed in to the system or if the user has not created a account for herself, the system indicates that the current user is viewing the site as a guest and offers her the option to sign up to the system.

The body of the page consists of three columns. The left most column illustrates a picture to graphically indicate the purpose of the system. The middle column offers a textual description of the site highlighting the features and benefits of the system. Finally the right hand side column provides the login facility for users who have already created an account in the system.

The main page follows the traditional page based Web application’s paradigm as it does not include high degrees of interaction and in addition, the conventional types provides more security regarding users sensitive data such as login credential compared to rich technologies for which security remains an unsolved concern.

2. User Home Page

User Main Page

User Main Page

Figure 2

Highlights

Figure 2 depicts a registered user’s home page which acts as a portal giving access to all the features and facilities of the site in a single page. This page is essentially a mix of rich and traditional user interface paradigm in that the main and frequently used features of the application has been included as widgets which update dynamically upon user’s interactions which does not require the page to be refreshed. This way the performance of the system will be highly improved and the interface would be more compact and user friendly.

The top banner remain enact to maintain the consistency of the system. The status bar however will be updated to show the status of the user as logged in and providing a sign out facility.  The footer also still present the indicate the end of the page.

The left hand side navigation bar contain the profile picture of the user along with a list of links to less frequently used features of the system or to pages which should be opened in a new window or as a front layer to the current page.

The main content pane includes a number of widgets which could be managed, closed, minimised or being replaced by other widgets available. Default widgets includes the user’s calender which is one of the most important and most frequently used feature of the system, enrolled modules list which present to the user the full list of the modules she has currently enrolled and contains links to each module’s resources and discussion pages. The notifications and actions widget lists all the recent activities, post, tags, friend’s statuses etc which are relevant to the user. The finder widget offer the facility for the user to search for people, friends, groups, events and activities through the system. The suggestion menu offers friend suggestions which is based on the system’s recommender system. Other widgets which can be included to the system would be accommodation section widget, each of the enrolled groups or activities widget, rss feed of subscribed friends, events or groups widget and so forth.

Please note that these are only the two so called landing pages of the system. If the design is accepted in the prototype review sessions, the prototype will be extended to cover the full details of the system.

Strengths

The strengths of the proposed prototype can be listed as follows:

  1. Taking advantage of the rich user interface design
  2. improved performance
  3. ease of use
  4. ease of navigation through the system
  5. highly customisable user pages
  6. quick and instant access to the most important features of the system
  7. high level of user interaction
  8. clear and intuitive interface design
  9. light weight widget based minimalistic design

Weaknesses

A number of weaknesses can be listed for the offered prototypes as below:

  1. lacks accessibility features
  2. implementation and coding challenges
  3. lack of standardised methodologies for implementation

Prototype to be expanded upon acceptance