Horizon Days

Project Plan
Food event

Pro-p Group
Andre Samuel Rieuwpassa, 3002500
Lama Naser Eddin, 3046699
Theodor Galinov Genov, 2987597
Kaloqn Babev, 3061507
Revision history
Old version New version

Content on current situation and Change content on current situation

project justification are difficult to and project justification
read and need more explanation
Project goals not in group Group project goals

Deliverables not have that many Add more deliverables

item
Project phasing don’t have accurate Project phasing make more the time
time accurate
Revision history don’t have old and Add old and new version on revision
new version history

1
 1.Project Statement:
In this document will explain why we started this project and what will achieve. The
following topics will be described. : the formal client, the project leader and the team
members ,current situation, the problem description, the goal of our project, the
deliverables and non-deliverables,
the constraints and the risks.

2.The Formal Client:

Contact information:
Name: Mr. Vladimir Kabzar
Place: Rachelsmolen 1, Eindhoven
Description: ICT from Fontys ICT Eindhoven is the Client.

3.Project Team:
-Project leader:
Name: Andre Samuel Rieuwpassa.
Email : a.rieuwpassa@student.fontys.nl

-Secretary:
Name: Lama Naser Eddin.
Email: lamanasereddin@student.fontys.nl.

-Note maker:
Name: Teodor Galinov Genov
Email: t.genov@student.fontys.nl

-meeting minute:
Name: Kaloyan Atanasov Babev
Email: k.babev@student.fontys.nl

2
 4.Current Situation:
The company wants to organise a food festival that starts on Friday morning and
continues until the end of the weekend. The event will take place on a big terrain
with a lot of space for visitors/tents, whatever the event requires.
Part of the terrain is reserved for the camping ground, where visitors can stay for the
night. The company is going to make a website that informs people about the event
and allow them to buy ticket and allows reservation of camping spots. The company
want to make profit by selling food, drinks, souvenirs etc.
The company will make an application to support the shops (food, drink, souvenirs).
It’s not possible to the customer to pay with cash because of that there will be
machine on the terrain to allow visitors to transfer money from their bank account
to their event account. In this case the company will need an application that
changes the balance of the visitors.
The company needs also a software system that is going to be used to manage the
event. Our company going to provide application to help the event management
team to see the overall status of the event.

5.Project justification:
Because the event started to attract more visitors, it has become impossible to
manage them without a proper software solution, that’s why the company is going
to make a website and some applications to control everything.

6.Project Goal
The system will be composed of balance application, check in and check application,
loan stand app, event overview application, out which will be used to manage the
event. The system must provide

Application (visitor) 1. There going to be a visitor status

on the application that we going
to made.

2. There going to be a visitor history

on the application that we going
to made.

3. On the application there going to

be number of total of people per

3
 day.

4. Camping statistics going to be

visible in the app

Application (money) 5. There is going to be an account

for every visitor

6. In the app total of balance of all

visitor going to be visible

7. In the app total of money that

been spent buy the visitor going
to be visible

8. Total money per shop is visible in

the application

9. Total amount of a certain product

in each shop is visible in the
application

Website 10. The website are for inform

people about the event

11. The website are for reserve a

ticket for the event

12. The website for reserve camping

13. The guy than reserve a camping

spot can bring guest with some
max amout
14. After reserve a ticket visitor going
to get a barcode in email for
entering the event

7.Project Deliverables and non-

Deliverables

4
Deliverables:
 Project plan – first draft
 Group name and logo
 Project plan
 Database ERD
 Static website
 Web app
 App for scanning ticket
 App for shop management
 App for loan stands
 App for event
 Database
 Presentation
 Deployed applications and website

Non-deliverables:
 gps track on the bracelet
 client wishes to add other features to the or recoding the c# app after a long
time(due to restricted time/we are busy with our new clients/projects and we cant
do that)*

8.Project Constraints:
Constraint 1: Time
In every week, we need to have a meeting to always plan the next step.
The company require to make an application and website with in 20 weeks

5
 9.Project risks:
Risk 1: Illness amongst team member
Probability: small
Impact on project: high (due to small team)
Steps to prevent: have one backup team member
Clean up action: push unavailable teammates’ deadlines to another teammate(s).

Risk 2: Impossible demand by client

Probability: medium
Impact on project: high
Steps to prevent: critical thinking when talking to client.
Clean up action: Inform client, negotiate new demands.

Risk 3: Missing deadline

Probability: medium
Impact on project: medium
Steps to prevent: Have realistic demands, keep all team members’ tasks organized.
Clean up action: Negotiate thing that you can and cant deliver to the client, reorder
tasks.

10.Project phasing:
Initiation Design Build Test Deploy

Build Test
Design
Apps

Start 6
Project
 Deploy
Apps

Document Build
Project Database

M1 M2 M3 M4 M5
wk1 wk3 wk6 wk13 wk15 wk16

Phase 1: Initiation
Action: Start project
Tasks:
1. Interview client
2. Discuss current situation, problems and end application
3. Set a goal
4. Organize team
Estimated duration: Done
Deliverables for Milestone 1

 Project plan – first draft

 Group name and logo

Phase 2: Documentation and design

Action: Make the project document and design
Tasks:
1. Finish project plan
2. Finish setup document
3. Provide reports of schedule every week

7
Estimated duration: 14 october
Design tasks:
1. Design application
2. Design database
3. Design UI of website
Estimated duration: Two weeks.
Deliverables for Milestone 2 are:

 Project plan
 Database ERD
 Static website

Phase 3: Build
Action: Build
Tasks:
1. Build and populate database
Estimated duration: 13 november
Deliverables are:

 Web app
 App for scanning ticket
 App for shop management
 App for loan stands
 App for event
 Database

Phase 4: Test
Action: Test applications and website
Tasks:
1. Database check
2. Test event apps
3. Test website

8
 4. Improve if needed
Estimated duration: between November 13 – January 6
Deliverables:

 Tested apps and website

Phase 5: Deploy
Action: Deploy applications
Tasks:
1. Deploy applications and website
2. Create a presentation
Estimated duration:
Deliverables:

 Presentation
 Deployed applications and website

9
 11. Management Plans:
1. Skill
 Making application on c#
 Making website
 Database basic
 Documentation making
 Application and database connection

2. Information
 In charge of all the document is : Andre
 In charge of the website is: Theodor
 In charge of the application is : kaloyan
 In charge of the database is: lama
(note: everyone going to make everything but the one that in charge of the above
are those people)

3. Time
 In every week at least 1 time meeting with the tutor
 In every week at least 1 time meeting not with the tutor
 before the 13 January everything should be done

10