Customer Relation Management About The Project: ISO 9001: 2008 Certified Institution 1
Customer Relation Management About The Project: ISO 9001: 2008 Certified Institution 1
CHAPTER 1
INTRODUCTION
• customer
• administrator
• service manager
Product Details useful for the customers to view the details of the products
which are in the company. When the customer needs to order for a product, they can
use the quotation order form to give the quotation to the company. Administrator
checks the quotation order of the customer and if the product is available, complete
details about the product is displayed. After seeing the quotation customer selects the
product according to their requirement. Administrator after seeing the purchase order
delivers the goods to the customer. If there is any fault in the goods purchased customer
can use goods return form to return the product. After customer purchases the product,
their credit card number is got and the number is sent to the finance department for
verification after verification is over the product is delivered to the customer.
Using the Feedback form customer can send their feedback about the product as
well as the company.
Quotation Order Placement is the area where the administrator checks for the
quotation made by the customer. If the customer purchases the product, there will be an
acknowledgement made to the administrator, he checks for presence of the product; if
the goods are available it will be delivered to the customer. If there is any defect in the
product which is purchased by the customer he will return it to the company using
goods returned form. Administrator checks the defect of the product and replaces to the
customer.
Modules
Customer
• Product Details
• Quotation Order
• Quotation Deliver
• Purchase Order
• Goods Delivery
• Payment
• Feedback
Administrator
• Quotation Placement
• Purchase Order
• Dispatching Products
• Payment
• Goods Return
• Add Product
• Delete Product
• Update Product
Service
• Servicing Details
• Feedback form
Our technically competent, experienced, and certified consultants have helped client
organization design, develop and deploy technology enabled business solutions.
SRM_Soft_Solutions provides a comprehensive managed service that masks the
complexity of extranet deployment and maximizes return on investment.
Operational Feasibility
In this test, the operational scope of the system is checked. The system under
consideration should have enough operational reach. It is observed that the proposed
system is very user friendly and since the system is built with enough help, even
persons with little knowledge of windows can find the system very easy.
Technical Feasibility
This test includes a study of function, performance and constraints that may affect the
ability to achieve an acceptable system. This test begins with an assessment of the
technical viability of the proposed system. One of the main factors to be accessed is the
need of various kinds of resources for the successful implementation for the proposed
system.
Economical Feasibility
An evaluation of development cost weighed against the ultimate income or benefit
derived from the development of the proposed system is made. Care must be taken that
incurred in the development of the proposed of the system should not exceed the from
the system. The income can be in terms of money or goodwill, since the software brings
in both, the system is highly viable.
JSP technology uses XML-like tags that encapsulate the logic that generates the content
for the page. The application logic can reside in server-based resources (such as
JavaBeans component architecture) that the page accesses with these tags. Any and all
formatting (HTML or XML) tags are passed directly back to the response page. By
separating the page logic from its design and display and supporting a reusable
component-based design, JSP technology makes it faster and easier than ever to build
Web-based applications. Java Server Pages technology is an extension of the Java
Servlet technology. Servlets are platform-independent, server-side modules that fit
seamlessly into a Web server framework and can be used to extend the capabilities of a
Web server with minimal overhead, maintenance, and support. Unlike other scripting
languages, servlets involve no platform-specific consideration or modifications; they are
application components that are downloaded, on demand, to the part of the system that
needs them. Together, JSP technology and servlets provide an attractive alternative to
other types of dynamic Web scripting/programming by offering: platform
independence; enhanced performance; separation of logic from display; ease of
administration; extensibility into the enterprise; and, most importantly, ease of use.
Today servlets are a popular choice for building interactive Web applications. Third-
party servlet containers are available for Apache Web Server, Microsoft IIS, and others.
Servlet containers are usually a component of Web and application servers, such as BEA
Web Logic Application Server, IBM Web Sphere, Sun Java System Web Server, Sun Java
System Application Server, and others.
Tag Libraries
JSP tag libraries define declarative, modular functionality that can be reused by any JSP
page. Tag libraries reduce the necessity to embed large amounts of Java code in JSP
pages by moving the functionality of the tags into tag implementation classes
Directives:
• Page
• Include
A page directive is aimed to define certain attribute of a JSP page. For example
Language of the page in which the page content should be written, which class to be
imported so that it can be used within the JSP page.
Include
This directive is to include the HTML, JSP or Servlet file into a jsp file. This is a static
inclusion of file i.e., it will be included into the jsp file at the time of compilation and
once the jsp file is complied any changes in the included the file will not the reflected.
Declarations
All the jsp variables are declare within < %!......%>
Expressions
All the expressions, evaluation and display the variables are expressed within this <%=
……… %>
Standard Action
Include<JSP: include page=”<filename>”/>
This inclusion of file is dynamic and the specified file is included in the JSP file at run-
time i.e., output of the included file is inserted into the JSP file.
This will redirect to the different page without notifying browser Custom Tags: Taglib
JSP Architecture
JSP are high level extension of servlet and it enables the developers to embed java code
in html pages. JSP files are finally complied into servlet by the JSP engine. Compiled
servlet is used by the engine to serve the requests.
Javax.servlet.jsp
JSP page
HTTP JSP page
These two are classes. This class defines the interface for the complied JSP page.
jspInit()
jspDestroy()
_jspservice(HttpServletRequest request,
Http ServletResponse response)
In the complied JSP file these methods are present. Programmer can define jspInit () and
With the lowest implementation and maintenance costs in the industry, SQL Server
2000 delivers rapid return on your data management investment. SQL Server 2000
supports the rapid development of enterprise-class business applications that can give
your company a critical competitive advantage. Benchmarked for scalability, speed, and
performance, SQL Server 2000 is a fully enterprise-class database product, providing
core support for Extensible Markup Language (XML) and Internet queries.
SQL Server 2000 has demonstrated record-breaking performance that you can
leverage.
XML - XML support allows your data to be easily stored for use by Web
applications.
Data Mining - Discover patterns and trends with data mining, and make
predictions about future trends in your business.
Replication - With SQL Server 2000 you can implement merge, transactional, and
snapshot replication with heterogeneous systems.
SYSTEM ANALYSIS
In system analysis phase, a preliminary analysis will be conducted to find out the
feasible tools & platform to develop the proposed system. The tools & platform selected
should be in such a manner that is adoptable at the client’s end easily.
Before creating this website, all users (actors) used to send their information through
telephones, fax, postal mails or they use person to person contacts with each other. It
will take long time to send their orders through this type of communications. And there
May error occurs in the process. The administration faces the problems to collect all the
orders from customers and to analyze the required goods for the corresponding
product. And also the information replies will again a delay process.
Administrations have to send their orders to suppliers for their required goods. In the
customers point of view sending their orders in a traditional manner is a risk process
and they have to wait for a long time in order to get reply.
The system incorporates intelligent Order processing System which checks and
intimates the required Higher-ups in the Company about any discrepancies in the
Once the parts are supplied the Stocks will be updated. Then a production plan will be
drawn up taking the bill-of-materials into consideration. Once the Production plan is
approved, the Part Stocks will be updated when the material is issued to the production
department.
Once the finished products are delivered from the Production Department, the Product
Stocks will be updated. Once the finished products are available the Products will be
dispatched to the Customers according to the Orders placed by the Customers. The
Product stocks with the company will be reduced by the amount dispatched & the
dealer’s stocks will be increased by the same amount. This will maintain the Product
inventory with the Customers also.
SYSTEM DESIGN
After analyzing the Requirements, the Architecture chosen for the System to be
implemented is decided as the Multi-tier Architecture. This architecture is chosen
because it separates the Development of the System into independent modules or tiers.
Generally complex projects use this, as the work in each tier can be taken up by
specialists in each field. Thus the team can be structured & integrated by making the
best possible use of the resources available.
Detailed design is logical design that the expands the system design to contain the more
detailed descriptions of the processing logic such that the designers successfully
complete the coding.
Input Design
In this input design we enter the input values from all login actors (users) and all the
required information for the respected entities. The inputs starts from asking the login
permission to enter into the site, this will be differ for all the actors depending on the
type of the user.
The administration actor will have separate accessing the modules and have special
features other than suppliers and customers. Total site controls will be handled by this
actor. All the new products, customers, supplier entities will be done by this actor. The
administration will give login permissions i.e., user name and password to customers
and suppliers.
Customers have the rights to send their product orders to the administration. All this
inputs are stored in the corresponding database.
Output Design
The output in each stage is displayed in a separate page. The accessibility of all the
actors will be entirely different when they login. The Admin will have all the rides. And
staff will have most of the rides except the add and delete of customers and suppliers.
The customers will have the separate page when they login in to the site. And they will
have the options product view, my profile, details, change password and submit orders
with which they can interact with the system and admin.
The suppliers will have the separate page which will contain like view part, my profile,
details, change password, part indent, submit quotation and these will accessed if and
only if he enters with the correct password. The suppliers will send their quotation to
the admin.
A database is a central source of data meant to be shared by many users for variety of
applications. The heart of the database is DBMS which allows creation, deletion and
updating of databases and retrieval of data.
Data Flow Diagrams (DFD) are the pictorial representations of the flow of the processes
in the system. They are very effective and understandable even by a novice. The process
involved in the system is represented with a circle and the flow is represented with an
arrow headed line in the direction of flow. The store is represented with a pair of
parallel lines. The flows, processes and stores are named meaningfully. The data flow
diagrams can be divided into levels. In the first level diagram if the process in abstract
that can be explained better in the next level. The following are the data flow diagrams
for the system. The data flow diagrams for the various functionalities in the application
are as follows.
LEVEL 0 DFD
LEVEL 2 DFD
LEVEL 3 DFD
A database is a collection of interrelated files and set of programs that allow users to
access and modify these files. It provides an abstract view of the data. A high-level data
model serves the database designer by providing the conceptual framework in which to
specify, in a systematic fashion, with the data requirements of the database users are,
and how the database will be structured to fulfill these requirements.
PRODUCT2
QUOTATION2
PURCHASE2
DISPATCH1
This table is used to store dispatchment master details
PAYMENT
This table is used to store payment details.
DEFECT2
This table is used to store defect product details
REMARKS
This table is used to store remark details
5.1 IMPLEMENTATION
Implementation includes all those activities that take place to convert the old system to
the new system .The new system will replace he existing system. The aspects of
implementation are as follows.
Conversion
Conversion means changing from one system to another. The objective is to put the
tested system into operation. It involves proper installation of the software package
developed and training the operating staff.
The software has been installed and found to be functioning properly. The users how to
be trained to handle the system effectively. Sample data provide to the operating stuff
and were asked to operate on the system. The operating stuffs now have a clear out look
of the software and are ready for practical implementation of the package.
5.2 TESTING
In testing the programs were generated and tested for its accuracy and bugs were
corrected as and when required. Every entry of the module was made accessible using
the menu.
Testing Process
In unit testing, individual components are tested to ensure that they operate correctly.
Each component is tested independently, without any other system components.
Module Testing
System Testing
The sub-systems are integrated to buildup the entire system. The testing process is
concerned with finding errors, which is an outcome of unanticipated interaction
between sub-system and system components. If is also concerned with validating
whether the system meets its functional and non-functional requirements.
A number of software testing strategies have been proposed. All provide the software
development with the procedure for testing and all have the following characteristics.
• Testing begins at the module level and works towards the integration of entire
component based system.
• Different testing techniques are appropriated at different point of time.
• The developer of the software and an independent test group conducts the testing.
• Testing and debugging are different activities, but debugging must be
accommodated in any testing strategy.
The Project is tested for its execution step by step for every file that is used in this
project. Each module in every file is tested completely for execution of each operation.
The testing operation was successful and every module works properly.
The project is tested with the various input and output test cases. For the appropriate
input values the corresponding outputs were seen. The error messaging system was
also checked by giving improper values to check if the validation processes are done
properly.
Integration Testing
The whole system which has been divided into modules has been integrated into a
single system and the testing operation is done to the whole system to find if any error
has occurred to the project due to integrating it or joining the various modules of the
system.
Functional Testing
The functioning of the system is tested with various test cases. The various functions
such as registration, sign-in, sending card and checking card are all tested with various
test data, and the functioning is proved to be successful without any errors or bugs in it.
This is the login page. It provides the options like Existing customer and new customer.
Using this form customer can login to the company website.
This page is the New Customer Registration Form. The customer can register to
the website through this page.
This customer module describes customer requirements, select product details button
that displays overall product details in the company, as in the same sequence all the
buttons displays corresponding details.
Customer can place quotation using this form. This contains the available products in
the company. Customer orders the available products in the company.
This is an acknowledgement page for customer quotation order. This form is sent by
administrator to the customer to enable the customer to know whether his quotation is
being processed or not
Customer selects the products that he wants to purchase using this form, after
processing his quotation order by administrator.
After delivering the goods to the customer. Administrator sends the payment Details by
the above form. After seeing this form customer pays the bill.
Customer uses this form to return the damaged goods if he founds any damages for the
purchased products. Administrator sees this form and directs to the service
Department.
This form is used for processing the customer quotation order. Administrator
does this job after seeing customer quotation order.
This form is used for processing the customer purchase order. Administrator does
this job after seeing customer purchase order.
This form is used to dispatch the products to the customer. Administrator uses this
form to dispatch products to customer based on purchase id.
This form contains the details like dispatch id, dispatch date, purchase id and total
amount. Administrator sends this form to customer.
This page contains servicing details and feedback form. service manager uses this
form to service the products that come to him.
Service manager sees the damaged products and service the products using this form.
CONCLUSION
This system has been developed successfully incorporate all the requirements.
Appropriate care has taken during database design maintain database integrity and to
avoid redundancy of data. This site was developed is such a way that any further
modifications needed can be easily done. User feel freely while using this site. In this all
technical complexities are hidden. This site is a more user friendly. The quality factors
like correctness, efficiency, usability, maintainability, portability, accuracy, errors,
tolerance, expandability and communicatively all are successfully done.
REFERENCES
BOOKS
WEB SITES
• www.javaworld.com
• www.allapplabs.com.
• www.apache.com.
• www.java.sun.com.