This document summarizes a group project to develop a wedding planner system. It outlines the goals, development process, analysis conducted, and design plans. The group analyzed requirements, created use case and entity relationship diagrams, and designed workflows. They plan to build a basic website and eventually expand services across Bangladesh and Southeast Asia, while limitations include current geographic coverage and potential security and speed issues.

1. Group : 02
Wedding Planner

2. Group Members
Monamy Islam(13301001)
Azmina Akter Papeya(13101234)
Shaekh Hasan Shoron(13301011)
Biprojit Mondal(13101193)
Asif Mahmud(13101208)

3. Wedding is the most special and important event in human life.
Wedding Management is always a huge task with lots of things to do in
very short time.
Wedding Planner is the solution to these problems.
Introduction
MONAMY ISLAM

4. Goals
# Create plans to start the system.
# Perform various analysis regarding the system.
# Design the planned system.
# Develop a basic demo version of the website.
MONAMY ISLAM

5. Systems Development
Life Cycle (SDLC)
MONAMY ISLAM

6. Planning Phase
MONAMY ISLAM

7. Why should we build this system?
To address the real life problem
To make wedding planning more efficient
To make the Wedding Management time-efficient and easy
MONAMY ISLAM

8. How long will it take to build?
Planning and analysis as well as design have taken 3 months.
It will take 1-2 year to produce a full- functioning website
MONAMY ISLAM

9. Fact Finding
Fact finding is an important part of starting a business.
This can be done by :
# Questionnaire form
# Interview
# Observation
# Studying
We have done all these for our fact finding.
MONAMY ISLAM

10. Analysis Phase
SHAEKH HASAN SHORON

11. Requirement Analysis
The main target was to know the requirement of customer for a wedding
arrangement.
# What Customers wants from our website
# What features our website will contain
# What information should required for vendors
# What will be overall system for different target audience
# What will type of payment method
SHAEKH HASAN SHORON

12. Functional and Non-Functional
A functional requirement describes what a software system
should do, while non-functional requirements place constraints on
how the system will do so.
SHAEKH HASAN SHORON

13. Functional Requirements
● The system shall accept customer orders
● User will be able to modify or cancel an order once it has been
created in the system.
● The system shall accepts payment options
● System will execute a unique PIN for each customer payment
SHAEKH HASAN SHORON

14. Non-Functional Requirements
● Performance is one of the main issue to speed up the whole
process
● All the categories have to be available on that time.
● Giving Security of people's Information and data.
● Regular maintaining.
SHAEKH HASAN SHORON

15. Design Phase
SHAEKH HASAN SHORON

16. # Use Case Diagram
# Entity Relation Diagram
# Activity Diagram
SHAEKH HASAN SHORON

17. Use Case Diagram
SHAEKH HASAN SHORON

18. SHAEKH HASAN SHORON

19. Entity Relationship Diagram
AZMINA AKTER PAPEYA

20. AZMINA AKTER PAPEYA

21. AZMINA AKTER PAPEYA

22. AZMINA AKTER PAPEYA

23. Activity Diagram
BIPROJIT MONDAL

24. (Admin)
BIPROJIT MONDAL

25. (Vendor)
BIPROJIT MONDAL

26. (User)
BIPROJIT MONDAL

27. (User cont.)
BIPROJIT MONDAL

28. Future Plans
Near Future Plans :
#Cover Total Bangladesh under our system’s service.
#Add Bride-Groom Matchmaker sub-division.
#Develop android and IOS Applications
Distant Future Plans :
#Provide service to whole south east asia.
ASIF MAHMUD

29. Limitations
No system is immune from limitations.
#Currently we can only provide service within Dhaka City.
#In some cases this system can be slower than conventional system.
#Security concern.
ASIF MAHMUD

30. Conclusion
This is an ambitious plan indeed, but not an
impossible one.
Thank you for your patience
ASIF MAHMUD