L/O/G/O

Project Electronic-Commerce

arafat m elmadhoun

120080147

Software Engineering

Modeling Software

Supervision by:

Eng: Mohamed Timraz

Electronic-Commerce

Class diagram

Activity Diagram

Sequence Diagrams

Functional Requirements

Non Functional Requirements

Use Case

Use case Details

Contents of the project

AbstractionAbstraction

Actore list

Glossary

Context digram

Abstraction Electronic shopping system is a system designed to the benefit of two people at the same time a

resource is the primary beneficiary and the beneficiary is the second customer, who is from purchase System is a system designed to display the goods provided by the supplier displayed in an organized

and uncluttered in groups and will offer on-site and display the price of each commodity Then the system allows the user to review the goods and the search for items within the same

system to gain access to the requested item and find out the details and purchase from the supplier through the Internet

In terms of the purchase using a credit card to purchase and here are the screening process by the system to communicate with the Bank in support of your purchase by credit card

Is to make sure that the amount requested is in a credit card or not and that was there is the procurement process and not the procurement process is not

Then after the purchase process is to confirm the order is delivered to the user through the address that was placed in the procurement process

And are also possible and send Bills sent electronically or sent also to the same address, which was placed in the procurement process

After the delivery process is also to confirm the delivery of the goods to the customer and also the process is to confirm transfer of funds from the account of a customer to supplier account via the mediator who is supportive of the Bank's procurement process

Also in the procurement process are checked by the Bank in the procurement process and ensure that the procurement process, which is the same as the credit card and do Bajrat protection for bank account

Actors list

Customer: the person is the beneficiary of a system with limited powers only allow him to take advantage of the

system which is ranked by the Director not less than the basic operations performed by the resource manager of the system

Supplier: is the person responsible for the system and with full powers in most cases he will be ranked higher

than where the customer in control of all operations carried out by the customer

Glossaryuse case list

Added: is the function of the harness and added a function that are common in most of the time between normal user and resource system where each person gets to this job

As a function of his powers, but limited in its operations

Delete: function is also be common in most cases, between the user and the Director, where each of them the function of the deletion in the system, but limited powers

Each of them where the user has limited powers to him only in terms of deletion and the supplier has the competence to be open to all in the function of deletion

Edit: is the function of the amendment or update and also be the user and the supplier have all his powers are limited in this function where the user modifies only for him and the operations carried out by only But the resource is adjusted for all the powers open to him

Login: is the function that responds to each of the average user to do the resource system in order to allow them either to take advantage of the system or control system by the supplier

Glossary Search: the function of which benefit the average user may be used purely for a little bit of a given

within the system And also used by supplier and manager of the system is purely for a particular element within the

system facilitates the process of reaching a speed of something desired or intended

Buy: the main thing is to take advantage of the user system is the final process undertaken by any user within the system that provides online shopping service

The purchase of the product even if Cash Payment is also to be considered Bmtabh purchase of the product and book it

Logout: the process out of the system is a joint operation between the manager and the average user, where both sides of the metal Login enthusiastically lobby system also logs out of the system

Confirm: Confirm is the process done by the supplier or system administrator on the purchase by the customer or the shipment of goods by the customer

Closure: the process of shutting down any system that was until the completion of all tasks to which the system for it

Context diagram.

Functional RequirementsSystem functions…..

System facilitates the process of shopping electronically, where displays of goods to the customer in electronic

System works on display all product prices in a way be successful with product prices in the store support system for electronic shopping

System makes it easier to buy goods from places may not be from the same country and also in producing, selling a home

System works to facilitate the process of deducting money through the bank in support of the procurement process Bosta credit card

System works to facilitate the purchase of products without the effort and instead go to the store that has the item you want to Cheriha

System works to facilitate the presentation of the same supplier's products to customers via the Internet while everyone uses at the present time the internet as a key in his life

Functional Requirements System works on a good marketing for the products of the supplier to become ready to compete in

global markets and international

System works on speed and safety of the delivery of funds in the supplier of the products by paying by credit card

System is a good link between the supplier and the customer, even if every person from the State or from another continent also

System works on marketing the products of the state not only in the country with but on a global scale, which makes the process of marketing products enter international competition, not only international

Non FunctionalPerformance Requirements The system shall process events at a reasonable speed

Usability Requirements The system should be usable by basically-familiar computer users . The system shall be easily recovered. Interface Requirements The interface shall provide recognizable functionality. Interface text should be understandable, and convey appropriate meaning.

Resource Requirements The delivery of the system shall be on time.

Maintainability Requirements The system shall be easy to maintain by admin. The software should be written in a way that is moderately extensible.   

Non FunctionalSecurity Requirements The system should thwart all but the most determined efforts to compromise communications privacy.  Safety Requirements The system shall be safe to use by users. Legal Requirements System shall meet the industry standard.  Installation Requirements System shall be easy to install by the admin.

Development Requirements The design and implementation process shall be well controlled. The project shall be well managed.

Use Case

Use Case

Use case DetailsCustomer ....

1)Use Case 1 : view Catalog Requirements:

Purpose: A customer can browse through the different genres, categories andcan also view the details of the products such as the description, pricelisting etc. Depending upon the genre/category selected, the contents of the tableare accessed using a select query.

Input: The User will select one of the genre and its category.

Output: The system will display product list and information of the selectedgenre and/or category. The product list will be displayed on product.aspx pageand 6 products will be displayed on each page and the rest (if any) will be on thenext page. This will be executed using the “pagination” property i.e. there will alink named “Previous” and “Next” on the bottom of every product.aspx page toenable the customers to go to the next and previous pages to view products. Thecurrent page of the customer will also be displayed on every page.

Use case DetailsCustomer ....

2) Use Case 2 : Perform Product Search Requirements:

Purpose: The purpose of this part of the application is to enable the customer tofind the available product of his choice without browsingthe entire catalog.

Input: The customer will hit the Search button on the top of every page. Thiswill redirect the user to Search.aspx Web page where he/she will have theoptions to enter name of the productrange of his/her choice. Also, the user can enter any text in the search text boxand can choose for the system to search for all the words he entered and hit the“Search” button. This will redirect the user to the page which will display all thematched items; otherwise an appropriate message will be displayed.

Output: If the user inputs are not valid (i.e. the user did not enter any of therequired options), an appropriate error message will be displayed. If the inputsare valid, a message will be displayed affirming the user’s choices along withthe appropriate product(s) information for the particular search. If there are nomatches, the system will display an appropriate message.

Use case Details3) Use Case 3 : Manage Account Requirements:

• System Login:

Purpose: This is implemented to enable user authentication. A valid useraccount must be used for an existing customer.

Input: The customer can login to the e-Commerce shopping system byentering his user name and password.

Output: The system will verify that the login name matches the loginpassword. If the user name or password is invalid, the appropriate error20message will be indicated and the user will be requested to re-enter username and password. If the user inputs are valid, the main page will bedisplayed.

Use case Details• System Register:

Purpose: This is implemented to enable a new user authentication. A validuser account must be used for an existing customer or a new customer canregister.

Input: If the customer is a new user, he can request to register with thesystem.

Output: The system displays a registration page and asks the customer tochoose a user name, password and enter a valid email id, security questionand answer.

Use case Details

4) Use Case 4 : Manage Profile Requirements:

Purpose: User can edit, update and save his personal information. Pre Condition: The user must be logged into his account to Update PersonalInformation. The user inputs will be saved to the database.

Input: The customer can request to update their customer info.The user will enter personal information such as: First name and last name Street address city, state, zip code, country Telephone Email Credit card information Billing and Shipping addresses

After entering all the information the user must click the update/save button. Output: The customer updates the customer information and the systemwill store the updated customer info in the system database.

Use case Details5) Use Case 5: Place Order Requirements:

• Add to cart: Purpose: This is implemented to add products to shopping cart whilesearching or browsing catalog. Pre Condition: The user must be logged in to add a product to the cart. Theproduct will be added to a shopping cart table in the database using insertcommand.

Input: When the customer finds the products he wants, he adds them to theshopping cart by clicking on the “Add to Cart” button.

Output: The product will be added to the shopping cart and the system willstore and keep track the information of the products that have been added intoshopping cart.

Use case Details• View Cart Details:

Purpose: This is to view contents of the shopping cart while searching orbrowsing the catalog. The contents of the shopping cart table will be displayedby using a select query. Pre Condition: The user must be logged in and must have atleast one Cartitem to view details of the shopping cart.

Input: The customer can request to view the contents of the shopping cart byclicking on the “view details” button.

Output: The system will return the contents of the shopping cart to thecustomer; the unit price and total price will be shown as well.Edit

Use case Details• Edit Billing & Shipping Details:

Purpose: This is to allow customers to edit and update their billing &shipping information.

Input: When the customer requests to checkout and he does not have creditcard information stored at this point (system cannot find his paymentinformation), the system will prompt credit card information page. Thecustomer will be given a choice on whether he wants the item shipped to hisstored address or to an alternative address.

Output: The input payment information will be saved into the order form.

Use case Details• Checkout:

Purpose: To allow user to buy the products added to the shopping cart.Precondition: User must be logged in and must have atleast one item inshopping Cart to be able to checkout and place the order.

Input: When the customer finishes shopping, he requests to checkout byclicking “checkout” button on Cart.aspx page.

Output: If the payment information of this customer already exists, thesystem prompts the customer to review or input a new one. If the credit cardis valid, the order form will be processed by the system and checkout iscomplete.

Use case Details• The Administrator actor can use the system for:1) Use Case 6 : System Login Requirement

Purpose: This is implemented to enable user authentication. A valid useraccount must be used for an existing customer.

Input: The user will enter two inputs (user name and password) through thekeyboard. Processing: The user inputs will be validated and authenticated against the localserver. The system will check the user name and password to see if they matchthe data stored onto the database.

Output: If the user name or password is invalid, the appropriate error messagewill be displayed and the user will be requested to re-enter user name andpassword. If the user inputs are valid, the default page will be displayed. If theuser is classified as an administrator, he/she will be redirected to anadministrator page wherein he/she can update the category details and viewcustomer orders.

Use case Details2) Use Case 7: Manage Catalog Requirements:• Add New Genre This is implemented to allow Administrator to do the following tasks:

• Category:

Purpose: To create and add new genres, categories to the catalog. Precondition: Administrator must be logged in to be able to create and add anew genre or category. Also, the genre to which the new category is to beassociated should exist in catalog.

Input: Administrator will enter the name and necessary details to create a newgenre or category to the Catalog and click “Add” button to complete theaction.

Output: After the action, the changes to the catalog will be updated and savedand a message will be displayed accordingly.

Use case Details• Delete genre/category:

Purpose: To remove genres, categories from the catalog. Precondition: Administrator must be logged in to be able to delete a genreor category. There has to be atleast one genre already present in catalog.

Input: Administrator will select a genre/category that is to be removed fromthe catalog and click “Remove” button.

Output: After the action, the changes to the catalog will be updated andsaved and a message will be displayed accordingly.

Use case Details• Add New Product:

Purpose: To create and add new products to the catalog. Precondition: Administrator must be logged in to be able to create a newproduct. Also, the genre and/or category to which the new product is to beassociated should exist in catalog.

Input: Administrator will enter the name and necessary details to create anew product to the Catalog and click “Add” button to complete the action.

Output: After the action, the changes to the catalog will be updated andsaed and a message will be displayed accordingly.

Use case Details• Delete Product:

Purpose: To remove product from the catalog.Precondition: Administrator must be logged in to be able to delete aproduct. There has to be atleast one product already present in catalog.

Input: Administrator will select a genre/category that is to be removed fromthe catalog and click “Remove” button.

Output: After the action, the changes to the catalog will be updated andsaved and a message will be displayed accordingly.

Use case Details• Manage Orders:

Purpose: To allow the site administrator to review and manage pending andpast orders according to various criteria such as date and status. Precondition: Administrator must be logged into the system. There has to beatleast one order already present in database.

Input: Administrator will enter the number of recent records he wishes toview and the range of dates the records are created. He/she will press the Gobutton against one or both the options – to view unverified, uncanceled ordersand/or to view verified, uncompleted orders.

Output: If the administrator enters invalid dates (Start date should be morerecent then the End date) to view orders between the range, the system shoulddisplay appropriate error message. The orders will be displayed as a dataset.Also, after all the orders are displayed and the administrator presses selectbutton for an order, he/she will be redirected to Orders Admin Web formwhere he can view and update order information. When selecting an order, itsdetails are displayed.

Use case Details• Manage Shopping Carts:

Purpose: To enable the administrator to see how many old shopping cartntries exist (shopping carts that haven’t been updated by their respective userfor certain amount of time) and delete them if necessary.Precondition: Administrator must be logged into the system. There has to beatleast one shopping cart before and up to that date.

Input: Administrator will select the number of days from the drop-down list(e. g 10, 15, 20 etc.) and click on “Count Old Shopping Carts” and/or “DeleteOld Shopping Carts” button(s) on ShoppingCartAdmin.aspx Web form.

Output: After the action, the changes to the catalog will be updated and savedand a message will be displayed accordingly.

Class Diagram

Activity DiagramActivity diagram – buyer (customer) browsing activities

Description:Customer browsing allows a search for a specific product or an examination of an entire product category. If a product is found it can be viewed, if not found thecustomer is allowed to search or brows again.

Activity DiagramActivity diagram – Buyer (customer) login and update activities

Description:

Customer login and update allows an update and verification of customerinformation after a valid login process.

Activity DiagramActivity diagram – buyer (customer) checkout activities

Description:Customer checkout first allows identification and entry of the shipping address, thenentry or retrieval of credit card information, and finally validation of the credit card.

Sequence DiagramsSystem Search Sequence Diagram

Sequence DiagramsSystem Login Sequence Diagram

Sequence DiagramsSystem Buying Sequence Diagram

Sequence DiagramsSystem Buying Sequence Diagram

L/O/G/O

Thank You!