Professional Documents
Culture Documents
Asset Managment
Asset Managment
Certificate of Undertaking I
Certificate of Institute II
Acknowledgment IV
7. Design 48-80
7.1 Front-End Screenshots
7.2 Back-End Screenshots
9. Limitations 93-94
INTRODUCTION OF
PROJECT
1. INTRODUCTION OF PROJECT
Surat Municipal Corporation is the local civic body responsible for the administration
of Surat, to make Surat a dynamic, vibrant, beautiful, self-reliant and sustainable city
offices and zones all over the Surat district, it consists of various technical assets like
Personal Computers, Laptops, CPUs, Keyboard, Data Servers, Printers, CCTV, etc
and many such kinds of devices, used daily to maintain the smooth functionality of
the organization.
While using technical devices at such a large scale, there is a constant need for
updating, repair and adding new devices into the stock and maintain a proper record
of all the assets and their detailed information about their purchase, warranty, usage
history, and repair history and there is a paramount requirement for an Asset
Management System.
Brief point-wise explanation of the main features of the Asset Management system:
● View, Add, Update, and Delete a Employee(s) who are affiliated with the
● View, Add, Update, and Delete a Vendor(s) through which devices are
purchased.
● View, Add, Update, and Delete a Department(s) where the devices and
● View, and request the repair requests for the devices by employee(s).
REQUIREMENT
SPECIFICATION
BUSINESS
REQUIREMENT
SPECIFICATION
Surat Municipal Corporation is local self-government which has come into being
under the Bombay Provincial Municipal Act, 1949. It carries out all the obligatory
Surat became one of the first municipalities of India in 1852 and was converted into a
municipal corporation in 1966 under the Bombay Provincial Municipal (BPMC) Act,
1949.
Surat Municipal Corporation (SMC) perceives its role as the principal facilitator and
provides services to provide a better quality of life for the city of Surat. SMC has
leadership and strong support from citizens, SMC has been instrumental in the
transformation of the city and its growth. It serves an estimated 5.5 million citizens
governance.
In this rapidly growing and changing world the demand for an updated living keep
increasing, there exist a huge need for technical development. SMC understand this
better than anyone. that’s why our standards have always kept pace with changing
The friendly atmosphere between the staff and students of SMC is a striking feature of
the department and their involvement in the new activity is also noteworthy.
● Modern infrastructure
● Latest technologies
SYSTEM
REQUIREMENT
SPECIFICATION
Existing System
● Books are maintained for the request report log which makes it messy
● Technician solves the request and note the request status in books/registers
manually.
● Dispatch manager checks the books and replies the solved request.
● Inquiry person gives the current status information of request from the books.
Proposed System
● All the records of devices and employees are now recorded online
● Admin can now maintain the log of the departments and also of the vendors
The objective of this application is maintain and keep a record of all the devices owned by
the Surat Municipal Corporation, maintain their purchase history, where and who uses the
devices, there are multiple devices such as printer, monitor, CPU, etc. and to maintain the
directory for each device’s repair and updation history and which request were put up, what
● Maintain all Asset details which are owned by the Surat Municipal Corporation
The main objective of this web application is that it deals with various levels of complaint’s
department of technician to handle the issues or query, and will account for the time used in
The web application involved in giving the user and the management the clear picture of the
usage of progress report or activeness of the complaint’s resolution by estimating the effort of
the progress.
FEASIBILITY STUDY
4. FEASIBILITY STUDY
For the scrutiny of the project, we gathered information from the users or management and
collected the requirements and got the information about various types of devices or
resources that they use, and issues regarding complain processing and getting aids from
technicians or management.
The main objective of this study is to determine whether the proposed system is feasible or
not. Solution strategies are usually generated without regard for feasibility because one
cannot be both creative and critical at the same time. Hence feasibility analysis is a must to
arrive at the most appropriate solution strategy. This feasibility analysis is done after a
The planning objective is achieved through a process of information discovery that leads to
Keeping the following aspects in mind, the system analysis for the development of the project
is done.
● Create a system definition that performs the foundation for the subsequent work.
Economical Feasibility:
The system being developed is economic with respect to a municipal point of view. It is
cost-effective in the sense that eliminates the in-process paper usage or effort and time
effective because the user can access it from anywhere or from its respective department.
Technical Feasibility:
The technical requirement for the system is economic and it does not use any other additional
Behavioral Feasibility:
The system working is quite easy to use and learn due to its simple but attractive interface.
Operational Feasibility:
The system is operationally feasible, it is made so easy that users will not encounter any
It is observed that the proposed system would provide a very interactive means to share
information or to communicate and have a far and wide range. The proposed system would
make the information more interactive and functionality is useful as per requirement.
SYSTEM DESIGN
FLOW CHART
Admin
Explanation:
● The flow starts with login, where admin has to input login details to access
admin panel.
Admin Panel
Device tab
● Admin selects the Device to create a device or view details in the database or
system.
Employee tab
● Admin selects the Employee to create employee or view details in the database
or system.
Department tab
or system.
User tab
● Admin selects the Request report to view Request or details in the system.
● Can select the Request report to complete request (existing) from database or
system.
Vendor tab
● Admin selects the Vendor to create vendor or details in the database or system.
Employee:
Explanation:
● The flow starts with login, where the employee has to input login details to
Employee Panel
● Employee selects the Request report to view registered complaint and views the
status.
● Can select the Complaint to add or register complaint details by filling the
complaint form.
User
Explanation:
● The flow starts with login, where IT technician has to input login details to
User Dashboard
details.
Context Level:
Admin Level 1:
Identified Process of :
ADMIN
1.0 Login
2.0 Device
3.0 User
4.0 Department
5.0 Employee
6.0 Vendor
Admin Level 2:
Admin Level 2:
Admin Level 2:
Admin Level 2:
Sub Process of: Sub Process of: Sub Process of: Sub Process of:
1.0 2.0 3.0 4.0
1.1 Change 2.1 Create Device 3.1 Create User 4.1 Create
Password Department
1.2 Login 2.2 View Device 3.2 View User 4.2 View
Department
Admin Level 3:
Admin Level 3:
Admin Level 3:
Admin Level 3:
2.2.3 Details
2.2.4 Request
History
7.2.3 Complete
Admin Level 4:
Main Process :
7.2.3 Complete
User Level 1:
Identified Process of :
USER
1.0 Login
User Level 2:
User Level 3:
Main Process :
2.2 View Request
2.2.2 Comment
2.2.3 Complete
User Level 4:
Main Process :
2.2.3 Complete
Employee Level 1:
Identified Process of :
Employee
1.0 Login
Employee Level 2:
Employee Level 2:
2.3 View
Employee Level 3:
Main Process :
2.3 View
2.3.3 Comment
ENTITY RELATIONSHIP
DIAGRAM
DATABASE DESIGN
6. DATABASE DESIGN
DB: DeviceLog
Column Name Data type Key
LogId int Primary key
DeviceId Int Foreign key
Description Varchar(500)
EntryDate datetime
EntryBy Varchar(200) Foreign key
DB: RequestLog
DB: DeviceMaster
DB: Department
DB: UserMaster
DB: Request
DESIGN
FRONT-END
SCREENSHOTS
Description – This is the Login page of the system, where we have to log in with our
valid credentials so that we can further operate with our system.
Description – Logging in with the credentials given to us i.e. with the given username
and password. Here logging in with the admin as username and it’s password.
Description – The homepage of the admin with the navigation bar to assist you further
with the system.
Description – Giving us the option to select between the Vendor, Device, Department,
the User(Technician) and the Employee.
Description – Also provided with the option to change the password for the admin if
he/she wishes to change it. And the log out button to log out from the current system
page.
Description – The age through which you can change your password if needed by filling
up these fields.
Description – Enter the username and your current password and then you enter your
new password.
Description – By clicking on the change button a pop-up shows about the confirmation
of your changes.
Description – These are the fields that are required to be filled to add up a new device.
Description – Filling up the fields with their respective requirements needed and the
required information.
Description – This is the detailed information about the particular device added by the
admin.
Description – You can search any device by a little information given about the device.
Description – This shows the Report about the devices and the issues related to them.
Description – You can also delete a particular device if it is not in need or has been
removed for the organization.
Description – There a page about the detailed report of all the devices and also the
names of the employee that as using that particular device.
Description – This shows that the particular zone office contains this number of devices.
Description – You can also search the departments to know what and which device that
departments is having with them for their employees.
Description – You can also add a new department and select the number of devices that
are in use in that department.
Description – You can also edit the department if details are entered incorrectly.
Description – User Master report gives you the details about the number of users that
are working and are working for which department with its location.
Description – You can add a new user by filling up the required fields.
B.Sc IT Semester VI Project Report
AURO UNIVERSITY, SURAT 59
Description – Giving you the Dropdown menu to select with the existing zone offices.
Description – By filling up the fields you can create a new user and also edit the details
about the user
Description – Selecting with the Dropdown for devices or for multiple device options.
Description – Employee master report shows all the details of the employees working
with us and which device or devices that the employee holds.
Description – Easy search style to search for the user to find out the details and to know
which device that is employee using.
Description – You can delete the user easily if that user is not needed anymore.
Description – You can also delete the employee if he/she has left the job.
Description – Getting a piece of detailed information about all the request that has been
given by the employees and which requests are completed or that are pending.
Description – Providing the facility to change the password for the user.
Description – Pop-up showing that the changes are confirmed and your password has
been successfully changed.
Description – Login page for the Employee to login with the respected username and
provided password.
Description – Also providing the facility to change the password for the employee.
Description – Detailed report shows that your request has been successfully solved and
is completed duly.
Description – You can add a request by entering the required fields and giving enough
information about the error.
Description – Giving you a dropdown to select within the particular devices assigned to
you.
Description – After a new report if generated it shows pending until it is solved by the
IT Support.
Description – You can also edit the request by selecting proper details.
Description – By entering the full and proper details about the updated request you can
update the same existing request.
Description –The report log shows the details about all the reports requested by the
particular employee.
Description – In the request, you can also add up the extra comments about that
request.
Description – the user after completing the request clicks on the complete button to
show the status to the employee.
Description – User can see the extra comments and can also add his comments and can
also view the details entered by the employee.
Description – The request log shows all the details of the requested reports by the
employees with time and date for more clear understanding.
Description – completing all the request the user can update accordingly.
Description – User can view all the details about the completed and the pending reports
by viewing through it.
Description – The vendor master report shows the name and the location of the vendor
and also the entry date and time.
Description – You can add the vendor as you buy the devices from them.
Description – Filling the details with name and location to locate easily.
Description – Detailed vendor master report shows the name, time and the date about
the vendor.
Description – Device report now shows the serial number of the device and all the other
details.
Description – Device detail shows the vendor name and the warranty period of that
particular device.
BACK-END
SCREENSHOTS
SOFTWARE TESTING
8. SOFTWARE TESTING
Unit Testing
Description: Admin, Employee, and User should able to login successfully and access
Requirement: Admin, Employee, and User must have a valid username and password
Steps:
1) Navigate to AMS.
Expected Results: If the credentials are correct then the user will be redirected to their
user, employee, vendor within AMS to make sure the pages loaded and were not
Integration Testing
Tests: Login Module – Authenticates Admin, Employee, and User from a common
Requirement: Admin, Employee, and User must have a valid username and password
Steps:
1) Navigate to AMS.
Expected Results: If the credentials match to that of Admin, they are redirected to the
Admin Dashboard or if the credentials match to that of Employee or User, they are
Department,Employee,User within AMS to make sure the pages loaded as per the
current Dashboard given that some of the functionalities of the Admin are restricted to
the Admin and are not to be accessed by the Employee or User, like, Adding or
Making sure that AMS delivers what it was primarily designed to deliver, that is,
output focused.
Test: Employee and User are being created by Admin, Device records are being
added, edited and retrieved upon request for by Admin. Employee and User logs in
using Admin provided credentials and can only View and request Complaint facility
service. Employee and User cannot make changes to their profile but can change
password.
Description: Admin create new Employee and User Details in the create Employee
and create User section and the Employee and User are added in the database so that
the Employee and User logs in using those credentials created by the Admin. Admin
also creates Device and department under the create device and create department
section respectively and submits it to the database and later accesses that record under
the View Records section from which they can later view, edit or remove a record.
Employee and User use those credentials to log in and can only view and perform
provided facility. Employee and User cannot make changes to their profile but can
change password.
Requirement: Admin uses credentials provided by the developers to login. Admin uses
genuine credentials to create an Employee, User and device. Admin must have the
Steps:
1) Navigate to AMS.
5) Click “Save”.
6) Select “Add” under Employee, user, device, and department on the navigation bar.
8) Click “Submit”.
15) Click “View Records” (only option) under the device tab.
Expected Result: The records must be saved, should update and print viewed upon
selection without any mishap in data storage or retrieval. The Employee and user must
be added and should be able to login using the credentials provided by the Admin to
them in person and should only be able to access restricted functionalities like View
Tests: Creating and deleting an employee, user, device or department entering dummy
Description: Dummy data is to be entered into the system. It should be viewed, edited
and removed upon request by the admin and only viewed by employee and user.
Requirement: Admin, Employee, and user must have a valid username and password
Steps:
1) Navigate to AMS.
5) Select “Employee or user” > “Add Employee or user” > add dummy details.
7) Select “Device or department” > “Add Device or department” > add dummy data.
9) Select “Logout”
Expected Results: If the admin has logged in, he/she can Add, View or Delete an
Employee or user. He/She can Add, Edit, View and Remove all sorts of records. If an
Employee or user has logged in, he/she can View his/her username only as a profile.
He/She can only view and select all sorts of records belonging to their activity.
Load Testing
Verifying whether or not the system has proper response time under heavy load
Tests: Accessing a particular record for viewing and editing and making sure it has the
Description: Dummy data is to be entered into the system. It should be viewed and
edited upon request by the admin and only viewed by the employee and user in
optimum time.
Requirement: Admin, Employee, and user must have a valid username and password
Steps:
1) Navigate to AMS.
Admin
5) Select “Employee or user” > “Add Employee or user” > add dummy details.
6) Select “View Employee or user” > “View Details” and/or “Delete”. 7) Select
“Device or department” > “Add Device or department” > add dummy data.
9) Select “Logout”
Expected Results: In any case of login, Admin or Employee or user, the records must
be viewed in time. Employee or user must have their details loaded in time and any
changes to the record must be reflected in optimum time. Admin should be able to add
new records or edit existing ones without any time lapses during the saving process
and they must be able to view, add and delete Employee or user without any time
lapses as well.
Security Testing
Tests: Login for authentication and authorization. Making sure the data isn’t available
through any back channels. Making sure that the data is available upon request.
Description: Login details are authenticated and authorized only if they are present in
the database. Data is requested randomly and verified that no back channels exist to
Requirement: Admin, Employee, and user must have a valid username and password
Steps:
1) Navigate to AMS.
Admin
5) Select “Employee or user” > “Add Employee or user” > add dummy details.
6) Select “View Employee or user” > “View Details” and/or “Delete”. 7) Select
“Device or department” > “Add Device or department” > add dummy data.
9) Select “Logout”
authorization of their credentials), the records must be viewed in time and printed. The
operator must have their details loaded in time and any changes to the record must be
credentials) should be able to add new records or edit existing ones without any time
lapses during the saving process and they must be able to view, add and delete
LIMITATIONS
9. LIMITATIONS
Every system have some limits in performing the best and functionality accordance to
the requirement, which leaves the system open for future enhancements
● The system may crash on having more than 1000 users spread across the city.
dashboard
● There isn’t no real time tracker of when a request will be solved and who is
ON-GOING CHANGES
AND FUTURE
ENHANCEMENTS
There are some ongoing changes and future enhancements which are expected of
us:
● To add an auto-generated device-id for all the devices added which makes them
easy to identify
CONCLUSION
11. Conclusion
All the objectives that had been charted out in the initial phases were achieved
System Features:
System satisfies all the requirements for which it is developed. System has relevant
security and fully functioning facility. System is fully GUI based. It is easy to operate
and user-friendly. Platform includes the in built communication and report generating
facility.
Working on the project was a good experience. Working together in teams helped us
The concept of peer-reviews helped to rectify the problems as and when they occurred
and also helped us to get some valuable suggestions that were incorporated by us.
Developing the project has helped us to gain some experience on real time
development procedures
LEARNING OUTCOMES
● Working with the cooperation of the team mates or developer and client or
● Everyone taking equal efforts and putting in hard work. Managing the work
● Taking in consideration the convenient time for all the team members, we
manage the time of the team mates and also with other work load.
● There was much diversity faced in the making of the software but all were
● In spite of having difference of opinion and quarrels the output was not affected
BIBLIOGRAPHY
13. Bibliography
https://www.w3schools.com/asp/
https://www.tutorialspoint.com/index.htm
https://www.wikipedia.org/
https://www.c-sharpcorner.com/
https://www.suratsmartcity.com/SuratSmartCity/AreaBasedDevProjects