ONLINE PERSONAL EVENT MANAGER

Submitted By Names

Under the guidance of Mr. Rajmohan De Sarkar Submitted for the partial fulfillment for the degree of MC

Name and ddress of the !nstitute

ACKNOWLEDGEMENT

Certificate
"his is to certify that the #roject Report entitled $%nline #ersonal &'ent Management( prepared under our super'ision by N M&S be accepted in partial fulfillment of the re)uirements for the degree of MC * under +est Bengal Uni'ersity of "echnology ,+BU"-.

..................... ,/%D* Department of MC Countersigned by .................... !nternal Mentor for the Minor #roject ,0ecturer* Department of MC -

..................... Mr. Rajmohan De Sarkar &1ternal Mentor for the Minor #roject ,"echnical /ead* rdent "echnologies-

Table of Contents

C2N%+0&D3&M&N"............................................................................................................................4 Certificate.................................................................................................................................................4 "able of Contents..............................................................................................................................................5 "able of 6igures................................................................................................................................................7 !N"R%DUC"!%N............................................................................................................................................7 S%6"+ R& R&8U!R&M&N"S S#&C!6 "!%N.......................................................................................... 9 :.;. !ntroduction................................................................................................................................................9 :.:. #urpose..................................................................................................................................................9 4.;. %'erall Description....................................................................................................................................< 5.4.:. ccess /ome #age.........................................................................................................................= 5.4.4. User Registration..........................................................................................................................:; 5.4.5. User 0og>in...................................................................................................................................:: 5.5. Detailed non>functional re)uirements.................................................................................................::

Table of Figures

INTRODUCTION
The system is designed for managing personal events of the users the servi!e "ill #e provided online$ After entering into the site the users !an vie" the glo#al events for that month$ The users of the system need to register first for that servi!e$ And already registered users should login "ith their user %D & pass"ord$ They !an get the follo"ing servi!es' They !an vie" the already e(isting events& "hi!h are previously added #y them$ The time& duration& !ategory of the events is sho"n at first$ On !li!)ing on a parti!ular event they !an see the details or any added note& atta!hed file for that event$ *sers !an update the personal events #y adding ne" events or deleting previous events$ The servi!e provider +administrator, !an send the glo#al events& "hi!h !ould #e vie"ed #y the users$ Ne" +un!he!)ed, glo#al events are highlighted$ Categori-ation of different events e$g$' !ultural event& sports event& !onferen!e et!$ or even #y glo#al and personal events$ *sers !an !ustomi-e the page #y !hanging the vie" pattern e$g$' month vie"& "ee) vie" et!$ or #y !hanging the theme or #a!)ground !olors$ On re!eiving glo#al events email alert is generated on personal email id$ *sers !an add details li)e notes& pi!ture or other files as the detail of any event$ They !an sear!h for any parti!ular event$ They !an maintain an address #oo) in their a!!ounts$ *sers !an re.uest administrator to invite any user to the group$ /e!eives an email alert if the administrator agrees to add that re.uested user$ *sers !an re.uest administrator to send any event to other users as a glo#al event$ /e!eives an email alert if the administrator agrees to add that re.uested event as glo#al event$ *sers should log out after their 0o#$ Administrator also need to login "ith their %D and pass"ord$ They perform the follo"ing'

They ma)e the glo#al events and send them to all the users$ They add users as "ell as a!!ept users re.uested #y e(isting users or deny them$ They !an a!!ept re.uest from users to add an event in glo#al event !ategory and send it to all other users or ignore it$ They generate email alert on sending glo#al events or a!!epting user1s re.uest$ After performing all these a!tions administrator must log out$

SOFTWARE REQUIREMENTS SPECIFATION 1.0. Introduction

1.1. Purpose
The 2ystems /e.uirements 2pe!ifi!ation +2/2, is designed to e(press the #ehavioral& performan!e& and development re.uirements of this system and serves as the fundamental re.uirements do!ument for the development of the system$ The 2ystems /e.uirements 2pe!ifi!ation in!ludes a des!ription of every input into the system& every output from the system and all fun!tions performed #y the system in response to input or in support of an output$

1.2. Scope
The s!ope of the 2/2 identifies the magnitude of "hat the system "ill !over$ The 2ystems /e.uirements 2pe!ifi!ation is intended for revie" #y the !lient to ensure that all desired fun!tional& performan!e and development re.uirements have #een stated in a "ay su!h that they are3 /eada#le3 minimi-es misinterpretations #y developers and testers #y using !lear& !on!ise& unam#iguous& and !omplete language$ Testa#le3 "ill #e used for strategies in Master Test 4lan& 5un!tional Test 4lan& and other formal testing do!uments$ Modifia#le3 !hanges easily as re.uirements !hange& a!!ommodates /e.uirements Tra!ea#ility Matri(& see se!tion 6 of this do!ument& and Change Management 4oli!y$ *sea#le for Operations3 "ill #e used as a living do!ument after pro0e!t is !ompleted for operations and maintenan!e$ Maintenan!e pro0e!ts use the 2/2 to o#tain a greater understanding of the system "hen !hanges need to #e made$ Tra!ea#le3 "or)s "ith the /e.uirements Tra!ea#ility Matri( to ensure !omponents& responsi#ilities& and test !ases lin) to minimi-e impa!t for re.uirements !hange and lo!ali-e defe!ts$ 7uilda#le3 "ill #e used #y developers to "rite !ode from spe!ifi!ations$ Do!umenta#le3 "ill #e used to "rite user manual and te!hni!al manual to help train ne" staff$

1.3. Glossary
/tml 8 SDD S8 # SRS +eb Site DB /yper te1t markup language 8uality assurance Soft?are Design Document Soft?are 8uality ssurance #lan Soft?are Re)uirements Specification place on the ?orld ?ide ?eb Database

1.4. References
8$ 2ystems Analysis and Design in a Changing World & 2at-inger& 7urd& 9a!)son& :rd edition ;$ The O#0e!t Oriented Approa!h Con!epts& 2ystem Development and Modeling "ith *ML& 2at-inger& Orvi)& ;nd edition

1.5. Docu ent !"er"ie#

The remainder of this do!ument is t"o !hapters& the first providing a full des!ription of the pro0e!t$ %t lists all the fun!tions performed #y the system$ The final !hapter !on!erns details of ea!h of the system fun!tions and a!tions in full for the soft"are developers1 assistan!e . These t"o se!tions are !ross'referen!ed #y topi!< to in!rease understanding #y #oth groups involved$

2.0. Over !! De"cri#tion

This se!tion of the 2/2 des!ri#es the general fa!tors that affe!t the system and its re.uirements$ This se!tion does not state spe!ifi! re.uirements$ %nstead& it provides a #a!)ground for those re.uirements& "hi!h are defined in detail in se!tion :& and ma)es them easier to understand$

2.1. Pro$ect %bstract

Pro$ect &a e' De"elope( )y' Date' Online 4ersonal Event Management 2ystem

2.1.1. Pro$ect Scope

Online 4ersonal Event Management 2ystem is a ne" system $ The Event Management system "ill manage all aspe!ts of personal events& in!luding a sear!ha#le data#ase of up!oming events listed #y administrators users< organi-ed !alendar vie"s of planned events< user registration< user'to'event mapping !apa#ilities$ %ntera!tion "ith the Event Management 2ystem "ill #e e(tremely user'friendly "ith e(tensive online help files& allo"ing for ease of use #y a "ide variety of users "ith varying te!hni!al )no"ledge$

2.1.2. )ac*groun(
The system is designed for managing personal events of the users the servi!e "ill #e provided online$ After entering into the site the users !an vie" the glo#al events for that month$ The users of the system need to register first for that servi!e$ And already registered users should login "ith their user %D & pass"ord$ They !an vie" the already e(isting events& "hi!h are previously added #y them$ The time& duration& !ategory of the events is sho"n at first$ On !li!)ing on a parti!ular event they !an see the details or any added note& atta!hed file for that event$ *sers !an update the personal events #y adding ne" events or deleting previous events$ The servi!e provider +administrator, !an send the glo#al events& "hi!h !ould #e vie"ed #y the users$ Ne" +un!he!)ed, glo#al events are highlighted$ Categori-ation of different events e$g$' !ultural event& sports event& !onferen!e et!$ or even #y glo#al and personal events$ *sers !an !ustomi-e the page #y !hanging the vie" pattern e$g$' month vie"& "ee) vie" et!$ or #y !hanging the theme or #a!)ground !olors$ On re!eiving glo#al events email alert is generated on personal email id$ *sers !an add details li)e notes& pi!ture or other files as the detail of any event$ They !an sear!h for any parti!ular event$ They !an maintain an address #oo) in their a!!ounts$ *sers !an re.uest administrator to invite any user to the group$ /e!eives an email alert if the administrator agrees to add that re.uested user$ *sers !an re.uest administrator to send any event to other users as a glo#al event$ /e!eives an email alert if the administrator agrees to add that re.uested event as glo#al event$ *sers should log out after their 0o#$ Administrator also need to login "ith their %D and pass"ord$ They ma)e the glo#al events and send them to all the users$ They add users as "ell as a!!ept users re.uested #y e(isting users or deny them$ They !an a!!ept re.uest from users to add an event in glo#al event !ategory and send it to all other users or ignore it$ They generate email alert on sending glo#al events or a!!epting user1s re.uest$ After performing all these a!tions administrator must log out$

2.1.3. Syste

Purpose
+sers of t,e -"ent .anage ent Syste Administrators *sers of the system %ccessibility of t,e -"ent .anage ent Syste =ia any online !omputer Responsibilities -"ent .anage ent Syste Maintaining an online data#ase of events and event organi-er information

/egistering users for events$ Allo"ing the user to invite their a!.uaintan!es through administrator Responsibilities t,e -"ent .anage ent Syste #ill not ,a"e =erifying !orre!tness of event information provided #y user >andling any means of event registration +i$e$ paper registrations& email re.uests& fa( re.uests, other than online registration through the supplied data#ase &ee( for t,e -"ent .anage ent Syste To !reate an easily managed& easily a!!essed free resour!e to users$

2.2. Functional Re/uire ents Specifications

5un!tional /e.uirements are those that refer to the fun!tionality of the system& i$e$& "hat servi!es it "ill provide to the user$ Nonfun!tional +supplementary, re.uirements pertain to other information needed to produ!e the !orre!t system and are detailed separately

2.3. +se Cases

2.3.1. +se Case' %ccess 0o e Page
7rief Des!ription3 Any user must type the appropriate */L at the address #ar of the #ro"ser$ %nitial step'#y'step des!ription3 5or this use !ase to #e initiated& the user must #e !onne!ted to the %nternet and !onne!ted to the We# 2erver$ The user !onne!ts to the "e# server$

2.3.2. +se Case' +ser Registration

7rief Des!ription3 The user must register to get the re.uired servi!e %nitial step'#y'step des!ription3 5or this use !ase to #e initiated& the user must #e !onne!ted to the %nternet and !onne!ted to the We# 2erver$ The user !li!)s on the re.uired ?/egistration@ lin)$ The server returns the /egistration form$ The user fills up the form$ The user then !li!)s ?2u#mit@$ The registration goes to the Data#ase$

2.4. &on Functional Re/uire ents

There are re.uirements that are not fun!tional in nature$ 2pe!ifi!ally& these are the !onstraints the system must "or) "ithin$ The system must #e !ompati#le "ith #oth the Mo-illa 5iirefo( and %nternet E(plorer "e# #ro"sers$

3.1. Re/uire ent Specifications

3.1. -2ternal 3nterface Specifications None 3.2. Functional Re/uire ents
3.2.1. %ccess 0o e Page

+se Case &a e' Priority Trigger Precon(ition )asic Pat,

A!!ess >ome 4age Essential Menu sele!tion *ser is !onne!ted to the %nternet *ser enters into the site$ The Organi-ational 2erver presents the *ser "ith the >ome 4age$ NAA The *ser is on the >ome 4age %f there is a !onne!tion failure the 2erver returns to the "ait state 2/2 ;$:$8$

%lternate Pat, Post con(ition -2ception Pat, Reference

3.2.2. +ser Registration

+se Case &a e' Priority Trigger Precon(ition )asic Pat, %lternate Pat, Post con(ition -2ception Pat, *ser /egistration Essential Menu 2ele!tion The *ser is !onne!ted to the %nternet and on the >ome 4age The 2erver presents the *ser "ith a registration form$ The *ser fills in the registration form and !li!) su#mit #utton$ The 2erver !he!)s to see if all re.uired fields are not empty$ %f the re.uired fields are not empty& the 2erver !reates a ne" re!ord in then registration Ta#le of the Data#ase$ %f any of the re.uired fields are empty& the 2erver returns a message and returns the *ser to the registration form$ The 2erver returns the *ser to the >ome 4age NAA The user a!!ount is !reated and user1s re!ords are in!luded in the Data#ase$ %f the !onne!tion is terminated #efore the form is su#mitted& the fields are all !leared and the 2erver is returned to the "ait state$ 2/2 ;$:$;$

Reference'

3.2.3. +ser 4og5in

+se Case &a e' Priority Trigger Precon(ition )asic Pat, *ser Log'in Essential Menu sele!tion The *ser must #e !onne!ted to the %nternet and on the >ome 4age$ The *ser enters the username and pass"ord$ %f the username or pass"ord or #oth& entered #y the user& are in!orre!t then the user is as)ed #y the 2erver to retype the same$ On su#mitting the !orre!t username and pass"ord& the 2erver returns the user to hisAher 4ersonal >ome 4age$ NAA The user is on hisAher 4ersonal >ome 4age$ %f the !onne!tion is terminated #efore the username or pass"ord is su#mitted& the fields are !leared and the 2erver is returned to the "ait state$ 2/2 ;$:$:$

%lternate Pat, Post con(ition -2ception Pat,

Reference'

3.3. Detaile( non5functional re/uire ents

3.3.1 +ser (atabase ttribute Name Username pass?ord User id 3.3.2 +ser Details (atabase ttribute Name Username User id e>mail !D ttribute "ype String String String ttribute Si@e 4; :; 5; ttribute "ype String String String ttribute Si@e 4; :; 4;

#hone no 3.3.3 -"ent (atabase Attri$ute N %e &'ent id &'ent type User id

Number

4;

Attri$ute T&#e Number String String

Attri$ute Si'e :; :; :;

>ard"are3 Operating 2ystem3 %nternet Conne!tion3 2oft"are 2pe!ifi!ation3 Code 2tandard3

2erver Windo" B4 E(isting telephone lines 9;EE 5rame"or) The "e# pages "ill #e !oded in html #y using Ma!romedia Dream"eaver$ The forms "ill #e done in 9ava 2erver 4ages$ The Data#ase "ill #e used is M2 A!!ess$ Ea!h page of the "e# site "ill #e fully do!umented$

3.2.

Syste

-"olution

%n future the system !ould #e updated to organi-e events for any event organi-ing !ompany$ There must #e s!ope to re!ord monetary transa!tions for ea!h event& and handling the registration for the events$ There must #e more se!urity to the data stored a#out events and provision for !he!)ing !orre!tness of the event information$

PRO(ECT CATE)OR*
Des)top3 We#& Net"or) Appli!ation Data#ase3 O#0e!t Oriented& /elational

SOFTWARE DESI)N DOCUMENT 1+ ,o-ic ! De"i-n i+ Se.uenti ! Di -r %/0

ii+ CRC/0 2+ P1&"ic ! De"i-n i+ ii+ Entit& Re! tion"1i# Di -r %/0 C! "" Di -r %/0