EVENT MANAGEMENT SYSTEM

Prepared By:
Innovins Software Solutions

CONTENTS
1. OBJECTIVES 2. OUR RESPONSIBILITIES 3. PROJECT PLANNING 4. FEASIBILITY STUDY 5. TECHNOLOGY 6. SOFTWARE REQUIREMENTS 7. SYSTEM DESIGN 8. FORM DESIGN 10. TESTING 11. FLOW DIAGRAM 12. BIBLIOGRAPHY .

OBJECTIVES

Event Management Software (EMS) gives the management the power to ease through the Participants registration process in the various events organized during a show. An authorized EMS administrator can login and access the database containing participant information. He can add, delete, update records about participant information. Along with this, he can also allocate the various participants already registered in the Participant information database to the Events. This software provides all the necessary features of a robust system such as Domain Constraints, Indexing and Networking. EMS is developed with the Visual Basic 6 IDE as the front-end application and MS Access as the back-end software.

OUR RESPONSIBILITIES
There are various activities that are needed to be considered time to time o Developing the logic required for solving various problem. o Studying, analyzing and representing the relations between the various components of the system. o Designing and developing user interface o Writing codes for processing data. o Designing reports and forms for displaying the output. o Designing and developing software. o Validating the data entry. o Implementing communication between network computers. o Writing codes to add new information, deleting previous one and modifying existing one. o Enabling transfer of data across different computers. o Writing reusable codes. o Developing user-friendly interface controls.

PROJECT PLANNING

Project planning of this project include the following points.

What the interface will look like (use various controls). The files needed with their structure, organisation and processing. How the data will be validated. The procedure needed

FEASIBILITY STUDY
A procedure to identify, describe and evaluate the candidate system and select the best system for a given job is termed as feasibility study. Many feasibility studies are dissillusioning for both users and analyst. Firstly, the analyst is required to evaluate every solution. Secondly, most studies tend to overlook the confusion inherent in system development.

FEASIBILITY CONSIDERATIONS
To perform a feasibility study, we need to consider the economical, technical and behavioral factors in system development. Lets briefly review each consideration and how it relates to the system design effort.

ECONOMIC FEASIBILITY
Economic analysis is the most frequently used method for evaluating the effectiveness of a candidate system. More commonly known as a cost/benefit analysis, the procedure is to determine the benefits and savings that are expected from a candidate system and compare them with costs.

TECHNICAL FEASIBILITY
In this type of feasibility study, we evaluate the existing computer system (h/w, s/w etc.) in terms of To what extent will it support the proposed solution.

BEHAVIORAL FEASIBILITY

In this type of feasibility, people are inherently resistant to change and computers have been known to facilitate change. An estimate should be made as to how strong a reaction the user staff is likely to have towards the development of a computerized system.

TECHNOLOGY

The development team has decided to use "Visual Basic 6.0" as a development platform. The decision is based on the following features of Visual Basic 6.0"Seeing the size of the application and the no. of screens Involved, we are concerned about finding a way to present data to the user in the simple but attractive manner. The screen should not look confusing or cluttered". Based on the committee orders & requirement analysis, the development team has decided to create a new look for the screen & the multi_tier design for the project. We are using MS ACCESS as a back end. MS ACCESS supports the RDBMS (Relational Database Management System) structure. It is used to store various types of Data Access pages. MS-ACCESS provides a variety of option for viewing and manipulating database objects.

SOFTWARE REQUIREMENTS
VB 6.0 MS-ACCESS Operating System: Windows 95 / 97 / 98 SE / ME / 2000 / NT / XP.

SYSTEM DESIGN
INPUT DESIGN
Input design is the process of converting user-oriented input to a computer-based format. Input data are collected and organized into groups of similar type of data. So, basically, it consists of data preparation, data capture and data entry. Care is taken to minimize the data to be captured. No redundant data is to be captured. The layout of the input document should be such that it is easily understandable by the operator. Input controls provide ways to: Ensure that only authorized user has access to the system. Guarantee that transactions are acceptable. Validate the data for accuracy. Determine whether any necessary data have been omitted.

OUTPUT DESIGN
Computer output is the most important and direct source of information to the user. Efficient, intelligent output design should improve the system's relationship with the user and help in decision making. The objective of the output design is to produce timely, accurate and relevant information in a user understandable form.

FILE DESIGN

In

file design it is seen that which data item is to be stored? What will be the length of the record in a file? The arrangements of record within a file are ascertained.

SCREEN SHOTS

LOGIN SCREEN

MAIN PAGE

PARTICIPANT REGISTRATION FORM

EVENT CHOICE FORM

EVENT REGISTRATION FORM

TESTING
INTRODUCTION
Software testing is an important element of software quality assurance and represents the ultimate review of specification, design and coding. It also evaluates the increasing visibility of the software of the system element and costs associated with software failure for a well planned and thorough testing. Testing presents an interesting challenge for the software engineer and attempts to build the software from an abstract concept to an acceptable implementation. In testing, the engineer creates a series of test cases that are intended to trap the software that has been built. Testing requires that the developer discards the preconceived notions of the correctness of the software developed and overcome a conflict of interest that occurs when errors are uncovered. Theoretically, a newly designed system should have all the pieces in working order, but in reality, each piece works independently. The purpose of system testing is to consider all the likely variations to which it will be subjected and then push the system to its limit. It is a tedious but necessary step in a system development.

PROGRAM TESTING
A program represents the logical elements of a system .For a program to run satisfactorily, it must compile and test the data correctly and fit in properly with other programs. Program testing checks for two types of errors: syntactical and logical. A Syntax error is a program statement that violates one or more rules of the language in which it is written .The errors are shown through error messages generated by the computer. A Logical error deals with incorrect data fields, output of range items are invalid combinations. The programs are checked for syntax and each logical path is traced during the testing for avoiding the illogical errors. No error is left for correction.

METHOD TESTING
Methods are invariabily related to each other and interact in a complete program. Each method is tested to see whether it conforms to relate

methods in a system. Each portion of the system is tested against the entire module with both test and live data before the entire system is ready to be tested. All methods of a program are connected to one another and test is carried to see whether the path of the methods and objects are in order.

TESTING INFORMATION FLOW

In this test process two class inputs were taken. They are: 1 Software configuration that includes software requirement specification and source code. 2 Test configurations that includes a test plan and procedure. Testing tools and test cases and there expected results. The test was conducted and all results were evaluated i.e. the test results were compared with the expected results and concluded that software quality and reliability are acceptable.

DATA FLOW TESTING

The data flow testing method selects test paths of program according to the locations of definitions and users of variable in the program.

SYSTEM TESTING
System testing is a series of different tests whose primary purpose is to fully exercise the computer based system. Although each test has a different purpose, all the work should verify that all system elements have been integrated and perform allocated functions.

RECOVERY TESTING
This is a system testing that forces the software to fail in a variety of ways and verifies that recovery is properly performed. If recovery is reutilization, checking point's mechanism data recovery and restart are evaluated for correctness. If recovery requires human intervention, the mean time to repair evicted to determine the error, determine whether it is within acceptable limits.

PERFORMANCE TESTING
This testing is designed to test the run time performance of software within the context of an integrated system .This testing occurs throughout all steps in the testing process.

REQUIREMENT ANALYSIS
A requirement survey was conducted, and probable solutions for these requirements have been identified. This analysis was carried out by studying the existing system and conducting extensive discussion with the system administrators. The solution to the analysis was that a highly interactive yet simple user interface screen would be defined for the users.

SYSTEM REQUIREMENTS:
The solution offered by the developing team addressed the following requirements: System Maintenance and Administration: Provide an easy and simple method of updating information of different participants in the various events. Maintain database of all the entries in the various events.

Customer Interface: Provide an easy method of browsing for information related to different events and the participants enrolled for the events. Enable a search based on various criteria's.

FLOW DIAGRAM

BIBLIOGRAPHY
1. Visual basic Programming 6.0 by Steven Holzner (Black book). 2. Mastering Visual Basic 6.0 3. Infomation system by Ms. Sarika Jain. 4. Management Information system by James A.OBrien. 5. Database Management by Korth