"Net-Auction"
Yüklə 310,72 Kb.
|
- Bu səhifədəki naviqasiya:
- Table of Contents
- 3.5 Global class diagram 10
- 3.8 PL design 14
- 4.1 Possible Extensions and improvements 23
- Design Design goals and requirements
- Clients system management goals
- Products system management goals
- Tables description: Hosting tables (User can modify its content)
- Administrative tables (User cant modify its content)
- Class structure Classes generated by ASP for dataset object
- DAL design Design patterns
- T he big picture BLL design
- Diagram of classes relationships
- PL design Design patterns
- Main algorithms Bidding algorithm
- Winners announcement algorithm
|
The Technion Electrical Engineering Software Laboratory "Net-Auction" Online auction system Project Book Directed by: Mr. Maxim Gurevich Submitted by: Yuri Kipnis Alex Scheotkin Table of Contents 3.1 Design goals and requirements 5 3.2 File structure 7 3.3 Data base design 8 3.3.1 Data base diagram 8 3.3.2 Tables' description: 9
3.6.1 Design patterns 11 3.6.2 The big picture 12
3.7.1 Design patterns 12 3.7.2 Diagram of classes relationships: 13
3.8.1 Design patterns 14 3.8.2 Diagram of site map: 15 3.8.3 Pages description: 15 3.9 Main algorithms 19 3.9.1 Bidding algorithm 19 3.9.2 Winners announcement algorithm 20 3.9.3 Feedback and vote algorithm 21 3.9.4 Search algorithm 22
Net-Auction is an implementation of web auction. It is like eBay, Sotheby, and others, but has its original design and bid politics. The main goal is to provide easy way for buying and selling items (products) over the web. Any person can register in the web site and after that can to present his own products for tenders, to take part in another tenders (add bids), to manage user account, to resell unsold products, rate another users, to be rated and other. Unregistered person may only see common pages with all tenders, products and seller's information. In addition to there common operations there are used some original marketing solutions. For example, there is an original algorithm for detecting auction winners, based also on the quantity of bought products and user`s money points that has been declared in his account or got in a process of his sells. There was invested much effort to make the web site easy, intuitive and friendly for use. Other features will be described in detail in following parts. There are few personal goals in this project; to become more familiar with ASP.NET, C#, Microsoft SQL Server, SQL language and a complex of all above.
The programming language used in the project is Microsoft C#. It is an object-oriented programming language developed by Microsoft as a part of the .NET platform. It has procedural, object-oriented syntax based on C++ and includes aspects of several other programming languages (Delphi and Java) with a particular emphasis on simplification. The additional programming tool we used in this project is a Microsoft SQL Server. It is a relational management system (RDBMS) produced by Microsoft. “Microsoft Visual Studio 2005” is a program environment that was used for project development.
The work on the project started with learning the main concepts and methods of web programming on ASP.NET 2. There were considered themes like HTTP protocol main methods, HTML objects and programming language. The next stage was studying C#, its object-oriented concepts, syntax and main libraries included in. After achieving general understanding of web-programming and after consolidation of a project design, it become possible to begin with writing the program code.
O In the third stage, the main part of the project, "Business Logic Layer", was built. This part includes main algorithms used by the web site. Moreover, it includes classes and methods that connect between a "DAL" and a "PL" – the next part of the work.
The next stage was "Presentation Layer". This part contains a visual building of internet pages and its object functionality. Master page mechanism was used for getting a unique visual structure of site pages. Also was used .scc file for building visual unique objects for most of project pages. Additional mechanisms that were used in this stage are a sitemap, session object and authentication forms. Some of the tools are present only in the latest version of ASP.NET and others are known from ASP.NET 1.x versions.
In addition there were prepared a power point presentation, placard and a simple website that represents our project.
This part contains detailed description of project requirements as it was presented at the start of a work on a project.
Database tables divide for two groups. The first contains tables for administration of the web site, like "Years", "Months", "Countries" and "Categories". The other one contains tables for hosting information about users, tenders, products, history and more.
On this diagram we can see the fields of all tables and relationships between data base tables. 
Hosting tables (User can modify its content): "Clients" – this table contains information about users, registered on the site. "Products" – this table contains information about all products on the site, there are products that have an active tender ("active" field is sat), products before tender and products that did not sold on its tender ("after tender" field is sat). "Tags vs. Products" – this table contains pairs of product and tag. We use this table for searching products by its tags. The "Is title tag" field is sat if current tag presents in title, we need it for priority in search algorithm. "Tenders" – this table contains information about tenders. "Bids per Tender" – this table contains information about all bids done by users. "Seller vs. Buyers" – this table contains pairs of seller and buyer. The field "Is voted" sat if the buyer voted for the seller. "Feedbacks vs. Clients" – this table contains feedbacks of all users. "Sold Product History" – this table contains information about previous purchases. Administrative tables (User can't modify its content): "Categories" – this table contains a list of categories. "Countries" – this table contains a list of countries. "Years" – this table contains a list of years. "Months" – this table contains a list of months.
"Waiting Clients" – not in use, this table can be used in future for email registration of new users.
Classes generated by ASP for dataset object: 
BLL Classes: 
Classes contain main algorithms: 
Note: detailed class diagram of BLL relations between classes will be presented in BLL design part. 
This layer implemented by using ASP.NET object – dataset. Dataset is a group of classes describing a simple in-memory relational database, were the star of the show in the initial release (1.0) of the .NET. Some of class methods are simple methods for getting, inserting or deleting rows. Others are complicated and use relations between different tables. Dataset object is represented by “Auction” class. It contains methods and fields allow access to in-memory data and classes for SQL database representation.
Business Logic Layer response for data exchange between DAL(Dataset) and presentation layer. In this layer were implemented main algorithms and all access operations to the database. Moreover, it contains two types of classes. The first one is classes that implement BLL algorithms and define objects used by them. The second one is classes that allow access to the DAL Dataset object. Each BLL class of this type contains protected field named “Adapter”. This field references an appropriate Dataset object that represents SQL table and allows access to its fields and queries. There is an example of creation such a field for “Clients” SQL table:
protected ClientsTableAdapter Adapter { get
{ if (_ClientAdapter == null) _ClientAdapter = new ClientsTableAdapter(); return _ClientAdapter; } }
Example of operating GetClientByClientID query: Auction.ClientsDataTable DataTable = new Auction.ClientsDataTable(); DataTable = Adapter.GetClientByClientID(ClientID);
All links in this diagram represent composition UML links between classes. 
Presentation layer contains 20 web pages. All of them use master page – "AuctionMaster" and .ssc file for visual matching of different pages and objects. There are three session fields that we use for most of pages:
There are few screen shots of described web pages in the User Guide appendix.
The vote algorithm allows user to vote for another user only if he purchased from him any product. After all purchases the buyer has a new availability for voting. The algorithm for feedbacks writing is the same like vote algorithm, but every user (buyer and seller all together) can write feedbacks with no limitation. 
|
n the second stage there were built classes for working with the database. The classes contain main methods, like "Get Data", "Insert Data", "Delete Data" and others, for access a database. The main component used in the process of building it was a "Data Set" object. This object supported by ASP.NET 2 and provides programmers a simple access to SQL server. So the building of a "Data Access Layer" was accomplished. Of course, the work done in this stage will be updated in the future but the main part has been already done.
he big picture