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
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.
1. Main Page
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)
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)
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.
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
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