1
Chapter III
RESEARCH METHODOLOGY
This chapter presents an overview of the system and also the presentation
description of the design, process flow, methodology used and paradigm
Brief Review of the Existing System
E-commerce (electronic commerce) is the buying and selling of goods and services,
or the transmitting of funds or data, over an electronic network, primarily the internet. These
business transactions occur either as business-to-business (B2B), business-to-consumer (B2C),
consumer-to-consumer or consumer-to-business. When the findings is to obtained results
demonstrated the efficiency and effectiveness of the proposed model in term of the success of
the recommender systems in the electronic commerce.
Brief Review of the System
In the proposed food delivery system, it gives a more convenient way
of accessing the transactions of buying in food services across the community, and the
admin will verify and grant login credentials. Also the customer was register and login
with their own details. And the admin was responsible to handle all of the activities. the
customer is able to find the food they want to buy just like they do when they go to the
restaurant. they can easily order the food they want quickly and they don't have to
choose in front of the counter. When the ordering systematically they can schedule
delivery for specific day or same day delivery too. Using these parameters, customers
can create a package they want to get delivered upon a nearby location.
Agile Methodology
According to Wrike a project management guide, Agile is a process by which a
team can manage a project by breaking it up into several stages and involving constant
collaboration with stakeholders and continuous improvement and iteration at every
stage. The Agile methodology begins with clients describing how the end product will be
used and what problem it will solve. This clarifies the customer's expectations to the
2
2
project team. Once the work begins, teams cycle through a process of planning,
executing, and evaluating — which might just change the final deliverable to fit the
customer's needs better. Continuous collaboration is key, both among team members
and with project stakeholders, to make fully-informed decisions.
Context Diagram
Each DFD may show a number of processes with data flowing into and out of
each process. If there is a need to show more detail within a particular process, the
process is decomposed into a number of smaller processes in a lower level DFD. In this
way, the Content Diagram or Context-Level DFD is labeled a “Level-0 DFD” while the
next level of decomposition is labeled a “Level-1 DFD”, the next is labeled a “Level-2
DFD”, and so on.
Context Diagrams and Data-Flow Diagrams were created for systems analysis and
design. But like many analysis tools they have been leveraged for other purposes. For
example, they can also be leveraged to capture and communicate the interactions and
flow of data between business processes. So, they don’t have to be restricted to
systems analysis.
2
3
Figure 2: Food Delivery Plant Selling System Context Diagram Level 0
The Figure shows the context diagram level zero of Food Deivery System with the
simple illustration of interaction of the online customer, the system and the admin.
Context Diagram Level 1
Figure 3: Food Delivery System Context Diagram Level 1
Figure 3 shows the detailed interactions between customer, admin, inventory and the
Food Delivery system.
2
4
Unified Modeling Language Diagram
The Unified Modeling Language (UML) was created to forge a common,
semantically and syntactically rich visual modeling language for the architecture, design,
and implementation of complex software systems both structurally and behaviorally.
UML has applications beyond software development, such as process flow in
manufacturing.
It is analogous to the blueprints used in other fields, and consists of different types of
diagrams. In the aggregate, UML diagrams describe the boundary, structure, and the
behavior of the system and the objects within it.
UML is not a programming language but there are tools that can be used to generate
code in various languages using UML diagrams. UML has a direct relation with object-
oriented analysis and design.
2
5
Unified Modeling Language Diagram
Figure 4: Food Delivery System Unified Modelling Language Activity Diagram
Data Flow Diagram
2
6
From process flows that clearly show responsibility and project handoffs to user flows
Figure 5: Food Delivery System Data Flow Diagram
Entity Relationship Diagram
Although data modeling has become a necessity around 1970’s there was no
standard way to model databases or business processes. Although many solutions were
proposed and discussed none were widely adopted.
Peter Chen is credited with introducing the widely adopted ER model in his paper “The
Entity Relationship Model-Toward a Unified View of Data“. The focus was on entities and
relationships and he introduced a diagramming representation for database design as
well.
His model was inspired by the data structure diagrams introduced by Charles Bachman.
One of the early forms of ER diagrams, Bachman diagrams are named after him.
And the ERD models in database design is Although data modeling has become a
necessity around 1970’s there was no standard way to model databases or business
processes. Although many solutions were proposed and discussed none were widely
adopted.
2
7
Entity Relationship Diagram
Figure 6: Food Delivery System Entity Relationship Diagram
Other Required Charts or Diagrams:
Use-Case Diagram
Work-Breakdown Structure
Gantt Chart
Cost-Benefit Analysis
References
Context-diagram: [Link]
[Link]
2
8
Unified modeling language(UML)
[Link]
lucidchart:
[Link]
Entity Relationships Diagram:
[Link]