| |
| Case Study |
| |
Application re-engineering helps apparel leader
achieve the right fit |
|
|
Patni's approach to re-engineer the existing problem management system to a MVC architecture
helped the client improve the speed and efficiency for resolving problems.
The Client
The client is one of the
world's largest apparel
manufacturers.
The Challenge
In an industry where style and fashion trends change quickly, the client relied heavily
on its IT infrastructure to react and deliver products ahead of the competition and
within budget. This called for proactive monitoring and resolution of problems to
deliver high uptime and continuous access to applications at all times. For resolving
problems, the client had a problem management system which captured details of
problems in the IT infrastructure and passed the same to the helpdesk team for
resolution. However, as the number of users increased, the system faced severe
scalability and performance issues.
Other key challenges for the client included:
 |
Inability to resolve the queries of the increased number of users within
stipulated time limits |
|
Inability to prioritize problems. |
The Solution
Patni partnered with the client to re-engineer the application. The re-engineering
technologies were Java based which implicitly addressed all performance and scalability
issues. Patni chose JSP, EJB and Java Servlets with IBM Websphere as the application server. As
the J2EE environment isolated the presentation layer from the business logic, it made
maintenance and enhancement of the application relatively easier.
Key features of the re-engineered application include:
|
MVC (model view controller) architecture for better performance and scalability |
|
Connectivity with IBM Tivoli for storing problems from mainframe system |
|
User interface for capturing incoming problem details |
|
Interface for paging. |
The Technology
|
JSP 1.1 - IBM HTTP Server |
|
EJB 2.0 - IBM Web Sphere
4.0 |
|
MQ Series 5.12 |
|
Visual Age 4.0 |
|
Oracle 8i |
| |
 |
The Benefits
The re-engineered application has provided the client the ability to track and
resolve user problems in a much more efficient manner. Key benefits for the
client include:
|
Faster resolution of user problems |
|
Queries classified and escalated according to the severity of the problem.
For example, the paging interface can send immediately send paging
notifications to the concerned support person, whenever a Severity 1 ticket
is logged |
|
Ability to enhance and add new features in a faster manner as the MVC
architecture decouples data access, business logic, data presentation and
user interaction. |
|
