khushilsheth/event-management-devdynasty

hackathon

Event Management System

1. Introduction

1.1 Purpose

The main purpose of this project is to create a platform where university students can find all events of their university and know the updated news and notices from one place and the organizer of the events can manage the student’s information who were participating in their past events.

1.2 Product Scope

This product is designed for university or any kind of educational institute where their clubs arrange many educational events many times.

2. Overall Description

2.1 Product Perspective

The perspective of this product is to create a platform where students can easily find themselves interested events which are arranged by many clubs of their university and find updated news and notices published by their university.

2.2 Product Functions

Functional Requirements:

1. The system will have five kind of user.
   • Students
   • Clubs
   • Main admin or university authority
2. The clubs can open an event in this system and manage the event through this system properly by following this way
   • They can create an event in this platform.
   • They can take register of students who are interested to participate this event
   • They can send SMS or mail to the students by using this system.
   • They can manage all of student information by this system and they can download student information from this system.
   • They can make certificate for the students through this system. For this we give some template of certificate. They need to use one of them for make certificate. They also print this certificate if this device where the system is running is connected to a printer.
3. Students can see all of the events and can also see the details of this event and they can register them for participating a particular event./li>
4. The main admin is university authority. They can create a club, add an executive member of a club, remove an executive from a club and update news and notices and academic calendar of the university.

Non-Functional Requirements:

1. The system has strong security.
2. The system manages all the student information squirrely and must verify the students who are come from a university who are form a particular university.
3. The system manages the payment issues perfectly.
4. The system is user friendly.

2.3 User Classes and Characteristics

There are three Character of use:

1. University Students
2. University Club
3. University Authority

Use Case Diagram

Class Diagram