Scribd
Upload
6 views2 pages

Course Registration System For ABC College Cost Estimated

Uploaded by

asterbelete021
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
6 views2 pages

Course Registration System For ABC College Cost Estimated

Uploaded by

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

Course Registration System for ABC College key functional and non-functional

requirements:
Functional Requirements:
1. Student Management
Software Requirements:
1. Operating Systems:2936
2. Course Management
2. Database Management System:2936
3. Registration Management
3. Web Application Server:2936
4. User Access and Permissions
4. Development Tools:2936
Non-Functional Requirements:
1. Performance
5. Productivity and Collaboration Tools:
2. Availability and Reliability
2936
6. Monitoring and Security Tools:2936
3. Security
Hardware Requirements:
4. Usability and Accessibility
1. Web Servers:2936
5. Scalability and Extensibility
2. Database Servers:2936
Maintainability and Documentation
3. Network Equipment:2936

4. Storage:2936

5. Client Devices:2936

Total Estimated Cost: birr32,300

Entities:

1. Student
o Attributes: StudentID, Name, Email, Phone
2. Course
o Attributes: CourseID, Title, Department, Credits
3. Registration
o Attributes: RegistrationID, StudentID, CourseID, RegistrationDate
Relationships:

1. Enrolls (between Student and Course)


o Cardinality: Many-to-Many
o Description: A student can enroll in multiple courses, and a course can have
multiple students enrolled.
2. Offers (between Course and Registration)
o Cardinality: One-to-Many
o Description: A course can have multiple registrations, but each registration is
associated with a single course.
3. Manages (between Student and Registration)
o Cardinality: One-to-Many
o Description: A student can have multiple registrations, but each registration is
managed by a single student.

Conceptual Design:

1. Student Entity:
o Stores information about students enrolled at the university, including their
unique StudentID, Name, Email, and Phone.
2. Course Entity:
o Stores information about the courses offered by the university, including the
CourseID, Title, Department, and Credits.
3. Registration Entity:
o Captures the registration of students for specific courses, including the unique
RegistrationID, the associated StudentID and CourseID, and the RegistrationDate.
4. Relationships:
o Enrolls (Many-to-Many): Represents the relationship between students and the
courses they enroll in. A student can enroll in multiple courses, and a course can
have multiple students enrolled.
o Offers (One-to-Many): Represents the relationship between courses and the
registrations associated with them. A course can have multiple registrations, but
each registration is associated with a single course.
o Manages (One-to-Many): Represents the relationship between students and the
registrations they manage. A student can have multiple registrations, but each
registration is managed by a single student.

You might also like