Scribd
Upload
4 views2 pages

Laptop Request Catalog Item Requirements

The document outlines the functional and non-functional requirements for the 'Laptop Request Catalog Item' project, dated November 2, 2025. Functional requirements include catalog item creation, dynamic form behavior, and an approval workflow, while non-functional requirements focus on usability, security, reliability, performance, availability, and scalability. The project aims to ensure a user-friendly interface and efficient processing of laptop requests within the ServiceNow platform.

Uploaded by

bytcraze2k25
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
4 views2 pages

Laptop Request Catalog Item Requirements

The document outlines the functional and non-functional requirements for the 'Laptop Request Catalog Item' project, dated November 2, 2025. Functional requirements include catalog item creation, dynamic form behavior, and an approval workflow, while non-functional requirements focus on usability, security, reliability, performance, availability, and scalability. The project aims to ensure a user-friendly interface and efficient processing of laptop requests within the ServiceNow platform.

Uploaded by

bytcraze2k25
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 02 November 2025
Team ID NM2025TMID00161
Project Name Laptop Request Catalog Item
Maximum Marks 4 Marks

Functional Requirements
Following are the functional requirements of the proposed solution.
FR Functional
Sub Requirement (Story / Sub-Task)
No. Requirement (Epic)
Admin creates a “Laptop Request” item in the Service
FR-1 Catalog Item Creation
Catalog.
Variable Admin adds form fields – Laptop Model, Justification,
FR-2
Configuration Accessories, and Accessories Details.
System applies UI Policies to show “Accessories
Dynamic Form
FR-3 Details” only when “Additional Accessories” is
Behavior
checked.
Allows user to reset the form instantly using a “Reset
FR-4 UI Action
Form” button.
Submitted requests are sent to the IT department for
FR-5 Approval Workflow
approval and fulfillment.
Deployment and All configurations are captured in an Update Set for
FR-6
Version Control exporting to another instance.

Non-Functional Requirements
Following are the non-functional requirements of the proposed solution.
NFR Non-Functional
Description
No. Requirement
The form interface should be user-friendly and easy
NFR-1 Usability
for employees to fill.
Only authorized users can access or modify catalog
NFR-2 Security
items.
The catalog form must load correctly and maintain
NFR-3 Reliability
consistent performance.
Dynamic field visibility (UI Policy) should trigger
NFR-4 Performance
instantly without lag.
The system should be available 24/7 via the
NFR-5 Availability
ServiceNow cloud platform.
The catalog should handle increasing requests and
NFR-6 Scalability
variables without performance issues.

You might also like