|

Computer Sciences Corporation
Computer Sciences Corporation used Diyatech as the primary development
resource in order to develop an eBusiness application for their important
client. Diyatech closely worked with CSC in capturing client's requirements,
designing the system, implementing and testing it. CSC gave all the development
work to Diyatech on this project.
Project Description
The client's website provides a central place for buying and selling
of internet based advertisements. This allows advertisers, to have access
to all premium online sites where they can advertise. Similarly it allows
sellers to sell their advertisement space through this common place. This
website lessens the worries of both sellers and buyers, by bringing their
corresponding targets to this common place. This website covers the entire
lifecycle of buying and selling internet based advertisement, which covers
exposing, buying and negotiating of available advertisement spaces matching
buyer's specification.
Diyatech was responsible for the architecture and implementation of the
back-end components, whose main responsibility was to load inventory and
expose it to buyers. These components included: Inventory Load, Inventory
Unload, Site Search and Check Availability.
Following are the environments used in this project for development and
deployment :
-
Used Weblogic 5.1
as the application server, on Sun Solaris.
-
Used Oracle 8i as the
database server, on Sun Solaris.
-
Used Symantec Visual
Café 3.0 as the development environment, on Windows NT.
-
Used MS Visual Source
Safe for source code management, on Windows NT.
-
Used Java 2 Platform,
Enterprise Edition (J2EE) for developing all these multi-tier components.
-
Used Java as the development
language.
Inventory Load
The main purpose of this component is to load inventory (available advertisement
spaces) submitted by a seller into the client's database.
-
Designed this component
using Unified Modeling Language (UML) with Rational Rose 2000.
-
Used Enterprise Java
Beans (EJB) for implementing this component, with business layer encapsulated
in a session bean, and data layer implemented using entity beans.
-
Developed Java Servlet
and Java Server Pages (JSP) for testing this component.
-
Provided support for
multiple inventory load file formats. This was made possible by providing
support for multiple parsers, through abstract factory pattern, which
was implemented as an Remote Method Invocation (RMI) server.
-
Defined inventory load
file format in Extensible Markup Language (XML), using XML Spy 3.0.
-
This component consisted
of 20 classes and approximately 4000 lines of code.
Inventory Unload
-
The main purpose of this component is to unload inventory belonging to
a specified seller from the client's database into a storage file.
-
Designed this component
using Unified Modeling Language (UML) with Rational Rose 2000.
-
Used Enterprise Java
Beans (EJB) for implementing this component, with business layer encapsulated
in a session bean, and data layer implemented using JDBC.
-
Developed Java Servlet
and Java Server Pages (JSP) for testing this component.
-
Defined inventory unload
file format in Extensible Markup Language (XML), using XML Spy 3.0.
-
This component consisted
of 12 classes and approximately 3000 lines of code.
Site Search
The main purpose of this component is to look for the websites targeting
buyer's criteria.
-
Designed this component
using Unified Modeling Language (UML) with Rational Rose 2000.
-
Used Enterprise Java
Beans (EJB) for implementing this component, with business layer encapsulated
in a session bean, and data layer implemented using JDBC.
-
Developed Java Servlet
and Java Server Pages (JSP) for testing this component.
-
This component consisted
of 10 classes and approximately 2500 lines of code.
Check Availability
The main purpose of this component is to bring back all available inventory
(advertisement spaces), which match buyer's targeting criteria.
-
Designed this component
using Unified Modeling Language (UML) with Rational Rose 2000.
-
Used Enterprise Java
Beans (EJB) for implementing this component, with business layer encapsulated
in a session bean, and data layer implemented using JDBC.
-
Developed Java Servlet
and Java Server Pages (JSP) for testing this component.
-
This component consisted
of 25 classes and approximately 5000 lines of code.
|