This essay has been submitted by a student. This is not an example of the work written by our professional essay writers.
The wedding automation system is getting popular across the world and in Kuwait. This automation adds on good value for customer and organizer in term of time, schedule, accuracy, auditing, budget and reporting. Therefore, as part of university system automation curriculum is to create an end to end automation project with documentation and a system prototype to advance student to the new level of know how to prepare, think and organized a project for work as soon as graduated.
This project is presenting the overview proposal of how to design and implement the wedding automation system with details of project tasks and activities.
The Wedding automation system goal is going to target:
Maximize customer (wedding couple) benefits in term of wedding schedule, human errors, finance struggle, visioning of pre and post wedding events.
Minimize paper work and automation all steps of wedding events with track records and reminders for references.
The system preparation - design and implementation will consist of:
Wedding customer requirement - information gathering
Conceptual design for the system
Logical model for the system
Physical implementation for the system
Hardware and software preparation
Application coding, development and implementation
General user support online screens
End to end security
1.2 Project layout
Chapter one includes introduction about the project.
Chapter two introducing database.
Chapter three designs and implementation.
Chapter four conclusions and feature works.
"A database is a collection of information that is organized so that it can easily be accessed, managed, and updated. In one view, databases can be classified according to types of content: bibliographic, full-text, numeric, and images."The Database is contains collection of information that been organized so that it is easily to accessed, managed and also updated. The Database architecture consists of three levels. These are external, conceptual and internal. They are the major elements of the Database relational model.
The internal level defines how the data physically stored and processed by the computing system, and also it's concerned with cost, performance and scalability. The conceptual provides a general view of the database that is not complicated by details of how the data is stored or managed; also it is the level between internal and external. The external level defines how users understand the organization of the data. 
These databases store detailed data about the operations with its organization. The Database can be used with any organization, also we can use Database in many things in our lives for example, customer database that record contact, credit, and information about a business customers, personnel databases that hold information such as salary, benefits, skills data about employees, manufacturing databases that record details about product components, parts inventory, and financial databases that keep track of the organization's money, accounting and financial dealings.
Data warehouses archive modern data from operational databases and sometimes from external sources such as Market Research Company. The warehouse is the central source of data so that the managers and other end-users can use it even that may not have access to operational data. The benefits of data warehousing includes retrieving and analyzing data, transforming, loading and managing data so as to make it available for further use.
These are databases of local work-groups and departments, branch offices and other work sites. These databases can include places of both common operational and common user databases, as well as data generated and used only at a user's own site. 
These databases contains of data developed by individual end-users. For examples word processing and downloaded files. 
These databases contain data collected for use across many organizations, either freely or via subscription. Movie database is an example for external database. 
Database replication means that there are many copies of database on different computers, to allow more users to access it, or to allow another site to immediately take over if the primary site stops working. Database collecting is a related concept to handle a larger databases and user communities by employing a cluster of many computers to a single database that can use replication as part of its approach. 
Database security means that the system processes and procedures are protected the database from unauthorized activity.
The benefits of DBMSs are access control, auditing and encryption:
Access control do manage to who want to connect to database and what they can do through there authorization.
Auditing records the information about the database activity who, when, what and where.
Encryption protects stored data and transmitted data in an unreadable form by encrypting the added data and decrypting it when returning results, so no one can understand it.
2.4 Relational Database
Database design includes ER (Entity-relationship model) diagrams. The ER diagram is a diagram that helps to design databases in an effective and efficient way.
Attributes in the ER diagram are done with an oval shapes with the name of the attribute linked to each entity to built a relation between them.
The relational model is the final step can be done and its determining the relation between the groups of an information or objects.
ER Diagram (Entity-relationship model)
This Diagram represents the relations (one-one) (one-many) between each table with mentioning its attributes and primary keys
Figure (1) ERD Diagram
2.5 Physical database design
The physical design of the database specifies physical configuration of the storage media.
That considers the detailed specification of data elements like, data types.
It is like a detailed design of the system that include many modules, hardware and software
Specification system. 
Project PLAN and TASKS
According to the SDLC - system development life cycle methodology steps are as per following:
1. User requirement gathering reports which include:
Interview single men and women - their wedding wish list
Interview parents with wedding experiences
Interview suppliers with wedding experiences
Interview technical expert on wedding system designer
Interview financial book keepers
2. Gathering sources for wedding brochures, pictures and internet research which include:
International wedding magazines and photos
Middle East wedding magazines and photos
Wedding photos style for groom, bride, groom man, bride maid, page boy and flower girl - Western and Arabic traditional
Photographer and video man
Music bands - Western and Arabic band
Flouriest suppliers - fresh and plastic sources
Master ceremony - MC
Legal documentation - Wedding certificates
Wedding cards for invitation - printer shop
Security and police for protection
Legal registration places
Resort booking and facilities
Payment method and staging of payments
Packaging offers and discount
Marketing and advertising plan
Word by mouth tactic
Promotion gifts and surprise offers
The figure below shows how the system works and what is the input, internal system process, external suppliers and the end the output of customer idea.(2)
Figure (2) Conceptual Design Model
The table below shows the description and priority of risks that could face me.
Table (1): wedding system Risk Analysis
RISKs of Guest > 500
Letter of guarantee
Lost of income
Full or partial
Exact style or requirements
missing in action
missing in action
missing in action
Supplier power cut off
Short of equipments
Music and songs
Security / police
Lack of authorities
missing in action
missing in action
missing in action
missing in action
Lack of rehearsal
Food and drink
Waiters and waitresses
check list indoor
check list outdoor
check list semi
Fire, bomb, abuse
Pre and Post action
lesson to learn
3.3 Use case Diagram
This Diagram shows the relation between the agent dealing with the company and the system to provide services to the customer, in the other side customer choosing his own order then receiving his payment report.
Figure (3) Use Case Diagram
Figure (3) below shows the relation between the customer and the suppliers that we are dealing with and screens layout of the system using Access database.
Figure (4) physical implementation of the project
This figure showing the wedding agent dealing with the system through the computer and helping clients to do the arrangements of the wedding, the client information will be stored in the database, by using the following:-
Software to use - Microsoft ACCESS database
Screen display GUI - Microsoft access forms and template
Programs interaction - Microsoft access program for interaction
Reporting - Microsoft SQL reporting code
Display brochure, diagrams and pictures - Microsoft HTML and hyperlink functions
Store and calculate data and pricing - Microsoft access database structure
System Database Tables
The tables below show each table and its attributes:
1. Customer Table
This table contains information about the customers. It shows the table fields and the primary key for the table
Table (3-1): Customer table and its fields.
This table contains the information about financial information of the bank with mention the primary key.
Table (3-2): Finance table and its fields.
This table contains supplier's information's.
Table (3-3): Supplier table and its fields.
This table contains information's about customer account.
Table (3-4): Accountant table and its fields.
This table contains the information's about the packages.
Table (3-5): Package table and its fields.
This table contains the information's about orders and how to make a new order.
Table (3-5): Order table and its fields.
This interface shows the main menu and each button leads to its related interface, the buttons are: Customer, Finance, Accountant, Packages, offer, Suppliers, Order and Report.
Figure (5) Main Menu
This form shows the customer information fields like customer CVID, Groom name, date of birth, bride name, date of birth and their nationality, as shown in the right side these save button will save customer data, add button it will add customer data to the database so it's easy to find it again, pressing main menu button will take you back to main menu screen.
Figure (6) Customer Form
This form shows the data fields of which bank is customer dealing with
And its finance information's such as bank name, credit card type and number, in the right side these save and add buttons will save then add customer finance information to the database, then main menu to go back to main screen.
Figure (7) Finance Form
This form shows the company information fields that the agent will deal with to supply the customers with its services, such as company hotline, email, fax and phone number.
Figure (8) Supplier Form
This form shows the customer accountant information such as account id, payment method, payment date and total payment, also can add and save the data.
Figure (9) Accountant Form
This form shows the information of each package such as package ID and package description so the customer can choose many different kinds of services at the same time he can look at each service picture linked as a hyperlink then decide what he like then adding it to his own package.
Figure (10) Package Form
This form shows the fields of services and the price of each them, also contains calculation process, the buttons bellow is to do a new order or going back to package form.
Figure (11) Order Form
This form shows customer bill information contains the total price of customer order with report date.
Figure (1) Customer Report
PROJECT PLAN AND MILESTONES
This figure shows the continuity time of the project, starting from feasibility study then ending with executing the information system.
Figure (1) Task Schedule
RECOMMENDATIONS AND FUTURE WORK:
There will be extra activities, computer graphics and complication tasks in programming and coding to improve the system and make its application more secure, scalable and easy to use by normal clients.
My aim in the future work is to do a powerful web application system.
As I referred before the classic companies face a lot of problem before moving to the automated systems such as data availability and data integrity, the time for storing and retrieving, data security and manage user's accounts.
The suggested solution here is to move from manual (classic) system to an automated system, which solves all these problems.
The solution is during three main stages:
Design a database using MS Access 2007.
Create relations between tables.
Create forms for each table.
Create report for printing out.