Event Quality Management System( A case study of Trade fair)

Price : 1000

<p>A Project (CSE-499) is submitted for the partial fulfillment of the requirements of B.Sc.(Hons) in Computer Science & Engineering (CSE), National University, Bangladesh.</p>

<ul class="">
<li><img src="images/controoler-pic.jpg" class="img-responsive img-rounded" height="200px" width="260px;"></li>
<li><img src="images/name-pic1.jpg" class="img-responsive img-rounded" height="200px" width="260px;"></li>
<li><img src="images/name-pic.jpg" class="img-responsive img-rounded" height="200px" width="260px;"></li>
</ul>

Put Bank Page

Letter Of Transmittal


<h1 style="color:#000; text-align:center;"> Letter of Transmittal </h1>
<h4>
08 Jun 2016.<br><br>
Md. Moklesur Rahman,<br><br>
Lecturer,<br><br>
Department of Computer Science and Engineering (CSE)<br><br>
Tejgaon College, Dhaka.<br><br>

<b>Subject:</b> Submission the Project Report on <b>“Event Management System ( A case study of Trade fair) ”.</b><br><br>

Dear Sir,<br><br>
It gave me an immense pleasure in presenting the project report, which assigned to me as fulfillment of my CSE degree requirement. In this paper, I have tried my level best to carry out all the requirements of a research project.<br><br><br>

In preparing this report, I had to gather information about the subject from Google, Wikipedia, blogs, text book, different article and different web sites. I have also conduct a survey to find out the problems and solution of the problems.<br><br><br>

I consider myself very privileged to prepare this research paper under your guidance. This has been an enormous opportunity for me to learn how to conduct a project program. It has provided me with a great scope of learning ICT of modern invention of the world. I must mention here that I am extremely thankful to you for your valuable guidance, tiresome effort and constant attention whenever required.<br><br><br>

Sincerely yours,<br><br><br>


………………………<br>
Sub Raz Suttra Dhar.<br>
NU Roll: 0190344<br>
Registration: 1000393<br>
Session: 2009-2010<br>
Computer Science and Engineering(CSE)<br>
Tejgaon College, Dhaka<br>
</h4>


Student Declaration
</h4>


<h1 style="color:#000; text-align:center;"><b> Student Declaration </b></h1>

<h4>

I am Sub RazSuttra Dhar, student of Computer Science and Engineering (CSE) program from the Tejgaon College, Dhaka do here by declare that the project report on <b>“Event Management System ( A case study of Trade fair)”</b> has not been submitted by me before for any degree, diploma, title or recognition.<br><br><br>


I hereby warrant that the work I have presented do not breach any existing copyright acts.<br><br><br>


Sub RazSuttraDhar<br><br>
NU Roll: 0190344<br><br>
Registration: 1000393.<br><br>
Department of Computer Science and Engineering (CSE)<br><br>
Session: 2009-2010.<br><br><br>

<b>Group Members</b><br><br>
Saddam Hossain<br><br>
NU Roll: 0110338<br><br>
Registration: 1001284<br><br>
Department of Computer Science and Engineering(CSE)<br><br>
Tejgaon College, Dhaka<br><br><br>

<b>Group Members</b><br><br>
Liaquate Hossain<br><br>
NU Roll: 0110337<br><br>
Registration: 1001283<br><br>
Department of Computer Science and Engineering(CSE)<br><br>
Tejgaon College, Dhaka<br><br>



Supervisor’s Certificate
</h4>


<h1 style="color:#000; text-align:center;">Supervisor’s Certificate</h1><br><br>

<h4>

This is to certify that Sub Raz Suttra Dhar, a student of Tejgaon College, Dhaka as under National University bearing Roll No : 0190344, Registration No: 100393, Session: 2009-2010 ExamminationYear – 2014. He has completed successfully his Project Report on <b>“Event Management System ( A case study of Trade fair) ”</b> Under my close supervision. He was found very active, sincere and devoted to his work during the preparation of his Project report.<br><br><br><br>

 

I wish him every success and prosperity in all his efforts.<br><br><br><br>

 

Faculty Guide,<br><br><br><br>


………………………….<br><br>
Md. MoklesurRahman<br><br>
Lecturer,<br><br>
Department of computer Science and Engineering (CSE).<br><br>
Tejgaon College, Dhaka.<br><br>


</h4>


Acknowledgement

</h4>


<h1 style="color:#000; text-align:center;"><b> Acknowledgement </b></h1></a><br><br><br>

<h4>
Firstly, I would like to express our gratitude to almighty God for enabling us strength and opportunity to complete this report within the schedule time successfully.<br><br><br><br>

I am very much grateful to my honorable supervisor <b>Md Moklesur Rahman</b> for assigning me to prepare this report, which enriches my academic as well as practical knowledge and aptitude. I have got the opportunity to submit this Project report on<b> “Event Management System ( A case study of Trade fair)”.</b><br><br><br><br>

I must take the opportunity to thank to my honorable Chairman, <b>Professor Md. Abdul Hadi</b> Dep- artment of Computer Science and Engineering, Tejgaon College, Dhaka for helping &giving me much information to prepare this project report.<br><br><br><br>

I also express special gratitude to all the teacher & my friends whom I have got sufficient help and co-operation for preparing the report.<br><br><br><br>

I have tried to fulfill my responsibility as much as possible to make this report attractive but some errors may occur without my intension. So I am requesting to pardon me and accept my report as the precious fruit my hard work.<br><br><br><br>

Thanks from,<br><br><br>

Sub RazSuttraDhar<br><br>
NU Roll: 0190344<br><br>
Registration: 1000393.<br><br>
Department of Computer Science and Engineering (CSE)<br><br>
Session: 2009-2010.<br><br>


</h4>

Abstract
</h4>

<h1 style="color:#000; text-align:center;"><b> Abstract </b></h1><br><br><br>

<h4>

Today’s city people are attending in various events, seminar, etc in every month. Some big events like Dhaka International Trade Fair, Digital World, ICT Fair, IEEE Conference are being arranged around the year. Visitors are gathering there for their fulfillment of desire. They visit there to buy, visit or promote their own products. Companies or Organizations open their stalls on the events. Stalls give their offers or services to the visitors and customers. But in common the visitors who planned to join the event but have no idea about the present conditions of the event. Companies can’t know the offers and visitors on other companies stalls. So to make everything centralized we are planned to develop a centralized system named <b>Event Management System( A case study of trade fair)</b>. which will keep everything I one place.

</h4>


Tables Of Contents
</h4>


<h1 style="color:#000; text-align:center;"><b> Chapter #1 : Introduction </b></h1>

<table class="table table-bordered table-responsive table-hover">

<thead>
<tr class="success">
<th> Topic No </th>
<th> Topic Name </th>
<th> Page </th>
</tr>

</thead>

<tbody>

<tr>
<td> 1.1 </td>
<td> Introduction </td>
<td> 02 </td>
</tr>
<tr>
<td> 1.2 </td>
<td> Fundamentals Of Microsoft Visual Studio 2010 </td>
<td> 02 </td>
</tr>
<tr>
<td> 1.3 </td>
<td> System Requirements for installing Visual Studio 2010 </td>
<td> 04 </td>
</tr>
<tr>
<td> 1.4 </td>
<td> Fundamentals Of Microsoft Visual C# Language </td>
<td> 04 </td>
</tr>
<tr>
<td> 1.5 </td>
<td> Title Of The Project </td>
<td> 05 </td>
</tr>
<tr>
<td> 1.6 </td>
<td> Objective Of Event management System (A Case Study Of Trade Fair) </td>
<td> 06 </td>
</tr>
<tr>
<td> 1.7 </td>
<td> Special Requirements </td>
<td> 06 </td>
</tr>
<tr>
<td> 1.8 </td>
<td> Scope </td>
<td> 06 </td>
</tr>
<tr>
<td> 1.9 </td>
<td> Project Category </td>
<td> 07 </td>
</tr>
</tbody>

</table>



Tables Of Contents
</h4>


<h1 style="color:#000; text-align:center;"><b> Chapter #2 : Project Planning </b></h1>

<table class="table table-bordered table-responsive table-hover">

<thead>
<tr class="success">
<th> Topic No </th>
<th> Topic Name </th>
<th> Page </th>
</tr>

</thead>

<tbody>

<tr>
<td> 2.1 </td>
<td> Proces Description </td>
<td> 09 </td>
</tr>
<tr>
<td> 2.2 </td>
<td> Data Flow Diagram </td>
<td> 09 </td>
</tr>
<tr>
<td> 2.3 </td>
<td> ER Diagram </td>
<td> 012 </td>
</tr>

</tbody>

</table>


Tables Of Contents
</h4>


<h1 style="color:#000; text-align:center;"><b> Chapter #3 : System Analysis </b></h1>

<table class="table table-bordered table-responsive table-hover">

<thead>
<tr class="success">
<th> Topic No </th>
<th> Topic Name </th>
<th> Page </th>
</tr>

</thead>

<tbody>

<tr>
<td> 3.1 </td>
<td> Proces Model </td>
<td> 16 </td>
</tr>
<tr>
<td> 3.2.1 </td>
<td> Water Fall Model </td>
<td> 16 </td>
</tr>
<tr>
<td> 3.2.2 </td>
<td> Water Fall Model Application </td>
<td> 17 </td>
</tr>
<tr>
<td> 3.2.3 </td>
<td> Advantage Of water Fall Model </td>
<td> 17 </td>
</tr>
<tr>
<td> 3.2.4 </td>
<td> Disadvantage Of water Fall Model </td>
<td> 17 </td>
</tr>
<tr>
<td> 3.2.5 </td>
<td> Reasons for use </td>
<td> 18 </td>
</tr>

</tbody>

</table>


Tables Of Contents
</h4>

<h1 style="color:#000; text-align:center;"><b> Chapter #4 : System Design </b></h1>

<table class="table table-bordered table-responsive table-hover">

<thead>
<tr class="danger">
<th> Topic No </th>
<th> Topic Name </th>
<th> Page </th>
</tr>

</thead>

<tbody>

<tr>
<td> 4.1 </td>
<td> Introduction </td>
<td> 20 </td>
</tr>
<tr>
<td> 4.2 </td>
<td> Overview </td>
<td> 20 </td>
</tr>
<tr>
<td> 4.3 </td>
<td> Scope </td>
<td> 20 </td>
</tr>
<tr>
<td> 4.4 </td>
<td> Back Ground </td>
<td> 21 </td>
</tr>
<tr>
<td> 4.5 </td>
<td> Applicable Document - Methodology </td>
<td> 21 </td>
</tr>
<tr>
<td> 4.6 </td>
<td> Risks </td>
<td> 22 </td>
</tr>
<tr>
<td> 4.7 </td>
<td> External </td>
<td> 23 </td>
</tr>
<tr>
<td> 4.8 </td>
<td> Destinations Of Programs </td>
<td> 23 </td>
</tr>
<tr>
<td> 4.9 </td>
<td> Context Flow Diagram </td>
<td> 23 </td>
</tr>
<tr>
<td> 4.10 </td>
<td> Data Flow Diagram </td>
<td> 24 </td>
</tr>
<tr>
<td> 4.11 </td>
<td> Data Flow Diagram Notation </td>
<td> 25 </td>
</tr>
<tr>
<td> 4.12 </td>
<td> Context Flow Diagram use of Admin </td>
<td> 26 </td>
</tr>
<tr>
<td> 4.13 </td>
<td> Work Flow Diagram </td>
<td> 32 </td>
</tr>
<tr>
<td> 4.14 </td>
<td> UML Diagrams </td>
<td> 33 </td>
</tr>
<tr>
<td> 4.15 </td>
<td> Types of UML Diagrams </td>
<td> 33 </td>
</tr>
<td> 4.16 </td>
<td> ER Diagram </td>
<td> 34 </td>
</tr>
<td> 4.16.1 </td>
<td> System Database Diagram </td>
<td> 34 </td>
</tr>
<tr>
<td> 4.16.2 </td>
<td> System ER Diagram </td>
<td> 35 </td>
</tr>
<tr>
<td> 4.17 </td>
<td> CSS Basic Concept </td>
<td> 36 </td>
</tr>
<tr>
<td> 4.18 </td>
<td> HTML Basic Conceptt </td>
<td> 36 </td>
</tr>
<tr>
<td> 4.19 </td>
<td> javaScript Concept </td>
<td> 36 </td>
</tr>
</tbody>

</table>


Tables Of Contents
</h4>


<h1 style="color:#000; text-align:center;"><b> Chapter #5 : Implementation </b></h1>

<table class="table table-bordered table-responsive table-hover">

<thead>
<tr class="danger">
<th> Topic No </th>
<th> Topic Name </th>
<th> Page </th>
</tr>

</thead>

<tbody>

<tr>
<td> 5.1 </td>
<td> Modules </td>
<td> 39 </td>
</tr>
<tr>
<td> 5.2 </td>
<td> Front End Technology </td>
<td> 39 </td>
</tr>
<tr>
<td> 5.3 </td>
<td> ASP.NET </td>
<td> 39 </td>
</tr>
<tr>
<td> 5.4 </td>
<td> ASP.NET MVC </td>
<td> 39 </td>
</tr>
<tr>
<td> 5.5 </td>
<td> Back End Technology </td>
<td> 40 </td>
</tr>
<tr>
<td> 5.6 </td>
<td> About Microsoft SQL Server 2012 </td>
<td> 40 </td>
</tr>
<tr>
<td> 5.7 </td>
<td> Database </td>
<td> 41 </td>
</tr>
<tr>
<td> 5.8 </td>
<td> Maintenance And Environment </td>
<td> 42 </td>
</tr>
<tr>
<td> 5.9 </td>
<td> Output Screen </td>
<td> 44 </td>
</tr>
<tr>
<td> 5.10 </td>
<td> Source Code </td>
<td> 53 </td>
</tr>

</tbody>

</table>


Tables Of Contents
</h4>

<h1 style="color:#000; text-align:center;"><b> Chapter #6 : Conclusion ANd Discussion </b></h1>

<table class="table table-bordered table-responsive table-hover">

<thead>
<tr class="danger">
<th> Topic No </th>
<th> Topic Name </th>
<th> Page </th>
</tr>

</thead>

<tbody>

<tr>
<td> 6.1 </td>
<td> Discussion </td>
<td> 61 </td>
</tr>
<tr>
<td> 6.2 </td>
<td> Future Plan </td>
<td> 61 </td>
</tr>
<tr>
<td> 6.3 </td>
<td> Conclusion </td>
<td> 61 </td>
</tr>
<tr>
<td> </td>
<td> Reference </td>
<td> </td>
</tr>

</tbody>

</table>



<!-- start of chapter 1 Introduction-->
<h1> Chapter #1 : Introduction </h1><br><br>


Chapter #1 : Introduction
</h4>

<img src="images/lesson1.png">
<h4 style="margin-top:200px; text-align:center; margin-left:850px;"> Page1 </h4>

Page 2
</h4>

<h1> 1.1: Introduction </h1>

<h4> <b>1.1: Introduction</b><br><br><br>
This project report will introduce how to build part of a c Event Quality Assurance and Development Management System using ASP.NET. ASP support three development model Web page, Web Form, MVC. MVC is a framework for building web applications using a MVC (Model View Controller) design:<br><br><br><br>
<ul class="list-group">

<li class="list-group-item"> The Model represents the application core (for instance a list of database records). </li>
<li class="list-group-item"> The View displays the data (the database records). </li>
<li class="list-group-item"> The Controller handles the input (to the database records). </li>
</ul><br><br>
The MVC model also provides full control over HTML, CSS, and JavaScript. This project provide us the information about student registration, teachers record, a department, all the course information, room allocation information, class schedule information & students result information. The system must provide the flexibility of generating the required documents on screen as well as on printer as and when required we can take it by pdf. <br><br>

<b>Advantages:</b><br><br><br>
1. Easy to check the Event Information.<br><br>
2. We can update any information in future.<br><br><br>

To develop this project Microsoft Visual studio Ultimate 2013 and SQL management studio has been used. <br><br><br>

<b>1.2: Fundamental of Microsoft Visual Studio Ultimate 2013 </b><br><br><br>
Microsoft Visual Studio is integrated development environment (IDE) from Microsoft. It is used to develop computer programs for Microsoft Windows, as well as web sites, web applications and web services. Visual Studio uses Microsoft software development platforms such as Windows API, Windows Forms, Windows Presentation Foundation, Store and Microsoft Silver light. It can produce both native code and code. Visual Studio includes a code editor supporting IntelliSense (the code completion component) as well as code refactoring. The integrated debugger works both as a source-level debugger and a machine-level debugger.
</h4>


Page 3
</h4>


<img src="images/vsu.png" class="img-responsive img-rounded" height="400px" width="100%;">

<h4>

<b>Visual Studio</b> is a tool-rich programming environment containing the functionality that you need to create large or small C# projects. You can even construct projects that seamlessly combine modules written by using different programming languages such as C++, Visual Basic, and F#. If you are using Visual Studio 2010 Express then it starts like this: <br><br><br>
If you are using Visual C# then the following tasks to create a new Windows Form Application:<br><br><br>
<ul class="list-group">
<li class="list-group-item">On the File menu, click New Project.</li>
<li class="list-group-item">In the New Project dialog box, in the middle pane click the Windows Form Application icon.</li>
<li class="list-group-item">In the Name field, type Event Quality Assurance and Development Management System.</li>

<li class="list-group-item">Click OK.</li>

<li class="list-group-item">Visual C# saves solutions to the C:\Users\Mabia\Documents\Visual Studio ultimate 2013\Projects\ Event Quality Assurance and Development Management System MvcApp folder by default. You can specify an alternative location when you save the solution.</li>

<li class="list-group-item"> On the File menu, click Save</li>
</ul>

</h4>


<h4 class="panel-title">
Page 4
</h4>
</div>

<h4>
<b> 1.3: System Requirements for Installing Visual Studio ultimate 2013</b><br><br><br><br>

When upgrading from Microsoft Visual Studio 2012 to Visual Studio 2013 you will take advantage of a refreshed and simplified environment with enhanced performance without any additional hardware requirements. Some of these core enhancements make use of capabilities that are only present in the latest versions of Windows and might require you to upgrade to a supported operating system.<br><br><br><br>


<b>Hardware Requirements</b><br><br>
<ul class="list-group">
<li class="list-group-item">1.6 GHz or faster processor.</li>
<li class="list-group-item">1 GB of RAM (1.5 GB if running on a virtual machine)</li>
<li class="list-group-item">10 GB (NTFS) of available hard disk space.</li>
<li class="list-group-item">5400 RPM hard drive.</li>
<li class="list-group-item">DirectX 9-capable video card running at 1024 x 768 or higher display resolution.</li>
</ul>
<br><br><br><br>

<b>Supported Operating System</b><br><br>
<ul class="list-group">
<li class="list-group-item">Windows 8.1 (x86 and x64)</li>
<li class="list-group-item">Windows 8 (x86 and x64)</li>
<li class="list-group-item">Windows 7 (x86 and x64)</li>
<li class="list-group-item">Windows Server 2008 R2 SP1 (x64)</li>
<li class="list-group-item">Windows Server 2012 (x64)</li>
</ul>
<br><br><br><br>

<b>Supported Architectures</b><br><br>
<ul class="list-group">
<li class="list-group-item">32-bit (x86)</li>
<li class="list-group-item">64-bit (x64)</li>
</ul>
</h4>
</div>
</div>
</div>


<h4 class="panel-title">

Page 5
</h4>

<h4>

<b> 1.4: Fundamental of Microsoft Visual C# Language</b><br><br><br><br>
<ul class="list-group">
<li class="list-group-item"><b>C# Language Basics:</b> New C# programmers are sometimes intimidated by the quirky syntax of the language, which includes special characters such as semicolons (;), curly braces {}, and backward slashes (\).Fortunately, once you get accustomed to C#, these details will quickly melt into the back-ground. In the following sections, you’ll learn about four general principles you need to know about C# before you learn any other concepts.<br><br><br><br></li>
</ul>
<b>Case Sensitivity:</b> Some languages are case-sensitive, while others are not. Java, C, C++, and C# are all examples of case-sensitive languages. VB is not. This difference can frustrate former VB programmers who don’t realize that keywords, variables, and functions must be entered with the proper case. For example, if you try to create a conditional statement in C# by entering If instead of if, your code will not be recognized, and the compiler will flag it with an error when you try to build your application.<br><br><br><br>

<b>Commenting:</b> Comments are descriptive text that is ignored by the compiler. C# provides two basic types of comments. The first type is the single-line comment. In this case, the comment starts with two forward slashes and continues for the entire current line. Optionally, C# programmers can also use multiple-line comments using the /* and */ comment brackets. This trick is often used to quickly comment out an entire block of code.<br><br><br><br>

<b>Statement Termination:</b> C# uses a semicolon (;) as a statement-termination character. Every statement in C# code must end with this semicolon, except when you’re defining a block structure such as a method, a conditional statement, or a looping construct. By omitting this semicolon, you can easily split a statement of code over multiple physical lines. You just need to remember to put the semicolon at the end of the last line, to end the statement.<br><br><br><br>

<b>Blocks:</b> The C#, Java, and C languages all rely heavily on curly braces—parentheses with a little more attitude: {}. You can find the curly braces to the right of most keyboards (next to the P key); they share a key with the square brackets .


</h4>


<h4 class="panel-title">
Page 6
</h4>

<h4>
<b>1.5 Title of The Project</b><br><br><br><br>

<b>“Event Management System ( A case study of Trade fair)” with reference to Tejgaon College , Dhaka.</b><br><br><br><br>

<b>1.6 Objective of Event Quality Assurance & Development Management System</b><br><br><br><br>
<ul class="list-group">
<li class="list-group-item">To develop a web-based application to find the information about past, present and upcoming events.</li>
<li class="list-group-item">To develop the quality and ensure management of the events.</li>
<li class="list-group-item">To concern the users about the events & take surveys from the system.</li>
<li class="list-group-item">All the users will sign up in this application from online and onsite.</li>
<li class="list-group-item">Every company who will take stalls or pavilion on the event will sign up in this application.</li>
<li class="list-group-item">User will be able to access the site with provided username and password.</li>
<li class="list-group-item">Stalls holders can access the site using their own authentication. Companies will be able to take survey and decision on how to develop their qualities and services.</li>
</ul>
<b>1.7 Special Requirements :</b><br><br><br><br>
<li class="list-group-item">HTML </li>
<li class="list-group-item">ASP.NET</li>
<li class="list-group-item">SQL </li>
<li class="list-group-item">CSS 3</li>
<li class="list-group-item">Java Script</li>
<li class="list-group-item">JQuery (JavaScript library)</li>
<li class="list-group-item">Bootstrap</li></b><br><br><br><br>

<b>1.8 Scope:</b><br><br><br><br>

This project is aimed at how the event can improve the efficiency of the services. Information of Event is one of the applications to improve the information of any particular events. This application involves almost all the features of the information system, the feature implementation will be online help for the users, visitors, companies who are attending an event to obtain information.

</h4>


<h4 class="panel-title">
Page 7
</h4>

<h4>
<b>1.9 Project Category</b><br><br><br><br>

<b>RDMMS (Relational Database Management System):</b><br><br><br><br>

Relational Database Management System is a type of Database Management System that Stores data in the form of related tables. Relational database are powerful because they require few assumptions about how data is related or how it will be extracted from the database. An important feature of relational system is that a single database can be across several tables.


</h4>

<!-- End of chapter 1 Introduction-->

<!-- start of chapter 2 Project Planning-->

<h1> Chapter #2 : Project Planning </h1><br><br>

<h4 class="panel-title">
Chapter #2 : Project Planning
</h4>
</div>

<img src="images/lesson2.png" class="img-responsive img-rounded">
<h4 style="margin-top:200px; text-align:center; margin-left:850px;"> Page8 </h4>

<h4 class="panel-title">

Process Description..........Page#9
</h4>

<h4>
<b> 2.1 Process Description:</b><br><br><br><br>

<b>User Control:</b> Manager login the application for control API with database.<br><br><br><br>

<b>Company Signup:</b> Companies will sign up hereto be enlisted with their stalls here
<br><br><br><br>
<b>User Signup:</b> Users outside of the events or who are going to visit the events is to sign up through a entry process.<br><br><br><br>

<b>Offers:</b> Stalls of various companies will sign up here. They will post their daily offers for the users and visitors for promoting their services and products.<br><br><br><br>

<b>Search Edit and delete:</b> Search and Edit option for query update.<br><br><br><br>

<b>2.2 Data Flow Diagram:</b><br><br><br><br>

A data Flow Diagram is a graphical representation of the “flow” of data through an http://en.wikipedia .org/wiki/information system Information System. A data flow diagram can also be used for the visualization of Data Processing it is common practice for a designer to draw a context- level DFD first which shows the interaction between the system and outside entities. This context – level DFD is then “exploded” to show more detail of the system begin modeled. A DFD represent flow of data through a system. Data Flow Diagram are commonly used during problem analysis. It views a system as a function that transforms the input into desired output. A DFD shows movement of data through the different transformations or process in the system.<br><br><br><br>

Data Flow Diagrams can be used to provide the end user with a physical idea of where the data they input ultimately has an effect upon the structure of the whole determined through a Data Flow Diagram. The appropriate register saved in database and maintained by appropriate authorities.
</h4>



<h4 class="panel-title">

Data Flow Diagram..........Page#10
</h4>

<img src="images/dfd-img.png" class="img-responsive img-rounded" width="100%;" height="100%;">
<h1 style="text-align:center; color:#000;">Fig 2.1: Data Flow Diagram Notation </h1>

<h4 class="panel-title">
<a data-toggle="collapse" data-parent="#accordion" href="#collapse24">
Level 0 DFD......... Page#11</a>
</h4>

<img src="images/dfd-level-0,1.png" class="img-responsive img-rounded" width="100%;" height="100%;">
<h1 style="text-align:center; color:#000;">Fig 2.1: Data Flow Diagram Level 0, 1 </h1><br><br><br><br>
<h4>
<b>Administrator:</b> Administrator assigns the company’s stalls, user and visitors information record. It also collects information from the database.<br><br><br><br>

<b>Company Information:</b> In company information the information of any company is recorded, which can be edited only by authorized company and can be used to view for any particular information.<br><br><br><br>

<b>User Details:</b> In the user details the details of any user information is recorded. Which can be edited and delete only by authorized user and can be used to view for any particular details.<br><br><br><br>

<b>Stalls Offer:</b> They will post their daily offers for the users and visitors for promoting their services and products.


</h4>

<h4 class="panel-title">

ER Diagram........ Page#12
</h4>

<h4>
<b>ER Diagram:</b> Entity Relationship Diagrams (REDs) illustrate the logical structure of database. An entity Relationship Diagram is a piece of data an object or concept about which data is stored..<br><br><br><br>

</h4>
<img src="images/ER-diagram-notations.png" class="img-responsive img-rounded" width="100%;" height="100%;">
<h1 style="text-align:center; color:#000;">Fig: 2.3 ER Diagram Notations. </h1><br><br><br><br>


<h4 class="panel-title">

There are three types of relationship between entities..........Page#13
</h4>


<h1 style="color:#000;">There are three types of relationship between entities:</h1>
<h4>
<ul class="list-group">
<li class="list-group-item"><b>One – to - One (1 to 1):</b> One instance of an entity ( A ) is associated with one other instance of another entity (B). For example , in a database of employees, each employee name (A) is associated with only one social security number(B).</li>

<li class="list-group-item"><b>One – to – many ( 1 to N):</b> One instance of an entity (A) is associated with zero, one or many instance of another entity (B), but for one instance of entity B there is only one instance of entity A. For example, for a company with all employees working in one building name (A) is associated with many different employees (B) , but those employees all share the same singular associated with entity A.</li>

<li class="list-group-item"><b>Many – to- many (N to N):</b> One instance of an entity (A ) is associated with one, zero or many instance of another entity (B), and one instance of entity B is associated with one, zero or many instances of entity A. For example, for a company is which all of its employees work on multiple projects, each instance of an employee ( A) is associated with many instance of project (B), and at the same time, each instance of a project (B) has multiple employees (A) associated with it.</li>

</ul>
</h4>

<!-- End of chapter 2 Project Planning-->

<!-- start of chapter 3 System Analysis-->
<h1> Chapter #3 : System Analysis </h1><br><br>


<h4 class="panel-title">
<a data-toggle="collapse" data-parent="#accordion" href="#collapse28">
Chapter #3 : System Analysis</a>
</h4>

<img src="images/lesson3.png" class="img-responsive img-rounded">
<h4 style="margin-top:200px; text-align:center; margin-left:850px;"> Page8 </h4>




<h4 class="panel-title">
<a data-toggle="collapse" data-parent="#accordion" href="#collapse29">
Process Model........Page#16</a>
</h4>

<h4>
<b>3.1 PROCESS MODEL</b><br><br><br>
The ultimate objectives of software engineering is to produce good quality maintainable software within reasonable time frame and at affordable cost. This is achievable only if we have matured processes to produce it. For a mature process, it should be possible to determine in advance how much time, cost and effort will be required to produce the final product. This can only be done using data from past experience, which requires that we must measure the software process.<br><br><br>
A key component of any software development process is the life cycle model on which the process is based. Life cycle of the software starts from concept exploration and ends at the retirement of the software.<br><br><br>
The system life cycle is the period of time that starts when a software product is conceived and ends when the product is no longer available for use. The software life cycle typically includes a requirement phase, design phase, implementation phase, test phase, installation and check out phase, operation and maintenance phase, and sometimes retirement phase.<br><br><br>
This system is developed mainly following WATERFALL MODEL<br><br>
<b>3.2.1. WATER FALL MODEL</b><br><br><br>
It suggests a systematic, sequential approach to software development that begins at the system level and progress through analysis, design, coding, testing and support.


<b>Figure: 3.1. Waterfall Model.</b><br><br>
The sequential phases in Waterfall model are: <br><br><br>
Requirement Gathering and analysis: All possible requirements of the system to be developed are captured in this phase and documented in a requirement specification doc.

</h4>

<h4 class="panel-title">
<a data-toggle="collapse" data-parent="#accordion" href="#collapse30">
Waterfall Model Application........Page#17</a>
</h4>

<h4>
<ul class="list-group">
<li class="list-group-item"><b>System Design:</b> The requirement specifications from first phase are studied in this phase and system design is prepared. System Design helps in specifying hardware and system requirements and also helps in defining overall system architecture.</li><br><br>
<li class="list-group-item"><b>Implementation:</b> With inputs from system design, the system is first developed in small programs called units, which are integrated in the next phase. Each unit is developed and tested for its functionality which is referred to as Unit Testing.</li><br><br>
<li class="list-group-item"><b>Integration and Testing:</b> All the units developed in the implementation phase are integrated into a system after testing of each unit. Post integration the entire system is tested for any faults and failures.
</li><br><br>
<li class="list-group-item"><b>Deployment of system:</b> Once the functional and non-functional testing is done, the product is deployed in the customer environment or released into the market. </li><br><br>
<li class="list-group-item"><b>Maintenance:</b> There are some issues which come up in the client environment. To fix those issues patches are released. Also to enhance the product some better versions are released. Maintenance is done to deliver these changes in the customer environment.</li> <br><br>
</ul>
All these phases are cascaded to each other in which progress is seen as flowing steadily downwards (like a waterfall) through the phases. The next phase is started only after the defined set of goals are achieved for previous phase and it is signed off, so the name "Waterfall Model". In this model phases do not overlap.<br><br><br>
<b>3.2.2 Waterfall Model Application</b><br><br>
Every software developed is different and requires a suitable SDLC approach to be followed based on the internal and external factors. Some situations where the use of Waterfall model is most appropriate are:<br><br>
<ul class="list-group">
<li class="list-group-item">Requirements are very well documented, clear and fixed</li>
<li class="list-group-item">Product definition is stable.</li>
<li class="list-group-item">Technology is understood and is not dynamic.</li>
<li class="list-group-item">There are no ambiguous requirements.</li>
<li class="list-group-item">Ample resources with required expertise are available to support the product.</li>
<li class="list-group-item">The project is short.</li>
</ul><br><br>
<b>3.2.3 Advantage of Waterfall Model</b><br><br><br>
The advantage of waterfall development is that it allows for departmentalization and control. A schedule can be set with deadlines for each stage of development and a product can proceed through the development process model phases one by one.
Development moves from concept, through design, implementation, testing, installation, troubleshooting, and ends up at operation and maintenance. Each phase of development proceeds in strict order.<br><br>
<b>3.2.4 Disadvantages of Waterfall Model</b><br><br><br>
The disadvantage of waterfall development is that it does not allow for much reflection or revision. Once an application is in the testing stage, it is very difficult to go back and change something that was not well-documented or thought upon in the concept stage.

</h4>


<h4 class="panel-title">
<a data-toggle="collapse" data-parent="#accordion" href="#collapse31">
REASONS FOR USE........Page#18</a>
</h4>

<h4>
<b>3.2.5. REASONS FOR USE</b><br><br><br>
<ul class="list-group">

<li class="list-group-item">This model can be used when the requirements of the complete system are clearly defined and understood.</li>
<li class="list-group-item">Major requirements must be defined; however, some details can evolve with time.</li>
<li class="list-group-item">There is a need to get a product to the market early.</li>
<li class="list-group-item">A new technology is being used</li>
<li class="list-group-item">Resources with needed skill set are not available</li>
<li class="list-group-item">There are some high risk features and goals.</li>

</ul>
</h4>


<!-- End of chapter 3 System Analysis-->


<!-- start of chapter 4 System Design-->
<h1> Chapter #4 : System Design </h1><br><br>


<h4 class="panel-title">
<a data-toggle="collapse" data-parent="#accordion" href="#collapse32">
Chapter #4 : System Design</a>
</h4>

<img src="images/lesson4.png" class="img-responsive img-rounded">
<h4 style="margin-top:200px; text-align:center; margin-left:850px;"> Page19 </h4>

<h4 class="panel-title">
<a data-toggle="collapse" data-parent="#accordion" href="#collapse33">
4.1 Introduction:........Page#20</a>
</h4>

4.1 Introduction:

The purpose of System Design is to create a technical solution that satisfies the functional requirements for the system. During analysis, the focus is on what needs to be done intendment of how it is done. During design, decisions are made about how the problem will be solved, first at a high level, then at increasingly detailed levels.

System design is the first stage in which the basic approach to solving the problem is selected. During system designing the overall structure and style are decided. The system architecture is the overall organization of the system into components called system. System design deals with transforming the customer requirements, as described in the SRS document, into a form that is implement able using the programming language. Certain items such as modules, relationships among indentified modules, data should designed during this phase.

4.2 Overview:
This System Design provides the overall design of the “Event Quality Assurance & Development Management System” implemented during this project, covering the purpose and reasoning behind the system’s major components.

4.3 Scope:
The main scope of the system design is:
Organize the system into module .

Organization sub-modules for each module.

Allocates tasks to process.

Choose an approach to manage data store.

Handle access to global resource.

Choose implementation logic.

The basic idea behind System Design is to develop a software system incrementally, allowing the developer to take advantage of what was begin learned during the development of earlier, incremental, deliverable versions of the system



<h4 class="panel-title">
<a data-toggle="collapse" data-parent="#accordion" href="#collapse34">
4.4 Back Ground:........Page#21</a>
</h4>

4.4 Back Ground:

The “Event Management System( A case study of trade fair)” records basic customer information, Company order information, Visitor information, user information.
• Maker management function involves:

• Manage company records

• Visitors information

• User information

• Stall information

In “Event Quality Assurance & Development Management System” administrator has a Login ID and Password.
Admin has complete access to the whole system.

4.5 Applicable document-Methodology:

This web application is developed for managing Company details , user details , visitors details, employee details and stall details. As the project is user friendly, it can be applied to large database with more information. This software can use by any sanitary administrator to make their work simple. They can get information quickly as possible. It can handle large volume of data and present reports whenever required.

Structure of software package

The main functional components are:

• Administrator/Operator login

• Company details

• Stalls details

• User details

• Visitor details

• Log Out




<h4 class="panel-title">
<a data-toggle="collapse" data-parent="#accordion" href="#collapse35">
4.6 Risk:........Page#22</a>
</h4>

4.6 Risk:

The risk factors are:

1. In case the database lost because of some OS failure or because of Antivirus actions the software should have option for restore data.

2. The restore is possible only if the backup maintained by the company and user/visitors is up to date .

3. Otherwise the restore may failure or the restore point may not be up to date.

Update Requirement Compliance Matrix:

Since we are using ASP.NET 3.5 version SQL server 2012 version, if there is any update , upgrade Apache IIS ( Integrated Information/Internet service) to update ASP.NET and SQL.

System Description:

The software is decomposed into several modules for the convenience of the user. The operator enters the company details, Visitors/user details , stalls details. In this all information are already stored details and account details. In this all information are already stored in access. Here we can insert, update or delete the existing records.


<h4 class="panel-title">
<a data-toggle="collapse" data-parent="#accordion" href="#collapse36">
4.7 External Interface:........Page#23</a>
</h4>


4.7 External Interface:

A. Name of application
“Event Management System( A case study of Trade fair)”

B. Details of interface

Admin login

4.8 Description of program:

Context Flow Diagram.

Data Flow Diagram.

4.9 Context Flow Diagram (CFD):

A context Flow Diagram is a top level (also known as level 0) data flow data diagram. It only contains one process node (process 0) that generalizes the function of the entire system in relationship to external entities. In context diagram the entire system is treated as a single process and all its inputs outputs, sinks and source are indentified and shown.


The Notation used in flow diagram are:

• Bubble: The Bubble represents a process or transmutation that is applied to the data which changes in some way. Each bubble is assigned a number.

• Box: The Box is called an entity which represents a product or a customer of the information.

• Arrow: The arrow represents the data flow. All arrows in the data flow diagram are labeled. The arrowhead indicates the direction of data flow.

• Parallel: Represents a repository of data that is to be stored for use by one or more process.


<h4 class="panel-title">
<a data-toggle="collapse" data-parent="#accordion" href="#collapse37">
4.10 Data Flow Diagram (DFD):........Page#24</a>
</h4>

<img src="images/cfd.png" width="800px" height="300px">
<h2>Fig: 4.1 Context Flow Diagram.</h2>

4.10 Data Flow Diagram (DFD):

A Data Flow Diagram (DFD) is a graphical representation of the “Flow” of data through an http://en.wikipedia.org/wiki/information system Information system. A through flow diagram can also be used for the visualization of Data processing. It is common practice for a designer to draw a context-level DFD first which shows the interaction between the system and outside entities. This context-level DFD is then “exploded” to show more detail of the system being modeled.

A DFD represents flow of data through a system. Data f low diagram are commonly use during problem analysis. It views a system as a function that transforms the input into desired output. A DFD shows movement of data through the different transformations or processes in the system.

Data flow diagrams can be used to provide the end user with a physical idea of where the data they input ultimately has an effect upon the structure of the whole system from order to dispatch to restock how any system is developed can be determined through a data flow diagram. The appropriate register saved n database and maintained by appropriate authorities.


<h4 class="panel-title">
<a data-toggle="collapse" data-parent="#accordion" href="#collapse38">
4.11: Data Flow Diagram Notations........Page#25</a>
</h4>

<img src="images/cfd2.png">
<h2>Fig: 4.2 Data Flow Diagram Notation .</h2>



<h4 class="panel-title">
<a data-toggle="collapse" data-parent="#accordion" href="#collapse39">
4.12: Context Flow Diagram Use for Admin........Page#26</a>
</h4>


<img src="images/cfd3.png">
<h2>Fig: 4.3 Context Flow Diagram use for admin .</h2>

<h4 class="panel-title">
<a data-toggle="collapse" data-parent="#accordion" href="#collapse40">
Top level 0 : ........Page#27</a>
</h4>


<h2>Top level 0 : </h2><br>
<img src="images/cfd0.png"><br><br>
<p>Fig: 4.4 Context Flow Diagram Level 0-</p>
<h2>L 01: Logic Design</h2><br>
<img src="images/logic_design.png"><br><br>
<p>Fig: 4.5 Context Flow Diagram Level 01.</p>



<h4 class="panel-title">
<a data-toggle="collapse" data-parent="#accordion" href="#collapse41">
L2 Logical design........Page#28</a>
</h4>

<h2>L2 Logical design: </h2><br>
<img src="images/l2_logic_design.png"><br><br>
<p>Fig: 4.6 Context flow diagram Level 02.</p>
 

<h4 class="panel-title">
<a data-toggle="collapse" data-parent="#accordion" href="#collapse42">
L3........Page#29</a>
</h4>

<h2>L3</h2><br>
<img src="images/l3_logic_design.png"><br>
<p>Fig4.7: L3 Context Flow diagram Level 03</p>


<h4 class="panel-title">
<a data-toggle="collapse" data-parent="#accordion" href="#collapse43">
L4........Page#30</a>
</h4>

<h2>L4</h2><br>
<img src="images/l4_logic_design.png"><br>
<p>Fig4.7: L4 Context Flow diagram Level 04</p>

<h4 class="panel-title">
<a data-toggle="collapse" data-parent="#accordion" href="#collapse44">
4.9 : Context Flow Diagram Web server........Page#31</a>
</h4>


<img src="images/cfd_ws.png"><br>
<p> Fig 4.9 : Context Flow Diagram Web server.</p>


<h4 class="panel-title">
<a data-toggle="collapse" data-parent="#accordion" href="#collapse45">
4.13 : Work Flow Diagram........Page#32</a>
</h4>

<h2>4.13 : Work Flow Diagram</h2><br>
<img src="images/wfd.png"><br>
<p>Fig 4.10: Work Flow Diagram</p>

<h4 class="panel-title">
<a data-toggle="collapse" data-parent="#accordion" href="#collapse46">
4.14. UML DIAGRAMS........Page#33</a>
</h4>

4.14. UML DIAGRAMS

Design is the place where quality is fostered in software development. Design is the only way that we can accurately translate a user’s requirements into a finished software product or system. Software design serves as the foundation for all software engineers and software engineers and software maintenance steps that follow. Without changes are made, one that may be difficult to test, and one whose quantity cannot be assessed until late in the software engineering process.

Taking software requirements specification document of analysis phase as input to the design phase we have drawn Unified Modeling Language (UML) diagrams. UML depends on the Visual modeling of the system. Visual modeling is the process of taking the information from the model and displaying it graphically using some sort of standards setoff graphical elements.

UML Diagrams are drawn using the Visual Paradigm Software. We seem to be able to understand complexity better when it is displayed to us visually as opposed to written textually. By producing visual models of a system, we can show how system works on several levels. We can model the interactions between the users and the system.
4.15. TYPES OF UML DIAGRAM

Each UML diagram is designed to let developers and customers view a software system from a different perspective and in varying degrees of abstraction. UML Diagram commonly created in visual modeling tools include;


<h4 class="panel-title">
<a data-toggle="collapse" data-parent="#accordion" href="#collapse47">
4.16 . E-R DIAGRAM ........Page#34</a>
</h4>

4.16 . E-R DIAGRAM

An entity-relationship diagram (ERD) is a graphical representation of an information system that shows the relationship between people, objects, places, concepts or events within that system. An ERD is a data modeling technique that can help define business processes and can be used as the foundation for a relational database.

4.16.1. SYSTEM DATABASE DIAGRAM


<img src="images/sdd.png">

<h4 class="panel-title">
<a data-toggle="collapse" data-parent="#accordion" href="#collapse48">
4.16.2 System E-R Diagram........Page#35</a>
</h4>

<h2>4.16.2 System E-R Diagram</h2><br>
<img src="images/er.png"><br><br>
<p>Fig: 4.11: E-R diagram.</p>

4.17: CSS Basic Concept:

CSS stands for Cascading Style Sheets

CSS describes how HTML elements are to be displayed on screen, paper, or in other media

CSS saves a lot of work. It can control the layout of multiple web pages all at once

External style sheets are stored in CSS files.

CSS is used to define styles for your web pages, including the design, layout and variations in display for different devices and screen sizes.




<h4 class="panel-title">
<a data-toggle="collapse" data-parent="#accordion" href="#collapse49">
4.18: HTML Basic:........Page#36</a>
</h4>

4.18: HTML Basic:

HTML is a markup language for describing web documents (web pages).

 HTML stands for Hyper Text Markup Language

 A markup language is a set of markup tags

 HTML documents are described by HTML tags

 Each HTML tag describes different document content

4.19: Java Script Concept:

JavaScript is a very flexible language. In contrast with Java, PHP, C++ and many other languages, there are many ways to implement OOP in JavaScript.

The three main features should be supported:

Inheritance

It is possible to create a child object Tree Menu which extends functionality of the Menu.

The child object automatically gains access to parent’s methods/properties, but it also can have own methods/properties

That’s great, because allows to reuse generic Menu code for Tree Menu, Sliding Menu and other specific menu types.

Encapsulation

An object can forbid external access to chosen properties and methods, so that they can only be called by other methods of same object.

That allows to hide internal details of Menu.

For example, the code which uses a Menu should not directly access it’s DOM structure, handler etc. They are internal.

On the other hand, there should be open, hide and other publicly accessible methods. These methods are called an external(or public) interface.

There are three most well-known encapsulation levels:

private

Accessible only from the class itself, not accessible from inheritants.

protected

Accessible from the class itself, inheritants are also allowed to access it.

public

Accessible from anywhere




<h4 class="panel-title">
<a data-toggle="collapse" data-parent="#accordion" href="#collapse50">
Type polymorphism........Page#37</a>
</h4>


Encapsulation helps to support the code, because a programmer always knows, which methods could have been used by the external code, and which can be safely modified or even removed.

Type polymorphism

A code which uses the Menu object can switch to a Tree Menu object or a Sliding Menu without modifications.

It’s possible, because the public interface of Menu is inherited.

In JavaScript, unlike most other languages, there are several syntactically different ways to do implement the OOP concepts described above.



<!-- End of chapter 4 System Design-->

<!--Start of Chapter 5 Implementation-->
<h1> Chapter #5 : Implementation </h1><br><br>


<h4 class="panel-title">
<a data-toggle="collapse" data-parent="#accordion" href="#collapse51">
Chapter #5 : Implementation</a>
</h4>

<img src="images/lesson5.png" class="img-responsive img-rounded">
<h4 style="margin-top:200px; text-align:center; margin-left:850px;"> Page19 </h4>



<h4 class="panel-title">
<a data-toggle="collapse" data-parent="#accordion" href="#collapse52">
5.1 Modules.........Page#39</a>
</h4>


5.1 Modules

A module consists of a group of procedures, which are called from the host programming language. Each procedure contains a single SQL statement, and data is passed to and from the procedure through parameters.

5.2 Front End Technology

5.2.1 ASP.NET

ASP.NET is a unified Web development model that includes the services necessary for you to build enterprise-class Web applications with a minimum of coding. ASP.NET is part of the .NET Framework, an