1final - Report MERN Stack
1final - Report MERN Stack
Chandkheda,Ahmedaba
dAffiliated
GYANMANJARI COLLEGE OF
COMPUTER APPLICATION
A
Project
ReportOn
Blissful Bazar
Under subject of
SOFTWARE PROJECT-1
M.C.A, Semester – II
Submitted By
Jelanshi Shah 225750694034
Krishna Patel 225750694031
CERTIFICATE
ACKNOWLEDGEMENT
We have taken efforts in this project. However, it would not have been possible without
the kind of support and help of many individuals and organizations. We would like to
extend our sincere thanks to all of them.
I am highly indebted to Prof. Mansi Gosai for their guidance and constant supervision as
well as for providing necessary information regarding the project & also for their support
in completing the project. We would like to express our special gratitude and thanks to
faculties forgiving me such attention and time.
Our thanks and appreciations also go to my colleague for guiding me during the project
andpeople who have willingly helped me out with their abilities.
I sincerely appreciate the inspiration; support and guidance of all those people who have
been instrumental in making this project a success. We would also like to thank all the
faculty members of M.C.A department for their critical advice and guidance without which
this projectwould not have been possible.
Last but not the least I place a deep sense of gratitude to our family members and our
friends who have been a constant source of inspiration during the preparation of this
project work.
Thank you.
Prepared by: -
Jelanshi Shah
Krishna Patel
205750694002
Jelanshi Shah (225750694034) I
Krishna Patel (225750694031)
GMCC,Bhavnagar Blissful Bazar
ABSTRACT
205750694002 II
Jelanshi Shah (225750694034)
Krishna Patel (225750694031)
GMCC,Bhavnagar Blissful Bazar
INDEX
SrNo. Chapter Name PageNo.
ACKNOWLEDGEMENT I
ABSTRACT II
1. Chapter 1: Introduction 1
1.1 Existing System 1
1.2 Need For New System 1
1.3 Objective Of The New System 1
1.4 Problem Definition 2
1.5 Core Components 2
1.6 Project Profile 3
1.7 Assumptions And Constraints 4
1.8 Advantages And Limitation Of Proposed System 4
2. Chapter 2:RequirementDetermination&Analysis 6
2.1RequirementDetermination 6
2.2TargetedUser 6
3. Chapter 3:SystemDesign 7
3.1UseCaseDiagram 7
3.2DataDictionary 12
4. Chapter 4:Development 19
4.1CodingStandards 19
4.2ScreenShots 22
5. Chapter 5:AgileDocumentation 35
5.1 Agile project chare 35
5.2 Agile Project Plan 35
5.3 User’s story 36
5.4 Agile Release plan 36
5.5 Agile Sprint Backlog 37
5.6 Agile Test plan 37
5.7 Earnedvalue 37
6. Chapter 6:ProposedEnhancement 38
7. Chapter7:Conclusion 39
8. Chapter8:Bibliography 40
205750694002
Jelanshi Shah (225750694034) III
Krishna Patel (225750694031)
GMCC,Bhavnagar Blissful Bazar
1. Introduction
1.1 Existing System:
The existing E-commerce systems often lack certain features and may not provide a
user-friendly experience. Therefore, the development of "Blissful Bazar" aims to
overcome these limitations and deliver a robust and efficient online shopping
platform.
The need for the new system arises from the growing demand for a user-friendly,
feature-rich, and reliable E-commerce platform that caters to the diverse needs of
customers.
Order management
Database MongoDB
Tools Vs code
1.7.1 Assumption
▪ Users will have access to a stable internet connection.
▪ Product information and image will be provide by vendors in a standardized format.
▪ The project must be completed within the given time frame and budget.
1.7.2 Constraints
▪ Internet connection is mandatory.
▪ Browser is mandatory.
▪ Project must be completed within the given time frame and budget.
Advantages:
▪ Enhanced user experience with a modern and intuitive interface.
▪ Increased sales and revenue potential due to a broader reach.
▪ Better customer engagement through personalized recommendations.
▪ Efficient order and inventory management.
Limitations:
▪ Initial setup cost and maintenance requirements.
▪ Dependency on third-party payment gateway.
▪ Potential security risks related to online transactions.
▪ Users should be able to register accounts, log in, and manage their profiles
securely.
▪ Implement a robust search and filtering system to help users find product
quickly.
▪ Users should be able to add items to their carts, view cart contents, and
proceed to checkout.
3. System Design
4. Development
1 Naming Convention:
2 Organization of Files :
▪ This is section that defines how we need to place the files used in the website
and under what section:
▪ We should follow MVC architecture. In which all the model classes or
fragment classes should be in model folder.
▪ All controllers should be separate and view should be separate as well.
▪ There should be a section to define all Constants for the app. The constants
should include the following:
▪ Constants for dimensions. For E.g.: row height = 80, number of cells = 5 etc.
▪ Constants for URLs used in the app. This can be for projects related to web
services. This should be at one place.
▪ All the image name should be defined at one place and there should be no
hard-code values in the code.
▪ All the code that is used repeatedly should be defined in macros whenever
possible.
▪ All images, videos and media should be in “resources” folder. There should
be sub folders to save images, medias etc.
Formatting and indentation are crucial aspects of coding in the MERN stack when
developing an E-commerce website. Consistent and well-organized code improves
readability, reduces errors, and enhances collaboration among developers. Here are some
formatting and indentation guidelines for the MERN stack E-commerce website:
▪ Files should be formatted with \n as the line ending, \r\n(Windows line endings).
▪ All text files should end in a single newline (\n). This avoids the verbose "\
No newline at end of file" patch warning and makes patches easier to read
since it's clearer what is being changed when lines are added to the end of a
file.
2 Operators:
▪ All binary operators (operators that come between two values), such as +, -, =, !=,
==, >, etc. should havea space before and after the operator, forreadability.
3 Casting:
▪ Put a space between the (type) and the $variable in a cast: (int)
$my_number.
4 Control Structures:
▪ Control statements should have one space between the control
keyword and opening parenthesis, to distinguish them from function
calls.
▪ Use curly braces for all control structures, even for single-line statements,
to prevent potential bugs.
▪ Properly indent the code within control structures for better code
organization.
User panel
5. Agile Documentaion
The Agile project plan provides a detailed breakdown of the development process,
including iterations, timelines, and milestones. It helps in effective project tracking
and progress evaluation.
Contents of agile project plan :
Iteration Schedule: A list of iterations (sprints) with start and end dates.
Feature Set : Features and functionalities planned for each iteration.
Deliverables : The expected deliverables for each iteration.
Resource Allocation : Allocation of resources (development team, tools, etc.)
for each iteration.
Milestones : Key milestones to track project progress.
Risk Assessment : Identification and assessment of potential risks during the
project.
Contingency Plan : Contingency strategies to handle unforeseen issues or
delays.
Review and Evaluation : Regular review and evaluation schedule to assess
progress and make improvements.
User stories describe the features or functionalities from the perspective of end-users,
helping to understand their needs and expectations.
Examples of user stories :
As a customer, I want to be able to search for products based on specific
categories or keywords.
As a user, I want to view my order history and track the status of my current
orders.
As a vendor, I want to manage my product listings, including adding new
products and updating existing ones.
▪ The Agile release plan defines the schedule and feature sets for each release of
the Blissful Bazar website.
▪ The Agile sprint backlog is a list of tasks and user stories to be completed within
each sprint (iteration).
▪ Contents of agile sprint backlog :
List of User Stories: The user stories that will be worked on in the current
sprint.
Task Breakdown: Breakdown of user stories into specific tasks with
estimated effort and assignment to team members.
Status Tracking: Tracking the progress of each task during the sprint.
6. Proposed Enhancements
● In future planning we are planning to add social media integration in this product if it
is possible so it is very easy to manage a social media of a blissful bazar and send a
product photos and many more videos and other things.
● In future we are planning to put a payment get way automatic to send a salary to all
person based on there work timing.
● This is a main thing for all we want to Enhancement in our product
7. Conclusion
● In conclusion I only want to say this is a mainly focus product to sell only andit make
a easy and reliable solution for all product instead of manual selling systems.
● This system is purely selling product It can manage a web application and many more
things and it is easy to understand for a professionals and make a reliable solution for
a call centers.
8. Bibliography