TABLE OF CONTENTS

1.1 BACKGROUND:.............................................................................................. 4

1.2 OBJECTIVES: ................................................................................................. 5

1.3 PURPOSE, SCOPE, AND APPLICABILITY: ..................................................... 6

1.3.1 PURPOSE: ........................................................................................................................6

1.3.2 SCOPE: ..............................................................................................................................8

1.3.3 APPLICABILITY: ............................................................................................................9

1.4 ACHIVEMENTS: .............................................................................................. 9

1.5 ORGANISATION OF REPORT....................................................................... 9

CHAPTER 2 SURVEY OF TECHNOLOGIES ...............................................................................12

CHAPTER 3: REQUIREMENTS AND ANALYSIS .......................................................................21

3.1 PROBLEM DEFINITION ................................................................................... 21

3.2 REQUIREMENTS SPECIFICATION ............................................................. 22

3.3 PRELIMINARY PRODUCT DESCRIPTION ................................................. 23

3.5 PLANNING AND SCHEDULING: ................................................................. 24

3.6 CONCEPTUAL MODELS ................................................................................. 28

CHAPTER 4: SYSTEM DESIGN .....................................................................................................41

4.1 BASIC MODULES: ......................................................................................................................41

4.2 DATA DESIGN: ................................................................................................. 42

4.2.1. Data Integrity and Constraints: ..................................................................................42

4.2.2 Database Structure: .......................................................................................................43

4.3 PROCEDURAL DESIGN: ................................................................................. 45

4.3.1 LOGIC DIAGRAM ..........................................................................................................45

4.3.2 ALGORITHM DESIGN: ...................................................................................................45

4.4 USER INTERFACE DESIGN: ........................................................................... 47

4.5 SECURITY ISSUSES: ....................................................................................... 50

4.6 TEST CASES DESIGN: .................................................................................... 51

1
 TABLE OF FIGURES

Figure 1 Logo of Fest Assist 6

Figure 2 Fest Assist System Communication Diagram 7

Figure 3 Visual Studio Components 12

Figure 4 Visual Studio Menu 13

Figure 5 ASP.NET Architecture Diagram 14

Figure 6 ASP.NET Lifecycle 14

Figure 7 ASP.NET Page Lifecycle 15

Figure 8 HTML Document Structure 19

Figure 9 SSMS Main Console 20

Figure 10 PERT Chart 25

Figure 11 Gantt Chart 27

Figure 12 Iterative model 28

Figure 13 Admin Flowchart 31

Figure 14 Marketing Team Flowchart 32

Figure 15 PR Team Flowchart 33

Figure 16 Participants Flowchart 34

Figure 17 Level 0 DFD 35

Figure 18 Level 1 DFD 35

Figure 19 Class diagram 36

Figure 20 Use Case to Add Sponsor 37

Figure 21 Use Case to Register for An Event 38

Figure 22 State Chart Diagram 40

Figure 23 Logic Diagram 45

Figure 24 Login Page 48

Figure 25 Sponsor Registration Page 49

2
 LISTS OF TABLES
Table 4-1: Validation for Login 42
Table 4-2: Validation for Registration1 42
Table 4- 3 : Validation for Registration2 43
Table 4-4: Test case design Table 51

3
 CHAPTER 1: INTRODUCTION
1.1 BACKGROUND:
In olden days for a good career academics used to play an important role. All
the universities and colleges use to give more attention towards the academics of
students. But in today’s world not only academic but social knowledge is equally
important to give the students career a better shape. For this colleges organize the
Fest. This Fest helps the student to showcase their talent. Groom themselves by
taking part in multiple cultural, technical activities, competitions. Not only this student
also participates in managing the Fest which improves their managing skills and take
them towards a path where he/ she can get a good job in management streams.

It encourages a person to improve his/her specialized aptitudes yet in addition

help him/her to develop the administration, correspondence and occasion taking care
of abilities by being a piece of Fest association group.

Fest includes different exercises held by various gathering of individuals, for

example, Promoting Group, Open Connection Group, Coordination’s Group,
Innovativeness Group, DPT Group, Execution Group, Administrator Group, Security
Group, Money Group, F and B Group and Occasion handler which goes about as the
mainstays of the fest. Not only these but the participants participating in the fest, the
sponsors giving the sponsorships, the faculties also play a vital role in the fest.

The different exercises included such advancing the fest, getting the members,
getting the supporters, sorting out specialized and non-specialized occasions, making
pennants, making handouts, making clusters are all pre-fest exercises.

The post-fest exercises are coordinators repayment, conveyance of

gratefulness testaments, mingling the fest, mingling the patrons, restoring the
supporters their pennants and so forth this all pre and post exercises at times become
a dreary errand to deal with. To make this fest association basic for the fest
coordinators here comes the "FEST ASSIST".

This framework gives a solitary stage to every one of the columns referenced
above meet up and have an efficient less administrative work method for dealing with
the fest.

By using this system:

• The participants get the platform to get information about the fest.
• The users can query if they have any confusion relating the fest
or events by the instant chat functionality in the system.
• Users get immediate email on successful registration with
schedule on event participated in.
• Sponsors get immediate email with the receipt.

4
 • Travelling expense of the organizers is being maintained.

1.2 OBJECTIVES:
The objective of the Fest Assist website is to allow the Fest Assist users
to get details of all event, fest and competition happening in the college. So, all
users in of the website are aware about the event.
This allow interested user to participate in the events held in the fest or
competition conducted in the college and also help to participate in events or
competition conducted in the college level without facing the difficulty of whom
to contact.
Fest Assist website also has objective to solve the difficulty of Head
conducting Fest to gather the name of user who is participating in different
events and collect more amount compared to manual process.
This website also helps the users of other colleges. Our application
provides a medium where the users can get the schedule of all the events by
just opening our website.
The objectives of the project are:
• Provides the information about the fest and the events.
• Online registration of the events.
• Online registration of the sponsors.
• Keeps record of all the activities of the fest.
• Keeps the record of all the participants and sponsors.
• Keeps the record of the travelling expense of the organizers of the fest.
• Event reminder functionality.
• Sending email on successful registration with schedule of event
participated in.
• Immediate email notification with receipt on becoming a sponsor.
• Instant chat functionality available for participants to resolve their query.
• Provide separate account login facility.
• Provide separate admin login facility.
• Provide separate marketing group login facility.
• Provide separate personal relation group facility.

5
 Figure 1 Logo of Fest Assist

1.3 PURPOSE, SCOPE, AND APPLICABILITY:

1.3.1 PURPOSE:
The main purposes of Fest Assist website are to bridge the communication gap,
between the participants and the organizers and between the sponsors and the
organizers while conducting events, competitions and fests in the college. This
would help the participants without need of worrying of whom to contact to get
the subtleties of the events, competitions and fest held in the college, how to
take part in the events and amount to be paid to participate in the events , if the
participate have any query they can ask directly through the instant chat
functionality in this website.
This website provides easiness of finding the event schedule at one place. The
members will discover the occasion plan for one website page rather to visit
unique. This system satisfies all the foregoing needs and avoids the drawbacks
of old systems and provide better, more timely, effective communication to
coordinate the events.
This purpose of the project is to do all the activities of the fest online it can be
participation or sponsors registration, sharing information, maintaining records,
solving participants query related to events. This would help the organizers
organizing the events without having wasting the time to talk to individual,
convincing them to participate in the event, collecting amount. Since, giving the
details to every individual which creates the event more burdensome so Fest
Assist solve this problem.
Fest Assist website also allows the users who are interested in participating the
events, they can participate through this website. They will get the details of the
events held in college. If they are interested in participating then they register
online then they get the email of registering successfully and once they pay the
money to the Admin, they get the email with the schedule of the respective event
they have participated in. This website is also useful for marketing team for
registration of the sponsors which sends the immediate email with the receipt to
the sponsors on becoming a sponsor.

6
 Manages Manages
ADMIN
Manages

PARTICIPANTS ORGANIZERS SPONSORS

Manages/Organizes
Provide Funds
Participates

Manages
Payments/Claims
Expense Makes Payments
Makes Payments

Figure 2 Fest Assist System Communication Diagram

7
1.3.2 SCOPE:
The scope of the project is doing the things online, increase the speed of accessing
the data when it is required and reduce the paper work.
Fest Assist is the website of management of Technical fest, events and competitions.
The existing websites have the features like:
• Give the detailed information of the Fest.
• Give the details of all the events in the Fest.
• Give the details of the last years sponsors.
• Give details of the pillars of the fest.
The main issue of the existing websites is that, it is relatively static in nature.
The existing website only provides the description of the fest, members, events and
previous years sponsors.
Fest Assist website will provide various functions like:
• The users get the information of the events or competition held in the College.
So that interested user can participate in the competition and events without
the need of face to face communication.
• Users can participate via the online mode.
• Users from other college can also see the information and participate in
events.
• Marketing team can register for the sponsors. After registering the sponsors
will get the email with the receipt which includes the type of sponsors, total
amount and the deliverables given to them by us.
• Participants can solve their queries related to events through the instant chat
functionality.
• Maintains the current year and upcoming years record.
• Post-activities of reimbursement claim for the organizers.
• Email notification functionality for each individual.
• Reminder functionality to give reminders of the event.
• Head conducting the Fest or Competition has to just enter the details of the
Fest or Competition held in the college.
• Admin get the details of the users participated and in which events the
particular user participated.
• Admin also gets the information about the organizers travelling expense and
also gets the information about the sponsors contributed to our fest.

8
 1.3.3 APPLICABILITY:
This project is applicable to college where manually giving information
about the competition, fest, events is not feasible. This website will
provide feasible solution like events details, alert, online registration for
an event, enquiry etc. this website will help to get all the information
about the Fest.
This website will also applicable to organisation besides college that
helps in getting information of various functions or events held in the
college. It will also applicable to the organisation to get the details of the
various functions and events held in that organisation with some
modification to this application. This website will also applicable for the
sponsors to register and get immediate email with the receipt including
the deliverables provided to them.

1.4 ACHIVEMENTS:
Through this project I gained the knowledge of how to understand the real-
world problem and to think of with digital solution to the people. I understood
the use of the models like Data Flow Diagram, ER diagram, Sequence
diagram, use case diagram, etc. that we learned in our syllabus and how to
apply that models in true situations. Also, I have learned to integrate various
application in my project. I have gained the knowledge of Visual studio that
is, how to build complex website in simple way.
• How to use Microsoft SQL database.
• Structure of Microsoft SQL database.
• How to link Microsoft SQL with the visual studio.
• How to communicate between the users and organizers, sponsors and
organizers.
• How make less use of paper.
• Layout of webpages in visual studio.

1.5 ORGANISATION OF REPORT

CHAPTER 1: INTRODUCTION:

This chapter contains the details of existing website, limitation in the

existing website, the reason which give rise to the proposed system.
This chapter also contains the details of the proposed system like it
objective of creating Fest Assist website, purpose, scope, applicability
sand what I have achieved by undertaking this project.

9
CHAPTER 2: SURVEY OF TECHNOLOGIES:
This chapter contains all the details of the technology that I have used
as a backend and frontend for building the project. This chapter also
contains the details of why I have selected particular technology for
backend and frontend.
I am utilizing C# as a Front End and Microsoft SQL Database is
utilized as a back end. I am creating Fest Help site with the assistance
of Visual Studio.
CHAPTER 3: REQUIREMENTS AND ANALYSIS:
This chapter contains the details of problem that were arise and how
this system that act as solution to the problem.
The issue is there is no such site which will give the every one of the
details of the fest held in the college. Sometimes, Users just here voice
of fest held in the College. Even though some user wants to participate,
they can’t because of some communication barriers.
The requirements of this app are:
• The admin should login and enter the details of the new competition or
events held in the college.
• The students should get the details of the events.
CHAPTER 4: SYSTEMS DESIGN:
This chapter contains the details of website design.
This website has 4 section:
1. Admin.
2. User.
3. Marketing.
4. Public relation.
The fest Head will go to Create new admin section, where he
logins with Email ID. If the authentication is successful then he
can create data or events details and user information. He can
also modify the data and post the news and pictures of the fest
in news feed.
In User section, the student can view the information of the Fest
and Competition held in the college. Users can also query if they
have doubt, they can query. Also, there is buttons Participate. If
user click Participate button get details where students get details

10
 how to make payments. User can view the all-news and pictures
uploaded by admin.
CHAPTER 5: IMPLEMENTATIONS AND TESTINGS:
This chapter contains the details of various modules, codes and
various libraries I have imported to successfully implement the
project. It also contains the details of process or work I have done
to make my code efficient.
This chapter also contains the details of various testing approach
I used to perform Unit Testing: To test the individual unit or
module in my project.
Integration Testing: It contains the details of testing used after
all the module.
CHAPTER 6: RESULTS AND DISCUSSION:
This chapter shows the details of the Test Results after testing
the software and generate report on the basis of the Test results.
This will detect why the Test Results deviated from the Test
Cases. This will also show behaviour of the software when Inputs
are different from the one written in the Test Cases.
This chapter also contains the details of working of the software
and the different functions in the projects. It should also contain
the User Documentation, which provides the means that user
reading a manual is able to understand working and the
functionality of the project.
CHAPTER 7: CONCLUSIONS:
This chapter summarise about all the important point of all the
other chapter. It also shows the limitation in the proposed system
and details about future plan to explore the scope of the project.

11
 CHAPTER 2 SURVEY OF TECHNOLOGIES
The main consideration for building website is to choose the technologies that will best
satisfy our need apart from the function of our website and the resources it will need.
There are many technologies available for building the websites. The technologies
used for developing the Fest Assist are as follows:
Front-End Tool Visual Studio 2017, Asp.Net
Language Used C#, HTML
Back-End Tool SQL Server Management Studio
Front-End Tool
VISUAL STUDIO:
Visual Studio is a Microsoft developed Integrated Development Environment
that helps to develop Web Application, Mobile Applications etc. A developer can code
for a website, mobile application using various languages such as for front end -HTML,
CSS etc. For Back end – C#, VB, java script, python etc. It is available for Windows
and MacOS.
There are three editions available for Visual Studio
Community Edition: It is a free version with all the features available in Professional
edition which was announced in 201lps an individual to develop various websites,
mobile apps etc.
Professional Edition: A commercial edition supported in version 200 or later. It
provides various benefits as Feasibility, productivity, collaboration, subscriber benefits
like plus Azure, Pluralsight
Enterprise Edition: An integrated solution for a greater team size with a 90-day trial
period. High scalable and high-quality software deliverable is the benefit of this edition.

Figure 3 Visual Studio Components

12
 Visual Studio has various components:
1. Code Editor: Section to write code
2. Output Window: Displays Output, Warnings, Error Messages and Debugging
information
3. Solution Explorer: Displays currently used files
4. Properties: Additional information about selected objects
User can add or remove windows using the View option in Menu Bar.

Figure 4 Visual Studio Menu

Various menus available in visual studio are –

1. File Menu: Create, Open, Save the project
2. Edit Menu: Search, Modify, Refactor code
3. View Menu: Open Additional tools available in Visual Studio
4. Project Menu: Helps to add files and dependencies in the project
5. Tools Menu: Helps to change Settings and functionalities to Visual Studio
VS Package a language service to add different languages is supported by Visual
Studio. Visual Studio provides three services SvsSolution – provide functionality to
enumerate solutions and projects in Visual Studio, SVsUIShell – provide UI
functionalities as toolbar, tabs. SVsSheel -deals with VSPackages registration.

ASP.NET:
Microsoft in 2002 provided a web development platform called ASP.Net. The
word ASP stands for Active Server pages and .Net is Network Enabled technology.
ASP.Net works on HTTP protocol, uses HTTP command policies to establish a
bilateral communication between web and server.
The ASP.Net Application codes can bee written in various languages as C#,
J#, Visual Basic.net, Jscript etc.
The architecture of .Net is based on following-
1. Language: Vb.Net and C# languages are used to develop web applications
2. Library: The .NET framework includes a standard set of libraries. The Most
common library is a web library which has all the components to develop web
applications
3. Common Language Runtime: Performs activities such as exception handling,
memory management, debugging, code execution, security checking etc.

13
 Figure 5 ASP.NET Architecture Diagram

ASP.NET Lifecycle – Below are the various stages of typical ASP.NET Web
Application
1. Application Start: The user request to the web server calls the Application Start
Method.

Figure 6 ASP.NET Lifecycle

2. Object Creation: This involves the creation of HTTP Context, HTTP Response
and HTTP Request by webserver. HTTP Context - a container for HTTP
Response and HTTP Request, HTTP Response – contains response sent to
the client, HTTP Request – contains the current request.

14
3. HTTPApplication Creation: An object created by Webserver that processes each
request sent to application.
4. Dispose: This method is called before application instance is destroyed.
5. Application End: Application is unloaded from memory.

ASP.NET Page Lifecycle – Below are the various stages of APS.NET webpage

1. Page Request: If the page request is for the first time then the server needs to
compile page and parse the response to send it to the requesting user. Else the
server checks to cache if output exists

Figure 7 ASP.NET Page Lifecycle

2. Page Start: includes two objects Request and Response that holds the information
which was sent back to user when page is requested and information which is set
back to user respectively
3. Page Initialization: Initializes all controls on web page
4. Page Load: The page is loaded with default values
5. Validation: Sometimes the validations are set on the form which when violated
leads to error in loading page.
6. Postback event handling: This event is triggered when the same page is loaded on
a click by user
7. Page Rendering: All information being saved is sent to user as complete webpage
8. Unload: All the objects used are removed from the memory.

15
 Languages Used
C#:
An object-oriented programming language developed in 2002 by Microsoft
used with XML webservice on .NET platform for development of websites. C# being a
modern, structured language; object and component oriented; ease in learning and
suitability with various platforms makes it a widely used professional language.
Design Goals:
ECMA standard records these plan objectives for C#:
• The language is expected to be basic present day broadly useful article
situated programming language.
• The language and usage thereof ought to offer help for programming
designing standards, for example, solid sort checking cluster limits
checking identification of Endeavours to utilize uninitialized factors and
Programmed trash accumulation programming heartiness solidness and
developer profitability are significant.
• Convey ability is significant for source code and software engineers
particularly those effectively acquainted with C and C++
• Support for internationalization is very important.
• C# is intended to be suitable for writing applications for both hosted and
embedded systems, ranging from the very large that use sophisticated
operating systems, down to the very small having dedicated functions.
• Although C# applications are intended to be economical with regard to
memory and processing power requirements, the language was not
expected to finish straightforwardly on execution and size with C or low-
level computing construct.
Features:
C# 2.0
• Generics
• Halfway types
• mysterious strategies
• Iterators
• Nullable worth sorts
• Getter/setter separate openness technique
• Bunch transformations
• Co- and contra- change for agents
• Static classes
• Delegate induction

16
C# 3.0
• Certainly, composed neighbourhood factors
• item and gathering initializers
• Auto- actualized properties
• Unknown sorts
• Expansion strategies
• Inquiry articulations
• Lambda articulation
• Articulation trees
• fractional strategies
C#4.0
• Dynamic binding
• Named and discretionary contentions
• conventional co and contra change
• implanted interop types
C#5.0
• Asynchronous methods
C# 6.0
• Compiler as an administration
• Import of static kind individuals into namespace
• special case channels
• anticipate in catch/at long last squares
• Auto property initializers
• Default esteems for getter- just properties
• articulation bodied individuals
• invalid propagator
• name of operator
• Dictionary initializer
C# 7.0
• Inline out variable declaration
• Pattern matching
• Deconstruction
• neighbourhood capacities
• Digit separators
• double literals
• Ref returns and locals
• Generalized async return types
• articulation bodied constructors and finalizers

17
 • Throw can be utilized as an articulation

C# 7.1

• Async principle
• Default strict articulations
• Inferred tuple component names

C# 7.2

• Reference semantics with worth kinds

• Non-trailing named contentions
• Leading underscores in numeric literals
• Private ensured get to modifier

C# 7.3

• Accessing fixed fields without sticking

• Reassigning ref nearby factors
• Using initializers on stackable clusters
• Using fixed proclamations with any sort that supports an example
• Using extra conventional limitations

C# 8.0

• Randomly struct individuals

• Default interface individuals
• Switch articulations
• Property, Tuple and positional examples
• Using statements
• Static nearby works
• Disposable ref structs
• Indices and Ranges
• Null-blending task
• Async Streams

HTML:
A hypertext mark-up language that is used in creating documents to be hosted
on WWW (world wide web). It helps in defining the layout of document using various
tags. It is a standard mark-up language used in various web pages. The HTML
elements have start and end tags. Each element of HTML is enclosed in angular

18
brackets.HTML elements also has attributes that provides additional information about
the elements.
HTML pages have following building blocks:
1. <!DOCTYPE html> - defines the document to be HTML5
2. <html> - root element of html page
3. Lang - defines the display language of document
4. <meta> - contains meta information
5. charset - defines character set used
6. <title> - defines the title of web page
7. <body> - contains the page content that is visible
8. <h1> - defines the heading
9. <p> defines the paragraph

Figure 8 HTML Document Structure

Back-End Tool
SQL SERVER MANAGEMENT STUDIO:
It is a product application previously propelled with SQL Server 2005 that
is utilized for designing, overseeing, and regulating all parts inside Microsoft
SQL Server. The instrument incorporates both content editors and graphical
devices which work with items and highlights of the server

19
 A focal element of SSMS is the Object Explorer, which enables the client
to peruse, select, and follow up on any of the items inside the server. It
additionally, delivered a different Express release that could be openly
downloaded, anyway late forms of SSMS are completely fit for interfacing with
and deal with any SQL Server Express case.
Microsoft likewise consolidated in reverse similarity for more seasoned
adaptations of SQL Server therefore permitting a more up to date form of SSMS
to interface with more established renditions of SQL Server occurrences. It
additionally, accompanies Microsoft SQL Server Express 2012, or clients can
download it independently.

Figure 9 SSMS Main Console

Various tasks to be performed by SSMS are

1. Creating database tables

2. Creating and maintaining roles
3. Querying to get the data
4. Import and export data
5. Keep backup of data
6. Prepare stored procedures

20
CHAPTER 3: REQUIREMENTS AND ANALYSIS

FEASIBILITY STUDY:
➢ Technical Feasibility:

Right away watch the proposed structure is in certainly possible

or not and to choose the development and bent imperative to do
the endeavour. If they are not available by then find the response
for get them.

➢ Economic feasibility:

While considering financial achievability, it is checked in centres

like execution, information and data from the structure. SQL
Server Studio available in one heap of the windows working
system and requires additional programming cost is freeware and
doesn’t procure the cost to the endeavour Backend database
development is a freeware.

3.1 PROBLEM DEFINITION

The main problem in the college that I have observed whenever any fest or
competition held in the college.

1. Students conducting the fest or competition have to go to every classroom

to give details of the events like:

• When this fest will be held?

• What are events or competition in that events or competition?
• Details of fest/competition.
• Meet individual student, give them information and urge to take
interest in the events competition.

So, much of the time and effort are wasted of students conducting
the fest. Due to this manual process, their resources are diverted
from the main activity like making arrangement for the Fest, inviting
guest, making Fest grand success.

2. Students who want to encouragingly participate in the

events/competition are sometimes not able to participate because:

21
 • Since, student conducting fest announce about the fest or
competition by visiting every class. If, however missed
lecture then they cannot get the complete details.
• Student interested in taking part in the fest sometimes face
problems like:

Whom to contact?

Procedures for participating in the events in the fest.

• They want to get details of the events in the fest without

contacting any people and wasting time.

Due to this problem, the interested student cannot take part

in the Fest or competition.

3.2 REQUIREMENTS SPECIFICATION

3.2.1 FUNCTIONAL REQUIREMENTS:

Functional requirement is the activity of the system. It

includes the operations perform by the system. What is the reason
and need, this system is need to be develop, they are as follows?

• Every user should be register.

• Maintain the records of every user separately.
• Doing all the activity in digital format.
• For register task no need of volunteer.
• Participate in event at any time, and get the immediate
participation email.
• View the events details.
• View the fest details and core members names, event head
names.
• For doing advertisement of sponsors at digital platform.
• To Register the sponsors, and sending them the receipt by
immediate email.
• To solve users query related to fest by instant chat functionality.
• To store travelling expense of organizers.

3.2.2 NON- FUNCTIONAL REQUIREMENTS:

• Availability: An alternative database could be used as backup in case

of failure or if the main server goes down could increase the availability
of system.

22
 • Reliability: System will work without loss of any data even in the phase
of numerous failures. All the personal details of the customer will be
stored in “Encrypted form” in order to secure the data.
• Security: The admin of the website is only going to handle the making
and processing of various activities on the system. All the information
will be stored in database securely and data will be prevented from
unauthorized access i.e. only admin will be allowed to login.
• Safety: The location of the customer to which he/she wants to shift is
not visible to anyone and the username and password of the vehicle
number must be safe. The admin will host the server.
• Maintainability: System will maintain the following data: Name,
username, emailed, password.

3.3 PRELIMINARY PRODUCT DESCRIPTION

3.3.1 REQUIREMENTS AND OBJECTIVES OF THE NEW SYSTEM:

• Reduces clerical work as most of the work done through

website.
• Less Time Consuming.
• Efficient and accurate database management.
• Data retrieval is faster.
• Provision for permanent database.
• Maximizes availability i.e. 24x7 solutions.
• Reduces paper work.

3.2.3 FUNCTIONS AND OPERATIONS OF THE WEBSITE:

• User Login and Registration.

• Organizers Login and Registration.
• Admin Login and Registration.
• View events details.
• Read data from database.
• Display the records.
• Registration for event.
• Sponsor registration.
• Instant chat functionality.
• Sending Immediate email with receipt on being a
sponsor.
• Sending Email to participates on successfully
participating with the details of the events.

23
3.4 SOFTWARE AND HARDWARE REQUIREMENTS:
3.4.1 SOFTWARE REQUIREMENTS:

• FRONT END: Visual studio 2017 with C#

• BACK END: SQL Server database
• OS: WINDOWS 10

3.4.2 HARDWARE REQUIREMENTS:

• Processor: Intel core i3

• Memory: Minimum 4GB RAM
• HARD DISK: Minimum 50GB free disk space.
• System Type: 64bit operating system.

3.5 PLANNING AND SCHEDULING:

3.5.1 PERT Chart:

PERT was developed to take account of uncertainty surrounding

estimates of task duration. It was developed in an environment of
expensive, high-risk and state-of-the-art projects – not that dissimilar to
many of today’s large software projects.

The method is very similar to the CPM technique, but instead of

using a single estimate for the duration of each task, PERT requires three
estimates.

• Most likely time: the time we would expect the task to take
under normal circumstances. We shall identify this by the
letter m.
• Optimistic time: the shortest time in which we could expect to
complete the activity, barring outright miracles. We shall use
the letter a for this.
• Pessimistic time: the worst possible time, allowing for all
reasonable eventualities but excluding ‘act6s of God and
warfare’. We shall use letter b for this

PERT then combines these three estimates to form a single

expected duration, te , using the formula

te = a+4m+b / 6

24
 The PERT technique uses the following three step method for
calculating the probability of meeting or missing a target date:

• Calculate the standard deviation of each project event;

• Calculate the z value for each event that has a target date;
• Convert z values to a probability

Figure 10 PERT Chart

25
3.5.2 Gantt Charts :

A Gantt Chart is a sort of bar diagram that outlines an undertaking plan,

named after its innovator, HENRY GANTT, who planned such a graph around
the years 1910-1915.

Present day Gantt Charts additionally show reliance connections among

exercises and current calendar status.

Gantt Charts are helpful instruments for breaking down and arranging
complex undertakings.

• Help in arranging out the errands that should be finished.

• Give a reason for booking when these errands will be
completed.
• Allow to design the designation of assets expected to finish
the undertaking.
• Help us to work out the basic way to venture where we should
finish it by a specific date

At this point when a task is in progress, Gantt Charts help to screen

whether the venture is on calendar.

The fundamental goal of a Gantt graph is to survey to what extend a

venture should take and to build up the request in which errands should be done
by consumption of the task.

26
 Jul 2019 Aug 2019 Sep 2019 Oct 2019

Figure 11 Gantt Chart

27
3.6 CONCEPTUAL MODELS

SDLC: Iterative Model

Programming Development Life Cycle or SDLC is a model of a point by point

plan on the best way to make, create, actualize and in the long run crease the product.
It is an entire arrangement plotting how the product will be conceived, raised and in
the end be registered from its capacity.

In the Iterative model, adaptations until the point that the total framework is
actualized and prepared to be send. An iterative life cycle show does not endeavour
to begin with a full determination of necessities. Rather, advancement starts by
indicating and actualizing simply part of the product, or, in other words to recognize
encourage necessities. This procedure is then rehashed, delivering another form of
the product toward the finish of every emphasis of the model.

Iterative Model- Design:

Iterative process begins with a basic execution of a subset of the product

prerequisites and iteratively improves the developing adaptations until the point that
the full framework is actualized. At every cycle, outline changes are made and new
utilitarian abilities are included. The fundamental thought behind this technique is to
build up a framework through rehashed cycles (iterative) and in littler bits at once
(incremental).

Figure 12 Iterative model

28
The Accompanying outline is a portrayal of the Iterative and
Incremental model – SDLC Iterative Model:

Iterative and Incremental advancement is a blend of both iterative outline or

iterative strategy and incremental form show for improvement. "Amid programming
advancement, in excess of one emphasis of the product improvement cycle might be
in advancement in the meantime."

This procedure might be portrayed as a "transformative obtaining" or

"incremental form" approach." In this incremental model, the entire prerequisite is
partitioned into different forms. As the product advances through progressive cycles,
tests must be rehashed and reached out to check every form of the product.

Iterative Model - Application:

This model is frequently utilized in the accompanying situations:

• Requirements of the total framework are obviously characterized

and comprehended.
• Major necessities must be characterized; in any case, a few
functionalities or asked for improvements may advance with time.
• An opportunity to the market requirement.
• A new innovation is being utilized and is being scholarly by the
improvement group while taking a shot at the task.
• Resources with required ranges of abilities are not accessible
and are wanted to be utilized on contract reason for particular
cycles.
• There are some high-hazard highlights and objectives which may
change later on.

Iterative Model - Pros and Cons:

The upside of this model is that there is a working model of the framework at
a beginning time of advancement, which makes it less demanding to discover practical
or configuration defects. Discovering issues at a beginning period of improvement
empowers to take remedial measures in a constrained spending plan.

The inconvenience with this SDLC demonstrate is that it is relevant just to vast
and massive programming advancement projects.

The upsides of the Iterative and Incremental SDLC Model are as per the
following: Some working usefulness can be produced rapidly and right off the bat in
the existence cycle.

29
 • Less expensive to change the extension/necessities.
• Testing and troubleshooting amid littler emphasis are simple.
• Risks are distinguished and settled amid cycle; and every emphasis is an
effortlessly overseen breakthrough.
• Easier to oversee chance - High hazard part is done first.
• With each addition, operational item is conveyed.
• Issues, difficulties and dangers recognized from every addition can be
used/connected to the following augmentation.
• Risk examination is better.
• It underpins evolving necessities.
• Initial Operating time is less.
• Better suited for substantial and mission-basic undertakings.
• During the existence cycle, programming is delivered early which encourages
client assessment and input.

The detriments of the Iterative and Incremental SDLC Model are as

per the following:

• More assets might be required.

• Although cost of progress is lesser, however it isn't extremely appropriate for
evolving necessities.
• More administration consideration is required.
• Defining augmentations may require meaning of the total framework.
• Not reasonable for littler projects.
• Management multifaceted nature is more.
• End of project may not be known which is a hazard.
• Highly gifted assets are required for hazard examination.

30
1. Flowchart:

Figure 13 Admin Flowchart

31
Figure 14 Marketing Team Flowchart

32
Figure 15 PR Team Flowchart

33
Figure 16 Participants Flowchart

34
2. Data Flow Diagrams:

Figure 17 Level 0 DFD

Figure 18 Level 1 DFD

35
3. Class Diagram:

Figure 19 Class diagram

36
 4. Use case Diagram:

Figure 20 Use Case to Add Sponsor

USE CASE SCENARIO:

This use case is to add sponsor to the Fest Assist Website. Below is the
process

1. The Marketing Member visits the Sponsor

2. Informs the Sponsor about the benefits they would get on being the part of
Fest
3. Marketing Member then Add the details of Sponsors to Fest Assist System
4. Also selects the type of sponsorship agreed by sponsor and also adds the
amount details.

37
 5. On receiving the payment from Sponsor the marketing member submits the
sponsor details
6. The Sponsor then receives the receipt of payment made via email

Figure 21 Use Case to Register for An Event

USE CASE SCENARIO:

This use case is to register the participant for an event. Below is the
process

1. The Participant Click on the list of events displayed

2. Participants then reads the details of each event

38
3. Participant then registers for the event they want to participate
4. PR member collects the payment from the participants
5. PR member marks the status of the participant as paid in the system
6. Participant then receives the receipt of payment via email

39
5. State Chart Diagram:

Figure 22 State Chart Diagram

40
 CHAPTER 4: SYSTEM DESIGN
4.1 BASIC MODULES:
1. Login and Registration:
It will allow users to login their accounts and if they are not
register user then they have to do registration first. After the
successful registration and login, they can access the features of
the app.
2. News feed and sharing part:
It is the window where the activities related to fest will be
shown and if any post or story will be posted by admin then it will
show here also.
3. Follow us:
It will display the all the social media links of the fest.
4. User account module:
It will display the user account information and contact details.
5. Sponsors module:
It will display all the sponsors name and logo.
6. Core members:
Information about the core members of the fest.
7. About fest:
Short description about the fest.
8. Events module:
List of all the events of the fest and user can see the price of
the events and timing of the events. In this module click in on the
event name he will get participate button and he can do online
registration process for an event online.
9. Participated module:
It will display the user to participated events list on which he
is participated.
10. Notification module:
It will push the notification to all the register users, 30
minutes before event will start with details off venue and event
time.
11. Admin module:

41
 It will allow admin to post the images in the new feed and also
upload the sponsors logo in the sponsors module.

4.2 DATA DESIGN:

4.2.1. Data Integrity and Constraints:

• Validation for Login:

Email-id It should not be empty.

Password It should not be empty.

Table 4-1: Validation for Login

• Validation for Registration of participants:

Name It should not be empty.

Email ID It should not be empty or

enter valid email id.

College Name It should not be empty.

Phone Number It should not be empty or

enter valid phone number.

Password It should not be empty.

Table 4-2: Validation for Registration1

• Validation for registration of sponsors:

Sponsor Name It should not be empty.

Name of shop It should not be empty

Email ID It should not be empty or

enter valid email id.
Contact number It should not be empty.

Type of sponsor It should be checked it

should not be left unchecked.

Amount It should not be empty.

42
 Table 4- 3 : Validation for Registration2

4.2.2 Database Structure:

• Authentication

43
44
4.3 PROCEDURAL DESIGN:
4.3.1 LOGIC DIAGRAM

Figure 23 Logic Diagram

4.3.2 ALGORITHM DESIGN:

Step 1. Select the right option from the main window log in or register

Step 2. If log in is click then go to log in page.

Else go to registration page.

Step 3. Validate the information fill by user. If validation of data is done then
registration the user and go to login activity.

Step 4. If login successful then go to newsfeed activity.

45
Step 5. Else go to password reset activity when it selected and reset the password and
again go to login page.

Step 6. View the news feed, read the notice.

Step 7. If menu button is click show the menu list.

i. About user
ii. About fest
iii. Events
iv. Participated
v. Core members
vi. Admin Login
vii. Follow us
viii. Sponsors
ix. Logout

Step 8. If about user is click show the user info.

Step 9. If about fest is click show the fest introduction.

Step 10. If event is click show the event list.

i. Select the event category
ii. If event category is selected, show the list of events in that
category.
iii. If event is selected then go to register in an event activity.

iv. If PR code is entering then verify the PR code and if PR code verified
then register that user into that event participated list.
v. Go back to event category activity.

Step 11. If participate is click show the list of participated events with venue and timing
of an event.

Step 12. If core member is click show the core members name.

Step 13. If follow us is click show the social media links.

i. If any button is click open the social media application according to the
social media button is click.

Step 14. If sponsors are click show the name and logo of sponsors.

46
 Step 15. If any back action performs go to previous window and display the info again.

Step 16. If logout option is selected then clear the user session from the device and go to
main activity login and register activity.

Step 17. If admin login selected then open the admin activity.

i. In Admin activity select the admin panel or event head panel.

ii. If admin panel is selected then go to admin panel activity. If event head
activity is selected then go to event head admin panel. iii. In Admin panel if
sponsors upload image is selected then go to sponsors upload activity. iv. If
news feed image upload is selected in then go to news feed upload image
activity.

Step 18. Close the app.

4.4 USER INTERFACE DESIGN:

User Interface Design (UID) or User Interface engineering (UIE) is the design
of user interfaces for machines and software, such as computers, home appliances,
mobile devices, and other electronic devices, with the focus on maximizing usability
and the user experience. The goal of user interface design is to make the user’s
interaction as simple and efficient as possible, in terms of accomplishing user goals.

47
Figure 24 Login Page

48
Figure 25 Sponsor Registration Page

49
4.5 SECURITY ISSUSES:
The significant risk parameters incorporate into security levels which
inhering decides the level of application security. The fundamental duty to
consider the application improvement advancements expected to ensure
user information. In the event that the information isn't anchor then the
outsider access can happen. There are a couple of focuses that are
important to consider.
They are:
o Insecure Data Storage:
Another security gap in common mobile applications is the lack of
secure data storage. A common practice among developers is to depend on
the customer's memory for the data. But the client storage is not an isolated
spatial environment in which security breaches are not possible. In the event
that an opponent acquires a mobile device, this data is accessible,
manipulated and easily usable.
This gives a great boost to the security of mobile applications and
reduces their dependence on the default cryptography.
o Poor Authentication:
If the authentication is not good then the data of the
system is insecure.

o Data duplication:
There is a chance of
data duplication.
o Data storage:
Data are store in a database and here the chance of data
leak because the servers are store on different location in different
country.
o Push Notification:
Pop-up messages which ought to be planned with the goal
that individual information does not show up on the screen all of a
sudden. Framework engineers ought to likewise execute the
component of programmed logout. This usefulness will enable you
to shield the clients from the unapproved access of private data.
o Data duplication:
There should be a chance of data duplication like email
and in phone numbers.

50
 4.6 TEST CASES DESIGN:
In software engineering, test design is the act of creating and writing test cases
for testing software.
Test design could require all or one of the following:
• Knowledge of the software and the business area it operates on,
• Knowledge of the functionality being tested.
• Knowledge of the testing techniques and heuristics.
• Planning skills to schedule in which order the test cases should
be designed, given the effort, time and cost needed or the consequences
for the most important and risky features.
Well-designed test suites will provide for an efficient testing. The test
suite will have just enough test cases to the test system, but no more.
This way, there is no time lost in writing redundant test cases that would
unnecessarily consume time each time they are executed. In addition,
the test suite will not contain brittle or ambiguous test cases.
Test Case 1:

Test Suite ID TS001

Test Case ID TC001

Test Case To verify that user is able to successfully login to the website
Summary

Prerequisites 1. User had received the code on registration

Test Procedure 1. User needs to enter the code received on registration

2. Enter the username
3. Enter password

Test Data 1. Code: FAP001

2. Username: oberaipallavi
3. Password: abc123@95

Expected Result 1. As per the code the user is the participant so on login user should be
able to navigate to the events page on clicking on login Button

51
Actual Result 1. The Web page displays “Incorrect Username/Password” Message

Status Fail

Created By Pallavi Oberai

Date of Creation 29/09/2019

Executed By Pallavi Oberai

Date of 29/09/2019
Execution

Test Case 2:

Test Suite ID TS002

Test Case ID TC002

Test Case To verify that sponsor receives the receipt on making the payment
Summary

Prerequisites 1. The sponsor must have agreed upon the sponsorship conditions
2. The Sponsor has made the payment to the marketing member

Test Procedure The Marketing member make below entries to the Fest Assist Website

1. Company Name
2. Sponsor Name
3. Sponsor Email ID
4. Sponsor Contact No
5. Type of Sponsor
6. Total Amount

Test Data 1. Company Name: Atlasa

2. Sponsor Name: Sonia
3. Sponsor Email ID: sonia@atlasa.com
4. Sponsor Contact No:987567458
5. Type of Sponsor: Title Sponsor
6. Total Amount: 100000

52
Expected Result 1. The Sponsor receives the email from Fest Assist website with the
receipt in PDF format

Actual Result 1. The Sponsor received the email from Fest Assist website with the
receipt in PDF format

Status PASS

Created By Pallavi Oberai

Date of Creation 29/09/2019

Executed By Pallavi Oberai

Date of Execution 29/09/2019

53