"Shopify": A Project Report ON

A
PROJECT REPORT
ON
“SHOPIFY”
SUBMITTED TO
GUJARAT TECHNOLOGICAL UNIVERSITY
AHMEDABAD.
Submitted in partial fulfillment of the requirements for the degree of
Master of Computer Application

Semester-5
SUBMITTED BY
Sejpal Hiren(Enrollment No.- 185443693038)

Parmar Parth (Enrollment No.- 185443693028)
Rathod Jignesh (Enrollment No.- 185443693035)
UNDER GUIDANCE OF
Dr. Vimal P. Parmar
DSTC, Junagadh
Shopify
PREFACE
There is a wide difference between theory and practical. If one has only theoretical
background of any subject, one would not succeed in own aim therefore it is necessary for
any person to have adequate practical knowledge of the concerned subject. As I know M.C.A.
is a course based on “Information Technology” and it is totally practical field. With only
theoretical knowledge one can’t be succeeded or one can’t be on the peak position.
In the course of M.C.A. designed by the “GTU” they have taken full care of these
things and designed the course in such a manner with which student can get theoretical and
practical both type of knowledge perfectly. According to the rules & regulation of “Web
Development”, we have a subject. In which we have to create a web project of any institute
or industry.
As a M.C.A. student, I have gathered general information about upload and download
the files. In this site Visitor can give his/her vote
In this project report I have covered all the information, which is required for the web
project of M.C.A. student.I have tried as my best present this project report in such a way that
it makes easy to understand the project work.
ACKNOWLEDGEMENT
I am thankful to all, who have helped me in preparing this project. I am very much
happy to present this “Project Report”. Before you expecting that you will acknowledgement
it. It is a matter of great pleasure for me that I had an opportunity to express our view on the
same.
As a part of our academic study the student of 5th semester of M.C.A. At first, I would
like to express our & humble thanks & gratitude to them who has provided us such a great,
Co-operative & progressive environment.
Secondly at this moment, I would like to express our deepest sense of gratitude to our
professor as well as project guides Dr. Vimal Parmar(Principal) sir who have contribute their
precious time for the purpose of giving us the correct information with special interest &
guidance throughout our project work.
Developed By: Sejpal Hiren, Parmar Parth, Rathod Jignesh

Shopify
INDEX
1. INTRODUCTION......................................................................................................................... 4
1.1 Existing System ............................................................................................................................ 4
1.2 Need for the New System ............................................................................................................. 4
1.3 Objectives for the New System .................................................................................................... 5
1.4 Problem Definition........................................................................................................................ 5
1.5 Core Components.......................................................................................................................... 5
1.6 Project Profile .............................................................................................................................. 6
1.7 Assumptions and Constraints ........................................................................................................ 7
1.8 Advantages or Limitations of Proposed System ........................................................................... 7
2. REQUIREMENT DETERMINATION & ANALYSIS ............................................................ 8
2.1 Requirement Determination .......................................................................................................... 8
2.2 Targeted Users .............................................................................................................................. 8
2.3Tools and Technology.................................................................................................................... 8
3. SYSTEM DESIGN ........................................................................................................................ 9
3.1 Use Case Diagram......................................................................................................................... 9
3.2 Class Diagram ............................................................................................................................. 11
3.3 Interaction Diagram .................................................................................................................... 14
3.4 Activity Diagram ........................................................................................................................ 16
3.5 Data Dictionary ........................................................................................................................... 18
4. DEVELOPMENT ....................................................................................................................... 20
4.1 Coding Standards ........................................................................................................................ 20
4.2 Sample Code ............................................................................................................................... 23
5. AGILE DOCUMENTATION ........................................................................................................ 25
5.1 Agile Project Charter .................................................................................................................. 25
5.2 Agile Roadmap ........................................................................................................................... 26
5.3 Agile Project Plan: ...................................................................................................................... 27
5.4 Agile User Story ......................................................................................................................... 28
5.5 Agile Release Plan ...................................................................................................................... 29
5.6Agile Test Plan:............................................................................................................................ 30
6. TESTING AND IMPLEMENTATION ....................................................................................... 32
6.1 SCREEN LAYOUT: ................................................................................................................... 32
7.LIMITATIONS AND PROPOSED ENHANCEMENT ............................................................... 32
8. BIBLIOGRAPHY ........................................................................................................................... 32

Shopify
1. INTRODUCTION
1.1 Existing System
Several trends are opening up the era of Computing, which is an Internet-based

development and use of Computer technology. The ever cheaper and more powerful
processors, together with the "software as a service" (SaaS) computing architecture, are
transforming data centers into pools of computing service on a huge scale. Due to increase in
network bandwidth and reliable yet flexible network connections make it even possible that
clients can now subscribe high quality services from data and software that reside solely on
remote data centers.
There is Many of Drawback of the system like,
 Maintenance Problem
 Security Problem
 Searching Problem
 Accuracy
 Storage Problem
 Backup Problem etc are the problem that may occur during working with it.
But There is Some Advantages is also helpful to us to work easily
 Time Saving
 Cheap
 Problem solving
 Easy Generate Reports
1.2 Need for the New System

Why did we need a new system?
Because the old system was inefficient, fragmented, unfair, underfunded and most
people with a disability didn’t get the support they needed. It was run on a state-by-state basis
and there was no national consistency. Most importantly, you didn’t get enough say in the
sort of assistance you need. But you will now.
Proposed System
The proposed system should have the following features. The transactions should take
place in a secured format between various clients in the network. It provides flexibility to the
user to transfer the data through the network very easily by compressing the large amount of
file. It should also identify the user and provide the communication according to the
prescribed level of security with transfer of the file requested and run the required process at
the server if necessary.

Shopify
1.3 Objectives for the New System
• To understand how the requirements are currently being met with existing system (s).
• To document the flow, processing and use of information within the existing system(s).
• To identify the problems with the existing system(s).
• To define new requirements.
1.4 Problem Definition
In this you can do shopify users. First you have to register as a user then you can login
in this site. In this project admin can add product and its choices and also give the shopify.
All super user and see users name. Admin can add, delete, edit the shopify product. Super
user also add, delete, edit the product in admin side. Users only see the product and visit the
site.
1.5 Core Components
FRONT END: you can give the shopify product from the choices of the product and
loging as a client user. clients do not do edit delete and end the product.
BACK END: The back end of the Project admin can add the product and give the choices
of the product and do edit & delete the products and choices….

Shopify
1.6 Project Profile
1. Project Title Shopify
2. Front end DJANGO
3. Back end SQLITE-3
4. Software tool Cmd, Browser, Sublime
5. Document tool MS Word, Fox it Reader
6. Internal Guide Dr.Vimal Parmar(Principal)
7. Submitted to Dr.Subhash Technical Campus(Dept. of MCA)

Sejpal Hiren
8. Submitted By Parmar Parth
Rathod Jignesh

Shopify
1.7 Assumptions and Constraints
Shopify is in shopping the shopify product to the different category. There are you
can do safely purchasing the product. New user register to the site.
In this you can purchase the product as a users. First you have to register as a user
then you can login in this. In this project admin can add product .Admin can filter staff
admin. All super user and see the users name. admin can add , delete, edit the products. Super
user also add, delete, edit the product in admin side.
ASSUMPTIONS:
Implementation project to begin from July, step-by-step Using plan do study
act(PDSA) process and completed by October.
Implementation of core components in website during requirement gathering period.
No new major software or hardware will be required to run current system.
CONSTRAINTS:
 Budget limitations
 Time Limitation
 Resource Limitations
1.8 Advantages or Limitations of Proposed System
ADVANTAGES
 Easy to use. Compatible with System Smart and Clear designing
 Easy understand
 Easy to do shopify shopping

Shopify
2. REQUIREMENT DETERMINATION & ANALYSIS
2.1 Requirement Determination
At he heart of systems analysis is a detailed understanding of all important facets of

the business are under investigation. Analysis working closely with employees & manages,
must study the business process to answer these key questions.
 What is being done?
 How is it being done?
 How frequently does is occur?
 Does a problem exist?
 If a problem exists, how serious is it?
 If a problem exists, what is the underlying cause?
2.2 Targeted Users
We expect the audience for this Project to be the End Users; Users of the give product
in shopify shop. first you have to login to give the site in product but you have to registered
first. then you can give the product .
2.3Tools and Technology

SOFTWARE REQUIREMENTS
No. Software Used Remarks
1 CMD Used to run code
2 Windows Used to run Apache web Server on sever side.
3 MS Word Used as the documentation tools
4 Internet Used as the communication tool
5 Photoshop Graphic Designing
6 Sublime 3 Used as Code editor
HARDWARE REQUIREMENTS
Category Server Side
Processor Pentium II or later version
Hard Disk Drive 350 MB free fixed disk
RAM 64 MB or Higher
Monitor 14’’ Color for best result
Network devices Network Adapter

Shopify
DJANGO:
Django and Python can seem overwhelming at first, but they don't have to be! In this course
I’ll walk you through it step by step and you’ll be building your first web app in MINUTES.
You’ll be amazed how quick and easy it is to create very professional looking websites, even
if you have no programming or web design experience at all.
Watch over my shoulder as I build a cool To-Do List app step by step right in front of you.
You’ll follow along and build your own copy. By the time we’re finished, you’ll have a solid
understanding of Django and how to use it to build awesome web apps.
SUBLIME:
Sublime Text is a proprietary cross-platform source code editor with a Python application
programming interface (API). It natively supports many programming languages and markup
languages, and functions can be added by users with plugins, typically community-built and
maintained under free-software licenses.
3. SYSTEM DESIGN
3.1 Use Case Diagram
A use case diagram at its simplest is a representation of a user's interaction with the
system that shows the relationship between the user and the different use cases in which the
user is involved. A use case diagram can identify the different types of users of a system and
the different use cases and will often be accompanied by other types of diagrams as well.
While a use case itself might drill into a lot of detail about every possibility, a use-case
diagram can help provide a higher-level view of the system. It has been said before that "Use

Shopify
case diagrams are the blueprints for your system".[1] They provide the simplified and
graphical representation of what the system must actually do.
Due to their simplistic nature, use case diagrams can be a good communication tool
for stakeholders. The drawings attempt to mimic the real world and provide a view for
the stakeholder to understand how the system is going to be designed. Siau and Lee
conducted research to determine if there was a valid situation for use case diagrams at all or if
they were unnecessary. What was found was that the use case diagrams conveyed the intent
of the system in a more simplified manner to stakeholders and that they were "interpreted
more completely than class diagrams"
The purpose of the use case diagrams is simply to provide the high level view of the
system and convey the requirements in layman's terms for the stakeholders. Additional
diagrams and documentation can be used to provide a complete functional and technical view
of the system.

Shopify
Use case Diagram
3.2 Class Diagram
A class diagram is an illustration of the relationships and source code dependencies

among classes in the Unified Modeling Language (UML). In this context, a class defines
Shopify
the methods and variables in an object, which is a specific entity in a program or the unit of
code representing that entity. Class diagrams are useful in all forms of object-oriented
programming (OOP). The concept is several years old but has been refined as OOP modeling
paradigms have evolved.
In a class diagram, the classes are arranged in groups that share common
characteristics. A class diagram resembles a flowchart in which classes are portrayed as
boxes, each box having three rectangles inside. The top rectangle contains the name of the
class; the middle rectangle contains the attributes of the class; the lower rectangle contains
the methods, also called operations, of the class. Lines, which may have arrows at one or both
ends, connect the boxes. These lines define the relationships, also called associations,
between the classes.

Shopify
Class diagram:
users category_table product_table

1
n n
user_id category_id product_id
user_email_id category_name product_name
1
user_name category_id
1
user_mobile sub_category_id
user_password product_rate
product_description
order_table
user_create_date 1
sub_category_table product_image order_id
product_gst invoice_no
sub_category_id
product_added_date 1
user_id
sub_categort_name
category_id 1 address_id
1
order_transport_charges
order_date
order_timestamp
stated user_address order_ref_table

n
n
n
address_id cart_table order_ref_id
state_id
n
user_id order_id
state_name n
user_name cart_id n
order_ref_product_id
user_mobile product_id order_ref_quantity
n
pincode product_quantity order_ref_rate

locality user_id order_ref_gst
n
districts
address
1
-district_id n
state_id
district_name 1 district_id
state_id
n

Shopify
3.3 Interaction Diagram
Interaction diagrams are models that describe how a group of objects collaborate in
some behavior - typically a single use-case. The diagrams show a number of example objects
and the messages that are passed between these objects within the use-case.
Interaction diagrams come in two forms, both present in the UML. The first form is the
sequence diagram. In this form objects are shown as vertical lines with the messages as
horizontal lines between them. This form was first popularized by Jacobson. The diagram
below shows this form in its UML notation.
When to Use Them
Interaction diagrams should be used when you want to look at the behavior of several
objects within a single use case. They are good at showing the collaborations between the
objects, they are not so good at precise definition of the behavior.
If you want to look at the behavior of a single object across many use-cases, use
a state transition diagram. If you want to look at behavior across many use cases or many
threads, consider an activity diagram.

Shopify
Interaction Diagram:
customer System Interface Cart Checkout Order
search item
result
select Item
Add to Cart
register
login
authorized
Manage Cart
buynow
checkout
Place Order
Order details
manage Orders
logout
For shopping Process

Shopify
3.4 Activity Diagram
Activity diagrams are graphical representations of workflows of stepwise activities

and actions with support for choice, iteration and concurrency. In the Unified Modeling
Language, activity diagrams are intended to model both computational and organizational
processes (i.e., workflows), as well as the data flows intersecting with the related
activities. Although activity diagrams primarily show the overall flow of control, they can
also include elements showing the flow of data between activities through one or more data
stores.
Activity diagram is another important diagram in UML to describe the dynamic
aspects of the system.
Activity diagram is basically a flowchart to represent the flow from one activity to
another activity. The activity can be described as an operation of the system.
The control flow is drawn from one operation to another. This flow can be sequential,
branched, or concurrent. Activity diagrams deal with all type of flow control by using
different elements such as fork, join, etc
Purpose of Activity Diagrams

The basic purposes of activity diagrams are similar to other four diagrams. It captures
the dynamic behavior of the system. Other four diagrams are used to show the message flow
from one object to another but activity diagram is used to show message flow from one
activity to another.
Activity is a particular operation of the system. Activity diagrams are not only used
for visualizing the dynamic nature of a system, but they are also used to construct the
executable system by using forward and reverse engineering techniques. The only missing
thing in the activity diagram is the message part.
It does not show any message flow from one activity to another. Activity diagram is
sometimes considered as the flowchart. Although the diagrams look like a flowchart, they
are not. It shows different flows such as parallel, branched, concurrent, and single.

Shopify
ACTIVITY DIAGRAM:
[skip it]
[search] [found]
Search Item View Item
[not found]
Browse Item
[browse]
[skip it]
[if like item]

[If not login]
Add to Cart
[if login]
View Cart
[more shopping]
Proceed to
Update Cart
checkout
[done with shopping]
Activity Diagram of Online Shopping

Shopify
3.5 Data Dictionary
Data Dictionary Reports allow m-Power developers to better understand the

organization and hierarchy of their Data Dictionary. Developers can utilize Data Dictionary
Reports in a number of ways, including:
 Viewing the Dictionary Dashboard, this provides numerous key statistics.

 Searching for where tables, fields, external objects, and UDFs are utilized with the
Data Dictionary.
 Accessing a listing of all applications that utilize a certain template.
 A complete synopsis of application specification details.
 The ability to review Stored Procedure syntax auto generated by m-Power for
External Objects.
The data dictionaries demonstrate detailed mappings for all of the CLM application data
that is collected and stored in the data warehouse Operational data store (ODS). There are
many cases where data warehouse tables and columns are non populated by CLM application
data because they are used for other purposes.

Shopify
users:
Field Name Datatype Length Constraint
user_id Varchar 40 Primary Key
user_email_id Varchar 150 NotNull
user_name Varchar 100 NotNull
user_mobile bigInt 20 NotNull
user_password Varchar 200 NotNull
user_create_date Timestamp NotNull
user_address:
address_id Varchar 40 Primary Key
user_id Varchar 40 Foreign Key
user_name Varchar 150 NotNull
user_mobile bigInt 20 NotNull
Pincode Int 10 NotNull
Locality Vachar 150 NotNull
Address Vachar 200 NotNull
state_id Int 8 Foreign Key
district_id Int 8 Foreign Key
states:
state_id Int 8 Primary Key
state_name Varchar 100 NotNull
districts:
district_id Int 8 Primary Key
district_name Varchar 100 NotNull
state_id Int 8 Foreign Key
category_table:
category_id Varchar 40 Primary Key
category_name Varchar 100 NotNull

Shopify
sub_category_table:
sub_category_id varchar 40 Primary Key
sub_category_name varchar 100 NotNull
category_id Varchar 40 Foreign Key
4. DEVELOPMENT
4.1 Coding Standards
There are few coding standards which followed while coding in project...
Coding Standards are an important factor for achieving a high code quality. A common visual
style, naming conventions and other technical settings allow us to produce a homogenous
code which is easy to read and maintain. However, not all important factors can be covered
by rules and coding standards. Equally important is the style in which certain problems are
solved programmatically - it’s the personality and experience of the individual developer
which shines through and ultimately makes the difference between technically okay code or a
well considered, mature solution.
These guidelines try to cover both, the technical standards as well as giving incentives for
a common development style. These guidelines must be followed by everyone who creates
code for the Flow core. We hope that you feel encouraged to follow these guidelines as well
when creating your own packages and Flow based applications.
 Indenting and Line Length: Use an indent of 4 spaces and don't use any tab because
different computers use different setting for tab. It is recommended to keep lines at
approximately 75-85 characters long for better code readability.
 Control Structures: These include if, for, while, switch, etc. Control statements should
have one space between the control keyword and opening parenthesis, to distinguish
them from function calls. You are strongly encouraged to always use curly braces even
in situations where they are technically optional.
 Function Calls: Functions should be called with no spaces between the function name,
the opening parenthesis, and the first parameter; spaces between commas and each
parameter, and no space between the last parameter, the closing parenthesis, and the
semicolon.
Shopify
 Comments: C style comments (/* */) and standard C++ comments (//) are both fine. Use
of Perl/shell style comments (#) is discouraged.
 PHP Code Tags: Always use <?php ?> to delimit PHP code, not the <? ?> shorthand.
This is required for PHP compliance and is also the most portable way to include PHP
code on differing operating systems and setups.
Namespace and Class names

 Only the characters a-z, A-Z and 0-9 are allowed for namespace and class names.
 Namespaces are usually written in UpperCamelCase but variations are allowed for well
established names and abbreviations.
 Class names are always written in UpperCamelCase.
 The unqualified class name must be meant literally even without the namespace.
 The main purpose of namespaces is categorization and ordering
 Class names must be nouns, never adjectives.
 The name of abstract classes must start with the word “Abstract”, class names of aspects
must end with the word “Aspect”.
Method names
All method names are written in lowerCamelCase. In order to avoid problems with different
file systems, only the characters a-z, A-Z and 0-9 are allowed for method names – don’t use
special characters.
Make method names descriptive, but keep them concise at the same time. Constructors must
always be called __construct(), never use the class name as a method name.
 addToCart()
 setOrder()
 deleteProduct()
 getUserName()

Shopify
Filenames
These are the rules for naming files:
 All filenames are UpperCamelCase.

 Class and interface files are named according to the class or interface they represent
 Each file must contain only one class or interface
 Names of files containing code for unit tests must be the same as the class which is
tested, appended with “Test.php”.
File naming in Flow
Ex. shopify/class/class.connection.php
Constant names
All constant names are written in UPPERCASE. This includes TRUE, FALSE and NULL.
Words can be separated by underscores - you can also use the underscore to group constants
thematically:
 STUFF_LEVEL
 COOLNESS_FACTOR
 PATTERN_MATCH_EMAILADDRESS
 PATTERN_MATCH_VALIDHTMLTAGS
Variable Names:
 A variable starts with the $ sign, followed by the name of the variable.
 A variable name must start with a letter or the underscore character.
 A variable name cannot start with a number.
 A valid constant name starts with a letter or underscore (no $ sign before
the constant name). Note: Unlike variables, constants are automatically global across
the entire script.

Shopify
 Alignment of Declaration Blocks:
Block of declarations should be aligned.
4.2 Sample Code
Connection file:
class.connection.php
<?php
class Connection extends PDO
{
private $host = "localhost";
private $user = "root";
private $password = "";
private $dbname = 'flowershop';
private $charset = "utf8";
private $opt = [
PDO::ATTR_ERRMODE => PDO::ERRMODE_EXCEPTION,
PDO::ATTR_DEFAULT_FETCH_MODE => PDO::FETCH_ASSOC,
PDO::ATTR_EMULATE_PREPARES => false,
PDO::MYSQL_ATTR_INIT_COMMAND => "SET NAMES utf8"
];
private $conn;
function __construct()
{
try {
$this->conn = parent::__construct("mysql:host=$this->host;dbname=$this-
>dbname;charset=$this->charset", $this->user, $this->password, $this->opt);
} catch (PDOException $e) {
echo $e->getMessage();

Shopify
}
}
public function closeConnection()
{
$this->conn = null;
}
}
?>

Shopify
5. AGILE DOCUMENTATION
5.1 Agile Project Charter
An Agile process is a process which manages unpredictability about the majority of s/w
projects.
Agile is a time boxed, iterative approach to software delivery that builds software
incrementally from the start of the project, instead of trying to deliver it all at once near the
end.
5.1 Agile Project Charter

 Agile project charter maybe very lightweight, like a single sheet as, Agile wants to
minimize the documentation. Agile Charter usually just define the goal of the project
at high level, the 5 “Why” & H of the project (Who, What Where, When, Why and
How) and the authorization for the project.
 It is flexible document that will allow the team to respond to changes as well as
delivery high quality product quickly for the organization
 Project Vision: Why does the project exist?
 Success Criteria: How will you know when the project is complete and the vision is
realized?
 Stakeholders: Who is involved and/or affected by this project?
 Project Risks: What are the top risks of this project?
 Responsibilities: What roles are needed and who is doing what?
 Project Size and Complexity: What is the size and degree of difficulty of this project?
 Product Roadmap: What is the strategic view of where the product is headed?

Shopify
Project Charter
Start date 25 July 2019

Project Title Shopify
End date 7 october 2019
Project Guide Dr.Vimal Parmar(internal)
In this you can do purchase the shopify product as a users. First you have
to register as a user then you can login in this. In this project admin can
Scope
add product. All super user and see the users name.
Success The project will be determined successful if the purchase watch.
Vision Provide Best Services to delivery.
Risk Only one time give the order it’s can’t change.

Shopify
5.2 Agile Roadmap
A roadmap is a powerful tool to describe how poll is add, to align the voters, and to acquire a
budget for voters the poll. But creating an effective roadmap is not easy, particularly in an
agile context where changes occur frequently and unexpectedly
Roadmaps show the evolution of your features over time to help you define vote . Thus, they
are managed by the poll Owner and by default can be seen by anybody having access to the
project.
It would not be very agile to define only one roadmap for your poll. . Just like on a real map,
you don’t want to see only the ideal path but also all the crossroads and the alternative paths
you may take as your direction and the traffic change.
ROADMAP

Shopify
5.3 Agile Project Plan:
An agile project plan is based on features. The plan estimates how long it will take for each feature
to be delivered, without much detail on how it will be delivered. And because the project plans are
focused on features, you can group similar features into sprints.
An agile project plan is always changing. Once the plan is developed, the project team needs to
maintain it and update status and timelines accordingly.
Also known as an agile project schedule, this Diagram lets you add your tasks, who is responsible,
start and end dates, and status. The duration for each task will be automatically calculated. This
Diagram also features a Gantt chart (a visual representation of your project timeline), which will
automatically adjust when you add your own data to the table.
Project Plan:
Task Name Responsible Start End Days Status

Requirement
- - - - -
Gathering
Analysis 25-7-19 10-8-19 16 Complete
Hiren
Deciding tools Parth 5-8-19 20-8-19 15 Complete
Jignesh
deciding Software 15-8-19 28-8-19 13 Complete
Coding - - - - -
Designing DB Hiren 5-9-19 10-9-19 5 Completed
Core Feature Parth 11-9-19 13-9-19 2 Overdue

Jignesh
Web Designing 14-9-19 18-9-19 4 In progress
Implementation - - - - -
Core coding 19-9-19 28-9-19 9 In progress

Hiren
Sub features 29-9-19 5-10-19 7 In progress
Parth
Testing Jignesh 6-10-19 10-10-19 4 Completed
Improvements 10-10-19 10-10-19 2 Completed

Shopify
5.4 Agile User Story
A user story describes a feature from the end-user’s perspective. It includes the type of user,
what they want, and why they want it. These short, one-sentence user stories create a super simple
description of a requirement. Then, the development team develops code that will satisfy the
requirements of the user story.
This agile use case Diagram follows the typical agile story structure: as a <type of user>, I
want to <perform some task> so that I can <achieve some goal>.
 User stories are short, simple descriptions of a feature told from the perspective of the
person who desires the new capability, usually a user of the system.
 The user story describes the type of user, what they want and why. A user story helps
to create a simplified description of a requirement.
ID As a<type of user> I want to <perform So that I can <achieve some goal>

sometask>
1 DB designer Design perfect Normalized Use python django database and

database for e commerce design tables.
website.
2 Developer Develop a core features Using django Core functions develop
like login, register etc. some features
3 Web Designer Design a best website and Using CSS, Bootstrap and other
User friendly features features
I can able to design website
4 Tester Testing as try to fail system Try best testing and taking help of
others.

Shopify
5.5 Agile Release Plan
Agile release planning happens during sprint zero, when there is no product to deliver and the team
can instead focus on defining the release goal, the features that need to be delivered, assigning
features to a sprint, and estimating the duration of each task. Release planning may change as new
stories are added or deleted.
This agile release diagram allows you to list all your tasks, assign each task to a sprint, and calculate
the duration based on start and end dates
Release Plan is a guideline that reflects expectations about which features will be
implemented and when they are completed. It also serves as a base to monitor progress within
the project.
The following table show Agile Release Plan for agile team – Provide insights into technical
feasibility and dependencies.
Agile Release Plan:

Sprint
Release
Feature name Start Finish Status Duration
date
1 Software configuration 25-7-19 30-7-19 Complete 5d -
In
2 Dashboard for admin 1-8-19 10-8-19 9d 25-7-19
progress
Registration-login & Complete
2 11-8-19 20-8-19 9d
validation d
In
2 Manage address feature 21-8-19 28-8-19 7d
progress
In
2 Manage cart 29-8-19 10-9-19 12d 29-8-19
progress
Complete
3 Place order 11-9-19 25-9-19 15d
d
Complete
3 User profile 26-9-19 10-10-19 15d
d

Shopify
5.6Agile Test Plan:
Instead of a static testing plan that must happen at a certain time, test plans in agile projects should
be dynamic and iterative. The testing phase becomes an extension of the requirements prioritization
process so that the most up-to-date information is used when defining tests and to avoid any
misunderstanding about scope.
While you don’t need an extensive agile test plan, you still need to track the actions, expected
results, actual results, and whether the test passed or failed.
Project Name
The Shopify
Tested By: DR. vimal Parmar
Description Agile Test Plan Browser Chrome
Tested on: 15-09-19 22-09-19
Test Pass?
action Expected Result Actual Result
#
Check out will continue if user checkout will continue

1 Checkout
Login without login
Form validation for all form,

Check Receives only validate
2 first validate form and
validation values
thensubmit

Shopify
6. TESTING AND IMPLEMENTATION:

6.1 SCREEN LAYOUT:
Welcome Page Screen shot:

Home page

Shopify
User login & registeration Page:

Shopify
Poll List:
Admin:

Shopify
Site Administration:
Users:

Shopify
Add Poll:
Add choice:
Shopify
Add Vote:

Shopify
Admin Logout:

Shopify
7. LIMITATIONS AND PROPOSED ENHANCEMENT
Everything has limitations no single thing is perfect, in this project many limitations
we can see,
For ex,
 Only admin can add ,edit , delete products.
 Paytm system is not available in this site.
 Not available of free delivery.
Future Enhancement
We are tried to set client can edit their shopify product.
8. BIBLIOGRAPHY
https://www.google.com/
https://www.djangoproject.com/start/
https://developer.mozilla.org/en-US/docs/Learn/Server-
side/Django/Tutorial_local_library_website

"Shopify": A Project Report ON

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

"Shopify": A Project Report ON

Uploaded by

Copyright:

Available Formats

A

GUJARAT TECHNOLOGICAL UNIVERSITY

Submitted in partial fulfillment of the requirements for the degree of

Master of Computer Application

Sejpal Hiren(Enrollment No.- 185443693038)

Developed By: Sejpal Hiren, Parmar Parth, Rathod Jignesh

Developed By: Sejpal Hiren, Parmar Parth, Rathod Jignesh

1.1 Existing System

Several trends are opening up the era of Computing, which is an Internet-based

1.2 Need for the New System

Developed By: Sejpal Hiren, Parmar Parth, Rathod Jignesh

1.3 Objectives for the New System

1.4 Problem Definition

1.5 Core Components

Developed By: Sejpal Hiren, Parmar Parth, Rathod Jignesh

1.6 Project Profile

1. Project Title Shopify

2. Front end DJANGO

3. Back end SQLITE-3

4. Software tool Cmd, Browser, Sublime

5. Document tool MS Word, Fox it Reader

6. Internal Guide Dr.Vimal Parmar(Principal)

7. Submitted to Dr.Subhash Technical Campus(Dept. of MCA)

Developed By: Sejpal Hiren, Parmar Parth, Rathod Jignesh

1.7 Assumptions and Constraints

1.8 Advantages or Limitations of Proposed System

Developed By: Sejpal Hiren, Parmar Parth, Rathod Jignesh

At he heart of systems analysis is a detailed understanding of all important facets of

2.2 Targeted Users

2.3Tools and Technology

Developed By: Sejpal Hiren, Parmar Parth, Rathod Jignesh

Developed By: Sejpal Hiren, Parmar Parth, Rathod Jignesh

Developed By: Sejpal Hiren, Parmar Parth, Rathod Jignesh

3.2 Class Diagram

A class diagram is an illustration of the relationships and source code dependencies

Developed By: Sejpal Hiren, Parmar Parth, Rathod Jignesh

users category_table product_table

stated user_address order_ref_table

pincode product_quantity order_ref_rate

Developed By: Sejpal Hiren, Parmar Parth, Rathod Jignesh

Developed By: Sejpal Hiren, Parmar Parth, Rathod Jignesh

customer System Interface Cart Checkout Order

For shopping Process

Developed By: Sejpal Hiren, Parmar Parth, Rathod Jignesh

3.4 Activity Diagram

Activity diagrams are graphical representations of workflows of stepwise activities

Purpose of Activity Diagrams

Developed By: Sejpal Hiren, Parmar Parth, Rathod Jignesh

[if like item]

[done with shopping]

Activity Diagram of Online Shopping

Developed By: Sejpal Hiren, Parmar Parth, Rathod Jignesh

3.5 Data Dictionary

Data Dictionary Reports allow m-Power developers to better understand the

 Viewing the Dictionary Dashboard, this provides numerous key statistics.

Developed By: Sejpal Hiren, Parmar Parth, Rathod Jignesh

Developed By: Sejpal Hiren, Parmar Parth, Rathod Jignesh

4.1 Coding Standards

Namespace and Class names

Developed By: Sejpal Hiren, Parmar Parth, Rathod Jignesh

 All filenames are UpperCamelCase.

File naming in Flow

Developed By: Sejpal Hiren, Parmar Parth, Rathod Jignesh