EventHub

Project Title

EventHub

Project Area of Specialization Software EngineeringProject Summary

Event hub is a unique platform that provides the customer with the option of booking a marquee or a caterer online on a single platform. Marquee owners and caterers can register themselves and their marquee and catering services with ease, where a customer can log in and select whether he prefers booking a marquee or ordering catering services. Our customers will be able to select a wide range of marquees and catering services. We aim to reduce the efforts made by customers from traveling one marquee to another to just booking at home, customer can establish direct communication with the services they opt to choose through our website, price of each item is displayed to the customer so that he/she can decide according to their budget. Nowadays in this era majority of people buy or book stuff online, with this platform we will be saving not only the precious time of our customers but also the expense of traveling from place to place. Our website ensures Customers and marquee owners/ caterers are in close contact with each other so that the risks are minimal and the customer can have a sense of satisfaction. Customers can easily pay online through jazz cash, easy paisa, etc. All details of marquees/caterers with photos are available so that the customer knows what he is paying for and what he can expect on his booking date. Customer feedback is also an option that helps customers to browse through different marquees according to the experience faced by other customers before him. Customers while visiting our website are well informed of the prices and the items by looking at their pictures in depth so that they can know what to expect on their booking date. We establish a close contact between the customers and the marquee owners/caterers so that the highest level of customer satisfaction might be achieved. We saw a major opportunity that was to save customers time and their traveling cost by bringing them to an online based solution where both the marquee owners/caterers and customers could establish contact with each other with minimum fuss, we exploited this opportunity to its fullest. This platform will not only be able to help customers but the owners of marquees and caterers so that they can be able to expand their business and reach customers with ease.

Project Objectives

The impartial of this project is to provide a customer with a user-friendly environment. So they could easily interact with the system. They can easily book a marquee or gave an order to a caterer. Customers (users) can pay online through jazz cash, easy paisa, online bank account etc.

main objectives are to provide platform where marquee , catering and banque hall can improve their business growth and with web application they can do all events booking fastly without wasting time.

customers can book event and pay online , when we book a event we go there in search of marquees etc and waste our day and time and spend lot of expense in many term but on our web application people can book all sorts of events easily.

On the other hand, we also provide marquee and caterer owners with a user-friendly environment. So that they can easily interact with our system to add pictures and update their menu with ease. Also “view feedback” of the customer so that they can improve their services and this would help them to grow their business and they could earn a healthy profit. Achieving these goals, we will be able to implement an efficient solution.

Project Implementation Method

project implementation method use Scrum (Agile)

Principles

1. Customer satisfaction through early and continuous software delivery
2. Accommodate changing requirements throughout the development process
3. Frequent delivery of working software
4. Collaboration between the business stakeholders and developers throughout the project
5. Support, trust, and motivate the people involved
6. Enable face-to-face interactions
7. Working software is the primary measure of progress
8. Agile processes to support a consistent development pace
9. Attention to technical detail and design enhances agility
10. Simplicity
11. Self-organizing teams encourage great architectures, requirements, and designs
12. Regular reflections on how to become more effective.
13. Scrum

14. Scrum team roles

15. Product owner: Product expert who represents the stakeholders, and is the voice of the customer.
16. Development team: Group of professionals who deliver the product (developers, programmers, designers).
17. Scrum master: Organized servant-leader who ensures the understanding and execution of Scrum is followed.

18. Scrum events

19. Sprint: Iterative time boxes in which a goal is accomplished. Time frame does not exceed one calendar month and are consistent throughout the development process.
20. Sprint planning: Where the entire Scrum team get together?—?at the beginning of every Sprint?—?to plan the upcoming sprint.
21. Daily Scrum: 15 minute time boxed meeting held at the same time, every day of the Sprint, where the previous day’s achievements are discussed, as well as the expectations for the following one.
22. Sprint review: An informal meeting held at the end of every Sprint where the Scrum team present their Increment to the stakeholders, and discuss feedback.
23. Sprint retrospective: A meeting where the Scrum team reflect on the proceedings of the previous Sprint and establish improvements for the next Sprint.

24. Scrum Artifacts

25. Product backlog: Managed by the Product Owner, it’s where all the requirements needed for a viable product are listed in order of priority. Includes features, functions, requirements, enhancements, and fixes that authorize any changes to be made to the product in future releases.
26. Sprint backlog: A list of the tasks and requirements that need to be accomplished during the next Sprint. Sometimes accompanied by a Scrum task board, which is used to visualize the progress of the tasks in the current Sprint, and any changes that are made in a ‘To Do, Doing, and Done’ format.

Benefits of the Project

The internet makes our life much easier, because of the internet we can do lots of things that makes it easier for a businessman to sell their services. And an ordinary person can facilitate themselves with these services. The stakeholders who are associated with this activity are the marquee owner, caterer owner, and customer. The marquee owner and caterer owner is much concerned about the services and products that they provided to their customer. And customer wants the services that are reliable and rapid and good quality products. Well because of this, they are facing many obstacles which can be addressed to create an opportunity.

The marquee and caterer owner wants their business to grow and they want to organize their business in such a way that customer gets satisfied. And the resources they utilize to fulfill the customer's need will be minimized. They both want that their businesses should be visible legitimately to customers. So that the customer would consider them as one of the options.

Everyone prefers the authentic and rapid delivery of the product and services. Because of this customer want everything on time with good quality as well. The customer wants an easy and authentic booking process, so that anyone can use the system and can communicate easily while being at home.

By observing the mentioned needs of both sides, we are looking at the impressive opportunity to fulfill both end needs in the current pandemic situation and create an opportunity for both sides so that they can full their needs and can get an easy profit. 

Technical Details of Final Deliverable

deliverables that we submitted to our university

List of Figures	1
List of Tables	2
Chapter 1: Introduction	3
Opportunity & Stakeholders	4
Motivations and Challenges	5
Goals and Objectives	6
Solution Overview
Report Outline
Chapter 2: Literature / Market Survey
2.1 Introduction
2.2 Literature Review/Technologies Overview
2.3 Summary
Chapter 3: Requirement Analysis
3.1 Introduction
3.2 Problem Scenarios
3.3 Functional Requirements
3.4 Non-Functional Requirements
Chapter 4: System Design
4.1 Introduction
4.2 Architectural Design
4.3 Detailed Design
Chapter 5: Implementation
5.1 Endeavour (Team + Work + Way of Working)
5.2 Flow Control/Pseudo codes
5.3 Components, Libraries, Web Services and stubs 5.4 IDE, Tools and Technologies
5.5 Best Practices / Coding Standards 5.5.1 Software Engineering Practices 5.5.2 Development Practices & Standards
5.6 Deployment Environment
5.7 Summary
Chapter 6: Testing and Evaluation
6.1 Introduction
6.2 List of Test Scenarios
6.3 Performance and Evaluation	&l

List of Figures

List of Tables

Chapter 1: Introduction

1. 1. Opportunity & Stakeholders

1. 1. Motivations and Challenges

1. 1. Goals and Objectives

1. 1. Solution Overview

1. 1. Report Outline

Chapter 2: Literature / Market Survey

2.1 Introduction

2.2 Literature Review/Technologies Overview

2.3 Summary

Chapter 3: Requirement Analysis

            3.1 Introduction

            3.2 Problem Scenarios

            3.3 Functional Requirements

            3.4 Non-Functional Requirements

Chapter 4: System Design

4.1 Introduction

4.2 Architectural Design

4.3 Detailed Design

Chapter 5: Implementation

5.1 Endeavour (Team + Work + Way of Working)

5.2 Flow Control/Pseudo codes

5.3 Components, Libraries, Web Services and stubs

5.4 IDE, Tools and Technologies

5.5 Best Practices / Coding Standards

5.5.1 Software Engineering Practices

5.5.2 Development Practices & Standards

5.6 Deployment Environment

            5.7 Summary

Chapter 6: Testing and Evaluation

6.1 Introduction

   6.2 List of Test Scenarios

   6.3 Performance and Evaluation

Final Deliverable of the Project Software SystemCore Industry FoodOther Industries Others Core Technology OthersOther Technologies Clean TechSustainable Development Goals Decent Work and Economic Growth, Industry, Innovation and InfrastructureRequired Resources

Elapsed time in (days or weeks or month or quarter) since start of the project	Milestone	Deliverable
Month 1	Introduction	Chapter 1: Introduction 1.1 Opportunity & Stakeholders 1.2 Motivations and Challenges 1.3 Goals and Objectives 1.4 Solution Overview 1.5 Report Outline
Month 2	Literature / Market Survey	Chapter 2: Literature / Market Survey 2.1 Introduction 2.2 Literature Review/Technologies Overview 2.3 Summary
Month 3	Requirement Analysis	Chapter 3: Requirement Analysis 3.1 Introduction 3.2 Problem Scenarios 3.3 Functional Requirements 3.4 Non-Functional Requirements
Month 4	System Design	Chapter 4: System Design 4.1 Introduction 4.2 Architectural Design 4.3 Detailed Design
Month 5	Implementation	Chapter 5: Implementation 5.1 Endeavour (Team + Work + Way of Working) 5.2 Flow Control/Pseudo codes 5.3 Components, Libraries, Web Services and stubs 5.4 IDE, Tools and Technologies 5.5 Best Practices / Coding Standards 5.5.1 Software Engineering Practices 5.5.2 Development Practices & Standards 5.6 Deployment Environment 5.7 Summary
Month 6	Testing and Evaluation	Chapter 6: Testing and Evaluation 6.1 Introduction 6.2 List of Test Scenarios 6.3 Performance and Evaluation 6.4 Summary
Month 7	Conclusion and Outlook	Chapter 7: Conclusion and Outlook 7.1 Introduction 7.2 Achievements and Improvements 7.3 Critical Review 7.4 Future Recommendations/Outlook 7.5 Summary