Scribd
Upload
5 views2 pages

Midterm Part1

The document outlines the need for a secure university chat tool, UChat, to replace external messaging platforms that pose security risks. Key goals include enhancing communication efficiency and minimizing reliance on external tools, with essential features such as messaging, file sharing, and integration with existing systems. Functional and non-functional requirements are specified, emphasizing user management, cross-platform support, and system reliability.

Uploaded by

kathyleeyh22
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
5 views2 pages

Midterm Part1

The document outlines the need for a secure university chat tool, UChat, to replace external messaging platforms that pose security risks. Key goals include enhancing communication efficiency and minimizing reliance on external tools, with essential features such as messaging, file sharing, and integration with existing systems. Functional and non-functional requirements are specified, emphasizing user management, cross-platform support, and system reliability.

Uploaded by

kathyleeyh22
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/ 2

MSCS 2101 Software Engineering

Yu-Hsin Lee
Software Requirements Elicitation for a University Chat Tool
Current Business Situation
The university administration is concerned about students using external messaging platforms
like WhatsApp, WeChat, and LinkedIn for communication. These platforms pose potential
security and privacy risks and are outside the university’s control. Currently, the university does
not have its own dedicated chat tool for students, faculty, and staff.
Business Goals
1. Provide a secure and private chat platform for communication among students, faculty,
and staff.
2. Enhance communication efficiency between students, faculty, and administration.
3. Minimize the dependency on external platforms for school-related communication.
Wish List
1. A university-branded chat platform called University Chat (UChat).
2. Controlled access and login for students, faculty, and administration.
3. Essential features such as private chat, group chat, and file sharing.
4. Integration with existing university systems, including SSO, LMS, email, and Canvas.
Needs
1. Messaging Features:
• Students, faculty, and staff should be able to send and receive instant messages.
• Support group chat functionality for courses, projects, and clubs.
• Allow file sharing, including assignments, lecture notes, images, and graphs.
2. Notifications and Alerts:
• Provide real-time notifications for new messages and announcements.
• Allow users to customize their notification preferences.
3. User Management:
• The system should integrate with the university’s SSO for login authentication.
• Admin roles should have tiered access, with only staff allowed to manage system
settings.
4. Cross-platform Support:
• Ensure compatibility across different platforms, including mobile and web
applications.
5. Search Function:
• Include a search tool to help users quickly find messages, files, or profiles using
keywords.
6. Scalability and Performance:
• Handle high usage during peak times, such as exams and registration periods.

Functional Requirements
R1 Users can send and receive instant messages.
R2 Admins can create and manage user roles (student, faculty, admin).
R3 The system integrates with the university’s SSO for authentication.
R4 Users can share files within the chat.
R5 Users can search for messages, files, and user profiles.
R6 Users can adjust the notifications according to their preferences.
R7 Users can access and utilize the tool on smartphone and web.

Non-Functional Requirements
R1 The system should smoothly handle over 5,000 users at the same time without delays.
R2 The system should be reliable, working well 99.9% of the time, with a plan to recover
quickly from unexpected issues.
R3 The system should be flexible enough to grow and add more users or features in the future.

You might also like