Mar 14

This document, Use Case 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: Amir Sezavar Keshavarz

This is the second version of our use case diagram. In this use case, I add the System and Admin role and made some modifications to use cases.

Use Case Diagram Version 2

SOTON Student Connect Use Case Diagram Version 2

Upon acceptance, a document explaining all the use cases will be provided.

Mar 06

This document, Use Case 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: Amir Sezavar Keshavarz

This is the first version of our use case diagram. For the next phase, we have to add use cases for system and admin actor and make any necessary modifications to this one as well.

SOTON Student Connect Use Case Diagram Version 1

SOTON Student Connect Use Case Diagram Version 1

Upon acceptance, a document explaining all the use cases will be provided.

Mar 02

This document, Project Requirements, 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: Amir Sezavar Keshavarz

Abstract

This document lists all the functional and non-functional requirements of this project. Based on these requirements, we have to design and implement a system to meet user needs.

State of this document

This document is a work in progress.

Requirements

Functional Requirements

Authentication and Authorisation
1.    This application will authenticate user base on a valid university email address. This email must end with soton.ac.uk and must be valid.
Personal Profile
2.    The application must provide opportunity for user to fill his personal information. This personal information could be name, interests, hobbies, and other relevant information.
Field of Study and Enrolled Modules
3.    The application must allow the user to register his field of study.
4.    The application must allow the user to choose his enrolled modules.
5.    The application must show all the students who study the same module to the user.
6.    The application must allow the user to participate in course discussions.
7.    The application must allow the user to create a new post and ask his questions.
Accommodation
8.    The application must allow the user to identify where he lives.
9.    The application must show all the students who live in the hall of residency of the user.
10.    The application must allow the user to rank his halls.
11.    The application must allow the user to review and send comment about his halls.
Events
12.    The application must allow the user to see all the events and be able to search for them.
13.    The application must allow the user to create an event.
14.    The application must allow the user to join an event.
15.    The application must allow the user to invite his friends.
Calendar
16.    The application must allocate one personal calendar to every user.
17.    The application must allow the user to add events to his calendar.
18.    The application must automatically add university event to user’s calendar.
Groups and Communities
19.    The application must show all the groups to user and let him to search.
20.    The application must allow the user to add group or community of his interests.
21.    The application must allow the user to join a group.
22.    The application must allow the user to invite his friends.

Non-Functional Requirements

•    Easy to use
•    Reliable and stable
•    Appropriate for students of university
•    Accurate and up-to-date information
•    Precise recommendation
•    Privacy and ethical consideration
•    Rich but user friendly
•    Easy to maintain and update