All, Case Study, Retail / E-commerce
Client in a short stint of 10 years in India has grown to tremendous heights. It has become one of the major suppliers to almost all the reputed car-manufacturing companies in India.Dealer Management System with CRM and POS a system to track all the dealers’ sales through a Dealer Management System and Point of Sales. Client demanded a web-based and desktop application for CRM and Point of Sales screen where they manage:
- Adding a Dealer
- Modifying a Dealer
- Deleting a Dealer
- Adding a Customer
- Modifying a Customer
- Deleting a Customer
- Adding an Item
- Modifying an Item
- Deleting an Item
- Applying Discounts to Items
- Managing Discounts
- Adding a Supplier
- Modifying a Supplier
- Deleting a Supplier
- Branch Management
- Regional Office
- POS Screen(Sales Type Sales/Return, Quotation, Minimum Stock Indicator)
- Receipt (Invoice) Printing & Reprinting
- Void Bill
- Screen Journal
- Goods In
- Stock Display(Display Item Information, Quantity for particular selected items)
- Inventory Correction
- Sales Report
- Quotation Report
- Turnover Report
- Claim Sales Report
- Stock Report
- Goods In Report
- Minimum Stock Report
- Inventory Correction Report
- Data Import
(Dealer, Suppliers, Items, Customers, Branch)
(Events Name, Events Date, Events Description, Down)
- Authorization Management
- Modifying a User Account
- Adding a New User Account
- Removing a User Account
- Account Types
Team faced the following challenges:
- Implementing POS Screen that pull information from CRM backend and manage data online and offline both.
- Incorporating web usability principles in the website design so as to ensure easy navigation for all types of users.
- Developing an online & Desktop Dealer Management POS System that has the routing mechanism so that dealers can fill it and route it to Bridge Stone.Generating complex reports which involved extensive querying of database without slowing down the site
- Providing and maintaining the database of a range of interactive features like mail service, sales & expenses, events announcement and reminders.
- The most important of all was to ensure data security.
|Operating System||Linux Cent OS, POS Desktop for Windows, Multi-Server Architecture with Staging & Production environment through Version controlling releases Load Balancer , Apache optimization, security and SSL implementation ,scheduler for backups, alert monitoring system integration,server performance tuning at regular intervals, software firewall configuration and maintenance, email server configuration etc.|
|Development Environment||CJava, Swing, J2EE, JSTL & Servlets, Spring XML Web Services, Java Script, AJAX, Tomcat Apache 6.0.28|
|Database||MYSQL, DB Clustering, DB Optimization, High Availability, Master – Slave Replication, Query optimization, Slow Query Optimization, scheduler for backups, Alert Monitoring System integration, etc.|
|Quality Assurance Testers||1|
- In order to most effectively access the database in an object-oriented context an interface translating the object logic to the relational logic was used to communicate with the relational databases in an object-oriented manner. An intermediary abstraction layer was created for accessing data from the database. Stored procedures were used only for complex retrieval of the data from multiple tables and were entirely avoided with conditional syntax to ensure the smooth performance of the website. The UI layer was kept free of any business logic with images, applications and data being called from their respective servers.
- The design approach was built around JSP using JSTL , Servlets and MYSQL Server due to the performance, security, scalability and the nature of the website. In addition to this, the development structure was specifically implemented to facilitate the ‘Faster to Market’transition of such concepts.
Keeping in mind the enormous structure of the website and the challenges involved n-tier architecture was adopted with all the layers loosely coupled with each other as follows:
- Presentation Specific Layer: This will include the page level layer which will be accessing the other layers beneath to present the data.
- Database Specific Layer: This will be a bridge between the physical database and the business logic accessing the data.
- Business Specific Layer: This will be the bridge between the presentation layer and the database layer. This will contain all the business logic for the different components involved in the project.
- Physical Database Layer: MYSQL5 with the tables, views, stored procedures etc.