Upload
others
View
1
Download
0
Embed Size (px)
Citation preview
An-Najah National University
Computerized Information Systems department
Project Documentation Auction Website
((Reverse Auction))
Team names :-
Anas Attallah
Ahmad Mehiar
Mahmoud Al-khateeb
Instructor name :
Dr.Baker Abd-Alhaq
1
Table of contents
Content pageMission statement 3
Business requirements 4
Communication diagram 7
System requirements 11
Survey 13
Use case diagram 14
Interface sketches 15
System classes 20
Classes attributes and methods 21
Class diagram 22
Communication diagrams 23
Database schema 25
Glossary 26
2
Mission statement
People always go to auction and the person who present the
maximum bid win the product, but in our scope we present a new idea
for auction by make the person who present the minimal bid will be win
the product, customer must be pay %1 of product price for each time
provide his bid.
Purposes and aims of the website:
1) Increase the number of customers.
2) Sell the product in lowest price.
3) The challenges between customers.
4) Increase the amount of profit.
The organization primary stakeholders:
1) People who participate in auction.
2) Website staff.
3) Upper level management.
4) Employees.
5) Source of products (the person who want to sell his product) .
Responsibilities of the organization toward these stakeholders
1) Keep the privacy of customers data.
2) Keep the commitments to products resources.
Products and services offered :
1) Any tangible products.
2) Auction on products.
Business requirements
3
The actors:
1) Admins: Persons whose manage the website and add new product and specific
start date and end date of the auction session .
2) Customers: People who enters the website and participate on auction to buy the
product in minimal price and must have credit card.
3) Web site: The scope of the project that contain the auction.
Use cases:
U1: customer provide bid: customer enter the price that predict it the minimal prices.
U2: customer view product details : customer or non-member can view details about
product that in auction.
U3: non-member view auction: non-member can view auction and customers emails
that in hot minimal bids list and browse the web site.
U4: admin sign in: admin sign in to manage website.
U5: admin change password: replacement old password to new password.
U6: admin add product: admin add new product for auction and enter full details
about it.
U7: Customer get his password: customer get his password from website.
U8: Customers forget his password: customer return his password from website.
U9: Customer charge balance: customer insert card number in website and gets $20
balance for each one card.
4
Use case details :-
U1: customer provide bid:
1) Customer open the auction page.
2) Customer click provide bid button.
3) Customer insert his email and his bid price and the credit number.
4) Customer click send button.
5) The system validate the information that the customer enter.
6) Web page record the process in database .
U2: customer view product details :
1- Customer or non-member open the auction page.
2- Customer or non-member click view details button.
3- website open details page.
U3: non-member view auction
1- non-member open the auction page .
2- non-member view online auction.
U4: admin sign in:
1) Admin open the admin page.
2) Admin enter his username and password.
3) website check admin account
4) website open admin session
U5: admin change password
1- Admin click on change password from menu.
5
2- Admin fill old password and new password.
3- Admin click on change button.
4- Website check old password.
5- Website replace the password.
U6: Admin add product:
1- Admin click on add product button from admin home page.
2- Admin fill required fields.
3- Admin add product image.
4- Admin specific the start and the end date for auction.
5- Admin click add button.
6- Website record the information about the product in database.
U7: Customer get his password:
1- Customer click on get password.
2- Customer provides his email.
3- Customer gets his password.
U8: Customers forget his password:
1- Customer click on forget password.
2- Customer inserts his email.
3- Customer receive his password at his email.
U9: Customer charge balance :
1) Customer provide his email, password and card number.
2) Customer balance increase.
Communication diagram
6
U1: customer provide bid:
U2: customer view product details :
Auction page1:enter page
2:connect3:provide bid
6: record
Pay pal
7: bid provided
7
U3: non-member view auction
Auction page
1:enter page
2: click view details
3: open details
Auction page
1:enter page
2: present auction
8
U4: admin sign in:
U5: admin change password :
Admin page
1:enter
3:check account2:fill form
4:open admin session
9
U6: admin add product:
Admin page
1:enter
6:check old password
2:click change from menu
4:fill old &new password5:click change button
7:password change
Change page
Admin site1:enter
7:record information
2:click on add button 3:fill required field4:add product image
8:added sucssesfuly
5: specific start and the end date 6:click add button
10
U7: Customer get his password:
U8: Customers forget his password:
U8: Customers charge balance :
System requirements
11
The actors:
1) admin: an employee who manage the website.
2) Customers: people who participate in auction by presented their email and bid and
credit information.
3) visitor : people who visit our website and didn’t participate in auction.
System Use case :-
U1: browse website : customer enter the auction page.
U2: view product details: customer view product details.
U3: view auction details: customer view details about the current auction and how
many bids provided and the last ten minimum bids.
U4: login: admin open admin page and fill name, password.
U5: change password: admin change password that use for login.
U6: monitor: admin view customers data, winners and number of frequency bid.
U7: logoff: admin logoff from admin page.
U8: Customer charge balance: customer insert card number in website and gets $20
balance for each one card.
U9:Customer get password: customer get his password from website.
U10:Customer forget password: customer request his password from website then
receive it at his email.
System use case details:
12
U1: browse website (include U2, U3).
1) Customer open website
2) Customer choice auction from menu
3) Auction page present
4) Customer view auction
5) Include U2
6) Include U3
U4: log in:(extend by U5,U7)
1) admin enter admin page.
1) enter its name .
2) enter its pass.
- post condition:
a) if admin name or pass are is incorrect ,then alert to admin that there is wrong on his
info.
b) if admin name or pass are is correct , pass it to admin page index.
U5: monitor :(extend U4)
Precondition : admin must be log in successfully.
1) Press monitor button.
2) Go to monitor page.
3) View customers (emails and bids),winners , and number of frequency bids
U8: Customer charge balance :
3) Customer provide his email, password and card number.
4) Customer balance increase.
Survey
13
Customers browse the website (U1) ,customer get his password
(U9) ,customer buy cards and charge it on website (U8),customer go to
auction page and view online current auction , view product details (U2),
product image , and auction details (U3), if the customer didn’t participate in
auction then he is visitor (U4).
Admin open admin page and log in (U4), and can monitor auction (U6) ,
change password (U5) , and when end his job he must log off (U7).
Use case diagram
14
Interface sketches
15
Customer interface sketches
1) Customer services menu
2) Customer get his password ( first time )
3) Customer forget his password then he request it
4) Customer Charge his balance using card
16
5) Customer Check his balance
6) Customer provide his bid
17
7) Customer provide his feedbacks (optional for customer)
8) Customer contact us (optional for customer)
Admin interface sketches
18
1) Admin log in
2) Admin main menu
3) Admin privileges
4) Admin change his password
19
5) Admin create auction
6) Admin add cards number
7) Admin update auction session ( in special cases )
20
*** Design ***
System classes
- website
- customer
- admin
- auction card
- product
- auction
- winner
21
Classes attributes and methods
22
Class diagram
Communication diagrams
23
Admin make auction
Admin Admin page
account
auction1:Sign in
2: add product
3: specify auction
create auction
24
Customer participate in auction
website
account
auction1:Get password
2: charge balance
3: provide bid
Organize bids
Customer
25
Database schema
Admins (id (int), name varchar (50), password varchar (50)).
Cards (id (int), number varchar (15), used (int)).
Contact (id (int), name varchar(40) , phone( int) ,email varchar(30),comment (text)).
Customers (email varchar (100), bids (int)).
Feedback (id (int), question varchar (100)).
Num_bids (num (text)).
Products (id (int), p_name varchar(70) ,p_img (text) ,p_details (text ), market_price
(int) , min_bid (int) ,bid_price (int), start_date (date), end_date (date)).
Tops (bid (int), freq (int)).
Users (id (int), email varchar (100), pass varchar (15), balance (float)).
Winners (id (int), varchar(100) ,bid (int) ,date (date) ,time(time) , p_id (int) ,
num_bids (int)).
26
Glossary
- Bid (business object): instants of customer price that provide it.
- The product (business object): object available for auction.
- Customer (business actor, business object): a person who participate on
auction by presenting his bid.
- End date (business object) : The date when auction end .
- Start date (business object): The date when start new auction.
- Auction time: (business object): The time available for participate in auction.
- Hot minimal bids: The minimal ten bids.
- Winner (business object, business actor): The customer that provide minimal
bid when the auction is finish.
- Balance: The amount of money that customer own.
- Auction card: The card available in market, customer buy it and use it to
increase his balance in website to participate in auction.
27