Department of Information Technology

Title: Plant and Flower Ordering

System
Advisor: Teshager Kassa (MSc)
Presentation date: Feb. 9 2022

1
 Chapter one: introduction
Background
• Nowadays the ubiquitous connectivity and internet makes different kinds of devices
interact to web applications. But although there is modern web applications In our day
to day life plants and flowers are ordered physically with different personnel’s and they
hold their materials by their shoulder up to their house and whatever they need places.
So this process is tired full and full of wastage of time and cost with additional
transportation costs.
• In the western world online plants and flowers ordering systems are adopting give
services but not in our country there is no any system applicable for this services.
• So that is why we want to develop plant and flower ordering system that applicable for
different shops.

2
The existing system
Weakness:
• The owner unable to update information details which is sold and available.
• There is no detail description on the plants it might be forgettable.
• Unable manage every customers orders.
• work every task with human labor or man power.
Strength:
• The shop owner have great knowledge about plants and flowers.
• Their is category of items in terms of their use and types.
• Every ordering and delivery process is done with great protection.
• The owner gives good customer services.

3
 Statement of the problems
• Their is no any services that are applicable for ordering plants and flowers.
• Customer spends much more time and cost for ordering their goods.
• To order their material customers must be goes to physically.
• Use much more man power.
• The existing system is manual and place an order with phone call.
• Customers have to wait in long queues.
• Ther is the problem on updating the items information quantity.
• The customer is not able to know about the new items and their prices.
• Ther is to much noise and disturbances in stead of it might happen
misunderstanding and error on orders.
4
 Objectives and significance of project
Objective
• The main of this project is to develop an automated plant and flowers ordering system.
• Make the process of customers order very quick and interactively.
• Develop record keeping the system and eliminate Losses of vital records.
• System should be easy to operate.
• Propose possible solutions for the current system.
• Finally implement and test the performance of the system.
significance
• The interface will be user-friendly and easy to use by any user.
• The system can be accessed ubiquitously any where and any time.
• The details of the orders placed by a customer can be found easily.
• Fault free management is achievable.
• It reduced both the time and manpower spent in running
the system. 5
 Scope and limitation of the project
Scope
This study focused on develop a web-based plants and flowers ordering system for different
shops.
• The customers and shop managers create registers or create their account.
• The administrator verify each created account.
• The customer select an item and send an order.
• The shop manager can view all orders to the websites.
• The database decrease automatically after the order is send.
Limitation
• Cost constraint ordering need additional hardware.
• Can create account and might not be used the system so it goes some storage issue.
• It needs a good internet connection to make system keep working properly.
• Works only in online platform there is no any offline access.
• There is no any online payment system. 6
 Methodology and materials used
Data collection methodology
• Observation
• Interview
System analysis, design and implementation methodology: we have used
Object Oriented Software Development(OOAD) the reason for using this methodology
is:
• Increase reusability.
• Increase extensibility.
• Easier to write and understand.
• Team members are familiar with OOP.
• Reduction of time and resources required to maintain existing systems.
Testing methodology
Unit testing: by selecting sample code and run it separately to look its correct 7
functionality.
 Con…
Integration Testing: combine some individual units together and perform integration test.
System Testing: perform system testing by selecting some user.
Acceptance Testing: check whether the system meets end user requirement or not.
Performance Testing: is non-functional testing method that is used to test the
performance of the system.
Materials used
Software materials:
hardware materials used
• Netbeans8.2
• Laptop or PC
• Microsoft Word (MS-Word 2016)
Core I3
• Microsoft Office Visio
4 GB RAM
• MYSQL
100 GB ROM
• Notepad ++
• Flash drive
• Adobe Photoshop 2021
• Printer
• XAMPP server (XAMPP Control Panel v3.2.1)
• Projector 8
 Proposed system features
Functional Requirements

• Create account • Update account

• Login • Cancel order
• View item lists • View order list (history):
• Send order • View users(customers):
• Change password • Logout
• Add items • Verify account
• Delete item • Write feedback
• Read feedback
9
 Con…
Non-functional requirement:
• Availability: the system is available on 24/7 hours.
• Reliability: will minimize crash during its runtime.
• Performance: run with high processing speed and low memory.
• Flexibility: The system operation shall be flexible.
• Correctness: the system should be correct and accurate.
• Maintainability: should be easily maintained by the other software developer.
• Usability: the system shall be Ease-of-use.
• Reusability: the data and record that are saved shall be reused if needed.
• Access control: ones user account cant by other users.

10
Usecase modeling

11
Class diagram

12
 System design goal and purpose
• Now in this phase we get into the solution domain in a software development.
Therefore we will focus on transforming the analysis model into the design model
that takes into account the nonfunctional requirements and constraints.
Purpose of system design: is to provide a description of the Design of our plant
and flower ordering system.
• To provide a description for how the new plant and flower ordering system will be
constructed.
• To find out the hardware/software stages on which the system will operate.
• To determine the architecture of the system to be developed.
• It gives us a clear idea how to deploy our proposed system in hardware level.
• It helps us to determine the architecture of our proposed system.
13
Goals of system design
The system provide a consistent set of criteria that would be taken into
consideration when making design decisions.
• Security : is used to secure the system by using .mad5 function for encryption

• Usability: to make the system usable in efficient way.

• Portability: able to run on any devices that is web based system.
• Performance: the system should give fast responses for user requests.
• Maintenance: should be easily extensible to add new functionalities.
• Availability: the system should available 24/7 hours.
• Reliability: perform its functionalities under any condition.
• Dependability: provide security in such a way that unauthorized users.
14
 Architectural design
The project use three tier architecture for designing purpose.

15
 Con…
Deployment view: illustrates the distribution of processing across a set of nodes in
the system, including the physical distribution of processes and threads.

16
 Database design
For our database design we have used entity relation diagram (ER).

17
 Con…
Relational mapping: The relational model for database management is an
approach to managing data using SQL with first order predicate logic.

18
 Con…
Normalization for ordering table

19
 Conclusion and recommendation
Conclusion
Generally, as we conclude our idea work in this project, we are try to develop plant
and flower ordering system that is functional for ordering and selling different items
that are listed on the online system those added by shops managers.
Furthermore this system gives or add different information about those plants or
flowers. And also the newly developed system has dynamic features of
manipulating, updating and managing items and data’s of them.
Recommendations
this system does not have any way of payment system after adding into the cart the
system. And also have the following recommendations as future work.
• Make efficient system adding different ways of payment systems.
• Make the system with different languages
• Enhance the system functionality by adding GPS system.
20
References
• References on testing.” https://www.softwaretestinghelp.com/types-of-software-
testing (accessed Nov. 29, 2021).
• system features and functional requirement.” https://www.pinnaclecart.com/blog/7-
key-features-online-shoppers-demand-from-an-online-store/ (accessed Dec. 25,
2021).
• To search items and their definition and their description.” https://en.wikipedia.org/
(www.wikihow.com/analaysisofdocument) (accessed Oct. 01, 2021).
• “Sequence diagram.” https://support.microsoft.com/en-us/office/create-a-uml-
sequence-diagram-c61c371b-b150-4958-b128-902000133b26?ui=en-us&rs=en-
us&ad=us (accessed Dec. 22, 2021).
• “relational database design for system.”
https://www.brainkart.com/article/Relational-Database-Design-Using-ER-to-
Relational-Mapping_11446/ (accessed Jan. 02, 2022).

21
22