Posted: June 30th, 2015

c#

Wedding Planner

Weddings-R-Us is a successful Adelaide-based franchise built around the management of weddings and, occasionally, other events. They work with the clients to ensure that all aspects of the event are completed and managed, so that everything comes together on the big day. It is a difficult task – weddings have to work, as people have a great deal of time, money and emotion invested into their success, but there is a huge number of small tasks to complete.

When they were first founded, they got by with two people and a spreadsheet. But as they grew into a national franchise, they found that they needed more formal models to manage the process. However, every wedding is different. so a strict structure just wouldn’t do the job. What they are looking for is software that they can train all of their staff on, which is unique to them, and which will help ensure that all the tasks are completed on time.

Structure

Each wedding is assigned a Wedding Planner, one per wedding. He or she is responsible for managing up to 12 weddings during busy parts of the year, with 2-3 weddings on any given weekend. Rather than handle all of the tasks themselves, they delegate the tasks out to the franchise’s staff, each of whom is given a particular task or tasks to prepare. Up to 8 or 9 people can work on one wedding, but generally the size is smaller with just 2-3 people in addition to the Wedding Planner. As staffing changes are possible, it may be the case that the people assigned will change during any given planning period, although generally the Wedding Planner remains the same.

System

Your system would allow the wedding planner to:

• Add and update (but not delete) people who can be assigned to tasks.
• Add and update (but not delete) clients and their details.
• Add, update and delete weddings
• Add, update and delete tasks
• Assign tasks to particular weddings
• Maintain a list of suppliers
• Assign people to tasks
• Generate reports

Tables

Staff

The Staff table contains a family name, given names, email, contact number, notes and a status. The status can be “active” or “inactive”. Inactive people cannot be assigned to tasks.

Clients

Clients consist of a bride and a groom, (or equivalent, depending on the wedding arrangements) and a person as the primary contact (normally the bride or groom, but sometimes a third party). The system needs to record their names, addresses, mobile and home phone numbers, and email.

Weddings/Events

Each event has a event name, start date, date when it is due to be held, description and status. The current status can be “Underway”, “Finished”, “On hold”, “Cancelled” or “In preparation”.

Tasks

Tasks have a task name, description, priority, who has been assigned to it, a date that it needs to be completed by, and an actual completion date (if it has been completed). Priority can be one of low, medium or high.

Reports

Staff Report

A printout for a given staff member

• Each task they need to implement for each wedding they have been assigned tasks for.
• The description of the task
• When the task is due to end

Event Report

Exported as a CSV or Excel file, the Event Report will list all of the tasks for a given event, their priority, when they are due to start, when they are due to finish, and who has been assigned to each one.

Event Progress

Similar to the Event Report, but the focus here is on progress – it needs to be a print out that displays the event details (what event is it for, when was it to start, when is it to finish), and list the tasks for that event. Ideally, it should include the priority, planned start date and the planned completion date for each task, and the actual completion date where available.

Event Task Report

At any time during the process, a report on the current status of all tasks should be generated and outputted to a CSV or Excel file. The report consists of:

• Each task name
• Each task’s description
• The task’s priority
• When it was due to start
• When it was due to be completed
• If it has been completed
• Who was assigned to it

Event progress

For any given event, draw a graph mapping out the progress on tasks. Given that each task has a start date and completion date, you can draw a graph showing progress, with the y-axis the number of tasks to complete, and the x axis days of the event. Then mark off how many tasks should be outstanding on a given day, and how many tasks are still outstanding on that day.

This should be available both on screen and as a print out.

Other Specifications

• You must use C# as the programming language
• You will be working in groups of 3-4. You can choose your own groups. If you cannot find a group the individual version may be available.
• You can use any database you think will be sufficient.
• Assignments must be developed with Visual Studio.NET.
• The completed code needs to be able to be run in a lab.
• You need to specify user tests for the UI classes and unit tests for other classes
• This is an Agile programming assignment. So coding in order to allow for refactoring is essential.

Deliverables

You will need to provide:

• Working code as a zipped archive containing all source files
• 500 word reflective report on the process

Marking scheme

The marking scheme is based on:

• Does it work: 40%
• How well does it meet the requirements: 20%
• How well is it written: 40%