venkateswaran2010,9976316089,m.venkateswaran,m.venkates[Voting system1 ragu]
Upcoming SlideShare
Loading in...5

Like this? Share it with your network


venkateswaran2010,9976316089,m.venkateswaran,m.venkates[Voting system1 ragu]







Total Views
Views on SlideShare
Embed Views



0 Embeds 0

No embeds


Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
Post Comment
Edit your comment

venkateswaran2010,9976316089,m.venkateswaran,m.venkates[Voting system1 ragu] Document Transcript

  • 1. CHAPTER I 1. INTRODUCTION 1.1 OVERVIEW OF THE PROJECT The “VOTE PLUS” software is based on an election activity for each student voting for a particular candidate he wishes to. Each student will be given a unique username and password. As soon as he logins by entering his username and password, a menu form will be shown with its first option as candidate list where all the candidates’ information standing for the election will be shown. Next procedure is the voting section where the user can vote for any candidate he wishes to. There are 3 categories in the candidate post i.e., President, Secretary, Joint Secretary. The user can vote to any 1 from these 3 categories. The system will not provide the user to vote for more than 1 candidate in each category. This completes the voting procedure. All the data’s are being stored in the database. Admin has his own username and password. Admin Provides username and password for other user’s .He also has the right to insert candidate’s name. And he also has the right to edit and delete those details to/from the list. The result will be shown. Only admin has the authority to see the results. 1
  • 2. 1.2 ORGANIZATION PROFILE The School was started in 28th of October 2001 by Dr.Kausalya Murugaiyan Educational Trust, Pollachi with an objective of providing quality education. The Foundation stone was laid by Dr.B.K.Krishnaraj Vanarayar in the year 2001 and the school was opened by Dr.N.Mahalingam in the year 2002. It is a co-educational school with strength of 720 students and more than 40 teachers, with separate hostel for boys and girls. Van facilities are available for local students. The institution is situated just 6 kilometers from the Pollachi town, on the Pollachi-Coimbatore main road. It is located in a serene pollution-free atmosphere in an area of 3.6 acres. Pure natural drinking water is available from Aliar. The school is under the care of a family of doctors. Dr.S.Murugaiyan MBBS FCGP is the Managing Trustee, Dr.V.Anand MS DLO is the Secretary, and Dr.Shanthi Anand MD DGO is the Correspondent. The hostel is under the direct supervision of the school principal Mr.F.Pratap Vimalesh B.Sc., M.A., M.Ed. Dr.Kausalya Murugaiyan (7.10.1933 - 1.12.2007) an able Doctor of Medicine with vast experience was directly involved in school activities from the beginning. The day she passed away, she attended the school annual day and was talking to parents & children. The school remembers her affection Inter school drawing competitions are also conducted in her memory once in a year in which students from various schools in and around Pollachi eagerly participate and win prizes or receive participation certificates. The winning school gets the Rolling Trophy. Address: Bharath Vidya Niketan Kovai Road Achipatti, Pollachi 2
  • 3. CHAPTER II 2. SYSTEM ANALYSIS It is important to evaluate the system’s components in relationship to one another, to determine how requirements fit into the system. So the system analysis is concerned with getting user requirements, analyzing it, designing and implementing it. After the requirements collection, the information have subjected to ambiguity, omissions and requirement consistency. Is the requirement collected from the concern are consistent with overall objective of the system, i.e. outline of inputs from and inputs to the system matched with proposed one. Feasibility analysis  Existing system  Drawbacks of existing system  Proposed system  Advantages of proposed system 3
  • 4. 2.1 EXISTING SYSTEM The voting system currently being used by the University’s student union is a paper based system, in which the voter simply picks up ballots sheets from electoral officials, tick off who they would like to vote for, and then cast their votes by merely handing over the ballot sheet back to electoral official. The electoral officials gather all the votes being cast into a ballot box. At the end of the elections, the electoral officials converge and count the votes cast for each candidate and determine the winner of each election category. Drawback of Existing System The current system in use today, has a number of problems my proposed system would aim to correct. The system is highly insecure and prone to election malpractice. Because any student can come and fill out a ballot sheet without prior authentication to determine who he/she says they are, is a major concern. The administration of the voting system as a whole is highly inefficient, slow and time consuming, and is highly prone to human error 4
  • 5. 2.2 PROPOSED SYSTEM The proposed system will have many advantages over the existing system. This system is also based on the storage but it will overcome all the existing problems. Cost efficiency of the system also seems to be good because the system is very fast in making the transaction. Advantage of proposed system  To build an online system this would enable voters to cast their votes on chosen candidates.  Create a secure authentication facility to check validate users logging into the voting system  Create a database to be used to stored votes, and user information on the system  Study and implement a security method to be used to ensure that votes being cast in the system will not be compromised and any outside attack  Enable the system to tally votes cast according to candidate voted for.  Create a backend administration section which will be used to enable the administration manage the election system effectively  Create tools for the administrator to add, delete and update details of voters, candidates and sub administrators on the system  Display voting results in a graphical fashion for the administer to analyze  To enable voters to cast their votes for their chosen candidates  Enable voters to view biographies of the candidates being voted for in the election  Timestamp votes cast to the database to know when each vote was cast  Enable administrators to generate reports on the vote results  Prevent voters from voting more than once for their choose candidates 5
  • 6. CHAPTER III 3. SYSTEM SPECIFICATION 3.1 HARDWARE SPECIFICATION Processor : PENTIUM IV Speed : 2.4 GHZ RAM : 512 MB Hard Disk Drive : 80 GB Monitor : SAMSUNG 17’Inch Color Keyboard : LOGITECH 108 Keyboards Mouse : LOGITECH Scroll Mouse 3.2 SOFTWARE SPECIFICATION Operating System : Windows XP (Service pack2) Front end : VB.Net 2008 Back end : SQL Server2005 6
  • 7. 3.3 ABOUT THE SOFTWARE OVERVIEW ABOUT VISUAL BASIC.NET Microsoft.NET Framework The .NET Framework is a new computing platform that simplifies application development in the highly distributed environment of the Internet. The .NET Framework is designed to fulfill the following objectives:  To provide a consistent object-oriented programming environment whether object code is stored and executed locally, executed locally but Internet-distributed, or executed remotely.  To provide a code-execution environment that minimizes software deployment and versioning conflicts.  To provide a code-execution environment that guarantees safe execution of code, including code created by an unknown or semi-trusted third party.  To provide a code-execution environment that eliminates the performance problems of scripted or interpreted environments.  To make the developer experience consistent across widely varying types of applications, such as Windows-based applications and Web-based applications.  To build all communication on industry standards to ensure that code based on the .NET Framework can integrate with any other code. The .NET Framework has two main components: the common language runtime and the .NET Framework class library. The common language runtime is the foundation of the .NET Framework. You can think of the runtime as an agent that manages code at execution time, providing core services such as memory management, thread management, and remoting, while also enforcing strict type safety and other forms of code accuracy that ensure security and robustness. In fact, the concept of code management is a fundamental principle of the runtime. Code that targets the runtime is known as managed code, while code that does not target the runtime is known as unmanaged code. The class library, the other main component of the .NET Framework, is 7
  • 8. a comprehensive, object-oriented collection of reusable types that you can use to develop applications ranging from traditional command-line or graphical user interface (GUI) applications to applications based on the latest innovations provided by ASP.NET, such as Web Forms and XML Web services. The .NET Framework can be hosted by unmanaged components that load the common language runtime into their processes and initiate the execution of managed code, thereby creating a software environment that can exploit both managed and unmanaged features. The .NET Framework not only provides several runtime hosts, but also supports the development of third-party runtime hosts. For example, ASP.NET hosts the runtime to provide a scalable, server-side environment for managed code. ASP.NET works directly with the runtime to enable Web Forms applications and XML Web services, both of which are discussed later in this topic. Internet Explorer is an example of an unmanaged application that hosts the runtime (in the form of a MIME type extension). Using Internet Explorer to host the runtime enables you to embed managed components or Windows Forms controls in HTML documents. Hosting the runtime in this way makes managed mobile code (similar to Microsoft® ActiveX® controls) possible, but with significant improvements that only managed code can offer, such as semi-trusted execution and secure isolated file storage. The following illustration shows the relationship of the common language runtime and the class library to your applications and to the overall system. The illustration also shows how managed code operates within a larger architecture. Features of the Common Language Runtime The common language runtime manages memory, thread execution, code execution, code safety verification, compilation, and other system services. These features are intrinsic to the managed code that runs on the common language runtime. 8
  • 9. With regards to security, managed components are awarded varying degrees of trust, depending on a number of factors that include their origin (such as the Internet, enterprise network, or local computer). This means that a managed component might or might not be able to perform file-access operations, registry-access operations, or other sensitive functions, even if it is being used in the same active application. The runtime enforces code access security. For example, users can trust that an executable embedded in a Web page can play an animation on screen or sing a song, but cannot access their personal data, file system, or network. The security features of the runtime thus enable legitimate Internet-deployed software to be exceptionally feature rich. The runtime also enforces code robustness by implementing a strict type- and code-verification infrastructure called the common type system (CTS). The CTS ensures that all managed code is self-describing. The various Microsoft and third-party language compilers Generate managed code that conforms to the CTS. This means that managed code can consume other managed types and instances, while strictly enforcing type fidelity and type safety. In addition, the managed environment of the runtime eliminates many common software issues. For example, the runtime automatically handles object layout and manages references to objects, releasing them when they are no longer being used. This automatic memory management resolves the two most common application errors, memory leaks and invalid memory references. The runtime also accelerates developer productivity. For example, programmers can write applications in their development language of choice, yet take full advantage of the runtime, the class library, and components written in other languages by other developers. Any compiler vendor who chooses to target the runtime can do so. Language compilers that target the .NET Framework make the features of the .NET Framework 9
  • 10. available to existing code written in that language, greatly easing the migration process for existing applications. While the runtime is designed for the software of the future, it also supports software of today and yesterday. Interoperability between managed and unmanaged code enables developers to continue to use necessary COM components and DLLs. The runtime is designed to enhance performance. Although the common language runtime provides many standard runtime services, managed code is never interpreted. A feature called just-in-time (JIT) compiling enables all managed code to run in the native machine language of the system on which it is executing. Meanwhile, the memory manager removes the possibilities of fragmented memory and increases memory localityof-reference to further increase performance. Finally, the runtime can be hosted by highperformance, server-side applications, such as Microsoft® SQL Server™ and Internet Information Services (IIS). This infrastructure enables you to use managed code to write your business logic, while still enjoying the superior performance of the industry's best enterprise servers that support runtime hosting. .NET Framework Class Library The .NET Framework class library is a collection of reusable types that tightly integrate with the common language runtime. The class library is object oriented, providing types from which your own managed code can derive functionality. This not only makes the .NET Framework types easy to use, but also reduces the time associated with learning new features of the .NET Framework. In addition, third-party components can integrate seamlessly with classes in the .NET Framework. For example, the .NET Framework collection classes implement a set of interfaces that you can use to develop your own collection classes. Your collection classes will blend seamlessly with the classes in the .NET Framework. As you would expect from an object-oriented class library, the .NET Framework types enable you to accomplish a range of common programming tasks, including tasks such as string management, data collection, database connectivity, and file access. In 10
  • 11. addition to these common tasks, the class library includes types that support a variety of specialized development scenarios. For example, you can use the .NET Framework to develop the following types of applications and services:  Console applications.  Scripted or hosted applications.  Windows GUI applications (Windows Forms).  ASP.NET applications.  XML Web services.  Windows services. For example, the Windows Forms classes are a comprehensive set of reusable types that vastly simplify Windows GUI development. If you write an ASP.NET Web Form application, you can use the Web Forms classes. Client Application Development Client applications are the closest to a traditional style of application in Windowsbased programming. These are the types of applications that display windows or forms on the desktop, enabling a user to perform a task. Client applications include applications such as word processors and spreadsheets, as well as custom business applications such as data-entry tools, reporting tools, and so on. Client applications usually employ windows, menus, buttons, and other GUI elements, and they likely access local resources such as the file system and peripherals such as printers. Another kind of client application is the traditional ActiveX control (now replaced by the managed Windows Forms control) deployed over the Internet as a Web page. This application is much like other client applications: it is executed natively, has access to local resources, and includes graphical elements. In the past, developers created such applications using C/C++ in conjunction with the Microsoft Foundation Classes (MFC) or with a rapid application development (RAD) environment such as Microsoft® Visual Basic®. The .NET Framework incorporates 11
  • 12. aspects of these existing products into a single, consistent development environment that drastically simplifies the development of client applications. The Windows Forms classes contained in the .NET Framework are designed to be used for GUI development. You can easily create command windows, buttons, menus, toolbars, and other screen elements with the flexibility necessary to accommodate shifting business needs. For example, the .NET Framework provides simple properties to adjust visual attributes associated with forms. In some cases the underlying operating system does not support changing these attributes directly, and in these cases the .NET Framework automatically recreates the forms. This is one of many ways in which the .NET Framework integrates the developer interface, making coding simpler and more consistent. Unlike ActiveX controls, Windows Forms controls have semi-trusted access to a user's computer. This means that binary or natively executing code can access some of the resources on the user's system (such as GUI elements and limited file access) without being able to access or compromise other resources. Because of code access security, many applications that once needed to be installed on a user's system can now be safely deployed through the Web. Your applications can implement the features of a local application while being deployed like a Web page. VB.NET ACTIVE X DATA OBJECTS.NET ADO.NET Overview ADO.NET is an evolution of the ADO data access model that directly addresses user requirements for developing scalable applications. It was designed specifically for the web with scalability, statelessness, and XML in mind. 12
  • 13. ADO.NET uses some ADO objects, such as the Connection and Command objects, and also introduces new objects. Key new ADO.NET objects include the DataSet, DataReader, and DataAdapter. The important distinction between this evolved stage of ADO.NET and previous data architectures is that there exists an object -- the DataSet -- that is separate and distinct from any data stores. Because of that, the DataSet functions as a standalone entity. You can think of the DataSet as an always disconnected recordset that knows nothing about the source or destination of the data it contains. Inside a DataSet, much like in a database, there are tables, columns, relationships, constraints, views, and so forth. A DataAdapter is the object that connects to the database to fill the DataSet. Then, it connects back to the database to update the data there, based on operations performed while the DataSet held the data. In the past, data processing has been primarily connection-based. Now, in an effort to make multi-tiered apps more efficient, data processing is turning to a message-based approach that revolves around chunks of information. At the center of this approach is the DataAdapter, which provides a bridge to retrieve and save data between a DataSet and its source data store. It accomplishes this by means of requests to the appropriate SQL commands made against the data store. The XML-based DataSet object provides a consistent programming model that works with all models of data storage: flat, relational, and hierarchical. It does this by having no 'knowledge' of the source of its data, and by representing the data that it holds as collections and data types. No matter what the source of the data within the DataSet is, it is manipulated through the same set of standard APIs exposed through the DataSet and its subordinate objects. While the DataSet has no knowledge of the source of its data, the managed provider has detailed and specific information. The role of the managed provider is to connect, fill, and persist the DataSet to and from data stores. The OLE DB and SQL Server .NET Data Providers (System.Data.OleDb and System.Data.SqlClient) that are part of the .Net Framework provide four basic objects: the Command, Connection, 13
  • 14. DataReader and DataAdapter. In the remaining sections of this document, we'll walk through each part of the DataSet and the OLE DB/SQL Server .NET Data Providers explaining what they are, and how to program against them. The following sections will introduce you to some objects that have evolved, and some that are new. These objects are:  Connections. For connection to and managing transactions against a database.  Commands. For issuing SQL commands against a database.  DataReaders. For reading a forward-only stream of data records from a SQL Server data source.  DataSets. For storing, remoting and programming against flat data, XML data and relational data.  DataAdapters. For pushing data into a DataSet, and reconciling data against a database. When dealing with connections to a database, there are two different options: SQL Server .NET Data Provider (System.Data.SqlClient) and OLE DB .NET Data Provider (System.Data.OleDb). In these samples we will use the SQL Server .NET Data Provider. These are written to talk directly to Microsoft SQL Server. The OLE DB .NET Data Provider is used to talk to any OLE DB provider (as it uses OLE DB underneath). Connections Connections are used to 'talk to' databases, and are respresented by providerspecific classes such as SQLConnection. Commands travel over connections and resultsets are returned in the form of streams which can be read by a DataReader object, or pushed into a DataSet object. Commands Commands contain the information that is submitted to a database, and are represented by provider-specific classes such as SQLCommand. A command can be a 14
  • 15. stored procedure call, an UPDATE statement, or a statement that returns results. You can also use input and output parameters, and return values as part of your command syntax. The example below shows how to issue an INSERT statement against the Northwind database. DataReaders The DataReader object is somewhat synonymous with a read-only/forward-only cursor over data. The DataReader API supports flat as well as hierarchical data. A DataReader object is returned after executing a command against a database. The format of the returned DataReader object is different from a recordset. For example, you might use the DataReader to show the results of a search list in a web page. DataSets and DataAdapters DataSets The DataSet object is similar to the ADO Recordset object, but more powerful, and with one other important distinction: the DataSet is always disconnected. The DataSet object represents a cache of data, with database-like structures such as tables, columns, relationships, and constraints. However, though a DataSet can and does behave much like a database, it is important to remember that DataSet objects do not interact directly with databases, or other source data. This allows the developer to work with a programming model that is always consistent, regardless of where the source data resides. Data coming from a database, an XML file, from code, or user input can all be placed into DataSet objects. Then, as changes are made to the DataSet they can be tracked and verified before updating the source data. The GetChanges method of the DataSet object actually creates a second DatSet that contains only the changes to the data. This DataSet is then used by a DataAdapter (or other objects) to update the original data source. The DataSet has many XML characteristics, including the ability to produce and consume XML data and XML schemas. XML schemas can be used to describe schemas interchanged via WebServices. In fact, a DataSet with a schema can actually be compiled for type safety and statement completion. 15
  • 16. DataAdapters (OLEDB/SQL) The DataAdapter object works as a bridge between the DataSet and the source data. Using the provider-specific SqlDataAdapter (along with its associated SqlCommand and SqlConnection) can increase overall performance when working with a Microsoft SQL Server databases. For other OLE DB-supported databases, you would use the OleDbDataAdapter object and its associated OleDbCommand and OleDbConnection objects. The DataAdapter object uses commands to update the data source after changes have been made to the DataSet. Using the Fill method of the DataAdapter calls the SELECT command; using the Update method calls the INSERT, UPDATE or DELETE command for each changed row. You can explicitly set these commands in order to control the statements used at runtime to resolve changes, including the use of stored procedures. For ad-hoc scenarios, a CommandBuilder object can generate these at runtime based upon a select statement. However, this run-time generation requires an extra round-trip to the server in order to gather required metadata, so explicitly providing the INSERT, UPDATE, and DELETE commands at design time will result in better run-time performance. 1. ADO.NET is the next evolution of ADO for the .Net Framework. 2. ADO.NET was created with n-Tier, statelessness and XML in the forefront. Two new objects, the DataSet and DataAdapter, are provided for these scenarios. 3. ADO.NET can be used to get data from a stream, or to store data in a cache for updates. 4. There is a lot more information about ADO.NET in the documentation. 5. Remember, you can execute a command directly against the database in order to do inserts, updates, and deletes. You don't need to first put data into a DataSet in order to insert, update, or delete it. 6. Also, you can use a DataSet to bind to the data, move through the data, and navigate data relationships 16
  • 17. SQL SERVER DATABASE A database management, or DBMS, gives the user access to their data and helps them transform the data into information. Such database management systems include dBase, paradox, IMS, SQL Server and SQL Server. These systems allow users to create, update and extract information from their database. A database is a structured collection of data. Data refers to the characteristics of people, things and events. SQL Server stores each data item in its own fields. In SQL Server, the fields relating to a particular person, thing or event are bundled together to form a single complete unit of data, called a record (it can also be referred to as raw or an occurrence). Each record is made up of a number of fields. No two fields in a record can have the same field name. During an SQL Server Database design project, the analysis of your business needs identifies all the fields or attributes of interest. If your business needs change over time, you define any additional fields or change the definition of existing fields. SQL Server Tables SQL Server stores records relating to each other in a table. Different tables are created for the various groups of information. Related tables are grouped together to form a database. Primary Key Every table in SQL Server has a field or a combination of fields that uniquely identifies each record in the table. The Unique identifier is called the Primary Key, or simply the Key. The primary key provides the means to distinguish one record from all other in a table. It allows the user and the database system to identify, locate and refer to one particular record in the database. 17
  • 18. Relational Database Sometimes all the information of interest to a business operation can be stored in one table. SQL Server makes it very easy to link the data in multiple tables. Matching an employee to the department in which they work is one example. This is what makes SQL Server a relational database management system, or RDBMS. It stores data in two or more tables and enables you to define relationships between the table and enables you to define relationships between the tables. Foreign Key When a field is one table matches the primary key of another field is referred to as a foreign key. A foreign key is a field or a group of fields in one table whose values match those of the primary key of another table. Referential Integrity Not only does SQL Server allow you to link multiple tables, it also maintains consistency between them. Ensuring that the data among related tables is correctly matched is referred to as maintaining referential integrity. Data Abstraction A major purpose of a database system is to provide users with an abstract view of the data. This system hides certain details of how the data is stored and maintained. Data abstraction is divided into three levels. Physical level: This is the lowest level of abstraction at which one describes how the data are actually stored. Conceptual Level: At this level of database abstraction all the attributed and what data are actually stored is described and entries and relationship among them. View level: This is the highest level of abstraction at which one describes only part of the database. 18
  • 19. Advantages of RDBMS  Redundancy can be avoided  Inconsistency can be eliminated  Data can be Shared  Standards can be enforced  Security restrictions ca be applied  Integrity can be maintained  Conflicting requirements can be balanced  Data independence can be achieved. Disadvantages of DBMS A significant disadvantage of the DBMS system is cost. In addition to the cost of purchasing of developing the software, the hardware has to be upgraded to allow for the extensive programs and the workspace required for their execution and storage. While centralization reduces duplication, the lack of duplication requires that the database be adequately backed up so that in case of failure the data can be recovered. FEATURES OF SQL SERVER (RDBMS) SQL SERVER is one of the leading database management systems (DBMS) because it is the only Database that meets the uncompromising requirements of today’s most demanding information systems. From complex decision support systems (DSS) to the most rigorous online transaction processing (OLTP) application, even application that require simultaneous DSS and OLTP access to the same critical data, SQL Server leads the industry in both performance and capability SQL SERVER is a truly portable, distributed, and open DBMS that delivers unmatched performance, continuous operation and support for every database. 19
  • 20. SQL SERVER RDBMS is high performance fault tolerant DBMS which is specially designed for online transactions processing and for handling large database application. SQL SERVER with transactions processing option offers two features which contribute to very high level of transaction processing throughput, which are  The row level lock manager Enterprise wide Data Sharing The unrivaled portability and connectivity of the SQL SERVER DBMS enables all the systems in the organization to be linked into a singular, integrated computing resource. Portability SQL SERVER is fully portable to more than 80 distinct hardware and operating systems platforms, including UNIX, MSDOS, OS/2, Macintosh and dozens of proprietary platforms. This portability gives complete freedom to choose the database sever platform that meets the system requirements. Open Systems SQL SERVER offers a leading implementation of industry –standard SQL. SQL Server’s open architecture integrates SQL SERVER and non –SQL SERVER DBMS with industries most comprehensive collection of tools, application, and third party software products SQL Server’s Open architecture provides transparent access to data from other relational database and even non-relational database. Distributed Data Sharing SQL Server’s networking and distributed database capabilities to access data stored on remote server with the same ease as if the information was stored on a single 20
  • 21. local computer. A single SQL statement can access data at multiple sites. You can store data where system requirements such as performance, security or availability dictate. Unmatched Performance The most advanced architecture in the industry allows the SQL SERVER DBMS to deliver unmatched performance. Sophisticated Concurrency Control Real World applications demand access to critical data. With most database Systems application becomes “contention bound” – which performance is limited not by the CPU power or by disk I/O, but user waiting on one another for data access . SQL Server employs full, unrestricted row-level locking and contention free queries to minimize and in many cases entirely eliminates contention wait times. No I/O Bottlenecks SQL Server’s fast commit groups commit and deferred write technologies dramatically reduce disk I/O bottlenecks. While some database write whole data block to disk at commit time, SQL Server commits transactions with at most sequential log file on disk at commit time, On high throughput systems, one sequential writes typically group commit multiple transactions. Data read by the transaction remains as shared memory so that other transactions may access that data without reading it again from disk. 21
  • 22. CHAPTER IV 4. SYSTEM DESIGN 4.1 DESIGN NOTATIONS The design phase started by reviewing the study phase activates and making decisions about which function are to be performing by the hardware, software and human ware. The process of the system design is elaborate and consists of five main stages and it becomes more and more elaborate of each stage. The supporting diagrams are provided in order to understand the working nature of the system. These diagrams will provide visual display, therefore it easy to understand in pictorial way rather than in a theoretical way. Here two types of supporting diagrams were provides as follows,  Data Flow Diagram  System Flow Diagram 22
  • 23. 4.2 DATAFLOW DIAGARAM Student 23
  • 24. 4.2 System Flow Diagram System flow diagram represents what the system or the application is required to do. It allows individuals to see logical elements apart from the physical components. System flow diagram describes the internal behavior of the system in order to deal successfully with the environment. Login page Validation User Admin Main Form Main Form Candidate Registration User Registration Vote Count Database Candidate Report Vote Count Report User Report 24 Vote
  • 25. DESIGN PROCESS INPUT DESIGN The design of input focuses on controlling the amount of input required, controlling the errors, avoiding delay, avoiding extra steps and keeping the process simple. The input is designed in such a way so that it provides security and ease of use with retaining the privacy. Input Design considered the following things:  What data should be given as input?  How the data should be arranged or coded?  The dialog to guide the operating personnel in providing input.  Methods for preparing input validations and steps to follow when error occur. OBJECTIVES OF THE INPUT DESIGN Input Design is the process of converting a user-oriented description of the input into a computer-based system. This design is important to avoid errors in the data input process and show the correct direction to the management for getting correct information from the computerized system. It is achieved by creating user-friendly screens for the data entry to handle large volume of data. The goal of designing input is to make data entry easier and to be free from errors. The data entry screen is designed in such a way that all the data manipulates can be performed. It also provides record viewing facilities. When the data is entered it will check for its validity. Data can be entered with the help of screens. Thus the objective of input design is to create an input layout that is easy to follow. 25
  • 26. The main inputs of the system are  Candidate Module This module maintains the candidate information like candidate post, name, class and etc.,  Registration Module This module maintains the voters information like voters name, class, user id, password and etc.,  Vote Plus Module Using this module, we can easily change the vote counting for particular candidate.  Voting Module Using this module, voters can easily vote for particular candidate OUTPUT DESIGN A quality output is one, which meets the requirements of the end user and presents the information clearly. In output design it is determined how the information is to be displaced for immediate need and also the hard copy output. It is the most important and direct source information to the user. Efficient and intelligent output design improves the system’s relationship to help user decision-making. Designing computer output should proceed in an organized, well thought out manner; the right output must be developed while ensuring that each output element is designed so that people will find the system can use easily and effectively. When analysis designs computer output, they should:  Identify the specific output that is needed to meet the requirements.  Select methods for presenting information. 26
  • 27.  Create document, report, or other formats that contain information produced by the system. The main outputs of the system are  Candidate Report Candidate report displays the all candidate information  Voters Report Voters report displays the all Voters information  Result Report Result report displays the candidate result. DATABASE DESIGN A database is an organized mechanism that has the capability of storing information through which a user can retrieve stored information in an effective and efficient manner. The data is the purpose of any database and must be protected. The database design is a two level process. In the first step, user requirements are gathered together and a database is designed which will meet these requirements as clearly as possible. 27
  • 28. TABLE DESIGN Table Name: tbl_register Primary Key: username Sl no Field Data Type Size Description 1 usertype varchar 50 User Type 2 username varchar 50 User Name 3 password varchar 50 Password Table Name: tbl_candidate Primary Key: post Sl no Field Data Type Size Description 1 post varchar 50 Post Name 2 name varchar 50 Candidate Name 3 class varchar 50 Class 28
  • 29. Table: tbl_vote Primary Key: post Sl no Field Data Type Size Description 1 post varchar2 50 Candidate Post 2 name varchar2 50 Candidate Name 3 vote varchar2 50 Vote 4 count number 10 Vote Count 29
  • 30. CHAPTER V 5. SYSTEM TESTING AND IMPLEMENTATION The method of designing the system to produce desired result is accomplished in the System development. All the facilities required for developing the new system is acquired and computer program preparation is started. INTRODUCTION The development phase is the phase where the system is developed according to the proposed system. In this phase the programs are coded, programs are coded; programs are the entered into the computer and checked for any possible errors. After the entire program was coded using asp. The hard copies of the reports were taken and the debugging was subsequently made. The designed new system is tested with the sample data and final outputs are verified with the actual manual reports. If this reports are satisfied then the system is put to process with on-line data entry. The method of designing the system to produce desired result is accompanished in the system development. All the facilities required for developing the new system acquired and computer program preparation is started. The desired new system is tested with sample data and final outputs are verified with oriented before implementation. It is alone to ensure that the system objectives have been achieved successfully. 30
  • 31. 5.1 SYSTEM TESTING Testing represents an interesting anomaly for software engineer. It is process of executing a program with the intent of finding error. The tests must be traceable to the requirement specifications. A good and efficient testing method demonstrates that software functions appear to be working according to the specification, that behavioural and performance requirements are being met. NEED FOR SOFTWARE TESTING Testing is an important component in the development of a system. The main objectives of testing are  To ensure that all the functions of the system are working properly.  To ensure that all the system accepts correct input and behave expectedly.  To locate the errors in the system and debug them.  To ensure that the system is internally consistent.  To rectify the errors.  To provide 100 percent error free system.  To provide user free entry.  To minimize the re-work.  To add additional features.  To find unnecessary process.  The system is understandable by the user and what are the changes are needed. 31
  • 32. TESTING METHODOLOGIES White-Box Testing This is performed knowing the internal working of the system. Tests are conducted to ensure that the internal operations perform according to the specification and all internal components have adequately been exercised. White-Box testing is carried out in this project. The testing is executed by giving the valid data types and data. By conducting this test, unnecessary codes which are malfunctioning has been removed from the project. The internal working of the system is tested by giving the inputs to the system successfully. Black-box Testing Black box testing treats the software as a black box without any understanding as to how the internals behave. It aims to test the functionality according to the requirements. Knowing the specific function that a product or module has been designed to perform; tests can be designed to demonstrate the operational validity of each function. This type of test design is applicable to all levels of unit, integration, functional, system and acceptance testing. After the completion of other testing, design of the system is tested using this testing. 32
  • 33. TYPES OF TESTING Unit Testing Unit testing is concerned with the testing of a small module. Using the detailed design description as a guide, important control paths are tested to uncover the errors within the boundary of the module. The module interface is tested to ensure that the information flows in and out of the program unit under test. The local data structure is ensured that the variables are exercised to ensure that all statements in the module are executed at least once. Integration Testing Integration testing is proceeded with bottom up approach. In bottom up integration testing, an individual module is first tested from a test harness. Once a set of individual module has been tested, they are combined into a collection of modules, known as builds, which are applied by a second harness. This process can combine until the build consists of the entire application. The main objective of the integration testing is to take the unit tested modules and to build a program structure that has been dictated by design. Once all modules are unit tested they are put together for integration testing process. All the unit-tested modules are combined and integrated. This type of testing is a must because the information can be lost across an interface. One module can have an inadvertent, adverse effect on the other sub functions may not produce desired results when integrated. User Interface Testing The software becomes a widely used tool only if it is an easily opera table tool. Since this is a website, care was taken to make the system to be operated even by the novices. All the users have to do is to click and buy the products. The input devices that are used in this system are keyboard and the mouse. And the output device is only the 33
  • 34. monitor. So by using only the mouse the user can buy all the products from the website. They have to use the keyboard only to enter their details at the time of ordering the products. The error messages produced by this system can be understood even to the people who know very common English. 34
  • 35. 5.2 IMPLEMENTATION Implementation is the stage of a project when the theoretical design is turned into a working system. If the implementation stage is not carefully planned and controlled, it can cause chaos. The implementation stage is a system project in its own. Implementation is the stage of the project where the theoretical design turns into a working system. Thus it can be considered to be the most critical stage in achieving a successful new and giving the users confidence that the new system will work and be effective and accurate. It is less creative than system design. It is primarily concerned with user training and site preparation. Depending on the nature of the system, extensive user may be required. Implementation simply means converting a new system design into operation. An important aspect of the system analyst’s job is to make sure that the new design is implemented to establish standards. Implementation means the process of converting a new raised system design into an operational one. The three types of implementation are  Implementation of a new computer system to replace an existing one.  Implementation of a modified application to replace an existing one.  Implementation of a computer system to replace a manual system. 35
  • 36. CHAPTER VI 6. CONCLUSION AND FUTURE ENCHANCEMENT CONCLUSION “Vote plus” software developed for a school or to a college has been designed to achieve maximum efficiency and reduce the time taken to handle the Election activity. It is designed to replace an existing manual record system thereby reducing time taken for calculations and for storing data. The system uses VB .Net as front end and Microsoft SQL as a backend for the database. The system is strong enough to withstand regressive yearly operations under conditions where the database is maintained and cleared over a certain time of span. The implementation of the system in the organization will considerably reduce data entry, time and also provide readily calculated reports. FUTURE ENCHANCEMENT The project is developed considering only material and money but it can be extended for man and machine also. Since our objective of the project is successfully completed. This is system provides efficiency in many ways. All the features that is required for the voting system has been finished successfully. All the complications concerned with this project are successfully solved. Every application has its own merits and demerits. The project has covered almost all the requirements. Further requirements and improvements can easily be done since the coding is mainly structured or modular in nature. Changing the existing modules or adding new module can append improvements. 36
  • 37. BIBLIOGRAPHY BOOK REFERENCES:  “Murach’s beginning VB.Net” Author : Anne Price Publisher : BPB Publication Edition : First Edition.  “System Analysis and Design” Author : ELIS.AWAD Publisher : Galgottia Publications Edition : 11 Edition.  “Mastering VB.Net” Author : EVANGELOS PETROUTOS Publisher : BPB Publications WEB PAGE REFERENCES: ‎ ‎ ‎ 37
  • 38. APPENDIX SAMPLE CODING Election Login Imports System.Data Imports System.Data.SqlClient Module Module1 Public conn As New ADODB.Connection Public rs As New ADODB.Recordset Public rss As New ADODB.Recordset Public sql As String Public server1 As String Public database1 As String Public user1 As String Public password1 As String Public oid As String Public sid As String Public d As Date Public dt As String Public route As String Public con As New SqlConnection("Server=SUSHANTHPC;Database=Election;Trusted_Connection=false;user id=sa;password=q1w2e3r4/;") Public i As Integer Public Function opendb() If conn.State = 1 Then conn.Close() conn.Open("Provider=SQLOLEDB.1;Persist Security Info=False;User ID=sa;password=q1w2e3r4/;Initial Catalog=Election;Data Source=SUSHANTHPC") Return 0 End Function Public Sub SetConnection(Optional ByVal Firstcomp As Boolean = False) Dim str As String str = "Data Source=SUSHANTH-PC;Initial Catalog=Election;User ID=sa;Password=q1w2e3r4/" Try If IsNothing(con) = False Then If con.State = ConnectionState.Closed Then con.Close() End If End If con = New SqlConnection(str) con.Open() Catch ex As System.Exception MsgBox(ex.Message) MsgBox("Not Connecting to Database Server.Please check your network.") End Try End Sub 38
  • 39. End Module Public Class frmlogin Private Sub frmlogin_Load(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles MyBase.Load opendb() End Sub Private Sub Button1_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles Button1.Click If cmdtype.Text = "" Then MsgBox("Enter usertype") ElseIf txtname.Text = "" Then MsgBox("Enter the username") ElseIf txtpass.Text = "" Then MsgBox("Enter the password") Else sql = "select * from tbl_register where usertype='" & cmdtype.Text & "' and username='" & txtname.Text & "' and password='" & txtpass.Text & "'" If rs.State = 1 Then rs.Close() rs.Open(sql, conn) If rs.EOF = False Then If cmdtype.Text = "ADMIN" Then Me.Hide() frmwelcome.Show() 'ComboBox1.SelectedIndex = -1 txtname.Text = "" txtpass.Text = "" ElseIf cmdtype.Text = "STUDENT" Then Me.Hide() 'menuform.PAYROLLToolStripMenuItem.Visible = False frmwelcome.MASTERToolStripMenuItem.Visible = False 'frmwelcome.REPORTSToolStripMenuItem.Visible = False frmwelcome.Show() 'ComboBox1.SelectedIndex = -1 txtname.Text = "" txtpass.Text = "" End If Else MsgBox("Login Failed") End If End If End Sub Sub clear() cmdtype.SelectedIndex = -1 39
  • 40. txtname.Text = "" txtpass.Text = "" End Sub Private Sub Button2_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles Button2.Click clear() End Sub End Class Candidate Register Public Class frmcandidates Private Sub frmcandidates_Load(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles MyBase.Load opendb() loadgrid() End Sub Sub loadgrid() i = 0 DataGridView1.Rows.Clear() sql = "select * from tbl_candidate If rs.State = 1 Then rs.Close() rs.Open(sql, conn) Do While Not rs.EOF DataGridView1.Rows.Add() DataGridView1.Item(0, i).Value DataGridView1.Item(1, i).Value DataGridView1.Item(2, i).Value DataGridView1.Item(3, i).Value i = i + 1 rs.MoveNext() " = = = = rs(0).Value rs(1).Value rs(2).Value rs(3).Value Loop End Sub Private Sub Button2_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles Button2.Click clear() End Sub Sub clear() cmdpost.SelectedIndex = -1 txtname.Text = "" cmdclass.Text = "" End Sub Private Sub Button1_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles Button1.Click 40
  • 41. sql = " select * from tbl_candidate where post='" & cmdpost.Text & "' and name='" & txtname.Text & "'" If rs.State = 1 Then rs.Close() rs.Open(sql, conn) If rs.EOF = False Then MsgBox("record exists") Else sql = "insert into tbl_candidate(post,name,class)" sql = sql & " values('" & cmdpost.Text & "','" & txtname.Text & "','" & cmdclass.Text & "')" conn.Execute(sql) sql = "insert into tbl_vote(post,name,vote)" sql = sql & " values('" & cmdpost.Text & "','" & txtname.Text & "',0)" conn.Execute(sql) MsgBox("Registered successfully") loadgrid() clear() End If End Sub Private Sub Button4_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles Button4.Click sql = " delete from tbl_candidate where id='" & DataGridView1.CurrentRow.Cells(0).Value & "'" conn.Execute(sql) sql = " delete from tbl_vote where name='" & txtname.Text & "'" conn.Execute(sql) MsgBox("deleted") loadgrid() clear() End Sub Private Sub Button3_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles Button3.Click sql = "update tbl_candidate set post='" & cmdpost.Text & "',name='" & txtname.Text & "', class='" & cmdclass.Text & "' where id='" & DataGridView1.CurrentRow.Cells(0).Value & "'" conn.Execute(sql) sql = " update tbl_vote set post='" & cmdpost.Text & "',name='" & txtname.Text & "' where name='" & txtname.Text & "'" conn.Execute(sql) MsgBox("record Updated") loadgrid() clear() End Sub Private Sub DataGridView1_CellClick(ByVal sender As Object, ByVal e As System.Windows.Forms.DataGridViewCellEventArgs) Handles DataGridView1.CellClick cmdpost.Text = DataGridView1.CurrentRow.Cells(1).Value txtname.Text = DataGridView1.CurrentRow.Cells(2).Value 41
  • 42. cmdclass.Text = DataGridView1.CurrentRow.Cells(3).Value End Sub End Class User Registration Public Class frmreg Private Sub frmreg_Load(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles MyBase.Load opendb() loadgrid() End Sub Sub loadgrid() i = 0 DataGridView1.Rows.Clear() sql = "select * from tbl_register" If rs.State = 1 Then rs.Close() rs.Open(sql, conn) Do While Not rs.EOF DataGridView1.Rows.Add() DataGridView1.Item(0, i).Value DataGridView1.Item(1, i).Value DataGridView1.Item(2, i).Value DataGridView1.Item(3, i).Value i = i + 1 rs.MoveNext() = = = = rs(0).Value rs(1).Value rs(2).Value rs(3).Value Loop End Sub Sub clear() txtname.Text = "" txtpass.Text = "" cmdtype.SelectedIndex = -1 End Sub Private Sub Button1_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles Button1.Click If cmdtype.Text = "" Then MsgBox("enter user type") ElseIf txtname.Text = "" Then MsgBox("enter username") ElseIf txtpass.Text = "" Then MsgBox("enter password") Else sql = "select * from tbl_register where username= '" & txtname.Text & "' or password='" & txtpass.Text & "' " If rs.State = 1 Then rs.Close() rs.Open(sql, conn) If rs.EOF = False Then 42
  • 43. MsgBox("Record exist") clear() Else sql = "insert into tbl_register(usertype,username,password)" sql = sql & "values('" & cmdtype.Text & "','" & txtname.Text & "','" & txtpass.Text & "')" conn.Execute(sql) MsgBox("REGISTRATION SUCCESSFUL") clear() loadgrid() End If End If End Sub Private Sub Button2_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles Button2.Click clear() End Sub Private Sub Button4_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles Button4.Click sql = "delete from tbl_register where eno='" & DataGridView1.CurrentRow.Cells(0).Value & "'" conn.Execute(sql) If MsgBoxResult.No = MsgBox("do you want to permanently delete this record?", MsgBoxStyle.YesNo) Then Exit Sub MsgBox("record deleted") clear() loadgrid() End Sub Private Sub Button3_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles Button3.Click If cmdtype.Text = "" Then MsgBox("enter user type") ElseIf txtname.Text = "" Then MsgBox("enter username") ElseIf txtpass.Text = "" Then MsgBox("enter password") Else sql = " select * from tbl_register where eno='" & DataGridView1.CurrentRow.Cells(0).Value & "'" If rs.State = 1 Then rs.Close() rs.Open(sql, conn) If rs.EOF = False Then MsgBox("already exists") Else sql = "update tbl_register set usertype= '" & cmdtype.Text & "',username= '" & txtname.Text & "', password ='" & txtpass.Text & "' where eno= '" & DataGridView1.CurrentRow.Cells(0).Value & "'" conn.Execute(sql) 43
  • 44. MsgBox("record updated") clear() loadgrid() End If End If End Sub Private Sub DataGridView1_CellClick(ByVal sender As Object, ByVal e As System.Windows.Forms.DataGridViewCellEventArgs) Handles DataGridView1.CellClick cmdtype.Text = DataGridView1.CurrentRow.Cells(1).Value txtname.Text = DataGridView1.CurrentRow.Cells(2).Value txtpass.Text = DataGridView1.CurrentRow.Cells(3).Value End Sub End Class Voting Public Class frmvote Private Sub frmvote_Load(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles MyBase.Load opendb() loadpresident() loadjoint() loadsecretary() End Sub Sub loadpresident() i = 0 DataGridView1.Rows.Clear() sql = " SELECT name, post" sql = sql + " FROM dbo.tbl_candidate" sql = sql + " WHERE (post = N'PRESIDENT')" If rs.State = 1 Then rs.Close() rs.Open(sql, conn) Do While Not rs.EOF DataGridView1.Rows.Add() DataGridView1.Item(0, i).Value = rs(0).Value i = i + 1 rs.MoveNext() Loop End Sub Sub loadsecretary() i = 0 DataGridView2.Rows.Clear() sql = " SELECT name, post" sql = sql + " FROM dbo.tbl_candidate" sql = sql + " WHERE (post = N'SECRETARY')" If rs.State = 1 Then rs.Close() rs.Open(sql, conn) Do While Not rs.EOF 44
  • 45. DataGridView2.Rows.Add() DataGridView2.Item(0, i).Value = rs(0).Value i = i + 1 rs.MoveNext() Loop End Sub Sub loadjoint() i = 0 DataGridView3.Rows.Clear() sql = " SELECT name, post" sql = sql + " FROM dbo.tbl_candidate" sql = sql + " WHERE (post = N'JOINT SECRETARY')" If rs.State = 1 Then rs.Close() rs.Open(sql, conn) Do While Not rs.EOF DataGridView3.Rows.Add() DataGridView3.Item(0, i).Value = rs(0).Value i = i + 1 rs.MoveNext() Loop End Sub Private Sub Button11_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Me.Close() frmwelcome.Show() End Sub Private Sub Button1_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles Button1.Click DataGridView1.Visible = True End Sub Private Sub Button2_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles Button2.Click DataGridView2.Visible = True End Sub Private Sub Button3_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles Button3.Click DataGridView3.Visible = True End Sub Private Sub DataGridView1_CellClick(ByVal sender As Object, ByVal e As System.Windows.Forms.DataGridViewCellEventArgs) Handles DataGridView1.CellClick Dim d As Integer 45
  • 46. For a = 0 To DataGridView1.Rows.Count - 1 If DataGridView1.Rows(a).Cells(1).Selected = True Then sql = " update tbl_vote set vote= vote+1 where post='" & Button1.Text & "' and name= '" & DataGridView1.Rows(a).Cells(0).Value & "'" conn.Execute(sql) End If Next DataGridView1.Enabled = False Button1.Enabled = False End Sub Private Sub DataGridView2_CellClick(ByVal sender As Object, ByVal e As System.Windows.Forms.DataGridViewCellEventArgs) Handles DataGridView2.CellClick Dim d As Integer For a = 0 To DataGridView2.Rows.Count - 1 If DataGridView2.Rows(a).Cells(1).Selected = True Then sql = " update tbl_vote set vote= vote+1 where post= '" & Button2.Text & "' and name= '" & DataGridView2.Rows(a).Cells(0).Value & "'" conn.Execute(sql) End If Next DataGridView2.Enabled = False Button2.Enabled = False End Sub Private Sub DataGridView3_CellClick(ByVal sender As Object, ByVal e As System.Windows.Forms.DataGridViewCellEventArgs) Handles DataGridView3.CellClick Dim d As Integer For a = 0 To DataGridView3.Rows.Count - 1 If DataGridView3.Rows(a).Cells(1).Selected = True Then sql = " update tbl_vote set vote= vote+1 where post= '" & Button3.Text & "' and name= '" & DataGridView1.Rows(a).Cells(0).Value & "'" conn.Execute(sql) End If Next 46
  • 47. DataGridView3.Enabled = False Button3.Enabled = False End Sub Private Sub Button4_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles Button4.Click Me.Close() frmwelcome.Show() frmwelcome.VOTINGToolStripMenuItem.Visible = False End Sub End Class 47
  • 48. SAMPLE SCREEN 48
  • 49. 49
  • 50. 50
  • 51. 51
  • 52. 52
  • 53. 53
  • 54. 54
  • 55. 55
  • 56. 56
  • 57. 57
  • 58. 58