An Application for Registration of

Courses in a University
ANALYSIS REPORT
Team No:7

Susmitha P 3122235001143
Thirilogsha S S 3122235001147
Yazhini C H 3122235001166

Contents:
1.PROBLEM STATEMENT
2.FUNCTIONAL REQUIREMENTS
3.NON-FUNCTIONAL REQUIREMENTS
4.CONSTRAINTS
5.STRUCTURED ANALYSIS USING DATA FLOW DIAGRAM
6.DATA DICTIONARY
7.OBSERVATIONS WITH RESPECT TO SOCIETY
8.REFERENCES

1.Problem Statements:
To create an application through which,
• The registration of the courses in a university can be done by the
students.
• Admissions are procured by the university for a new semester.

Input:
• Student-id
• Number of courses the student wishes to register
for
• Course Code
• Course Name
 • Name of the Faculty Member
Output:
• Course Code
• Course Name
• Name of the Faculty Member
• Allotment Status(yes/No)
• Waitlist Number if Allotment Status is “No”

2. Functional Requirements:
Functional requirements in programming define what a system or
software application should do. They typically describe the specific
behaviours or functions the system must perform to satisfy user needs or
business objectives. These describes the high-level requirements of the
system, which usually takes input from the user, and then does some
processing, and gives an output which is useful to the user.
REQUIREMENT 1: Registrations of courses
Students(users) should provide basic information such as name,
username, password, email, etc. to login. Display a list of available
courses with details such as course code, title, instructor, and available
seats. Courses can be registered by the students if the provided
information regarding marks and specialities match the requirements of
the course. The allotted courses along with the name of the teacher for
each course should be displayed.
REQUIREMENT 2: Allotment of courses
All the data for course registration are provided, the program reads
through the data and allow registered users to enrol in courses. It checks
for seat availability before enrolling and update the number of available
seats after enrolment. It allows the users to withdraw from courses they
have already enrolled in.

The program follows the below mentioned constraints:

• Each user should register for a minimum of 4 and a maximum of 6
courses per semester.
• Each core course will have 3 sections and each elective course will
have two sections. Every section will have a fixed strength. If the
section fills up, further registration should not be allowed.
 • If a user wants to add or drop any course after initial registration, it
should be allowed only within the first two weeks after the
semester starts.
• A waitlist (10% of the class strength) will be maintained in case the
allotment is not possible in the first round.
• Users from the waitlist can be allotted their choice subsequent to
the processing of drop requests.

3.Non-functional Requirements:

1. Security: The system should ensure secure login mechanisms, data

encryption for sensitive information like student records, and protection
against unauthorized access or tampering.

2. Scalability: The system should be able to handle a large number of

concurrent users during peak registration periods, without significant
degradation in performance.

3. Reliability: The system should have high uptime and reliability to

ensure that students can access the registration system when needed. It
should also have mechanisms in place to handle unexpected errors or
failures gracefully.

4. Usability: The user interface should be intuitive and easy to navigate,

catering to a diverse range of users with varying levels of technical
proficiency. Clear instructions and error messages should be provided
throughout the registration process.

5. Performance: The system should be responsive and efficient, with

minimal latency during course selection and registration processes.
Database queries and transactions should be optimized to minimize
delays.

6. Compatibility: The system should be compatible with various web

browsers and devices to accommodate the preferences of different users.
It should also adhere to accessibility standards to ensure inclusivity for
users with disabilities.
7. Data Integrity: The system should maintain the integrity of student
records, course information, and registration data. This includes ensuring
that updates and modifications to data are accurately recorded and
reflected in the system.

8. Auditability: The system should keep comprehensive logs of all user

activities, including login attempts, course registrations, and changes to
student records. These logs should be accessible for auditing purposes to
maintain accountability and traceability.

9. Performance Monitoring: The system should include monitoring

tools to track key performance metrics such as server load, response
times, and user activity. This data can be used to identify potential
bottlenecks and optimize system performance over time.

10. Maintainability: The system should be designed with modular

components and well-documented code to facilitate future maintenance
and updates. This includes regular backups of data and software version
control to safeguard against data loss and ensure continuity of service.

4.Constraints:

1. Prerequisite Completion:
- A student should only be allowed to register for a particular course if
they have completed all prerequisites for that course. This constraint
ensures that students have the necessary background knowledge to
succeed in the course they are registering for.

2. Multiple Faculty Members:

- Each course can be taught by multiple faculty members. This
constraint allows for flexibility in scheduling courses and ensures that
there are enough instructors available to meet the demand for different
sections of the same course.

3. Fixed Section Strength:

 - Every section of a course will have a fixed capacity. Once a section
reaches its maximum capacity, further registrations should not be
allowed for that section. This constraint ensures that class sizes are
manageable and that students have a conducive learning environment.

4. Waitlist Maintenance:
- A waitlist will be maintained in case the initial course allotment is not
possible due to sections reaching their maximum capacity. The waitlist
will accommodate 10% of the class strength for each course. This
constraint ensures that students have an opportunity to enroll in courses
even if they are initially full.

5. Add/Drop Window:
- Students are only allowed to add or drop courses within the first two
weeks after the semester starts. This constraint provides a defined period
for students to make adjustments to their course schedules while
minimizing disruptions to the learning process.

6. Waitlist Processing:
- Students from the waitlist can be allotted their preferred courses after
the initial registration period, following the processing of drop requests.
This constraint ensures fairness in course allocation and allows students
on the waitlist to have a chance to enroll in their desired courses if spots
become available due to other students dropping out.

5. Structured Analysis Using Data Flow Diagram

DESCRIPTION:
The user can be either a student, or an administration
accessing this application. Firstly, the user logins, open the course
application and fills out the form with the required details, represented
by the arrows going from the user to the form. Later, after all the users
have filled their forms, the administration processes the information
given by the user and user will get in return a allotment status of the
applied courses.
LEVEL 1:
DESCRIPTION:
In the level 1 allow the user to login/sign up.In 0.2 display the
available courses along with the faculty names and allow them to select
their comfortable courses.In 0.3 ask the user to submit the proof for the
selected courses.After this display the alloted and waitlisted courses.
LEVEL 2:

DESCRIPTION:
In the level 2 display the core courses and elective courses along
with faculty names.In 0.31 ask the user to select minimum 4 and
maximum 5 courses from the core courses and 1 from elective
courses.Ask proof from the user for the selected courses and allow them
to move further only if they submit the proofs.Verify the proofs.Expose
the confirmed and waitlisted courses along with their respective faculty
names.In 0.42 send email to the registered users regarding confirmed
and waitlisted courses.

Observations with respect to society in simple terms:

1. Fairness: The system ensures fairness by allowing all students to

register for courses they want, provided they meet prerequisites. This
promotes equal opportunity for learning.

2. Efficiency: By offering a clear list of available courses and faculty

information, the system helps students make informed choices quickly.
This saves time and effort for both students and faculty.

3. Inclusivity: Allowing a waitlist ensures that students who couldn't get

into a course initially still have a chance. This promotes inclusivity and
ensures that no student is left behind.

4. Responsibility: Allowing course changes only within the first two

weeks encourages students to take responsibility for their academic
decisions early on. This promotes accountability and helps in effective
course planning.

5. Support: By providing clear information and assistance throughout

the registration process, the system supports students in navigating their
academic journey smoothly. This fosters a supportive learning
environment within the university.

6. Adaptability: The system's ability to handle multiple faculty

members teaching the same course sections reflects the diverse teaching
styles and expertise within the university. This encourages adaptability
and collaboration among faculty members.

7. Transparency: Displaying allotted courses and waitlist information

openly fosters transparency in the registration process. This builds trust
among students and ensures that the system operates fairly.

Overall, the course registration system not only simplifies the

registration process but also promotes fairness, efficiency, inclusivity,
responsibility, support, adaptability, and transparency within the
university community.