24311691 event management system
TRANSCRIPT
CONTENTS
ACKNOWLEDGEMENT
SYNOPSIS
CONTENTS
1. INTRODUCTION 1.1 About the Organization 1.2 About the Project
2. PROGRAM ENVIRONMENT 2.1 Hardware Specification 2.2 Software Specification 2.3 About the Operating System 2.4 Languages/Tools 2.5 Front End and Back End
3. SYSTEM STUDY AND ANALYSIS 3.1 Existing System 3.2 Drawbacks of Existing System 3.3 Proposed System 3.4 Features of Proposed System
4. SYSTEM DESIGN AND IMPLEMENTATION 4.1 Input Design 4.2 Output Design 4.3 Database Design 4.4 Process Design
5. SYSTEM TESTING AND IMPLEMEMNTATION 5.1 Testing Objectives 5.2 System Testing 5.3 System Implementation
6. CONCLUSION
7. SCOPE FOR FUTURE ENHANCEMENT
8. BIBILIOGRAPHY
9. APPENDICES 9.1 Data Flow Diagram 9.2 E-R Diagram 9.3 Screen Layouts 9.4 Reports
SYNOPSIS
EVENT MANAGEMENT SYSTEM
The aim of the project titled EVENT MANAGEMENT is to develop
enterprise software that optimizes the performance of an event management company.
This system helps the managers at different departments to coordinate their work and
thereby save their valuable time and finance.
Event management offers multilevel facilities to the firm to increase
their revenue. The system helps the firm to receive the orders from different clients
irrespective of their location. It increases the speed of processing the orders and prepares
the quotations by allocating the duties to the managers of different departments.
This system helps to decompose the different tasks involved in a
particular order and sequences these processes. It provides a flexible web outlet to engage
more clients in the process of event management process.
The various modules are:
• Marketing
• Production
• Promotion
• Finance
• Admin
• HR
1.INTRODUCTION
1.1 About the Project
The System “Event Management System” is an automated system
for event management. It is capable of managing multiple events happening in different
locations. The System enables even the remote client to make online registrations. It is
powerful, user-friendly, and flexible and it offers great degree of customization with ease
of management. It manages the whole logistics of the company with maximum
optimization. It provides analytical status of event processing and follows efficient
approach towards the execution of the show. The system projects the status of the events
based on the authorization provided for the different entities. With its powerful
functionality it can maintain the records of various events simultaneously, and can print
various reports.
2.PROGRAM ENVIORNMENT
2.1 Hardware Specification
Processor : Pentium IV RAM : 512MB DDR Cache : 512 HDD : 80GB FD : 1.44 Printer : Ink jet printer
2.2 Software Specification
Operating System : Windows 2003 server System architecture : .net frame work DataBase : MySQL Connectivity : ADO.net GUI Builder : FrontPage 2002 Server : IIS Server 2003 Presentation Layer : ASP.net Business logic : VC#.net Validation Language : Java Script
2.3 About the Operating System
Event Management System was normally being developed
under windows platform called of as Windows 2000 Professional.
WINDOWS 2000 PROFESSIONAL
Windows is an operating system and has evolved from a
basic graphical user interface like windows 3.1. Windows 2000 is a part of
Microsoft Windows family that includes windows 98.Windows 2000
provides access to all the parts of computing environment documents,
files, application, email and internet. Microsoft Windows 2000
professional is more compatible and more powerful than any workstation
used before.
Windows 2000 is heavily focused on Windows rectangular areas on the
screen that presents information, that is, we open Windows when we need
them and close them when we don’t need them. Individual Windows can
be resized and moved around the screen.
Window 2000 uses small graphical icon pictures on desktop
to represents objects such as documents, applications, folders, devices,
WebPages and other computers. Icons often have text labels to help make
there purpose a bit clearer. That is, if we move the mouse overran object
on the desktop or in a windows and click the right mouse button windows
2000 displays a menu with the objects common commands. All the
windows applications are the same convention called a contend menu or
right click menu.
We can access selected object in several ways for most
types of objects,we click them: move cursors on to the objects and then
press the left mouse button once. A selected object is highlighted; its label
is darkened and has a line indicating that the selected object is ready to be
choosen.We choose an object to activate its associated commands .we
choose the objects by double clicking its icon: Move the mouse cursor on
to the icon and then press the left mouse button rapidly twice. If the object
is a menu selection or command button, we choose it with the single click.
We can also move or copy objects using drag and drop. To
drag and drop On object, move the cursor on to the icon on the object to
be dragged. Press and hold the left mouse button while we move the
mouse cursor to the determination objects icon then release the mouse
button.
FEATURES
1.Easier To Use
With the windows 2000 professional we have faster access to
information and we are able to accomplish test more quickly and easily.
Windows 2000 professional make it easier to
Find Information
Work on the Web
Work remotely
Work with the files
Personalize your computer environment
2.Easier To Manage
We can work more efficiently, because many of the most common
computer management tests are automated and streamlined to the
windows 2000Professional
With the windows 2000 work station, it will be easier to
Set up
Administered
Support
2.4 Languages/Tools
The following languages/tools are required for developing the project:
Windows 2000 Professional OS has to be installed
C#.NET,ASP.NET (Front End)
SQL SERVER2000 (Back End)
2.5 Front End and Back End
.NET The .NET Framework is just part of Microsoft’s overall
.NET platform strategy. The framework is made up of the
Common Language Runtime environment, Base Class Library,
and higher-level frameworks such as ASP.NET and Windows
Forms as shown in Figure
The complete documentation on the .NET Framework fills
entire books. What we do here is cover the basics so that
you have a firm enough understanding of the .NET
Framework to enable you to get started developing XML
Web Services.
We’ll start with how to obtain the .NET Framework
SDK.The minimum system requirements can be confusing
so we’ll cover those in some detail. The common language
runtime (CLR) is the foundation that sits on top of the
Windows operating system. Since this is the most
important part of the .NET Framework we’ll spend most of
our time going through the CLR.The base class library is a
set of hundreds of classes that are provided as part of the
framework to help us build applications that will execute in
the CLR.We’ll get an overview of these so that we can get
an idea of the breadth of support provided by the SDK “out
of the box”. To make building applications even easier
Microsoft provides some higher level frameworks like
ASP.NET and Windows Forms that utilize and extend the
functionality provided by the Base Class Library.ASP.NET
greatly simplifies the building of Internet applications by
using Web Forms and Web Services. Windows forms
provides the ability to develop for the rich environment
that the Windows platform provides. We’ll take a look at
these frameworks to give you an overview of the purpose
of each.
ADO.NET
ADO.NET is the latest in a long line of data access
technologies
released by Microsoft. ADO.NET differs somewhat from the previous
technologies, however, in that it comes as part of a whole new platform
called the .NET Framework. This platform is set to revolutionize every
area of development, and ADO.NET is just one aspect of that. The
ADO.NET classes are divided into two components: the Data Providers
(sometimes called Managed Providers), which handle communication with
a physical data store, and the Dataset, which represents the actual data.
Either component can communicate with data consumers such as Web
Forms and Win Forms.
.
Data Providers
The Data Provider components are specific to a data source. The .NET
Framework includes two Data Providers: a generic provider that can
communicate with any OLE DB datasource, and a SQL Server provider
that has been optimized for Microsoft SQL Server versions 7.0 and later.
Data Providers for other databases such as Oracle and DB2 are expected to
become available, or you can write your own. The two Data Providers
included in the .NET Framework contain the same objects, although their
names and some of their properties and methods are different. The
Connection object represents the physical connection to a data source. Its
properties determine the data provider (in the case of the OLE DB Data
Provider), the data source and database to which it will connect, and the
string to be used during connecting. Its methods are fairly simple:
You can open and close the connection, change the database, and manage
transactions. The Command object represents a SQL statement or stored
procedure to be executed at the data source. Command objects can be
created and executed independently against a Connection object, and they
are used by Data Adapter objects to handle communications from a
Dataset back to a data source. Command objects can support SQL
statements and stored procedures that return single values, one or more
sets of rows, or no values at all.
A Data Reader is a fast, low-overhead object for obtaining a forward-only,
read-only stream of data from a data source. They cannot be created
directly in code; they are created only by calling the Execute Reader
method of a Command.
The Data Adapter is functionally the most complex object in a Data
Provider. It provides the bridge between a Connection and a Dataset. The
Data Adapter contains four Command objects: the Select Command,
Update Command, Insert Command, and Delete Command. The Data
Adapter uses the Select Command to fill a Data Set and uses the
remaining three commands to transmit changes back to the data source, as
required.
DataSets
The Dataset is a memory-resident representation of data. Its structure is
shown in the figure below. The Dataset can be considered a somewhat
simplified relational database, consisting of tables and their relations. It’s
important to understand, however, that the Dataset is always disconnected
from the data source—it doesn’t “know” where the data it contains came
from, and in fact, it can contain data from multiple sources.
C#.NET:
C# was built from scratch as the .NET language. While it has
features familiar to C programmers, and it has some of the great RAD
features so beloved by Visual Basic programmers, it is completely new.
Some have said that C# is Microsoft’s “me too” language to compete with
Sun’s Java.
Microsoft has introduced a new language especially for .NET,
called C#. As this is now Microsoft’s flagship language, and the most
likely language to be supported by Open Source projects.
C# has been described as J++ mark 2.There is more to it than that.
C# is effectively C++ built from scratch. The problems with C++ are well
documented, so there is no need to go into them here, but suffice it to say
that in C++, object orientation was an optional bolted-on afterthought,
whereas in C#, it was built in from the ground up.
All the functionality and support of the .NET Framework is
available to any of the .NET languages, and in addition, objects written
under one language can be used, inherited, and extended under any of the
others. This is a very powerful concept and introduces the idea of
language independence. This is achieved through the Common Language
Runtime technology.
The CLR takes your .NET language code and converts it into an
intermediate language (Microsoft Intermediate Language [MSIL]), and
this intermediate language is then compiled to target machine-specific
binary code.
C# is a truly modern language with all the features you could wish for, such as full object-orientation, automatic memory management, and housekeeping
ASP.NET
The .Net by Microsoft Company is to overcome the difficulties in the ASP.Microsoft
ensured the asp scripts execute without modification on the machine with the .Net Frame
work.
Advantages
• Separation of code from the content.Asp.Net allows the developer to separate
script code from html.This allows for a clean seperation of code from content and
formatting and promotes code reuse.
• support for compiled languages. while ASP.Net still supports the traditional set of
scripting languages, support is also provided for fully compiled language,Instead
of using vbscript the developer can use VB.NET and access features such as
strong typing and object oriented programming.Asp.Net pages are precompiled to
bytecode and just in time compiled when first requested.
• Greater support for different browsers via server side controls and events.
Following object oriented design principles, ASP.NET pages make use of server
side controls called ASP.NET Webcontrols.These controls are instantiated on the
server, and like regular objects they have associated methods,properties,and
events. The advantage of the server side controls is that they render themselves on
the client as standard HTML 3.2 (optionally DHTML).depending on the
capabilities of the client browser.
• Intuitive GUI design, with ASP.NET you can design web applications as you read
in Visual Basic 6 by dragging and dropping GUI elements in a sophisticated
design environment.
Introducing Dynamic Web Pages
The client-to-server-to-client process described is important because it happens
each time your client contacts the server to get some data. That’s distinctly different from
the stand-alone or client-server model you may be familiar with already. Because the
server and the client don’t really “know” anything about one another, for each
interaction, you must send, initialize, or restore the appropriate values to maintain the
continuity of your application.
As a simple example, suppose you have a secured site with a login form. In a
standard application, after the user has logged in successfully, that’s the only
authentication you need to perform. The fact that the user logged in successfully means
that they’re authenticated for the duration of the application. In contrast, when you log in
to a Web site secured by only a login and password, the server must re-authenticate you
for each subsequent request. That may be a simple task, but it must be performed for
every request in the application.
In fact, that’s one of the reasons dynamic applications become popular. In a site that
allows anonymous connections (like most public Web sites), you can only authenticate
users if you can compare the login/password values entered by the user with the “real”
copies stored on the server. While HTML is an adequate layout language for most
purposes, it isn’t a programming language. It takes code to authenticate users.
Another reason that dynamic pages became popular is because of the ever-changing
nature of information. Static pages are all very well for articles, scholarly papers, books,
and images-in general, for information that rarely changes. But static pages are simply
inadequate to capture employee and contact lists, calendar information, news feeds,
sports score-in general, the type of data you interact with every day. The data changes far
too often to maintain successfully in static pages. Besides, you don’t always want to look
at that data the same way.
How Does the Server Separate Code from Content?
In classic ASP pages, you could mix code and content by placing special code tags
(<% %>) around the code or by writing script blocks, where the code appeared
between<script> and </script> tags. Classic ASP pages use an .asp file name extension.
When the server receives a request for an ASP file, it recognizes—via the extension
associations—that responding to the request requires the ASP processor. Therefore, the
server passes the request to the ASP engine, which parses the file to differentiate the code
tag content from the markup content. The ASP engine processes the code, merges the
results with any HTML in the page, and sends the result to the client.
ASP.NET goes through a similar process, but the file extension for ASP.NET files
is .aspx rather than .asp. You can still mix code and content in exactly the same way,
although now you can (and usually should) place code in a separate file, called a code-
behind module, because doing so provides a cleaner separation between display code and
application code, and makes it easier to reuse both. In ASP.NET, you can write code in
all three places—in code-behind modules and also within code tags and script blocks in
your HTML files. Nevertheless, the ASP.NET engine must still parse the HTML file for
code tags.
How and When Does the Server Process Code?
The ASP.NET engine itself is an Internet Server Application Programming Interface
(ISAPI) application. ISAPI applications are DLLs that load into the server’s address
space, so they’re very fast. Different ISAPI applications handle different types of
requests. You can create ISAPI applications for special file extensions, like .aspx, or that
perform special operations on standard file types like HTML and XML.
There are two types of ISAPI applications: extensions and filters. The ASP.NET engine
is an ISAPI extension. An ISAPI extension replaces or arguments the standard IIS
response. Extensions load on demand when the server receives a request with a file
extension associated with the ISAPI extension DLL. In contrast, ISAPI filters load with
IIS and notify the server about the set of filter event notifications that they handle. IIS
raises an event notification (handled by the filter) whenever a filter event of that type
occurs.
ASP.NET pages that contain code tags bypass the standard IIS response procedure if
they contain code tags or are associated with a code-behind module. If your ASPX file
contains no code, the ASP.NET engine recognizes this when it finishes parsing the page.
For pages that contain no code, the ASP.NET engine short-circuits its own response, and
the standard server process resumes. Classic ASP pages began short-circuiting for pages
that contained no code with IIS 5 (ASP version 3.0). Therefore, ASP and ASPX pages
that contain no code are only slightly slower than standard HTML.
SQL Server Enterprise Manager
SQL Server Enterprise Manager is a graphical tool that allows for easy, enterprise-
wide configuration and management SQL Server and SQL Server objects. SQL Server
Enterprise Manager provides:
• A scheduling engine.
• Administrator alert capability.
• Drag-and-drop control operations across multiple servers.
• A built-in replication management interface.
You can also use SQL Server Enterprise Manager to:
• Manage logins, permissions, and users.
• Create scripts.
• Manage devices and databases.
• Back up databases and transaction logs.
• Manage tables, views, stored procedures, triggers, indexes, rules, defaults, and
user-defined data types.
Creating and Maintaining Databases
Designing your Microsoft SQL Server database structure involves creating and
maintaining a number of interrelated components.
Database component Description
DatabasesContain the objects used to represent, manage, and access data.
TablesStore rows of data and define the relationships between multiple tables.
Database DiagramsRepresent database objects graphically and enable you to interact with the database without using Transact-SQL.
IndexesOptimize the speed of accessing the data in the table.
ViewsProvide an alternate way of looking at the data in one or more tables.
Stored ProceduresCentralize business rules, tasks, and processes within the server using Transact-SQL programs.
Triggers
Centralize business rules, tasks, and processes within the server using special types of stored procedures that are only executed when data in a table is modified.
Accessing and Changing Data
SQL Server Enterprise Manager includes a tool for designing queries interactively using
a graphical user interface (GUI). These queries are used:
• In views.
• In Data Transformation Services (DTS) Packages.
• To display the data in Microsoft SQL Server tables.
Replication
Replication is an important and powerful technology for distributing data and stored
procedures across an enterprise. The replication technology SQL Server allows you to
make copies of your data, move those copies to different locations, and synchronize the
data automatically so that all copies have the same data values. Replication can be
implemented between databases on the same server or different servers connected by
LANs, WANs, or the Internet. The procedures in this section help you configure and
maintain replication using SQL Server Enterprise Manager.
Data Transformation Services
Data Transformation Services (DTS) provides the functionality to import, export, and
transform data using COM, OLE DB, and Microsoft ActiveX Scripts. DTS enables you
to build and manage data marts and data warehouses by providing:
• An extensible transaction-oriented workflow engine that allows execution of a
complex series of operations.
• Powerful integrated heterogeneous data movement, scrubbing, and movement.
DTS can copy, validate, and transform data from many popular desktop and
server-based data sources including Microsoft Access, dBase, Microsoft Excel,
Microsoft Visual FoxPro®, Paradox, SQL Server, Oracle, and DB2.
• An industry standard method of sharing metadata and data lineage information
through Microsoft Repository. This information model has been adopted by
leading data warehousing and database design vendors.
• Package storage in Microsoft Repository, SQL Server, or COM-structured storage
files. After a package has been saved, it can be scheduled for execution using
SQL Server Agent.
• Extensibility that allows advanced users to meet their unique needs while
continuing to leverage DTS functionality.
• Integration with Microsoft SQL Server OLAP Services.
Managing Security
To ensure that data and objects stored in Microsoft SQL Server are accessed only by
authorized users, security must be set up correctly. Understanding how to set up security
correctly can help simplify ongoing management. Security elements that may have to be
set up include authentication modes, logins, users, roles, granting, revoking, and denying
permissions on Transact-SQL statements and objects, and data encryption.
Databases
A database in Microsoft® SQL Server consists of a collection of tables with data, and
other objects, such as views, indexes, stored procedures, and triggers, that are defined to
support the activities performed with the data. Before objects within the database can be
created, you must create the database and understand how to change the settings and the
configuration of the database. This includes tasks such as expanding or shrinking the
database, or specifying the files used to create the database
Tables
Tables are database objects that contain all the data in a database. A table definition is a
collection of columns in the same way a database is a collection of tables. Before data
can be stored in a database, you must understand how to create, modify, and maintain the
tables within your database. This includes tasks such as defining keys and adding or
deleting columns from a table.
Database Diagrams
Database diagrams enable you to create, manage, and view database objects in a
graphical format. Before objects within the database can be manipulated using database
diagrams, you must understand how to: create a database diagram, add objects to it, work
within a database diagram, and save a database diagram
Indexes
To create efficient indexes that improve the performance of your database application by
increasing the speed of your queries, you need an understanding of how to create and
maintain the indexes on the tables in your database.
Views
By creating, modifying, and maintaining views, you can customize each user’s perception
of the database.
Stored Procedures
By creating, modifying, and using stored procedures, you can simplify your business
applications and improve application and database performance.
Triggers
By understanding how to create, modify, and maintain triggers, you can use triggers to:
• Cascade changes through related tables in the database.
• Disallow or roll back changes that violate referential integrity, thereby canceling
the attempted data modification transaction.
• Enforce restrictions that are more complex than those defined with CHECK
constraints.
• Find the difference between the state of a table before and after a data
modification and take action(s) based on that difference
3. SYSTEM STUDY AND ANALYSIS
3.1 Existing System
The Existing system for Event management is a manual process. With
respect to the existing system, the marketing executive has to interact with the client in
person, brief on the services they provide and so on. All this requires more time and labor
work. This also gives root to lack of coordination, follow-ups and manual errors.
Moreover, the data collected may be inconsistent, redundant and servicing a remote client
will become impossible.
Events to be organized at multiple locations become a tedious task. The burden over
both the client and the employee increases and gives form to confusions and
erroneous data.
This section deals with the concept of system analysis, which is the
primary phase of the software development. The purpose is to identify the new system
and establish what the new system is to accomplish. Moreover a brief review of
requirement determination, software environment, a report on feasibility analysis, DFD is
also presented. The proposed system was subjected to thorough analysis and the findings
are recorded here. System analysis is an important activity that takes place when new
system is being build. It is the central whole of system development and it includes
gathering necessary data and developing a plan to the new system. It is not an easy task
because many people need to be satisfied and many conflicts resolved. System analysis
should be creative and imaginative in producing new solutions to meet the user
requirements.
3.2 Drawbacks of Existing System
The existing system is:
Involves more manual work
Time consuming
Expensive
Gives redundant and inconsistent data
Inefficient communication and process
3.3 Proposed System
The main objective of the system is to provide up-to-date status and
accurate data regarding each event to all the departments which may be situated apart.
Improved customer satisfaction at low cost
Easy updating of information
Better coordination of various departmental activities
Provides online registration facility
Status of processing can be verified and identified at any stage of process
Efficient allocation of resources
Ensures timeline management
Event Management System provides a full fledged Enterprise package for
an event management company. This also provides a user friendly web outlet for the
system to communicate with the remote end-users. The main issues that faced by the firm
is in managing the logistics that are distributed country wide. The proposed system
bridges this gap between the end-users and the company by providing a centralized
control over the entire system. The different departments utilize the system for
sequencing the different processes that are isolated apart.
The department utilizes the system to derive maximum profit by
optimizing resources. There are FIVE modules in the system.
Marketing
Marketing people in the existing system finds difficulty in canvassing
different clients, and to provide quick and complete information about the events. The
proposed system provides many alternatives to solve the problem by providing different
modes of registration for the clients in their finger tips.
The system provides a three level security mechanism for the department
with respect to their designations of the users. The clients can also engage themselves to
register their requirements. The filtering of the requirements with respect to schedules is
done in the marketing departments. The system provides a calendar tool for the purpose.
The processes take places under the department were distributed according to the
hierarchy of officials. The requirements were verified and recorded in corresponding
databases. It provides facilities to convey and send the order information to different
departments.
Production
The production department of the firm holds the complete execution of the
entire event. Event Management System helps this department by providing an
interactive environment for selecting services and vendors. The production department
also utilizes the process of verification by recording the result of each selected services. It
helps to select the vendors of each item by selecting the needed items for each service.
Thus it provided a profit directed process structure for the whole system.
Promotion
The promotion department has the whole authority to provide various
facilities to promote the event in the public. The proposed system enables to find out the
more suitable promotional activities for the event. It helps to engage the sponsors to the
event .The Event Management System provides a much easier environment to inform the
clients and the vendors of the company. The final costsheet of the event will be provided
to the finance departments.
Finance
The finance department utilizes the whole system many ways. It finds out
a tool to merge different cost sheets to prepare a proposal for the whole event. It also uses
the system to determine the performance of the employees to calculate the salaries
provided and incentives given. The finance gets the main aid while settling the bills and
getting the payment from the client. It also records every payment information from the
company point of view. Finance has also the work to receive the approved quotations and
process it and forward the selected details to various departments. Event Management
System manages to generate various internal and external reports for the future use.
These reports include annual, monthly, fortnight, bills and receipts.
Admin
The admin has the role to control entire activities of the system. The Event
Management System helps admin by providing an interactive environment to track the
whole activities of the employees and monitor whole processes that take place inside the
system. Another aspect of the work done by admin is to provide proper security settings
to the whole system. This is done through Event Management System by providing
different levels securities to the system. These security levels can be changed but only by
the Admin.
H R
HR of the existing system deals with the human resource of the company.
The optimized allocation of jobs is a very tidy process in the manual way. Event
Management System helps the HR manager to record the allotted jobs and corresponding
dates and then helps to allocate the new jobs to employees and workers. So the workload
of the HR managers will be reduced.
.
3.4 Features of Proposed System
The proposed system “Event Management System”, is a fully automated
system for event Management. The system automates all the activities of an event
management company, from the client registration to the bill settlement. In the proposed
system the client online can view the company details and services provided by them.
Online registration is also possible with this the proposed system. As the proposed system
is a centralized one, redundancy can be avoided; moreover the coordination of different
departments becomes much easier. This system constitutes a scheduler, which helps it to
manage events happening in multiple locations. Above all the system provides high
security for all its data. Advantages of the proposed system can be listed as:
Online registration
Better security
Managing multiple events efficiently
Redundancy can be reduced
Event processing status can be checked anytime
Erroneous data can be avoided
Latest Technological implementation
4. SYSTEM DESIGN AND IMPLEMENTATION
Design begins when management approves the feasibility study produced
during detailed analysis and authorizes the necessary funds and personnel to continue. It
concludes when management approves the design and authorizes development of the
actual system
4.1 Input Design
The input design is the process of converting the user-oriented inputs in
to the computer-based format. The goal of designing input data is to make the automation
as easy and free from errors as possible. For providing a good input design for the
application easy data input and selection features are adopted.
The input design requirements such as user friendliness, consistent format
and Interactive Dialogue for giving the right message and help for the user at right time
are also considered for the development of the project.
The main forms used here are:
Login Form
This is the form through which different users can enter into the system.
Different levels of validation at server and client side have been given.
Client Requirement form
This form allows the remote clients to register in the system.
Requirement Form
This form allows the marketing executives to register the clients from
remote locations.
Vendor selection form
This form helps promotion and production managers to select the exact
vendors for different items.
4.2 Output Design
A quality output is one, which meets the requirements of the end user and
presents the information clearly. In any system results of processing are communicated to
the users and to other systems through outputs. In the output design it is determined how
the information is to be displayed for immediate need and also the hard copy output. It is
the most important and direct source information to the user. Efficient and intelligent
output design improves the system’s relationship the user and helps in decision-making.
Outputs from computers are required primarily to communicate the results
of processing to the users. They are also used to provide a permanent copy of these
results for later consultation.
The output types are:
External outputs
Internal outputs
Operational outputs
Interactive Outputs
Turnaround time
The outputs may be defined in terms of type of output, content, format,
location, frequency, response, volume, sequence and action required.
4.3 Database Design
Client registration
Field name Data type lenght constraints description KeyClient_id varchar 5 notnull Client
identificationPk
Clint_pwd varchar 10 notnull Client password
Client name varchar 20 notnull Name of client
Date of birth date 8 notnull Date of birth
City varchar 20 notnull City of client
Nationality varchar 20 notnull Nationality of client
Gender varchar 10 Notnull Gender of client
Phone no number 15 Notnull Phone of the client
Mobile no number 20 notnull Mobile of the client
Address varchar 20 notnul Address of client
E_mail varchar 25 notnull E_mail address of client
Client order
Field name Datatype Length constraints description Keys
Client_id Varchar 5 Notnull Client identification
Foreign
Order_idVarchar 5 Notnull Order
identificationPrimary
Typ_evnt Varchar 15 Notnull Type of event
Date_evnt Date 8 Notnull Date of event
Attendence Number 10 Notnull Attendence
LocationVarchar 20 Notnull Location
BudgetNumber 10 Notnull Budget
timeDate/time 8 notnull time
Schedule table
Field name datatype length constraints description keys
Order_id Varchar 5 Notnull Order identification foreign
Evnt_name Varchar 20 Notnull Event name
Date_evnt Date 8 Notnull Date of event
Venue Varchar 15 Notnull Venue of event
Time Date/time 8 notnull Time of event
Calander table
Field name datatype length constraints description Keys
Order_id Varchar 5 Notnull Order identification foreign
Date Date 8 Notnull Date of event
Month Date 8 Notnull Month of event
Year Date 8 Notnull Year of event
Time Date/time 8 Notnull Time of event
Evnt_name Varchar 20 Notnull Name of event
Attendence number 10 notnull attendence
Service table
Field name
datatype length constraints description keys
Serv_id Varchar 5 Notnull Service identification primary
Type Varchar 20 Notnull Type of service
Date Date 8 Notnull Date of service
Time Date/time 8 Notnull Time of service
Desc varchar 50 notnull description
Service verification
Field name datatype length constraints description keys
Serv_id varchar 5 notnull Service identification
Foreign
Order_id varchar 5 notull Order identification Foreign
Evnt_name varchar 15 notnull Name of event
Description varchar 50 notnull description
Item selection
Promotional table
Field name datatype length constraints description keys
Vendor_id Varchar 5 Notnull Vendor identification
primary
Field name Data type
length constraints description Keys
Vendor_id Varchar 5 Notnull Vendor identification
Foreign
Item_id Varchar 5 Notnull Item identification foreign
Item_type Varchar 20 Notnull Item type
Cost number 10 notnull Cost of item
Name Varchar 20 Notnull Vendor nameAddress Varchar 50 Notnull Address Mobno Number 15 Notnull Mobile numberEmail varchar 15 notnull Email address
Sponser table
Field name datatype length constraints description keys
Order_id Varchar 5 Notnull Order identification foreignEvnt_name Varchar 20 Notnull Event nameTyp_event Varchar 20 Notnull Type of eventSpon_cost Number 10 Notnull Sponsership cost of
eventSpon_pay Number 10 Notnull Payment of money
for sponsoring Date_pay Date 8 Notnull Date of payment
Date_evnt date 8 notnull Date of event
Promotion information table
Field name Datatype length constraints description keys
Order_id Varchar 5 Notnull Order identification Foreign
Vendor_id Varchar 5 Notnull Vendor identification
foreign
Type_evnt Varchar 15 Notnull Type of event
Date_evnt Date 8 Notnull Date of event
Cost number 10 notnull Cost
Costsheet
Field name datatype length Constraints description keys
Order_id varchar 5 Notnull Order identification
Foreign
Type_evnt varchar 15 Notnull Type of event
Cost number 10 Notnull Cost of event
Event proposal
Field name datatype length Constraints description Keys
Order_id Varchar 5 Notnull Order identification
foreign
Qutn_id Varchar 5 Notnull Qutation identification
primary
Cost Number 10 Notnull Estimated cost
Desc Varchar 50 Notnull description
Bill table
Field name datatype length constraints description keys
Order_id Varchar 5 Notnull Order identification
Foreign
Bill_id Varchar 5 Notnull Bill identification primary
Bill_date Date 8 Notnull Bill date
Advance Number 10 Notnull Advance paid
Rem_amt Number 10 Notnull Remaining amount
Total Number 10 Notnull Total to be paid
Duedate Date 8 notnull Duedate of payment
Employee salaries
Field name description length constraints Description keys
Emp_id Varchar 5 notnull Employee identification
foreign
Desig Varchar 20 Notnull Designation
Basicpay Number 10 Notnull Basic pay
Incentives Number 10 Notnull Incentives
Total number 10 notnull Total salary
Client payment
Field name Datatype length constraints description keys
Client_id Varchar 5 Notnull Client identification
Order_id Varchar 5 Notnull Order identification
Bill_id Varchar 5 Notnull Bill identification
Advance Number 10 Notnull Advance paid
Rem_amt Number 10 Notnull Remaining amount
Amt_pay Number 10 Notnull Amount to be paid
Date_pay date 8 Notnull Date of payment
Qutation processing table
Field name datatype length constraints description keys
Order_id Varchar 5 Notnull Order identification Foreign
Qutn_id Varchar 5 Notnull Qutation identification
foreign
Date_qutn Date 8 Notnull Date of qutation
Est_Amount Number 10 Notnull Estimated amount
Desc Varchar 50 notnull Description
Employee activity
Field name Datatype length constraints description keys
Emp_id Varchar 5 notnull Employee identification
foreign
Worker_id Varchar 5 Notnull Worker identification
foreign
No_workers Number 5 Notnull No of workers
Status_job Varchar 20 Notnull Status of job
Desc varchar 50 notnull description
Process monitoring
Field name
datatype length constraints description keys
Emp_id Varchar 5 notnull Employee identification
Foreign
Worker_id Varchar 5 Notnull Worker identification
foreign
Job allocation
Field name datatype length constraints description keys
Order_id Varchar 5 Notnull Order identification Foreign
Emp_id Varchar 5 Notnull Employee identification
Foreign
Worker_id Varchar 5 Notnull Worker identification
foreign
No_days Number 5 Notnull No of days allotted for job
Status varchar 20 notnull Status of the job
Employee details
Field name datatype length constraints description keys
Emp_id Varchar 5 notnull Employee identification
primary
Emp_name Varchar 5 Notnull Employee name
Address Varchar 20 Notnull Employee address
Phno number 15 Notnull Phone number
Mobno number 15 Notnull Mobile number
Email varchar 20 notnull Email address
Worker details
Field name datatype length constraints description keys
Worker_id Varchar 5 Notnull Worker identification
primary
Name Varchar 20 Notnull Worker name
Address Varchar 50 Notnull Worker address
Phno Number 15 Notnull Worker phone no
Mobno Number 15 Notnull Mobile number
Email varchar 20 Notnull Email address
HR details table
Field name datatype length constraints description keys
Order_id varchar 5 notnull Order identification
Foreign
Evnt_name varchar 20 notnull Name of event
Date_evnt date 8 l notnull Date of event
Cost number 10 Notnull Cost of the event
Feedback table
Field name datatype length constraints description keys
Client-id varchar 5 notnull Client of identification
Fk
Order-id varchar 5 notnull Order of identification
Date of fb date 8 notnull Date of feedback
Event name varchar 20 notnull Name of event
Description varchar 50 notnull description
Reference table
Fieldname datatype length constraints description Keys
Ref-id varchar 5 notnull Reference of identification
Pk
Ref-name varchar 20 notnull Reference name
Address varchar 50 notnull Reference address
Phone no number 15 notnull Reference phone no
Mobile no number 15 notnull Reference of mobile
Web addr varchar 20 notnull Website address
E-mail addr varchar 20 notnull Email of address
4.4 Process Design
Integrated Software System for Enterprise Resource Scheduling was
designed and developed based on the Waterfall Model. This model particularly expresses
the interaction between subsequent phases. Testing software is not an activity, which
strictly follows the implementation phase. In each phase of the software development
process, we have to compare the results obtained against that which is required. In all
phases quality has to be assessed and controlled.
5. SYSTEM TESTING AND IMPLEMEMNTATION
5.1 Testing Objectives
Software testing is an important element of Software Quality Assurance and represents
the ultimate review of specification, design and coding. The increasing visibility of
software as a system element and the costs associated with a software failure are
motivating forces for well planned, through testing.
There are several rules that can serve as testing objectives,
1) Testing is a process of executing a program with the intent of
finding errors.
2) A good test case is the one that has a high probability of finding an
undiscovered error.
3) A successful test is one that uncovers an undiscovered error.
5.2 System Testing
System testing is actually a series of different tests whose primary purpose
is to fully exercise the computer-based system. Although each test has a different
purpose, all work to verify that all system elements have been properly integrated and
perform allocated functions.
During testing I tried to make sure that the product does exactly what is
supposed to do. Testing is the final verification and validation activity within the
organization itself. In the testing stage, I try to achieve the following goals; to affirm the
quality of the product, to find and eliminate any residual errors from previous stages, to
validate the software as a solution to the original problem, to demonstrate the presence of
all specified functionality in the product, to estimate the operational reliability of the
system. During testing the major activities are concentrated on the examination and
modification of the source code.
Testing Methodologies
The following are the Testing Methodologies:
1. Unit Testing.
2. Integration Testing.
3. User Acceptance Testing.
4. Output Testing.
5. Validation Testing.
Unit Testing
Unit testing focuses verification effort on the smallest unit of Software
design that is the module. Unit testing exercises specific paths in a module’s control
structure to ensure complete coverage and maximum error detection. This test focuses on
each module individually, ensuring that it functions properly as a unit. Hence, the naming
is Unit Testing.
Integration Testing
Integration testing addresses the issues associated with the dual problems
of verification and program construction. After the software has been integrated a set of
high order tests are conducted. The main objective in this testing process is to take unit
tested modules and builds a program structure that has been dictated by design.
The following are the types of Integration Testing:
1 - Top Down Integration
This method is an incremental approach to the construction of program
structure. Modules are integrated by moving downward through the control hierarchy,
beginning with the main program module. The module subordinates to the main program
module are incorporated into the structure in either a depth first or breath first manner.
2 - Bottom-up Integration
This method begins the construction and testing with the modules at the
lowest level in the program structure. Since the modules are integrated from the bottom
up, processing required for modules subordinate to a given level is always available and
the need for stubs is eliminated. The bottom up integration strategy may be implemented
with the following steps:
The low-level modules are combined into clusters into clusters that perform a
specific Software sub-function.
A driver (i.e.) the control program for testing is written to coordinate test case
input and output.
The cluster is tested.
Drivers are removed and clusters are combined moving upward in the program
structure
User Acceptance Testing
User Acceptance of a system is the key factor for the success of any
system. The system under consideration is tested for user acceptance by constantly in
touch with the prospective system users at time of developing and making changes
wherever required is done in regard to the following point:
1. Input Screen design
2. Output Screen design
3. Menu driven system
Output Testing
After performing the validation testing, the next step is output testing of
the proposed system, since no system could be useful if it does not produce the required
output in the specified format. The outputs generated or displayed by the system under
consideration are tested by asking the users about the format required by them. Hence
the output format is considered in 2 ways – one is on screen and another in printed
format.
Validation Checking
Validation checks are performed on the following fields.
Text Field
The text field can contain only the number of characters lesser than or
equal to its size. The text fields are alphanumeric in some tables and alphabetic in other
tables. Incorrect entry always flashes and error message.
Numeric Field
The numeric field can contain only numbers from 0 to 9. An entry of
any character flashes an error messages. The individual modules are checked for
accuracy and what it has to perform. Each module is subjected to test run along with
sample data. The individually tested modules are integrated into a single system.
Testing involves executing the real data information is used in the program the existence
of any program defect is inferred from the output. The testing should be planned so that
all the requirements are individually tested.
A successful test is one that gives out the defects for the inappropriate
data and produces and output revealing the errors in the system.
Preparation of Test Data
The above testing is done by taking various kinds of test data. Preparation
of test data plays a vital role in the system testing. After preparing the test data the system
under study is tested using that test data. While testing the system by using test data
errors are again uncovered and corrected by using above testing steps and corrections are
also noted for future use.
Using Live Test Data
Live test data are those that are actually extracted from organization files.
After a system is partially constructed, programmers or analysts often ask users to key in
a set of data from their normal activities. Then, the systems person uses this data as a way
to partially test the system. In other instances, programmers or analysts extract a set of
live data from the files and have them entered themselves.
It is difficult to obtain live data in sufficient amounts to conduct extensive
testing. And, although it is realistic data that will show how the system will perform for
the typical processing requirement, assuming that the live data entered are in fact typical,
such data generally will not test all combinations or formats that can enter the system.
This bias toward typical values then does not provide a true systems test and in fact
ignores the cases most likely to cause system failure.
Using Artificial Test Data
Artificial test data are created solely for test purposes, since they can be
generated to test all combinations of formats and values. In other words, the artificial
data, which can quickly be prepared by a data generating utility program in the
information systems department, make possible the testing of all login and control paths
through the program.
The most effective test programs use artificial test data generated by
persons other than those who wrote the programs. Often, an independent team of testers
formulates a testing plan, using the systems specifications.
5.3 System Implementation
Implementation is the stage of the project where the theoretical design is
turned into a working system. At this stage the main work load, the greatest upheaval
and the major impact on the existing system shifts to the user department. If the
implementation is not carefully planned an controlled it can cause chaos and confusion.
Implementation includes all those activities that take place to convert from
the old system to the new one. The new system may be totally new, replacing an existing
manual or automated system or it may be a major modification to an existing system.
Proper implementation is essential to provide a reliable system to meet the organization
requirements. Successful implementation may not guarantee improvement in the
organization using the new system, but improper installation will prevent it.
The process of putting the developed system in actual use is called system
implementation. This includes all those activities that take place to convert from the old
system to the new system. The system can be implemented only after thorough testing is
done and if it is found to be working according to the specifications. The system
personnel checks the feasibility of the system.
The most crucial stage is achieving a new successful system and giving
confidence on the new system for the user that it will work efficiently and effectively. It
involves careful planning, investigation of the current system and its constraints on
implementation, design of methods to achieve the changeover. The more complex the
system being implemented, the more involved will be the system analysis an the design
effort required just for implementation. The system implementation has three main
aspects. They are education and training, system testing and changeover.
The implementation stage involves following tasks.
Careful planning.
Investigation of system and constraints.
Design of methods to achieve the changeover.
Training of the staff in the changeover phase.
Evaluation of the changeover method.
The method of implementation and the time scale to be adopted are found
out initially. Next the system is tested properly and the same time users are trained in the
new procedures.
Implementation Procedures
Implementation of software refers to the final installation of the package
in its real environment, to the satisfaction of the intended users and the operation of the
system. In many organizations some one who will not be operating it, will commission
the software development project. The people who are not sure that the software is meant
to make their job easier. In the initial stage, they doubt about the software but we have to
ensure that the resistance does not build up as one has to make sure that
The active user must be aware of the benefits of using the system
Their confidence in the software is built up
Proper guidance be imparted to the user so that he is comfortable in using the
application.
Before going ahead and viewing the system, the user must know that for
viewing the result, the server program should be running in the server. If the server object
is not up running on the server, the actual processes wont take place.
User Training
To achieve the objectives and benefits expected from computer based
system, it is essential for the people who will be involved to be confident of their role in
the new system. As systems become more complex, the need for education an training is
more and more important.
Education is complementary to training. It bring life to formal training by
explaining the background to the resources for them. Education involves creating the
right atmosphere an motivating user staff. Education sections should encourage
participation from all staff with protection for individuals for group criticism. Education
should start will before any development work to enable users to maintain or to regain the
ability to participate in the development of their system.
Education information can make training more interesting and more
understandable. The aim should always be to make individual feel that they can still
make all important contributions, to explain how they participate in making system
changes, and to show that the computer and computer staff do not operate in isolation,
but are of the same organization.
Training on the Application Software
After providing the necessary basic training on the computer awareness
the users will have to be trained on the new application software. This will give the
underlying philosophy of the use of the new system such as the screen flow, screen
design, type of help on the screen, type of errors while entering the data the
corresponding validation check at each entry and the ways to correct the data entered. It
should then cover information needed by the specific user/groups to use the system or
part of the system while imparting the training of the program on the application. This
training may be different across different user groups and across different levels of
hierarchy.
Operational Documentation
Once the implementation plan is decided, it is essential that the user of the
system is made familiar and comfortable with the environment. Education involves right
atmosphere & motivating the user. A documentation providing the whole operations of
the system is being developed. The system is developed in such a way that the user can
work with it in a well consistent way. The system is developed user friendly so that the
user can work the system from the tips given in the application itself. Useful tips and
guidance is given inside the application itself to help the user. Users have to be made
aware that what can be achieved with the new system and how it increases
theperformance of the system. The user of the system should be given a general idea of
the system before he uses the system.
7. SCOPE FOR FUTURE ENHANCEMENT
Event Management System can be further enhanced in the future
by adding more customer service to the customer through Online Ticket Reservations for
participating in the events. The application can communicate to other event business
applications which can be enhanced to distribute the business data and serve as a broker
between the customer and the Business Entity. Online payment services will be the most
added advantage for the customer to make their payment through Credit Card
Transaction. The application developed is designed in such a way that any further
enhancements can be done with ease. The system has the capability for easy integration
with other systems. New modules can be added to the system with less effort.
Event Management System will be enhanced further with automated
mailing services to the customer.
8. BIBILIOGRAPHY
1. “ASP.NET UNLEASHED” STEPHEN WALTER
PEARSON EDUCATION.
2. “LEARNING ASP.NET” GLEN JOHNSON
WILEY EDITION
3. ”MICROSOFT .NET BIBLE” DON JONES
WILEY EDITION.
4. ”VISUAL C# .NET UNLESHED” –
KEVINHOFFMAN & LONNY KRUGER
PEARSON EDUCATION
5.”VISUAL C#.NET”
BRAD MAIANI,JAMES STILL
WROX EDITION
5. “ADO.NET FOR VISUAL STUDIO .NET”
BILL HAMILTON & MATHEW
MCDONALD-O’REILLY EDITION.
7 “MICROSOFT SQL SERVER 2000 BIBLE”
PAUL NELSON-WILEY EDITION.
8 ”SQL SERVER 2000 THE ULTIMATE REFERENCE”
ANTHONY SEQUEIRA & BRAIN ALDERMAL-DREAMTECH
EDITION.
9. APPENDICES
9.1 Data Flow Diagram
Context Analysis Diagram (level 0)
A P S
M a r k e t i n g
A d m i n i s t r a t o r
P r o d u c t i o n
F i n a n c eP r o m o t i o n
H RC u s t o m e r s
EVENT MANAGEMENT SYSTEM
L e v e l 2D F D F o r P r o d u c t i o n
O r d e rP r o c e s s i n g
P r o d u c t i o nM a n a g e r
P r o d u c t i o nA s s t M a n a g e r
O r d e r
S e l_ v e n d
O r d e r
L e v e l 3D F D F o r P r o d u c t i o n
P r o d u c t i o nM a n a g e r
P r o d u c t i o nA s s t . M a n a g e r
S e l e c tS e r v i c e s
O r d e r
C l i e n t
S e r v i c e s
V e n d o rS e l e c t i o n
s e l_ S e r v i c e s
p r d n_ v e n d o r
p r d n_ i t e m s
s e l_ v e n d o r s
p r d nc o s t s h e e t
O r d e r
S e l e c t e d s e r v i c e s
P r o m o t i o nM a n a g e r
P r o m o t i o na s s t . M a n a g e r
P r o m o t i o nE s t i m a t i o n
L e v e l 2D F D F o r P r o m o t i o n
o r d e r
s e l_ s e r v i c e sO r d e r
m e d i a &s e r v i c e
s e l e c t i o n
L e v e l 3D F D F o r P r o m o t i o n
P r o m o t i o nM a n a g e r
P r o m o t i o na s s t . M a n a g e r
P r o m o-v e n d o r
s e l e c t i o n
o r d e r
P r o m o- s e l- s e r v i c e s
P r o m o- v e n d o r
P r o m o- i t e m
P r o m o- s e l- v e n d
p r o m o t i o nc o s t
s h e e t
O r d e r
m o d e s o fp r o m o
H Rw o r k
e s t i m a t i o n
P r d n_ s e l_ s e r v i c e s
P r o m o_ s e l_ s e r v i c e s
E m p
E m p_ t r a c k
C o s to f
L a b o r
costsh
eets
L e v e l 2D F D F o r H R
L e v e l 3D F D F o r H R
H Rj o b
a l l o c a t i o n
P r d n_ s e l_ s e r v i c e s
P r o m o_ s e l_ s e r v i c e s
c o s te s t i m a t i o n
E m p_ t r a c k
E m p
co s ts he e ts
C o s to f
l a b o r
O r d e r
O r d e r
W o r kd o n e
F i n a n c eP r o p o s a l
P r e p a r a t i o n
o r d e r
s e l_ s e r v i c e s _ p r o d
s e l_ s e r v i c e s _P r o m o
s e l_ v e n d o r _P r o m o
s e l_ v e n d o r _P r o m o
E m p_ t r a c k
E m p
P r o p o s a l _ s t o r e
P r o p o s a l
qu o tat io n
L e v e l 2D F D F o r F i n a n c e
O r d e r
P r o d u c t i o n
P r o d u c t i o nM a n a g e r
V e n d o rM a i l i n g
P r o d u c t i o nV e r i f i c a t i o n
P r d n_ s e l_ v e n d o r s
E m p_ t r a c k
v e r i f y s t a t u s
P r d n_ s e l_ v e n d o r s
P r d n_ s e l_ v e n d o r s
P r o c e s s e s A f t e r P r o p o s a l
C r e a t i v e D i r e c t o r
C r e a t i v eD i r e c t o r
S c h e d u l eC o m p a r i s o n
A g e n d aP r e p a r a t i o n
S c h e d u l e
P r o p o s a l _ S t o r e
A g e n d a _ s t o r e
Q u o t a t i o n
Q u o t a t i o n s c h e d u l i n g
P r o c e s s e s A f t e r P r o d u c t i o n
V e n d o r
C l i e n t
V e r i f yB i l l
P a y m e n t
B i l lC l e a r a n c e
P r d n_ S e l_ v e n d o r s
V e n d o r _ b i l l
C l i e n t_ p a y m e n t
v e r i f i c a t i o n
v e r i f i c a t i o n
F i n a n c e
P r o m o_ s e l_ v e n d o r s
B i l l
C h e q u e/ c a s h
9.2 E-R Diagram