Final Report

Human Computer Interaction

4/25/2016

SP STUDENT MANAGEMENT SYSTEM

MADE BY:

SHAHZEB PIRZADA (5701)

1

TABLE OF CONTENT

Description PagesPROJECT DESCRIPTION

FUNCTIONAL REQUIREMENTS3

DESIGN PRINCIPLESERGONOMICS

USABILITYLEARNABLITY

4-5

FLEXIBILITY 5-6

ROBUSTNESSGUI OF PROJECT

78

2 | P a g e

Project Description:

A SP Student Management System (SP.SMS) is a software application website for education establishments to manage student data. Also known as Student information management system (SIMS), The SP Student Management System can handle all the details about a Student. The details include University details, Faculty details, Course details, Students Personal details, Academic details, Grade details etc.

Functional Requirements:

Faculty Login Add , Update, Delete , Undo, View Record. View Student Information. View Course details and do particular amendments. Add, Update, and Delete, View Student Absentees. Add, Update, and Delete, View Student Absentees. Add, Update, Delete, View Student Grades, CGPA etc many more.

Student Login Add Courses View, Absentees, Grades, CGPA etc many more.

Design Principles:

1. Ergonomics:

3 | P a g e

Ergonomics principal is implemented on each of the elements of the GUI for example, color theme of the website gives so great feel to the user eyes.

2. Usability:a. Learnability:

The design is so simple and interactive so that user may achieve maximum performance.

i. Predictability:The User can predict before interacting with anything because of the text as well as pictures on all elements. The picture in the search button indicates searching, so if the User see this can predict easily it may be a search button because User already see it many times.

ii. FamiliarityElements in the [SP SMS] GUI are all frequently used in the real world like textboxes, buttons, tabs, tables, label etc.

4 | P a g e

iii. Synthesizability:Where you are now lie the slider button will tell you the page name as well as the page number. You can also see the immediate response by pressing CTRL + 5 to find student details by searching through Student ID.

iv. Generalizability:Each slider image can be seen through slider button.

b. Flexibility:The user may need to access only as directed by the design.

i. Multithreading:At Student Panel, Student may insert, select, view, update and delete data at the same time because as mentioned before all happening in the same page.

ii. Task Migratability:Page will not refresh upon get and post requests but only when the user wishes to see a new page.

iii. Substitutability:User will post numeric and string data both and also see the result in grid view format as well as in the form of chart.

5 | P a g e

iv. Customizability:Yes it can be customized to change template of SP SMS website.

v. Dialog Initiative:When you are going to delete any entry or student information or something else confirmation required from the system weather to perform this action or not.

6 | P a g e

c. Robustness:There is a very less chance that user may enter false data or make slips because on the client side there are validation checks on forms and rows which are to be edited on the UI or the database.

i. Observability:Short information of everything is available as reduce the Observability problem.

ii. Recoverability:There are CRUD operations available for each entity, so if the user may slip or make a mistake, it is reversible, like in the student course registration.

iii. Responsiveness:Full of responsiveness, however pressed left all events are entertained.

iv. Task Confirmance:Yes successfully completing task.

7 | P a g e

GUI OF PROJECT

8 | P a g e