“Event Management”
1.Title:- “Event Management” 2. Introduction and Objectives of Event Management :-
Introduction •
•
NC Techsoft is an Event Management agency established in 2000 to cater to growing potential of events in brand-awareness building. huge universe of Events falls under different categories. arge technology firms may hold events! which are essentially seminars! and wor"shops that populari#e or spread awareness on their products. $n automobile company may hold an event to launch a new model of a car. $ soft drin" company may hold a series of events across many cities to get attention on their specific brand of soft drin" and so on. NC Techsoft reali#ed that one of "ey ingredients of success in this business was the e%tent of networ"ed contacts the company had at any point in time. These contacts are essentially providers of specific services who can be mobili#ed &uic"ly to participate in any given event. 'or e%ample! in a (oc" )how event to populari#e a brand of soft drin"! several "ey service providers are re&uired * )ound systems! ighting providers! Canteen services! stage construction and so on. $nd since NC Techsoft was interested in carrying out operations in all metros in +ndia! it was important to develop these contacts across the country and ma"e it all available for NC Techsoft agents on the touch of a button.
•
•
NC Techsoft saw itself as a company completely bac"ed by +nformation Technology. $lthough its main office was in Mumbai! its $ccount Managers would travel to all the metro locations! interacting with clients and soliciting their business. NC Techsoft decided to create an e%tremely efficient +nformation )ystem in the bac"end and ma"e their $ccount Managers use this system wherever they are through the +nternet.
$n Event is characteri#ed by several elements coordinated together for a period of time. ,hen NC Techsoft underta"es an event contract for a client! it usually is characteri#ed by following o
b/ective of the event
o
Target audience who will visit the event.
o
eriod of the event.
o
Manner of inviting the audience 1E%clusive invitation! public advert etc.
o
Type of Event
o
3ate1s of the event
o
4enue1s of the event. 1May even be in multiple cities5towns.
o
o
•
•
6ospitality erformances
NC Techsoft sits with client to get details on all of the above parameters. NC Techsoft maintains an e%haustive list of )ervice roviders 1or 4endors who provide a speciali#ed service! which forms part of the overall event. 'or e%ample! there are more than 7-8 service providers in the category of $udio )ystems providers! almost 9-: entries each in every city for caterers! ;0-;2 entries for 3isc
across the country. =y bringing appropriate sponsors to events! event gets funded ade&uately and decisions are also ta"en in a speedy manner. ac" of funds often delay events! which means revenue losses for NC Techsoft. •
$fter initial interactions happen with a client! the first thing to do is to create an estimate for the event for which NC Techsoft is responsible. =ased on the re&uirements for the event! the various services needed are listed down and based on the rates of a specific service provider! the rates are &uoted. 3ifferent services would have different specifications and units for &uoting rate. 'or e%ample! in the case of )ound )ystems! the e%act type and power of sound systems be specified andwith rates would be on per-day basis. Catering would need be onto number of people rate &uoted peraperson.
•
•
The Estimate5proposal should also reflect the specific scheduling of tas"s within the event. The overall event would have specific dates with a description of what would happen and when. The detailed proposal would also outline when a specific service would be delivered and in place. 'or e%ample! in a (oc" )how event slated for! say! November ;0th! setting up the multi-layer stage would finish by > th November! )ound systems would be in place by ?th November and so on. The proposal would schedule all re&uired services and elements for event. ne of the items in the estimate would be NC Techsoft rofessional charges which would be a fi%ed amount depending on the event and its comple%ity. $fter negotiations! a contract is signed after firming up the rates and the schedules. NC Techsoft assigns an Event Coordinator for the event who would have complete responsibility for the successful conduct of the event. The primary responsibility of the Event Coordinator is to ensure that the )ervice roviders are contacted! briefed and purchase orders generated for availing their service. Thereafter! there should be a strict monitoring of dates and the &uality of service providedby the vendors. 3elays should be trapped in time so that there is scope for corrective action. ,ith events! the final event dates can never be changed and therefore Event Coordinators need information of every specific detail all the time. That is the role of +nformation )ystems.
•
Currently! there is no formal system by which orders are generated to service providers or for recording when such services were delivered and if the services were of the right &uality. )o information is passed around verbally and this has caused considerable problems. Events often relied on the memory capacity of the Coordinators to remember every bit of what needs to be notes made ondifferent diaries and services an done! event based were on provided from a city notes. or if Moreover! the eventif itself wasfor conducted in multiple cities! it was e%tremely difficult to coordinate various activities and telephone calls were the only means of sharing information.
. !ategor" # $%&M' This pro/ect can be purely considered for the (3=M) category. ,hy@ ,ell there are many reasons in support. •
•
•
This deals in "eeping record of all the events organi#ed. +t deals with maintenance of the rights for each level of hierarchy of the users in the company. Aeeps trac" of all the sponsors and service providers.
'oft(are Engineering )aradigm of Event management s"stem '*iral Model This model has many cycles. The radial dimension represents the cumulative cost incurred in accomplishing the steps done so far! and angular dimension represents the progress made in completing each cycle of the spiral.
A spiral model is divided into a number of framework activities, also called task regions. Typically, there are between three and six task regions. •
Customer communication * Tas"s re&uired to establish effective
•
communication between developer and customer. Planning * Tas"s re&uired to define resources! timelines and other pro/ect related information.
•
•
•
•
Risk anal ysis Of event mana gement sy stem * Tas"s re&uired to assess both technical and management ris"s. Engineering * Tas"s re&uired to build one more representations of the application. Construction and release * Tas"s re&uired to construct. Test! install and provide user support 1e.g. documentation and training. Customer evaluation * Tas"s re&uired to obtain customer feedbac" based on evaluation of software representations created during the engineering stage and implemented during the installation stage.
The spiral model is a realistic approach to the development of large-scale systems and software. Because software evolves as process progresses, the developer and customer better understand and react to risks at each evolutionary level. The spiral model uses prototyping as a risk reduction mechanism but more important enables the developer, to apply the prototyping approach at any stage in the evolution of the product. It maintains the systematic stepwise approach suggested by the classic lifecycle but incorporates it into an iterative framework that more realistically reects the real world. The spiral model demands a direct consideration of technical risks at all stages of the pro!ect and, if properly applied, should reduce risks before they become problematic.
+. Tools,)latform ard(are and 'oft(are $e/uirement '*eci0cation Of Tools , )latform:-
Technology and "nvironment •
)ervers * )B )erver 200>! Microsoft ,indows 2000
•
Clients * Microsoft +nternet E%plorer
•
Tools * 4isual )tudio 20;0
•
)ervices * ayment ateway ,eb )ervices from =an"
ard(are Interface of Event management s"stme:1. Processor: Core2 Duo. 2. Primary Memory: 1 GB or Higher RAM. 3. Secondary Memory: 5 GB o! Hard Dis" S#ace $inc %uding &rac%e ins'a%%a'ion(.
). Microso!' *indo+s ,P Pro!essiona% or Ser-er 23. #. A Modem and n'erne' connec'ion and /A0 card.
'oft(are Interface:Client End * +nternet E%plorer! perating )ystem1$ny 3evelopment End * 4isual )tudio 20;0! perating )ystem.
Ser-ers Microso!' *indo+s 2 Microso!' S/ Ser-er 2 Ser-ices ASP.04 ,M/ *e6 Ser-ices
. )roblem %e0nition$•
•
•
•
NC Techsoft needs an electronic system. system should be robust and supports multiple actions. +t should be able ta"e input from any user for any re&uirement respect of gathering. The estimation system should be able to prepare the estimates of the events.
)lanning and 'ceduling:-
3antt !art
,hich uses a calendar*oriented chart to represent the pro/ect schedule. Each activity is represented as a bar in the calendar! starting from the starting date of activity and ending at the ending date for that activity. The start and end of each activity become milestones 1or chec" points for the pro/ect. Coloring each milestone when completed can represent progress. The milestone or chec"points are usually at the completion of each tas". et us draw the antt chart for each tas" identified in these pro/ect .the hori#ontal bars indicates the duration of each tas" and all pro/ect tas"s are listed in the left handed column. ,e estimate the no. of days for each tas" as follows -)election of rgani#ation-;0 days! )election of problem-Ddays!Collection of information *27 days !$nalysis of information *;0 days !3esigning application * :0 days !Coding for the application -:7 days ! (eview the specification *Ddays! 4erification54alidation * D days! Testing -;> days ! 3ummy activity *7 days ! +mplementation and follow-up *;0 days! user training *D days. Drawback of GANNT Cart The main drawbac" of antt chart is that it does not depict the dependency relationships among the different activity .
)E$T cart of Event management s"stem he success o! any %argesca%e #ro7ec' is -ery much de#enden' u#on 'he 8ua%i'y o! #%anning schedu%ing and con'ro%%ing o! 'he -arious #hase o! 'he #ro7ec'. 9n%ess some 'y#e o! #%anning and coordina'ing 'oo% is used num6er o! #has es does no' 'o 6e -er y %arge 6e!ore managemen' s'ar's %osing con'ro%s. &ne such &R 'oo% used on %arge sca%e #ro7ec' 'o aid managemen' in e#anding and con'ro%%ing 'he u'i%i;a'ion o! #ersona% ma'e ria% !aci%i'ies and 'ime is #rogram e-a%ua'ion and re-ie+ 'echni8ue $P4R(. his 'echni8ue is used 'o #in#oin' cri'ica% areas in a #ro7ec' necessary ad7us'men's can 6e made in order 'o mee' 'he schedu%e com#%e'ion da'e 'he #ro7ec'. Pro7ec' schedu%ing 6y P4R consis' o! !our main s'e#s: P%anning Schedu%ing A%%oca'ing o! resources Con'ro%%ing he Per' char' o! 'he o-era%% im#%emen'a'ion is sho+n in !o%%o+ing !igures: NODE
DESCRIPTION
UTILIZETHENO.OF DAYS
1
Selet!"n "# "$gan!%at!"n
)
Selet!"n"#*$"+lem
-
C"llet!ng te !n#"$mat!"n
)/ Da'(
0
Anal'(!("#!n#"$mat!"n
1&Da'(
/
De(!gn!ng "# te A**l!at!"n 0& Da'(
C"2!ng #"$ A**l!at!"n
0/ Da'(
,
Rev!e3 te (*e!4at!"n
, Da'(
1& Da'( ,Da'(
5
6al!2at!"n76e$!4at!"n
,Da'(
8
Te(t!ng
15Da'(
1&
D9mm'at!v!t'
/Da'(
H4 P4R Char' is re#resen'ing 'he in'erde#endencies among 'as"s. he P4R #ro -ides 8uan'i'a'i-e 'oo%s 'ha' a%%o+ so!'+are #%anner 'o de'ermine 'he cri'ica% #a'h. he P4R Char' use is 7us'i!ied in %arge #ro7ec's.
TE )E$T !art %iagram
*
%
&
' * )
#
+
(
Node 1 - Organization Selection Node 2 - Proj / Prob Selection Node 3 - Information collect No de 4 – Analyi o f In formation Node ! - "eign of t#e a$$lication Node % - &e'ie( t#e S$ecification Node ) - *oding Node + - ,erification/,alidation Node – .eting Node 1 – "0mmy Acti'ity
Notation Notation *ritical Pat# - Acti'ity --- "0mmy Acti'ity Node
4. 'olution 'co*e:•
•
The entire application needs to be a web-based application running on the +nternet with security-based access for NC Techsoft Coordinators and staff. )ignificant time was currently being spent in very first stages itself of client interactions * namely Estimate preparation. )ince a lot of the wor" that NC Techsoft carries out is similar for a particular type of event! there was the scope to create Event Templates based on the type of event. 'or e%ample! if an Educational )eminar Event were to be conducted for an +T Training +nstitute! then the list of things to be done under such an event would be more or less the same all the time. The dates may change and the specific service provider may change. The content of what needs to be delivered will change. =ut essentially! from an estimation perspective! the chec"list remains the same. Therefore! it should be possible to create Event Templates for different "inds of events which will include all "nown important services under with a default vendor 1which can be changed from time to time for each service. Thus! selecting an Event Template and modifying its dates and service selections can arrive at Estimation at almost immediately. These templates are li"ely to be very detailed based on the e%tensive e%perience of handling such events in the past.
•
The Event ,or"sheet is a full statement of Costs and (evenues for the event. ne source of revenue for the event is through )ponsors. )uch sponsor funds may come in the form of cash or sometimes through a specific deliverable. 'or e%ample! a arment company would sponsor all hoardings for an event. The amount set aside for that would now be considered as a revenue source and would also asfigure an e%pense under $dvertising hoardings. Tic"et sales ! for e%ample! as a (evenue source. ,hile estimating an Event! all sources of (evenues need to be identified and recorded indicating either cash inflows or service-sponsorship. The Event ,or"sheet is approved by client and signed when the contract is signed after ma"ing necessary changes.
•
•
+t should be possible to generate an Estimate from an event template for a specified Client. The Estimate! when approved! would become the contract. The system should enable generation of urchase rder based on the inclusions in the Contract for specific )ervice roviders. Each urchase order would have multiple service descriptions! dates for delivery! units! rates and total amounts with provisions for ta%es and other charges. The urchase rder would also have a section to include terms of purchase. Each term specifies a condition under which service should be delivered and there can be multiple terms in a urchase rder. There should be a facility to store all commonly used terms and conditions so that they can be &uic"ly entered in the .
•
•
,henever a )ervice is delivered! there should be a )ervice 3elivery transaction that should be entered with the authori#ation of the Coordinator who would chec" for the &uality of the service delivered. )ervice $cceptance slips are generated and signed for by the Coordinator to indicate that the delivery was according to the re&uirements. ayments are released only after acceptance and according to payment terms agreed upon with the )ervice rovider. The )olution rovider is e%pected to ma"e recommendations in designing processes within NC Techsoft that can capture the necessary "inds of data so that critical monitoring information would be made available.
5.6nal"sis7%ata Models li8e 9 1 and 2 level %%s !om*lete E$ %iagrams (it cardinalit" !lass %iagrams etc. as *er te re/uirement;:%ata modeling: Da'a mode%ing is a me'hod used 'o de!ine and ana%y;e da'a re8uiremen's needed 'o su##or' 'he 6usiness #rocesses o! an organi;a'ion. he da'a re8uiremen's are recorded as a conce#'ua% da'a mode% +i'h associa'ed da'a de!ini'ions. Ac'ua% im#%emen'a'ion o! 'he conce#'ua% mode% is ca%%ed a %ogica% da'a mode%. o im#%emen' one conce#'ua% da'a mode% may re8uire mu%'i#%e %ogica% da'a mode%s. Da'a mode%ing de!ines 'he re%a'ionshi#s 6e'+een da'a e%emen's and s'ruc'ures.<2= Da'a mode%ing 'echni8ues are used 'o mode% da'a in a s'andard consis'en' #redic'a6%e manner in order 'o manage i' as a resource. use o! 'hi s s'andard is s'ro ng%y reco mmended !or a%% #ro7ec's re8uiring a s'andard means o! de!ining and ana%y;ing 'he da'a resources +i'hin an organi;a'ion.
unctional Model The functional model shows how output values in an computation are derived from input values! without regard for the order in which the values are computed. The functional model consists of multiple data flow diagrams which show the flow from e%ternal inputs! through operations and internal data stores! to e%ternal outputs. The functional model also includes constraints among values within an ob/ect model.
Data Dictionary A data dictionary is a >cen'ra%i;ed re#osi'ory o! in!orma'ion a6ou' da'a such as meaning re%a'ionshi#s 'o o'her da'a srcin usage and
!orma'.> 'erm may ha-e one o! se-era% c%ose%y re%a'ed meanings #er'aining 'o da'a6ases and da'a6ase managemen' sys'ems $DBMS(: • •
•
a documen' descri6ing a da'a6ase or co%%ec'ion o! da'a6ases an in'egra% com#onen' o! a DBMS 'ha' is re8uired 'o de'ermine i's s'ruc'ure a #iece o! midd%e+are 'ha' e'ends or su##%an's 'he na'i-e da'a dic'ionary o! a DBMS
%% 7%ata
/ 0+12evel 5lient
6ta7
0*1 2evel
"vent 3rgani4ation
"vent
5lient
"vent "ntry
"vent
3rgani4e event 6ta7
%% =2> level
5lient
8egist er
5lient
elivery 5hallan
5heck 2ogin =alid
"nter "vent
6ervice eliver y
"stimate
"vent;esc
5hec k 5onta ct :ossib le 6ponsor
9enera te "stimat e
9enera te :3 5onta ct :ossib le
=alid
:rovider
"nter :rovide 5heck r
"nter 6ponso r 6ta7
6ta7
:urchase 3rder
Entit" $elationsi* %iagram 5lient
=iew s
6ubmi ts 5heck ed by
"vent 8e>uest
6ta7 5ontac ts 6ervice :roviders
6ponsors
eclare 6ponsors hip Amount
9ener ate "stima te 5harge s "xpenses
8evenues
"stimat es "xpens es
"xpenditure
!lass %iagram
"vent "vent
5lient 5lient
Add"vent?@ 9et"vent?@ :roposal?@
8egistration?@ 2ogin?@
6ta7 6ta7name :assword
6ervice:rovider :roviderId
2ogin?@
Type :roduct nits
6ponsors 6ponsorId 6ponsor
Add:rovider?@ Assign"vent?@
?. 6 !om*lete %atabase and tables detail (it )rimar" and oreign @e"s and *ro*er !onstraints in 0elds.. Database Design and RDBMS he genera% 'heme 6ehind da'a6ase design is 'o hand%e in!orma'ion as on in'egra'ed +ho%e. here is none o! 'he ar'i!icia%i'y 'ha' is norma%%y em6edded in se#ara'e !i%es or a##%ica'ions. A da'a6ase is a co%%ec'ion o! in'erre%a'ed da'a s'ored +i'h minimum redundancy 'o ser-e many users 8uic"%y and e!!icien'%y. he genera% o67ec'i-e is 'o ma"e in!orma'ion access easy 8uic" ine#ensi-e and !%ei6%e !or 'he user. n da'a6ase design o! 'his #ro7ec' se-era% o67ec'i-es +ere considered. *.
Controlled redundancy: Redundan' da'a occu#ies s#ace and 'here!ore is +as'e!u%. ! -ersions o! 'he same da'a are in di!!eren' #hase o! u#da'ing 'he sys'em gi-es con!%ic' in!orma'ion. A uni8ue as#ec' o! da'a6ase design is s'rong a da'a on%y once +hich con'ro% redundancy and im#ro-es sys'em #er!ormance.
%.
Ease of learning and use: A ma7or !ea'ure o! user!riend%y da'a6ase #ac"age is ho+ easy i' 'o %earn and use. Re%a'ed 'o 'his #oin' is 'ha' a da'a6ase can 6e modi!ied +i'hou' in'er!ering +i'h es'a6%ished +ay o! using da'a.
.
Data independence An im#or'an' da'a6ase o67ec'i-e is changing hard+are and s'ore #rocedures or adding ne+ da'a +i'hou' ha-ing 'o re+ri'e a##%ica'ion #rograms.
.
Performance his o67ec'i-e em#hasi;es res#onse 'ime 'o in8uiries sui'a6%e 'o use o! 'he da'a. Ho+ sa'is!ac'ory 'he res#onse 'ime is de#ends on 'he na'ure o! 'he user da'a6ase dia%ogue.
The database tables that have been identified for storing data are 1.
'taA AttributeName
2.
4archar170
assword
4archar190
3esignation
4archar190
Dataty!e
Client+d
4archar170
assword
4archar190
Contacterson
4archar170
ContactNo
4archar1;;
$ddress
4archar1;00
CompanyName
4archar1>0
rimaryAey
"eature rimaryAey
EB*enditure AttributeName
+.
"eature
!lient AttributeName
.
Dataty!e
Emp+d
Dataty!e
"eature
Trans+d
Numeric1;0
rimaryAey
Event+d
Numeric1;0
'oreignAey
rovider+d
Numeric1;0
'oreignAey
Emp+d
4archar170
'oreignAey
$mount
Numeric1;0
3ateE%p
3atetime
Event%esc AttributeName Event+d
Dataty!e Numeric1;0
"eature rimaryAey
.
Client+d
4archar170
b/ective
4archar1900
$udience
4archar170
Timeeriod
4archar1;0
+nvitation
4archar170
TypeEvent
4archar190
3ateEvent
3ateTime
4enue
4archar1;00
6ospitality
4archar1;00
erformance
4archar1;00
Estimate AttributeName
4.
'oreignAey
Dataty!e
Event+d
Numeric1;0
Emp+d
4archar170
(ate
Numeric18
$pprove)tatus
=oolean
"eature 'oreignAey
'ervice)rovider AttributeName
Dataty!e
rovider+d
Numeric1;0
CompanyName
4archar1;00
Contact
4archar170
ContactNo
4archar1;;
)erviceType
4archar1;00
)ervice(ate
Numeric18
)erviceHnit
4archar120
"eature rimaryAey
5.
Event'ervice AttributeName
?.
Numeric1;0
'oreignAey
rovider+d
Numeric1;0
'oreignAey
E%penses
Numeric1;0
'*onsors Dataty!e
)ponsor+d
Numeric1;0
)ponsorName
4archar1;00
roduct
4archar1;00
"eature rimaryAey
Event'*onsor AttributeName
19.
"eature
Event+d
AttributeName
C.
Dataty!e
Dataty!e
"eature
Event+d
Numeric1;0
'oreignAey
)ponsor+d
Numeric1;0
'oreignAey
)ponsorType
4archar1;7
)ponsor)ervice
4archar170
(evenue
Numeric1;0
)urcaseOrder AttributeName
Dataty!e
"eature
Event+d
Numeric1;0
'oreignAey
rovider+d
Numeric1;0
'oreignAey
3escription
4archar1900
3ate3elivery
3atetime
11.
Hnits
Numeric1;0
(ate
Numeric1;0
Ta%es
Numeric1;0
thers
4archar120
ther(ate
Numeric1;0
%eliver"!allan AttributeName
Dataty!e
"eature
ChallanNo
Numeric1;0
rimaryAey
Event+d
Numeric1;0
'oreignAey
rovider+d
Numeric1;0
'oreignAey
Emp+d
4archar170
'oreignAey
Challan3ate
3atetime
Buality
=oolean
$mount
Numeric1;0
$ccept)tatus
=oolean
C. 'tructure of Event management s"stem D Modular 'tructure •
•
•
•
Customer #odule * +t is customer who has to ta"e initiative for inputting the values for any event. Event management * The events needs to be entered for the company to organi#e. $!onsors management * )ome events cannot do without sponsors so their arrangement and management has to be done.
'ervice )roviders management C These are care taker of the event so work has to be allotted.
:rocess 2ogic of Dodule
!ustomer Module 5ustomer
=isits Eebsite
5reates Account
oes "vent "ntry
Event Module
2ogin
5heck :ropos al
6ta7
=isits Eebsite
2ogin
=iews "vent "ntry
9ets 6ponsors Arranged
5hecks 6ervice :roviders
:repar es :ropos al
'*onsors Module
6ta7
=isits Eebsite
2ogin
Adds 6ponsors 6ponsorsh ip Amount
9et 5omplete etails
6ponsorsh ip Dethod
'ervice Module
6ta7
=isits Eebsite
2ogin
Adds 6ervice :roviders 8ate per nit
9et 5omplete etails
D Im*lementation Metodolog" Of Event Management s"stem ! .Fet C? is an e%egan' and 'y#esa!e o67ec'orien'ed %anguage 'ha' ena6%es de-e%o#ers 'o 6ui%d a +ide range o! secure and ro6us' a##%ica'ions 'ha' run on .04 @rame+or". ou can use C? 'o crea'e 'radi'iona% *indo+s c%ien' a##%ica'ions ,M/ *e6 ser-ices dis'ri6u'ed com#onen's c%ien'ser-er a##%ica'ions da'a6ase a##%ica'ions and much much more. Microso!' isua% C? 25 #ro-ides an ad-anced code edi'or con-enien' user in'er!ace designers in'egra'ed de6ugger and many o'her 'oo%s 'o !aci%i'a'e ra#id a##%ica'ion de-e%o#men' 6ased on -ersion 2. o! 'he C? %anguage and 'he .04 @rame+or".
! Ganguage C? syn'a is high%y e#ressi-e ye' +i'h %ess 'han "ey+ords i' is a%so sim#%e and easy 'o %earn. he cur%y6race syn'a o! C? +i%% 6e ins'an'%y recogni;a6%e 'o anyone !ami%iar +i'h C C or Ea-a. De-e%o#ers +ho "no+ any o! 'hese %anguages are 'y#ica%%y a6%e 'o 6egin +or"ing #roduc'i-e%y in C? +i'hin a -ery shor' 'ime. C? syn'a sim#%i!ies many o! 'he com#%ei'ies o! C +hi%e #ro-iding #o+er!u% !ea'ures such as nu%% a6%e -a%ue 'y#es enumera'ions de%ega'es anonymous me'hods and direc' memory access +hich are no' !ound in Ea-a. C? a%so su##or's generic me'hods and 'y#es +hich #ro-ide increased 'y#e sa!e'y and #er!ormance and i'era'ions +hich ena6%e im#%emen'ers o! co%%ec'ion c%asses 'o de!ine cus'om i'era'ion 6eha-iors 'ha' are sim#%e 'o use 6y c%ien' code. C? 6ui%d #rocess is sim#%e com#ared 'o C and C and more !%ei6%e 'han in Ea-a. here are no se#ara'e header !i%es and no re8uiremen' 'ha' me'hods and 'y#es 6e dec%ared in a #ar'icu%ar order. A C? source !i%e may de!ine any num6er o! c%asses s'ruc's in'er!aces and e-en's.
. FET rame(or8 )latform 6rcitecture use in Event Management C? #rograms run on 'he .04 @rame+or" an in'egra% com#onen' o! *indo+s 'ha' inc%udes a -ir'ua% eecu'ion sys'em ca%%ed 'he common %anguage run'ime $C/R( and a uni!ied se' o! c%ass %i6raries. he C/R is Microso!'Fs commercia% im#%emen'a'ion o! 'he common %anguage in!ras'ruc'ure $C/( an in'erna'iona% s'andard 'ha' is 'he 6asis !or crea'ing eecu'ion and de-e%o#men' en-ironmen's in +hich %anguages and %i6raries +or" 'oge'her seam%ess%y.
)ource code written in CI is compiled into an intermediate language 1+ that conforms to C+ specification. The + code! along with resources such as bitmaps and strings! is stored on dis" in an e%ecutable file called an assembly! typically with an e%tension of .e%e or .dll. $n assembly contains a manifest that provides information on the assemblyJs types! version! culture! and security re&uirements..
'HG server 'he
S/ Ser-er is a c%ien'ser-er da'a6ase sys'em. he ser-er runs S/ Ser-er da'a6ase so!'+are +hich #rocesses re8ues's
su6mi''ed 6y 'he da'a6ase c%ien' so!'+are and sends 'he resu%'s 6ac" 'o 'he c%ien'. he S/ 4ecu'i-e and 'he S/ Ser-er Da'a6ase 4ngine ser-ice are eam#%es o! da'a6ase ser-ices #er!ormed 6y S/ Ser-er. he S/ Ser-er so!'+are is arranged in mu%'i#%e %ayers. he 0e' /i6rary %ayer +hich acce#'s connec'ions !rom c%ien's hides 'he ne'+or" connec'i-i'y de'ai%s +hen a c%ien' communica'es +i'h a ser-er running S/ Ser-er. 0e'/i6raries use in'er#rocess communica'ion $PC( mechanisms such as named #i#es remo'e #rocedure ca%%s $RPCs( and *indo+s Soc"e's. Se-era% 0e'/i6raries are inc%uded +i'h S/ Ser-er !or 6o'h 'he ser-er and 'he c%ien'. 0e'/i6raries on ser-er %is'en !or c%ien' connec'ion a''em#'s.
$e*orting 'tructure of •
The )ystem should answer the following &uestions in the form of reports or &ueries o
o
o
o
o
o
,hat are the pending activities in a specific Event! when are they e%pected to be completed and by whom @ ,hat is the comparison between the budget for a specific event and actual amounts already spent @ ,hat are the pending service deliverables from a specific )ervice rovider across all events that purchased from that provider @ ,hat is the (evenue 4s E%penditure summary of a specific event @ To what e%tent has revenue sources supplemented total Event e%penditure @ ,hich )ervice rovider has been contracted the ma%imum number of times previously for a particular "ind of service@ 1$cross all locations and in a specific location ,hich )ervice provider! under a given category of service! has been always punctual with delivery and &uality of delivery@
o
o
,hich service provider is consistently delaying delivery over the specified period@ 1Eg. Hpto ;0K of the time! 20 * 90K! more than :0 K and so on. )ummary and details of NC Techsoft earnings
$cross all Events
$cross events of a specific Event type
$cross events for a specific Client
$cross events for a specific ocation 1where possible
$cross events of a specific Event Coordinator
Im*lementation of 'ecurit" Mecanism of •
•
•
•
2ogin :rocess has proper check for authentic user to login.
uture 'co*e and furter enancement The future is &uite bright for the system. +t has to reach all of the people on their mobile sets. )o the system will became more popular.
%ibliogra!y *.
Fol4uer 6teven A6:.
%.
Dc. 9raw hill
6oftware engineering and design
:ressman .
9algotia atabase system concept Gorth :ublication
ebsites *. www.Dicrosoft.com and www.freshersworld.com
