0% found this document useful (0 votes)
4 views2 pages

Solution Requirements

The document outlines the solution requirements for the Project Design Phase-II aimed at streamlining ticket assignment for efficient support operations. It details functional requirements such as user registration and confirmation methods, as well as non-functional requirements focusing on usability, security, reliability, performance, availability, and scalability. The project is managed by Team ID SWTID-2026-1718 and is dated January 31, 2026.

Uploaded by

sairam.m.2005.65
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
0% found this document useful (0 votes)
4 views2 pages

Solution Requirements

The document outlines the solution requirements for the Project Design Phase-II aimed at streamlining ticket assignment for efficient support operations. It details functional requirements such as user registration and confirmation methods, as well as non-functional requirements focusing on usability, security, reliability, performance, availability, and scalability. The project is managed by Team ID SWTID-2026-1718 and is dated January 31, 2026.

Uploaded by

sairam.m.2005.65
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

Project Design Phase-II

Solution Requirements (Functional & Non-functional)

Date 31 January 2026

Team ID SWTID-2026-1718

Project Name Streamlining ticket assignment for efficient support


operations

Maximum Marks 4 Marks

Functional Requirements:

Following are the functional requirements of the proposed solution.

FR No. Functional Requirement (Epic) Sub Requirement (Story / Sub-Task)

FR-1 User Registration Registration through Form

Registration through Gmail

Registration through LinkedIN

FR-2 User Confirmation Confirmation via Email

Confirmation via OTP

FR-3

FR-4

Non-functional Requirements:

Following are the non-functional requirements of the proposed solution.

FR No. Non-Functional Requirement Description

NFR-1 Usability

NFR-2 Security

NFR-3 Reliability

NFR-4 Performance

NFR-5 Availability
NFR-6 Scalability

You might also like