E – COMMERCE  COURSE PROJECT

 

ELECTRON OOAD

                                                                                                                 Designed by

                                                                                                      RAKESH KUMAR TIWARI           &              ARCHANA SINGH

                                                                                                                                                                                                                                                                    

 

INTRODUCTION:

 

                    ELECTRON is an online auction system.Traders(buyers/sellers) can register with ELECTRON .Traders can choose one of several business models that are offered by ELECTRON.

                      A potential seller registers with ELECTRON and provides information on the product(s) he would like to sell and choose a business model.This could be an auction (direct or reverse),continuous double auction ,call market etc.As soon as the seller  registers ,ELECTRON will do variety of things such as matching him to potential buyers or matching(aggregating) him with other potential sellers,etc,as entailed by business model.

                      A potential buyer registers with ELECTRON and provides information on products(s) she would like to buy.When a buyer registers,ETH will enable the buyer to know the potential sellers,aggregate the buyer with other potential related buyer,etc,as entailed by business model.

                        A “Trade” happens where buyer(s) and seller(s) participate and negotiate according to a chosen  business model.The trade determines the winner(s).The winning buyer(s) make the payment electronically and security to the seller(s).

USECASE DIAGRAM:

                   

     First in usecase diagram we identifies actors that are performing some critical functions(use cases) and  then showed that how actors are communicating with use cases.

Use cases for each actors are identified by considering the following:

1.Functions the actor requires from the system.

2.Information retrieval/modification in the system by the actor.

3.Events in the system to which actor needs to respond/be notified about.

            

              

CLASS DIAGRAM:

     In Class diagram we have identified many classes and showed the relation between them:

 

            Electron Trading House : This is the main class,which is the aggregation of  Electron monitor and Trader.

 

           Trader: Trader is the class which is generalization of Buyer and Seller .It can buy the product and sell them.

 

Buyer: Buyers will create the buying agent they will buy the product on the behalf of buyer.

 

Seller:Seller will create the selling agent they will sell the product on the behalf of seller.  

 

Agent:It will do all the bidding,buying and selling on the behalf of Trader.

 

Auction: Auction will be of anyone type depending upon business model chosen by seller.

 

Rules:Different business models have different rules associated with them.

 

Negotiation strategy:There will be Negotiation strategy associated with agent ,specified by Trader(Buyer/Seller).According to which agent       will increment or decrement his/her price.

 

Product:Treder(Buyer/Seller) will specify product and it’s description.

 

Deal finalization:Treader will finalise the deal when an appropriate match will find by the agents.

 

SEQUENCE DIAGRAM:

 

   There are two Sequence diagrams. First Sequence diagram  describes the login usecase ,when Trader is not registered and Second Sequence diagram shows the sequence of main activity performed  in the ELECTRON.

 

ACTIVITY DIAGRAM:

 

   Here we are presenting Activity diagram for the main activities performed  in ELECTRON between User,Marketplace,and Agent.

 

STATE CHART:

 

  State chart diagram shows the various states ELECTRON  market can be in.

 

ARCHITECTURAL ANALYSIS:

 

 We are using four Tier architecture.

DESIGN PATTERNS:

 Design Patterns are simple and elegant solution for problem occuring in software design process. For ETH following design patterns may be used :

                  Abstract factory: Create object class for business model so that we can select two different model.

 Decoraotar : Decorate auction object helps in providing added services to users of ETH. That can be used to add/delete services at run  time.                 

Composite: To represent the structure of the Auction house .

                  Strategy : Different types of  negotiation strategy are used in ETH, linear,cubic  etc. Strategy can be used in this case.

IMPLEMENTATION:

 

            ELECTRON  is implemented according to architecture discussed  above. We are using Java for implementing this whole architecture. We are using JDBC (Java DataBase Connectivity) to use database in our system.
                        Following two figures shows Component Diagram and Deployment Diagram, for implementation of ETH .