Scribd
Upload
59 views6 pages

Srs - Assignment7

The document outlines requirements for a student enrollment system. It describes the system environment which includes students and an admin actor along with a cooperating database. It defines functional requirements for students to view their course schedule and for admins to enroll students. Specifically, it allows students to search and view their enrolled courses and admins to add, remove, and manage student accounts. Non-functional requirements address system performance, security via Google authentication, and browser compatibility. A logical database diagram shows tables for admins, students, and teachers with relevant data.

Uploaded by

api-498436043
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
59 views6 pages

Srs - Assignment7

The document outlines requirements for a student enrollment system. It describes the system environment which includes students and an admin actor along with a cooperating database. It defines functional requirements for students to view their course schedule and for admins to enroll students. Specifically, it allows students to search and view their enrolled courses and admins to add, remove, and manage student accounts. Non-functional requirements address system performance, security via Google authentication, and browser compatibility. A logical database diagram shows tables for admins, students, and teachers with relevant data.

Uploaded by

api-498436043
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 6

Software Requirements Specification

October 19, 2021

Student Enrollment

Harsandeep Singh

CST438 - Software Engineering


2.0. Overall Description
2.1 System Environment

Figure 1 - System Environment

The Student Enrollment has two active actors and one cooperating system.

The admin can add the student to a course. The student can view their current schedule

and also can make necessary changes to it such as adding new courses or dropping them.

A database is used to store all the information about students and any new changes made

to the student accounts.


2.2 Functional Requirements Specification

This section is used for the use cases for students to perform actions to their

accounts.

2.2.1 Student schedule Use Case

Use case: Course schedule Diagram:

Brief Description
The students should can access their accounts to see the course schedule.

Initial Step-By-Step Description


Before this use case can be initiated, the students should be enrolled in order to access
their accounts.

1. The students should be able to add courses based on a course id.


2. The system should display all the courses via term.
3. The students should be able to select courses.

2.2.2 Admin Use Case


Admin should have authoritative control over the students accounts and perform actions
such as adding, modifying or removing students from the courses.

Use case: Enroll students


Diagram:
Brief Description
The admin has full control over student accounts and he can perform actions such as
enrolling, removing students.

Initial Step-By-Step Description


Before this use case can be initiated, the admin should have administrative level
privileges to perform different actions on student accounts.

1. The admin can look up different courses offered under different terms.
2. The admin can add students with their student id.
3. The admin can remove students from courses.

3.2 Functional Requirements

3.2.1 Student Schedule


Use Case Name Student Schedule
Trigger Students can view their schedule.
Precondition Enrolled course should be displayed with brief information
Basic Path 1. The student chooses how to search the Web site. The
choices are by course id, by class name, and by professor
name.
2. If the search is by professor name, the system creates and
presents an alphabetical list of all courses offered by that
professor in the database.
3. The student can select a course with course id.
4. The system presents the course in the database.
Alternative Paths If the student selects to search by class name, the system
creates and presents a list of the class under different terms
1. The student selects a class by name.The system creates
and presents a list of all articles in that category in the
database. Return to step 2.
In step 1, if the student selects to search by keyword, the
system presents a dialog box to enter the keyword or phrase.
2. The student enters a keyword.

Postcondition The result of enrolled courses shows up on the student's screen.


Exception Paths The student may cancel the search at any time.
3.2.2 Student enrollment
Use Case Name Enroll Students
Trigger The admin can enroll students into courses
Precondition The admin has administrative authority to add, remove
students from different courses.
Basic Path Students are added or removed from courses.
Alternative Paths Students can enroll themselves in the courses
Postcondition Students are added or removed as per other conditions met
Exception Paths The attempt may be abandoned at any time.

3.3 Detailed Non-Functional Requirements

3.3.1 Performance

If students are cleared to enroll into courses, they can add the courses by

themselves or an admin can perform those tasks on behalf of them. Students should be

able to check the previously added or newly added courses on the student dashboard.

3.3.2 Security

The data stored on the database should be accessible securely by adding google

authentication applications where users need to log in via their gmail accounts. This way

students can only access their own accounts and not other students and also make

necessary changes to their own accounts.

3.3.3 Browser versions

Different browsers have different builts and updated versions. As long as the

browsers are not outdated, they should be able to run the website without any issues.
3.4 Logical database diagram

The admin table has admin id, class catalog, class schedule and other dataset that

are needed for an admin to perform administrative tasks such as adding students,

modifying their current schedules or even removing them from courses and updating the

database. The students have student id, class schedule, class description and other

datasets to view and change their current schedules. The teachers can also view the class

schedule and also view other information such as course id, start and end date,

description of the course and other brief information about the course.

You might also like