Janardan Bhagat Shikshan Prasarak Sanstha’s

CHANGU KANA THAKUR

Arts, Commerce, Science College
New Panvel (W)
A PROJECT REPORT ON
“Online Event Management System”
SUBMITED TO

“UNIVERSITY OF MUMBAI”
BY
Mr. Prakash Gaikwad

Under The Guidance Of

Prof. Mrs. Priya Shenoy

2015-2016
Sr. No Contents Page No.
1 Introduction
2 Analysis
Project History
Problem with Existing System
Requirement Gathering
Objective and Scope of Project
Advantage Of Proposed System
Requirement Specification
3 Gantt Chart
4 Design Phase
E-R Diagram
Event Table
Use Case Diagram
Class Diagram
Activity Diagram
Sequence Diagram
5 Coding Phase
Data Base Design
Forms
Reports

6 Testing Phase
7 Maintenance And Evaluation
System Maintenance
Future Enhancement
8 References & Bibliography
Introduction
 INTRODUCTION

Our website is especially design to reduce the communication gap between event planner
and clients. Clients can manage an event according to his wish sitting at his place. Client a large
variant of event elements.

The basic idea behind designing this website is that the user can plan the event according
to his requirement, needs and budget.

Customers may view the contents of any event show at any time and may book any event
ticket as needed. The program automatically calculates the subtotal and grand total.
When a visitor decides to finally book the ticket, the order information including the
buyer’s name, address and billing instruction is stored in the database securely and payment has
been made.
Our website also provide facility to organize their own event and publish it over the
internet.
You need to register a new user whenever you have first visited or site then for future it
will be stored in our database permanently and you can book your event ticket at any time you
want with this username and password.
Analysis
 PROJECT HISTORY

Our website serves the functionality of an event manager. The system allows only registered
users to login and new users are allowed to resister on the application. The project provides most
of the basic functionality required for an event.
It allows the user to select from a list of event types. Once the user enters an event type, the
system then allows the user to select the date and time of event, place and the event equipment’s.
All this data is logged in the database and the user is given a receipt number for his booking.
This data is then sent to the administrator (website owner) and they may interact with the client
as per his requirements and his contact data stored in the database.
E-Ticket system is basically made for providing the system an anytime and anywhere service
for booking ticket for event and to gather information about the event online. The user can easily
be able to know about the event scheduled and then make the choice.
 Problem with existing System

 It is having lots of manual work to maintain all customer record.

 It is time consuming process.

 The present system is very less secure.

 It is having less interaction with clients.

 It is also not having facility to publish events online


 Requirement Gathering

 The web page (e.g. the time table page, the main page) will be generated automatically
according to the data in database.
 A way in which the customer can create its own account (member registration).
 A way in which the users can login to the system to perform different operation.
 A way in which the customer can modify its own data.
 A way in which the customer can cancel the booking and get the refund.
 A way in which the customer can check the ticket record according to the transaction
number.
 A way in which the admin can use the system to add data (e.g. film description) to the
database.
 The system can generate the time table automatically or the time table is set by the
admin.
 The system can generate some statistic information according booking and ticket selling
record.
 Users can check event information by clicking on a certain event on main page
 Objectives and Scope of Project

The system after careful analysis has been identified to be presented with the following objective
and its scope:

The objectives involved are:

1. Administration
2. Client
3. Advertisement
4. Report
5. Authentication

Administration:-
Admin has all privileges to add/modify services details and appointment information etc.
1. Add new Offers
2. Manage events
3. Analysis the report

Client:-
In this module again divided into 4 module
1. Client Details
2. Advance Booking
3. Booking for occasions
4. Create new event

Advertisement:-
In this module admin and client post event information on site. User can create account and sent
request for booking event passes to admin.
Authentication:-

This module contains all the information about the authenticated user. User without his username
and password can’t enter into the login if he is only the authenticated user then he can enter to
his login.

Report:-
 This module is used to print various online reports. This module will be enabled only to
the admin type of users.
 In this admin generate various types of reports about the employees working in the
organization.
 In this admin generate various types of billing reports which are generated by employees
working in the organization.
 On the base of all billing report admin can set new offer to customer.
 Advantage of Proposed System

Our System is a web-based system. The customers can buy ticket online and cancel at a
suitable time (2 days before the show to 1hour before the show).
To enhance the refund function, all the customers have to registration become a member
before buying ticket.
The development of the new system contains the following activities, which try to automate
the entire process keeping in view of the database integration approach.

 User friendliness is provided in the application with various controls.

 The system makes the overall project management much easier and flexible.

 It can be accessed over the Internet.

 There is no risk of data mismanagement at any level while the project development is

under process.
 REQUIREMENT SPECIFICATION

 HARDWARE REQUIREMENT

Hard Disk: Minimum 50GB HDD

RAM: Minimum 2 GB

CPU Type: Pentium dual-core 2.50GHz onwards

 SOFTWARE REQUIREMENT

Operating Systems Windows 7 and onwards

Front End: Microsoft Visual Studio 2012

Back End: Microsoft SQL Server 2008

 Front-End Used: ASP.net

Today virtually all websites contain dynamic web pages of one kind or another. Any site
that allows a user to search the site's content, order products, or customize the site's content is
dynamic in nature. There are a plethora of technologies for creating dynamic pages, one of the
best ones being ASP.NET.

 Advantages of ASP.net
 ASP.NET provides security by hiding the code.
 It is user friendly.
 It supports session variables.
 ASP.NET is compiled language means display errors at the time of compilation.
  BACK-END USED: MICROSOFT SQL SERVER 2008

Microsoft SQL Server 2008 is a relational database management system (RDBMS)

produced by Microsoft. Its primary query language is Transact-SQL, an implementation of the
ANSI/ISO standard Structured Query Language (SQL). SQL ("Structured Query Language") is
an ANSI Standard computer language commonly used to access data stored in databases. SQL is
a tool for managing, organizing, and retrieving data stored in a computer database. SQL works
with relational databases which all organize data into tables, rows, and columns which
correspond to files, records and fields.
When you need to retrieve data from a database, you use the SQL language to make the
request. The DBMS processes the SQL request, retrieves the requested data and returns it to you.
This process of requesting data from a database and retrieving back the results is called a
database query-hence the name structured.
Gantt Chart
Gantt chart
Design Phase
 E-R Diagram

The Entity Relationship Diagram (Model) is based on perception of a real world that consists of
a collection of basic objects called as Entity and relationships among these objects. Entities in
database are described as set of attributes.

 A Relationship is an association among several Entities.

 The set of Entities of the same type are called as Entity Set.

 The set of Relationships of same type are called as Relationship Set.

A graphical model of the data needed by the system, including think about which
information is stored and the relationship among them, produced in structured analysis and
information engineering.

The relational approaches to system development places a great deal of emphasis on data
storage requirements include the data entities, their attributes and the relationship among the data
entities. The model used to define the data storage requirements is called the Entity Relationship
Diagram.

On the Entity Relationship Diagram, a rectangle represents data entities, and lines
connecting the rectangle show the relationship among data entities.

Entities-relationship analysis uses three major abstractions to describe data.

1) Entity:- Represents Data Entity

2) Attribute:-Attributes

3) Relationship:- Represents the relationship

4) Relationship:-Connection between two or more entities

 Password
UserName

Admin

View User
info
BookingID

EventID
Create Admin
Booking
EventName

NoOfPasses
Date EventDate

Book
Event NoOfPasses
event

EventID
EventName
 Event Table

A table that list events in tabular format that is in rows and key pieces of information about each
event in columns is known as event table.
While developing the list of events, the analyst should note additional information about each
this information is entered in an event table.
An event table comprises of rows and columns. Each row in an event table records information
about one event and each column is about its key piece of information about that event.
Attributes of Event Table:
Trigger:
An occurrence that tells the system that has occur, either the arrival of data needing or of a point
in time.
Source:
An external agent or actor that is supplies data to the system.
Activity:
Behavior of that the system performs when an event occur.
Response:
An output produce by the system, that goes to a destinations.
Destination:
An external agent or an actor that is receives data from system.
 Event Trigger Source Activity Response Destination

want to Account User Registration Account User

Register form creating info.

User login Login User Authentication Valid/Invalid User

Booking Book User Advance Show booking User

booking info.

Create New Create User Fill Event Detail Event Created User
Event

Event collection Admin calculation Profit Info Admin

collection

Event collection User calculation Profit Info User

Collection
 Use Case Diagram

The use case diagrams describe system functionality as set of task that the system must carry out
and the actor who interact with the system to complete the tasks.
Use Case:
Each of use case on the diagram represents a single task that the system needs to carry out. Buy a
product, add client, make purchase and validate order information are all example of use case.
Some use cases may include or extends task represent by another use case.
Actor:
An actor is anything outside the system that interacts with system to complete a tasks. The actor
“uses” the use case to complete a task.
 System
Registration

Login

Create Event

Update
View Event Details

Event selection

Admin
Booking

User
Payment
Update
View
Status

Reports
 Class Diagram

The class diagram is the main building block of object oriented modelling. It is used both for
general conceptual modelling of the systematic of the application, and for detailed modelling
translating the models into programming code. Class diagram can also be used for modelling.
The classes in a class diagram represent both main objects, interactions in the applications and
the classes to be programmed.
A class with 3 sections.
In the diagram, classes are represented with boxes which contains 3 parts:
The upper part holds the name of the class.
The middle part contains the attributes of the class.
The bottom parts gives the methods or operations the class can take or undertake.
In the design of the system, a number o classes are identified and grouped together in a class
diagram which helps to determine the static relation between those objects. With detailed
modelling, the classes of conceptual design are often split into a number of sub classes.
In order to further describe the behavior of systems, this class diagram can be complemented by
state diagram or UML state machine.
The class diagram is the main building block of object oriented modelling. It is used both for
general conceptual modelling of the systematic of the application, and for detailed modelling
translating the models into programming code. Class diagram can also be used for modelling.
The classes in a class diagram represent both main objects, interactions in the applications and
the classes to be programmed.
A class with 3 sections.
In the diagram, classes are represented with boxes which contains 3 parts:
The upper part holds the name of the class.
The middle part contains the attributes of the class.
The bottom parts gives the methods or operations the class can take or undertake.
In the design of the system, a number o classes are identified and grouped together in a class
diagram which helps to determine the static relation between those objects. With detailed
modelling, the classes of conceptual design are often split into a number of sub classes.
In order to further describe the behavior of systems, this class diagram can be complemented by
state diagram or UML state machine.
 Activity Diagram

Activity diagrams are mainly used as flow chart consists of activities performed by the system.
But activity diagram are not exactly a flow chart as they have some additional capabilities.
Before drawing an activity diagram we must have a clear understanding about the elements used

BookingDetail
+Bookingid: Integer
+eventid: Integer
Event +eventname: String
User +noofticket: Integer
+EventId: Integer
+Uid: Integer +EventName: String +price: Float
+UserName: String +Description: String +total: Float
+UserId: String +Venue: String +fullname: String
+Password: String +StartDate: String +emailid: String
+StartTime: String +mobileno: String
+Signin() +EndDate: String +cardno: String
+SignOut() +EndTime: String +nameoncard: String
+BookTicket() +ticketType: String +expiry: String
+Price: Float
+EventPoster
+ticketName: String
+EventOwner: String
+generateReport() Payment
+updateBookingInfo() +Bookingid: Integer
EventManager
+eventid: Integer
+Uid +eventname: String
+UserName +noofticket: Integer
+UserId +price: Float
+Password +total: Float
+fullname: String
+Signin() +cardno: String
+Signout() +nameoncard: String
+BookTicket() +expiry: String
+CreateEvents()
+ManageEvent()
+viewEventReport()

in activity diagram. The main elements of an activity diagram is the activity itself. An activity is
the function performed by the system. After identifying the activities we need to understand how
they are associated with constraints and conditions.
So before drawing an activity diagram we would identify the following elements:
 Activity
 Association
 Condition
  Constraint

Once the above mentioned parameters are identified we need to make a mental layout of the
entire flow. This mental layout is then transformed into an activity diagram.
Basic Activity Diagram Symbols and Notations:
Action State:
Action States represent the non-interruptible action of objects. You can draw an action state in
Smart Draw using a rectangle with rounded corners.
Action Flow:
Action Flow arrows illustrate the relationships among action states.
Initial State:
Following arrows represents the initial action states.
Object Flow:
Object flow refers to the creation and modification of objects by activities. An object flow arrow
from an action to an object means that the action creates or influence the object. An object flow
arrow from an object to an action indicates that the action state uses the objects.
Final State:
An arrow pointing to an circle represent the final action state.
Branching:
A diamonds represents a decision with alternate paths. The outgoing alternates should be labelled
with a condition or guard expression. You can also label one of the path “else”.
Synchronization:
A synchronization bar helps illustrate parallel transitions. Synchronization is also called as
forking and joining.
 Is No
Registered Registration

Yes

Login

No
Is Valid

Yes

Selection Creation

Event

Booking

Payment

Logout
 Sequence Diagram

 A Sequence diagram shows object interactions arranged in time sequence.

 It depicts the objects and classes involved in the scenario and the sequence of messages

exchanged between the objects needed to carry out the functionality of the scenario.

 Sequence diagram typically are associated with use case realization in the logical view

of system under deployment.

 Sequence diagrams are sometimes called as event diagrams.

User Event Booking Bill

1 : create()

2 : select()

3 : Booking for passes/ticket()

4 : Pay()

5 : status()
 Coding Phase

DATA BASE DESIGN

Tables
tblUser
Field Name Data type Constraints Size
Uid Int Primary Key 10
UserName VARCHAR2 20
Email VARCHAR2 20
Password VARCHAR2 20

Event Table
Field Name Data type Constraints Size
EventID INT Primary Key 10
EventName VARCHAR2 20
Description VARCHAR2 20
Category VARCHAR2 20
Venue VARCHAR2 50
StartDate Date
StartTime VARCHAR2 20
EndDate Date
EndTime VARCHAR2 20
TicketType VARCHAR2 20
Price DECIMAL(18,2) 20
EventPoster Image
ticketName Varchar2 50
Eventowner Varchar2 50
tblBooking
Field Name Data type Constraints Size
Bookingid Int Primary Key 10
EventID VARCHAR2 50
EventName VARCHAR2 50
NoOfTickets Int 20
Price Decimal 20
Total Decimal 20
FullName Varchar2 50
Emailid Varchar2 50
MobileNo Varchar2 50
Cardno Varchar2 50
Nameoncard Varchar2 50
Expiry Varchar2 50
 Forms
Home.aspx

Events.aspx
Sign in.aspx
CreateEvent.aspx

Dashboard.aspx
DashboardEventPreview.aspx

EventReport.aspx
EventPreview.aspx

MakePaymentFree.aspx
EventPreview.aspx

MakePayment.aspx
PrintTicket.aspx

PrintTicketHere.aspx
Testing Phase
 TESTING:
Testing is an empirical investigation conducted to provide stakeholders with information
about the quality of the product or service under test, with respect to the context in which it is
intended to operate. Testing also provides an objective, independent view of the software to
allow the business to appreciate and understand the risks at implementation of the system. Test
techniques include, but are not limited to, the process of executing a program or application with
the intent of finding software bugs.

Testing, depending on the testing method employed, can be implemented at any time in
the development process, however the most test effort is employed after the requirements have
been defined and coding process has been completed.

METHODOLOGIES USED FOR TESTING

V-MODEL:-

V- Model means Verification and Validation model. Just like the waterfall model, the V-
Shaped life cycle is a sequential path of execution of processes. Each phase must be
completed before the next phase begins.  Testing of the product is planned in parallel with a
corresponding phase of development.
The various phases of the V-model are as follows:

Requirements like BRS and SRS begin the life cycle model just like the waterfall model. But, in
this model before development is started, a system test plan is created.  The test plan focuses on
meeting the functionality specified in the requirements gathering.

The high-level design (HLD) phase focuses on system architecture and design. It provide
overview of solution, platform, system, product and service/process. An integration plan is
created in this phase as well in order to test the pieces of the software systems ability to work
together.

The low-level design (LLD) phase is where the actual software components are designed. It
defines the actual logic for each and every component of the system. Class diagram with all the
methods and relation between classes comes under LLD. Component tests are created in this
phase as well.

The implementation phase is, again, where all coding takes place. Once coding is complete, the
path of execution continues up the right side of the V where the test plans developed earlier are
now put to use.

Coding This is at the bottom of the V-Shape model. Module design is converted into code by
developers.

Validation Phases:-
In the V-model, each stage of verification phase has a corresponding stage in the validation
phase. The following are the typical phases of validation in the V-Model, though they may be
known by other names.

Unit testing
In the V-Model, Unit Test Plans (UTPs) are developed during module design phase. These UTPs
are executed to eliminate bugs at code level or unit level. A unit is the smallest entity which can
independently exist, e.g. a program module. Unit testing verifies that the smallest entity can
function correctly when isolated from the rest of the codes/units.
Integration testing
Integration Test Plans are developed during the Architectural Design Phase. These tests verify
that units created and tested independently can coexist and communicate among themselves. Test
results are shared with customer's team.

System testing
System Tests Plans are developed during System Design Phase. Unlike Unit and Integration Test
Plans, System Test Plans are composed by client's business team. System Test ensures that
expectations from application developed are met. The whole application is tested for its
functionality, interdependency and communication. System Testing verifies that functional and
non-functional requirements have been met. Load and performance testing, stress testing,
regression testing, etc., are subsets of system testing.

User acceptance testing

User Acceptance Test (UAT) Plans are developed during the Requirements Analysis phase. Test
Plans are composed by business users. UAT is performed in a user environment that resembles
the production environment, using realistic data. UAT verifies that delivered system meets user's
requirement and system is ready for use in real time.

Advantages of V-model:

 Simple and easy to use.

 Testing activities like planning, test designing happens well before coding. This
saves a lot of time. Hence higher chance of success over the waterfall model.
 Proactive defect tracking – that is defects are found at early stage.
 Avoids the downward flow of the defects.
 Works well for small projects where requirements are easily understood.
Disadvantages of V-model:

 Very rigid and least flexible.

 Software is developed during the implementation phase, so no early prototypes of
the software are produced.
 If any changes happen in midway, then the test documents along with requirement
documents has to be updated.

When to use the V-model:

 The V-shaped model should be used for small to medium sized projects where
requirements are clearly defined and fixed.
 The V-Shaped model should be chosen when ample technical resources are available
with needed technical expertise.

TYPES OF TESTING

WHITE BOX TESTING

White-box testing is a method of testing the application at the level of the source code.
These test cases are derived through the use of the design techniques mentioned above: control
flow testing, data flow testing, branch testing, path testing, statement coverage and decision
coverage as well as modified condition/decision coverage. White-box testing is the use of these
techniques as guidelines to create an error free environment by examining any fragile code.
These White-box testing techniques are the building blocks of white-box testing, whose essence
is the careful testing of the application at the source code level to prevent any hidden errors later
on. These different techniques exercise everys visible path of the source code to minimize errors
and create an error-free environment. The whole point of white-box testing is the ability to know
which line of the code is being executed and being able to identify what the correct output should
be.
Advantages

1. Side effects of having the knowledge of the source code is beneficial to thorough testing.
2. Optimization of code by revealing hidden errors and being able to remove these possible
defects.
3. Gives the programmer introspection because developers carefully describe any new
implementation.
4. Provides traceability of tests from the source, allowing future changes to the software to
be easily captured in changes to the tests.
5. White box tests are easy to automate.
6. White box testing give clear, engineering-based, rules for when to stop testing.

Disadvantage

1. White-box testing brings complexity to testing because the tester must have knowledge of
the program, including being a programmer. White-box testing requires a programmer
with a high-level of knowledge due to the complexity of the level of testing that needs to
be done.
2. On some occasions, it is not realistic to be able to test every single existing condition of
the application and some conditions will be untested.
3. The tests focus on the software as it exists, and missing functionality may not be
discovered.

BLACK BOX TESTING

Black-box testing is a method of software testing that examines the functionality of an

application without peering into its internal structures or workings. This method of test can be
applied to virtually every level of software testing: unit, integration, system and acceptance. It
typically comprises most if not all higher level testing, but can also dominate unit testing as well.
Tools used for Black Box testing
Black box testing tools are mainly record and playback tools. These tools are used for
regression testing that to check whether new build has created any bug in previous working
application functionality. These record and playback tools records test cases in the form of some
scripts like TSL, VB script, Java script, Perl.

Advantages of Black Box Testing

– Tester can be non-technical.

– Used to verify contradictions in actual system and the specifications.
– Test cases can be designed as soon as the functional specifications are complete

Disadvantages of Black Box Testing

– The test inputs needs to be from large sample space.

– It is difficult to identify all possible inputs in limited testing time. So writing test cases is slow
and difficult
– Chances of having unidentified paths during this testing

Methods of Black box Testing

Graph Based Testing Methods

Each and every application is buildup of some objects. All such objects are identified and
graph is prepared. From this object graph each object relationship is identified and test cases
written accordingly to discover the errors.

Error guessing
this is purely based on previous experience and judgment of tester. Error Guessing is the
art of guessing where errors can be hidden. For this technique there are no specific tools, writing
the test cases that cover all the application paths.

Boundary Value Analysis:

Many systems have tendency to fail on boundary. So testing boundary values of
application is important. Boundary Value Analysis (BVA) is a test Functional Testing technique
where the extreme boundary values are chosen. Boundary values include maximum, minimum,
just inside/outside boundaries, typical values, and error values.Extends equivalence
partitioningTest both sides of each boundary
Look at output boundaries for test cases tooTest min, min-1, max, max+1, typical values.

Equivalence partitioning:
Equivalence partitioning is a black box testing method that divides the input domain of a
program into classes of data from which test cases can be derived.
RequiredField Validation
 MAINTENANCE:
 In software engineering, software maintenance is the modification of a software product after
delivery to correct faults, to improve performance or other attributes, or to adapt the product
to a modified environment.
 This international standard describes the 6 software maintenance processes as:

 The implementation process contains software preparation and transition activities,

such as the conception and creation of the maintenance plan, the preparation for
handling problems identified during development, and the follow-up on product
configuration management.

 The problem and modification analysis process, which is executed once the
application has become the responsibility of the maintenance group.

 The maintenance programmer must analyze each request, confirm it (by

reproducing the situation) and check its validity, investigate it and propose a
solution, document the request and the solution proposal, and, finally, obtain all the
required authorizations to apply the modifications.

 The process considering the implementation of the modification itself.

 The process acceptance of the modification, by checking it with the individual who
submitted the request in order to make sure the solution provided a solution.

 The migration process (platform migration, for example) is exceptional, and is not
part of daily maintenance tasks.

 If the software must be ported to another platform without any change in

functionality, this process will be used and a maintenance project team is likely to
be assigned to this task.
  Finally, the last maintenance process, also an event which does not occur on a daily
basis, is the retirement of a piece of software.

 Software will undoubtedly undergo changes after it has been delivered to the user.

 Change will occur because errors have been encountered, because the software
must be adapted to accommodate changes in external environment or because the
user requires functional or personal enhancements.

 Software maintenance reapplies each of the preceding life cycle steps to an existing
program rather than a new one.

 The basic idea of the Software Developed Life Cycle method is that there is well-
defined process by which the application is conceived, developed and implemented.
It gives the structure to a creative process.

 The phases in the Software Developed Life Cycle provides a basis for management
and control because they define segments of flow of work which can be identified
for management purpose and specify the documents or other deliverables to be
procured in each phase.

 A thorough analysis of the existing system is done and the new requirements for the
proposed system are studied.

 The entire application is modularized considering the features required for the
proposed system.

 There are 4 categories of maintenance:

1. Corrective maintenance: Reactive modification of a software product

performed after delivery to correct discovered problems.

2. Adaptive maintenance: Modification of a software product performed after

delivery to keep a software product usable in a changed or changing
environment.
 3. Perfective maintenance: Modification of a software product after delivery to
improve performance or maintainability.

4. Preventive maintenance: Modification of a software product after delivery to

detect and correct latent faults in the software product before they become
effective faults

Maintenance Activities:

 Identification & Tracing - It involves activities pertaining to identification of

requirement of modification or maintenance. It is generated by user or system may itself
report via logs or error messages. Here, the maintenance type is classified also.
 Analysis - The modification is analysed for its impact on the system including safety and
security implications. A set of required modifications is then materialized into
requirement specifications. The cost of maintenance is analysed and estimation is
concluded.
 Design - New modules, which need to be replaced or modified, are designed against
requirement specifications set in the previous stage. Test cases are created for validation
and verification.
 Implementation - The new modules are coded with the help of structured design created
in the design step. Every programmer is expected to do unit testing in parallel.
 System Testing - Integration testing is done among newly created modules. Integration
testing is also carried out between new modules and the system. Finally the system is
tested as a who
 le, following regressive testing procedures.
 Acceptance Testing - After testing the system internally, it is tested for acceptance with
the help of users. If at this state, user complaints some issues they are addressed or noted
to address in next iteration.
 Delivery - The final testing takes place at client end after the software is
delivered.Training facility is provided if required, in addition to the hard copy of user
manual.
  Maintenance management - Configuration management is an essential part of system
maintenance. It is aided with version control tools to control versions, semi-version or
patch management.

Evaluation:

Evaluation, is the structured interpretation and giving of meaning to predict or actual impacts
of proposals or results. It looks at original objectives, and at what is either predicted or what
was accomplished and how it was accomplished. So evaluation can be formative that is
taking place during the development of a concept or proposal, project or organization, with
the intention of improving the value or effectiveness of the proposal, project, or organisation.
It can also be assumptive, drawing lessons from a completed action or project or an
organisation at a later point in time or circumstance.

Evaluation nature and scope

A software evaluation is done for someone.  Someone wants to know about the state of a

particular package, and may even be paying you to look into it!  So, at the outset, you should
agree with this "someone" the scope of the evaluation.  This includes what software and other
project resources will be evaluated and the user classes from whose perspective the evaluation
will be done. The following classes of user can be assumed:

 User. A person who, depending on the artefact, downloads, installs, configures and uses
the artefact but does not write any code to use in conjunction with it. The software may
be a web portal, a GUI or a command-line tool.
 User-Developer. A user who writes code which extends but does not change the software
e.g. a client to some service endpoints, or a pluggable component coded against some
extensibility point. As an analogy, a developer of web services using Apache Axis.
 Developer. A user who writes code that changes the software e.g. fixes bugs, makes the
software more efficient, or extends its functionality. As an analogy, someone who
changes Apache Axis to make WSDL2Java easier to use.
 Member. A Developer who is a project member and has write access to the source code
repository. Unlike a Developer, a Member has to be aware of such issues as what the
policy is on upgrading to use new versions of prerequisite packages, coding standards,
who owns copyright, licensing, how changes are managed.
 FUTURE
ENHANCEMENT

Future Enhancement:
Future enhancement is an approach to web development that aims to deliver the
best possible experience to the widest possible user — whether your users are viewing your sites
on a Mobile, a high-end desktop system, a Kindle, or hearing them on a screen-reader, their
experience should be as fully featured and functional as possible With an ever-growing variety of
browsing situations and platforms that must be supported, the concept of Future enhancement
has become an important topic of conversation. Put simply, Future enhancement is the technique
of building websites with strong foundations so that it’s accessible to the wide range of browsing
situations — from mobile devices and notebooks, to desktops and screen-readers, so your user
always remember you in the future In its simplest conceptualization, Future enhancement is the
separation of HTML, CSS and JavaScript. That’s it, really. If you had to remember one thing
about Future enhancement, it should be that.
Think of these web technologies as being in layers, with HTML as the first layer, CSS being the
second, and JavaScript (and other client-side technologies that deal with site interactivity, such
as Flash or Java applets) as being the third.
There are several important features we would like to add to this website. We have created this
lists to help us track these improvements, as well as share with the general public our goals for
this project.

BIBLIOGRAPHY
 BIBLIOGRAPHY

1. Mastering in Visual Studio:

-By Evangelous Petroutsas
2. System Analysis and Design in Changing world
-By Satzinger
1. Pressman S Roger: Software Engineering – A practitioners approach.
1. (Mc. Graw Hill International Edition)
2. Pankaj Jalote : An Integrated approach to Software Engineering-
1. Narosa Publishing House.

3. HTML & XHTML Fourth Edition the Complete Reference TATA Mc GrawHill
Publishing Company Limited.

4. MySql the Complete Reference TATA Mc Graw Hill Publishing Company Limited.
 REFERENCES

1. www.google .com

2. www.wikipedia.com

3. www.msdn.com

4. www.w3school.com

5. www.c-sharpcorner.com

6. support.microsoft.com

7. www.meraevent.com

8. www.meraevents.com