Project on VEHICLE IDENTIFICATION
INDEX & TABLES
1) Introduction:
1.1) Purpose:
1.2) Scope:
1.3) References:
1.4) Technologies:
1.5) Abbreviations:
2) Overall Description:
2.1) Product Perspective:
2.02) Software Interface:
2.03) Hardware Interface:
2.04) Communication Interface
2.05) Product Function:
2.06) User Characteristics:
2.07) Constraints:
2.08) 0-Level Data Flow Diagram:
2.09) 1-Level Data Flow Diagram:
2.10) Entity Relationship Diagram:
2.11) Class Diagram:
2.12) Use Case Diagram:
1) Introduction:
1.1) Purpose: Vehicle Identification is for establishing and sustaining the customer relationships by maintaining valuable customer information. It also integrates the Support Desk, which gives an overall view of all the customer relationships. The central repository enables to track account- level data, service level agreements, user contact information and product ownership details.
1. In the automotive service industry, two factors are essential for success – outstanding customer service and operational efficiencies. Through outstanding customer service, automotive service companies can gain customer loyalty, increase the number of customer referrals and provide more customers with lucrative preventive maintenance services. Operational efficiencies, on the other hand, improve repair and maintenance accuracy, reduce errors, and improve decision-making processes.
2. To assist its services staff in retrieving information needed for their work and to meet the heightened service expectations of its customers, the client Web-enabled its internal information systems. In an effort to further streamline the service and repair process and to gain deeper insight into operations so that it could better serve customers, the client also sought to improve the timely exchange of data.
3. Improved customer satisfaction by reducing the need for customers to fill out forms and provide information about their vehicles to customer service representatives during the check-in process. The representatives can more quickly access the vehicle's history and suggest which periodic maintenance services should be performed. They can also determine what parts are in stock for the various models, which helps customer service representatives keep customers informed about their vehicles while respecting their time. This improved level of service results in higher customer loyalty.
1.2) Scope:
Create different system users and assign different roles with related permissions.
Manage all the account details such as user name, company, phone numbers, address
Websites, email addresses of the entire customer from one central location.
Manage all the details regarding features of the vehicle such as vehicle type, Vehicle Company, vehicle model number, vehicle color, vehicle cost.
Track all the customers and their contact details.
Group the contacts together in a single account according to some criteria.
Capture, View and edit all user transactions, including email, chats, and services calls in a single system.
Confirmation of end user identity and will verify which users are authorized to receive support.
Maintain history of each customer and their related information about the product sale, & support related transactions.
View all the details of all the interactions made with the customer.
Activities like updations, creations done in the system by the system users will be maintained in the form of logs for auditing and maintaining the integrity of the system.
1.3) References:
IEEE SRS Format
1.4) Technologies:
J2EE: Application Architecture
MySql: Database
Tomcat:Server
Kawa
1.5) Abbreviations:
Overall Description will describe major components of the system, interconnection and external interfaces.
Specific Requirements will describe the functions of actors, their role in the system and constraints.
Use Case Diagram will describe the functional relationship between different entities, i.e. Actors (users).
2) Overall Description:
Describe the general factors that affect the product and its requirements.
2.01) Product Perspective:
Client Side Application Database
Server Server
The web pages (XHTML/JSP) are present to provide the user interface on customer client side. Communication between customer and server is provided through HTTP/HTTPS protocols.
The Client Software is to provide the user interface on system user client side and for this TCP/IP protocols are used.
2.02) Software Interface:
Client on Internet: Web Browser, Operating System (any)
Client on Intranet: Client Software, Web Browser, Operating System (any)
Web Server: WAS, Operating System (any)
Data Base Server: MySql, Operating System (any)
Development End: WSAD (J2EE, Java, Java Bean, Servlets, HTML), MySql, OS (windows), web server.
2.03) Hardware Interface:
Client Side
Processor
RAM
Disk Space
Internet Explorer
6.0
Pentium II at 500
MHz
128 MB
1 GB
Server Side
Web sphere
application server
V5.0
Pentium III at 1
GHz
512 MB
1 GB
MySql
Pentium III at 1
GHz
512 MB
1GB (Excluding
data size)
2.04) Communication Interface:
Client on Internet will be using HTTP/HTTPS protocol.
Client on Intranet will be using TCP/IP protocol.
2.05) Product Function:
It will be used by Insurance Company for physical verification of vehicle.
It will be used by vehicle workshop for better customer service.
It will be used by police for theft checking.
It will be used by RTO for registrations and license making.
2.06) User Characteristics: Every user should be comfortable of working with computer and net browsing. He must have basic knowledge of English too.
2.07) Constraints:
GUI is only in English.
Login and password is used for identification of customer and there is no facility for guest.
This system is working for single server.
There is no maintainability of back up so availability will get effected.
Limited to HTTP/HTTPS.
2.08) 0-Level Data Flow Diagram
2.09) 1- Level Data Flow Diagram
2.10) Entity Relationship Diagram
2.11) Class Diagram
2.12) Use Case Diagram
1) Service Center Manager: He manages the request registered by the user and maintain user database and provides satisfactory services to them.
2) Admistrator: He maintains all records of the customers regarding information of their Vehicles and carry out the various identification processes.
Manage system user
3) Insurance Manager: He accepts all the requests from the user and provides the Suitable insurance facilities. Provides insurance schemes
4) Police: Useful in theft checking and reduction of crime.
Investigation Manages FIR report
5) User: He makes request for obtaining various services and take benefits from them.
Manage all the account details such as user name, company, phone numbers, address
Websites, email addresses of the entire customer from one central location.
Manage all the details regarding features of the vehicle such as vehicle type, Vehicle Company, vehicle model number, vehicle color, vehicle cost.
Track all the customers and their contact details.
- Maintain the services provided to the customer through Service Level Agreements.
Group the contacts together in a single account according to some criteria.
Capture, View and edit all user transactions, including email, chats, and services calls in a single system.
Confirmation of end user identity and will verify which users are authorized to receive support.
Maintain history of each customer and their related information about the product sale, & support related transactions.
View all the details of all the interactions made with the customer.
Activities like updations, creations done in the system by the system users will be maintained in the form of logs for auditing and maintaining the integrity of the system.
1.3) References:
IEEE SRS Format
1.4) Technologies:
J2EE: Application Architecture
MySql: Database
Tomcat:Server
Kawa
1.5) Abbreviations:
- HTML: Hypertext Markup Language is a markup language used to design static web pages.
- J2EE: Java 2 Enterprise Edition is a programming platform— part of the Java Platform—for developing and running distributed multi tier architecture Java applications, based largely on modular software components running on an application server.
Overall Description will describe major components of the system, interconnection and external interfaces.
Specific Requirements will describe the functions of actors, their role in the system and constraints.
Use Case Diagram will describe the functional relationship between different entities, i.e. Actors (users).
2) Overall Description:
Describe the general factors that affect the product and its requirements.
2.01) Product Perspective:
Client Side Application Database
Server Server
The web pages (XHTML/JSP) are present to provide the user interface on customer client side. Communication between customer and server is provided through HTTP/HTTPS protocols.
The Client Software is to provide the user interface on system user client side and for this TCP/IP protocols are used.
2.02) Software Interface:
Client on Internet: Web Browser, Operating System (any)
Client on Intranet: Client Software, Web Browser, Operating System (any)
Web Server: WAS, Operating System (any)
Data Base Server: MySql, Operating System (any)
Development End: WSAD (J2EE, Java, Java Bean, Servlets, HTML), MySql, OS (windows), web server.
2.03) Hardware Interface:
Client Side
Processor
RAM
Disk Space
Internet Explorer
6.0
Pentium II at 500
MHz
128 MB
1 GB
Server Side
Web sphere
application server
V5.0
Pentium III at 1
GHz
512 MB
1 GB
MySql
Pentium III at 1
GHz
512 MB
1GB (Excluding
data size)
2.04) Communication Interface:
Client on Internet will be using HTTP/HTTPS protocol.
Client on Intranet will be using TCP/IP protocol.
2.05) Product Function:
It will be used by Insurance Company for physical verification of vehicle.
It will be used by vehicle workshop for better customer service.
It will be used by police for theft checking.
It will be used by RTO for registrations and license making.
2.06) User Characteristics: Every user should be comfortable of working with computer and net browsing. He must have basic knowledge of English too.
2.07) Constraints:
GUI is only in English.
Login and password is used for identification of customer and there is no facility for guest.
This system is working for single server.
There is no maintainability of back up so availability will get effected.
Limited to HTTP/HTTPS.
2.08) 0-Level Data Flow Diagram
2.09) 1- Level Data Flow Diagram
2.10) Entity Relationship Diagram
2.11) Class Diagram
2.12) Use Case Diagram
1) Service Center Manager: He manages the request registered by the user and maintain user database and provides satisfactory services to them.
2) Admistrator: He maintains all records of the customers regarding information of their Vehicles and carry out the various identification processes.
Manage system user
3) Insurance Manager: He accepts all the requests from the user and provides the Suitable insurance facilities. Provides insurance schemes
4) Police: Useful in theft checking and reduction of crime.
Investigation Manages FIR report
5) User: He makes request for obtaining various services and take benefits from them.
No comments:
Post a Comment