This document outlines a project charter for planning a wedding. It defines the purpose, justification, description, objectives, stakeholders, funding, success criteria, deliverables, constraints, assumptions, acceptance criteria, milestone schedule, risks, budget, and approval requirements for the wedding planning project. The key objectives are to plan the wedding to achieve quality while managing constraints and risks to ensure the ceremony proceeds smoothly with minimal issues.

1. WBSCode Wedding Task Project mangerProgram
owner/BridgroomFinance controllerDriversBenquet
adminLogistics controllerChurch
adminPhotographer/mediaR=Responsible
A= Accountable
C=Consultant
I=Inform1Guest1.1List of GuestRCI1.1.1Prepare
invitationRCI1.1.2Mailing the invitationAIC1.2RSVPs
preparationCRI1.3Check the guest special
needsAIR2Locations2.1Selectig the venue(church for
wedding)CIAA2.2Selecting Partying
LocationARIIII2.3Checking the suitability of the
venueACRI3Trasportation 3.1Deciding on the means to get to
the churchACRII3.2Setting up the car pooling service for the
guestACIR3.3Taxi or Uber booking to transport guest to and
from the hotelCAR3.2Strateggies to move the data
centerICRI3.3Providing detail maps on the venue of both
eventsRCI4Venue4.1Venue
themeRCAI4.2Tables/chairsCIR4.3Setting/utensilIA4.4Specil
equipmentsAIR5Decoration 5.1Deciding on the flowers to use
both at church and party
venueCIIR5.2TableclothsCIR5.3Wedding
favorsACR6Banquet6.1Food MenuRCIA6.2Serving
CIR6.3Special needsR6.4Wedding party names for the
programACIR7Personal Items7.1Gowns and tuxedos
CIAR7.2HairRCIR7.3MakeupsRCI7.4Wedding
ringsRCI8Entertainment8.1MusicACIR8.2PerformanceACIR8.3
ShowsACIR9Church9.1BridesmaidsAICR9.2GroomsmenAICR9.
3Interior
decorationAICR10Media10.1PhotographerACIIRIR10.2Weddin
g VideographerACIIRIR

2. Competency
In this project, you will demonstrate your mastery of the
following competency:
• Write programs by applying concepts and principles of object-
oriented programming
Scenario
You work for Global Rain, a software engineering company that
specializes in custom software design and development. As a
junior
software developer, you are part of a software development
team
that collaborates to create solutions for entrepreneurs,
businesses,
and government agencies around the world.
As part of a development team at Global Rain, you will be
designing
and developing custom software for a local pet boarding and
grooming business, Pet Boarding and Grooming (Pet BAG). Pet
BAG
is seeking a way to modernize its operations by introducing
custom
software that will help replace inefficient paper-based
processes.

3. Your Global Rain team will collaborate to develop an app that
will have the following initial
functional areas: Check-in pets, Check-out pets, Pet
management, and Reports.
As part of this team, you have been tasked with completing
some preliminary work that consists of
writing a Java class, writing pseudocode, and creating a
flowchart. You will provide these
deliverables to your supervisor.
Directions
Pet BAG has provided you with a specification document
detailing its software needs and design
documentation from your supervisor to complete your tasks.
1. Before you begin, it is
important to analyze your
client’s software requirements
and the design documentation
from the Supporting Materials
section. Specifically, review the
Pet BAG specification

4. document and the UML Class
diagram, paying close attention
to the class hierarchy,
attributes, and behaviors.
2. To begin, open the Virtual Lab by clicking on the link in the
Virtual Lab Access module. Then
open your integrated development environment (IDE) and create
the Pet class based on the
UML Class diagram. The Pet class must meet all the
specifications from the class diagram
including the following:
◦ All attributes with appropriate data structures
◦ At least one constructor method
◦ Accessors and mutators for all attributes
3. When you are done implementing the Pet class, refer back to
the Pet BAG specification
document and select either the pet check-in or check-out
method. These methods are detailed
in the Functionality section of the specification document. You

5. will develop pseudocode and a
flowchart for the method you select.
4. Based on the method you chose, write pseudocode that lays
out a plan for the method,
ensuring that you organize each step in a logical manner.
Remember, you will not be creating
the actual code for the method, and you do not have to write
pseudocode for both methods.
5. Based on the pseudocode you wrote, use the tool of your
choice to create a flowchart for the
method you selected. Your flowchart will help your team
communicate how you are planning to
develop the software for your client. In your flowchart, be sure
to do the following:
◦ Include start and end points.
◦ Include appropriate decision branching.
◦ Align the flowchart to the check-in/check-out process.
6. Based on your software design and development experience,
your supervisor has asked you to
articulate your programming approach. This will help ensure
clarity, consistency, and efficiency
among all developers working on this app. Specifically, you
have been asked to briefly explain

6. how you applied object-oriented programming principles and
concepts (conditional statements,
inheritance, and so on) in the your software development work
thus far.
What to Submit
To complete this project, you must submit the following:
Pet.java Class File
As part of your tasks for the software development team, create
the Pet class in your integrated
development environment (IDE). To submit this deliverable,
save the Pet class file as Pet.java.
Global Rain Summary Report
As a junior software developer, you will use the Global Rain
Summary Report Template to complete
the report. Your report must contain your pseudocode,
flowchart, and explanation of the object-
oriented programming principles you applied.
Supporting Materials
Use the following resources to support your work on this
project:

7. Pet BAG Specification Document
Review this specification document provided by Pet BAG to
understand your client’s software
requirements. You will use these requirements to create your
flowchart and write your pseudocode.
UML Class Diagram
Use this UML class diagram, prepared by the senior developer
leading your team, to implement the
Pet class. This class diagram demonstrates the Pet class, Dog
class, and Cat class and illustrates
inheritance. A text version of this image is also available: UML
Class Diagram Text Version.
Downloading Files From Eclipse Tutorial
You will write, test, and run your Pet class file using an
integrated development environment (IDE).
Review this tutorial to learn how to save and export files from
your IDE. Important: Do not change
the names of any class files.
The following rubric will be used to assess Project One.
Familiarize yourself with this document as
you work on the project, and return to this rubric before you
submit Project One to make sure
you've included everything you need to be successful.

8. Project One Rubric
Criteria Exemplary Proficient
Needs
Improvement
Not Evident Value
Class Creates a
class that
meets UML
Shows
progress
toward
Does not
attempt
criterion (0%)
30
class diagram
specifications,
including all

9. attributes with
appropriate
data
structures, a
constructor,
and accessors
and mutators
(100%)
proficiency,
but with errors
or omissions;
areas for
improvement
may include
appropriate
data
structures,
naming

10. conventions,
method
structure,
return values,
or functionality
(55%)
Pseudocode
Writes
pseudocode
that outlines a
plan for
developing a
method and
aligns to
software
requirement
specifications
(100%)

11. Shows
progress
toward
proficiency,
but with errors
or omissions;
areas for
improvement
may include
pseudocode
clarity,
formatting,
logic, or
alignment to
software
requirement
specifications
(55%)

12. Does not
attempt
criterion (0%)
15
Flowchart Creates a
flowchart that
aligns to
Shows
progress
toward
Does not
attempt
criterion (0%)
15
software
requirement
specifications

13. including
appropriate
decision
branching and
start and end
points (100%)
proficiency,
but with errors
or omissions;
areas for
improvement
may include
logic,
representation,
appropriate
decision
branching, or
start- and end-

14. point accuracy
(55%)
OOP
Principles
Exceeds
proficiency in
an
exceptionally
clear,
insightful,
sophisticated,
or creative
manner
(100%)
Concisely
explains the
application of
object-

15. oriented
programming
principles in a
software
development
process (85%)
Shows
progress
toward
proficiency,
but with errors
or omissions;
areas for
improvement
may include
accuracy,
depth, or
missing

16. principles
(55%)
Does not
attempt
criterion (0%)
30
Articulation
of Response
Exceeds
proficiency in
an
exceptionally
clear,
insightful,
sophisticated,
or creative
Clearly
conveys

17. meaning with
correct
grammar,
sentence
structure, and
spelling,
demonstrating
Shows
progress
toward
proficiency,
but with errors
in grammar,
sentence
structure, and
spelling,
Submission
has critical

18. errors in
grammar,
sentence
structure, and
spelling,
preventing
10
manner
(100%)
an
understanding
of audience
and purpose
(85%)
negatively
impacting
readability

19. (55%)
understanding
of ideas (0%)
Total: 100%
Developer: [Insert name here]
Date: [Insert date here]
Summary Report Template
Directions: Place your pseudocode, flowchart, and explanation
in the following sections. Before you submit your report,
remove all bracketed [ ] text.
Pseudocode
When you are done implementing the Pet class, refer back to the
Pet BAG specification document and select either the pet check-
in or check-out method. These methods are detailed in the
Functionality section of the specification document.
Write pseudocode that lays out a plan for the method you chose,
ensuring that you organize each step in a logical manner.
Remember, you will not be creating the actual code for the
method. You do not have to write pseudocode for both methods.
Your pseudocode must not exceed one page.
[Type/copy pseudocode here.]

20. Flowchart
Based on the pseudocode you wrote, create a flowchart using a
tool of your choice for the method you selected. In your
flowchart, be sure to include start and end points and
appropriate decision branching, and align the flowchart to the
check-in/check-out process. Your flowchart must be confined to
one page.
[Insert flowchart image here.]
[Refer to the Project One Supporting Materials for tool options
to create your flowchart and how to copy images into this
template.]
OOP Principles Explanation
Briefly explain how you applied object-oriented programming
principles in the software development process. Your
explanation should be one paragraph, or four to six sentences.
[Type your explanation here.]
Page | 2
System Specification Document
Overview
Pet Boarding and Grooming (Pet BAG) is a company that

21. provides boarding and grooming services for
dogs and cats. We want to modernize our operations by
introducing custom software that will help
replace inefficient paper-based processes.
Functionality
We are seeking an app that has the following initial
functionality:
• Check-in pets
• Check-out pets
• Pet management
• Reports
Each of these functional areas are described below.
Pet Check-In
To update our current processes, we outline our current manual
check-in process below, which involves
multiple steps and verifications.
First, we determine whether the pet is a dog or a cat. Next, we
determine if boarding space is available
for the pet. There are currently 30 spaces for dogs and 12 spaces
for cats. We would like the ability to
update these settings as needed. If boarding space is available,
we identify whether the pet is a new or
returning visitor. If the pet has stayed with us before, we are
seeking the ability to update information
as needed. If the pet is a new visitor, we would like the
opportunity to collect all the appropriate
information.

22. Additionally, we would like the ability to gather information on
the length of stay for each pet and if
grooming services are required. Grooming services are only
offered for dogs that stay at Pet BAG for two
or more days. No grooming services are offered for cats.
Our final step is to assign the pet to a space.
Pet Check-Out
To update our current processes, we outline our current manual
check-out process below, which
involves multiple steps.
First, we identify the pet and its current boarding space within
Pet BAG. If the pet is scheduled for
grooming, this service is provided as part of the check-out
process. We also collect information of the
amount due to the customer based on the fees below:
Type of Pet Daily Boarding Fee Grooming Fee
Cat $18.00 N/A
Dog (greater than or equal
to 30 lbs.)
$34.00 $29.95
Dog (20–30 lbs.) $29.00 $24.95
Dog (fewer than 20 lbs.) $24.00 $19.95

23. Finally, we clean the boarding space and prepare it for the next
visiting pet.
Pet Management
We require the following to manage the pets that we have
boarded:
• Ability to move a pet from one boarding space to another
• Ability to record morning and evening feedings
• For dogs, ability to record morning, afternoon, and evening
yard time
• Ability to add notes on any pet
• Ability to update pet data including weight, grooming
requirements, and notes
• Ability to denote whether a pet stay has been paid for or not
• Ability to schedule a space for cleaning and alert personnel
when the space is ready
Reports
TBD
System Specification DocumentOverviewFunctionalityPet
Check-InPet ManagementReports
Pet
- petType
- petName
- petAge
- dogSpace
- catSpace
- daysStay
- amountDue

24. + checkIn()
+ checkout()
+ getPet()
+ createPet()
+ updatePet()
Dog
+ dogSpaceNbr
+ dogWeight
+ grooming
+ getGrooming()
+ setGrooming()
+ getDogWeight()
+ setDogWeight()
Cat
+ catSpaceNbr
Arrow pointed from table labeled Dog to table labeled Pet;
arrow pointed from table labeled Cat to table labeled Pet

25. <Wedding planning
<Class Name>
<Student Name>
<Date>
2
8
Table of Contents
Wedding plan project charter2
Project Purpose/Justification2
Description2
Objective2
Project Stakeholders2
Funding3

26. Project Success Criteria3
Major Deliverables4
Constraints5
Assumptions5
Acceptance Criteria5
Milestone Schedule6
Risks6
Summary Budget6
Approval Requirements7
References8
Wedding plan project charterProject Purpose/Justification
The purpose of this project is to plan the wedding so that
quality is achieved while ensuring that all constrains and risks
are kept in check. Therefore, the wedding ceremony will go on
without any encounters or minimal if there will be
any.Description
The project charter is used for performing different tasks in
various stages of project development. This document explains
the processes that must be accomplished right from the moment
the project commences to the end. Having a well-designed
project charter ensures that every deliverable is done and
completed in time; thus, avoiding the technical challenges
occurring in the process. Objective
Before the commencement of the project, it is important to
detail every aspect and plan that will be implemented. The
wedding function has some specific tasks that should be entirely
completed correctly for the successful completion of the
project. These details include the stakeholders involved,
resources that are going to be used, project success criteria,
project deliverables, constraints, and project success criteria
among other tasks crucial in the project. Project Stakeholders
Task Stakeholders – List all resources who have a part in the

27. project success
Stakeholder
Description
· Project Manager
Responsible for the overall planning, execution and successful
delivery of the project.
· Sponsor
The project sponsor is responsible for funding all the functions
in the project.
· Project team
The team members perform the basic tasks in the process of
project development.
· Wedding vendors
Responsible for making everything important at that particular
date of the wedding.
· Family members
Organizing what is required at the wedding.
· Bride and groom
Are the real guest of the stakeholders
Funding
Most of the funds come from individuals with a mutual interest
in colorful and successful weddings (Verzuh, 2005). For this
wedding project, the funds will come from the friends and
relative, but the large proportion come from the bride and
groom who are the main stakeholders who have the resources
that will sponsor the wedding project, and who is also interested
in the overall success of the project as well. The wedding team
members are given the task of determining the projected amount
that will be spent on the overall wedding function. The amount
suggested must go through the wedding panel to determine its
feasibility. The wedding funds will not include other activities
done after the day of the wedding ceremony.Project Success
Criteria
The project manager will be required to communicate the status
of the project on the weekly bases the main sponsors (bride and
groom). The following factors will determine project success.

28. 1. Cost
The wedding and all other functions on the given date of the
ceremony will be required to complete within $ 20, 000 dollars.
Also, the costs will further need some changes since the
resources and estimates of costs are on a contract basis.
2. Quality
The quality of the functions shall be upheld and in order to be
well-thought-out to have met that quality, the following
requirements must be looked at. All the wedding plans will be
done according to the requests and plans of the bride and the
groom.
a. The bride and the groom will have to inspect all the
requirements before they are booked into the reception.
b. All the risks management issue shall be done by the bride,
groom, and the project manager.
c. The primary goal of the project is for the bride and groom to
enjoy and create enjoyable memories. Major Deliverables
The project deliverables include those items that must be
delivered on the particular date of the function or even in the
process of planning (Fangel, 2018). These deliverables will
include:
i. The wedding location
ii. Reception site
iii. Preferred wedding colors
iv. The guest lists
v. The invitations
vi. Wardrobes
vii. Food catering
viii. Interior decoration
ix. Marriage license
x. Executive reception Constraints
The project constraints provide factors that could affect the
success of the overall project. The wedding plan project
constraints are:
i. The key stakeholders, bride, and groom have no acceptable
funds to obtain the project.

29. ii. The project must be completed immediately
iii. The estimated budget must not be more than $ 10,000
iv. The gust should be more than 175 participantsAssumptions
The assumption of the project are those factors that have a
limited effect on the overall progress of the project and even its
success (Project Management Institute, 2018). The assumptions
of this particular wedding projects are:
i. The bride and groom have selected the date of the function
that will never be altered or changed.
ii. The bride and the groom will not back out of the wedding
iii. The project will be completed on December 20th, 2019
which will be carried out within the estimated budget.
Acceptance Criteria
When dealing with the deliverables from the vendors, those
deliverables must be within the quality, the budget and the
requirements stated in the contract document ("Project Charter,"
2016). The deliverables from other interested parties, family
and friends, are appreciated and are expected to be beautiful and
perfection guaranteed.
Milestone Schedule
Summary Milestone Schedule – List key project milestones
relative to the project start.
Project Milestone
Target Date (2/20/6-20)
· Project Start
10/1/2019
· Deciding the number guest
12/20/2019
· Weeding Item shopping and Hotel Booking
2/20/2020
· Ordering wedding stationaries and transportation
4/20/2020
· Send wedding invitation and menu detail discussion
5/20/2020
· Buying a guest book, seating preparation plan, and guest plan

30. confirmation
6/10/2020
· Project Complete
10/20/2020
Risks
High Level Rick – List high level project risk
Risk Factor
Project Impact
(High, Med, Low)
· Resource Contract Risk
high
· Budget Risk
high
· Sponsor Support Risk
low
· Schedule Risk
med
Summary Budget
The following table contains a summary budget based on the
planned cost components and estimated costs required for the
successful completion of the project.
Summary Budget – List component project costs
Project Component
Component Cost
· Venue
$500
· Attire (dress and suit)
$1000
· Flowers
$2000
· Photographer
$1000
· Meals
$3000

31. Total
$7500
Approval Requirements
The project will be required to meet some specific requirements
for it to be used for planning the wedding event. The main
stakeholders will have to approve the charter and allow the
commencement of the preparation of the planning. Therefore,
the project sponsor, bride, and groom must approve the project
and check if it meets the requirements; if not the reject it or
suggest the modification.
References
Fangel, M. (2018). Proactive project management: How to make
common sense common practice.
Project Charter. (2016). Project Management Simplified, 13-20.
Project Management Institute. (2018). A guide to the project
management body of knowledge: (PMBOK® guide). Newtown
Square, Pennsylvania: Author.
Verzuh, E. (2005). The fast forward MBA in project

32. management (2nd ed.).