King Saud UniversityCollege of Computer and Information Sciences

Information Technology Department

IT322Software Engineering I

academic advising systemSoftware Requirements Specification

phase #2Prepared by

Group#: 2 Grade:Group Email/Wiki: http://it322g2.wordpress.com/Group members:Ashjan alsabhan, 429202584 LeaderAfnan alrwaiys, 429202052 Analysis 1Aljoharah alshagri, 429202605 Analysis 2Nesreen al-hodaithy, 429202022 Analysis 3Abrar assery, 429203591 Analysis 4Somaiah al mutlaq 429202625 Analysis 5

Supervised by T. Hanan

First semester 1332 H Spring 2011

Revision Table

Page# Section# Reviewer Corrected by (Reviewer, Author)

4 1 Leader(ashjan) Leader , analysis 5 (sumaih)5 2 Analysis 3(nsreen) Analysis3 ,analysis4 (abrar)6 3 Analysis2(aljoharh) Analysis3, analysis 4(abrar)7 4.1 Analysis1 (afnan) Analysis1, analysis3 (aljoharh)9 4.2 Analysis 4(abrar) Analysis4, Leader(ashjan)

4.3 Analysis 5(sumaih) Analysis5,analysis1 + analysis3 (Afnan + nsreen)

2

TABLE OF CONTENTS

1. Introduction..........................................................................................................................................4

2. Scope.....................................................................................................................................................5

3. User Characteristics..............................................................................................................................6

4. Requirements Determination................................................................................................................7

4.1. literature review...........................................................................................................................7

4.2. Interview......................................................................................................................................9

4.3. Questionnaire.............................................................................................................................14

5. Specific Requirements...........................................................................................................................0

5.1. User Requirements.......................................................................................................................0

5.2. System Requirements...................................................................................................................0

5.3. Non Functional Requirements......................................................................................................0

6. Use Cases..............................................................................................................................................0

7. System Models......................................................................................................................................0

7.1. Use Case Diagram.........................................................................................................................0

7.2. Sequential Diagrams.....................................................................................................................0

7.3. Conceptual Diagram.....................................................................................................................0

7.4. Contracts......................................................................................................................................0

7.5. Collaboration Diagram..................................................................................................................0

7.6. Class Diagram...............................................................................................................................0

8. References..........................................................................................................................................16

Appendices..................................................................................................................................................17

Software Requirements Specification SRS

1. INTRODUCTION

This SRS have been written for creation of Academic Advising System that will help managing the advising online in order to facilitate and fast the communication between the advisors and student .

The Academic Advising is a staple support of the student march through campus life, student tantamount to provide information and guidance and assist in the preparation and registration of Subjects courses best suited to them are all factors that help to cope with university study and its requirements.

Therefore Depend King Saud University on the experiences of members of the faculty to guide students in academic matters such as selection of track, and provide students with suggestions and tips to improve their education, and assist them in overcoming their problems, and take advantage of the expertise available in the university

.The purpose of this document is to present a detailed description of the Academic Advising System .

It describes the system's features and functions, along with what constraints it must function under. This document's targeted readers are the stakeholders and the system developers and will be proposed to the administration of King Saud University for its approval.

Our SRS document also contain the scope which it specify what the system can allow and what not

user characteristics that describes the general characteristics of the intended users their educational level, experience, and technical expertise

Requirements Determination it provides how the team collect the requirements for the system .first of all the Literature review was done, then there was the interview and the last thing is the questioner

Page 4

Software Requirements Specification SRS

2.

SCOPE

academic advising system is a web based system for managing students study schedules each semester, ensure they strictly follow their approved plans of study and pay special attention to those who face difficulty in following their plans of study

in this system the student cann't add or drop or change their courses sections by themself ,

he just will send request (add/drop form) to his advisor when he cann't add or drop or

change their courses from eduGate .

the advisor can help student to change him/her schedules (drop , add courses , changing

groups ) in first week in beginning of each semester ONLY, after this period the advisor

will help students in any problems they may have except registration courses. Only course

withdrawals are allowed. Course withdrawals are done until five weeks before the final

examination period . also the advisor can help students in tracks registration . also the

advisor can access the student's academic record , study plan and advising visits record ,

give an advice to help the student and facilities a registration to those who faced some

trouble.

Page 5

Software Requirements Specification SRS

3. USER CHARACTERISTICS

our system can be used by faculty advisors , students and registrar at king saud

university . the advisor most have PHD OR MASTER'S DEGREE and they should be

teaching on their faculty and have view about the study plan and the courses . The

student studied to have BACHELOR DEGREE OR PHD OR MASTER'S DEGREE. The

registrar most be on department of faculty and have management and organization

skills. They all most know how to deal with web-based systems and have different

skills and interests in many FIELDS but they should be know English language.

the motivation of system is make communicate between the faculty advisors ,

students and registrar at king Saud university online as fast and as easy as possible .

We support Arabic/ English interface to help people with different languages dealing

with our system with simple and easy tools to helping people who beginners in use

computer.

Page 6

Software Requirements Specification SRS

4. REQUIREMENTS DETERMINATION

4.1. LITERATURE REVIEW

Shaw university

RICE university

PlattsburghUniversity of California

International university of Thailand

functionNo.

√√The Student can change his advisor

1

√√√√Exam conflicts2

√√√√√The student and advisor can Register to system

3

√√Display dates and deadline for all requests

4

√Searching based on student ID

5

√√√Show student's academic action to advisor

6

√√Modify profile account on system

7

√√√√√Help8

Page 7

Software Requirements Specification SRS

√√√√√View details of course registered

9

√√√√√search10

√√Backup Database

11

√√Communicate with other via system

12

√√√√√View details of course registered

13

Summary:

The comparison of the systems shows some common features between them.

The most common feature was that they all provide search by keywords , help ,communication and view detail of registered course.

There are also some helpful features although it is not that common, such as providing exam confects request when student have two exam in same day and time he can send request online via system.

Page 8

Table 1

Software Requirements Specification SRS

4.2. INTERVIEW

Interview time: Saturday 8/10/2011 , 12:00 pm -1:00 pm

Location: KSU – Building 20 - First floor – room 37

Interviewer: Students (as teams) of Software Engineering I course in KSU.

Interviewee: T.Rana almarshd

Page 9

Software Requirements Specification SRS

4.2.1 INTERVIEW QUESTIONS

1-on what based the student are distributed to the advisor ? ..

based on the sequence of the id number and its distributed by the secretary department

2-who can use the system ?

student , advisor , registers

3-if students wants to change her group to a big group how can the system do it?

if there is an alternative student they write it as comment in the form and the advisor do it

4-how the student can enter the system?

entered by her id

5-what is the communication between the student and the advisor ??

private mailing

6-Is the student academic page record and plane are open to the advisor?

yes

Page 10

Software Requirements Specification SRS

7-what should the system provide??

it should provide the privacy between the student and the advisor

8-how the student know that her requests are rejected ??

the register write the comment why her requests are rejected and send it to the advisor then from the advisor to the student

9-is the requests have a dead line ??

yes, also the forms did not shown to the student if she want to write a request after the dead line

10-who create the account to the students??

the secretary department

11-can the student change her advisor?

no , the advisor might be change only under special circumstance and the new advisor is assigned by the department

12-if two student send a request at the same time to register to a specific section and this section has only one chair left who can get this chair??

there is a priority on the date request

Page 11

Software Requirements Specification SRS

13-can the student cancel her request ?

yes, but before her request is implement.

14-how can the advisor know that she get a new request?

by showing a new alert in the student name.

15-are the students records is deleted after they graduate from the system?

the secretary will delete her account after her graduate

Page 12

Software Requirements Specification SRS

Summary:

After we met with T. Rana and discussed some questions that asked by our team and other teams about the system, we came out the following findings

1- all students account will be create by the secretary department.

2- the system interface will be English but the text box can support other languages.

3- the system should be available not just the registration week but all the semester

4-the advisor system should has a visiting record for the student .

5- the system has a private mailing between the student and her advisor .

Page 13

Software Requirements Specification SRS

4.3. QUESTIONNAIRE

Sample:

Our sample is the 6 people who are academic advisors at the college of computer and information sciences in KSU University we sent to their an emails contain our questionnaire form and we get the following result :

Question Yes No

1- Do you think the advising system will take you less time to advise students ? 100% 0%

2- Does the student account is deleted immediately after graduating ? 33.34% 66.66%

3- Is the implementation of priority requests is to who sent first ? 66.66% 33.34%

4- can the user know if the request arrived to the adviser ? 100% 0%

5- Do you believe the system as it is will reduce the traffic of students seeking academic advising to your office?

100% 0%

6- Will you use the system in the future ? 83.33% 16.67%

7- can the adviser delete students files when they graduate ? 33.34% 66.66%

8- Can the adviser delete a request after implementation ? 66.66% 33.34%

9- Will you recommend students using the site in the future ? 100% 0%

10- Is the advisers restricted to a particular period when they entered the system ?

0% 100%

11- can the student change her adviser ? 32.96% 67.04%

12- is the Graphical Design important for the site ? 66.66% 33.34%

13- Do you think the system will be needs future improvements ? 100% 0%

14- Does the adviser have a certain number of students ? 100% 0%

Page 14

Software Requirements Specification SRS

15- Is there someone who can be monitored at the expense of the adviser ? 100% 0%

16- can the adviser controls the student account ? 16.67% 83.33%

17- When a student sends a request for an adviser period prior to completion and the adviser had not seen the application only after you are finished. Can the execution of the request ?

66.66% 33.34%

Summary of the outcomes:

The advising system will take less time to advise students The system will reduce the traffic of students on advisers' office Student account does not delete immediately after the graduation The adviser can delete a request after implementation The students files will still in website after graduation for a period of time Each adviser have a certain number of students the priority of implement the requests is to who sent first

Page 15

Software Requirements Specification SRS

5. REFERENCES

HTTP://ADVISING.AU.EDU/STUDEFAULT.ASP

HTTPS://SAAS.UCR.EDU/SAAS/FSM_MAIN.WELCOME_PAGE

HTTPS://LUMINIS.CC.PLATTSBURGH.EDU/CP/HOME/DISPLAYLOGIN

HTTP://REGISTRAR.RICE.EDU/STUDENTS/REGISTRATION /

HTTP://WWW.SHAWUNIVERSITY.EDU/STUDENTS/ACADEMIC_ADVISING.ASPX

Page 16

Software Requirements Specification SRS

APPENDICES

Page 17