Project System analysis for E-Commerce App

1. E–COMMERCE APP
SYSTEM ANALYSIS AND DESIGN
BY : MAJID SAQR

2. INTRODUCTION

3. 3
WHAT IS E-COMMERCE
•
It is commonly known as electronic marketing.
•
•
It consist of buying and selling goods over an electronic system such as the
internet.
•
•
E-Commerce is the purchasing, selling & exchanging goods and services
over computer network or internet through which transactions or terms of sale
are performed electronically

4. 4

5. 5
ADVANTAGES OF E-COMMERCE
●
Faster buying & selling procedure , as well as easy to find products.
●
More reach to customers, there is no theoretical geographic limitations.
●
Low operational costs and better quality of services.
●
No need of physical company set-ups.
●
Easy to start and manage a business.
●
Customers can easily select products from different providers without
moving around physically.

6. 6
DISADVANTAGES OF E-COMMERCE
●
Unable to examine products personally
●
Not everyone is connected the internet
●
There is the possibility of credit card number theft
●
Mechanical failures can cause unpredictable effects on the
total processes

7. INFORMATION GATHERING
&
SYSTEM STUDY

8. 8

9. 9

10. 10

11. 11

12. 12

13. 13
GOALS OF MY PROJECT
●
The main goals of my project are :
1. User friendly navigation to provide ease.
2. Maximize search options
2.1 by category name
2.2 by product title
3. Help user by providing specification of products.
4. Full Security System
5. Buy online any product at home fast.

14. 14
PROPOSED FEATURES
1. Home
2. Search
3. Categories
4. Logo
5. Sign up & Sign in
6. Product images
7. Cart
8. Product Review
9. Animation
10. Latest product

15. Systems Development Life
Cycle (SDLC)

16. 16
E-COMMERCE LIFE CYCLE
●
Plan
●
Analysis
●
Design
●
Development
●
Test
●
Implement
●
Maintain

17. 17
PLANING
●
Appoint App master team
( only me )
●
Define the objective of the e-commerce app / portal to be developed.
●
Define the project scope.
●
Develop the project plan including tasks, resources and time frames.

18. 18
ANALYSIS
●
Define who is the audience
B2B – Business visitors
OR B2C – Customers visitors
OR Others
●
Gather the business requirement for the system
●
SRS – System Requirement Specifications

19. 19
Design
●
Designing the navigation view
- starting with home page and first level child page
●
Hyperlinks plan and buttons
●
Back end required
Database ?
●
Payment Gateway

20. 20
SELECT WAY TO DEVELOP APP
●
Prepare app – write codes in :
- Java + android studio
OR Kotlin + android studio
OR Python ( Kivy & KivyMD )
●
Use frameworks :
- Flutter

21. 21
TEST / QUALITY CHECK
●
Test App
- Check for broken links
- Speed : Slow pages
●
Database test records
updating of database
●
Money transaction ( if applicable )

22. 22
Publish
●
Select hosting company
●
Pay hosting charges and get passwords
●
Unable app to the internet server

23. 23
MAINTAIN & UPDATE
●
Regularly change and update the content
●
Preform SEO
●
Update keywords / Meta tag as the per the changes in
business needs

24. SYSTEM DESIGN
&
SHOW DESIGN

25. CONTEXT DIAGRAM
A context diagram is a high-level view of a system. It’s a basic
sketch meant to define an entity based on its scope,
boundaries, and relation to external components like
stakeholders.

27. ACTIVITY DIAGRAM
Activity diagram is another important behavioral diagram in
UML diagram to describe dynamic aspects of the system.
Activity diagram is essentially an advanced version of flow chart
that modeling the flow from one activity to another activity.

30. DATA FLOW DIAGRAM
A data flow diagram (DFD) maps out the flow of information
for any process or system. It uses defined symbols like
rectangles, circles and arrows, plus short text labels, to show
data inputs, outputs, storage points and the routes between
each destination.

33. USE CASE
A use case diagram is the primary form of system/software
requirements for a new software program underdeveloped.
Use cases specify the expected behavior (what), and not the
exact method of making it happen (how).

34. Sign Up
Sign in
Search
Show
Buy
Confirm
Put product
Modify
Accept
Reset

35. ERD DIAGRAM
An Entity Relationship (ER) Diagram is a type of flowchart that
illustrates how “entities” such as people, objects or concepts
relate to each other within a system. ER Diagrams are most
often used to design or debug relational databases in the fields
of software engineering, business information systems,
education and research.

37. FLOW CHART DIAGRAM
A flowchart is a diagram that depicts a process, system or
computer algorithm. They are widely used in multiple fields to
document, study, plan, improve and communicate often
complex processes in clear, easy-to-understand diagrams.

38. Start
End
Info ( Name –
Email – Password )
Sign up
Info ( Email –
Password )
Sign in
Right Info ?
NO
Search
Show
Choose
process
Buy
Confirm
YES

39. Start
Info ( Email –
Password )
Sign in
Right
Info ?
Choose
process
Put product Accept
Modify
Yes
NO
End

40. CLASS DIAGRAM
The UML Class diagram is a graphical notation used to construct and
visualize object oriented systems. A class diagram in the Unified
Modeling Language (UML) is a type of static structure diagram that
describes the structure of a system by showing the system's:
●
classes,
●
their attributes,
●
operations (or methods),
●
and the relationships among objects.

42. SCREEN SHOTS OF PROJECT
&
VISUAL GUIDE

49. CONCLUSION
●
In conclusion we can say that there is no end to product
improvement. Even when there seems to room for improvement
there always is. Just like google was once just a search engine.
But provide additional related features; similarly my goals is
other features to my e-commerce system.