CHAPTER 1INTRODUCTION

1. INTRODUCTION

1.1 OVERVIEWTech Fest Registration System is a new online as well as offline registration concept which uses the client server application for online registration and Console application for the offline registration. It Include:1. The complete knowledge of each and every events like its totle no. of rounds, max. & min no. of participants, participation fees etc. 2. The interested participant can register himself by using online registration.3. An automated user-id and password will be sent to the email-id of participant.4. usng the unique user-id and password, participant can login to various events make the online payment using the secure gateway(here IDBI).As a new registration system, it has been developed fast in china, But I think the development progress is different form the western countries. Client Server Application for online registration. Console Application for offline registraion.

The following list is a quick summary of Techfest modalities currently in use:1. Online registration for distance participants (no face-to-face meetings)2. Blended instruction (combining online and face-to-face registration)3. Synchronous: real-time, multiple participants can register online, instructor-led.4. Asynchronous: participant can register himself in online mode but using his unique user-id he/she can make payment in offline mode.5. We use multiple layering .

1.2 SCOPE TechFest registration System has world wide scope because any distant participant can get the information about the events and register thereselves for various events. The biggest advantage of Techfest registration lies in its ability to cover distances. For the participants who are spread across multiple locations, traditional registration becomes a constraint. All participants need to come to a university/college for the registration. Additionally, sometimes participant also does not get time to go again and again to the university due to lack of time hence online registration is the solution for all this type of problem.

1.3 PURPOSED WORK

1.) Console registration software will be provided for registrations on the helpdesk in the fest. Central database server will be used for both offline and online registrations. Graphics will relate to the proposed theme that is SPACE.

2.) Events will be categorized into multiple categories as follows - Technical events: This category of events will contain the events which are related to technology, science or engineering or technical skills. Some technical events are Robo war Code combat Kaizen Prakshepan etc. Non-technical Events: This category of events will include the events which do not require technical skills but these are for fun and cultural activities. So we will sub categories into two these are: Performance events: These events are like some physical activities or performance. Some are as follows: Style check Band wars Zayka Bacchanalia the dancing event etc.

Fun/Cultural events: These events are for fun and some crazy events. Some are as follows: Rajneeti Art mania Motoracezz Clash of titans (chess game) etc.

Workshops: workshops, in the techfest are categorised separately. It contains workshops like Autonix, Robodroid and Metasploit. 3.) There will be three types of users of the Software-

Administrator - This type of user has power to update the database and authenticate users. Head of the events will be administrator. Coordinators This type of user will be able to register participants for the events. Participants This type of user will be able to register their self for the events online.1.4 Related work: Similar functions of the software can be seen on multiple websites. Some are:1.) http://www.apogee.org etc. Websites were developed previously. But online registrations were not there. Offline registration software was not introduced.

CHAPTER 2NOMENCLATURE & ABBRIVIATIONS

2. NOMENCLATURE

2.1 HTTP: HTTP governs the transfer of Hypertext (is a text uses by a standard system called HTML) between two or more computers based on client server architecture. It is a transaction oriented client/server protocol between web browser & web server.

2.2 HTML: Hypertext Markup Language used to create web document or web pages. FIG 2.1 : HTMLIn the right hand side of above figure, web pages of different following sites are shown: > http://www.yahoo.com > http://www.ibm.com > http://www.netscape.com > http://shareware.com

2.3 PHP: PHP is a server-side scripting language designed for web development but also used as a general-purpose programming language. PHP is now installed on more than 244 million websites and 2.1 million web servers. Originally created by Rasmus Lerdorf in 1995, the reference implementation of PHP is now produced by The PHP Group. While PHP originally stood for Personal Home Page, it now stands for PHP: Hypertext Pre-processor, a recursive acronym.PHP code is interpreted by a web server with a PHP processor module which generates the resulting web page: PHP commands can be embedded directly into an HTML source document rather than calling an external file to process data. It has also evolved to include a command-line interface capability and can be used in standalone graphical applications.PHP is free software released under the PHP License, which is incompatible with the GNU General Public License (GPL) due to restrictions on the usage of the term PHP. PHP can be deployed on most web servers and also as a standalone shell on almost every operating system and platform, free of charge. 2.4 MySQL: MySQL ("My S-Q-L", officially, but also called "My Sequel") is the world's most widely used open source relational database management system (RDBMS) that runs as a server providing multi-user access to a number of databases. It is named after co-founder Michael Widenius' daughter, my. The SQL phrase stands for Structured Query Language. The MySQL development project has made its source code available under the terms of the General Public License, as well as under a variety of proprietary agreements. MySQL was owned and sponsored by a single for-profit firm, the Swedish company MySQL AB, now owned by Oracle Corporation. MySQL is a popular choice of database for use in web applications, and is a central component of the widely used LAMP open source web application software stack (and other 'AMP' stacks). LAMP is an acronym for "Linux, Apache, MySQL, Perl/PHP/Python." Free-software-open source projects that require a full-featured database management system often use MySQL.2.5 Wamp 2.0: This web server application for php technology. Used in the market. And available with free user licence . It is most widely used server application.WAMPs are packages of independently created programs installed on computers that use a Microsoft Windows operating system.WAMP is an acronym formed from the initials of the operating system Microsoft Windows and the principal components of the package: Apache, MySQL and one of PHP, Perl or Python. Apache is a web server. MySQL is an open-source database. PHP, Perl and Python are scripting languages that can manipulate information held in a database and generate web pages dynamically each time content is requested by a browser. Other programs may also be included in a package, such as phpMyAdmin which provides a graphical user interface for the MySQL database manager.2.6 HTTPS: Secure Hypertext Transfer Protocol is a HTTP over SSL (secure socket layer).

2.7 TCP/IP: Transmission Control Protocol/Internet Protocol, the suite of communication protocols used to connect hosts on the Internet. TCP/IP uses several protocols, the two main ones being TCP and IP.

CHAPTER 3LITERATURE SURVEY

3. LITERATURE SURVEY3.1 GROWTH OF PROJECTLiteraturesurvey is the documentation of a comprehensive review of the published and unpublished work from secondary sources data in the areas of specific interest to the researcher. The library is a rich storage base for secondary data and researchers used to spend several weeks and sometimes months going through books, journals, newspapers, magazines, conference proceedings, doctoral dissertations, master's theses, government publications and financial reports to find information on their research topic.The researcher could start the literature survey even as the information from the unstructured and structured interviews is being gathered. Reviewing the literature on the topic area at this time helps the researcher to focus further interviews more meaningfully on certain aspects found to be important is the published studies even if these had not surfaced during the earlier questioning. So the literature survey is important for gathering the secondary data for the research which might be proved very helpful in the research. The literature survey can be conducted for several reasons. The literature review can be in any area of the business.

3.2 WORKING PROCESS OF PROJECT

The Techfest is a collaborative software to assist the participant to register in an interactive manner. It aims to reduce the paper work and benefit distant student. 3.2.1. How It Work: Firstly student traverse the whole website, and gathered the required information for various events like technical events and non technical events from EVENTS module.

If participant need any other details then he/she can get contact information from ABOUT US module.

Participant can know about workshop like who organizes the workshop, duration of workshop etc via WORKSHOP module.

Once Student done with traversing the website he can Register himself as a Participant.

Automated generated ID and password will sent to the students email-id. Using his Id and Password he can login for the registration of various events registration.

Particiant can make an online payment or he can book his seat and pay the fee in offline mode.

CHAPTER : 4PROJECT DISCRIPTION

4. PROJECT DESCRIPTION4.1 OBJECTIVE OF PROJECTTech Fest Registration System is a new online as well as offline registration concept which uses the client server application for online registration and Console application for the offline registration. It Include:1. The complete knowledge of each and every events like its totle no. of rounds, max. & min no. of participants, participation fees etc. 2. The interested participant can register himself by using online registration.3. An automated user-id and password will be sent to the email-id of participant.4. usng the unique user-id and password, participant can login to various events make the online payment using the secure gateway(here IDBI).As a new registration system, it has been developed fast in china, But I think the development progress is different form the western countries. Client Server Application for online registration. Console Application for offline registraion.

2.2 PROJECT MODULES It contains the following elements:- 1. Events It enables a participant to go through all types of evevts. It contain all the necessary information about each and every event.Technical Events: These are those events which are related to technology. These events include: Workshops, code combat, robobar etc. Non Technical Events: These events include the events which are related to performance such as: Zayaka, Rangoli, Rajniti etc.2. Registration: It enables a user to register themselves as a participant for the Techfest events . An automated user-id and password will be send to the users email id.3. Login: Participant view all the details related to all the events. The registered participant can login himself /herself in any events.4. Workshops: workshops, in the techfest are categorised separately. It contains workshops - Autonix Robodroid Metasploit5. About Us: It include all the necessary information regarding the university,college, co-ordinators contacts so that user can satisfy completely from his side if he/she has any doubt by callin or emailing the co-ordinator/mentor. 2.3 ADVANTAGES OF TECHFEST REGISTRATION Reduced overall cost is the single most influential factor in aTechfest registration. The elimination of costs associated with instructor's salaries, meeting room rentals, and travelling cost, lodging, and meals are directly quantifiable. The reduction of time spent away from the job by user may be the most positive offshoot. Increased retention and application form to the register averages an increase of 25 percent over traditional methods Consistent delivery of content is possible with asynchronous, self-paced registration. Proof of registration, is given by Unique User-id. Interactivity engages the user to understand the site only by seeing the graphics.

2.4 DISADVANTAGES OF TECHFEST REGISTRATION Up-front investment required of an Techfest solution is larger due to development costs and deployment cost. Budgets and cash flows will need to be negotiated. Technology issues that play a factor include whether the existing technology infrastructure can accomplish the training goals, whether additional tech expenditures can be justified, and whether compatibility of all software and hardware can be achieved.

CHAPTER 4SOFTWARE AND HARDWAREREQUIREMENTS

4.2 TECHNOLOGIES SOFTARWE AND HARDWARE REQUIREMENTS

4.1.1 ) Technologies:a) For website:* php* MySQL server* wamp 2.0* Dreamweaver* HTTP* HTTPS * TCP/IP

b) For console registration application:* java* MySQL server* JVM* Netbeans

4.4.2 INTERFACE:

a) For website: fig: The web pages (XHTML/JSP) are present to provide the user interface on client side. Communication between client user and server is provided through HTTP/HTTPS protocols. The Client software is to provide the user interface on the system user client side and for this TCO/IP protocols are used.

On the server side web server is for EJB and Database server is for storing the information.

4.1.3 ) Software Interface: a ) For website:* Operating System (Any like Linux, windows) * Client on Internet: Web Browser * Client on Intranet: Client Software, Web Browser * WebServer* MySQL * Development End: (php, HTML, javascript, css), MySQL, Web Server.

b ) For console application software:* Operating System (Any like Linux ,windows)* Java( JVM ) installed. * MySQL

* Development End: (java, Netbeans ), MySQL.

4.1.4) Hardware Interface:

Client Side:

* Mozilla Firefox (for best view). * Processor: Pentium II at 500 MHz * Ram: 64 MB Server Side:

* Wamp v2.0 * Processor: Pentium II at 500 MHz * Ram: 256 MB * Disk space: 1GB * MySQL server 5.0 * Processor: Pentium II at 500 MHz * Ram: 64 MB * Disk space: 1GB

4.1.5 ) Communication Interface: * Client on Internet will be using HTTP/HTTPS protocol * Client on Intranet will be using TCP/IP protocol.

CHAPTER 5SOFTWARE ENGINEERING PARADIGM

5. SOFTWARE ENGINEERING PARADIGM5.1 INTRODUCTIONTo solve actual problems in an industry setting, a software engineer or a team of engineers must co-operate a development strategy that encompasses the process, methods and tools layers and the generic phases. This strategy is often referred to as a process model or a software engineering paradigm.It is chosem based on the nature of the project and application, the method and tools to be used , and the controls and the deliverables that are required. All software development can be characterized as a problem solving loop in which four distinct stages are encountered: status quo, problem definition, technical development, technical development and solution integration.Status quo represents current state of the affairs; problem definition identifies the specific problem to be solved; technical development to be solved the problem through the application of some technology, and solution integration delivers the result to those who requested the solution in the first place. Regardless of the process model chosen , all of the stages coexist simultaneously at some level of the details. Various process model are as follows: The linear sequential model The prototype model The RAD model The incremental model The spiral model

5.2 PARADIGM USEDWATERFALL MODEL

In our project we have usedthe waterfall model. The waterfall model isa popularversion of the systems development life cyclemodel for software engineering. Often considered the classic approach to the systemsdevelopment life cycle, the waterfall model describes a development method that islinear and sequential. Waterfall development has distinct goals for each phase ofdevelopment. Imagine a waterfall on the cliff ofa steep mountain. Once the water hasflowed over the edge of the cliff and hasbegun its journey down the side of themountain, it cannot turnback. It is the samewith waterfall development. Once a phase of development is completed, the development proceeds to the next phase and there isno turningback. The advantage of waterfall development is that it allowsfor departmentalization and managerial control. A schedule can be setwith deadlines for each stage ofdevelopment and a product can proceed through the development process like acarin 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 ofdevelopment proceeds in strict order, without any overlapping or iterative steps. The disadvantage of waterfall development is that it doesnot allow for much Reflection and Revision.

CHAPTER 6SOFTWARE REQUIREMENT SPECIFICATION

6. SOFTWARE REQUIREMENT SPECIFICATION6.1 OVERVIEW & SUMMARYRequirement analysis is the first technical step in the software process. It is at this point that a general statement of software scope is refined into a concrete specification that becomes the foundation for all software engineering activities that follow. Analysis must focus on the information, functional and behavioral domain of a problem. To better understand what is required, modes are created, the problem is partitioned and representations that depict the essence of requirement and, later, implementation details are developed.The introduction of the software requirement specification states the goal and objectives of the software describing it in the context of the computer based system. The information description provides a detail description of the problem that the software must solve. Information, flow and structure are documented. Hardware , software and human interfaces are described for external system elements and internal software functions.A description of each function required to solve the problem is presented in the functional description. A processing narratives is provided for each function, design constraints are sated and justified , performance characteristics are stated and one or more diagrams are included to graphically represent the overall structure of the software and interplay among software function and other system elements. The behavioral description section of the specification examines the operation of the software as a consequence of external events and internally generated control characteristics. Validation criteria are the most important section of SRS. Specification of validation criteria acts as an implicit review of all other requirements.SRS include a bibliography and appendix. In many cases SRS may be accompanied by an executable prototype or a preliminary users manual.

6.2 DATABASE SUMMARYTable NameSchemaDescription

personalinfokronos13Personal information about registerUsers of the website.

paymentinfokronos13Payment information of the online registration process.

eventskronos13Information about events their fees, member limit in the event.

eventinfokronos13Information about the users who have registered for events.

adminsdesk_regUser name and password of the administrator of the window application.

coordinatorsdesk_regInformation about the authenticatedusers of the offline software.

Participates_singledesk_regPersonal information about the participants of the events.

singleevntdesk_regParticipation information in the events in which team size is single.

grpevntprticptdesk_regParticipation information in the events in which team size is more than one.

Table 6.2.1: Admin Table Field namedata type Description

Name VarcharIt is the user id for the admin .it is the primary key of the table.

Password Varchar

This contain the password related to the name.

Field nameData type Description

Name varcharIt contain the name of the coordinator.

Password varcharIt contain the password related to the user.

Created by varcharThis field contain ,through which admin id ,this coordinator id is created.

Clgvarchar This field contain the college name of related user.

Branch

varcharBranch of the coordinator.

Amount varcharTotal amount earned by this coordinator.

MbradedInt Total registration is done by this coordinator.

Table 6.2.2: Coordinator Table :-

Table 6.2.3: Single user Field name data typeDescription

Team id varcharIt contains the unique id of the group. It is the primary key for the table.

GrpnamesvarcharThis contains the name related to the team id.

Mobileno.varcharIt contains the mobile no of the user.

noofmembersInt Total no of member in a group.

Email varcharEmail id of one user from the group.

Date

Date It contains the date of registration.

Event namevarcharIt contains the name of related event which is register by the coordinator.

Amount Int Total amount related to the group event.

Added by varcharThis contains the information of

Table 6.2.4: singleeventField name Data type Description

Id varcharThis is the primary key for the single participant table.

Password

varcharThis field contains the password related to the user id.

Email

varcharContains the email id of related user.

Clg

varcharCollege information

Mobile no.

varcharContains the Mobile no of the user.

City

varcharContains the city information of the user.

Date Date Date of registration.

Added by varcharContains the information of coordinator which register the user.

Totalamt Int Contains the information of total amount of related event in which user registered.

Noofevnt Int Total no of event of a single user.

Field name Data typeDescription

Id Varchar This is the primary key for this table .

Event name Varchar Contains the event name related to particular id.

Table 5: Event info-Field name Data type Description

U_idVarchar This is the primary key for this table,it contains the user id.

E_nameVarcharName of event in which participant has taken part.

Grp_idVarcharContains the id of the particular group.

No_memberInt Total no of member in a group

Acceptance Tinyint This field contains the information any event in two way, if 0 means not accepted or 1 means accepted .

Pay type VarcharThis field contains the information of pay mode either online or offline.

Date Date Information of date of registration.

Table 6.2.6: Event Field nameData type Description

E_noInt This the primary key .which contains the information of event no.

E_nameVarcharThis contains the name of related event.

E_feesInt This field contains the fees information of related event.

Max_memberInt Max member in particular group

E_date

Date Date of registration

E_typeVarcharContains the information of particular type of the event either technical or nontechnical

Min_memberInt Min member in a particular group.

Table 6.2.7:Paymentinfo-Field name Data type Description

U_id VarcharThis the primary key for this table ,contains the user id.

Amount IntAmount info of particular event.

Payment_flagTinyint

Payment _typeVarcharPayment type eiher online or off line.

E_nameVarcharName of the particular event.

Field nameData type Description

S_noIntSerial number.

NameVarcharName of the participants.

E_mailVarcharEmail id of the participant.

BranchVarcharStream of the participant.

ClgVarcharCollege name of the participant in which he/she is

PhoneVarchar

No_event

Int

CityVarchar

StateVarchar

DateregistrationDate

PwdVarchar

U_idVarchar

6.3 FUNCTIONAL REQUIREMENTThe functional requirement of the project is defined under two modules. The first module allows the system Administrator(admin) to log into his account and has the privileges to do multiple things some of the include, manage user info, manage daily Database, manage Website, Update payment status . The second module of the project defines itself in terms of being used by the Registered user; User have to enter their user-id and password which automatically send to his email-id by an aumated system. After that the id is verified and they can pursue the facilities provide to the student like view all information, register for any event, online payment .The Third module of the project defines itself in terms of being used by Native User. They can traverse whole website , view all information about events and register theirselves.Functional requirements are listed in the following sections as use cases for the instructor and student actors separately.

6.3.1 ADMINISTRATOR USE

Manage user information Manage daily database Manage website Update payment status.

6.3.2 STUDENT/PARTICIPANT USE Traverse the whole website Get himself /herself register View information about all the events Register for events. Online payment

CHAPTER 7TOOLS AND TECHNOLOGIES USED

7. TOOLS AND TECHNOLOGIES USED7.1 JAVAJava is a programming language originally developed by James Gosling at Sun Microsystems and released in 1995 as a core component of Sun Microsystems' Java platform. The language derives much of its syntax from C and C++ but has a simpler object model and fewer low-level facilities. Java applications are typically compiled to byte code that can run on any Java virtual machine (JVM) regardless of computer architecture.The original and reference implementation Java compilers, virtual machines, and class libraries were developed by Sun from 1995. As of May 2007, in compliance with the specifications of the Java Community Process, Sun made available most of their Java technologies as free software under the GNU General Public License. Others have also developed alternative implementations of these Sun technologies, such as the GNU Compiler for Java and GNU Class path. PRIMARY GOALSThere were five primary goals in the creation of the Java language: It should be "simple, object-oriented, and familiar". It should be "robust and secure". It should be "architecture neutral and portable". It should execute with "high performance". It should be "interpreted, threaded, and dynamic". 7.1.1 JAVA LIBRARIESJava libraries are the compiled bytecodes of source code developed by the JRE implemention to support application development in Java. Examples of these libraries are: The core libraries, which include: Collection libraries that implement data structures such as lists, dictionaries, trees, sets, queues and double-ended queue, or stacks XML Processing (Parsing, Transforming, Validating) libraries Security Internationalization and localization libraries. The integration libraries, which allow the application writer to communicate with external systems. These libraries include: The Java Database Connectivity (JDBC) API for database access. Java Naming and Directory Interface (JNDI) for lookup and discovery RMI.7.1.2 JAVA SWINGSwingis the primaryJavaGUIwidget toolkit. It is part ofOracle'sJava Foundation Classes(JFC) anAPIfor providing a graphical user interface(GUI) for Java programs.Swing was developed to provide a more sophisticated set of GUIcomponentsthan the earlierAbstract Window Toolkit (AWT). Swing provides a nativelook and feelthat emulates the look and feel of several platforms, and also supports apluggable look and feelthat allows applications to have a look and feel unrelated to the underlying platform. It has more powerful and flexible components than AWT. In addition to familiar components such as buttons, check box and labels, Swing provides several advanced components such as tabbed panel, scroll panes, trees, tables and lists.Unlike AWT components, Swing components are not implemented by platform-specific code. Instead they are written entirely in Java and therefore are platform- -independent. The term "lightweight" is used to describe such an element.The Swing toolkit includes a rich set of components for building GUIs and adding interactivity to Java applications. Swing includes all the components you would expect from a modern toolkit: table controls, list controls, tree controls, buttons, and labels.Swing is far from a simple component toolkit, however. It includes rich undo support, a highly customizable text package, integrated internationalization and accessibility support. To truly leverage the cross-platform capabilities of the Java platform, Swing supports numerous look and feels, including the ability to create your own look and feel. The ability to create a custom look and feel is made easier with Synth, a look and feel specifically designed to be customized. Swing wouldn't be a component toolkit without the basic user interface primitives such as drag and drop, event handling, customizable painting, and window management.Swing is part of the Java Foundation Classes (JFC). The JFC also include other features important to a GUI program, such as the ability to add rich graphics functionality and the ability to create a program that can work in different languages and by users with different input devices.

7.1.3 JAVA DATABASE CONNECTIVITY (JDBC)It has been estimated that half of all software development involves client/server operations. A great promise of Java has been the ability to build platform-independent client/server database applications. In Java 1.2 this has come to fruition with Java DataBase Connectivity (JDBC).There is a standard database language, Structured Query Language (SQL-92). JDBC is designed to be platform-independent, so doesnt need to worry about the database while programming. JDBC, like many of the APIs in Java, calls to the logical operations when gathering data from a database: connect to the database, create a statement and execute the query, and look at the result set.To allow this platform independence, JDBC provides a driver manager that dynamically maintains all the driver objects that were database queries will need.The driver objects register themselves with the driver manager at the time of loading, and we can force the loading using Class.forName( ).To open a database, we must create a database URL that specifies:That were using JDBC with jdbc The sub protocol: the name of the driver or the name of a database connectivity mechanism. Since the design of JDBC was inspired by ODBC, the first sub protocol available is the jdbc-odbc bridge, specified by odbc The database identifier. This varies with the database driver used, but it generally provides a logical name that is mapped by the database administration software to a physical directory where the database tables are located. For our database identifier to have any meaning, we must register the name using our database administration software. (The process of registration varies from platform to platform.)All this information is combined into one string, the database URL. For example, to connect through the ODBC sub protocol to a database identified as people, the database URL could be:String dbUrl = "jdbc:odbc:news";When were ready to connect to the database, we call the static method DriverManager.getConnection( ), passing it the database URL, the user name, and a password to get into the database. We get back a Connection object that we can then use to query and manipulate the database.Once the connection is made with DriverManager.getConnection( ), we can use the resulting Connection object to create a Statement object using the createStatement( ) method. With the resulting Statement, we can call executeQuery( ), passing in a string containing an SQL-92 standard SQL statement.The executeQuery( ) method returns a ResultSet object, which is quite a bit like an iterator: the next( ) method moves the iterator to the next record in the statement, or returns false if the end of the result set has been reached. Well always get a ResultSet object back from executeQuery( ) even if a query results in an empty set (that is, an exception is not thrown). Note that we must call next( ) once before trying to read any record data. If the result set is empty, this first call to next( ) will return false. For each record in the result set, we can select the fields using (among other approaches) the field name as a string. Also note that the capitalization of the field name is ignored it doesnt matter with an SQL database. We determine the type well get back by calling getInt( ), getString( ), getFloat( ), etc. At this point, weve got our database data in Java native format and can do whatever we want with it using ordinary Java code.

Java Application

JDBC-ODBC Bridge

ODBC DriverSQL CommandResult Set

DATABASE

Proprietary protocol7.2 MYSQL (BACK END):-MySQL ("My S-Q-L", officially, but also called "My Sequel") is the world's most widely used open source relational database management system (RDBMS) that runs as a server providing multi-user access to a number of databases. It is named after co-founder Michael Widenius' daughter, my. The SQL phrase stands for Structured Query Language. The MySQL development project has made its source code available under the terms of the General Public License, as well as under a variety of proprietary agreements. MySQL was owned and sponsored by a single for-profit firm, the Swedish company MySQL AB, now owned by Oracle Corporation. MySQL is a popular choice of database for use in web applications, and is a central component of the widely used LAMP open source web application software stack (and other 'AMP' stacks). LAMP is an acronym for "Linux, Apache, MySQL, Perl/PHP/Python." Free-software-open source projects that require a full-featured database management system often use MySQL.

CHAPTER 8DESIGN AND DEPLOYMENT

8. Design and Development8.1 Design of projectGUI 1: Main provides the basic navigation access to the user allowing him to choose his login type as Administrator, Faculty or Student.GUI 2: Based on the users selection on the first screen he is navigated to the other screen on the basis of selection he/she made. GUI 3: This screen is the users main work area from the navigation menu the user selects for the operation to be performed and is taken to the respective domain of the project8.2 ARCHITECTURE DIAGRAM:-

8.3 Use Case Diagram:-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 (represented as use cases), 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.Use Case diagrams are formally included in two modeling languages defined by the OMG: the Unified Modeling Language (UML) and the Systems Modeling Language (SysML).USE CASE DIAGRAM:-Use case model :- For web-application:

Administrator User: This type of user will supervise the registration process and information given on the website and software.

There are following use cases of the administrative user:1. Manage user information: Administrator will have the authority to access and manage users information.2. Manage Daily Database: Administrator can have daily updated information of the database like no of registration, no of registration in particular event etc.3. Manage website: Administrator will have the responsibility to maintain the website.4. Update the payment status: As we know that we have two payment modes. First is pay online and second is pay later. In the database we have put an attribute acceptance for this problem; it will work as a flag for the payment. So if a user registers him in any event with the option pay later and after that the person comes to the organizers and submits the fees. Then administrator will update his/her payment status and an acceptance mail will be sent to the user automatically.

Registered user: This type of user is registered on our website means we have information about this user in our database. There are following use cases of the registered user:1. Register in different events: There are several events in the fest he register himself for different events in the fest.2. View all information: This type of user can traverse the whole website and see whole information about the events in the techfest. Native user: This type of user can traverse the whole website and see information given on the website.He can also register himself on the website.

Use Case ModalFor Console Appliction

8.4 Data Flow Diagram:- A data flow diagram (DFD) is a graphical representation of the "flow" of data through an information system. It differs from the system flowchart as it shows the flow of data through processes instead of hardware.The DFD a way of expressing the system in a graphical format in a modular design was developed by Larry Constrains. This DFD is also known as Bubble Chart has the purpose to classify the system requirement and to identify the major information that will be a program in system design.A Data Flow Diagram is logical model of the system and shows the flow of the data and the flow of logic so this all thing describes what takes place in a proposed system, not how the activities are accomplished. We have noted that the DFD describes what the flow is rather then how they are processed, so it means the DFD doesnt depend on the hardware, software, data structure or file organization.DFD consist of a series of symbols joined together by a line. There may be a single DFD for the entire system or it may be exploded into various levels.1.Context Free Diagram2.First Level DFD3.Second Level DFD

Data Flow Diagram

0-level DFD:

LOGIN PROCESS1-level DFD:

AdminSTUDENTCo-ordinator

2-level DFD:

TechFest PORTAL

REGISTER

DATABASEMANAGE WEBSITEMANAGE USER INFOMAKE PAYMENTGET REGISTERPARTICIPANTADMINISTRATORMATCHEDCo-ordinatorADMINISTRATORRETRYLOGIN

STUDENT

TRAVERSE WEBSITEMANAGE DAILY INFOUPDATE PAYMENT STATUS

8.5 Entity Relationship Diagram:- An entity-relationship diagram is a data modeling technique that creates a graphical representation of the entities, and the relationships between entities, within an information system.The three main components of an ERD are: The entity is a person, object, place or event for which data is collected. For example, if you consider the information system for a business, entities would include not only customers, but the customer's address, and orders as well. The entity is represented by a rectangle and labeled with a singular noun.

The relationship is the interaction between the entities. In the example above, the customer places an order, so the word "places" defines the relationship between that instance of a customer and the order or orders that they place. A relationship may be represented by a diamond shape, or more simply, by the line connecting the entities. In either case, verbs are used to label the relationships.

The cardinality defines the relationship between the entities in terms of numbers. An entity may be optional: for example, a sales rep could have no customers or could have one or many customers; or mandatory The steps involved in creating an ERD are: Identify the entities. Determine all significant interactions. Analyze the nature of the interactions. Entity Relationship Diagram NotationsPeter Chen developed ERDs in 1976. Since then Charles Bachman and James Martin have added some slight refinements to the basic ERD principles.EntityAn entity is an object or concept about which you want to store information.

Weak EntityAttributes are the properties or characteristics of an entity.

Key attributeA key attribute is the unique, distinguishing characteristic of the entity. For example, an employee's social security number might be the employee's key attribute

Multivalued attributeA multivalued attribute can have more than one value. For example, an employee entity can have multiple skill values.

RelationshipsRelationships illustrate how two entities share information in the database structure.

E-R DIAGRAM:

CHAPTER 9SNAPSHOT PORTAL

CHAPTER-10

USER MANUAL & TESTING

10. User Manual:10.1. User Manual:Step1-Install Java, text pad, MYSQL, wamp 2.0 in the system.Step2-Copy all the programs to folder into c drive and add their path with in envieonment variables Step3-Compile all the programs in text pad.Step4-Now open command prompt.Step5-Write cd\rmi press enter, rmic AddServerImpl press enter, then rmiregistry press enter.Step-6 Now Run AddServer Program.Step-7 Now Run frontpage program.Step6-The home page will be displayed. Click to enter any of the two zones(student , Administrator)Step7-In the particular zone , give user id and password ,you will be loginStep8-Once you are login successfully , perform all the features included in it .Step9-After doing your work, click on logout.Step10-you will successfully logout from the project.

10.2 TESTING

10.2.1 PREPARATION FOR TEST DATAWe face various challenges inherent to testing remote applications, ranging from practical limitations, to tedious, mundane tasks, to understanding what factors and issues affect the results of our testing. Trying to test using all possible devices is impractical. Trying to multiply that testing across the rest of the factors exacerbates the problems, e.g. network operator, different versions of the underlying software, etcSome factors that could affect the test results may be outside our direct control. They may hard to even identify and therefore even harder to measure. When we do test, accurate test data may be hard to obtain, and there are numerous gaps and contradictions in the data we have which we need to sift through to determine the key issues and their likely impact.Measuring performance of remote applications is an imperfect art, and particularly error-prone when trying to obtain consistent, accurate results.

10.2.2 OUR TESTING FOCUS-

Given the vast problem space, and our typically severely constrained resources, we need to focus our testing if we are to be effective. When automation is used appropriately we can be significantly more effective and reduce the overall time needed to test each software release. Some types of applications can be automated relatively easily and successfully, others are more challenging e.g. client applications. Finally some aspects are better tested manually e.g. to assess the rendering of the UI on actual devices. For applications that run on a range of devices, where there are lots of variations between devices and where upgrades can be expensive or difficult, we first want to focus on finding and addressing problems that would prevent users from being able to use the application on their device. These problems include: Finding incompatibilities ranging from not installing, to poor rendering, Discovering and working around limitations in the software on the device, including browser issues, etc. Detecting content or behavior that may adversely affect the behavior of the device. Once we've tested for these issues the next step is determining whether users get the most technically suitable content for their device. For all our applications we want our users to like using them. After all, unless we have a monopoly e.g. for internal company applications, then our users have plenty of alternatives available. Here we focus on: Usability, the wow factor, etc. Performance, which is an umbrella term that includes: a users perception of responsiveness, client-side rendering, over-the-air transmission times, and server-side timings.Test design helps us to increase the effectiveness of each test, and the test coverage, without testing every possible permutation! Thankfully, we can adopt existing techniques and good practices from elsewhere in the software testing communities. For example we can use combination testing techniques select our test cases and use exploratory testing techniques to help guide our testing.

10.2.3 OUR GOALS WHEN TESTING

Testing our software is a 'means to an end' part of the journey rather than the ultimate goal. However, if we have clear, measurable goals then we can keep track of how well we're doing and whether our testing is useful for the applications we're testing. Here are some of the goals I've used over the years to help you identify goals that suit you and your work. To ensure we deliver attractive, easy-to-use, working applications for as many users as practical. Lots of happy, frequent users help show our software is successful and useful. To have justified confidence in the quality of our software. Providing accurate information on the quality of software is an important aspect of software testing. When we test well, and communicate the results so other people understand the strengths, weaknesses, risks, etc. with releasing our application, there should be few surprises after deploying the software to our users. Ideally, most of the bugs would be found and fixed before the software is widely used. Fast feedback to developers. Fast feedback helps them to fix the code while it's still 'warm', while they are still intimately familiar with it. To quickly detect issues so they can be addressed. This is particularly relevant when the problem is related to external factors e.g. an operators network configuration, or a specific handset model. Note: we tend to make changes to our software as thats the fastest way to fix the issue from the users perspective. We can then work with the relevant third parties to address the underlying issues in a more considered fashion.

CHAPTER 11CONCLUSION

11. CONCLUSION11.1 CONCLUSION

We are here conclude that our project is in two part 1. Online 2. Offline Both are running successfully. Through Web site we can easily register in any technical on non technical event smoothly and through off line project which is a consol application ,registration are done very easily and smoothly. Almost 2000 registration are done through these application . there is also a appreciation mail for over website and the console application received by the HACK PLANET pvt. limited.

BIBLIOGRAPHY

We convey a special thanks to our department and to our college. We also convey a special thanks to all these softwares and websites, they have been helping a lot in doing the project.

BOOKS AND MANUALS:-

1. JAVA-2 Mastering Java2

Author : John Zukowski Publisher : BPB Publications Complete Reference: Java

2. System Analysis & Designing

Author : James A. senn Publisher : Tata McGraw Hill

3. Software Engineering Concepts

Author : Fairley Publisher : Tata McGraw Hill Publication,3rd Edition.

4. Software Engineering Principles

Author : Roger.S. Pressman

Web Reference:-

urls : http://www.xml.org / http://www.java.sun.com/jdk141/doc.html http://www.xmldb.com/resources/paper.html http://www.apache.org/xerces.html http://www.w3c.org http://www.w3schools.com http://www.wikipedia.org http://www.google.com http://www.answers.com http://www.google.com/images http:// www.campus-technology.com/article.asp?id=11046 E-book of ROGER S PRESSMAN http://yahooanswers.com

PROFILE OF GROUP MEMBERS

RAGHVENDRA CHOUBEYRoll No. 0915CS091063Mob. - 8982561668Email -choubey.raghvendra@gmail.com

Siddhartha SahuRoll No. 0915CS091084Mob. - 9039148299Email sid.9022@gmail.com

Ankita KhareRoll No. 0915CS091014Mob. 9039419146Email- ankita.khare27@gmail.com

[2]