INTRODUCTION

The Wedding Industry is a multi-million pound sector with thousands of pounds being
spent on each wedding. With the wedding couple spending so much money on making the
’big day’ perfect and memorable, they are becoming more willing to pass the
responsibility of planning a wedding into the hands of a professional. Wedding planners
are given the task of generating ideas and guiding the planning of a wedding so that
couples can have a less stressful build up to their big day. The wedding planner would like
to use a computer system that aids them with setting a timetable, and recognizes the
individual features that each couple may request. It is anticipated that the system will
initially deal with the events and tasks that occur on a wedding day and will eventually be
extended to organise other functions that build up to a wedding day and also manage
details about industry contacts that wedding planners recommend.

1.2 Literature Review

Products are considered as the business resources for the organization. This includes
managing the product with appropriate way to review any time as per the requirement.
Therefore it is important to have a computer based WMS which has the ability to generate
reports, maintain the balance of the stock, details about the purchase and sales in the
organization.

Problem Statement:

A wedding day can be split up into many small events, some of these events are dependent
on the religion of the couple getting married and others are generic events that occur in
most weddings independent of culture (for example, cutting a cake). For each of the four
religions mentioned above, the wedding planner has a list of generic events that take place
on a wedding day. However, some events in this list are not seen as a necessity by some
couples and there are also other family traditions people like to include that are not part
of the list. Therefore the wedding planner relies heavily upon the initial consultation with
their client to ensure that the couple’s expectations are met and that their cultural
background is reflected by the wedding day. The wedding planner will typically visit a
client, gather their requirements and build up a “timetable” for their wedding day. There
are many restrictions when building up a timetable, the main restriction is that some

1
events are dependent on others and need to be performed in a sequential order. There are
also preparation tasks (herein referred to as “Tasks”) that need to take place before
certain events can begin.

1.4 Objective of the Project:

The aim of this project is to explore how a wedding day and its preparations can be
segmented into events and tasks and to design a technique which sequences these events
so that given constraints are satisfied.

1.3 Project Outline

 The objectives of this project are to:

 Research project management and scheduling tools that are already available for
solving this type of problem.
 Develop a piece of software that implements the core modules of the wedding
planner.
 Perform a personal and technical evaluation, investigating the efficiency and quality
of the solution using real-life data.

Scope of the Application

Wedding Management System (WMS) is targeted to the small or medium organization
which doesn’t have many Restaurant or Hotel i.e. only to those organization that has
single power of authority. Some of the scope is:

 Only one person is responsible in assigning the details or records.

 It is security driven.
 Hotel can be added as per the requirement.

Background Research

2.1 The Wedding Model

This section describes the wedding model. Appendix C contains four real-life timetables
created by the wedding planner. Figure 11.2 shows a graphical representation of Example
1 of Appendix C. These timetables will be used throughout this section to illustrate the
model. In the consultation the wedding planner has with the client, a list of events and
2
tasks that the day will consist of will be constructed. A preferred start time for the first
event or a finish time for the last event (or both) is also specified. Associated with each
event and task is a duration which indicates the estimated time it takes to complete. Some
events also have deadlines or earliest start times. For example the Priest performing the
ceremony might have another ceremony to attend to later in the day, so any events he is
involved in will need to be completed by a given time in the day

There are different groups of people involved with each event/task. In

The following groups are used:
• Bride • Groom • Bride’s Parents • Groom’s Parents • Guests
•Pandit (Priest) • DJ •Caterer • The Cake Maker • Mandap (Altar)
Hire
• Serving Staff • Beautician • Photographer • Video Camera Person
The “Events” are usually associated with the “Guests” group as the guests are usually
involved with all of the main events throughout the day. No group can take part in two
events or tasks simultaneously, so if the caterer is busy preparing the starters, they cannot
be serving the refreshments at the same time (so one of these tasks will need to be
moved).

3.2 Existing Solutions:

Wedding Planning Software There are numerous companies that offer software that
enable a couple plan their own wedding General features allow users to organize contacts,
keep track of the budget and store ideas. My Wedding Companion also allows events that
occur on the wedding day to be selected. However, these events are not constrained by
any resource groups and they do not have processing times or start times. It is just a
simple list of events that the user inputs and can add comments to. There are a limited
number of companies that develop software for wedding planners. iDo is an application
used by professional wedding planners. It contains extensive features that help wedding
planners manage their business and weddings. In effect, like My Wedding Companion , iDo
is a sophisticated checklist rather than a schedule that takes into account dependency
between events. Thus, none of the applications investigated manage to solve the problem
posed by the wedding planner.

2.1.3 Data tier :

Data layer is also the class which gets the data from the business tier and sends it to the
database or gets the data from the database and sends it to business tier. This is the actual
DBMS access layer or object layer also called the business object. The database backend
stores information which can be retrieved by using the mysql database Connectivity.
Mysql database connectivity is used to manage the communication between the middle
tier and the backend database by issuing complex database queries.

3
2.2 Database Theory: A database is a collection of information that is organizes so that it
can easily be accessed, managed and updated. In one view, database can be classified
according to types of content: bibliography, full-text, numeric, and image.

2.2.1 Relational Database

WMS has the relational database model. A relational database is a digital database whose
organization is based on the relational model of data. This model organizes data into one
or more tables of rows and columns. These tables here have the relation.
The relation is maintained by the unique key defined in each row.

Primary Key

The primary key of a relational table uniquely identifies each record in the table. It can
either be a normal attribute that is guaranteed to be unique or it can be generated by the
DBMS. A primary key’s main features are:
 It must contain a unique value for each row of data.
 It cannot contain null value.

Foreign Key

A foreign key is a column or group of column in a relational database table that provides a
link between data in two tables. In foreign key reference, a link is created between two
tables when the column or columns that hold the primary key value for one table are
referenced by the column or column in another table thereby establishing a link between
them. Creating a foreign key manually includes the following advantages:
 Changes to primary key constraints are checked with foreign key constraints in
relation table.
 An index enables the Database Engine to quickly find related data in the foreign key
tables.

2.2.2 Structured Query Language (SQL)

The structured Query language (SQL) is the set of instructions used to interact with a
relational database. In fact, SQL is the only language the most databases actually
understand. Whenever you interact with such a database, the software translates your
commands into SQL statement that the database knows how to interpret. SQL has three
major Components:
 Data Manipulation Language (DML)
 Data Definition Language (DDL)
 Data Control Language (DCL)
4
 ANALYSIS AND DESIGN:

Background Research

We started research by identifying the need of WMS in the organization. Initially we

bounded our research to find the general reasons that emerged the needs of Wedding
Management System. We used different techniques to collect the data that can clearly give
us the overall image of the application. The techniques we used were interview with the
developers, visiting online websites that are presented as the templates and visiting some
organization to see their WMS application. Basically the following factors forced us to
develop WMS application:
Cost and affordability
 Lack of Party management.
 Effective flow of service transfer and management.
 Difficulty in monitoring the Wedding management.

3.2 Requirement Analysis

We collected a number of requirements for project from our primitive research, website
visits, and interview to the concerned personnel and their experiences regarding the
concepts of its development. We have even visited some organization in Kathmandu valley
and analyze its importance and try to develop the project by fulfilling all the weakness
that was found in the application. We then decided to build same type of application with
different logic flow and new language which will be suitable for the small organization.

3.3 WMS Requirement

The goal for the application is to manage the Wedding management function of the
organization. Once it is automated all the functions can be effectively managed and the
organization can achieve the competitive advantage. Business requirement are discussed
in the Scope section, with the following additional details:
 Helps to search the specific product and remaining stock.
 Details information about the product sales and purchase.
 Brief Information of the organization today’s status in terms of news, number of
present Wedding as per the date entered.
 It helps to identify the total presented Wedding in the company.
 To know the balance and details of sales distributed in specific date.
 There is proper transaction management of Wedding .
5
  All transaction has specific entry date along with quantity and rate.
 Only admin can login in the page.

3.4 Feasibility Analysis

This software has been tested for various feasibility criterions from various points of
views.

3.4.1Economic Feasibility

The system is estimated to be economically affordable. The system is medium scale

desktop application and has affordable price. The benefits include increased efficiency,
effectiveness, and the better performance. Comparing the cost and benefits the system is
found to be economically feasible.

3.4.2 Technical Feasibility

Development of the system requires tools like:

 Visual Studio 2015
 NET Framework 4.5
 Microsoft SQL server 2008, etc

Which are easily available within the estimated cost and schedule? 10

3.5.3 Operational Feasibility

The system provides better solution to the libraries by adding the typical requirement and
necessities. The solution provided by this system will be acceptable to ultimate solution
for the stock management.

3.5.4 Schedule Feasibility

The organized schedule for the development of the system is presented in the schedule
sub-section. The reasonable timeline reveals that the system development can be finished
on desired time framework.

6
SYSTEM DESIGN:

4.1 Process Flow Diagram

Process Flow Diagram or Flowchart is a diagram which uses geometric symbols and
arrows to define the relationships. It is a diagrammatic representation of the algorithm.
The Process flow Diagram of our application is shown below:

7
ER Diagram :

4.2 Use Case Diagram

Its purpose is to present a graphical overview of the functionality provided by a system in

terms of actors and their goals.
The main purpose of a use case diagram is to show what system functions are performed
for which actors:

4.2.1 Diagram Building Block

Use cases

A use case describes a sequence of actions that provide something of measurable value to
an actor and is drawn as a horizontal ellipse.

Actor

An actor is a person, organization or external system that plays a role in one or more
interactions with the system

8
 TOOLS AND TECHNOLOGY USED
5.1Development Tools:

DBMS:

5.1.2 Microsoft SQL server Management Studio Express

Microsoft SQL Server Management Studio Express (SSMSE) provides a graphical
management tool for SQL Server Express Edition. SSMSE user interface is a subset of SQL
Management Studio that is available with other editions of SQL Server. SSMSE call also
manage instance of the SQL Server Database Engine created by any edition of SQL Server.
Wedding Management System is developed using Microsoft SOL Server 2008.

Data Provider

The data provider is responsible for providing and maintaining the connection to the
database. A database provider is a set of related components that works together to
provide in an efficient and performance driven manner. Each Data provider consists of the
following components classes:
 The command object which is used to execute a command.
 The Connection object which provides a connection to the database.
 The Data Reader object which provides a ready only, connects record set.

The Data Reader object

The Data Reader object provides a read-only, connected stream record set from a
database. Unlike other components of the Data Provider, Data Reader objects cannot be
directly instantiated. Rather, the Date Reader is returned as the result of the Command
objects Execute Reader method. The Data Reader can provide rows of data directly to
application logic when one does not need to keep the data cached in memory.

Microsoft SQL Server

Microsoft SQL Server is an application used to create computer databases for the
Microsoft Windows family of server operating systems. Microsoft SQL Server provides an
environment used to generate database that can be accessed from workstations, the
Internet, or other media such as a personal digital assistant (PDA). Microsoft SQL Server is

9
used to create desktop, enterprise, and web-based database applications. It is used at
different levels and with various goals.

Reliability: achieve a more secure deployment. SQL Server provides rich security features
to protect data and network resources.

Confidentiality: Protect your data. SQL Server clustering supports Kerberos

authentication on a virtual Server and Microsoft-style policies on standard logins so that a
consistent policy is applied across all accounts in the domain.

Integrity: SQL Server supports encryption capabilities within database itself, fully
integrated with a key management infrastructure. By default, client server
communications are in encrypted.

CODING IMPLEMENTATION:
Implementation: As detailed in Section 2.1, the RAD method has been selected for the
implementation of this project. A RAD project generally begins with an extendable design
outline, this ensures that a system has good foundations. These foundations are then built
upon over numerous iterations. During each iteration extra elements of functionality are
added. The additional functionality is then tested and evaluated enabling any changes to
be made in the next iteration. During the evaluation of each iteration it is possible to make
minor adjustments to the design. These adjustments are generally due to user
requirements changing or unexpected effects of implemented functionality becoming
apparent. The adjustment of user requirements will not be considered in this project.
However, if there are any issues with functionality then a minor redesign will be
considered. Such issues may arise during the implementation of the algorithm, for
example the algorithm may be considered to be too slow.
Data Capture :

Build

This first iteration concerns the input of data for generating a new wedding sequence. The
input element of the process is represented by the “Main Menu”, “Wedding Details” and
“Job Selection” blocks of Figure:
The image containing interlocking rings with TWP (The Wedding Planner) engraved in the
centre has been developed using Jasc Paint Shop Pro 9. The colour schemes and fonts are
to be used throughout the application. Familiarities such as the menu bar across the top
and status bar along the bottom of the window have been included to aid the user by
providing form specific functions and alerts. The options available in the main menu are to
plan a new wedding, load a sequenced wedding, access the contacts database, perform
application maintenance and view help files
10
 DEBUGGING AND TESTING
Purpose of Testing

Testing performed for this section includes multiple form interaction and database
connectivity. Movement between the implemented forms works as expected. Progressing
from the new wedding form to the job selection form, validation ensures that a numeric
value is entered into fields such as “Number of Guests”. The entry format of the religion
and resources use combo boxes and checkboxes, this ensures that the user cannot enter
details that will produce errors. The database connectivity also works as expected, the
data contained in the table of the job selection form corresponds with the data entered in
the new wedding entry form. Error handling has also been included to detect when the
database is not in the directory it is configured to be in. If there is no database present,
then the user is alerted and prompted for its file path.

To identifying defects in the application.

 The most important role of testing is simply to provide information.
 To check the proper working of the application while inserting updating and
deleting the entry of the products.

7.2 Type of Testing

We have used one type of testing to ensure the error free features of our software
application:

7.2.1 Units Test

This type of testing is the testing of individual software components. It is typically done by
the programmer and not by the testers. It requires details information and knowledge
about the internal program design and code to perform this.
During unit testing, we carried out various testing task such as the reflection of the unit
data on database and its interface. Various types of bugs associated with the component
were identified and fixed. We use various functional keys to test our software.

11
 CONCLUSION AND LESSON LEARNT
Conclusion

This iteration has dealt with user interface and input issues. The next iteration will build
upon this by processing the data entered here. Improvements to be made in future
iterations should include an enhanced table of selectable jobs. The current
implementation displays multiple rows for single jobs, this is due to multiple predecessors
and resources being used. This can be improved upon by using a parent-child tree
structure that is supported. datagrid object. Kofler [12] explains how the existing format
can be modified to include this. This may be implemented after the final iteration as it is a
cosmetic feature and the first build of this project is a prototype that does not require full
functionality. Another improvement that will be included in the display & additions
iteration is to enable the user to edit multiple rows that belong to the same job. This will
speed up the input process as the user will only need to modify one row.

Lesson Learnt:

Doing something for long time periods always gives good lesson. Some of the things that
our team learnt are listed as below:
 Basically we learnt to work in team.
 Learnt about the WMS process.
 Learnt about java Technology, its components and ways to implement them
 Learnt to work in pressure and to be patient.
 Learnt to manage the database under Microsoft SQL server 2008.

Future Enhancements

Since this project was started with very little knowledge about the Wedding Management
System, we came to know about the enhancement capability during the process of
building it. Some of the scope we can increase for the betterment and effectiveness oar
listed below:
 Interactive user interface design.
 Manage Stock Godown wise.
 Use of Oracle as its database.
 Online payment system can be added.
 Making the system flexible in any type.
 Sales and purchase return system will be added in order to make return of products.
 Lost and breakage

12
 Annexure.1
Workflow and screen view:
Home

About

13
Services

14
15
16
Testimonials

FAQ
17
Blogs

18
19
CONTACT US

20
21
22
BIBLIOGRAPHY

23