Internship (Industry)

Report

By
Bhagyashri Bharat Patil

(232121036)

Department of Master of Computer

Application
The Shirpur Education Society’s

R. C. Patel Institute of Technology, Shirpur - 425405.

[2024-25]
 Internship (Industry) Report
In partial fulfillment of requirements for the degree of
Master of Computer Application
Submitted By
Bhagyashri Bharat Patil
(232121036)

Under the Supervision of

Ms. Rupali Gaikwad

Paarsh Infotech,
Nashik

The Shirpur Education Society’s

R. C. Patel Institute of Technology, Shirpur - 425405.
Department of Master of Computer Application

[2024-25]
 The Shirpur Education Society’s

R. C. Patel Institute of Technology

Shirpur, Dist. Dhule (M.S.)
Department of Master of Computer Application
CERTIFICATE
This is to certify that an Internship (Industry) Report (Semester- I V )
submitted by Bhagyashri Bharat Patil (232121036) under the
supervision of Prof. H.O.Borase in partial fulfillment of the
requirement for the degree of Master of Computer Application of R. C.
Patel Institute of Technology, Shirpur affiliated to Dr. Babasaheb
Ambedkar Technological University, Lonere during the academic
year 2024-25.
Date:
Place: Shirpur

Ms. Rupali Gaikwad Prof. H.O.Borase

Industry Mentor Institute Internship Mentor

Prof. Dr. D.R. Patil Prof. Dr. J.B. Patil

Head of Department Director

 Acknowledgment

We are deeply grateful to the MCA Department of RCPIT, Shirpur, for the in-
valuable opportunity to work on our semester project. Under the guidance of Prof.
Ms. Rupali Gaikwad, our esteemed mentor, we received invaluable suggestions,
insightful ideas, and unwavering support, leading to the successful completion of our
project. We sincerely appreciate his dedication, expertise, and patient guidance.
Our heartfelt thanks also go to Prof. Dr. D. R. Patil, Head of the MCA De-
partment, for his constant encouragement, cooperation, and indispensable leadership
throughout the project. We are grateful for the opportunities he provided us to learn
and grow, and we deeply appreciate his contribution to the project’s success through
assistance, support, and collaborative efforts.
Furthermore, we express profound appreciation to Prof. Dr. J. B. Patil, the
Director of RCPIT, for his unwavering support. Working under the mentorship of
these responsible and talented individuals, we efficiently completed our project within
the given time frame.

Bhagyashri Bharat Patil

 OFFERS LETTER

Figure 1: INTERNSHIPS OFFER LETTER

 R. C. P. I. T., Shirpur

Figure 2: INTERNSHIPS COMPLETION CERTIFICATE

 Abstract
The E-Marketplace project aims to develop a dynamic and secure web-based plat-
form that facilitates online buying and selling of products by connecting vendors and
customers in a seamless digital environment. The system is designed to simulate the
functionalities of a real-world marketplace, offering features such as user registration,
product listing, category-wise browsing, secure payment integration, order tracking,
and customer reviews.
This project addresses key issues in traditional commerce such as geographical
limitations, limited customer reach, and operational inefficiencies by leveraging in-
ternet technologies. The application is built using a robust architecture compris-
ing front-end technologies like HTML, CSS, JavaScript, and backend support with
PHP/Node.js and a MySQL/MongoDB database. Key components include an in-
tuitive user interface, an admin dashboard for managing users and inventory, and a
secure authentication system.
Additional features like personalized recommendations, responsive design for mo-
bile accessibility, and real-time notification systems enhance user experience and en-
gagement. The system also supports vendor-side login for inventory and order man-
agement.
The E-Marketplace project not only streamlines e-commerce operations but also
opens new opportunities for small and medium enterprises to reach broader markets,
thus contributing to digital economic growth.
Contents

1 INTRODUCTION 1
1.1 Introduction of the Project E-Market Place: . . . . . . . . . . . . . . 1
1.1.1 Functionalities provided by E-Market Place are as follows: . . 2
1.1.2 Objective of Project on E-Market Place: . . . . . . . . . . . . 2
1.2 Problem Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
1.2.1 Features of Proposed System . . . . . . . . . . . . . . . . . . . 3
1.3 Following points should be well considered: . . . . . . . . . . . . . . . 3

2 LITERATURE SURVEY 5
2.1 Technical Feasibility . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
2.2 Economical Feasibility . . . . . . . . . . . . . . . . . . . . . . . . . . 5
2.3 Initial Costs : . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
2.4 Ongoing Costs : . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
2.5 Revenue Streams : . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
2.6 ROI Analysis : . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
2.7 Legal Feasibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
2.8 Operational Feasibility . . . . . . . . . . . . . . . . . . . . . . . . . . 7

3 SYSTEM DEVELOPMENT 9
3.1 System Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
3.1.1 System Features . . . . . . . . . . . . . . . . . . . . . . . . . . 10
3.1.2 User Management . . . . . . . . . . . . . . . . . . . . . . . . . 10
3.1.3 Product Management . . . . . . . . . . . . . . . . . . . . . . . 10
3.2 Shopping Cart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

i
 R. C. P. I. T., Shirpur

3.3 Order Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

3.4 Admin Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
3.5 Existing System of E-Market Place: . . . . . . . . . . . . . . . . . . . 11
3.6 Proposed System of E-Market Place: . . . . . . . . . . . . . . . . . . 11
3.7 Objective of the System . . . . . . . . . . . . . . . . . . . . . . . . . 12

4 Preliminary Design 13
4.1 Tools of data flow strategy . . . . . . . . . . . . . . . . . . . . . . . . 13
4.1.1 Data flow analysis makes use of the following tools : . . . . . . 13
4.2 Use Case Model of the Project: . . . . . . . . . . . . . . . . . . . . . 13
4.3 Entity Relationship Diagram . . . . . . . . . . . . . . . . . . . . . . . 15
4.4 Data Flow Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
4.5 What is UML? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
4.6 Notations and meta-models: . . . . . . . . . . . . . . . . . . . . . . . 22
4.6.1 Class Diagram: . . . . . . . . . . . . . . . . . . . . . . . . . . 22

5 System Requirement Analysis 24

5.0.1 Software Requirement Specification . . . . . . . . . . . . . . . 24
5.0.2 Tools/Platform. Hardware and Software Requirement specifi-
cations: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
5.1 Scope of the project E-Market Place . . . . . . . . . . . . . . . . . . 25
5.2 Project Planning: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
5.3 Project Scheduling: . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
5.4 GANTT CHART: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
5.5 Technical Specification . . . . . . . . . . . . . . . . . . . . . . . . . . 32
5.5.1 Project Category . . . . . . . . . . . . . . . . . . . . . . . . . 32
5.5.2 Brief Introduction about RDBSM . . . . . . . . . . . . . . . . 32
5.6 JSP(Java Server Pages): . . . . . . . . . . . . . . . . . . . . . . . . . 33
5.7 Implementation Methodology: . . . . . . . . . . . . . . . . . . . . . . 35

6 Detailed Design 38
6.1 Data Dictionary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

ii
 R. C. P. I. T., Shirpur

6.2 Input and Output Design :- . . . . . . . . . . . . . . . . . . . . . . . 39

7 CONCLUSIONS 46
7.1 Conclusions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
7.2 Future Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
7.3 Limitation of Project on E-Market Place . . . . . . . . . . . . . . . . 47

BIBLIOGRAPHY 48

iii
Chapter 1

INTRODUCTION

1.1 Introduction of the Project E-Market Place:

The ”E-Market Place” has been developed to override the problems prevailing in
the practicing manual system. This software is supported to eliminate and in some
cases reduce the hardships faced by this existing system. Moreover this system is
designed for the particular need of the company to carry out operations in a smooth
and effective manner.
The application is reduced as much as possible to avoid errors while entering the
data. It also provides error message while entering invalid data. No formal knowledge
is needed for the user to use this system. Thus by this all it proves it is user-friendly.
E-Market Place , as described above, can lead to error free, secure, reliable and fast
management system. It can assist the user to concentrate on their other activities
rather to concentrate on the record keeping. Thus it will help organization in better
utilization of resources.
Every organization, whether big or small, has challenges to overcome and man-
aging the information of Product Type, Product, Customer, Payment, Order. Every
E-Market Place has different Product needs, therefore we design exclusive employee
management systems that are adapted to your managerial requirements. This is de-
signed to assist in strategic planning, and will help you ensure that your organization
is equipped with the right level of information and details for your future goals. Also,
for those busy executive who are always on the go, our systems come with remote

1
 R. C. P. I. T., Shirpur

access features, which will allow you to manage your workforce anytime, at all times.
These
systems will ultimately allow you to better manage resources.

1.1.1 Functionalities provided by E-Market Place are as fol-

lows:

• Provides the searching facilities based on various factors. Such as Product, Vendor,
Customer, Order. • E-Market Place also manage the Payment details online for
Customer details, Order details, Product. • It tracks all the information of Product
Type, Payment, Customer etc. • Manage the information of Product Type and Shows
the information and description of the Product, Vendor. • To increase efficiency of
managing the Product, Product Type . • It deals with monitoring the information
and transactions of Customer. • Manage the information of Product • Editing, adding
and updating of Records is improved which results in proper resource management of
Product data. 8 E-Market Place • Manage the information of Customer • Integration
of all records of Order.

1.1.2 Objective of Project on E-Market Place:

The main objective of the Project on E-Market Place is to manage the details of
Product, Product Type, Vendor, Customer, Order. It manages all the information
about Product, Payment, Order, Product. The project is totally built at administra-
tive end and thus only the administrator is guaranteed the access. The purpose of the
project is to build an application program to reduce the manual work for managing
the Product, Product Type, Payment, Vendor. It tracks all the details about the
Vendor, Customer, Order.

1.2 Problem Definition

The old manual system was suffering from a series of drawbacks. Since whole of the
system was to be maintained with hands the process of keeping, maintaining and

2
 R. C. P. I. T., Shirpur

retrieving the information was very tedious and lengthy. The records were never used
to be in a systematic order. there used to be lots of difficulties in associating any
particular transaction with a particular context. If any information was to be
found it was required to go through the different registers, documents there would
never exist anything like report generation. There would always be unnecessary
consumption of time while entering records and retrieving records. One more problem
was that it was very difficult to find errors while entering the records. Once the records
were entered it was very difficult to update these records. The reason behind it is
that there is lot of information to be maintained and have to be kept in mind while
running the business For this reason we have provided features Present system is
partially automated (computerized), actually existing system is quite laborious as
one has to enter same information at three different places.

1.2.1 Features of Proposed System

1. Dynamic and Attractive Website: A visually appealing interface that engages

users and provides authentic information. 2. Comprehensive Product Information:
Detailed product descriptions, images, and reviews to help users make informed pur-
chasing decisions. 10 E-Market Place 3. Comparison Tools: Enables users to com-
pare prices and features across different e-commerce websites. 4. Easy Accessibility:
User-friendly navigation and accessibility features for seamless browsing and shopping
experience. 5. Return Policy: Allows users to return products easily if dissatisfied,
enhancing customer satisfaction and trust. 6. Advanced Delivery Mechanism: Inte-
gration of technology such as flying robots and GPS for efficient and timely product
delivery.

1.3 Following points should be well considered:

• Documents and reports that must be provided by the new system: there can also be
few reports, which can help management in decision-making and cost controlling, but
since these reports do not get required attention, such kind of reports and information
were also identified and given required attention. • Details of the information needed

3
 R. C. P. I. T., Shirpur

for each document and report. • The required frequency and distribution for each
document.
• Probable sources of information for each document and report. • With the
implementation of computerized system, the task of keeping records in an organized
manner will be solved. The greatest of all is the retrieval of information, which will
be at the click of the mouse. So the proposed system helps in saving the time in
different operations and making information flow easy giving valuable reports.

4
Chapter 2

LITERATURE SURVEY

Feasibility study includes consideration of all the possible ways to provide a solution
to the given problem. The proposed solution should satisfy all the user requirements
and should be flexible enough so that future changes can be easily done based on the
future upcoming requirements.

2.1 Technical Feasibility

This included the study of function, performance and constraints that may affect the
ability to achieve an acceptable system. For this feasibility study, we studied complete
functionality to be provided in the system, as described in the System Requirement
Specification (SRS), and checked if everything was possible using different type of
front-end and back-end platforms. There is lot of security, accuracy and reliability
in system by considering the above reason the system is technically feasible.

2.2 Economical Feasibility

This aspect assesses whether the technical resources and skills are available to com-
plete the project successfully.

• All hardware and software cost has to be borne by the organization.

• Overall we have estimated that the benefits the organization is going to receive from

5
 R. C. P. I. T., Shirpur

the proposed system will surely overcome the initial costs and the later on running
cost for system.

2.3 Initial Costs :

Development costs (salaries, equipment, software licenses)

• Hosting and domain registration fees

• Marketing and promotional expenses.

2.4 Ongoing Costs :

• Maintenance and support

• Continuous development and updates

• Hosting and bandwidth expenses

2.5 Revenue Streams :

• Sales of products

• Advertising and affiliate marketing

• Subscription models (e.g., premium membership)

2.6 ROI Analysis :

With a well-executed marketing strategy and a user-friendly interface, the website
can attract a substantial user base. E-commerce platforms typically see a high ROI
due to the scalability of online sales and low overhead costs compared to physical
stores.

6
 R. C. P. I. T., Shirpur

2.7 Legal Feasibility

This aspect checks for legal considerations, regulations, and compliance requirements.

• Data Protection : Compliance with data protection laws (e.g., GDPR for EU cus-
tomers, CCPA for California residents) is crucial. This includes secure handling of
user data and clear privacy policies.

• E-commerce Regulations : Adherence to e-commerce regulations, including con-

sumer protection laws, digital transaction laws, and refund policies.

• Intellectual Property : Ensuring no infringement on intellectual property, including

trademarks, copyrights, and software licenses.

• Payment Processing : Compliance with financial regulations and payment gateway

requirements (e.g., PCI-DSS for credit card processing).

2.8 Operational Feasibility

No doubt the proposed system is fully GUI based that is very user friendly and all
inputs to be taken all self-explanatory even to a layman. Besides, a proper training
has been conducted to let know the essence of the system to the users so that they
feel comfortable with new system. As far our study is concerned the clients are
comfortable and happy as the system has cut down their loads and doing.
In this phase, a logical system is built which fulfils the given requirements. Design
phase of software development deals with transforming the clients requirements into
a logically working system. Normally, design is performed in the following in the
following two steps:
Primary Design Phase In this phase, the system is designed at block level. The
blocks are created on the basis of analysis done in the problem identification phase.
Different blocks are created for different functions emphasis is put on minimising the
information flow between blocks. Thus, all activities which
require more interaction are kept in one block.
Secondary Design Phase: In the secondary phase the detailed design of every
block is performed. The general tasks involved in the design process are the following:

7
 R. C. P. I. T., Shirpur

Design various blocks for overall system processes.

• Design smaller, compact and workable modules in each block.

• Design various database structures.

• Specify details of programs to achieve desired functionality.

• Design the form of inputs, and outputs of the system.

• Perform documentation of the design.

8
Chapter 3

SYSTEM DEVELOPMENT

System analysis is a process of gathering and interpreting facts, diagnosing prob-

lems and the information about the E-Market Place to recommend improvements on
the system. It is a problem solving activity that requires intensive communication
between the system users and system developers. System analysis or study is an
important phase of any system development process. The system is studied to the
minutest detail and analyzed. The system analyst plays the role of the interrogator
and dwells deep into the working of the present system.
Preliminary study is the process of gathering and interpreting
facts, using the information for further studies on the system. Preliminary study
is problem solving activity that requires intensive communication between the system
users and system developers. It does various feasibility studies. In these studies a
rough figure of the system activities can be obtained, from which the decision about
the strategies to be followed for effective system study and analysis can be taken.

3.1 System Overview

The e-commerce website will enable users to browse products, add items to their
shopping cart, and complete purchases securely. Administrators will have the ability
to manage products, orders, and user accounts through a dedicated admin panel.

9
 R. C. P. I. T., Shirpur

3.1.1 System Features

3.1.2 User Management

User Registration and Login : Users can register with their email and password.
Authentication will be managed using Django’s built-in user authentication system

• Profile Management : Users can view and update their profile information, including
name, address, and password.

• Password Recovery : Users can reset their password via email verification if they
forget it.

3.1.3 Product Management

• Product Listing : Products are listed with details like name, price, description, and
images. Users can browse products by category or search for specific items

• Product Details : Detailed view of each product, including specifications, reviews,

and availability status.

• Categories : Products are organized into categories for easier navigation.

3.2 Shopping Cart

• Add to Cart : Users can add products to their cart from the product listing or
detail pages.

• Update Cart : Users can update the quantity of items in their cart or remove items.

• View Cart : Users can view their cart at any time to see the products added, total
price, and proceed to checkout.

3.3 Order Management

• Checkout Process : Users can enter shipping details and choose a payment method
to complete their purchase.

10
 R. C. P. I. T., Shirpur

• Order Confirmation : After payment, users receive an order confirmation with

details and estimated delivery time.

• Order History : Users can view their past orders and order statuses.

3.4 Admin Panel

• Dashboard : Overview of sales, orders, and user activities.

• User Management : Admins can view, add, update, or delete user accounts.

• Product Management : Admins can add new products, update existing ones, and
manage inventory.

• Order Management : Admins can view all orders, update order statuses, and handle
customer queries.

3.5 Existing System of E-Market Place:

In the existing system the exams are done only manually but in proposed system we
have to computerize the exams using this application.

• Lack of security of data

• More man power

• Time consuming.

• Consumes large volume of pare work.

• Needs manual calculations

• No direct role for the higher officials.

3.6 Proposed System of E-Market Place:

The aim of proposed system is to develop a system of improved facilities. The pro-
posed system can overcome all the limitations of the existing system. The system
provides proper security and reduces the manual work.

11
 R. C. P. I. T., Shirpur

• Security of data.

• Ensure data accuracy’s.

• Proper control of the higher officials.

• Minimize manual data entry.

• Minimum time needed for the various processing.

• Greater efficiency.

• Better service.

• User friendliness and interactive.

• Minimum time required.

3.7 Objective of the System

All the steps required in the software-analysis process related to this project (product
function, user characteristics, functional and nonfunctional requirements, constraints,
assumptions, and dependencies for the online shopping cart application) are described
in the following sections.

12
Chapter 4

Preliminary Design

4.1 Tools of data flow strategy

Data flow strategy shows the use of data in the system pictorially. The tools use in
following this strategy show all the essential features of the system and how they fit
together. It can be difficult to fully understand a business process through a verbal
description alone; data flow tools help by illustrating the essential components of a
system and their interactions.

4.1.1 Data flow analysis makes use of the following tools :

• Use Case Model of the Project

• Entity Relationship Diagram

• Data Flow Diagrams

• System Flow Diagram

4.2 Use Case Model of the Project:

The use case model for any system consists of ”use cases”. Use cases represent
different ways in which the system can be used by the user. A simple way to find
all the use case of a system is to ask the questions ”What the user can do using

13
 R. C. P. I. T., Shirpur

the system?” The use cases partition the system behavior into transactions such that
each transaction performs some useful action from the users’ point of view.
In the use case diagram each use case is represented by an ellipse with the name of
use case written inside the ellipse. All the ellipses of the system are enclosed with in a
rectangle which represents the system boundary. The name of system being module
appears inside the rectangle. The different users of the system are represented by
using stick person icon. The stick person icon is normally referred to as an Actor.
The line connecting actor and the use cases is called the communication relationship.

Figure 4.1: Use Case Diagram for Admin :

14
 R. C. P. I. T., Shirpur

Figure 4.2: Use Case Diagram for User :-

4.3 Entity Relationship Diagram

E-R Model is a popular high level conceptual data model. This model and its varia-
tions are frequently used for the conceptual design
of database application and many database design tools employ its concept.
A database that confirms to an E-R diagram can be represented by a collecton of
tables in the relational system. The mapping of E-R diagram to the entities are:

• The entities and their relationships between the Attributes.

• Relations 1. Many-to-many 2. Many-to-one 3. One-to-many 4. One-to-one

15
 R. C. P. I. T., Shirpur

• Weak entities

• Sub-type and super-type

• figure are shown using the following conventions.

• An entity is shown in rectangle.

• A diamond represent the relationship among number of entities.

• The attributes shown as ovals are connected to the entities or relationship by lines.

• Diamond,oval and relationships are labeled.

Figure 4.3: ER Diagram

• Model is an abstraction process that hides super details while

16
 R. C. P. I. T., Shirpur

highlighting details relation to application at end.

• A data model is a mechanism that provides this abstraction for database application.

• Data modeling is used for representing entities and their relationship in the database.

• Entities are the basic units used in modeling database entities can have concrete
existence or constitute ideas or concepts.

• Entity type or entity set is a group of similar objects concern to an organization for
which it maintain data

• Properties are characteristics of an entity also called as attributes.

• A key is a single attribute or combination of 2 or more attributes of an entity set

is used to identify one or more instances of the set.

• In relational model we represent the entity by a relation and use tuples to represent
an instance of the entity.

• Relationship is used in data modeling to represent in association between an entity

set.

• An association between two attributes indicates that the values of the associated
attributes are independent.

4.4 Data Flow Diagram

Data flow diagram is the starting point of the design phase that functionally decom-
poses the requirements specification. A DFD consists of a series of bubbles joined by
lines. The bubbles represent data transformation and the lines represent data flows
in the system. A DFD describes what data flow rather than how they are processed,
so it does not hardware, software and data structure.
A data-flow diagram (DFD) is a graphical representation of the ”flow” of data
through an information system. DFDs can also be used for the visualization of data
processing (structured design). A data flow diagram (DFD) is a significant modeling
technique for analyzing and constructing information processes. DFD literally means

17
 R. C. P. I. T., Shirpur

an illustration that explains the course or movement of information in a process. DFD

illustrates this flow of information in a process
based on the inputs and outputs. A DFD can be referred to as a Process Model.

Figure 4.4: Data Flow Diagram

The data flow diagram is a graphical description of a system’s data and how to
Process transform the data is known as Data Flow Diagram (DFD). Unlike details flow
chart, DFDs don’t supply detail descriptions of modules that graphically describe a
system’s data and how the data interact with the system. Data flow diagram number
of symbols and the following symbols are of by DeMarco.

18
 R. C. P. I. T., Shirpur

Figure 4.5: DFD Level 1 for Admin :-

19
 R. C. P. I. T., Shirpur

Figure 4.6: DFD Level 1 for User :

20
 R. C. P. I. T., Shirpur

Figure 4.7: System Flow Diagram :-

On a DFD, data items flow from an external data source or an internal data store
to an internal data store or an external data sink, via an internal process. It is common
practice to draw a contextlevel data flow diagram first, which shows the interaction
between the system and external agents, which act as data sources and data sinks.
On the context diagram (also known as the Level 0 DFD’), the system’s interactions
with the outside world are modeled purely in terms of data flows across the system
boundary. The context diagram shows the entire system as a single process, and gives
no clues as to its internal organization.
This context-level DFD is next ”exploded”, to produce a Level 1 DFD that shows
some of the detail of the system being modeled. The Level 1 DFD shows how the
system is divided into sub-systems (processes), each of which deals with one or more
of the data flows to or from an external agent, and which together provide all of the
functionality of the system as a whole. The level 1 DFD is further spreaded and split
into more descriptive and detailed description about the project as level 2 DFC).The

21
 R. C. P. I. T., Shirpur

level 2 DFD can be a number

of data flows which will finally show the entire description of the software project.

4.5 What is UML?

UML stands for Unified Modeling Language is the successor to the wave of Object
Oriented Analysis and Design (OOA and D) methods that appeared in the late 80’s.
It most directly unifies the methods of Booch, Rumbaugh (OMT) and Jacobson. The
UML is called a modeling language, not a method. Most methods consist at least in
principle, of both a modeling language and a process. The Modeling language is that
notation that methods used to express design.

4.6 Notations and meta-models:

The notation is the graphical stuff; it is the syntax of the modeling language. For
instance, class diagram notation defines how items are concepts such as class, associ-
ation, and multiplicity is represented. These are:

4.6.1 Class Diagram:

The class diagram technique has become truly central within object oriented methods.
Virtually every method has included some variation on this technique. Class
diagram is also subject to the greatest range of modeling concept. Although the
basic elements are needed by everyone, advanced concepts are used less often. A
class diagram describes the types of objects in the system and the various kinds of
static relationship that exist among them. There are two principal kinds of static
relationship:

22
 R. C. P. I. T., Shirpur

Figure 4.8: System Flow Diagram :-

23
Chapter 5

System Requirement Analysis

5.0.1 Software Requirement Specification

The Software Requirements Specification is produced at the culmination of the anal-

ysis task. The function and performance allocated to software as part of system
engineering are refined by establishing a complete information description, a detailed
functional and behavioral description, an indication of performance requirements and
design constraints, appropriate validation criteria, and other data pertinent to re-
quirements.
The proposed system has the following requirements:

• System needs store information about new entry of Product.

• System needs to help the internal staff to keep information of

Product Type and find them as per various queries.

• System need to maintain quantity record.

• System need to keep the record of Vendor.

• System need to update and delete the record.

• System also needs a search area.

• It also needs a security system to prevent data

24
 R. C. P. I. T., Shirpur

5.0.2 Tools/Platform. Hardware and Software Requirement

specifications:

5.1 Scope of the project E-Market Place

It may help collecting perfect management in details. In a very short time, the
collection will be obvious, simple and sensible. It will help a person to know the man-
agement of passed year perfectly and vividly. It also helps in current all works relative
to E-Market Place. It will be also reduced the cost of collecting the management and
collection procedure will go on smoothly. : Software Requirements:

25
 R. C. P. I. T., Shirpur

Figure 5.1: System Flow Diagram :-

Our project aims at Business process automation, i.e. we have tried to computerize
various processes of E-Market Place.

• In computer system the person has to fill the various forms and number of copies
of the forms can be easily generated at a time.

• In computer system, it is not necessary to create the manifest but we can directly

26
 R. C. P. I. T., Shirpur

print it, which saves our time.

• To assist the staff in capturing the effort spent on their respective working areas.
To utilize resources in an efficient manner by increasing their productivity through
automation.

• The system generates types of information that can be used for various purposes.

• It satisfy the user requirement

• Be easy to understand by the user and operator

• Be easy to operate

• Have a good user interface

• Be expandable

• Delivered on schedule within the budget.

5.2 Project Planning:

Software project plan can be viewed as the following:
1 Within the organization
How the project is to be implemented? What are various constraints (time, cost,
staff)? What is market strategy?
2. With respect to the customer: Weekly or timely meetings with the cus-
tomer with presentation on status reports. Customers feedback is also taken and
further modification and developments are done. Project milestones and deliverables
are also presented to the customer.
For a successful software project. the following steps can be followed:

• Select a project

• Identifying project’s aims and objectives

• Understanding requirements and specification

• Methods of analysis, design and implementation

• Testing techniques

27
 R. C. P. I. T., Shirpur

• Documentation

• Project milestones and deliverables

• Budget allocation o Exceeding limits within control

• Project Estimates

• Cost of Time a . Size of code b . Duration c . Resource Allocation o Hardware o

Software

• Previous relevant project information

• Digital Library a . Risk Management b . Risk avoidance c . Risk detection

5.3 Project Scheduling:

An elementary Gantt chart or Timeline chart for the development plan is given below.
The plan explains the tasks versus the time (in weeks) they will take to complete.

28
 R. C. P. I. T., Shirpur

Figure 5.2: Project Scheduling:

WiS are weeks of the months, for i = PERT CHART (Program Evaluation Review
Technique) PERT chart is organized for events, activities or tasks. It is a scheduling
device that shows graphically
the order of the tasks to be performed. It enables the calculation of the critical
path. The time and cost associated along a path is calculated and the path requires
the greatest amount of elapsed time in critical path.

29
 R. C. P. I. T., Shirpur

Figure 5.3: PERT Chart representation

5.4 GANTT CHART:

It is also known as Bar chart is used exclusively for scheduling purpose. It is a project
controlling technique. It is used for scheduling. Budgeting and resourcing planning.
A Gantt is a bar chart with

30
 R. C. P. I. T., Shirpur

each bar representing activity. The bars are drawn against a time line. The length
of time planned for the activity. The Gantt chart in the figure shows the Gray parts
is slack time that is the latest by which a task has been finished.

Figure 5.4: PERT Chart representation

31
 R. C. P. I. T., Shirpur

5.5 Technical Specification

5.5.1 Project Category

Relational Database Management System (RDBMS) : This is an RDBMS based

project which is currently using MySQL for all the transaction statements. MySQL
is an open source RDBMS System.

5.5.2 Brief Introduction about RDBSM

A relational database management system (RDBMS) is a database management sys-

tem (DBMS) that is based on the relational model as invented by E. F. Codd, of
IBM’s San Jose Research Laboratory. Many popular databases currently in use are
based on the relational database model.
RDBMS have become a predominant choice for the storage of information in
new databases used for financial records, manufacturing and logistical information,
personnel data, and much more since the 1980s. Relational databases have often
replaced legacy hierarchical
databases and network databases because they are easier to understand and use.
However, relational databases have been challenged by object databases, which were
introduced in an attempt to address the object-relational impedance mismatch in
relational database, and XML databases

32
 R. C. P. I. T., Shirpur

Figure 5.5: Data Base Server

5.6 JSP(Java Server Pages):

Java Server Pages (JSP) is a technology for developing web pages that support dy-
namic content which helps developers insert java code in HTML pages by making
use of special JSP tags, most of which start with A Java Server Pages component

33
 R. C. P. I. T., Shirpur

is a type of Java servlet that is designed to fulfill the role of a user interface for a
Java web application. Web developers write JSPs as text files that combine HTML
or XHTML code, XML elements, and embedded JSP actions and commands. Using
JSP, you can collect input from users through web page forms, present records from
a database or another source, and create web pages dynamically.
JSP Architecture:
The web server needs a JSP engine ie. container to process JSP pages. The JSP
container is responsible for intercepting requests for JSP pages. This tutorial makes
use of Apache which has built-in JSP container to support JSP pages development.
A JSP container works with the Web server to provide the runtime environment and
other services a JSP needs. It knows how to understand the special elements that
are part of JSPs.

34
 R. C. P. I. T., Shirpur

Figure 5.6: JSP Architecturer

5.7 Implementation Methodology:

Model View Controller or MVC as it is popularly called, is a software design pattern
for developing web applications. A Model View Controller pattern is made up of the
following three parts:

35
 R. C. P. I. T., Shirpur

• Model - The lowest level of the pattern which is responsible for maintaining data.

• View - This is responsible for displaying all or a portion of the data to the user.

• Controller - Software Code that controls the interactions between the Model and
View.

Figure 5.7: MVC Architecturer

MVC is popular as it isolates the application logic from the user interface layer

36
 R. C. P. I. T., Shirpur

and supports separation of concerns. Here the Controller receives all requests for
the application and then works with the Model to prepare any data needed by the
View. The View then uses the data prepared by the Controller to generate a final
presentable response.

37
Chapter 6

Detailed Design

6.1 Data Dictionary

This is normally represented as the data about data. It is also termed as metadata
some times which gives the data about the data stored in the database. It defines
each data term encountered during the analysis and design of a new system. Data
elements can describe files or the processes.
Following are some major symbols used in the data dictionary:
1. = equivalent to
2. + and
3. [] either/or
4. () Optional entry
Following are some rules, which defines the construction of data dictionary entries:

• Words should be defined to understand for what they need and not the variable
need by which they may be described in the program .

• Each word must be unique. We cannot have two definition of the same client.

• Aliases or synonyms are allowed when two or more enters shows the same meaning.
For example a vendor number may also be called as customer number.

• A self-defining word should not be decomposed. It means that the reduction of

any information in to subpart should be done only if it is really required that is it
is not easy to understand directly. Data dictionary includes information such as the

38
 R. C. P. I. T., Shirpur

number of records in file, the frequency a process will run, security factor like pass
word
which user must enter to get excess to the information

6.2 Input and Output Design :-

Home Page : A home page is the default or front page of a site. It is the first page
that visitors see when they load a URL. Web managers can control the home page as
a way of directing the user experience. A home page contains the fields like Products
search bar, Our Featured products, Menu Bar and Oder List, Card, Feedback section.

39
 R. C. P. I. T., Shirpur

Figure 6.1: Home

User Registration : Register page allows new users to create accounts and pro-
vide their personal information to access the web application’s features and services.
The page should ensure a smooth and secure registration process, gathering the neces-
sary information while maintaining user privacy and data protection. The following
sections evaluate the User Register page and suggest improvements to enhance its

40
 R. C. P. I. T., Shirpur

usability and functionality.

Figure 6.2: Registration Page

Customer Login : The Login Module is a portal module that allows users to
type a user name and password to log in. A web page or an entry page to a web/mobile
application that requires user identification and authentication, regularly performed
by entering a username and password combination. The Login page provides a secure

41
 R. C. P. I. T., Shirpur

and streamlined process for users to authenticate their identity and gain access to
their accounts. It should prioritize security measures while ensuring a user-friendly
experience.

Figure 6.3: Login Page

Product List A product list page is a crucial component of any e-commerce web-
site, providing users with a comprehensive view of available products and facilitating

42
 R. C. P. I. T., Shirpur

product discovery and selection. By implementing features such as product display,

filtering and search, pagination, product actions, and inventory management, devel-
opers can create a seamless and user-friendly product browsing experience for their
customers.

Figure 6.4: Product List

Shipping Address :The shipping address section is an essential part of the

checkout process in an e-market place website, allowing users to input or edit the
address to which their purchased items will be shipped. By implementing features
such as form fields for address details, address validation, address management, and
user experience enhancements, developers can create a smooth and efficient shipping
address experience for users.

43
 R. C. P. I. T., Shirpur

Figure 6.5: Shipping Address

Make Payment : he ”Make Payment” section of an e-market place website is a

crucial part of the checkout process where users can enter their payment details and
complete their purchase. Here’s a detailed breakdown of its features and implemen-
tation.

44
 R. C. P. I. T., Shirpur

Figure 6.6: : Make Payment

45
Chapter 7

CONCLUSIONS

7.1 Conclusions
Our project is only a humble venture to satisfy the needs to manage their project
work. Several user friendly coding have also adopted. This package shall prove to be
a powerful package in satisfying all the requirements of the school. The objective of
software planning is to provide a frame work that enables the manger to make rea-
sonable estimates made within a limited time frame at the beginning of the software
project and should be updated regularly as the project progresses
At the end it is concluded that we have made effort on following points...

1. A description of the background and context of the project and its relation to work
already done in the area.

2. Made statement of the aims and objectives of the project.

3. The description of Purpose, Scope, and applicability.

4. We define the problem on which we are working in the project.

5. We describe the requirement Specifications of the system and the actions that can
be done on these things.

6. We understand the problem domain and produce a model of the system, which
describes operations that can be performed on the system.

7. We included features and operations in detail, including screen layouts. We de-

signed user interface and security issues related to system.

8. Finally the system is implemented and tested according to test cases.

46
 R. C. P. I. T., Shirpur

7.2 Future Scope

In a nutshell, it can be summarized that the future scope of the project circles around
maintaining information regarding:

1. We can add printer in future.

2. We can give more advance software for E-Market Place including more facilities.

3. We will host the platform on online servers to make it accessible worldwide.

4. Integrate multiple load balancers to distribute the loads of the system.

5. Create the master and slave database structure to reduce the

overload of the database queries.

6. Implement the backup mechanism for taking backup of codebase and database on
regular basis on different servers.

7.3 Limitation of Project on E-Market Place

Although I have put my best efforts to make the software flexible, easy to operate
but limitations cannot be ruled out even by me. Though the software presents a
broad range of options to its users some intricate options could not be covered into
it; partly because of logistic and partly due to lack of sophistication. Paucity of time
was also major constraint, thus it was not possible to make the software foolproof
and dynamic. Lack of time also compelled me to ignore some part such as storing old
result of the candidate etc.

47
Bibliography

[1] Abraham Silberschatz, Henry F. Korth, and S. Sudarshan, “Database System

Concepts”, McGraw-Hill Education, 2019.

[2] Ian Sommerville, “Software Engineering”, Addison-Wesley, 10th edition, 2016.

[3] Roger S. Pressman, “Software Engineering: A Practitioner’s Approach”,

McGraw-Hill, 9th edition, 2014.

[4] Luke Welling and Laura Thomson, “PHP and MySQL Web Development”,
Addison-Wesley, 4th edition, 2009.

[5] Bootstrap Documentation, “The World’s Most Popular Framework for Building
Responsive, Mobile-First Projects on the Web”, https://getbootstrap.com, 2020.

[6] Django Documentation, “The Web Framework for Perfectionists with Dead-
lines”, https://www.djangoproject.com, 2020.

[7] MDN Web Docs, “Web Technology for Developers”,

https://developer.mozilla.org, 2020.

[8] OpenAI, “GPT-4 Technical Report”, OpenAI, 2024,

https://openai.com/research/gpt-4.

[9] W3Schools, “Web Development Tutorials”, https://www.w3schools.com, 2020.

[10] Apache JMeter, “Apache JMeter Manual”, https://jmeter.apache.org, 2020.

48