Ruchit Final SE PDF

CONTENTS
Sr. No. Contents Page No.
Certificate of Undertaking I
Certificate of Institute II
Certificate of Organization III
Acknowledgment IV
1. Introduction of Project 1-3
2. Requirement Specification 4-10

2.1 Business Requirement Specification
2.2 Software Requirement Specification
3. The objective of the Software 11-12
4. Feasibility Study 13-15
5. System Design with description 16-44

5.1 Flow Chart
5.2 Data Flow Diagram
5.3 Entity-Relationship Diagram
6. Database Design 45-47
7. Design 48-80
7.1 Front-End Screenshots
7.2 Back-End Screenshots
8. Software Testing 81-92
9. Limitations 93-94
10. On-going changes and Future Enhancements 95-96
11. Conclusion 97-98
12. Learning Outcomes 99-100
13. Bibliography 101-102

AURO UNIVERSITY, SURAT 1
INTRODUCTION OF
PROJECT
B.Sc IT Semester VI Project Report

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
with all basic amenities, to provide a better quality of life.
In such a government organization like Surat Municipal Corporation with various
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 Device(s) owned by the organization.
● View, Add, Update, and Delete a User(s) who is IT-Support of a department.
● View, Add, Update, and Delete a Employee(s) who are affiliated with the
organization and uses multiple devices.
● 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
employees are located.
● View, and request the repair requests for the devices by employee(s).

REQUIREMENT
SPECIFICATION

BUSINESS
REQUIREMENT
SPECIFICATION

2.1 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
functions and discretionary functions entrusted by the BPMC Act, 1949.
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
responded to the challenges of fastest population growth and high-speed economic
development by adopting the best urban management practices. With visionary
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
and promises to deliver modern, accountable, transparent and progressive
governance.

The SURAT MUNICIPAL IT DEPARTMENT, run by visionary technical people
with the mission of nurturing advance citizens by providing highly technical
encompass environment and feasible solution to the complexity.
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
needs and times
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.
Specialties about the place:
● Spacious work environment
● Modern infrastructure
● Latest technologies
● Creative thinkers and developers

SYSTEM
REQUIREMENT
SPECIFICATION

Existing System
● All the assets were handled manually by the technician
● This process consumes more time
● Books are maintained for the request report log which makes it messy
● Many records and data were lost due to manual handling
● User must go to management for their requests
● All the arrived request submit to the administration.
● Then Administration distributes request among different departments according
to the request type.
● 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 maintain the request report log easily
● All the details are now automatically updated
● The employee can request the issue online
● There is no data lost as everything is stored online
● The technician can get the details of the issue online
● Admin can now maintain the log of the departments and also of the vendors

THE OBJECTIVE OF THE

SOFTWARE

3. OBJECTIVE OF THE SOFTWARE
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
was the issue and at what time it was solved
The general objectives are:
● Maintain all Asset details which are owned by the Surat Municipal Corporation
● Maintain complaints details.
● Maintain devices details.
● Maintain IT Support(Technician) details.
● Maintain report-sheet for various levels of process or progress or success.
The main objective of this web application is that it deals with various levels of complaint’s
solution processing development from multiple centers or department to the particular
department of technician to handle the issues or query, and will account for the time used in
allocation, solution, and completion.
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
thorough study of the system.
The planning objective is achieved through a process of information discovery that leads to
reasonable effort to develop.
Keeping the following aspects in mind, the system analysis for the development of the project
is done.
● Identify the drawbacks of the existing system.
● Identify the need for conversion.
● Perform a feasibility study.
● Identify hardware, software and the database requirements.
● Create a system definition that performs the foundation for the subsequent work.

Four key combinations are involved in the feasibility analysis are:
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
hardware and software. The only internet is required.
Behavioral Feasibility:
The system working is quite easy to use and learn due to its simple but attractive interface.
User requires no special training for operating the system.
Operational Feasibility:
The system is operationally feasible, it is made so easy that users will not encounter any
problem during working, as it is very user-friendly.
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

5.1 FLOW CHART

Admin
Explanation:
● The flow starts with login, where admin has to input login details to access
admin panel.
● If Admin credentials > redirect to Admin Dashboard.
● Else verify if it is a user or an employee.
Admin Panel
Device tab
● Admin selects the Device to create a device or view details in the database or
system.
● Can select Edit to edit device(existing) from database or system.
● Can select Req. History to view device request history.
● Can select Delete to remove the device from database or system.
● Can select details to view the device or its details.

Employee tab
● Admin selects the Employee to create employee or view details in the database
or system.
● Can select Employee to view employee or details.
● Can select Edit to edit employee(existing).
● Can select Delete to remove the employee from database or system.
Department tab
● Admin selects the Department to create department or view details in database
or system.
● Can select Department details to view department or details.
● Can select Edit to edit department(existing) from database or system.
● Can select Delete to remove the department from database or system.

User tab
● Admin selects the User to create a technician or details in database or system.
● Can select the User to view the technician or details.
● Can select Edit to edit a technician(existing)
● Can select Delete to remove a technician.
● Request report 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.
● Can select Delete to remove the request from database or system.
Vendor tab
● Admin selects the Vendor to create vendor or details in the database or system.
● Selects vendor to view vendor or details.
● Can select Edit to edit vendor(existing) from database or system.
● Can select Delete to remove the vendor from database or system.
Employee:

Explanation:
● The flow starts with login, where the employee has to input login details to
access employee Dashboard and facility.
● If Employee credentials > redirect to Employee Dashboard.
● Else verify if it is a user.
Employee Panel
Complaint Request report tab
● Employee selects the Request report to view registered complaint and views the
status.
● Can select edit to edit(existing) registered complaint.
● Can select delete to remove(existing) registered complaint.
● Can select a comment to add a comment on the registered complaint.
● 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
access the User Dashboard.
● If IT technician credentials > redirect to use Dashboard.
● Else re-enter the correct Login Details again.
User Dashboard
● Complaint request report tab
● IT technician selects the request report to view the received complaint or
details.
● Selects comment to comment to respond to the requested complaint.
● Selects delete to remove the requested complaint.
● Selects complete if the complaint is resolved.

DATA FLOW DIAGRAM

5.2 DATA FLOW DIAGRAM
Context Level:
Identified Entities: 1. Admin

2. User
3. Employee
Identified Processes: 1. AMS - Asset Management System

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
7.0 Request Report

Admin Level 2:

Admin Level 2:

Admin Level 2:

Admin Level 2:
Main Process : Main Process : Main Process : Main Process :

1.0 Login 2.0 Device 3.0 User 4.0 Department
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
Main Process : Main Process : Main Process :

5.0 Employee 6.0 Vendor 7.0 Request Report
Sub Process of: Sub Process of: Sub Process of:

5.0 6.0 7.0
5.1 Create Employee 6.1 Create Vendor 7.1 Search Request
5.2 View Employee 3.2 View Vendor 7.2 View Request

Admin Level 3:

Admin Level 3:

Admin Level 3:

Admin Level 3:

2.2 View Device 3.2 View User 4.2 View Department

2.2 3.2 4.2
2.2.1 Edit 3.2.1 Edit User 4.2.1 Edit Department
2.2.2 Delete 3.2.2 Delete User 4.2.2 Delete Department
2.2.3 Details
2.2.4 Request
History

5.2 View Employee 6.2 View Vendor 7.2 View Request

5.2 6.2 7.2
5.2.1 Edit Employee 6.2.1 Edit Vendor 7.2.1 Delete Request
5.2.2 Delete 6.2.2 Delete Vendor 7.2.2 Comment

Employee
7.2.3 Complete

Admin Level 4:
Main Process :
7.2.3 Complete
Sub Process of:

7.2.3
7.2.3.1 Add Remark
7.2.3.2 Complete Request

User Level 1:
USER
1.0 Login
2.0 Request Report

User Level 2:
Main Process : Main Process :

1.0 Login 2.0 Request Report
Sub Process of: Sub Process of:

1.0 2.0
1.1 Change Password 2.1 Search
1.2 Login 2.2 View

User Level 3:
Main Process :
2.2 View Request
Sub Process of:

2.2
2.2.1 Delete Request
2.2.2 Comment
2.2.3 Complete

User Level 4:
Main Process :
2.2.3 Complete
Sub Process of:

2.2.3
2.2.3.1 Add Remark
2.2.3.2 Complete Request

Employee Level 1:
Employee
1.0 Login
2.0 Request Report

Employee Level 2:

Employee Level 2:
Main Process : Main Process :

1.0 Login 2.0 Request Report
Sub Process of: Sub Process of:

1.0 2.0
1.1 Change Password 2.1 Create
1.2 Login 2.2 Search
2.3 View
Employee Level 3:
Main Process :
2.3 View
Sub Process of:

2.3
2.3.1 Edit Request
2.3.2 Delete Request
2.3.3 Comment

ENTITY RELATIONSHIP
DIAGRAM

5.3 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

LogId Int Primary key
RequestId Int Foreign key
EntryDate Datetime
EntryBy Varchar(50) Foreign key
Comment Varchar(200)
DB: DeviceMaster

DeviceId Int Primary key
DeviceNumber Varchar(50)
Name Varchar(200)
Description Varchar(500)
Photo Varchar(10)
EnteryDate datetime
EnterBy Varchar(50) Foreign key
Vendor Varchar(500) Foreign key
PurchaseDate Date
WarrantyUpto Date
DeviceType Varchar(100)
Location Varchar(100)

DB: Department

DepartmentId Int Primary key
DepartmentName Varchar(50)
DeviceId Varchar(100) Foreign key
DB: UserMaster

UserId Int Primary key
UserName Varchar(50)
Password Varchar(100)
UserType Varchar(50)
DepartmenId Int Foreign key
Mobile Varchar(20)
Name Varchar(100)
DeviceIds Varchar(100)
DB: Request

RequestId Int Primary key
RequestNo Int
ReqDate Datetime
Status Varchar(50)
EnteryBy Varchar(50)
Title Varchar(50)
Remark Varchar(200)
DepartmentId int

DESIGN

FRONT-END
SCREENSHOTS

7.1 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 – There also an option to edit the device’s information if entered

incorrectly.
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.
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 – Logging in with the given credentials to the user.

Description – Homepage for the user.
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 – Changing password with filling up the required fields.

Description – Pop-up shows the successful changes done.
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 – Page showing the format of the request log report.

Description – In the request, you can also add up the extra comments about that
request.
Description – Showing the details of a selected request given by the employee.

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

7.2 FRONT-END SCREENSHOTS




SOFTWARE TESTING

8. SOFTWARE TESTING
Unit Testing
Testing of individual software components or modules.
Tests: Admin, Employee, and User Login Module – Authenticates successfully.
Description: Admin, Employee, and User should able to login successfully and access
Admin, Employee, and User Dashboard respectively.
Requirement: Admin, Employee, and User must have a valid username and password
provided by developers and admin respectively.
Steps:
1) Navigate to AMS.
2) In the field of username enter the valid username.
3) In the field of password enter the valid password.
4) Click the Login button.

Expected Results: If the credentials are correct then the user will be redirected to their
respective Dashboard from where they will able to utilize AMS.
Likewise, testing was performed on other Modules, namely Devices, Department,
user, employee, vendor within AMS to make sure the pages loaded and were not
resulting in errors as outputs.
Integration Testing
Verifying the smooth function of the modules post-integration.
Tests: Login Module – Authenticates Admin, Employee, and User from a common
page based upon the credentials entered.
Description: If the credentials of an Admin are entered, they will be redirected to
Admin Dashboard or else, if the credentials verified authorize an Employee
or User, they will be redirected to their respected Dashboard.
Requirement: Admin, Employee, and User must have a valid username and password
provided by the Developers and Admin respectively.

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
redirected to the Employee and User Dashboard respectively.
Likewise, testing was performed on other Modules, namely, Devices ,
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
Editing a record(device) and Adding and Deleting a User.

System and Functional Testing
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
records to be added to the database.
Steps:
1) Navigate to AMS.
2) Login using Admin credentials.
3) Select “Create Employee, create User, create a device or create a department” on
the navigation bar.
4) Add Employee, user, devices, and credentials.
5) Click “Save”.
6) Select “Add” under Employee, user, device, and department on the navigation bar.
7) Add the data to be recorded.
8) Click “Submit”.
9) Select “Employee” under Employee on the navigation bar.
10) Select a particular record, click “Edit”, add updated data.
11) Select “Update”.

12) Select a particular record, click “View”, view the record.
13) Select a particular record, click “Delete”, remove the record.
14) Login using Employee or User credentials.
15) Click “View Records” (only option) under the device tab.
16) Select a particular record, click “View”, view the record.
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
device and Complaint status and comment.
End to End and Acceptance Testing
Verifying the function of website/software as per real-world requirements and whether
or not the requirements are met.
Tests: Creating and deleting an employee, user, device or department entering dummy
data, viewing it, editing it through the Admin side.
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.
6) Select “View Employee or user” > “View Details” and/or “Delete”.
7) Select “Device or department” > “Add Device or department” > add dummy data.
8) Select “View Device or department ” > Edit/View/Remove.
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
conditions, that is when a lot of data is stored in the database.
Tests: Accessing a particular record for viewing and editing and making sure it has the
same response time.
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.

Steps:
1) Navigate to AMS.
Admin
6) Select “View Employee or user” > “View Details” and/or “Delete”. 7) Select
“Device or department” > “Add Device or department” > add dummy data.
8) Select “View Device or department” > Edit/View/Remove.
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
Verifying Confidentiality, Integrity, Availability, Authentication, and Authorization.
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
access the data.
Steps:
1) Navigate to AMS.

Admin
6) Select “View Employee or user” > “View Details” and/or “Delete”. 7) Select
“Device or department” > “Add Device or department” > add dummy data.
8) Select “View Device or department” > Edit/View/Remove.
Expected Results: In case of Employee or IT Support login (on authentication and
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
reflected in optimum time. Admin (on authentication and authorization of their
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
Employee or user without any time lapses as well.

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
In Asset Management System, the limitations we noticed are :
● The system may crash on having more than 1000 users spread across the city.
● The system doesn’t have more personalised user/employee and admin
dashboard
● There isn’t no real time tracker of when a request will be solved and who is
attaining the request.

ON-GOING CHANGES
AND FUTURE
ENHANCEMENTS

10. On-going changes and Future Enhancements
There are some ongoing changes and future enhancements which are expected of
us:
● Making a personalised dashboard for Admin/User/ and Employee
● Adding a time tracker of when a request is created and solved
● To add vendor details, and create a serialised number of devices added
● To add an auto-generated device-id for all the devices added which makes them
easy to identify
● To improve the css of the system

CONCLUSION

11. Conclusion
All the objectives that had been charted out in the initial phases were achieved
successfully. System gives the expected output with desired functionality.
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
to communicate better. We understand the importance of planning and designing as a
part of software development. It provides the practical learning and implementation of
knowledge into real world problem statement.
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

12. Learning Outcomes
The learnings outcomes after the internship are:
● Working with the cooperation of the team mates or developer and client or
corporation. The individual work given enhanced the ones responsibility.
● The theoretical knowledge was practically implemented and gave us practical
knowledge and information regarding it.
● Everyone taking equal efforts and putting in hard work. Managing the work
allotted and doing it with acceptance.
● 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
solved with good determination.
● In spite of having difference of opinion and quarrels the output was not affected
and equal efforts were put in

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
Book : Professional ASP.NET 4.5 in C # and VB

Ruchit Final SE PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Ruchit Final SE PDF

Uploaded by

Copyright:

Available Formats

CONTENTS

Sr. No. Contents Page No.

Certificate of Organization III

1. Introduction of Project 1-3

2. Requirement Specification 4-10

3. The objective of the Software 11-12

4. Feasibility Study 13-15

5. System Design with description 16-44

6. Database Design 45-47

8. Software Testing 81-92

10. On-going changes and Future Enhancements 95-96

11. Conclusion 97-98

12. Learning Outcomes 99-100

13. Bibliography 101-102

B.Sc IT Semester VI Project Report

with all basic amenities, to provide a better quality of life.

In such a government organization like Surat Municipal Corporation with various

B.Sc IT Semester VI Project Report

● View, Add, Update, and Delete a Device(s) owned by the organization.

● View, Add, Update, and Delete a User(s) who is IT-Support of a department.

organization and uses multiple devices.

employees are located.

B.Sc IT Semester VI Project Report

B.Sc IT Semester VI Project Report

B.Sc IT Semester VI Project Report

2.1 BUSINESS REQUIREMENT SPECIFICATION

functions and discretionary functions entrusted by the BPMC Act, 1949.

responded to the challenges of fastest population growth and high-speed economic

development by adopting the best urban management practices. With visionary

and promises to deliver modern, accountable, transparent and progressive

B.Sc IT Semester VI Project Report

The SURAT MUNICIPAL IT DEPARTMENT, run by visionary technical people

with the mission of nurturing advance citizens by providing highly technical

encompass environment and feasible solution to the complexity.

needs and times

Specialties about the place:

● Spacious work environment

● Creative thinkers and developers

B.Sc IT Semester VI Project Report

B.Sc IT Semester VI Project Report

● All the assets were handled manually by the technician

● This process consumes more time

● Many records and data were lost due to manual handling

● User must go to management for their requests

● All the arrived request submit to the administration.

● Then Administration distributes request among different departments according

to the request type.

B.Sc IT Semester VI Project Report

● Admin can maintain the request report log easily

● All the details are now automatically updated

● The employee can request the issue online

● There is no data lost as everything is stored online

● The technician can get the details of the issue online

B.Sc IT Semester VI Project Report

THE OBJECTIVE OF THE

B.Sc IT Semester VI Project Report

3. OBJECTIVE OF THE SOFTWARE

was the issue and at what time it was solved

The general objectives are:

● Maintain complaints details.

● Maintain devices details.

● Maintain IT Support(Technician) details.

● Maintain report-sheet for various levels of process or progress or success.