The document describes a proposed system to automate the management of IT equipment and complaint registration processes at a university department. Some key points: - Faculty and lab instructors need a way to submit requests for new equipment and register complaints about issues with existing devices. - The system should track inventory, complaint logs, and resolution reports. It should generate analytical reports and dashboards for administrators. - The document outlines functional requirements like user authentication, equipment management, complaint registration, and decision support reports. It also lists non-functional needs around security, availability, and accessibility. - Students will develop this system as a project to address the current problems with manual processes that cause delays and issues when staff are unavailable

1. U & P U Patel Department of Computer Engineering Technician
Kalpeshbhai and Bhavinbhai facing issues to maintain their Laboratory and
other IT resources of department. Faculty members or Lab Incharge filling
up requisition for New PC, Network cable, Keyboard, Power cable, mouse,
Projector, Speaker or Internet switch, etc. They also calling them randomly
for in trouble or problem in their class room, laboratory or faculty room.
Bhavinbhai/Kalpesh is not available in cabin or phone not reachable or both
of them are on leave some time, because of that many problem and issues are
in hanging state. These creates lot of trouble. To resolve this issue HoD and
IT Cell of CHARUSAT propose one live project to Students as SGP
/Summer internship which can automate process of New Entry of equipment
or devices. Complaint registration by any Lab-Incharge / Faculty members
for respective devices under their ownership. Complaint solution report as
Site Visit report by identifying technical fault, process done to resolve the
issue, cost of replacement of any part of device, time required if not solved
in single visit, etc.
This system should generate Stock maintained report with location and
ownership, Complaint Register log, Complaint Solution log, other Decision
Support Analytics report with Dashboard for HoD and IT Cell.
You have to write and formulate all Functional and Non Functional
Requirements with Use Case Diagram and User Stories (Any 4). Prioritize
requirements using MosCow method.
Functional Requirement
F1 : User Management
Register: The user can register their self-based on their role and they will get login
credentials
 Input: User role, name of user, user id [faculty employee id]
 Output: New user will be added.
Login: The user can login to the system with his/her username and password.
 Input: Username and Password.
 Output: Employee Dashboard, Admin Dashboard
 Processing: Username and password verify from database if user exist in
database then user interface will be displayed according to their role.
User Profile: The user can login to the system with his/her username and password and

2. update the required details.
 Input: Login credentials and updated field [user details]
 Output: Employee Dashboard
 Processing: Username and password verify from database if user exist in
database then user interface will be displayed according to their role.
Logout: The users can logout from system.
 Input: ‘Logout’ option is selected.
 Output: User login Screen will be displayed.
Password reset: Users can reset their password.
 Input: Username/email
 Output: reset password page provided to user
 Processing: if user exist in database then mail will be sent to user through
which users can reset their passwords.
F2: Equipment Management
Faculty members and Lab Incharge should be able to submit requisition requests for
new equipment including PCs, network cables, keyboards, mice, projectors, speakers,
internet switches, etc.
submit requisition requests:
 Input: selection of equipment [ give checkbox choice PCs, network cables,
keyboards, mice, projectors, speakers, internet switches, etc.]
 Output: request sent successfully
 Processing: if user exist in database then mail will be sent to user through which
users can see their prior requested items.
Notification:
 Output: Send notification to Client.
 Processing: When any faculty will generate requisition request notification will be
prompted at lab technician side.
Add/Update equipment’s details:
 Input: Add/update details of equipment, equipment ids, location
 Output: equipment data will be stored.
 Processing: after entering the data into the equipment module The system

3. will maintain an inventory of all equipment including details such as type,
quantity, location, ownership, and availability status.
F3 : Complaint Management
 Add complaint: it will raise a complaint for specific issue.
 Input: emp id, equipment name, issue
 Output: It will display raised complaint at the lab tech’s dashboard as
notification
F4 : Track record of employee Complaints
 Input: Details of all complains which completed , pending and currently
working
 Output: List out all records to lab technicians.
F5 : Decision support
Decision support analytics reports should be available with a dashboard for HoD and
IT Cell to monitor equipment status, complaint resolution times, and other relevant
metrics.
 Input: Login with admin/Hod credentials, check status
 Output: analytics reports will be generated on dashboard of HoD and IT cell.
 Process: after receiving complaints status of resolved complaints will be
updated and based on that logs will be generated and reelected as graph
format.
3.2 Non-Functional Requirement
Accessibility and Availability:
• The system should be accessible via web browsers to ensure ease of use and
availability across different devices.
• The system should be available 24/7 to accommodate complaint registrations and
access to equipment information at any time.
Security:
• The system should implement appropriate security measures to protect sensitive
information including user data, equipment inventory, and complaint details.
• Access to the system should be secured through authentication mechanisms such as
usernames and passwords.

4. Identify the functional and non-functional requirements in the following problem
description and write in standard format. Design Use case diagram and Design
minimum 2 user stories.
A cosmopolitan clock software is to be developed that displays up to 6 clocks with the
names of the city and their local times. The clocks should be aesthetically designed.
The software should allow the user to change name of any city and change the time
readings of any clock by typing (for configure) on any clock. The user should also be
able to toggle between a digital clock and an analog clock display by typing either d
(for digital) or a (for analog) on a clock display. After the stand-alone implementation
works, a web-version should be developed that can be downloaded on a browser as an
applet and run. The clock should use only the idle cycles on the computer it runs.
Functional Requirements:
F1: Display Clocks
Output: The software should display up to 6 clocks simultaneously. Each clock should show the name
of the city it represents along with its local time.
F2: Change City Names
Input: select city
Ouput: based on selected city,clock time will be update.
F3:Change Time Readings
Input: set time details
Output: newly updated time
Processing: The user should be able to manually configure the time displayed on any clock by typing
the desired time.
F4:Toggle Display Mode
Input: select Mode[A for Analog, D for Digital]
Output: Display Clock
Non-Functional Requirements:
 Aesthetic Design:The software should have visually pleasing clock designs to
enhance user experience.
 Efficiency:The software should utilize idle computer cycles efficiently to
minimize resource consumption.
 Usability:The software should be user-friendly and intuitive, allowing users to
easily change city names, time readings, and display modes.
 Performance:The software should update the displayed time accurately and
promptly without significant delay.
 Cross-Platform Compatibility:The web version of the software should be
compatible with major web browsers and operating systems.

5.  Reliability:The software should function reliably without crashing or freezing
during normal usage.
 Security:The software should not compromise the security of the user's device
or personal information.
 Scalability:The software should be scalable to accommodate potential future
enhancements or additional features.