You are on page 1of 5





REG.NO: 15MIS0390
FACULTY: Prof. Krithika L.B

Chosen Title: Event Management System

What is a Event Management System?

Event management software is a solution that helps companies to automate

the process of planning, marketing, organizing, and analyzing promotional events. This
type of software can be used for event registration, ticketing, seat allocations, and onsite
operations management. It can also be utilized to conduct real-time surveys and polls to
engage the audience and to use customer feedback to enhance future events.
Event management software can be used to organize and manage
conventions, trade exhibitions, academic and professional conferences, and Continuing
Professional Development (CPD) meetings. Top features include session management,
barcode scanning, badge printing, guest list management, and venue management.
Construction life cycle models:

System Development Life Cycle:

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 {system 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.
Most professional software developers plan a software project using a series of
steps generally referred to as the software development life cycle. A number of models
exist that differ in the number of stages defined, and in the specific activities that take
place within each stage. The following example is a generic model that should give you
some idea of the steps involved in a typical software project.

Key Features:
● Session management
● Onsite management
● Event marketing
● Reporting and event analytics
● Ticketing
● Venue management
● Registration management
● Attendee management

The Construction fundamentals that will be focused in our project are,

1) Minimizing Complexity:
The minimum the complexity of the project the more the understanding and
ease of use will be. Less complexity and more user friendly. The code created here
should be simpler and readable. We need to avoid redundancy and reduce the Lines of
code to as minimum as possible.

● We have gone through the code to prevent any kind of infinite loops and security
holes such as buffer overflow or array index overflow.
● The code is built in java, so it is organized into classes, subroutines and packages.
● We have a detailed code documentation with all the initial errors we committed
and the bugs that we have seen through.
● The code style is android style cause we are developing an android application.
● We are reusing the basic parts of a typical android application such as the Login
page, the Account details page.
● All the data is stored in database and is easy to retrieve the data.
2) Anticipating Change:
The application is frequent to updates and the API Level for apk installation will be
around 22 because most of the mobile phones these days have atleast KitKat version.

● The new features such as the BIg Data applications to predict our events in future
can also be added.
● Also our application can be added as a widget on the homescreen to reduce the
time to access the app for small event details.
● It syncs with the user’s email and gives alerts about the upcoming events.

Constructing for Verification:

Constructing for verification means building software in such a way that faults can be
ferreted out readily by the software engineers writing the software, as well as during
independent testing and operational activities.

Specific techniques that support constructing for verification include following coding
standards to support code reviews, unit testing, organizing code to support automated
testing, and restricted use of complex or hard-to-understand language structures, among

Standards in Construction:

● Standards that directly affect construction issues include Use of external standards.
● Construction depends on the use of external standards for construction languages,
construction tools, technical interfaces, and interactions between Software
Construction and other software engineering.
● Standards come from numerous sources, including hardware and software
interface specifications such as the Object Management Group (OMG) and
international organizations such as the IEEE or ISO.
● Use of internal standards. Standards may also be created on an organizational
basis at the corporate level or for use on specific projects.
● These standards support coordination of group activities, minimizing complexity,
anticipating change, and constructing for verification.