proj322.files.wordpress.com€¦  · web vieweach one of the users will login to the system with...

36
King Saud University College of Computer and Information Sciences Information Technology Department IT322 Software Engineering I SUMMER TRAINING SYSTEM Software Requirements Specification Prepared by Group#: 1 Grade: Group Blog: proj322.wordpress.com Group members: 431200799 ي ب ر ح ل مد ا ح م دور ب431200552 ف ل خ ل له ا دال ب ع صه ح431202349 ي ض ا ض ع ل مد ا ح م دى& ش431200205 ي ب ا ب) ي خ س ل ا ز ي ر لع دا ب ع رة ي ن م

Upload: others

Post on 07-Feb-2021

0 views

Category:

Documents


0 download

TRANSCRIPT

Project Proposal

Software Requirements Specification SRS

King Saud University

College of Computer and Information Sciences

Information Technology Department

IT322Software Engineering I

Summer training system

Software Requirements Specification

Prepared by

Group#: 1

Grade:

Group Blog: proj322.wordpress.com

Group members:

431200799

بدور محمد الحربي

431200552

حصة عبدالله الخلف

431202349

شدى محمد العضاضي

431200205

منيرة عبدالعزيز السحيباني

431201383

منيرة محمد العوض

Project Proposal

Page 2

Supervised by: Nada Al-Harbi

First Semester, 1433

Autumn, 2012

Revision Table

Page#

Section#

Reviewer

Corrected by (Reviewer, Author)

بدور محمد الحربي

حصة عبدالله الخلف

شدى محمد العضاضي

منيرة عبدالعزيز السحيباني

منيرة محمد العوض

Table of Contents

Summer training system1

Revision Table2

1.Introduction4

2.Scope4

3.User Characteristics5

4.Requirements Determination5

4.1.Literature review5

4.2.Interview8

4.3.Questionnaire8

5.Specific Requirements9

5.1.Functional Requirements9

5.2.Non Functional Requirements11

6.Use Cases4

7.System Models5

7.1.Use Case Diagram5

References---------------------------------------------------------------------------------------------------------------------------12

Appendices12

Table of figures

Table 17

1. Introduction

This document describes software requirement specification of summer training registration system. An interview and questionnaire help us in writing requirements.

Scope of this document describes the scope of the registration system by specifying what the system will cover. For example, the available companies, the process to accepting in the company, matching KSU’s conditions and the option to withdraw or continue the program. This section also describes what the system will not cover such as the final grade of the training course.

In this document, user characteristics describe the intended audience. In literature review there are three system chosen to discus their functionalities addition to our system. Stack holder from KSU IT department and students from IT section help us filling and answering the interview and the questionnaire.

Specific requirements section provide an overview of the registration system define as a result of the requirements determination.

2. Scope

Our software help managing the summer training processes by using web based system that will connect the beneficiaries in an easy way.

The system shows the companies that the student can register in them and continue the process until she accepted in the company. Also, our software makes sure that the student match the university’s conditions before she join. The software gives the students the option to withdraw from the program or continue.

Finally, the software is suppose to assessment of the daily work of the student (trainee), the registration of attendance and writes notes about student’s work and behavior.

On the other side, the software will not cover some of students needs such as the final grade of this training course.

3. User Characteristics

Our users are girl students from King Saud University. They have a middle degree of technical skills (especially an experience in dealing with the Web).

In addition, supervisor (man/women) is almost from outside KSU, coordinator and administrator (KSU staffs). They should have an accepted degree of technical skills.

4. Requirements Determination4.1. Literature review

· System (1): i3indya™ Technologies

i3indya™ Technologies (A unit of I THREE INFOTECH PVT LTD) with its foundation pillars as Innovation, Information and Intelligence is exploring indefinitely as a Technology service provider and as a Training Organization.

The multi domains in which i3indya™ Technologies operate include the following: - Research & Development- Technical Workshops & Seminars- Training Programs

We focused on "Training program" and its registration process that can benefit us in build our system.

i3indya™ organizes Summer Trainings and Internships on Embedded Systems & Ethical Hacking for the students to get an edge above the others. This is followed by an i3indya™ Certification for Training Completion which is highly acknowledged in the job market.

· System (2): Summer Training Registration and Review System Bilkent University-Faculty of Engineering

In Turkey this system allows students to attend summer training through display company List, statement city where the company is located and the type of application being done in addition to the sector. It also contains another page which displays Announcements for faculty and companies.

Entering the system for students who are allowed to only (according to the conditions precedent) and enter Student/BAIS ID , password.

· System (3): The Crimson Summer training registration system

The Crimson Summer training registration system provides information about the training process and its outcomes for high school students.

The system allows the student to login by three different ways: The Harvard University PIN System, Post. Harvard Login or XID.

It is support three different login type because some PIN-protected applications are available to multiple groups of users and those groups use different types of login IDs.

Hint: the URLs of each three systems are in references.

Functions

Our System

System (1)

System (2)

System (3)

Function 1

The system allow student from different organization (university/schools).

No

Yes

No

Yes

Function 2

The system shows the list of companies before login.

No

No

Yes

No

Function 3

The system allows the student to login in different ways.

No

No

No

Yes

Function 4

The system allows the student to fill her/his information immediately without registration.

No

Yes

No

No

Function 5

The system contacts all the training departments.

Yes

No

Yes

No

Table 1 compare three different systems by our system

By comparing our system with several types of other systems, we conclude that our system is intended for a class of IT students at KSU. While the other systems allow registration for university and school students.

Our system also does not allow viewing the companies available before register to the system but in Bilkent University system allow that.

In addition the login to our system is through KSU ID and password, in other hand the Crimson Summer training registration system allows the student to login by 3 different ways.

One advantage of our system is the access to student information through its connection to the table offered by KSU database, this more security in terms of the validity of the input data. Another advantage of our system that it is consists of a link between training departments.

4.2. Interview

            The interview determined and summarized the user requirement and expectation about the software. This interview gives a comprehensive overview of the system and describes the registration process, the ability of the system, security issue and so on.

            Stack holder want the login process to be exactly like the edu gate, and the system should check the student information from a small table taken from KSU database.

           Also, she clarify the process of registration if the Training position brought by the students. Student shall fill a form and wait for the agreement. Along this time a status message will shown in the system.  After accepting or rejecting an e-mail shall send to inform the student.

            Finally, she mentioned that system shall allow the coordinator to follow up her student and the supervisor to fill the electronic following up form every 

Hint: the interview is attached in appendix A.

4.3. Questionnaire

According to the Questionnaire that answered by IT students, we get some of the user requirements that help us to build the system. First of all, we found that 60% from the students are preferred to submit her enrolment form and the other forms as a soft copy. Also, 60% from the students are preferred to use their KSU Id number and password to login the system.

While 100% from the students prefered to allow them to edit/update their information on the system and prefer that the coordinator upload her schedule in the system, to allows her to choose the suitable time for her final representation.

About viewing the status of the student's registration (e.g. Waiting, accepted, rejected) 80% are prefer to provide this service for them. Also 80% from the students prefer to inform him about the registration result by sending an email.

For the companies, there were 80% from the students like to browse all of companies that they can join and allows the arrangement all of the available companies on them desire.

Also, we put a question for the student who finished the training summer to know which step was the most difficult for her. We found that the most difficult stage that faced them is register in the training summer.

Hint: the questionnaire is attached in appendix B.

5. Specific Requirements

5.1. User Requirements

1. The system shall allow student to register in the registration system.

2. The system should allow student to login in the registration system.

3. The system should allow the student to edit/update her information.

4. The system shall allow the students to compete for an IT position provide by IT department or identify the training location on her own.

5. The system shall allow the student to following up her registration process

6. The system should allow the student to upload her report and presentation at the end of training.

7. The system should allow the student to choose the suitable time to represent her presentation.

8. The system should allow the supervisor to login in the registration system.

9. The system shall allow the coordinator to login in the registration system.

10. The system should allow the administrator to login in the registration system.

5.2. System Requirements

1. The system shall allow student to register in the registration system.

1.1 The system will check if the student is qualified to the training or not (the system will contain an imported table from the university database, in this table there will be the information of the students who they expected to the training (all students who met the preconditions for summer training).

1.2 The system should activate the account for the student.

2. The system should allow student to login in the registration system.

2.1 The student will use KSU ID and password to login.

2.2 The system will check if the ID and password are correct. If not, it should display a message "The ID or password is not correct OR you are not allowed to access the system".

3 The system should allow the student to edit/update her information.

3.1 The system shall allow the student to edit her phone number or her email.

4 The system shall allow the students to compete for an IT position provide by IT department or identify the training location on her own.

4.1 The student shall fill an enrollment form that includes the GPA and ILETS grade or equivalent English qualification.

4.2 If the GPA is greater than 4 and the ILETS grade is greater than 5.5, the system shall display two options (the companies from the IT department and student own companies).

4.3 If the student choose companies that offered by IT department, the system should view a list of all companies provided by IT department.

4.4 The system shall allow student to arrange all companies depending on her wishes.

4.5 The system shall allow student to change the arrangement of the companies list in one week.

4.6 In the case the student choose her own company or she is not qualified IT department companies' conditions, the system should download a form to fill it and sign it from the company.

4.7 The system shall allow the student to upload the form and the training plan (the plan which given by the company).

5 The system shall allow the student to following up her registration process

5.1 Waiting statues shall appear after the student submits choosing company(s). After one week the student will announced the final results.

5.2 If the student accepted in one of her choices, an email should send to inform her all details (company name and the process of answering) and update her statues.

5.3 The system shall allow the student to replay in three days; she will be rejected if she did not replay during this time.

5.4 If the student rejected, an email shall be sent to inform her.

6 The system should allow the student to upload her report and presentation at the end of training.

7 The system should allow the student to choose the suitable time to represent her presentation.

8 The system should allow the supervisor to login in the registration system.

8.1 The supervisor shall login by her/his email and password that provided by the admin.

8.2 The system shall provide an electronic following up form to attendance, assessment and the supervisor's notes about the student weekly.

8.3 In the case the supervisor forgot her/his password; the system shall ask her/him to rewrite her/his email. After that, the system shall insure that the email is in the supervisor table. Then, it shall send the new password to her/his email.

9 The system shall allow the coordinator to login in the registration system.

9.1 The coordinator shall login by the username and password that provided by the admin.

9.2 The system shall display to the coordinator the students’ information and their uploaded documents along with their supervisor’s evaluations.

9.3 The system should allow to the coordinator to upload her schedule to specify available times for presentations.

10 The system should allow the admin to login in the registration system.

10.1 The admin shall login username and password.

10.2 The admin shall be able to send coordinators & supervisors their passwords.

10.3 The admin shall be able to update students list.

10.4 The admin shall be able to post announcement.

10.5 The admin shall be able to assign students to coordinators and supervisors.

10.6 The admin shall be able to receive (and accept or reject) students’ requests to train in a company not provided by IT department.

5.3. Non Functional Requirements

1. The System accommodates 250 students at the same time.

2. The system has high speed "not less than 5GB per second" to process the data.

3. The memory of the system has 500GB to store the data.

4. The system usable and has a simple layout.

5. The system should use version 6.5 and above.

6. Use Case

Use Case Name: login.

Actor(s): Student, Admin, coordinator, and Supervisor.

Purpose: login and interact with the system.

Overview: Each one of the users will login to the system with specific information. The student will login to the system using KSU ID and password while the admin login to the system using username and password. The coordinator will login the system using username and password which provided by the admin, but the supervisor will login using her/his email and password which provided by the admin too.

Type: primary.

Cross Reference: Functions R 2.1,R 8.1,R 9.1, R10.1

System Response

Actor Action

2. The system asked the student to enter her ID KSU and the password.

1. The student wants to login the system.

4. The system checked if the ID KSU and the password are correct or not.

3. The student enters her ID KSU and the password.

5. The system opens the main page for the student to interact with the system.

6. The system asked the admin or the coordinator to enter her username and password.

5. The admin or the coordinator wants to login the system.

8. The system checked if the username and the password are correct or not.

7. The admin or the coordinator enters her username and password.

9. The system opens the home page for the admin and make her access the whole system component, Or the system previews to the coordinator the full information about the students who they coordinated by her.

11. The system asked the supervisor to enter her/his E-mail and the password.

10. The supervisor wants to login the system.

13. The system checked if the E-mail and the password are correct or not.

12. The supervisor enters her/his E-mail and the password to login the system.

14.The system opens the home page and provides an electronic following up form to attendance, assessment and the supervisor's notes about the student weekly to fill in.

Alternative:

Line 4: if the student's ID/password incorrect OR she is not recorded in the table, The system will show a message that benefit the student "The ID or password is not correct OR you are not allowed to access the system".

Line 13: In case the supervisor forgot her/his password, the system asks her/him to rewrite her/his email. After that, the system insures that the email is in the supervisor table. Then, it sends the password to her/his email.

Use Case Name: update.

Actor(s): Student and Admin.

Purpose: edit and update some data in the system.

Overview: The system allow the student and the admin to update the some data, the student can update only her profile information like the phone number and her email. On the other hand the admin can update the students list.

Type: primary.

Cross Reference: functions R3.1, R 10.3

System Response

Actor Action

1. This use case begins when a student wants to update her information like telephone number.

3. The system opens the profile page to the student.

2. The student goes to her profile page.

5. The system allows the student to update her profile.

4. The student clicks the update profile button.

7. The system accepts the changes.

6. The student will change the telephone number.

9. The system saved the updating information.

8. The student clicks save changing.

Use Case Name: Register.

Actor(s): Student.

Purpose: Join in the system.

Overview: Initially if the student wishes to enroll in summer training the system allow student to login in the registration system.

Type: primary.

Cross Reference: Function R5.1.1 ,R5.2.1.1 ,R 5.2.1.1 ,R5.2.1.2

System Response

Actor Action

2. The system check if the student is qualified to the training or not.

1. The student register in the system by enters his information.

3. The activating student account.

Alternative:

Line 1. If student ID wrong not acceptable.

Line 2. If a student is not included in the database not available to register ..

Use Case Name: Apply for summer training.

Actor(s): Student

Purpose: Subscription summer training.

Overview: After the registration process the student is given a choice either to train in companies offered by the university or that he is bringing in other companies. But companies affiliated to the University of certain conditions must be applied to the student to enroll.

Type: primary.

Cross Reference: Function R5.1.4

System Response

Actor Action

2. System displays the form to insert the degree.

1. Student inter the IELTS grade or equivalent English qualification.

3. System show list of companies..

5. The activating student account.

4. The student arranges all companies depending on her wishes.

7. System should download a form to the student to fill it and sign it from the company.

6. In the case the student choose her own company.

Alternative:

Line 2. if the student has GPA less than 4 and not have IELTS grade or equivalent English qualification does not allow him to attend companies from IT department.

Line 4. If you do not bring the approval and sign it from the company is rejected.

Use Case Name: Upload final report.

Actor(s): Student

Overview: Student uploading her/his final report.

Type: primary.

Cross Reference: 6

System Response

Actor Action

2.System will open upload page.

1. The Student at the end of summer training will chose upload final report option.

3. student start uploading her/his report

4.System saves this report.

Use Case Name: Select presentation time.

Actor(s): Student

Purpose:select time for presentation .

Overview: The student must choose the time for submission of the report and representation at the end of training from the schedule make it by coordinator.

Type: primary.

Cross Reference: Function R5.1.6, R5.1.7, R 6, R 7

System Response

Actor Action

1. The system displays the schedule.

3. The system allows the student to upload her report and presentation at the end of training at the chosen time.

2. The student must choose the time for her representation.

Use Case Name: fill out the attendance.

Actor(s): Supervisor.

Purpose: The supervisor follows up the student attendance

Overview: The supervisor fills out an electronic following up form to attendance, assessment and the supervisor's notes about the student.

Type: primary.

Cross Reference: Function R 8.1

System Response

Actor Action

1. The supervisor wants to fill out the attendance of the student.

3. The system uploads an electronic following up form.

2. She/he go to "filling attendance" page.

5. The system then saves the results.

4. The supervisor notes about the student attendance.

Use Case Name: view Students Information.

Actor(s): Coordinator

Overview: Coordinator viewing Students Information.

Type: primary.

Cross Reference: 9.2

System Response

Actor Action

2.System will upload the form for this specific student “form with full information filled by Student”.

1. The Coordinator will chose view Student option on the interface.

3.System makes the form visible on the screen.

Use Case Name: Specify available time for presentation.

Actor(s): Coordinator

Overview: Coordinator choosing an available time for the presentation.

Type: primary.

Cross Reference: 9.3

System Response

Actor Action

2.System will view a calendar for the Coordinator, the unavailable time are marked as invisible only the available time is visible.

1. At the end of summer training Coordinator will select chosen the available time for the presentation.

4. System will save the chosen time.

3. Coordinator will choose available time for the presentation.

Use Case Name: post announcement.

Actor(s): Admin.

Purpose: announce the important events and news.

Overview: The system gives the admin the eligibility to post announcements for the other users" Student, coordinator, and Supervisor." to inform them about the important events and news that interest them.

Type: Secondary.

Cross Reference: R 10.4

System Response

Actor Action

1. The admin wants to post some announcements.

3. The system opens the announcements page for the admin.

2. The admin goes to the announcements page.

5. The system opens form to the admin to write the announcement.

4. The admin clicks the post new announcements button.

7. The system post the announcement and view it to the other users.

6. The admin writes the announcement and click post.

Use Case Name: assign students to the coordinators and the supervisors.

Actor(s): Admin

Purpose: The student will assigned to her coordinator and her supervisor.

Overview: The admin will assign each student for her coordinator and supervisor.

Type: primary.

Cross Reference: Functions R 10.5

System Response

Actor Action

1. The admin can see the information of all students who they have been registered.

3. The system displays a list of: all students with their information, coordinators and companies supervisor.

2. The admin go to “Students List” option

4. The admin then assign each student for her coordinator and supervisor.

Use Case Name: Send coordinators & supervisors passwords.

Actor(s): Admin

Overview: Admin able to send coordinators & supervisors passwords, in the beginning of the training period.

Type: primary.

Cross Reference: Functions R 10.2

System Response

Actor Action

2. System will show to the admin all the coordinators and supervisors available in this training period.

1. The use case begins when the admen chose the “Send coordinators & supervisors passwords.” option from the interface.

4. System will send randomly password(s).

3. Admin ether chose to send a password(s) to specific groups or for all of them.

Use Case Name: Send Receive students’ requests.

Actor(s): Admin

Overview: Admin able to receive and accept or reject students’ requests to train in a company not provided by IT department.

Type: primary.

Cross Reference: Functions R 10.6

System Response

Actor Action

2. System will show to the admin all the students requests.

1. The use case begins when the admen chose the “students’ requests.” option from the interface.

4. System will send an email to the student inform her about the request result, the student status will be updated. If the student didn’t response in the time system assume that she is rejected.

3. Admin can choose any of student requests and view it to accept or reject process.

7. system models

7.1 Use Case Diagram

References

References

· i3indya™ Technologies

http://www.i3indya.com/training/summer-training/training-details-delhi-for-students.html

· Summer Training Registration and Review System Bilkent University-Faculty of Engineering

http://mfstaj.cs.bilkent.edu.tr

· System (3): The Crimson Summer training registration system

http://www.crimsonsummer.harvard.edu/index.html

APPINDECES

Appendix A

Interview:

  The interview was on Sunday 14th of October with Ms. Naela Al-Hasson.

Q1)  how would you like the student to login?

I would the student to login with her KSU ID and password, like the KSU edugate.

Then the system should check if the student is qualified to enter the system or not.

Q2) is the system able to access the KSU database to know the qualified students?

No, system shall not be able to do that, but the admen can improve small table from the KSU database. This small table contains the qualified students.

Q3) what is the constraints and conditions that shall be applied to the student who register in the companies provided by the IT department?

If the student choice to training in a company the IT department provides it, she has to submit her IELTES degree or the equivalent English qualification. After that student can arrange list contains all the company

Q4) what is the constraints and conditions that shall be applied to the student who identifies the training location on her own?

First, the student shall download a form and fill it from her company. After that she uploads it with the training plan to the system,

Then she will wait the IT department to agree.

Q5)  Is there  any process to inform the student about the registration status?

Yes I want the system to show the status of registration process. If the process not finished yet it will be “waiting”, otherwise an email shall send to tell her that you are accepted or rejected

Accepted student can foreword in limit time “3 days” after that we supposed the student is rejected. 

Q6) how to connect the system with the coordinator?

System could allow the coordinator to login and follow up the student. In addition she’ll be able to contact with her student.

Q7) what is the supervisor ability in the system?

Supervisor can login to the system by the email address. Then the system check if this email is valid or not and send to him\her the password.

Supervisor is responsible to fill the electronic following up form every week.

 

Finally, the stakeholder mentioned that in the end of the training period all the students accounts will be in the history and the student can’t login anymore. In the other side the administrator can access to all the system components any time.

·

Appendix B

Link of Questionnaire: http://www.survs.com/survey/AMBJF2Y4GJ

Copy of the Questionnaire:

Page 17