Presentation (software engineering)

18
ONLINE SHOPPING CART (WEB APPLICATION) Team Name: Web Alien ------------------------------------- Team Members: 1)Abdullah al Shiam (13065401) 2)Nondon Sharker (13075415) 3)Najmul Hasan (13055453)

Transcript of Presentation (software engineering)

Page 1: Presentation (software engineering)

ONLINE SHOPPING CART (WEB APPLICATION) Team Name: Web Alien

------------------------------------- Team Members:

1)Abdullah al Shiam (13065401) 2)Nondon Sharker (13075415)

3)Najmul Hasan (13055453)

Page 2: Presentation (software engineering)

What Is E-Commerce

Commonly known as Electronic Marketing. E-commerce is the purchasing, selling and exchanging

goods and services over computer networks (internet) through which transaction or terms of sale are performed Electronically.

2

Page 3: Presentation (software engineering)

Short Description Of Our Project

o Our Project is Online Shopping Management.

o This is web base application. The basic concept of the application is to allow the customer to shop virtually using the Internet and allow customers to buy the items and articles of their desire from the store.

o And Also sellers can sell his items via the internet.The sale and purchase transaction is completed electronically and interactively in real-time.

o Administrator of Shopping Cart System has multiple features such as Add, Delete, Update shopping Items.

3

Page 4: Presentation (software engineering)

TRADITIONAL BUSINESS

DIRECT SELLING

MANF. UNIT 20%

DISTRIBUTOR 10%

WHOLESALER 10%

RETAILER 10%

CUSTOMER 100%

ADVERTISEMENT 50%

CUSTOMER

COMPANY

Page 5: Presentation (software engineering)

Why And What We Want To Do?

What to do?o Good User interface.o Transaction processing system.o Security management. Why to do?o No need to meet buyers and sellers to purchase

products.o Can use anyone from anywhere vai internet.o It will reduce time and transaction cost and energy.

Page 6: Presentation (software engineering)

Time Schedule

DEADLINE: AFTER 13 WEEKS

6

Task 1 Task 2 Task 3 Task 4 Task 5 Task 6

0 weeks 2 weeks 4 weeks 8 weeks 11 weeks 13 Software

Requirement Design Coding Intigration Deployment Maintenance

2 weeks 2 weeks 4 weeks 3 weeks 2 weeks

Lifetime

Page 7: Presentation (software engineering)

User Domain USER

Everyone from everywhere can use the application. The only need to use the application is capability to

browse internet .

BENEFICIARY It helps buyers to buy product easily. It also helps sellers to sell product successfully.

Page 8: Presentation (software engineering)

User Requirements

End User Requirementso Transactions should be secure. o User should be able to view a complete list of specified

items and able to search for items.o The user interface should be attractive.o Users should be able to modify the quantities of items in

and/or delete items from their shopping carts before checkout.

Administrator Requirements (Shoop Keeper)

o Administrators should be able to change the status of goods purchased by users after items have been shipped.

o Administrators should be able to view all user transactions.

o Site managers should be able to view all transactions.

Page 9: Presentation (software engineering)

Team Structure Team Type: Centralized

Shiam(Leader

)

Nondon(Analyst

)

Nayem(Design

)

Page 10: Presentation (software engineering)

Software Development Life Cycle(SDLC)

We use waterfall model for our project

Fig:waterfall model

10

Page 11: Presentation (software engineering)

Reason For Using Waterfall Model

This model is simple and easy to understand and use.

Waterfall model works well for smaller projects where requirements are very well understood.

 Phases do not overlap. Each phase has specific deliverables and a

review process.

11

Page 12: Presentation (software engineering)

Testing

We use black-box, white-box and gray-box testing.

White-box Testing: It is start at coding face.It usually used for testing data

flow. Our group leader will test white-box testing

12

Page 13: Presentation (software engineering)

Black-box Testing: This testing enable the software engineer to

find Error Performance error Initialization error Interface error

Nayem and nondon as like as user will test black-box testing.

13

Page 14: Presentation (software engineering)

Gray-box Testing: In gray-box testing the tester have access to

find the error and correction the error.

So all the member of the team will test gray-box testing

14

Page 15: Presentation (software engineering)

Myth’s

Management’s myths:o If we get behind schedule, we can add more

programmers and catchupo All information can be acquired from manual.

Users myth’s.o Software is flexible.

Developer’s myth’s:o Once we write the program and get it to work, our job

is done.o Testing is Too Expensive.Only Fully Developed

Products are Tested

o

15

Page 16: Presentation (software engineering)

Risk Management

Identify the risk Analyse about the risk(Communicating with group

member) Planning for avoiding risk Track the risk Mitigate the risk(Control risk).

16

Page 17: Presentation (software engineering)
Page 18: Presentation (software engineering)

18

?