Non-Functional Requirements Analysis

The system shall maintain high performance and fast loading speeds.

Yes

4

The system shall keep club member data and event details protected.

Yes

5

The system shall have a clear and intuitive layout with easy-to-navigate sections for event management, club details, and communication features.

Yes

3

The system shall be extremely fast and responsive, ensuring optimal performance under all conditions.

Yes

4

The system shall provide a flawless and efficient feedback system to ensure that no user finds it difficult to submit an issue.

Yes

3

The system shall integrate with the university authentication system to ensure secure access.

yes

5

The app should load each page in less than 3 seconds to ensure fast performance.

yes

3

The system shall implement strong security measures to protect student data and prevent unauthorized access.

yes

5

The system must protect faculty data and enforce strict access controls.

yes

5

The system must not share faculty data with third-party services without explicit consent.

yes

5

The system should have an intuitive, easy-to-use interface that keeps the dashboard relevant to faculty needs.

yes

3

The in-app messaging system shall be structured and organized, avoiding inefficiencies from email and other platforms.

yes

3

The system shall integrate with Google Calendar, LinkedIn and email services.

Yes

3

Users shall have control over which integration they want to enable and which data is shared.

Yes

4

The system shall ensure that users have full control over who can see their activities.

Yes

4

The main dashboard shall display upcoming events and ticket statuses using distinct visual cards with icons.

Yes

3