Event Management Using Pocket PC - fair Report

Event Management Using Pocket PC

1. INTRODUCTION

This software has been created as a part of our mini project. In the system study

phase we have conducted a detailed study regarding the demerits of the existing Event

Management system. By analyzing this report we have been able to create the new design

fulfilling all the demerits that were analyzed.

Nowadays all kind of events are managed through computer technologies. The

main reason is that it reduces the human efforts, save time & smooth handling. Therefore

you can estimate how much this project is beneficial.

The project entitled “Event management using Pocket PC” is a complete kit for an

event management, which includes applications for both manager (administrator) & user.

Users (exhibitors & visitors) interact with Pocket PCs offered at the stalls which are

configured with manager’s windows application.

This project is also a solution for all the difficulties encountered while conducting

an event management process involving high profile clients.

Department of Computer Science and Engg. AWH Engineering College

1


2. SOFTWARE AND HARDWARE REQUIREMENTS

2.1 Suggested hardware requirements

The hardware configuration required to perform smooth running is as

Processor : Pentium IV or above

Speed : 1.3 GHz or above

Memory : 1 GB RAM

Hard disk : 80 GB or above

Monitor : SVGA Color

Mouse : Ps/2 Compatible Mouse Port

2.2 Suggested software requirements

The software specifications required are

Operating System : Windows 7/XP/2000

Programming Language tools used

Front End : Microsoft Visual Studio .NET

Smart Device Application

Back End : Microsoft SQL server 2005

Scripting Language : C#.Net

Emulator : Microsoft Mobile Explorer


2


3. SYSTEM ANALYSIS

3. 1 Study phase

Firstly initial investigation is conducted to identify the demerits of an existing Event

Management System. This is done by visiting an Event arena and gathering information

through interviews and enquiries. The next step is to determine what features have to be

added in order to solve the problems of an existing system. The final outcome of initial

investigation is determining the possibility of an alternative system.

The main purpose of initial investigation is collecting the merits of the current

project and making reasonable changes to it. The developer also has to be aware of various

users and the nature of their requirements.

3. 2 Existing System

For the successful designing of the system it is necessary to study and analyze the

present working mode of the existing system. The existing Event Management system was

not completely centralized under the administrator. And also did not allow easy

communication and updation of the data with manager (server).

3. 3 Proposed System

The aim is to develope an Event Management system that overcomes the demerits

of existing system by providing user friendly environment for scheduling, function-

coordination and event management. The entire event is centralized under administrator

with smooth communication between segments of the event. Thus resulting in alternative

system by adding latest technologies to the existing system. The proposed Event

Management system has to be designed in such a way that it can be modified with very

little effort when such a need arises in the future.


3


4. TECHNOLOGIES USED

4.1 Microsoft .Net

Microsoft released the .net (pronounced dot net) framework in February 2002. It’s

biggest initiative since the launch of windows in 1991. . Net is a revolutionary multi

language platform that knits various aspects of application development together with the

Internet. The framework covers all layers of software development above the operating

system. Several softwares will be developed by Microsoft to achieve this goal. It is

accepted that every player in the industry, be it a software developer or a device

manufacture, adopt .Net so that they can be integrated. The .Net initiative is all about

enabling data transfer between networks, PCs and devices seamlessly, independent of the

platforms, architecture and solutions. Microsoft has taken many of the best ideas in the

industry, combined in some ideas of their own, and bought them all in to one coherent

package. . Net is Microsoft’s next –generation platform for building web applications and

web services. It is a platform for XML web services areas of Microsoft.

.Net is Microsoft’s new internet and web strategy

.Net is not a new operating system

.Net is delivers software as web services

.Net is a framework for universal services

.Net is server centric computing model

.Net will run in any browser on any platform

.Net is based on the newest web standards

The .Net framework includes classes, interfaces and value types that help expedite

and optimize the development process and give you access to system functionality.

Microsoft designed VB from the ground up to take advantage of its new .Net framework.

The .Net framework is made up of four parts. The common Language Runtime, as set of

class libraries, a set of programming languages, and the ASP.Net environment. The .Net

framework was designed with tree goals in mind. First, it was intended to make windows

applications much more reliable, while also providing an application with greater degree

of security.


4


Second, it was intended to simplify the development of web applications and

services that not only work in the traditional sense, but on mobile devices as well.

Lastly, the framework was designed to provide a single set of libraries that would

work with multiple languages. The .Net framework is the infrastructure for the new

Microsoft .Net platform and it is common environment for building, deploying and

running web applications and web services. The .Net framework contains a common

language runtime and common class libraries- like ADO.Net, ASP.Net and Windows

Forms – to provide advanced standard services that can be integrated into a variety of

computer system. The .Net framework provides a feature rich application environment,

simplified development and easy integration between a numbers of different development

languages. The .Net framework is language neutral. Currently supports C++, C#, Visual

Basic, and Jscript. Microsoft’s Visual Stdio.Net is a common development environment

for the new Framework.

One of the designing goals of .Net framework was to unify the runtime engines s

that all developers could work with a set of runtime services. The .Net Framework’s

solution is called the Common Language Runtime (CLR). The CLR provides capabilities

such as memory management, security, and robust error handling for interoperability of

different languages. Memory can be allocated by code written in one language and can be

freed by code written in another language. Similarly, errors can be raised in one language

and processed in another language.

The .Net framework provides many classes that help developers re-use code.

The .Net class libraries contain code for programming topics such as threading; file I/O,

database support, XML parsing and data structures such as stacks and queues. This entire

class library is available to any programming language that supports the .Net framework.

Because all languages now support the same runtime, they can reuse any class that works

with the .Net framework. This means that any functionality available to one language will

also be available to any other .Net language.

The .Net Framework provides a set of tools that help to build code that works with

the .Net Framework. Microsoft provides a set of languages that are already .Net

compatible.

4.2 ADO .Net

ADO.Net is a set of classes that expose data access services to the .Net

programmer. ADO.Net provides a rich set of components for creating distributed, data-


5

http://msdn.microsoft.com/library/e80y5yhx(VS.80).aspx


sharing applications. It is an integral part of the .Net Framework, providing access to

relational, XML, and application data. ADO.Net supports a variety of development needs,

including the creation of front-end database clients and middle-tier business objects used

by applications, tools, languages, or Internet browsers making access to data in MS

Windows programs a straightforward task.

The first data access model, DAO (data access model) was created for local

databases with the built-in Jet engine which had performance and functionality issues.

Next came RDO (Remote Data Object) and ADO (Active Data Object) which were

designed for Client Server architectures but, soon ADO took over RDO.

ADO was a good architecture but as the language changes so is the technology.

With ADO, all the data is contained in a record set object which had problems when

implemented on the network and penetrating firewalls. ADO was a connected data access,

which means that when a connection to the database is established the connection remains

open until the application is closed. Leaving the connection open for the lifetime of the

application raises concerns about database security and network traffic. Also, as databases

are becoming increasingly important and as they are serving more people, a connected data

access model makes us think about its productivity. For example, an application with

connected data access may do well when connected to two clients, the same may do poorly

when connected to 10 and might be unusable when connected to 100 or more. Also, open

database connections use system resources to a maximum extent making the system

performance less effective.

In addition, ADO introduced the concept of disconnected record sets as a way to

transport data between the tires of distributed applications. The low-level API behind ADO

is called OLE DB.ADO.Net was designed with the disconnected data in mind, because this

stateless approach works best for distributed Internet applications. ADO.Net contains two

sets of similar classes. One set is a generic set of classes that can be used to access all

databases that have OLE DB provider and a set of classes for Microsoft’s SQL server.

ADO.Net Entity Framework simplifies application data access by providing an

extensible, conceptual model for data from any database and enables this model to closely

reflect business requirements.ADO.Net Data Services provides a first-class infrastructure

for the next wave of dynamic internet applications by enabling Web applications to expose

data as REST-based data services that can be consumed by client applications in corporate

networks and across the internet. Based on the architecture Data Access in ADO.Net relies

on two components: Dataset and Data Provider.


6

http://www.microsoft.com/sqlserver/2008/en/us/ado-net-data.aspx

http://www.microsoft.com/sqlserver/2008/en/us/ado-net-entity.aspx

http://www.webhostingsearch.com/dedicated-server.php


The dataset is a disconnected, in-memory representation of data. It can be

considered as a local copy of the relevant portions of the database. The DataSet is persisted

in memory and the data in it can be manipulated and updated independent of the database.

When the use of this DataSet is finished, changes can be made back to the central database

for updating. The data in DataSet can be loaded from any valid data source like Microsoft

SQL server database, an Oracle database or from a Microsoft Access database.

The Data Provider is responsible for providing and maintaining the connection to

the database. A DataProvider is a set of related components that work together to provide

data in an efficient and performance driven manner. The .Net Framework currently comes

with two DataProviders: the SQL Data Provider which is designed only to work with

Microsoft's SQL Server 7.0 or later and the OleDb DataProvider which allows us to

connect to other types of databases like Access and Oracle. Each DataProvider consists of

the following component classes:

The Connection object which provides a connection to the database

The Command object which is used to execute a command

The DataReader object which provides a forward-only, read only, connected

recordset

The DataAdapter object which populates a disconnected Dataset with data

and performs update

Data access with ADO.Net can be summarized as follows:

A connection object establishes the connection for the application with the database. The

command object provides direct execution of the command to the database. If the

command returns more than a single value, the command object returns a DataReader to

provide the data. Alternatively, the DataAdapter can be used to fill the Dataset object. The

database can be updated using the command object or the DataAdapter.

The ADO.Net components have been designed to factor data access from data

manipulation. There are two central components of ADO.Net that accomplish this the

Dataset, and the .Net data provider, which is a set of components including the

Connection, Command, Data Reader, and Data Adapter objects. The ADO.Net Dataset is

the core component of the disconnected architecture of ADO.Net. The Dataset is explicitly

designed for data access independent of any data source. As a result it can be used with

multiple and differing of any data sources, used with XML data, or used to manage data

local to the application. The Connection object creates the connection to the database.

Microsoft Visual Studio .Net provides two types of Connection classes:


7


the SqlConnection object, which is designed specifically to connect to Microsoft SQL

Server 7.0 or later, and the OleDbConnection object, which can provide connections to a

wide range of database types like Microsoft Access and Oracle. The Connection object

contains all of the information required to open a connection to the database.

The Command object is represented by two corresponding classes:

SqlCommand and OleDbCommand. Command objects are used to execute commands to a

database across a data connection. The Command objects can be used to

execute stored procedures on the database, SQL commands, or return complete tables

directly. Command objects provide three methods that are used to execute commands on

the database. ExecuteNonQuery executes commands that have no return values such as

INSERT, UPDATE or DELETE. ExecuteScalar returns a single value from a database

query. ExecuteReader returns a result set by way of a DataReader object. The Data Reader

object provides a forward-only, read-only, connected stream recordset from a database.

Unlike other components of the Data Provider, DataReader objects cannot be

directly instantiated. Rather, the DataReader is returned as the result of the Command

object's ExecuteReader method. The SqlCommand. ExecuteReader method returns a

SqlDataReader object, and the OleDbCommand. ExecuteReader method returns an

OleDbDataReader object. The DataReader can provide rows of data directly to application

logic when you do not need to keep the data cached in memory. Because only one row is

in memory at a time, the DataReader provides the lowest overhead in terms of system

performance but requires the exclusive use of an open Connection object for the lifetime of

the DataReader.

The DataAdapter is the class at the core of ADO .Net's disconnected data access. It

is essentially the middleman facilitating all communication between the database and a

DataSet. The DataAdapter is used either to fill a DataTable or DataSet with data from the

database with it's Fill method. After the memory-resident data has been manipulated, the

DataAdapter can commit the changes to the database by calling the Update method. The

DataAdapter provides four properties that represent database commands:

SelectCommand

InsertCommand

DeleteCommand

UpdateCommand

When the Update method is called, changes in the DataSet are copied back to the database

and the appropriate InsertCommand, DeleteCommand, or UpdateCommand is executed.


8


4.3 SQL Server

Relational database systems are the most important database systems used in the

software industry today. One of the most outstanding systems is Microsoft SQL Server.

SQL Server is a database management system developed and marketed by Microsoft. It

runs exclusively It runs exclusively under Windows NT, Windows 95/98, Windows 2000

Server. The most important aspects of SQL Server 7 are,

SQL Server is easy to use.

SQL Server scales from a mobile laptop to symmetric multiprocessor system.

SQL Server provides data warehousing features that until now have only been

available in Oracle and other more expensive DBMS.

A data base system is an overall collection of different database software

components and database containing the parts via, database application programs, front

components, DBMS and databases.

The Database system must provide the following features

A variety of user interfaces.

Physical data independence.

Logical data independence.

Query optimization.

Data integrity.

Concurrency control.

Backup and recovery.

Security and authorization.

SQL Server is a Relational Database Management System. The SQL Server

relational language is called Transact-SQL. SQL is a set oriented language. This means

that SQL can query many rows from one or more tables using just one statement. This

feature allows the use of this language at a logically higher level than procedural language.

Another important property of SQL is its non-procedurality. SQL contains two sub

languages DDL and DML.

SQL Server work as a natural extension of Windows NT/ 95/ 98. SQL Server is

relatively easy to manage through the use of graphical computing environment for almost

every task of the system and database administration. SQL Server uses services of

Windows NT to offer new or extended database capabilities, such as sending and

receiving messages and managing login security. The SQL Server administrator’s primary


9


tool for interacting with the system is Enterprise Manager. The Enterprise Manager has

two main purposes: Administration of the database server and Management of database

objects. SQL Server Query Analyzer provides a graphical presentation of the execution

plan of a query and an automatic component that suggests which index should be used for

a selected query. This interactive component of SQL Server performs the task like:

Generating and executing Transact-SQL statements.

Storing the generated Transact-SQL statements in a file.

Analyzing execution plans for generated queries.

Graphically illustrating the execution plan for a selected query.

A stored procedure is a special kind of batch written in Transact-SQL using the SQL

language and SQL extensions. It is saved on the database server to improve the

performance and consistency of repetitive tasks. SQL Server supports stored procedures

and system procedures. Stored procedures can be used for the following purposes: to

control access authorization, to create an audit trial of activities in database tables, to

separate data definition and data manipulation statements concerning a database and all

corresponding applications. The database object view can be used for:

Restricting the use of particular columns and rows of the tables-that is to

control access to a particular part of one or more tables.

To hide the details of complicated queries, to restrict inserted and updated

values to certain ranges.

Indices are used to access data more efficiently. The Query Optimizer is the part of

SQL Server that decides how to perform a query in a better way. It generates several query

execution plans for the given query and selects the plan with the lowest cost.


10


5. SOFTWARE MODEL

Selection of a proper software model plays an important role in the development of

a software system. We have chosen waterfall model for the development of this Event

Management software.

Waterfall Model

The waterfall model is a popular version of the systems development life cycle

model for software engineering. Often considered the classic approach to the systems

development life cycle, the waterfall model describes a development method that is linear

and sequential. Waterfall development has distinct goals for each phase of development.

Imagine a waterfall on the cliff of a steep mountain. Once the water has flowed over the

edge of the cliff and has begun its journey down the side of the mountain, it cannot turn

back. It is the same with waterfall development. Once a phase of development is

completed, the development proceeds to the next phase and there is no turning back.

The advantage of waterfall development is that it allows for departmentalization

and managerial control. A schedule can be set with deadlines for each stage of

development and a product can proceed through the development process like a car in a

carwash, and theoretically, be delivered on time.

Development moves from concept, through design, implementation, testing,

installation, troubleshooting, and ends up at operation and maintenance. Each phase of

development proceeds in strict order, without any overlapping or iterative steps.

The disadvantage of waterfall development is that it does not allow for much

reflection or revision. Once an application is in the testing stage, it is very difficult to go

back and change something that was not well-thought out in the conceptual stage.

Alternatives to the waterfall model include joint application development (JAD), rapid

application development (RAD), synch and stabilize, build and fix, and the spiral model.

The model consists of six distinct stages, namely:

1. Requirements analysis: This first step is also the most important, because it involves

gathering information about what the customer needs and defining, in the clearest possible

terms, the problem that the product is expected to solve. The requirements analysis

showed need for developing software with overall control given to the administrator at the

server side, for managing all events such that there is also a feature for instant


11


communication and updation for user. In addition to this it is aimed to develop software

that is secure and affordable.

2. Design: This step consists of "defining the hardware and software architecture,

components, modules, interfaces, and data to satisfy specified requirements. It involves

defining the hardware and software architecture, specifying performance and security

parameters, designing data storage containers and constraints, choosing the IDE and

programming language, and indicating strategies to deal with issues such as exception

handling, resource management and interface connectivity. This is also the stage at which

user interface design is addressed, including issues relating to navigation and accessibility.

The output of this stage is one or more design specifications, which are used in the next

stage of implementation.

3. Implementation: This step consists of actually constructing the product as per the

design specification(s) developed in the previous step. Typically, this step is performed by

a development team consisting of programmers, interface designers and other specialists,

using tools such as compilers, debuggers, interpreters and media editors. The output of this

step is one or more product components, built according to a pre-defined coding standard

and debugged, tested and integrated to satisfy the system architecture requirements. For

projects involving a large team, version control is recommended to track changes to the

code tree and revert to previous snapshots in case of problems.

4. Testing: In this stage, both individual components and the integrated whole are

methodically verified to ensure that they are error-free and fully meet the requirements

outlined in the first step. An independent quality assurance team defines "test cases" to

evaluate whether the product fully or partially satisfies the requirements outlined in the

first step. Three types of testing typically take place: unit testing of individual code

modules; system testing of the integrated product; and acceptance testing, formally

conducted by or on behalf of the customer. Defects, if found, are logged and feedback

provided to the implementation team to enable correction. This is also the stage at which

product documentation, such as a user manual, is prepared, reviewed and published.

5. Installation: This step occurs once the product has been tested and certified as fit for

use, and involves preparing the system or product for installation and use at the customer


12


site. Delivery may take place via the Internet or physical media, and the deliverable is

typically tagged with a formal revision number to facilitate updates at a later date.

6. Maintenance: This step occurs after installation, and involves making modifications to

the system or an individual component to alter attributes or improve performance. These

modifications arise either due to change requests initiated by the customer, or defects

uncovered during live use of the system. Typically, every change made to the product

during the maintenance cycle is recorded and a new product release (called a

"maintenance release" and exhibiting an updated revision number) is performed to enable

the customer to gain the benefit of the update.

Advantages

The waterfall model, as described above, offers numerous advantages for software

developers. First, the staged development cycle enforces discipline: every phase has a

defined start and end point, and progress can be conclusively identified (through the use of

milestones) by both vendor and client. The emphasis on requirements and design before

writing a single line of code ensures minimal wastage of time and effort and reduces the

risk of schedule slippage, or of customer expectations not being met.


13



14


6. IMPLEMENTATION

Implementation is the process of bringing a newly developed system or devised

onto operational one. It is the practical job of putting a theoretical design into practice. It

may involve the computer implementation of a computer complex or the introduction of

one small subsystem. The new system and its components are to be tested in a structured

and planned manner. The implementation stage of a project is often very complex and

time consuming and many more people are involved in the earlier stages. This involves

careful planning, investigation of the current system and constraints of implementation,

creating computer-compatible files, installing hardware, training the operating staff in the

changeover procedures before the system is setup and running. A critical factor in the

conversion is not disrupting the functioning of the organization.

The implementation phase of a project covers the period from the acceptance of the

tested design to its satisfactory operations, supported by the appropriate user and

operations manual. It is a major operation across the whole organizational structure and

requires a great deal of planning. The implementation plan involves the following:

Testing to confirm effectiveness

Detection and correction of errors

Making necessary changes so as to satisfy the requirements.

6.1 Implementation Procedure

Once the PC with required specification is available then the required software’s

like Microsoft Visual Studio 2008 and Microsoft SQL Server 2005 are installed.

Microsoft Visual Studio allows to quickly and easily developing a bank of visual controls

with sliders, switches and meters or a complex form for a user to fill out. It uses the

BASIC language which is known to most computer programmers, and which can be

learned quickly if it is not already known. It is a Graphical User Interface (GUI) language.

i.e. VB program will always show something on the screen that the user can interact with

(usually via mouse and keyboard) to get a job done. The first step in building the VB

program is to get the GUI items on the screen. This is done via pull-down menus that list

the available graphical objects. Every system is slightly different but, generally speaking,

left-clicking on an object allows you to describe attributes like size and position. Right


15

http://www.ehow.com/careers/


clicking allows you to write code. With visual inheritance, developers can greatly simplify

the creation of Windows-bases applications by centralizing in parent forms the common

logic and user interface for their entire solutions. Using control anchoring and docking,

programmers can build resizable forms automatically, while the in place menu editor

enables developers to visually author menus directly from within the Forms Designer.

C# is an object-oriented programming language from Microsoft that aims to combine the

computing power of C++ with the programming ease of Visual Studio. C# is based on

C++ and contains features similar to those of Java. C# is designed to work with

Microsoft's .Net platform. Microsoft's .Net Framework is a runtime environment and

class library that dramatically simplifies the development and deployment of modern,

component-based applications. C# simplifies programming through its use of Extensible

Markup Language (XML) and Simple Object Access Protocol (SOAP) which allow

access to a programming object or method without requiring the programmer to write

additional code for each step. Because programmers can build on existing code, rather

than repeatedly duplicating it, C# is expected to make it faster and less expensive to get

new products and services to market

Microsoft SQL Server is a relational model database server produced by Microsoft. A

database is a collection of tables with typed columns. SQL Server supports different data

types. Microsoft SQL Server also allows user-defined composite types (UDTs) to be

defined and used. It also makes server statistics available as virtual tables and views

(called Dynamic Management Views or DMVs). In addition to tables, a database can also

contain other objects including views, stored procedures, indexes and constraints, along

with a transaction log. A SQL Server database can contain a maximum of 231 objects, and

can span multiple OS-level files with a maximum file size of 220 TB. The data in the

database are stored in primary data files with an extension .mdf. Secondary data files,

identified with a .ndf extension, are used to store optional metadata. Log files are

identified with the .ldfextension. SQL can query many rows from one or more tables using

just one statement. This feature allows the use of this language at logically higher level

than procedure language. Another important property of SQL is Non-Procedurally. SQL

contains two sub languages DDL and DML. SQL Server Administrators primary tool for

interacting with the system is enterprise manager. The enterprise manager has two main


16

http://en.wikipedia.org/wiki/Terabyte

http://en.wikipedia.org/wiki/Constraint_(database)

http://en.wikipedia.org/wiki/Index_(database)

http://en.wikipedia.org/wiki/Stored_procedure

http://en.wikipedia.org/wiki/View_(database)

http://en.wikipedia.org/wiki/Type_system

http://en.wikipedia.org/wiki/Microsoft

http://en.wikipedia.org/wiki/Database_server

http://en.wikipedia.org/wiki/Relational_model

http://whatis.techtarget.com/definition/0,289893,sid9_gci212559,00.html










processes. Administration of database server and management of database objects. SQL

Server query analyzer provides a graphical presentation of execution plan of a query and

an automatic component that suggests which index should be used for a selected query.

Once the installation is done the necessary directories are created in the disk drive,

to store all the files related to the project being made safely. In initial stage the necessary

icons and logos are also designed that may be needed for the project.

Now open a new windows forms application in Microsoft Visual Studio .Net C# and

the necessary environment settings are enabled that are required to make the project. The

environment settings include options like solution explorer, properties, and toolbox. The

solution explorer contains the form and its details. The properties option is also needed to

resize the forms, set the font details and basic form options. Lastly the toolbox contains the

list of contents that can be fixed on the form like label, buttons, radio button etc. Once the

environment settings are active then all the forms are designed.

Now open Microsoft SQL Server and create a new database. Then write the queries

and fields required for the tables that are created in the database. Here setting a unique

primary key to the table filed is also an important step.

Then nextly the forms that were made in Visual Studio are linked between

themselves as well as with database made using the Microsoft SQL Server.

Then format the forms that are used. And also edit them by adding appropriate

backgrounds and graphics for making the forms attractive. In order to assure user

friendliness and security appropriate message box's are also used here to notify if any

errors like blank space in the field to be filled or an error in the format of the details to be

entered occurs.

Now the windows application is tested from the server side and is debugged to find

occurrence of error in the program codes. If an error is located it is corrected and then the

application is set to trial run from the administration side.

In next phase a new Pocket PC project is opened in a smart device application. And

its basic forms are designed after the environmental settings are enabled. Then create a

duplicate database in itself from the solution explorer, since Pocket PC is not connected to

its fair end at its developing stage. After that the forms are linked between themselves as

well as with the duplicate database. Then in coding phase the forms are coded to activate

the features on form like buttons. Now the forms are formatted and they are made user

friendly and secure by displaying message box's where ever needed to notify the user.


17


Then it is debugged to locate if there is any error present in the coding. Finally the Pocket

PC application is deployed into the emulator. And the application is trial run at Pocket PC

level.

The final step is linking the Pocket PC with original backend by deleting its

previous link with duplicate backend. Then an integration test is carried out once the

windows application and pocket pc application are attached together. Now execute the

total project and debug the program to check if there is any flow and fix errors. Lastly run

a trial regression to ensure that a code is free from errors. And then create a setup file to

launch the software. Hence the product is released.

6.2 Database Design

We are using 6 tables for storing details gathered through user interfacing forms.

Login: For storing administrator login details with fields username &

password

Exhibitor: For storing exhibitor registration details with fields ex_id, ex_name

etc.

Visitor: For storing visitor registration details with fields vis_id, vis_name etc.

Ex_interestlist : For storing the details of products available with each

exhibitor

Vis_interestlist: For storing the details of items on which the visitor is

interested

Vis_feedback : For storing visitor feedback after visiting the stall.

6.3 UML

6.3.1 Use Case Diagrams

In software engineering, a use case diagram in the Unified Modeling Language

(UML) is a type of behavioral diagram defined by and created from a Use-case analysis.

Its purpose is to present a graphical overview of the functionality provided by a system in

terms of actors, their goals, and any dependencies between those use cases. The main

purpose of a use case diagram is to show what system functions are performed for which

actor. Roles of the actors in the system can be depicted.


18

http://en.wikipedia.org/wiki/Actor_(UML)

http://en.wikipedia.org/wiki/Use-case_analysis

http://en.wikipedia.org/wiki/Unified_Modeling_Language

http://en.wikipedia.org/wiki/Software_engineering


In this project, actors are Administrator, Exhibitor& Visitor


19


6.4 Input Design

Input Design is the process of converting the user-originated input to a computer

based format. The design for handling input specifies how data are accepted for computer

processing. Input Design is a part of overall system design that needs careful attention and

it includes specifying the means by which actions are taken. The following are the input

screens used in Event Management Application.

Server Side:

Administrator login

Exhibitor registration

Visitor registration

Exhibitor interestlist

Pocket PC Side:

Exhibitor login

Visitor scan

Visitor search

Visitor interestlist

6.5 Output Design

The output design has been done so that the results of processing can be

communicated to the user. Effective output design improves the clarity and performance

of outputs. Output is the main reason for developing the system and the basis on which

they will evaluate the usefulness of the application.


20


7. TESTING

This section describes the testing procedure, starting with the testing methodology

and continuing with the tests performed on the system. Software testing is a critical

element of software quality assurance and represents the ultimate review of specification,

design and coding. Testing presents an interesting anomaly for the software. The testing

phase for the ‘Event management system’ involves testing of this system using various

test data.

System testing

A series of testing is performed on the ‘Event management system’ before it is

ready for implementation. The various testing methods that has been approached for the

testing of Event management system are

Unit testing

Integration testing

Validation testing

Unit testing

In computer programming, unit testing is a software verification and validation

method in which a programmer tests if individual units of source code are fit for use. A

unit is the smallest testable part of an application. In procedural programming a unit may

be an individual program, function, procedure, etc., while in object-oriented

programming, the smallest unit is a class, which may belong to a base/super class,

abstract class or derived/child class. This project is implemented as two levels which are

1. Administrator level (Server side)

2. User level (Pocket PC side)

- In the conditional testing part each and every condition in the Event management

system is tested to both true and false aspects and all resulting paths were tested.

- In the loop testing part all the loops involved in the Event management system are

tested to all the limits possible.

Integration testing

Integration testing is systematic technique for constructing the program structure.

As an integrated testing approach different part of software are combined. The top-down

strategy has been used for upper level and bottom-up level approach is used for

subordinate levels.


21


Validation testing

Validation testing succeeds when software functions in a manner that is expected.

Some of the validations imposed in this project are as follows

Forms cannot be submitted without filling up the mandatory data so that

Manual mistakes of submitting fields that are empty can be sorted out.

All data entries are validated as per system requirement.

Forms cannot be submitted without writing email_id & website in the correct

format so that manual mistakes like these can be avoided.

User is provided with appropriate error messages about the operation errors.

Access permissions to various type of user are controlled according to the

organizational structure.

Consistency testing

All functions, informations, help messages are tested to make consistent the

system ensures uniform look and feel thought the application.

Portability testing

The system is tested under different versions of Windows operating system to

ensure platform independent. No failures occurred.

User environment testing

We have worked as various end users (manager, exhibitor & visitor) of the system.

No failures have occurred.

White-Box Testing

White-Box testing can be called as functional testing. This deals with the testing of

logic and control. This is completely related with the working of program body. Here the

program is considered first and output is considered next. By keeping the output in mind

tests each control block and logical unit. Special care has been taken to eradicate the

abnormality in all levels. White-Box testing of software is predicted on close

examination of procedural details.

User Acceptance Testing

User acceptance testing of a system is the key factor for the success of any system.

The system under consideration is tested for user acceptance by constantly keeping in

touch with prospective system users at time of developing and making changes whenever

required. The system considered is tested for user acceptance; here it should satisfy the

.


22


8. SCREEN SHOTS

This section includes the important screen shots of applications for both Server PC &

Pocket PC.

8.1 Server PC Application

8.1.1 Administrator Login

8.1.2 Main form


23


8.1.3 Exhibitor Registration

8.1.4 Visitor Registration


24


8.2 Pocket PC Application

8.2.1 Exhibitor Verification & Menu

8.2.2 Visitor Scan

8.2.3 More Exhibitor Options


25


9. CONCLUSION

The project “Event Management Using Pocket PC” assumes an ultimate solution

for the existing inconveniences in an event. After testing it was found to be achieving all

the requirements. This software conserves time by all means and saves the precious

minutes of user, and provides flexible use of the database. Any changes that lead to the

system failures are prevented with security measures. The system has been designed in

such a way that it can be modified with very little effort when such a need arises in the

future. The system has been found to work efficiently and effectively.


26


10.BIBILIOGRAPHY

[1] http://www.dummies.com

[2] http://www.wikipedia.org

[3] http://www.csharp-station.com

[4] http://www.visualbuilder.com

[5] http://www.programmerworld.net

[6] http://www.22pixels.com

[7] C# 2008 for dummies

[8] Remez elmasari, B Navathe, person. “Fundamentals of database design”

[9] Andrew Trolsen, “Pro C# 2008 and the .Net 3.5 platform”, fourth edition


27

http://www.22pixels.com/

http://www.wikipedia.org/

Documents

Event Management Using Pocket PC - fair Report