Acknowledgement

The success of this project is an outcome of sincere efforts challenged in the

right direction, efficient supervision and most valuable technical assistance.

The project wouldn’t have been completed without the help and guidance of
management.
We express our deep gratitude to --------------- project incharge. With great
pleasure, we would like to opportunity to thank my practical in charge for her
valuable guidance, support he gave to me for the completion of the project on
“Event Management” Aurangabad.

He provided with me the necessary resources, encouragement for better

understanding and learning. We will always carry the memories of my
training period.
Last, but not least we will fail in my duty if we don’t express regards and
grateful to my parents and friends.

BSC (Computer Science)

 Index
Sr.No Topic Page No.
1. Introduction 1
 Introduction to Project
 Purpose of System
 Problems in existing System
2. System Analysis
2.1 Introduction
2.2 Analysis Model
2.3 Study of System
2.4 System requirement Specification
2.5 Proposed System
2.6 Input & output
3. Feasibility Report
3.1 Technical feasibility
3.2 Operational Feasibility
3.3 Economical Feasibility
4. Introduction to selected software
5. System Design
5.1 Introduction
5.2 Normalization
5.3 Data flow Diagram(DFD)
5.4 E R-Diagram
5.5 Data Dictionary
6. Coding
7. Output Screens
8. Testing Model
9. Conclusion
10. Bibliography
1.Introduction
 Introduction To Project
 Event Management when compared to other traditional professions
such as medicine, law and accounting is relatively a young field. It is an
area that is growing rapidly and now represents hundreds of
professionals who are responsible for planning, coordinating and
evaluating a wide range of events all year round.
 Event management is predominantly about creating an experience.
Bearing in mind that first impressions last, it is important when
embarking on any event regardless of its scale to take the correct
approach and use the right techniques to ensure that your event is
successful

1.2 Purpose :
 To reserve a room and request room set-ups, equipment management, technology
and catering needs for all events including large-scale or high profile events
 To avoid double-booking and room schedule conflicts
 Assess and report usage and planning for the following year
 To effectively communicate campus event activity to all stakeholders and
constituents

1.3 Problems in existing system

In the present scenario, existing system has many drawbacks which make it
inefficient to carry on with it. The present working system of the referred company is
manual. It is difficult to maintain all details of events, customers and the services. The
execution of the event sometimes delays due to unmanaged planning. As far as quality
is concerned it is ok but not as good when handled using computerized system. Now
the inefficiency of the existing system can be stated in terms as follows:

 The manually handled system is time consuming

 Data security is not assured.
 It is difficult to maintain records in long run.
 Large number of manpower is required.
 It is hectic to handle huge transaction.
2.System Analysis
2.1 Introduction:
The Sustainability Program at Florida Tech has over thirty requests for participation at
events annually. This project brings a systems perspective to organizing and
implementing for these dense event management tasks, with a focus on the busy spring
semester at Florida Tech.
Planning the timing and obtaining the resources in people-hours and expenses is
challenging, particularly due to the high density of sustainability events in the spring,
which terminates with Earth Day, which is celebrated across Earth Week at Florida
Tech The Association for the Advancement of Sustainability in Higher Education
sponsors the premier campus sustainability certification program, the Sustainability
Tracking, Assessment & Rating System (STARS). Florida Tech could receive credits
towards this certification from improved event planning.
Florida Tech currently does not have a Sustainable Events Plan, although such a plan
would improve coordination of events.
The project goal is to build a systems-based approach to improve coordination and
execution of sustainability events. This goal will be achieved by these objectives:
• To inventory and tabulate the metrics for sustainability related events both on and off
campus to improve system efficiency.
• To apply findings from Objective 1 to improve best practices for Earth Week at Florida
Tech.
• To apply Florida Tech student event activities to achieve credits for up to 10 STARS
green campus certification points.
2.2 Analysis Model:

The analysis model must achieve three primary objectives:

1. To describe what the customer requires.
2. To establish a basis for the creation of a software design,and
3. To define a set of requirements that can be validated once the software is built.

To accomplish this objectives,the analysis model derived during structured

analysis takes the form.At the core of the model lies the datat dictionary a
repository that contains descriptions of all data objects consumed or produced by
the software.

2.3 Requirement Analysis

This paper proposed a kind of software requirements analysis technology method
based on event-driven. In structured analysis method, system relation diagram, DFD
fragments and 0-level figure are developed through the establishment of events table.
Further DFD diagram decomposition is carried on to obtain the analytical model. We
can divide the subsystem through events and external entities interaction, data storage
interaction and common point analysis in processing requirements. Regarding the
object-oriented method, use case diagram and sequence diagram are developed based
on the events. Presented two analysis methods in the analysis technology and realized
the analysis in detail. Through the case analysis, briefly introduces how to use the
method to carry on structured analysis and complete software requirement modeling.
The result shows that the method is easy and feasible.

Software Devlopment Life Cycle

System development Life cycle consist of two major steps of System analysis and design. It
includes set of activities that analysts, designers and users carry out to develop and implement an
information system.

The structured sequence of operation required imaging developing and making operational a new
information system it’s a cycle because the System will need replacement and Development,
cycle will begin. System development life cycle is a process of developing software on the basis
of the requirement of the end user to develop efficient and good quality software. It is necessary
to follow a particular procedure. The sequence of phases that must be followed to develop good
quality software is known as SDLC (software development life cycle).The software is said to
have a life cycle composed of several phases. Each of these phases results in the development of
either a part of the system or something associated with the system, such as a test plan or a user
manual. In the life cycle model, called the “Spiral Model”, each phase has well-defined starting
and ending points, with clearly identifiable deliverables to the next phase. In practice, it is rarely
so simple. As with most undertakings, planning is an important factor in determining the success
or failure of any software project. Essentially, good project planning will eliminate many of the
mistakes that would otherwise be made, and reduce the overall time required to complete the
project. As a rule of thumb, the more complex the problem is, and the more thorough the
planning process must be.

What is the Spiral Model?

The Spiral Life Cycle Model is a type of iterative software development model which is
generally implemented in high risk projects. It was first proposed by Boehm. In this system
development method, we combine the features of both, waterfall model and prototype model. In
Spiral model we can arrange all the activities in the form of a spiral. Each loop in a spiral
represents a development phase and we can have any number of loops according to the Each
loop has four sections or quadrants:
1. To determine the objectives, alternatives and constraints. We try to understand the product
objectives, alternatives in design and constraints imposed because of cost, technology, schedule,
etc.
2. Risk analysis and evaluation of alternatives. Here we try to find which other approaches can
be implemented in order to fulfill the identified constraints. Operational and technical issues are
addressed here. Risk mitigation is in focus in this phase. And evaluation of all these factors
determines future action.
3. Execution of that phase of development. In this phase we develop the planned product. Testing
is also done. In order to do development, waterfall or incremental approach can be implemented.
4. Planning the next phase. Here we review the progress and judge it considering all parameters.
Issues which need to be resolved are identified in this phase and necessary steps are taken.
Subsequent loops of spiral model involve similar phases. Analysis and engineering efforts are
applied in this model. Large, expensive or complicated projects use this type of life cycle.

If at any point of time one feels the risk involved in the project is a lot more than anticipated,
one can abort it. Reviews at different phases can be done by an in-house person or by an external
client.
Advantages of Spiral Model :
• Spiral Life Cycle Model is one of the most flexible SDLC models in place.
Development phases can be determined by the project manager, according to the
complexity of the project.
2) Project monitoring is very easy and effective. Each phase, as well as each loop,
requires a review from concerned people. This makes the model more transparent.
3) Risk management is one of the in-built features of the model, which makes it extra
attractive compared to other models.
 4) Changes can be introduced later in the life cycle as well. And coping with these
changes isn’t a very big headache for the project manager.
5) Project estimates in terms of schedule, cost etcbecome more and more realistic as
the project moves forward and loops in spiral get completed.
6) It is suitable for high risk projects, where business needs may be unstable.

Disadvantages of Spiral Model :

1) Cost involved in this model is usually high.
2) It is a complicated approach especially for projects with a clear SRS.
3) Skills required, evaluating and reviewing project from time to time, need expertise.
4) Rules and protocols should be followed properly to effectively implement this model. Doing
so, through-out the span of project is tough.
5) Due to various customizations allowed from the client, using the same prototype in other
projects, in future, is difficult.
6) It is not suitable for low risk projects.
7) Meeting budgetary and scheduling requirements is tough if this development process is
followed.
8) Amount of documentation required in intermediate stages makes management of project very
complex affair.

2.4 Software Requirement Specification

Determination of system requirement means studying the adjacent system in order to collect
the details regarding the way it captures data, processes the data, produces the output. I used
following techniques for identifying system requirements:

• Reviewing organization documents

• Onsite observations
• Conducting interviews
SYSTEM ANALYSIS
After analyzing of the task to be performed, the next step is to analyze the problem and
understand its context. The first activity in the phase is studying the existing system and other is
to understand the requirements and domain of the new system. Both the activities are equally
important, but the first activity serves as a basis of giving the functional specifications and then
successful design of the proposed system. Understanding the properties and requirements of a
new system is more difficult and requires creative thinking and understanding of existing
running system is also difficult improper, understanding of present system can lead diversion
from solution.

Reviewing Organization Documents:

We first learnt about the organization involved in, or affected by the project, We got to
know how the department works and the employees were directly involved/associated with the
application. Annual manuals and reports were of great help to us.

Here, We observed the activities of the system directly. We saw the office environment,
workload on the system, and workload on the users. The physical layout of the current system
along with the location & movement of staff was analyzed. In this way, the information about the
present workflow, objects and people was gathered. This helped us to understand various
procedures & processes, which were to be developed in the new system.

SRS- Hardware and Software requirements :

Hardware Software
Intel or AMD-based CPU For development – VS 2012
Compatible motherboard Framework - .NET 4.0
1 GB RAM OS - Windows XP onwards
50 MB free hard disk space Media player control library and
namespace
Minimum 512 MB Graphic card
(GPU)
3. Feasibility Report
 3.1 Technical Feasibility

The system must be evaluated from the technical point of view first. The assessment of this
feasibility must be based on an outline design of the system requirement in the terms of input,
output, programs and procedures. Having identified an outline system, the investigation must go
on to suggest the type of equipment, required method developing the system, of running the
system once it has been designed. Technical issues raised during the investigation are? Does the
existing technology sufficient for the suggested one? Can the system expand if developed? The
project should be developed such that the necessary functions and performance are achieved
within the constraints. The project is developed within latest technology. Through the technology
may become obsolete after some period of time, due to the fact that never version of same
software supports older versions, the system may still be used. So there are minimal constraints
involved with this project. The system has been developed using Java the project is technically
feasible for development.

3.2 Operational Feasibility

It is mainly related to human organizational and political aspects. The points to be

considered are:
• What changes will be brought with the system?
• What organizational structures are distributed?
• What new skills will be required? Do the existing staff members have these skills?
• If not, can they be trained in due course of time?
Generally project will not be rejected simply because of operational infeasibility
but such considerations are likely to critically affect the nature and scope of the eventual
recommendations. The project would be beneficial because it satisfies the objectives
when developed and installed. All Operational aspects are considered carefully and
conclude that the project is behaviorally feasible.

3.3 Economical Feasibility

The developing system must be justified by cost and benefit. Criteria to ensure that effort
is concentrated on project, which will give best, return at the earliest. One of the factors, which
affect the development of a new system, is the cost it would require. The following are some of
the important financial questions asked during preliminary investigation:
 • The costs conduct a full system investigation.

• The cost of the hardware and software.

• The benefits in the form of reduced costs or fewer costly errors.

The various advantage of using above software is as follows:-

• The software can be made exactly as per the needs of the management.
• No specific training is required to use the software. The use just has to enter the fields
according to requirements.
• Besides, a graphical user interface (GUI) will be much more demanding on memory.
• No overburdening of work for ‘clerk’ since most of the work will be performed by the
system by the system itself.
• And lastly, the cost of development is very less compared to other alternatives

Since the system is developed as part of project work, there is no manual cost to spend for the
proposed system. Also all the resources are already available, it give an indication of the system
is economically possible for development.

As part of the feasibility study, an estimate is made whether the identified user needs may be
satisfied using the current software and hardware. This study decides that whether or not the
proposed system will be cost effective from a business point of view. In this case, user has one
head clerk who does all the work. So the one clerk has maintain records regarding new A/c and
deletion of A/c addition and deletion of customer, balance amount etc.

4. Introduction Of Selected Software

MICROSOFT VISUAL STUDIO 2012

Microsoft Visual Studio is an integrated development environment (IDE) from Microsoft. It is
used to develop console and graphical user interface applications along with Windows Forms
applications, web sites, web applications, and web services in both native code together with
managed code for all platforms supported by Microsoft Windows, Windows Mobile, Windows
CE, .NET Framework, .NET Compact Framework and Microsoft Silver-light.

Visual Studio includes a code editor supporting IntelliSense as well as code refactoring. The
integrated debugger works both as a source-level debugger and a machine-level debugger. Other
built-in tools include a forms designer for building GUI applications, web designer, class
designer, and database schema designer. It accepts plug-ins that enhance the functionality at
almost every level—including adding support for source-control systems (like Subversion and
Visual SourceSafe) and adding new toolsets like editors and visual designers for domain-specific
languages or toolsets for other aspects of the software development lifecycle (like the Team
Foundation Server client: Team Explorer).

5. System Design

5.1 Introduction

Design is the first step into the development phase for any engineered product or system. Design
is a creative process. A good design is the key to effective system. The term “design” is defined
as “the process of applying various techniques and principles for the purpose of defining a
process or a system in sufficient detail to permit its physical realization”. It may be defined as a
process of applying various techniques and principles for the purpose of defining a device, a
process or a system in sufficient detail to permit its physical realization. Software design sits at
the technical kernel of the software engineering process and is applied regardless of the
development paradigm that is used. The system design develops the architectural detail required
to build a system or product. As in the case of any systematic approach, this software too has
undergone the best possible design phase fine tuning all efficiency, performance and accuracy
levels. The design phase is a transition from a user oriented document to a document to the
programmers or database personnel. System design goes through two phases of development:
Logical and Physical Design.

LOGICAL DESIGN:

The logical flow of a system and define the boundaries of a system. It includes the following
steps:

• Reviews the current physical system – its data flows, file content, volumes frequencies
etc.

• Prepares output specifications – that is, determines the format, content and frequency of
reports. Prepares input specifications – format, content and most of the input functions.

• Prepares edit, security and control specifications. Specifies the implementation plan.
Prepares a logical design walk through of the information flow, output, input, controls
and implementation plan.

• Reviews benefits, costs, target dates and system constraints.

PHYSICAL DESIGN:

Physical system produces the working systems by define the design specifications that
tell the programmers exactly what the candidate system must do. It includes the following steps.

• Design the physical system.

• Specify input and output media.

• Design the database and specify backup procedures.

• Design physical information flow through the system and a physical design Walk
through.

• Plan system implementation.

• Prepare a conversion schedule and target date.

• Devise a test and implementation plan and specify any new hardware/software.
 • Update benefits, costs, conversion date and system constraints Design/Specification
activities: Concept formulation.

• Problem understanding. High level requirements proposals.

• Feasibility study.

• Requirements engineering. Architectural design.

Interface Design:

A well-designed interface improves the user perception of the content or services. It needs not to
be flashy but it should be ergonomically sound. Two main types of design interface, which I
considered, are:

• User Interface
• Communication Interface

Detailed Design Specification:

Complete design specification serves the following purposes:

• It should be able to adequately serve as training material for new project members,
imparting them enough information and understanding about the project implementation.
• It should serve as “Objective Evidence” that the designers and/or implementers are
following through on their commitment to implement the functionality described in their
requirements specifications.

5.2 Normalization
 As the name implies, it denoted putting things in the normal form. The application
developer via normalization tries to achieve a sensible organization of data into proper tables and
columns to the data by the and where names can be easily correlated user. Normalization
eliminates repeating groups at data and thereby avoids data redundancy which proves to be a
great burden on the computer resources. These include:

• Normalize the data.

• Choose proper names for the tables and columns.

• Choose the proper name for the data.

5.3 E-R Diagram