Você está na página 1de 93

Exhibition Management System

MAHARSHI DAYANAND COLLEGE


PAREL, MUMBAI-400 012 PROJECT REPORT ON

Exhibition Management System

BY Miss. Pratima Patil. T.Y.B.SC (COMPUTER SCIENCE) 2010-11

PREFACE

Exhibition Management System

This project reports aims at introduction to Exhibition Management System, a System developed for information about Exhibition. This report depicts the information used for the system development. For detail information scope of the project along with table design and Screen Layouts are provided. Although this report is prepared with utmost care, there may be errors for the project and is subjected to further enhancements.

PRATIMA N. PATIL

Acknowledgement

Exhibition Management System

It gives us a great pleasure to present this project on Exhibition Management System and would like to take this opportunity to thank everyone who has been a part of making it possible. We would also like to thank prof. Miss.sonal pawar (Head.Of.Department), for providing all the necessary system facilities and privileges than enabled us to complete the project on time. We sincerely express our gratitude to prof.Mr.Vishal Ghogare. We are heartly thankful to them for their unfailing inspiration and encouragement during the course of our project. Their innate knack of unfolding new ideas forms us and adopting the same to practical work has been of great help. During the progress of this report we received all possible help from our colleagues; friends and we most sincerely acknowledge the same. Last but not the least we great debt to our parents for offering their invaluable guidance and help in the hour of need improving our project with positive criticism.

INDEX

Exhibition Management System

SR. No. 1 (a) (b) (c) (d) (e) (f) 2. (a) (b) (c) (d) (e) (f) (g) (h) (i) 3. (a) (b) (c) (d) (e) 4. (a) (b) (c) (d) (e) (f) (g) 5. 6. 7.

TOPIC Preliminary Investigation Organization Overview Description Of System Limitation Of Present System Proposed System And Its Advantages Feasibility Study Gantt Chart System Analysis Fact Finding Technique (Questionnaire) Event Table Use case Diagram,UseCase Description Entity Relationship Diagram Activity Diagram Class Diagram Object Diagram Sequence Diagram State Diagram System Design Converting ERD To Tables Component Diagram Package Diagram Deployment Diagram Structure Chart System Coding Menu Tree List Of Table with Attributes and Constraints Program List Validations Test Cases Screen Layouts with Validation and Description Report Layout
System Implementation

PAGE NO 7 8 10 11 13 18 19 21 23 25 31 32 38 40 42 51 52 52 53 55 57 59 61 61 62 67 68 69 70 84
90

Future Enhancement Reference And Bibliography

91 92

Exhibition Management System

Exhibition Management System

Introduction
This project is about Exhibition Management. The purpose of

developing this project is to decrease the working load of management. The main aim to do this project is to convert the MANUAL system into the COMPUTERISED system that is very useful to them.

1.1 Purpose
The Software is for Automation of Exhibition management. The Software includes : Maintaining Member,Exhibition records. Booth Details. Maintains Calender of Exhibitiion. Retrives Final Bill.

1.2 Scope
It can be used by management for maintaining members detail and keep track of all Exhibitions.

1.3 Technologies to be used


This project will be a desktop application to be developed in VB.net having MS Access as backend. Database Design(Ms Access) Form Design(VB .net) Coding(VB.net)

Exhibition Management System

PRELIMINARY INVESTIGATION

Organizational Overview

The Maharashtra Vyapari Peth was established in 1989. It is located in Dadar, Mumbai. They organizes many Exhibitions at various location.Manages booth and allocate booth to the members as they demand. Then According the price of booth they create the bill. This all work is done manually by the peth. The peth currently is not using any kind of software. Peth is in need of software which will help in solving the said given problems throughout the documentation.

Exhibition Management System

Existing System
The existing system, which was studied for developing a new system, was manual one. This system is difficult to use. It is a tedious job to work on this system as a lot of efforts have to be put in to maintain the data on paper. Moreover, there is always a chance of corruption of data by unauthorized access.

Exhibition Management System

Current System

The current system does not have software and is working on pc without any. All the work is stored on the disk. Member details,exhibition detsails,booth details are stored in a excel sheet. It becomes difficult for searching the particular Exhibition whenever needed. General bill is calculated manually. Reports are generated in format of the word files.The system does not provide any Back-end . Thus data is stored manually . This system stores data in individual files.Eg:-member data in member file, Exhibition data in Exhibition file and bill data in bill file.

Exhibition Management System

Limitation of Current System

Lack of computerization leads to time wasting in gathering data. Huge paper work had to be maintained to keep the track of ongoing transactions. This System is time-consuming and very tedious. Another need could be updating in this system to enhance the functioning of system and also update certain existing processes to more optimal procedures. Data security is poor ,for eg:there is chance of misplacing of records. For storing a data it requires large space like no. of cupboards. It is efficient neither for Admin nor for the user.

10

Exhibition Management System

PROPOSED SYSTEM

1) Membership Registration:Maintaining member registration 2) Store booth details. 3) Booth booking and space allocation:Manage booth booking, space allocation and all exhibition management features 4) Manage registration of exhibitors and attendees:5) Stores all service details. 6) The records which were maintained manually in the files will now be Maintained in the database. 7) The records could be added , edited, deleted and also retrieved easily through the front end provided by our system .It is also possible to have multiple copies of the records. 8) While entering the data in the system, most of the validation will be done Automatically, that is if the user of the system enters wrong data in the Database then automatically error message will be prompted to the user that he should enter the right data. 9) This software made all the things possible i.e. maintenance of data, inconsistency of data & poor data security.

11

Exhibition Management System

Advantages of Proposed System

The proposed system empowers the user with a new computer based

system by reducing the efforts of data maintains. This System developed according to the user specification hence it is

A user-centered system. Data protection through password and restore facility. Daily/Weekly report generation. No previous expertise on computers required using the software. Reduces manual work of records keeping,ledger posting etc. Data is available electronically.Eliminates data entry work

12

Exhibition Management System

FEASIBILITY ANALYSIS:
When the developer is building any system, he/she should make sure that the system he/she is going to build is feasible. Feasibility study mainly comprises of three kinds of feasibility. Technical Feasibility Economical Feasibility Operational Feasibility

Technical Feasibility:
Technical Feasibility is concerned with the availability and capability of hardware, software and people.

Hardware:

A computer should be available that is powerful enough to handle the proposed system. DBMS systems usually consume more computer power because of its data structure, security, Rule. These take more machines processing time. Now almost any system is technically feasible.

Software:

According to convenience of the system, the system developer should decide which computer languages or software he/she is going to use for the proposed project. The developer should keep in mind that the software or languages he/she is going to use should be easily available, efficient, and portable and the database language. In case of matrimonial application system software the Language used to build the system is very popular language VB.Net.
13

Exhibition Management System

People:

The developers of the system should be ready to learn a new set of skills if necessary. It will be beneficial if he is thorough with the Operating System and System Development Life Cycle. During the development of matrimonial application system software a new skill was learned of how to make the best use of two applications Microsoft Visual studio edition 2008, Microsoft SQL server 2008 with VB.NET and SQL.

Economical Feasibility:
Usefulness of the Project is to be based on the cost benefit analysis from this perspective a project that costs greater than the benefits is only in feasible in the sense that it is not profitable to undertake such project. First, the cost and the benefit ratio should be estimated and then the project should be undertaken. The present software developed for the Marathi vyapari mitara mandal, Mumbai has proved to be economically and technically beneficial.

Operational feasibility:
A system is technically feasible and is implemental. Management has actively supported us in implementation of the system.

14

Exhibition Management System

STAKE HOLDERS
Stake holders are the primary source of information for the for the system requirements. Stakeholders are the people who have an interest in the successful implementation of the system. Generally, we categorize stakeholders into three groups 1) The users, those who actually use the system on daily basis. 2) The clients, those who pay for and own the system. 3) The technical staff, the people who must ensure that the system operates in the computing environment of the organization.

USERS AS THE STAKE HOLDERS

There are 3 types of users:

1) Business users
Business users are the people who use the system to perform the dayto-day operations of an organization. We often call these operations transactions. A transaction is a piece of work done in an organization, such as enter an order etc.. Business users provide information about the daily operations of the business and the ways the system must support them.

2) Information users
Information user is a person who needs current information from the system. This person might be an operational user or someone else. In some cases, a business might want to make information directly available to customers. However an information user may not be allowed to enter information on business transactions, just to view specific information. An information user, then, monthly, and annually and about what information is most convenient.

15

Exhibition Management System

3) Management users
Managers are responsible for seeing that the company is performing its daily procedures efficiently and effectively. Consequently, they need statistics and summary information from a system. Management will help an analyst answer the following questions: What kind of reports must the system produce? What kind of performance statistics must the system maintain? What kind of volume information must his system keep? And what volumes of transactions must the system support? Are the controls in the system adequate to prevent errors and frauds? How many requests for information will be made and how often?

4) External users
More and more systems today allow external entities to have direct access to the system. Customers may directly access to the system through internet. Suppliers may have access to a system to check inventory levels and to initiate billing transactions. These users are more difficult to identify and access because they are not regular members of the organization. However today they belong to an important group that must be considered in system development

CLIENT STAKEHOLDERS
Although project team must meet the information processing needs of the users, it also must satisfy client. Client Is the person or the group who is providing funding for the project. In many cases, the client is the same group as the executive users. However, clients may also be a separate
16

Exhibition Management System

group such as board of trustees or executives in a parent company. The project team includes the client in its list of important stakeholders because the team must provide periodic status reviews to the client through the development.

TECHNICAL STAKEHOLDERS
Although the technical staffs are not a true user group, this group affects many system requirements. The technical staffs include people who establish and maintain the computing environment of the organization. They provide guidance in such areas as programming language, computer platforms, and other equipment. For some projects, the project team includes a member of the technical staff. For other projects, technical personnel are available as needed.

17

Exhibition Management System

GANTT CHART

Analysis Phase
June July August

Week Week Week Week Week Week Week Week Week Week Week Week 1 2 3 4 1 2 3 4 1 2 3 4 System Analysis Study of Current System Documentation of Proposed System Study Data of System and draw Class Diagram Study of Scenario and Documentation Draw Event Table Draw Use Case Diagram Draw Sequence Diagram Draw Collaboration Diagram Draw State Chart Diagram Present System Requirement

Planning

Execution

Break

18

Exhibition Management System

SYSTEM ANALYSIS

System Study:1) The Planning Phase: The primary objectives of this phase are to identify the scope of the new system, ensures that the project is feasible, develop a schedule, allocate the resources & budget for the remainder of the project.

The FOUR activities in the project planning phase, 1. Define the problem 2. Confirm the project feasibility 3. Produce the project scheduled

2) The Analysis phase:


The primary objectives of this phase are to understand the business need & processing requirements of the new system. Analysis is essential to find out the process of business. There are FIVE Primary Activities: 1. Gather the Information 2. Define the system requirements 3. Build prototype for requirements 4. Generate and evaluate alternatives 5. Review recommendation with management

19

Exhibition Management System

3) The

Design phase:

The objectives of design phase are to design solution for the system. High-level design consists of developing as architecture structure for software programming, database, the user interface and the operating environment. Design activity is closely interrelated. 1) Design an application network 2) Design the application architecture 3) Design the user interface 4) Design the system interface 5) Design the integrated database 6) Design and integrate the system controls 4) The

Implementation phase:

During the implementation phase the final system is built ready to install. The objectives of this phase is not only to have reliable , working information system but also to ensures that the user are all trained and that t the business is benefiting. This phase have FOUR major activities. 1. Construct the software component 2. Verify the testing 3. Train and documentation 4. Install the system

20

Exhibition Management System

FACT FINDING TECHNIQUES Onsite Observations


Observations were done during the first interview with director. It was very useful in which it help us to understand how each employee works and interact with the current system.

Interviews
We mainly interviewed the executive director and administrative assistant. The information provide by both interviewees was very important because it help us in the analysis of the current system. In the interviews some objectives are considered such as: 1) Determining the areas to be discovered. 2) List the facts you want together.

Questionnaires
This helps us to find the information about how the project will walk through and the processing of it can be done. There may be different themes applied to this module. The three major themes are as follows. What are the business processes?? The question asked most formally is what do you do??? The focus is on understanding the functionality of the work. It must contain all the information of all the process which is on going. The users provide answers in terms of the present system. so we must take into consideration what of the functions are fundament5al and what of them should be eliminated and improved system. How is the business process performed?? The second question how can it be done?-moves the discussion from the current system to the new system. The focus is on how the new system should support the function rather than how it does now. Thus, the first two questions go hand in hand to discover the need and begin to define the system requirements in terms of the new system. What information is required?
21

Exhibition Management System

The final question what information is needed? Elaborates the second question by defining specific information that the new system must provide. The answers to the second and the third question form the basis for definition of the system requirements. One of the shortcomings of the many new systems analysts is that they do not identify all of the required pieces of information .in both this questions and the previous one detail, detail, and detail, is the watch word. An analyst must understand the nitty-gritty detail to develop a correct solution.

Here are some of the questions which interrogate the client.

1) 2) 3) 4) 5)

What is the current system? How it works? What all modules you currently work with? How are the bills prepared? How are the raw material details stored? How you store the details of the client? That is personal information, Measurements, site photos etc.

6) What is the overall functioning of the system? 7) What modules you would like to integrate? 8) What are the limitations in the current system?

22

Exhibition Management System

Event Table

EVENT TABLE
List of events gathered during analysis are entered in event table. An event table includes rows and columns representing events and their details respectively. The rows record the information about every event. The columns record information about the event.

TRRIGER
Tells the system that event has occurred for an external event the arrival of data, the system must process is a triggered. A customer places an order, then the new order details are provided as input.

SOURCE
It is the external agent or actor that supplies data to the system.Ex. Customer is the source of new order details.

ACTIVITY
Activity is the system reaction to the event when the customer plac an order the system carries out the activity to create new order.Response is an input from the system. There could be several response to one activity.

DESTINATION
Destination is where the response is sent which is again an external agent or actor. An event could have no response. Ex. Customer wants to update account info, the information is recorded in the database but no output needs to be produced. Event table is convenient way of recording key information about the requirement of the information system.

23

Exhibition Management System


NO 1. 2. 3. 4. 5. EVENT USER LOGIN REGISTRATI ON OF MEMBER UPDATION OF MEMBER ADDITION OF EXHIBITION DETAILS ADDITION OF EXHIBITION DETAILS DELETION OF EXHIBITION DETAILS ADDITION OF BOOTH DETAILS ADDITION OF SERVICE DETAILS FILL EXHIBITION FORM SELECTION OF EXHIBITOR ALLOCATION OF BOOTH PAYMENT TRIGGER LOGIN REQUEST NEW REGISTRATION UPDATE MEMBER DETAILS NEW EXHIBITION ENTRY UPDATE EXHIBITION DETAILS DELETE EXHIBITION DETAILS ADD NEW BOOTH DETAILS ADD SERVICE DETAILS NEW EXHIBITOR ENTRY SELECT EXHIBITOR ALLOCATE BOOTH TO EXHIBITOR PAYMENT OF BOOTH CANCEL BOOTH GET BILL DETAILS SOURCE MEMBER MEMBER MEMBER MANAGEME NT MANAGEME NT ACTIVITY ENTER PASSWORD CREATE NEW REGISTRATION OF MEMBER UPDATING MEMBER DETAILS ADDING EXHIBITION DETAILS UPDATING EXHIBITION DETAILS DELETING EXHIBITION DETAILS ADDING BOOTH DETAILS ADDING SERVICE DETAILS FILLING EXHIBITION FORM EXHIBITOR SELECTION ALLOCATING BOOTH PAYING PAYMENT BOOTH CANCELLED RETRIVING BILL DETAILS RESPONSE USER LOGGED IN NEW MEMBER CREATED MEMBER DETAIL UPDATED EXHIBITIO N DETAILS ADDED EXHIBITIO N DETAILS UPDATED EXHIBITIO N DETAILS DELETED BOOTH DETAIL ADDED SERVICE DETAILS ADDED EXHIBITIO N FORM FILLED NEW EXHIBITOR SELECTED BOOTH ALLOCATED TO MEMBER PAYMENT BILL GENERATE D REFUND REPORT DISPLAY DESTINATION SYSTEM MANAGEMENT/ MEMBER MANAGEMENT/ MEMBER MANAGEMENT/ MEMBER MANAGEMENT/ MEMBER

6.

MANAGEME NT MANAGEME NT MANAGEME NT MEMBER MEMBER

MANAGEMENT/ MEMBER MAMAGEMENT MANAGEMENT MANAGEMENT/ MEMBER MANAGEMENT/ MEMBER MANAGEMENT/ MEMBER MANAGEMENT/ MEMBER MANAGEMENT/ MEMBER MANAGEMENT/ MEMBER

7. 8. 9. 10.

11. 12.

MEMBER MEMBER

13. 14.

CANCELLATI ON OF BOOTH RETRIVE BILL DETAILS

MEMBER MANAGEME NT/ MEMBER

24

Exhibition Management System

USE CASE DIAGRAMS


Use Case Diagrams model the functionality of system by using Actors and Use Cases
Actor

Actor is user of the system Actor is any entity that is external to the system, thus deriving some benefit From the interaction Actor can be human being, a machine ,or software Actor is a role that a particular user plays while interacting with the system Examples of Actor as End-user(roles), External systems, and External object (entities).

Use Case

Use case are services or functions provided by the system to its users.A Use case is the set of activities performed within a system by a user.Each Use Case describes one logical interaction between the actor and The system Defines what has changed by the interaction
Drawing the Use Case

A Use Case Diagrams has the following elements: Stick figure: representing an Actor Oval: representing a Use Case Association lines: representing communication between Actor and Use Case
Identifying the Use Case

Identifying the different types of Actor and their usage in the system. For each Actor, we identify the function they initiate or participate

25

Exhibition Management System

Use Case Diagram

New Member

Selection Of Exhibitor

Allocation Of Booth

Payment

Generate Payment Bill Member Cancellation Of Booth

Management

Refund

26

Exhibition Management System

LOGIN EXTENSION

LOGIN INVALID LOGIN <<extend>> <<include>> <<includes>>

SIGNIN

SIGNOUT

Management

27

Exhibition Management System

New Member (Extension)

Login
<includes> <includes>

New Member

Registration
<include> Member

Fills Exhibition Form

28

Exhibition Management System

Selection of exhibitor (extension)

Fill up exhibition form

<<includes>>

Get Exhibition Details


<<includes>> Check available booth <<uses>> Issue booth charge <<includes>>

User

Confirm Booking

Management
<<uses>> Update booking table

29

Exhibition Management System

Cancellation of Booth (extension)

Cancellation of Booth

<<includes>>

Get Exhibitors Details <<includes>> Check cancellation period <<uses>> Issue cancellation charge <<includes>>

Member Confirm Cancellation <<uses>> Update booking table

Management

30

Exhibition Management System

ENTITY RELATIONSHIP DIAGRAM

The file system structure is the database structure of the system. It represents the storage system structure. An ER-Diagram (Entity Relationship Diagram) is the graphical model of the data needed by the system. This includes entity about which information is stored and relationships among them. It is provided in structured analysis methods.

BOOKING_MASTER

BOOK_DETAILS_TEMP BOOKING_DETAILS PAYMENT

EXHIBITION

CANC_DETAILS

MEMBER

31

Exhibition Management System

Activity Diagram
It is a variation of state chart diagram organized according to actions and mainly targeted towards representing the internal behavior of method (implementation) of an operation or use case. An activity diagram represents the execution state of mechanism as a sequence of steps grouped sequentially as parallel control flow branches. An activity is displayed as stereotype of state an activity is represented by a rounded rectangle in the same way as states in a state diagram but the rectangle is more oval in appearance. Each activity represents a particular state within the execution of the method. Activities are linked by automation transitions represented by arrows. When an activity terminates the transition is triggered and the next activity starts. It is not necessary to place event name on the transition but activities may be guarded by mutually exclusive Boolean conditions. A decision is represented by a diamond with many transitions coming out of it. Synchronization between control flows is shown by using synchronization bars. They make it possible to open and close parallel branches within the flow of execution of method. The synchronization bar is crosses when all input transition on the bar has been triggered. To show various activities within a mechanism or organization the activity diagram is split swim-lanes (as in swimming pool) each responsibility is given to each lane. Relative positions of the lanes are not important and transition can cross the lanes. Object flows are represented by dotted lines. Arrows are used to relate an object to the activity that created it and activities that involve too. State and event are represented by rectangles with rounded edges Transition information is also shown through activity diagram. A single broadcast is symbolized by convex pentagon linked by dotted arrow to the object that is to receive the signal.

32

Exhibition Management System

Login:

Enter User Name and Pass word

Submit User Name And Password

Verify User Name and Password

Invalid login Valid login

Redirect to user homepage

33

Exhibition Management System

New member:

Member

System

Enter Member Info.

Enter Member Info.

no

yes
Enter Member Info.

Enter Exhibition Form

Exhibitor selection:

End Process

Enter Member Info.

34

Exhibition Management System

SELECT EXHIBITOR

Management

System

Select exhibitor

Build selected exhibitor info.

Allocate booth

Build booth info

Issue booth charges

Build charges details

End process

Close process

35

Exhibition Management System

Exhibition

Management

System

Enter Exhibition Details

Buid new Exhibition

Exhibition Over Delete Details Back up the Details

End Process

Close process

36

Exhibition Management System

Payment: Management System

Enter payment details

Booth Confirm

Payment
Booth Cancel

Build payment record

Refund

Print receipt

End payment process

Close process

37

Exhibition Management System

CLASS DIAGRM
Classes of objects have attributed and associations just like data entities, cardinality also supplies among classes .objects do the actual processing in the system as well as storing information. Processing is done because objects have methods. Class diagram is used to depict following features. The classes that exist in the system the class name, the key fields, the methods of the classes. Association between classes what types of associations exist between different classes? Subtype, super type relationshipsClasses may also form sub-types giving hierarchies using polymorphism. The class diagram can represent these hierarchies also. Relationships between classes Aggregation is indicated by hollow diamond. Composition is indicated by filed diamond. Diamond points to the whole class or the aggregate.

Multiplicity indicates the number of instances of one class linked to one instance of another class. Ex.

SYMBOL 1 0....* * 0....* 1....*

MEANING Exactly one Zero or one Many Zero to many One to many

38

Exhibition Management System

BOOK_DETAILS _TEMP
ID FK_BOOK_NO FK_EXH_ID BOOTH_TYPE PRICE NO _OF_DAYS TOTAL

1 1..* 1..*

BOOKING_MASTER

1..*

BOOKING_DETAILS
ID FK_BOOK_NO FK_EXH_ID NO_OF_BOOTH TOTAL_PRICE

BOOKING_NO FK_MEMBER_ID 1..* BOOKING_DATE

1..*

CANC_DETAILS
1..* CANCELLATION_ID FK_MEMBER_ID FK_EXH_ID GRAND_TOTAL REFUND

MEMBER EXHIBITION
1 EXHIBITION_ID EXHIBITION_NAME LOCATION_NAME START_DATE END_DATE AVAILABLE_BOOTH L-SHAPE U-SHAPE T-SHAPE 1 MEMBER_ID SURNAME FIRST_NAME MIDDLE_NAME ADDRESS CITY PIN_CONE PHONE_NO MOBILE_NO EMAIL 1 1

PAYMENT
PAYMENT_ID FK_BOOK_ID ADVANCED_PAYMENT BALANCE_PAYMENT 1

39

Exhibition Management System

OBJECT DIAGRM
Object diagrams describe the static structure or the snap shot of the system at a particular time. Ex. We have department class, employee and address when values are assigned for the object i.e. sales department, employee name jack and home address as the address of jack. This is shown as object diagram.

Representation of objects

Each object is represented by rectangle which contains either the name of the objects, the name of the class and the object (separated by a colon), or only the object class.

40

Exhibition Management System

BOOK_DETAILS _TEMP
ID=1 FK_BOOK_NO=1 FK_EXH_ID=1 BOOTH_TYPE=L-SHAPE PRICE=3000 NO _OF_DAYS=3 TOTAL=9000

1 1..*

BOOKING_MASTER
BOOKING_NO=1 FK_MEMBER_ID=4 BOOKING_DATE= 21/2/2011

1..*

BOOKING_DETAILS
1..*

1 1..*

ID=1 FK_BOOK_NO=1 1..* FK_EXH_ID=1 NO_OF_BOOTH=3 TOTAL_PRICE=27000

CANC_DETAILS
1..* CANCELLATION_ID=1 FK_MEMBER_ID=1 FK_EXH_ID=1 GRAND_TOTAL=27000 REFUND=20000

MEMBER EXHIBITION
EXHIBITION_ID=1 EXHIBITION_NAME=KOLHA PURI MELAVA LOCATION_NAME=WORALI START_DATE=1/11/2011 END_DATE=1/16/2011 AVAILABLE_BOOTH=100 L-SHAPE=20 U-SHAPE=40 T-SHAPE=40 1 MEMBER_ID=1 SURNAME=PATIL FIRST_NAME=PRATIMA MIDDLE_NAME=NIVRUTT ADDRESS=DADAR CITY=MUMBAI PIN_CONE=4000012 PHONE_NO=7845335 MOBILE_NO=5454656567 EMAIL=PAT@GMAIL.CO 1 1

PAYMENT
PAYMENT_ID=1 FK_BOOK_ID=1 ADVANCED_PAYMENT= 20000 BALANCE_PAYMENT= 7000

41

Exhibition Management System

Sequence diagram

A sequence diagram shows the sequence of the interactions between objects that occur during the flow of events of a single scenario or use case. Four basic symbols are used in a sequence diagram. They are,

The Actor symbol Represented by a stick diagram. It indicates work done by the actor in the given system.

The Object symbol Represented by a rectangle with the object name underlined. It can be written in 3 different ways objname : - name of the object and underline.

: objname :- colon followed by objname and underlined. Ram : objname :- the value followed by a colon and the object name

The Lifeline Symbol Represented by a dashed line or narrow vertical rectangle. The vertical line under an object is to show the passage of time for the object.

The Message symbol Represented by directional message arrow with a message description. A sequence diagram represents a specific set of message and interchanges between objects thus objects are indicated on the diagram instead of classes.

42

Exhibition Management System 1. sequence diagram for member registration:

Member
user

system

register

1.Registration request

2.Add information

3.Registration done 4.Registration confirm

43

Exhibition Management System

2. Create new Member

Management

Member

CreateNewMember(Member info)

NewMemberCreated

44

Exhibition Management System

3. Create New Exhibition

Management

ExhibitionMaster

Exhibition id =Create new Exhibitions(Exhibition id)

NewExhibitionCreated

45

Exhibition Management System

4.Display Booth Details

Management

Booth

Boothinfo: =GetBoothDetails(Booth id)

BoothInfo

46

Exhibition Management System

5. Create new Booth Booking

Customer

Admin

[Exhibition] booking _id: = CreateNewExhibition Booking

Booth Booth name Booth type: = Getboothdetails

Add booth (booth_Id)

47

Exhibition Management System

6.Display Exhibition Details

Management

Booth

Exhibition Master

(Memberid, member name)= Get Booth Detail (BoothNo)

(Exhibition Name ) =GetExhibitionDetails (Exhibition id)

48

Exhibition Management System

7. Display bill record:-

Customer

Admin

Bill generate

[Bill] payment_id:= Payment info

Get payment info

49

Exhibition Management System 8. Display bill cancellation record:-

Customer

Admin

Request For cancel Booth

Cancellation

Get refund

50

Exhibition Management System

STATE DIAGRAM
LOGIN
Accept uername, password Details homepage

yes
Client details are accepted

login completed
Redirect to the homepage

MEMBER

Client details are accepted

No

Accept member details Member details accepted

Record creation

yes

Member details completed


Record inserted into the database

No

EXHIBITION
Addition of exhibition details Exhibition details Added
updated

Record Updated
Record inserted into the database

51

Exhibition Management System

SYSTEM DESIGN
CONVERTING ERD TO TABLES
BOOKING_MASTER BOOKING_DETAILS
PK ID FK FK_BOOK_NO FK FK_EXH_ID NO_OF_BOOTH TOTAL_PRICE PK BOOKING_NO FK_MEMBER_ID BOOKING_DATE

BOOK_DETAILS _TEMP
PK FK FK ID FK_BOOK_NO FK_EXH_ID BOOTH_TYPE PRICE NO _OF_DAYS TOTAL

MEMBER EXHIBITION
PK EXHIBITION_ID EXHIBITION_NAME LOCATION_NAME START_DATE END_DATE AVAILABLE_BOOTH L-SHAPE U-SHAPE T-SHAPE PK MEMBER_ID SURNAME FIRST_NAME MIDDLE_NAME ADDRESS CITY PIN_CONE PHONE_NO MOBILE_NO EMAIL

CANC_DETAILS
PK CANCELLATION_ID FK FK_MEMBER_ID FK FK_EXH_ID GRAND_TOTAL REFUND

PAYMENT
PK FK FK PAYMENT_ID MEMBER_ID FK_BOOK_ID ADVANCED_PAYMENT BALANCE_PAYMENT

52

Exhibition Management System

COMPONENT DIAGRAM

Standardized and interchangeable software that is fully assembled and ready to use is component. Component diagrams are used during the implementation phase of an application. Components diagrams can also be represented as a static implementation view of a system. The component diagram allows you to combine deployment nodes with components to show which components run on each node (i.e. hardware)

53

Exhibition Management System

Admin Computer

Exhibition Management

Visual Basic .Net

Database Server

ACCESS

54

Exhibition Management System

PACKAGE DIAGRAM

It is a high level diagram that identifies the major components of the system only two symbols are used in package diagram. 1. Tabbed rectangular:

It identifies the major section (system) and subsystem enclosure of sub system within the primary system indicates thats it is a part of the major system 2. Dashed arrow:

The arrow is a dependency arrow. The arrow is connected to the independent package.

55

Exhibition Management System

View Layer Business Layer

Login.vb
Exhibiti_b ooking.vb members earch.vb Booking.r pt

Member.vb

exhibition.vb

cancellation.v

payment.vb

Login

Exhibition

b
Exhibitionsearc h.vb cancellation.rp t boothsearch

.vb
payment.rpt

Booking Exhibition

Cancel Exhibition

exhibition .rpt

member.rpt

Book_repot.r pt

changepassword.vb

Data access Layer


Login Member_details

Exhibition

56

Exhibition Management System

DEPLOYMENT DIAGRAM

In a deployment diagram, the focus is on what software element uses which hardware that is how the system is deployed. The diagram shows where and how the system components will be deployed. It is a specific map of the physical layout of the system. A deployment diagram expresses a system into production or test environment. It shows where components will be located on each server machine or hardware. It may represent or illustrate network links, LAN, bandwidth It consists or describe A) Cube B) Links Cube: It represents the hardware components used in the system like the CPU and printer. Links: Used to connect the various hardware components together in the system.

57

Exhibition Management System

Microsoft Access

EXHIBITION Database

Exhibition Management System

58

Exhibition Management System

Structure Chart

Exhibition Management System


Member Name Exhibition Details Exhibition Details

Member Name Member Registration

Exhibition Entry

Transaction

Exhibition for member Member Details Add Member Member Name

Register Member Member Name Add Member Record

59

Exhibition Management System

USER REGISTER MEMBER

REGISTERED

EXHIBITION DETAILS GET MEMBER j GET EXHIBITION DETAILS

GET MEMBER

GET EXHIBITION DETAILS

Get the exhibition details

B
EXHIBITION DETAILS EXHIBITION DETAILS

C ALCULATION

BILL CALCULATION

SHOW BILL REPORT

GET EXHIBITION CHARGES

60

Exhibition Management System

SYSTEM CODING
MENU TREE
MDI MASTER MEMBER

EXHIBITION TRANSACTION BOOKING

CANCELLATION PAYMENT SEARCH EXHIBITION

MEMBER BOOTH REPORT BOOKING

EXHIBITION MEMBER

61

Exhibition Management System

LIST OF TABLES WITH ATTRIBUTES AND CONSTRAINTS 1) Table name: ADMIN_LOGIN


This table stores the username and password.

Column Name

Data Type Text Text

Description

Constraint

USER_NAME PASSWORD

Holds the user name Holds the password

Not Null Not Null

2) Table name: MEMBER_LOGIN


This table stores the username and password.

Column Name

Data Type Text Text

Description

Constraint

USER_NAME PASSWORD

Holds the user name Holds the password

Not Null Not Null

3) Table name: MEMBER


This table stores the details about the member..

Column Name

Data Type Number Text Text Text

Description

Constraint

MEMBER_ID SURNAME FIRST_NAME MIDDLE_NAME

Holds the member id Holds the surname Holds the first name Holds the middle name

Primary Key Not Null Not Null Not Null

62

Exhibition Management System

ADDRESS CITY PINCODE PHONE_NO MOBILE_NO EMAIL_ID

Text Text Number Text Text Text

Holds the member address Holds the city Holds the pincode number Holds the member phone no Holds the member mobile no Holds the member email id

Not Null Not Null Not Null Not Null Not Null Not Null

5) Table name: EXHIBITION


This table stored the information about Exhibition including the exhibition name, location name, start date and available booth.

Column Name

Data Type Number Text Text Text Text Number

Description

Constraint

EXHIBITION_ID EXHIBITION_NAME LOCATION_NAME START_DATE END_DATE AVAILABLE_BOOTH

Holds the exhibition id Holds the exhibition name Holds the location name Holds the exhibition start date Holds the exhibition start date Holds the exhibition available booth Holds the exhibition l-shape booth Holds the exhibition u-shape booth Holds the exhibition t-shape booth

Primary Key Not Null Not Null Not Null Not Null Not Null

L_SHAPE U_SHAPE T_SHAPE

Number Number Number

Not Null Not Null Not Null

63

Exhibition Management System

6) Table name: BOOKING_MASTER


This table stores the booking number of particular member along with booking date.

Column Name BOOKING_NO FK_MEMBER_ID BOOKING_DATE

Data Type Text Number Text

Description Holds the booking no Holds the member id Holds the booking date

Constraint Primary Key Foreign key Not Null

7) Table name: BOOKING_DETAILS


This table stors member has booked which exhibition and how many booth ho booked and total price.

Column Name ID FK_BOOK_NO FK_EXH_ID NO_OF_BOOTH

Data Type Text Text Number Number

Description Holds the id Holds the booking no Holds the exhibition id Holds the no of booth that member booked Holds the total price

Constraint Primary Key Foreign key Foreign key Not Null

TOTAL_PRICE

Number

Not Null

7) Table name: BOOKING_DETAILS_TEMP


This temporary table stores the booking done by member.

Column Name ID FK_BOOK_NO FK_EXH_ID BOOTH_TYPE

Data Type Text Text Number Number

Description Holds the id Holds the booking no Holds the exhibition id Holds the booth type

Constraint Primary Key Foreign key Foreign key Not Null

64

Exhibition Management System

PRICE NO_OF_DAYS TOTAL

Number Number Number

Holds the price of booth Holds the no of days of exhibiiton Holds the total booth booked by member

Not Null Not Null Not Null

8) Table name: PAYMENT


This table stores the payment information for particular member also includes advanced payment and balance payment.

Column Name

Data Type Text Text Number

Description

Constraint

PAYMENT_ID FK_BOOK_ID ADVANCED_PAY MENT BALANCE_PAYM ENT

Holds the payment id Holds the booking id Holds the member advance payment Holds the member balance payment

Primary Key Foreign key Not Null

Number

Not Null

9) Table name: CANCELLATION


This table stores the cancellation done by member and refund.

Column Name

Data Type Text

Description

Constraint

CANCELLATION_ ID FK_MEM_ID FK_EXH_ID REFUND

Holds cancellation id

Primary Key

Number Number Number

Holds the member id Holds the exhibition id Holds the refund

Foreign key Foreign key Not Null

65

Exhibition Management System

PRPGRAM DESCRIPTION WITH NAMING CONVENTION

NAMING CONVENTION

OBJECT NAME
Database Form Lable Text box Button Image Report Date Time Picker Combo box

PREFIX
Db frm lbl txt btn img rpt dtp com

66

Exhibition Management System

PROGRAM DESCRIPTION

NO
1 2 3 4 5 6 7

FORM NAME
NEW_MEMBER_FORM NEW_EXHIBITION EXHIBITION_BOOKING PAYMENT CANCELLATIONFORM LOGINPAGE ADMIN_MDI

DESCRIPTION
It is used to add,modify,delete and nevigatethe member details. It is used to update, delete,navigate and addexhibition details. It is used to book the exhibition for particular member. It is used for payment. It is used to cancel the booth. It is used to log in the system. In which menu bar is present from which admin can select the menu and go wherever he/she wants to go. It is used to search the exhibition. It is used to search the booth. It is used to search the member. It is used to create new member. It used to create login name and password when new member is created. It used to change the password. In which menu bar is present from which user can select the menu and go wherever he/she wants to go. It is used to navigate and search booth details for member. It is used to navigate and search member details for member. It is used to navigate and search exhibition details for member.

8 9 10 11 12

SEARCHEXHIBITION SEARCH_BOOTH SEAECHFORM new_member NAMEPASSWORD

13 14

CHANGEPASS MEMBER_MDI

15 16 17

Show_booth Show_member ADD_EXHIBITION

67

Exhibition Management System

VALIDATIONS

Validation Name
Numonly()

Description
This function allows the user to enter only numeric values and no characters or any other special symbol. It is called on the KeyPress Event of those TextBoxes which should contain only numbers.

Charonly()

This function allows the user to enter only characters and no numeric values or any other special symbol. It is called on the KeyPress Event of those TextBoxes which should contain only characters.

EmailVal()

This function alloes user to enter E_MAIL in the format abc@pqr.com . It is called on tne KeyPress Event of Those TextBoxes which should contain email.

68

Exhibition Management System

TEST CASES,TEST DATA AND TEST RESULT


Test case The name field should contain A-z or a-z The name field should contain A-z or a-z Test data Letters from A-Z or a-z State Valid Test Input case abc Expected result It will allow the user to enter the name Message to be displayed: Name cannot contain number special characters. It will allow the user to enter the number Message to be displayed: Contact No. cannot contain characters. It will allow the user to enter the emailid

Number or any other special character

Invalid

Contact no. should contain exact 10 digits

Digits from 09

Valid

9867586867

Invalid Less than or greater than 10 digits or any characters Standard emailid

9867/abcd

Email should be in standard format

Valid

abc@gmail.com

Invalid Use of extra spaces.

a bc@gmail.com Message to be displayed: Enter valid emailid.

69

Exhibition Management System

SCREEN LAYOUTS AND REPORT LAYOUT

SCREEN LAYOUTS: LOGIN:

70

Exhibition Management System

SPLASH SCREEN:

71

Exhibition Management System

CREATE NEW MEMBER:

72

Exhibition Management System

MDI FORM:

73

Exhibition Management System

MEMBER:

74

Exhibition Management System

EXHIBITION:

75

Exhibition Management System

BOOKING

76

Exhibition Management System

CANCELLATION

77

Exhibition Management System

PAYMENT

78

Exhibition Management System

SEARCH MEMBER:

79

Exhibition Management System

SEARCH EXHIBITION:

80

Exhibition Management System

SEAECH BOOTH:

81

Exhibition Management System

CHANGE PASSWORD:

82

Exhibition Management System

ABOUT US:

83

Exhibition Management System

REPORT AND BILL

BOOKING BILL:

84

Exhibition Management System

CANCELLATION BILL:

85

Exhibition Management System

PAYMENT BILL:

86

Exhibition Management System

EXHIBITION REPORT:

87

Exhibition Management System

EXHIBITION BOOKING REPORT:

88

Exhibition Management System

MEMBER REPORT:

89

Exhibition Management System

SYSTEM IMPLEMENTATION/UPLOADING
Steps Open Visual Studio 2008 IDE. In the File Menu, click on New Project. Select Other Project Types. Click on Setup and Deployment and Select Setup Project or Setup Wizard. Setup Wizard Type the Name in the Name dialog box and click OK. Click NEXT. Select the option: Create a setup for a Windows application.; and click Next. Add the files you want to include and click Next. A File System window will open. Build the Project. A setup file and a Windows Installer Package files are created in the Debug folder of this project. Setup Project Type the Name in the Name dialog box and click OK. Click NEXT. A File System window will open. Right click on Application Folder Add File. Add the files you want to include. In order to add a shortcut on Users Desktop, right click on it and Add the files. Build the Project.

90

Exhibition Management System

FUTURE ENHANCEMENT

Following are the updating which can be done to this system in its future version: Data-Back-Up and Recovery option.

More networking features.

Crystal reports software would be used for generating reports.

Making project to run in different resolution.

91

Exhibition Management System

BIBLIOGRAPHY

BOOKS

Murach Visual Basic 2008, Anne Boehm, Murach Mastering Visual Basic 2008, Evangelos Petroutsos, Willey-India Edition System Analysis and Design, Satzinger, Jackson, Burd, Cengage Learning, India Ed. Software Engineering: A Practitioners Approach, Roger Pressman.

WEBSITES
www.daniweb.com www.dotnetspider.com

92

Exhibition Management System

Epilogue

Although extensive effort has been put by myself to develop this project and full code is debugged numerous times by me, but you see there are times when things doesnt go the way one expects them to go!

Hence in case of mistake physical or logical I hope that you will be kind enough to make me aware of my mistakes and will overlook it. I will ensure that I will try to check that the mistakes are not repeated in future!!

Thanking you!!
PRATIMA N.PATIL

93