Final answer:
Functional requirements for a course management system detail specific actions it must perform, while non-functional requirements outline how the system carries out these actions. A use case for course registration includes actors (students, instructors, administrators), input and output processes, normal operation flow, and handling of exceptions.
Step-by-step explanation:
Functional and Non-Functional Requirements for a University Course Management System
Functional requirements are specific activities the system must perform to facilitate course management. These might include:
- User authentication and authorization.
- Course registration and enrollment management.
- Assignment submission and grading system.
- Schedule planning and conflict resolution.
- Communication tools for students and instructors.
Non-functional requirements describe how the system performs certain activities and may include:
- System reliability and uptime.
- Data backup and security protocols.
- Response time and system performance criteria.
- Accessibility compliance for users with disabilities.
- Compatibility with multiple devices and browsers.
Use Case Example: Course Registration
Actors: Students, Instructors, Administrators
Inputs: Course selection, student data, prerequisites verification.
Outputs: Confirmation of enrollment, updated course list, payment prompt if necessary.
Normal operation: A student logs in, searches for a course, verifies prerequisites, enrolls, and receives confirmation.
Exception: If a course is full or prerequisites are not met, the system alerts the student and suggests alternatives.