Professional Documents
Culture Documents
Project
Project
Project
On
Local Market
Submitted to
LOVELY PROFESSIONAL UNIVERSITY
Submitted by Supervised By
Akash Jaiswal (11801300) Dr. Mudasir Ashraf
Mohd Hanzla (11801310)
Ravi Kumar (11718599) (Lovely Professional University)
Sameer Mathew Chand (11616357)
I Title Page i
II Certificate ii
III Acknowledgement iii
1) Introduction
2) Objective
3) System Analysis
-- Identification of Need
--Preliminary Investigation
4) DFD (0Level, 1-Leveland2Level/ Table structure etc.)
5) S/W & H/W Requirement Specification
6) System Design
7) Screen Shots
8) Validation & Testing
9) Implementation and Maintenance
10) System Security measures
11) Various types of Reports/Modules
12) Future scope of the project
CERTIFICATE
This is to certify that the declaration statement made by this group of students is correct to the best
of my knowledge and belief. They have completed this Capstone Project named “Local Market”
under my guidance and supervision. The present work is the result of their original investigation,
effort and study and market research. No part of the work has ever been submitted for any other
degree at any University. The Capstone Project is fit for the submission and partial fulfillment of
the conditions for the award of BCA degree Program from Lovely Professional University,
Phagwara.
It is a genuine pleasure to express our deep sense of thanks and gratitude to our mentor or guide
Dr. Mudasir Ashraf Assistant Professor, Lovely Professional University for providing me the
guidance to work on the capstone project entitled “Local Market”. He dedication and keen interest
above all his overwhelming attitude to help his students had been solely and mainly responsible
for completing my Project. He timely suggestions, meticulous scrutiny, scholarly advice, and
friendly approach have helped us to a very great extent to accomplish this task. I owe a deep sense
of gratitude to all my faculty members whose teachings have contributed to this project directly or
indirectly. I would also like to thank Lovely Professional University for providing me the
opportunity to work on this project.
2. Objective
1. Awareness – Getting your brand or product known
Measures can include number of app downloads, how many sessions each user has,
how many pages views that have or brand recognition (if your company tracks this.
3. Communication – This depends upon what and to/with whom you are trying to
communicate
Measures can include the number of active users, how often they open the app, which
pages they visit, how often they send or receive messages among target groups, what
types of messages or even what time they are sending messages.
4. Interaction (Engagement) – Are your users doing what you wanted them to do?
Measures include how many users are active, how often do they use the app or how
long do they stay. Additionally, do they perform the action that you envisaged e.g.,
upload photographs, chat, buy, share etc.?
5. Loyalty – Similar to Engagement but you may want to measure specific loyalty
program components
Measures may include members registered, new members signed up, sessions, points
earned or redeemed.
3. System Analysis
Identification of Need: -
• Zomato: - This has most of similar features with our platform but is deals
with restaurant and food stores rather than groceries and general stores.
• Jiomart:- This platform is similar features to ours but major problem is
availability is only major cities and it is centralized based means it have
warehouse in major cities and sold product and deliver from there which
even further cause the decline of local retailers.
4. DFD
• DFD 0-LEVEL
• DFD 1-LEVEL
• DFD 2-LEVEL
• DFD 3-LEVEL
INTRODUCTION
Software requirement specification (SRS) document provides an overview of the
entire project’s purpose and scope. It also concentrates on the capabilities required
by the developers and users while developing the android application software and
its features.
Welcome Page
This is the initial page displayed by all access to the application. The welcome page
of the app contains the following function:
• Login as User
Function to login for Users.
• Login as Seller
Function to login for Seller.
Login
• Existing users/seller have to login to the system to use the platform.
• Users/sellers need to provide their email and password and click the login
button.
Registration
• New users/sellers are required to register before they can use the platform.
• Users must enter name, email, pin code and password to register.
• Seller must enter name, email, password, store name, address, and store name
to register.
Dashboard
• Here user can see store name and products from them and can purchase that.
• And for seller have function to add/update their products and get the selling
orders.
NON-FUNCTIONAL REQUIREMENTS: -
Usability
User interface
Accessibility
Users can access the application from any device and anywhere on the internet.
Performance
• The performance may vary depending upon the hardware components of the
user’s device.
• The application may take initial load time depending on the internet
connection strength.
Software Requirements
• Operating system: Any
• Back-end tool: MongoDB, VSC, Postman
• Front-end Tool: VSC, Browser
• Technology: MongoDB, Node.js, HTML, CSS
6. System Design
Use-Case Diagram:
ER Diagram:
Flow Chart:
7. Screen Shots
8. Validation & Testing
This is the testing in which overall application is tested for any bugs.
User Acceptance Test: It is a type of testing in which tests are performed by the
end user or the client to verify / accept the software. This test is usually performed
by companies as the last phase of testing in which user is using the software and
the functioning of the software is shared with the company. This is so that the
software can be further improvised and any bug which was not detected in the
previous testing can be found if any and removed.
Image Sample:
9. IMPLEMENTATION AND MAINTAINCE
System Security Measures here refer to the security measures taken at the application
level to prevent any data in the application to leak outside to any third party or
unauthorized user. It consists of all the measures taken to stop such events and
protect the data integrity.
Application Security measures are all the processes and testing done to prevent any
unauthorized user from accessing the user data.
To maximize the System Security, we need to minimize these risks as much as
possible. Security can be compromised in case of:
a) Breach of confidentiality
b) Breach of integrity
c) Breach of availability
d) Theft of Service
e) Denial of Service
Breach of Confidentiality refers to the unauthorized access to the data that should
not be available normally.
Breach of integrity refers to the unauthorized modification as such a user
modifying other users’ data.
Breach of availability refers to the unauthorized deletion of another or many
users.
Theft of Service refers to when data is being stolen by any third-party API or any
other service or software.
Denial of Service refers to any attack or accident that stops services provided by
the software / application.
These risks are greatly minimized by the using a three-layer architecture in our
application this provides much security as the user has no access to the whole data
but only the perception / user layer which interacts with application layer and at last
the data layer.
This makes difficult for any leak of data as the application layer will act as filter
for such accesses.
Other than this the System Security is done by:
A) Stopping unauthorized access: this is done by creating user's id and
providing services only to the users who enter their login credentials correctly.
This is applied in the application by using Login page to identify the user.
B) Maintaining Secrecy: The secrecy is maintained in an application by limiting
the data that the user can access and modify. The user can modify data in the
data layer only by using the application layer which stops any deletion or
modification being done. The user has access to read the data of other, but he
can write the data that is his only. This is applied by the network layer and
presentation layer only giving access to these functions.
To maintain the user from accessing the unauthorized data it is each and every
request of user is to pass through validation. For example, Fetching the
account of another user.
C) Availability: The User must not be able to access all the resources of the data
layer. This kind of situation should not occur in any case to make sure there is
legitimate use of the software resources.
Availability is maintained by making sure that the data in the application is
flowing as expected. Many tests performed in the validation Check Step is to
make sure there is no threat to availability of the data service. For example,
the Data Fetching and the services functionality which is checked in unit
testing and integration testing.