Professional Documents
Culture Documents
Amir
Amir
Submitted to the faculty of computing in partial fulfillment of the requirements for the
degree of Bachelor of Science in Information Technology
Group members
Name IDNo
The Project is our own and has not been presented for a degree in any other university and all the
sources of material used for the project have been duly acknowledged.
Amir Sultan ---------------------------------------------
Mohammed Yasin -----------------------------------------------
Habtam nega -----------------------------------------------
Faculty: Computing
This is to certify that I have read this project and that in my opinion it is fully adequate, in scope and
quality, as a project for the degree of Bachelor of Science.
------------------------------------- ---------------------------------------------
Name of Advisor Signature
1. Examiner 1
2. Examiner 2
It is approved that this project has been written in compliance with the formatting rules laid down by
the faculty.
i
Acknowledgment
First and foremost, we would like to thank almighty God that permits us to do and enable us to be
successful in our final year project and to be complete without any problem as his permission. We also
pass our sincerest thanks to our advisor Mekonnene Fantahun, who have given timely advice as well
as encouragement to completion of our project and his continuous support in every phase of this
project. Also, we do not need to miss to thanks again and again for Information Technology graduate
class student members who collaborated and helped us during the system development.
Finally, giving great thanks for our parents who are always with us in all our educational participations
and who give us great attention for our final project success with their financial and idea support.
Group members.
ii
List of acronyms
Notations:
DB: Database. A computerized record keeping system or a kind of electronic filing cabinet (a
collection of logically related data)
UML: Unified Modeling Language. Is a standard notation for the modeling of real-world objects as
a first step in developing an object-oriented design methodology.
PHP: Hypertext Processor (personal home page) is a widely-used open source general-purpose
scripting language that is especially suited for web development.
HTML: hypertext markup language.
HTTP: hypertext transfer protocol
CSS: cascade style sheet is language for describing the presentation of web pages including colors,
layout, and fonts.
JS: JavaScript: An object-oriented computer programming language commonly used to create
interactive effects within web browsers.
AJAX: Stands for asynchronous java script and xml. It is a new a technique for creating better
faster, and more interactive web application with the help of xml, Html, CSS and java script.
UC: Use case diagram. Use-cases are a scenario which identify the actors in an interaction and
which describe the interaction itself.
SD: Sequence diagram. Which show interactions between actors and the system and between system
components?
AD: Activity diagram.
CD: Class diagram: -visually represent classes and their inheritance relationships.
DD: Deployment diagram: - Deployment diagrams are used to visualize the topology of the
physical components of a system where the software components are deployed.
UI: User Interface
PK: primary key. fields that uniquely identify a record.
FK: foreign key. Are attributes contained within a database which uniquely identify another record,
but not the one within which they are contained.
Pdf: portable document format
JPEG: Joint Photographic Experts Group (technology which reduces the size of files that contain
images).
GIF: Graphic Interchange Format (a type of computer file that contains images and is used a lot on
the Internet).
iii
Symbols:
Boundary link
iv
List of Figures
FIGURE 1 USE CASE DIAGRAM.................................................................................................................................................... 10
FIGURE 2 USER INTERFACE PROTOTYPES....................................................................................................................................... 30
FIGURE 3: ACTIVITY DIAGRAM FOR LOGIN .................................................................................................................................... 31
FIGURE 4: ACTIVITY DIAGRAM FOR ORDER ITEM............................................................................................................................ 32
FIGURE 5: ACTIVITY DIAGRAM FOR UPDATE ITEM DETAIL ................................................................................................................ 33
FIGURE 6: ACTIVITY DIAGRAM FOR CREATE ACCOUNT .................................................................................................................... 34
FIGURE 7: ACTIVITY DIAGRAM FOR REGISTER ITEM ........................................................................................................................ 35
FIGURE 8: SEQUENCE DIAGRAM FOR LOGIN .................................................................................................................................. 36
FIGURE 9: SEQUENCE DIAGRAM FOR ORDER ITEM ......................................................................................................................... 37
FIGURE 10: SEQUENCE DIAGRAM FOR ADD ADVERTISEMENT ............................................................................................ 38
FIGURE 11: SEQUENCE DIAGRAM FOR REGISTER ITEM .................................................................................................................... 39
FIGURE 12: SEQUENCE DIAGRAM FOR DELETE ITEM ....................................................................................................................... 40
FIGURE 13: SEQUENCE DIAGRAM FOR UPDATE ITEM DETAIL ........................................................................................................... 41
FIGURE 14: DEPLOYMENT DIAGRAM ............................................................................................................................................ 44
FIGURE 15: DESIGN CLASS MODEL .............................................................................................................................................. 45
FIGURE 16: PERSISTENT MODEL ................................................................................................................................................. 52
FIGURE 17: UI FOR LOG IN ........................................................................................................................................................ 53
FIGURE 18: UI FOR CREATE ACCOUNT ......................................................................................................................................... 54
FIGURE 19: UI FOR ADD ITEM ................................................................................................................................................... 55
FIGURE 20: UI FOR UPDATE CART............................................................................................................................................... 56
FIGURE 21: UI FOR UPDATE ACCOUNT ........................................................................................................................................ 56
v
List of table
TABLE 1 USE CASE DESCRIPTION FOR MANAGE CART ..................................................................................................................... 11
TABLE 2 USE CASE DESCRIPTION FOR VIEW ITEMS FOR SALE ............................................................................................................. 12
TABLE 3 USE CASE VIEW ORDER STATUS ....................................................................................................................................... 12
TABLE 4 USE CASE DESCRIPTION FOR PAY FOR ITEM ....................................................................................................................... 13
TABLE 5 USE CASE DESCRIPTION FOR ORDER ITEM......................................................................................................................... 14
TABLE 6 USE CASE DESCRIPTION FOR CREATE ACCOUNT .................................................................................................................. 15
TABLE 7 USE CASE DESCRIPTION FOR MANAGE ACCOUNT ................................................................................................................ 16
TABLE 8 USE CASE DESCRIPTION FOR LOGIN ................................................................................................................................. 17
TABLE 9 USE CASE DESCRIPTION FOR VIEW REPORT ....................................................................................................................... 18
TABLE 10 USE CASE DESCRIPTION FOR REGISTER ITEM ................................................................................................................... 19
TABLE 11 USE CASE DESCRIPTION FOR DELETE ITEM ...................................................................................................................... 20
TABLE 12 USE CASE DESCRIPTION FOR UPDATE ITEM DETAIL ........................................................................................................... 21
TABLE 13 USE CASE DESCRIPTION FOR VIEW COMMENT ................................................................................................................. 22
TABLE 14 USE CASE DESCRIPTION FOR RECEIVE ORDER ................................................................................................................... 23
TABLE 15 USE CASE DESCRIPTION FOR ADD ADVERTISEMENT .......................................................................................................... 24
TABLE 16 USE CASE DESCRIPTION FOR PAYMENT VERIFICATION ........................................................................................................ 25
TABLE 17 USE CASE DESCRIPTION FOR GENERATE RECEIPT .............................................................................................................. 26
TABLE 18 USE CASE DESCRIPTION FOR LOGOUT ............................................................................................................................ 27
TABLE 19 USE CASE DESCRIPTION FOR SEARCH ITEMS FOR SALE ....................................................................................................... 28
TABLE 20 USE CASE DESCRIPTION FOR UPDATE SHIPPING INFO ........................................................................................................ 29
vi
Contents
Declaration...................................................................................................................... i
Acknowledgment ...........................................................................................................ii
List of acronyms .......................................................................................................... iii
List of Figures ................................................................................................................ v
List of table ................................................................................................................... vi
Abstract .......................................................................................................................... 1
Chapter One: Introduction .......................................................................................... 2
1.1. Introduction ..........................................................................................................................................2
1.1.1. Background ......................................................................................................................................2
1.1.2. Vision ...............................................................................................................................................2
1.1.3. Mission .............................................................................................................................................2
1.1.4. Existing System Study .....................................................................................................................3
1.2. Objectives ............................................................................................................................................3
1.2.1. General Objective ............................................................................................................................3
1.2.2. Specific Objective ............................................................................................................................3
1.3. Statement of the problem .....................................................................................................................3
1.4. Beneficiaries of the project ..................................................................................................................4
1.5. Limitations of the project .....................................................................................................................4
1.6. Scope of the project .............................................................................................................................4
1.7. Methodology ........................................................................................................................................5
1.7.1. Requirement gathering methods ......................................................................................................5
1.7.2. Analysis and design Methodology ...................................................................................................5
1.7.3. Implementation Methodology ..........................................................................................................6
vii
2.3.1.3. Use Case documentation ........................................................................................................... 11
2.3.2. User Interface prototype................................................................................................................ 30
2.3.3. Activity Diagram........................................................................................................................... 31
2.3.4. Sequence diagram ......................................................................................................................... 36
2.4. Nonfunctional requirement ............................................................................................................... 42
2.5. System Requirement ......................................................................................................................... 43
2.5.1. Hardware requirements ................................................................................................................. 43
2.5.2. Software requirements .................................................................................................................. 43
viii
Abstract
This project is a part of the industrial project for the fulfillment of bachelor degree in Information
Technology. The project focuses on developing web based application for Smart electronics shopping
center system. It will provide simple and efficient way of E-commerce by display and get electronics
information for seller and buyer. Customers who are using the system must create their own account to
buy any electronic device that exists in the shop. It would make searching, viewing and selection of a
product easily. It contains sophisticated search methods for users to search item. The user can view the
complete detail of each product. The system also provides user can add a product to the shopping cart.
The main emphasis lies in providing customer to order item in easy way by using add to cart or select
one item. The system generate receipt for the customer when successfully order item. The Admin and
sales person have many privileges in the system. Such as delete, update item detail, view report and
view order. This project is developed by using HTML5, CSS, JavaScript, AJAX, and PHP. This
document contains introduction, system feature, methodology and tools like JEdit and Visual Paradigm,
data sources like site introspection and interview, and for design methodology we use object-oriented.
For analysis model, we use sequence and activity diagram. For system design we include deployment
diagram, class diagram, user interface design, data structure design, and algorithm design for the project
that is going to be developed.
1
Chapter One: Introduction
1.1. Introduction
Smart Electronics shopping center is the system that involves selling and buying transaction process.
Such transaction is concentrate on electronics materials like cameras, tablets, smart mobile phones,
desktop computers, laptop, external hard disk, cooler, printer, scanner, Xerox, fax machine, different
types of cables and other kinds of electronics material.
Smart Electronics shopping center is one of the well-known electronic shop in Bahir Dar city that highly
used by customers. So, the business has been profitable and has worked out well for the Admin. The
growth of electronic sales has been very good and the store has been well received in the community.
1.1.1. Background
Smart Electronics Shop center was founded in Bahir Dar city. It is located to the right of Bahir Dar city
bus station. It established in 2015 to serve the needs of local people in Bahir Dar city, and has served in
this area to present time. Besides give services for customers and company nearest to our system. It is
staffed by 3 employees. The shop is funded by Mr.Tsgye T/ Brhan. It is recognizing a responsibility to
improve technology development, and job marketability. Toward that goal, it offers various electronics
goods. The system has been computers recently added to help with store item name, there cost and
printing bill for customer.
1.1.2. Vision
We intend to provide the customers with the best online shopping experience from beginning to end,
with a smart searchable website, clear and secure payment methods, fast, and quality delivery.
1.1.3. Mission
To provide fast, efficient, effective and accurate information to anyone who want to buy electronics
device. To moderate the cost, serve the needs of the employers, the labor movement and the
community. It also guarantees that all its customers will be given utmost respect, love, attention and
service.
2
1.1.4. Existing System Study
The existing system of electronic shopping mechanism is manual. Customers when they need to buy
any electronics device they must come to the shop physically. And he/she must come with cash birr or
check note. Transaction money transfer hand by hand.
The shop open at 2:00 o’clock in local time and closed in 12:00 o’clock local time and it’s not opened
Sunday. The price of the good is made by negotiation.
1.2. Objectives
➢ It gives the service only for 10 hour in a day and 6 days in week.
➢ May be the money stole easily by robbery’s
➢ There is no full information about customers
➢ There are no updatable advertisements.
➢ Its take large time to processes transaction.
➢ There is no written cost description on items for customers.
➢ Sometimes customers may not get they need
3
1.4. Beneficiaries of the project
In development of this system different customers and stakeholders are beneficiary. Customers
fulfill what they need, reduce cost and time of hiring and secure transaction. Stakeholders
decrease work load, reliable and honest, describe stable cost of material and it attract the
customers.
• Online transaction: - today in our country Ethiopia doesn’t allow online payment in
worldwide systems like PayPal.
• Because of this problem, we don’t sale goods in online. The transaction takes hand by
hand or manually.
The scope of the project is defined in terms of the tasks that the system accomplishes. Thus, the
scope of the project is
➢ Not give permission of transaction for customers who have no account number.
➢ Not give permission of transaction for customers who have insufficient balance.
➢ Develop online selling and buying transaction for smart Electronics Shop center in Bahir
Dar.
➢ The company gives shipping service for customer who lives around Bahir Dar city.
➢ Generate advertisement for items which price is discount and when new item is registered.
➢ Doesn’t advertise for other companies.
4
1.7. Methodology
We have applied or used two types of data gathering methodologies introspection and interview. To
know about the existing shopping system.
Introspection
This method has been the primary base for this project. Therefore, using the current or background
knowledge of the group, the group is able to identify and list out the common functionalities and
requirements for the project. This helps the group to proceed to the next level. Furthermore, it had been
a bridge or cause for other methodology to conduct them in proper method.
Interview
As we know there are two types of interviewing methodologies which are open and closed, we use open
interview methodologies to get information about the existing system. We ask different questions to the
administrator and shop keeper.
We will use object oriented system development methodologies because of many reasons, some of the
reasons are listed below.
✓ This method is well known by the group members and the group members uses for different
course projects.
✓ Any system made by this method are easy to maintain, therefore it reduces maintenance burden.
✓ It is easy in terms of flexibility.
✓ Ease of understanding object-oriented models due to a consistent underlying representation
throughout the development process.
✓ Easy of modification and extensibility of object-oriented models.
❖ Tools to be used for analysis and design.
✓ Visual paradigm: - this software tool is used for designing different architectural figures, for
example, use case diagram, activity diagram, sequence diagram, class diagram, and the likes.
✓ Microsoft word 2016: - this software application is used to prepare the document of this
project.
✓ Adobe Photoshop: - used for editing different graphical pictures.
5
1.7.3. Implementation Methodology
The system is designed for web based system. So, an interactive web based system commonly needs
the following tools.
✓ Web server software: - apache web server
✓ Server side programming language: - PHP
✓ Client side programming language: - HTML5, CSS, JavaScript, AJAX
✓ Database system: - MySQL database
✓ JEdit: - This software application used for editing the coding part of this project.
There are many reasons why we select PHP for server side programming and MYSQL for the database
some of the reasons are described as follows.
From many of scripting languages PHP is powerful, easy to learn, cross platform, free, and PHP is
faster. There are also so many reasons to choose MYSQL database some of the reasons are it is quick
and powerful, handles large database, and it is free.
6
Chapter Two: System features
This chapter of the project document which provides a system features of the project. This chapter
contains and describes about User requirement, Functional requirement, and Non-Functional
requirement, use case diagram, and use case description, Analysis Model (Activity diagram and
Sequence Diagram).
Online shopping system is providing the online shopping facility available for everyone. Any type
of the product will be available for the customer, and it can be easily purchased faster. Online
shopping system concentrate more on user friendly interface and promotes users to purchase faster
and easier. There is a facility available to do online purchase. Shop online have registration facility.
The registration process is faster and easier. In the user interface of shop online there will be
accomplished with options to find new product available and most purchased and customer satisfied
products. Customer can avail this facility and buy the product faster. All products in the website will
be highlighted with image of the product. By click on Buy now button it will take you to directly to
the buy page, from where customer can have purchased easily. Shop online is provided with
customer support page. Using this page any customer can get the assistance from the available
customer support executive online. There we have support over phone and email. Customer can use
this facility any time.
.
7
2.3. Requirement Analysis
Functional requirements focus on the intended behavior of the system or what the system will do.
Accordingly, the tasks that the smart electronics shopping center will do are listed as follows:
8
✓ The system shall have added advertisement that display in the website.
✓ The system shall have added to cart transaction.
✓ The system shall have update form.
✓ The system shall have insert form.
✓ The system shall have delete form.
9
2.3.1.2. System Use case
Figure 1 Use case Diagram
Order Item
Custmer
Pay for items
Manage
account Create account View order
status
Logout
Uses
Login
View report
Register item
Admin Update item
detail Update order
status Sale person
Delete item
Add
View comment advertisment
Recive order
10
2.3.1.3. Use Case documentation
11
Table 2 Use Case Description for view items for sale
Actor Customer
Description The customer view items posted in the site
Precondition ✓ Search the website in the internet.
Post condition The customer may order the item that have seen in the site
Basic course of action User action System response
1. The customer search the 2. The system displays the
site. items.
3.view items in site.
4. user end
12
Table 4 Use Case Description for pay for item
Alternative course of action 3&6. The system displays an error message when not input
correct.
6. The system will give a chance to re-enter the password.
13
Table 5 Use Case Description for Order Item
Use case number UC-5
Use case Name Order item
Actor Customer
Related use case Includes: generate receipt.
Description The customer orders the item, when he/she wants to buy the
item.
Precondition ✓ Customer selects the item.
✓ The customer click on buy button.
✓ Log in
Post condition The system generate report.
Basic course of action User action System response
1. The customer select item. 3. The system displays the order
2.Click on buy button form.
4. Fill the order form with 6. The system display receipt
the valid account number when customer enter and send
and password. correct account and sufficient
5. Click order button. balance.
7. System end.
Alternative course of action Alternetive1
1. The customer selects more than one item by use add to cart.
Alternetive2
6. The system will display an error message when the
customer enters invalid account or have not sufficient balance.
14
Table 6 Use Case Description for create account
15
Table 7 Use Case Description for manage account
16
Table 8 Use Case Description for Login
17
Table 9 Use Case Description for View Report
18
Table 10 Use Case Description for Register Item
Alternative course of action 5. The system will display error message when items not register
successfully.
19
Table 11 Use Case Description for Delete Item
20
Table 12 Use Case Description for Update Item Detail
21
Table 13 Use Case Description for View Comment
22
Table 14 Use Case Description for receive order
Use case number UC-14
Use case name receive order
Actor Sales person
Description The sales person receives the order if get message from the
system.
Precondition ✓ Log in
✓ The sales person get message from system.
Post condition The sales person knows which item is ordered.
Basic course of action User action System response
23
Table 15 Use Case Description for Add Advertisement
Use case number UC-15
Use case name Add advertisement
Actor Sales person
Description The sales person adds advertisement to system when the price
of item discount or new items entered to our system.
Precondition ✓ Price of item discount.
✓ New items entered to our system.
Post condition Attract the customer.
Provide information.
Basic course of action User action System response
Alternative course action 1. The sales person get discount of price on item.
24
Table 16 Use Case Description for payment verification
Alternative course of 4. System display error message to customer when get negative
action response from bank.
25
Table 17 Use Case Description for Generate Receipt
Alternative course of 2.System display error message to customer when get negative
action response from bank.
26
Table 18 Use Case Description for Logout
27
Table 19 Use Case Description for Search Items for sale
28
Table 20 Use Case Description for Update shipping info
29
2.3.2. User Interface prototype
Figure 2 User Interface prototypes
URL
Home
page
order Rigester
Item Update Item
Detail
Add to Cart
View Order
detail View alart
Edit message
Cart
view status Delete
Pay Item
update status
View Order remove
Detail sale person
verify
Update payment
account Read
Comment
Read
view status
Comment Create Account
for Sale person
write
Comment
Create Account
30
2.3.3. Activity Diagram.
Define graphical representations of workflows of stepwise activities and actions with support for
choice, iteration and concurrency. In the UML, activity diagrams can be used to describe the
business and operational step-by-step workflows of components in a system.
Incorrect
Correct
31
Figure 4: Activity Diagram for Order Item
Search item
Login
new registration
Incorrect
Incorrect
Correct
Generat rceipt
32
Figure 5: Activity Diagram for Update Item Detail
Login in as admin
Incorrect
Correct
Search item
Not available
Avalable
Click update
Incorrect
Correct
33
Figure 6: Activity Diagram for Create Account
Click register
Incorrect
Correct
34
Figure 7: Activity Diagram for Register Item
Correct
35
2.3.4. Sequence diagram
Define a Unified Modeling Language (UML) is a kind of interaction diagram that shows how
processes operate with one another and in what order. It shows object interactions arranged in time
sequence.
Click()
Create
Open()
Fill()
Submit()
[Check]
Validate()
[Ifnot valid]
Validated()
Open()
Display()
36
Figure 9: Sequence Diagram for Order Item
Select()
Buy now()
Submit
Create()
Fill()
Order()
Validate()
[Check]
[Ifnot valid]
Validate()
[Check]
Display error message() [If not valid]
Validated
Validated
Create
Display receipt()
37
Figure 10: Sequence Diagram For Add Advertisement
Click()
Create
Open()
Fill()
Submit()
Submited
Create()
Display()
38
Figure 11: Sequence Diagram for Register Item
Click()
Create()
Open()
Fill()
Register()
[Check]
[Ifnot valid]
Display error message
Validated()
Registered()
39
Figure 12: Sequence Diagram for Delete Item
Get()
Click ok button()
Display()
40
Figure 13: Sequence Diagram for Update Item Detail
Click()
Create()
Open()
Display
Edit()
Submit()
[Check]
Validated()
Create()
Display()
41
2.4. Nonfunctional requirement
Nonfunctional requirement is a requirement that specifies criteria that can be used to judge the operation
of a system, rather than specific behaviors. The plan for implementing nonfunctional requirements is
detailed in the system architecture. Systems must exhibit software quality attributes, such as:
Robustness
The system will face different interactions from different users. Therefore; each interaction may bring
an invalid input to the system. These invalid inputs may crash the system. The system will be
implemented to capture any invalid data with Error Handling Mechanism. Therefore; any invalid data
will be thrown and notified to the user as soon as possible.
Usability
• The interface should contain prompts and help to avoid making mistakes
• The product should be used by people with no training.
Performance
• The system shall display errors message that guide user to handle it.
Modifiability
• The system is can easily modify or change the given information.
Security
✓ The system gives appropriate output based on the expected lists of inputs.
✓ The system operates the shortest time rate within the least amount of resources.
42
2.5. System Requirement
43
Chapter 3: System Design
3.1. Architectural Design
Deployment diagrams are used to visualize the topology of the physical components of a system where
the software components are deployed. Deployment diagrams are used to describe the static
deployment view of a system. Deployment diagrams consist of nodes and their relationships.
php odbo
{user:
html
owner
notepad++
sales person
customer}
44
3.2. Detail Design
Figure 15: Design class model
User
#id: String
#fName: String
Account
#lName: String
#dob: Date -userName:String
#sex: Char -password:S tring
#phoneNo: String
#email: String
+login(userName:String,pass:String):void
+logout():void
create_account
1
1
1 Sale_Person
Admin
1 -salary:flaot
+registerItem():String Customer +viewComment():String 1
+viewOrder():String +deleteItem(itemId:int):void
1 -houseNo:int +deleteGroup(groupId:int):void
+viewAlartMessage():String
-kebele:int +updateDetail():String
+viewComment():String 1
1 +orderItem():String +createAccount():String
1 +searchItem(name:String):String +viewReport():String
search +createAccount():String
create 1
1 manage 0..1
Register
0..* ShoppingCart
Order -cartID:int
1
-itemID:int 1
0..* 1..* 0..* -orderID:int -quantity:Int
-orderCreateDate:Date +addItem():void
ItemsGroup -shippendDate:Date +deleteCart():void
-buyerName:String +updateQuantity():String
-ItemgroupID: int -sellerName:String +viewCartDetail():String
-ItemgroupName: String -itemName:String +checkOut():String
-ItemgroupDetail: String -status:String +cartUnitPrice():Double
+getAllItems():String -shipTo_place:String +cartTotalPrice():Double
1 +placeOrder():void 1
1..* +sendAccouNo():String 0..1
+sendBalance():Double
Cart 1
Item 1 1 1
1..* -name:String
-itemID: int
1 -itemID:int
-itemName: string
-quantity:int
-itemBrand: string
Shipping_Info -unitCost:Double
-price: Double
-subTotal:Double
-quantity: int 1
-shippingID: int
-manDate: Date
-shippingType: string Order_detail
-manCompany: string
-shippingCost: Double
+desplayItem():String -shippingRegion: string read
-orderID:int
read +getItemDetail():String
-itemId:int
+updateShippInfo():String
1..* 0..* -itemName:String
-quantity:int
Update -unitCost:Double
-subTotal:Double
+calcuPrice():Double
0..*
add
veiw
0..* 0..*
Comment
-custName:String
-commDate:Date
-discription:String
+display():String
45
3.2.1. Logic model
Algorithm design for Login
Login ()
Begin
Connect to database
If (valid)
Else
End
Register user ()
Begin
Validate input
Connect to Database
If (valid)
Insert to Database;
46
Display success massage;
Else
End
Add Item ()
Begin
Validate input
Connect to database
If (valid)
Insert to database
Else
End
47
Algorithm design for Search
Search ()
Begin
Validate to database
If (valid)
Else
End
Begin
Connect to database
48
Update item table;
Validate;
If (Valid)
Insert to database;
Else
End
Edit Account ()
Begin
Change information;
Validate;
If (valid)
Insert to database;
Else
End
49
Algorithm design for order Item
Order Item ()
Begin
If (use cart)
Edit cart
Validate;
If (valid)
If (sufficient balance)
Else
50
Display Error message;
End
Delete item ()
Begin
Connect database
Delete item
If (yes)
Delete item
End
51
Figure 16: Persistent model
User
create_account
1
1
1 Sale_Person
1 Customer Admin
1 -salPerID:varchar(15){PK,FK} -custID:int{PK,FK}
-salary:float -adminID:varchar(15){PK,FK}
-houseNo:int 1
-kebele:int 1
1
1
1
1
create
search
0..* ShoppingCart
Order -cartID:int{PK}
0..* 1..* 0..* 1 1
-itemID:int{FK}
-orderID:int{PK} -custID:int{FK}
ItemsGroup
-custID:int{FK} -quantity:int
-ItemgroupID: int{PK} -orderCreateDate:Date
1
-ItemgroupName: varchar(50) -shippendDate:Date
-ItemgroupDetail: varchar(100) -buyerName:varchar(40)
-salperID: varchar(15) {FK} -sellerName:varchar(40)
-custID: varchar(15){FK} -itemName:varchar(30){FK} 0..1
-admiID: varchar(15){FK} -status:varchar(15)
-shippingID:int{FK} Cart
1 -shipTo_place:varchar(100)
1..* -cartID:int{PK,FK}
1 1 1 -name:varchar(30)
Item -ItemID:int{FK} 1
1..* -quantity:int
-itemID: int{PK} -unitCost:Double
-itemgroupID: int{FK} 1
-subTotal:Double
-orderID: int{FK}
Shipping_Info 1
-itemName: varchar(30)
-itemBrand: varchar(30) Order_detail
-shippingID: int{PK}
-price: Double read
-salperID: varchar{FK} -orderID:int(PK,FK)
read -quantity: int
-shippingType: varchar(25) -itemId:int(FK)
-manDate: Date
-shippingCost: Double -salPerID:int(FK)
-manCompany: varchar(30)
-shippingRegion: varchar(50) -itemName:varchar(30)
-cartID: int{FK}
0..* -quantity:int
1..* -unitCost:Double
Update -subTotal:Double
add
0..*
veiw
Comment
0..* 0..*
-custID:varchar(15){PK,FK}
-commDate:Date
-discription:varchar(100)
-salperID:varchar(15){FK}
-adminID:varchar(15){FK}
52
3.3. User Interface Design
Figure 17: UI for log in
53
Figure 18: UI for Create Account
54
Figure 19: UI for Add Item
55
Figure 20: UI for Update cart
56
4. References
1. Sawyer, I. a. Requirement Engineering a good Practice. The Object Primer 2nd Edition.
2. PAGINAS.ISPGAYA.PT. (2016, 12 14). Persistence model. Retrieved from PAGINAS.ISPGAYA.PT:
http://paginas.ispgaya.pt/~msantos/2b-SI1- _UML_(Persistence_Data_Modeling).pdf
3. Mr. Tsegaye T/ Brhan (2016, December 03). About existing system (Admin. Interview)
4. Official website of Sheger, Ethiopia (http://www.Sheger.com) Retrieved on (2016, November 17)
5. Official website of Amazon (http://www.Amazon.com) Retrieved on (2016, November 10)
57
5. Appendices
1. Where items are stored?
2. How many employees in the shop?
3. What is the responsibility of employees?
4. Who is responsible for importing items?
5. How much times the system work per day?
6. How many customers serve the system per day?
7. How many items sold per day?
58