0|Page
King Abdulaziz University Faculty of Computing & Information Technology Computer Science Department
Fall 2014 CS-351 Software Engineering Final Project
E-Commerce System
1|Page
Table Of Content : I.
Overview .......................................................................................................... 2-3 1.1 1.2 1.3 1.4
II.
Introduction ........................................................................................................... 2 Project objectives ................................................................................................. 2 Project organization.............................................................................................. 3 Project team .......................................................................................................... 3
Goals and Scope ................................................................................................ 4 2.2 Project Goals ......................................................................................................... 4 2.2 Project Scope ........................................................................................................ 4 2.2.1 Included ...................................................................................................................... 4 2.2.2 Excluded .................................................................................................................... 4
III.
Requirement Gathering & Analysis ............................................................. 5-13 3.1 3.2 3.3 3.4 3.5 3.6
IV.
Domain analysis ................................................................................................. 5,6 Requirements & its types ..................................................................................... 7 Techniques for gathering data ............................................................................. 8 Use Cases ......................................................................................................... 8-11 Difficulties & risk analysis in the domain .......................................................... 12 Use case diagram for given problem ................................................................. 13
Modeling & Structuring ............................................................................... 14-15
4.1 : Converting use cases to class diagram14 4.2 UML class diagram14 ...................................................................................... 14-15 4.2.1 Association ............................................................................................................... 14 4.2.2 Multiplicity................................................................................................................. 14 4.2.3 Generalization .......................................................................................................... 14 4.2.4 Object diagrams ....................................................................................................... 15
4.3 Difficulties & risk when creating class diagram16.............................................. 15
V.
Modeling, Interaction & Behavior17 .......................................................... 16-25 5.1 Interaction diagram ........................................................................................ 16-25 5.2.1 Sequence diagram .............................................................................................. 16,17 5.2.2 Collaboration diagram ..................................................................................... 17,1819 5.2.3 State diagram ............................................................................................. 19,20,2119 5.2.4 Activity diagram .................................................................................... 22,23,24,25 19
VI.
References……………………………………………………………………........... 26
2|Page
I. Overview 1.1 Introduction: E-Commerce System describe software systems which enable companies to do business over the Internet. They must be able to deal with a large number of visitors and transactions, and coordinate multiple stakeholders to deliver the products to the customers. Three common transaction patterns are Business-to-Consumer, Business-to-Business, and Consumer-to-Consumer.
Business-to-Consumer: sites, like amazon.com , souq.com , sukar.com and that’s what our project about also, that’s enable retail transactions where a company sells goods to an individual. That’s all done through an e-shop web site, which is sometimes referred to as a shopping cart solution. Business-to-Business: sites are meant for the exchange of products, services or information between multiple companies. They include company web pages, product supply and procurement exchanges, information sites, and brokerage services. Consumer-to-Consumer: site allows individuals to sell to other individuals. Sites can be run by an intermediary business, such as E-Bay , Haraj.com Marketplace, that’s done by consumers themselves.
1.2 Project objectives: -This project will helps people to increase their knowledge in electronic community . - the system might be used for many E-commerce project because it has good level of abstraction. -the system will reduce number of shops which have high leases . -by 20th of December the project will be ready.
3|Page
Continue : Overview 1.3 Project organization - First phase start with little overview about project overview which includes small introduction not completed and we will complete it after finishing whole project , then we did objectives and project team members. - Second phase is about Goals and Scope and it’s include the goals and scope of the project. - Third phase is Requirement Gathering & Analysis it’s include domain analysis , Requirements & its types , Techniques for gathering data , Use Cases, Difficulties & risk analysis in the domain , and complete use case for the whole system. - Fourth phase is just about UML Class diagram with Difficulties & risk we faced during build the class diagram. - Fifth phase is about Interaction diagrams(Sequence, Collaboration, State, Activity) - Sixth phase for References which helps us in project.
1.4 Project team and Work Distribution:
Project team:
ID
Name
E-mail
Mobile
1009543 1108778 1108798 1109826 1109845 1111221
Abdullah AlMagror Saeed AlMastoor Khalid AlZubaidi Abdallah Balubaid Hattan Gouth Abubkr Basim
[email protected] [email protected] [email protected] [email protected] [email protected] [email protected]
0561650600 0533612592 0542220030 0542010080 0505573103 0566722725
Work Distribution:
Member’s Name
Responsibility
Abdallah Balubaid - Leader Saeed AlMastoor Hattan Gouth Khalid AlZubaidi Abdullah AlMagror Abubkr Basim
Overview (1)+ Goals and Scope (2) Requirement Gathering & Analysis (3) Requirement Gathering & Analysis (3) Modeling & Structuring (4) Modeling & Structuring (4) Modeling Interaction & Behavior (5)
4|Page
II. Goals and Scope 2.2 Project Goals: - To increase interactivity and get immediate feedback on product prices, features, and quality etc. - To raise number of global markets , neither you nor the seller are restricted to your/their locality. - To increase speed , which means you'll locate what you want much quicker buy just internet connection. - 24-hour availability, so that the shop never closes. - To reduce the price , goods bought online tend to be cheaper than shops. - Immediacy , no going to the shops or waiting in queues. - Reduce overall marketing expenses. - Enhance customer service.
2.2 Project Scope - Included: - This project will provide the main functionalities of the web site shopping . - Create accounts for each and all customers . - Viewing products and search for goods. - Multiple payment methods . - Shipping the products to the customers.
- Excluded: This project will Not provide these functionalities but we can provide it over time. -Evaluation the products (rates) of each product. -Delivery service and shipment service . -Make notification system for new offers and new products .
5|Page
III. Requirement Gathering & Analysis 3.1 Domain analysis : A. Introduction : E-commerce(Business-to-Consumer) is an Online store where the customer can buy things online. There’re many seller who are registered in the system to sell their products .The products will be under control of the owner of the system if they are kept in their store(Account). The products will be kept in the company store in other words the sellers can keep their own items. The customer will be able to select one or products and add them to cart, They can buy them later if they wants. If the user is subscribed to newsletter special offers will be send to him via email. There are many paying method such as (PayPal, Visa , Gift Card or cash) , there will three kinds of offers, Special Season offers, Coupons offers or Special day offers. The system will use some companies to ship products to the customers. B. Glossary : The most terminology for this domain will be technical in nature, but there will also be terminology related to business , electronic activities , and business administration . C. General knowledge about the domain : The service should work probably any time anywhere . The client should have just internet connection for connecting to the system . this system is similar to Mobile-Commerce" is a term that describes online sales transactions that use wireless electronic devices such as hand-held computers, mobile phones or laptops. These wireless devices interact with computer networks that have the ability to conduct online merchandise purchases. Any type of cash exchange is referred to as an e-commerce transaction. Mobile e-commerce is just one of the many subsets of electronic commerce. This is the general knowledge about this domain. D. Customers and users : There’re many actors involved in the system " customers there are two types of customers – Buyer : the person who's want to search and buy the product by using the system, customers – Seller : this is the person who makes offer and provide the goods for all by using the system .also , technician :this person who's responsible for manage and updating the system. E. The environment the equipment which the system will use is host and domain form web-server and hosts providers and just technician to manage the system and database for customers and products.
6|Page F. Tasks and procedures currently performed The procedures that are currently used by seller and customers will help us decide the functions that will have to implement. Examples of procedures include: how decisions are made about which customer want to buy a product; how seller and buyer can decide upon a many products, especially when there're many products has same thing; what seller can do when there are not enough products for customers; how communications are established among the seller and the customers; and how records of each buying product are logged. The study of these procedures will help us to identify what aspects can be improved and how the system will become an asset to the customer. G. Competing software There’re many systems already on demands and others which is under-developed. So, we can add many things which will help us to earn more customers to our system cause it’s better than others. H. Similarities to other domains The main Idea of this system is how to save user’s time and make shopping easier for them also there’re many alternatives but here we will do easier and simplest system to serve their needs.
7|Page
3.2 Requirements & its types A. Functional Requirements Customer Functional Requirement : - personalized system access(login into system) - selecting one or more product/s . - selecting payment and shipment methods . Seller Functional Requirement: - personalized system access(login into system) - managing products (add, delete, update, make Offers) - provide payment method/s . - support and response for customer questions about specific product . System Functional Requirement: - Manage and organize products . - Help and support . - Check products if it’s available / not .
B. Non-Functional Requirements - Insurance for product and delivery guarantee . - Evaluation the products (rates) of each product. - Delivery service and shipment service . - Response time of the server . - Good and nice user interface design. - portability of the system.
8|Page
3.3 Techniques for gathering data : Brainstorming , Observations , Interviewing.
3.4 Use Cases : Actor ( Customer ) Use Case :
9|Page Actor( Seller ) Use Case :
10 | P a g e Actor ( System ) Use Case :
11 | P a g e Actor ( Admin ) Use Case :
12 | P a g e
3.5 Difficulties & risk analysis in the domain Customers : Difficulties: - His country not included in shipment area . - Pay only with credit card.
Risks: - Damage product. - Product quality. - Product may used before. - Shipment problem. Sellers: Difficulties: - System not refreshing product counter . Risks: - Product may damaged or lost by shipment company. - Customer doesn't take his product if he choose cash payment. System: Difficulties: - Encrypt connections. - Wrong product information. Risks: - Illegal product. - Seller doesn't have the product. - Server Down. - Authorization of admin . - Alternative server if there necessary maintenance (updates ).
13 | P a g e
3.6 Use case diagram for System Complete Use Case Diagram :
14 | P a g e
IV. Modeling & Structuring 4.1 Converting use cases to class diagram: 4.2 UML class diagram: 4.2.1 Association ≪Đõňē≫ 4.2.2 Multiplicity ≪Đõňē≫ 4.2.3 Generalization ≪Đõňē≫
15 | P a g e
16 | P a g e
4.2.4 Object diagram:
4.3 Difficulties & risk when creating class diagram It was there many problems such as deciding how many classes do we need also their attributes ,operations and generalization . But the big problem was that about make sure what we did is it perfect or not.
17 | P a g e
V. Modeling, Interaction & Behavior: 5.1 Interaction diagram 5.2.1 Sequence diagrams: - Customer Sequence Diagram:
18 | P a g e
- Seller Sequence Diagram:
5.2.2 Collaboration diagrams: - Customer Collaboration Diagram:
19 | P a g e
- Seller Collaboration Diagram:
20 | P a g e
5.2.3 State diagrams: - Customer State Diagram:
21 | P a g e
- Seller State Diagram:
22 | P a g e
23 | P a g e - System State Diagram:
24 | P a g e 5.2.4 Activity diagrams: - Customer Activity Diagram:
25 | P a g e
- Seller Activity Diagram:
26 | P a g e
- Administrator Activity Diagram:
27 | P a g e
- Registration Activity Diagram:
28 | P a g e
29 | P a g e
VI. References - Timothy C. Lightbridge and Robert Laganiere, Object-Oriented Software Engineering: Practical software development using UML and Java, 2nd Edition, McGraw Hill, 2005. - https://uwaterloo.ca/software-engineering/ - http://en.wikipedia.org/wiki/E-commerce/ - http://www.investopedia.com/terms/e/ecommerce.asp - http://ecommerce.about.com/ - http://www.webopedia.com/TERM/E/electronic_commerce.html - LAU domain analysis of e-commerce systems using feature based model.
