Abstract

The purpose of the study was to solve the problems of being localized within the barriers of the
locality, so I thought to develop the system which will make it easy to see the latest happenings the
peoples related to the school, about the events organized in the near future. So I developed the system in
which all the past and future events can be seen easily.

The organized events are placed on the webpage in such a way that any new visitor can
also be able to find the each and every minute details about every event, about date & time as
well as venue of the event.

This Event management system will provide the calendar by using which person visiting the
website will get the information about forthcoming events in the school, which helps the visitor in
knowing the timings and venue information early.

The main purpose of the development of this system is to provide the information about each
every program or an event to students, teachers and the families of the students, who are eager to know
about every activity happening in the school where there child studies and grows with it.

Due to launch of the event management webpage the school is also get benefited because due to
launch of website, school can take online admission, and event management makes the whole website
even more attractive because events are the most entertaining part of the school, so all the students,
teachers and parents of the students are also eager to know the events and their pictures as well.

1
 Company Profile

Qualsoft Systems Pvt. Ltd is a privately held company owned by qualified and experienced
entrepreneurs. Founded in 2007, within very short span of time we have achieved a leading position in
the region through our sincere efforts, hard work and complete dedication The company is involved in
the development of state of the art ERP, SaaS - Cloud Computing applications & Web solutions which
are robust, scalable & secure.

Our team is a right blend of management, technical and administrative personnel supported by
the most competitive and advanced IT and communications infrastructure. Our extensive
communication facilities allow us to be in service 24x7.

We have set reputation of our organization as an outstanding and most reliable service provider,
with reasonable compensation. We are a customer-focused company. We firmly believe that working as
partners with our customers is the best way to stay in tune with their specific needs. As we continue to
grow, our customers will always be the primary focus of our organization.

Products of Qualsoft Systems India:

eSchool TM
An educational organization management system which is developed to make educational system more
qualitative in the web world...

Smart TM
A Complete package for Hotel management this project will enhance the business around the world
with data to be secured properly...

Care One TM
Consultancy in Hospital Management we have ever is the best product we developed which will help
the hospitals to be globally famous…

Features to be looked at:

 . Excellence and Credibility

 Customer Satisfaction
 Effective Communication
 Employee Welfare
 Ethical Conduct
 Honesty and Integrity
 Innovativeness
 Social Responsibility
2
 Problem Definition

In the development of the e-school project one of the major problem occurred in the management of the
events which are held regularly with lot of interest, and passion in the school teachers , students and
importantly parents of the students, who are really eager to know about the latest happenings in the
school and love to see their children’s performing.

However in the context of parents interest due to lack of time parents are unable to know about
the details of the events in the school.

Below are some major problem areas because of which there is need of development of the
Event Management module.

Unformatted Events list:

It is one of the major problem area due to which this study is being done, every year school
organizes lot of events in the school, for the all round students development, but if the list of the events
is not properly mentioned it becomes so hard for the students as well as their parents to get the exact
details f the upcoming events, by knowing which they can do the plan for those events.

In this website of e-school all other things were managed properly but the event list is not
properly mentioned which causes lot of problems.

Details of all ready happened events :

If some of the parents wants to see the photos of their children’s who have performed in the last
years Parents day function, so it becomes very difficult for the parents to find the photographs, video,
and some other details of the past happened events.

Event Distribution:

When someone wants to find the last years 15th Augusts functions details or see photos or see
videos of the pared etc. then it becomes too difficult to get that particular events details in the volume of
data. With this finding a particular video or photo it becomes very up heal task in scattered database, so
it becomes really hard to get the exact event detail category wise.

Updating Records :

To see all the latest happening in the school firstly all the data need to be updated properly and
correctly, because a small mistake in the data updation will cause a lot of problems among all the related
personnel’s who are largely depend on that information, same problem was happing previously

3
 Older System View

Previously when any events were being organized in the school only the forthcoming events around one
month were displayed on the notice board and which may become less help full for the parents of the
students who gets very less time to visit the school personally, hence they remains unaware of the events
in the school, like Parents Day etc.
There are some important points mentioned below which I found during the detailed analysis of
the older event management system of the school.

Invitation For Events:

Previously when school things of organizing any event then the first and the most important part
is the invitation card or later to the respective staff members, chief guest, and largely to each & every
student and their family members, at the time mostly invitation about the upcoming event is conveyed
through students to their respective family members.
The next option was to pest the Invitation on the main notice board and every class is being
given instruction to read the notice board carefully.

Upcoming Events List:

School conducts lot of events every year some of them are such events which are organized
every year such as Republic day, Annual Sports Day, Term wise exams etc.
So to get the time for preparation of these events students were given knowledge about these
events in advanced, which is handy for the students to prepare for the examinations or take part in some
of the Cultural events of the program.
The list of some major events with their timetable and venue is given at the time of the admission
on the prospectus of the school.

Photo Presentation:

After every event get over the next attraction is the presentation of the events photo, which
includes photos of the chief guests as well as some of the prize winners photos were presented to be seen
by the people who due to some reason miss the actual event.
This was the thing which I really like about the school of keeping all the photos of all the
recently ended events at one big auditorium for a day or so, and all the respected teachers, students and
their families given invitation to see all the pictures.

Other Important:

 After end of every big event students are provided with well organized DVD of the respective
program with photos & Videos.
 Each and every year regularly educational workshops being organized for the growth of the
students.

4
 Proposed System

One major change suggested to the school management is to launch the website of their own and put all
these and more detail on that for the easy access to the students and their parents.
After studying all the details of the previous system of the school I have decided to implement
the system in the school which will help the students their parents as well as all related people to know
the school events in detail, to see the upcoming events, watch the photos, videos and all on just click of
the button.

Some major attributes are described below in detail:

Browse Categories:

The events are categorized differently to make information of the events more beneficial for the
visitor on the website. This will make them select the particular category to see the events details of the
particular category only.

Categories mentioned below

 Festival
 Sports
 Conferences
 Educational Tours
 Others

Photo Gallery:

If you want to see tall the pictures of all the events with good quality and event wise only one
lace to see it all is the photo gallery of the event managements webpage. In this photo gallery all
photographs of all the events organized by the school, all the special guest appearances in the school as
well as the photos of all the educational tours organized were included in the most attractive and
watchable photo gallery of the event management.

Video Gallery:

Separate online video gallery is provide for the students with their parents to see the videos of their
child’s performance in cultural event, or see any guest lecture happened in the school. All these videos
can be easily accessed & downloaded as per the visitors choice.

Statistics:

Record of all the annual events can be seen in the statistics module, which helps to boost the
reputation of the school among the students to be inspired to get admission in the school. These stats are
shown in the form of graphs which is easy to understand.

Calendar:

5
 Calendar is the most attractive and important enhancement in the old manual system of
displaying the forthcoming events on the notice board.

This calendar module will help the people visiting to the schools website to know the events in
each and every day or week or month, which is the best feature in the calendar. With the inclusion of the
calendar in the events module, this becomes the most user friendly webpage for the school website.

Calendar shows the events when selected on particular date, so it displays the event name, date &
time of the event, and special appearance if any,.

Event Updation:

This the most important part in this webpage development because for events details to be shown
or to see the photos & videos of any past or current event or to see the upcoming events of the year, it is
necessary to update the events list, upload the photos and videos to see the statistics number of annual
events it is very much important to regularly update the date on the website.

User is provided with the good & easy facilities of updating the date or deleting the date or
adding the new data to the website.

These are some proposed features of the Event management webpage.

6
 Feasibility Study

After clarifying the request, it is important to check whether it is practical to implement.

Feasibility study checks whether it is technically or economically feasible or not.

Technical Feasibility

After clarifying the user requests and analyzing the information provided by user, it is well
understood that current process was effective and efficient until now. But as the volume of data is
increasing so rapidly, it is very hard to continue with current manual process. The use of any
computerized system has become necessary. The major expectation from computerized system is that it
will store all the information in proper format and will provide to the user, whenever it is required again
it will create problems like
a) Searching of any specific data from different files,
b) Regular and conscious multiple updates,
c) Presentations of data to the user in desired form.

So only the use of computerized file system will not be the proper solution to this problem.
Instead of file system, the centralized database approach will be suitable for storing the data in
appropriate format.

DBMS can manage large amount of information. A simple user interface can be developed for
easier operation.

Currently many DBMS packages are available, among which MS-Access, Oracle, MySQL are
very popular and easy. For developing a simple and user-friendly user interface with lower load on
memory of computer, either Microsoft’s Visual Basic or Java Package are two best options. Among
which MS Visual Basic 6.0 is easy to handle.

For the development of this system, some important resources are required – manpower,
software and hardware. From the above discussion, it may be concluded that necessary hardware and
software support is available.

7
Economical Feasibility

Technical feasibility does not guarantee if the system will be beneficial to the system if
developed. Therefore economic feasibility is studied.

Firstly, the hardware and software cost required for development of the system is evaluated and
the total amount for this software is approximately 2, 00,000.

As shown in the table, the cost depicted in the table does not include development and training
fees by software development organization. The sum of total cost and development cost is economically
affordable to the client. Therefore the proposed system is economically feasible.

Behavioral feasibility

At the time of requirement gathering, different users are interviewed. They are now used to the
routine job of maintaining current system. But they are happy and excited by the idea that some system
is going to reduce their headache, so that they can concentrate on more important issues like providing
new service. They have welcomed the change in current process and are giving a good response to the
planning and development of the system.

Some users are a little doubtful about accurate working of the proposed system. So they are
interested in testing the system until they are satisfied with its working.

8
 Fact Finding Techniques
The importance of constantly involving the users in the process of requirements analysis and
specifications cannot be overemphasized. Only the users know their domain properly, and for that
reason they should certainly participate in defining the system's functions, designing them, and
evaluating their implementation and testing.

The users should also participate in creating, verifying, and updating the requirements
specification document for the project. The users should share with the developers the responsibility for
the requirements' completeness and consistency.

It is the project managers' duty to establish and maintain good relations with the users throughout
the development process, as well as to consult them whenever the project gets stuck due to the
development team's lack of domain understanding.

It is essential to make as explicit as possible all the requirements that reflect the user's work and
the tasks that the software system under development is supposed to automate. Any situation in which
users can find themselves when doing their job is the context that must be taken into account through
requirements engineering. It is equally important not to concentrate on a single user's task, but to cover
communication between users when the task requires collaboration.

There is a wide spectrum of techniques for requirements engineering. Whatever technique is

applied, it is always desirable to involve the user to increase the correctness of the requirements
specification.

Important Types of Fact Finding Techniques

• structured interviews and questionnaires that the user fills in (inquiry based
requirements gathering);

• diagram-based requirements analysis (using multiple diagrams to sketch

relevant parts of the user's work process and describe the requirements
graphically);

• using metaphors of the user's work process (e.g., the office metaphor, or
the agent/agency metaphor);

• scenario analysis (scenario is a typical sequence of activities

characterizing the user's work process, hence it reflects what the user will
do with the system and helps define the test procedures);

• using special-purpose software tools for requirements gathering (some of

them can be simulation-based);

• requirements completeness and consistency checks (some of them can be

automated, others must be performed manually);
9
• using special-purpose requirements-specification languages in order to
describe requirements more formally and hence provide more automated
requirements tracing;

• prototype system development, in order to make the requirements clear

and to establish better mutual understanding with the users;

• analyzing videotaped user's work process.

10
 Software Requirement Specifications

Development/ Maintenance Environment

ASP.NET

is a web application framework developed and marketed by Microsoft to allow programmers to

build dynamic web sites, web applications and web services. It was first released in January 2002 with
version 1.0 of the .NET Framework, and is the successor to Microsoft's Active Server Pages (ASP)
technology. ASP.NET is built on the Common Language Runtime (CLR), allowing programmers to
write ASP.NET code using any supported .NET language. The ASP.NET SOAP extension framework
allows ASP.NET components to process SOAP messages.

Characteristics

Pages

.NET pages, known officially as "web forms", are the main building block for application
development. Web forms are contained in files with an ".aspx" extension; these files typically contain
static (X)HTML markup, as well as markup defining server-side Web Controls and User Controls where
the developers place all the required static and dynamic content for the web page. Additionally, dynamic
code which runs on the server can be placed in a page within a block <% -- dynamic code -- %>
which is similar to other web development technologies such as PHP, JSP, and ASP, but this practice is
generally discouraged except for the purposes of data binding since it requires more calls when
rendering the page.

User controls

User controls are encapsulations of sections of pages which are registered and used as controls in
ASP.NET. User controls are created as ASCX markup files. These files usually contain static (X)HTML
markup, as well as markup defining server-side web controls where the developers place all the required
static and dynamic content. A user control is compiled when its containing page is requested and is
stored in memory for subsequent requests. User controls have their own events which are handled during
the life of ASP.NET requests. An event bubbling mechanism provides the ability to pass an event fired
by a user control up to its containing page. Unlike an ASP.NET page, a user control cannot be requested
independently; one of its containing pages is requested instead.

Custom controls

Programmers can also build custom controls for ASP.NET applications. Unlike user controls,
these controls don't have an ASCX markup file, having all their code compiled into a DLL file. Such
custom controls can be used across multiple web applications and Visual Studio projects (which is not
allowed with user controls). By using a Register directive, the control is loaded from the DLL.

11
State management

ASP.NET applications are hosted by a web server and are accessed using the stateless HTTP
protocol. As such, if an application uses stateful interaction, it has to implement state management on its
own. ASP.NET provides various functions for state management. Conceptually, Microsoft treats "state"
as GUI state; problems may arise if an application needs to keep track of "data state", for example, a
finite state machine which may be in a transient state between requests (lazy evaluation) or which takes
a long time to initialize.

Application state

Application state is held by a collection of shared user-defined variables. These are set and
initialized when the Application_OnStart event fires on the loading of the first instance of the
applications and are available till the last instance exits. Application state variables are accessed using
the Applications collection, which provides a wrapper for the application state variables. Application
state variables are identified by name.[9]

Session state

Server-side session state is held by a collection of user-defined session variables, which are
persisted during a user session. These variables, accessed using the Session collection, are unique to
each session instance. The variables can be set to be automatically destroyed after a defined time of
inactivity, even if the session does not end. Client-side user session is maintained by either a cookie or
by encoding the session ID in the URL itself

INTRODUCTION TO VISUAL STUDIO.NET

Visual Studio .NET is a complete set of development tools for building ASP Web applications, XML Web
services, desktop applications, and mobile applications. Visual Basic .NET, Visual C++ .NET, and Visual C# .NET all
12
use the same integrated development environment (IDE), which allows them to share tools and facilitates in the
creation of mixed-language solutions. In addition, these languages leverage the functionality of the .NET
Framework, which provides access to key technologies that simplify the development of ASP Web applications
and XML Web services.

For front end we are using Vb.net (Visual Basic.net) all the forms i.e. interfaces are developed using
Vb.net as it is very convenient , efficient and user friendly language and has the capability for multiple language
integration and provides us with the feature of disconnected data architecture.

Features of VB.net

1. Object oriented – Supports polymorphism, inheritance, encapsulation, data binding and other related
features related to objects.

2. Error Handling – Supports both structured and unstructured error handling.

3. Multithreading – Supports concept of dividing a process into sub processes and running them simultaneously
to increase efficiency.

4. Deployment of project – Vb.net provides a well specified wizard for proper deployment of project.

5. Supports global assembly catch.

SQL Server 2005

Microsoft SQL Server is a relational model database server produced by Microsoft. Its primary
query languages are T-SQL and ANSI SQL.

The code base for MS SQL Server (prior to version 7.0) originated in Sybase SQL Server, and
was Microsoft's entry to the enterprise-level database market, competing against Oracle, IBM, and, later,
Sybase. Microsoft, Sybase and Ashton-Tate originally teamed up to create and market the first version
named SQL Server 1.0 for OS/2 (about 1989) which was essentially the same as Sybase SQL Server 3.0
on Unix, VMS, etc. Microsoft SQL Server 4.2 was shipped around 1992 (available bundled with
Microsoft OS/2 version 1.3). Later Microsoft SQL Server 4.21 for Windows NT was released at the
same time as Windows NT 3.1. Microsoft SQL Server v6.0 was the first version designed for NT, and
did not include any direction from Sybase.

About the time Windows NT was released, Sybase and Microsoft parted ways and each pursued
their own design and marketing schemes. Microsoft negotiated exclusive rights to all versions of SQL
Server written for Microsoft operating systems. Later, Sybase changed the name of its product to
Adaptive Server Enterprise to avoid confusion with Microsoft SQL Server. Until 1994, Microsoft's SQL
Server carried three Sybase copyright notices as an indication of its origin.

Since parting ways, several revisions have been done independently. SQL Server 7.0 was a
rewrite from the legacy Sybase code. It was succeeded by SQL Server 2000, which was the first edition
to be launched in a variant for the IA-64 architecture.

.
13
  HARDWARE REQUIREMENTS

Platform 32 bit version /X-64

Operating System 32/x64-based version of Windows Server 2003, Standard Edition, Enterprise Edition, or
Datacenter Edition

Requirements for single server deployment

Same as the requirements for the edition of Windows Server 2003

Requirements for server farm deployment

 1 64-bit CPU
 2 or more CPUs recommended 2 GB RAM

 SOFTWARE REQUIREMENTS

Windows Server 2003 Editions

a) Windows Internet Information Services (IIS) 7.0, running in IIS 7.0 worker

process isolation mode

b) Microsoft ASP.NET 3.0

Database Requirements

SQL Server 2005 Standard Edition/ Express, with the latest service pack

Client Software Requirements

Any Windows, Macintosh, or UNIX client can use Windows features if the client runs the software

14
 Scope

The scope of the system is to provide the visitors of the schools website a well formatted view of
the yearly happening events and functions at their own work place, which will save their time and
provide the unambiguous information directly.
Main aim of the website is to reach out from local to global visitors of the school related people,
another important factor is searching the information on the website about the particular event becomes
easy due to inclusion of separate event categories.

Some other important features are mentioned below:

 Categorized event according their programs included in those events, such as

o Festival:- Includes the festivals celebrated in the school every year

o Sports: - It has the Annual Sports day Event and some other sports competitions.
o Educational Tours:- Includes the details about the tours arranged in the whole year

 In the form of calendar it provides the tool for the visitors to find the event date/day wise,
because of which visitors can see the particular dates events.

 Photo gallery adds more charm to the website because the people those unable to see the events
because of some unwanted reason and they want see those moments they can see in good quality.
And those who want to relive those moments can also see the pictures.

 Video gallery is the best option for the parents to see the performances of their children’s in
High Definition.

In all the event management system will add a new dimension to the e-school website, and provide
the satisfactory results to the school management as well.

15
 Data Flow Diagrams

Level ‘0’ DFD

School Data Display Events Category wise

Admin Access
Category wise events

Calendar information Display Photo Album

Statistics Data
Level 0
Event Management System
Display Statistics Graph
Login Information

Display Videos
Feedback/Suggestions
Queries
Display Calendar Events
User Access

16
Level ‘1’ DFD

User Detail

Tbl Login

Authorized User Login

Admin Access Sub System Desired Reports

Data Manipulation Sub System

Data View Sub System

Tbl Events Category

User View Respective data view

Feedback Sub System

User Access
Feedback by user

Tbl Feedback

Level ‘1’ DFD

Entity Relationship Diagram

Calendar Sub System

Tbl Event Details

17
View Calendar

Statistics Sub System

Tbl Stats
 Video Gallery Sub System

Data View Sub System

View Videos
Database Design
Photo Gallery Sub System Tbl Videos
event_date
event_name Image_path
Tbl Photos
event description View Photo Album
Browse Categories Sub System

Tbl Event Category

event_id
View Events

Login Event_Details event_id Event_images

Sub System
Tbl Login
event_venue

t_id
d

n
_i

eve
event

Image_id
Admin Access

Event_login Event_videos

User_id
Video_path
Video_id
password

Figure 1:Table-Event_Details

18
Figure 2:Table-Videos

Figure 3:Table-Images

19
 Figure 4:Table-Images

Methodology

Prototyping Model

Often, a customer defines a set of general objectives for software but does not identify detailed
input, processing, or output requirements. In other cases, the developer may be unsure of the efficiency
of an algorithm, the adaptability of an operating system, or the form that human/machine interaction
should take. In these, and many other situations, a prototyping paradigm may offer the best approach.

The prototyping paradigm begins with requirements gathering. Developer and customer meet
and define the overall objectives for the software, identify whatever requirements are known, and outline
areas where further definition is mandatory. A "quick design" then occurs. The quick design focuses on
a representation of those aspects of the software that will be visible to the customer/user (e.g.,
input approaches and output formats).

20
 The quick design leads to the construction of a prototype. The prototype is evaluated by the
customer/user and used to refine requirements for the software to be developed. Iteration occurs as the
prototype is tuned to satisfy the needs of the customer, while at the same time enabling the developer to
better understand what needs to be done.

Ideally, the prototype serves as a mechanism for identifying software requirements. If a working
prototype is built, the developer attempts to use existing program fragments or applies tools (e.g., report
generators, window managers) that enable working programs to be generated quickly. But what do we
do with the prototype when it has served the purpose just described? Brooks [BRO75] provides an
answer:
In most projects, the first system built is barely usable. It may be too slow, too big, awkward in
use or all three. There is no alternative but to start again, smarting but smarter, and build a redesigned
version in which these problems are solved . . .
When a new system concept or new technology is used, one has to build a system to throw away,
for even the best planning is not so omniscient as to get it right the first time. The management question,
therefore, is not whether to build a pilot system and throw it away. You will do that. The only question
is whether to plan in advance to build a throwaway, or to promise to deliver the
21
throwaway to customers . . .
Developers get to build something immediately. Yet, prototyping can also be problematic
for the following reasons:

1. The customer sees what appears to be a working version of the software, unaware that the
prototype is held together “with chewing gum and baling wire,” unaware that in the rush to get it
working no one has considered overall software quality or long-term maintainability.
When informed that the product must be rebuilt so that high levels of quality can be maintained,
the customer cries foul and demands that "a few fixes" be applied to make the prototype a
working product. Too often, software development management relents.

2. The developer often makes implementation compromises in order to get a prototype working
quickly. An inappropriate operating system or programming language may be used simply
because it is available and known; an inefficient algorithm may be implemented simply to
demonstrate capability. After a time, the developer may become familiar with these choices and
forget all the reasons why they were inappropriate. The less-than-ideal choice has now become
an integral part of the system.

Although problems can occur, prototyping can be an effective paradigm for software
engineering. The key is to define the rules of the game at the beginning; that is, the customer and
developer must both agree that the prototype is built to serve as a mechanism for defining
requirements. It is then discarded (at least in part) and the actual software is engineered with an eye
toward quality and maintainability.

22
 Functional Details
After all the efforts finally the website is ready to go on the web, but before that it is need to be seen the
functionality areas of the website. It describes the actual working boundaries of the website.

Some of the major functional areas are described below.

Event Categories:

The most attractive of the areas of this webpage on which details about all the events are displayed
according to the category they belong.

Categories:

 Festival
 Sports
 Conference
 Educational Tours

Ex. Details about annual Sports Day event will be seen under the category called Sports only.

23
Calendar:

One of the most attractive functional area of the website which helps the user to view the events listed
for the whole educational year. Actually calendar is very old & traditional concept seeing the future happening
events, but in this case calendar is provided with the new & attractive format.

Selecting any date on the calendar it will display the event name, date of the event, venue where event
is to healed with event details of particular event.

Photo & Video Gallery:

Videos, photos are the fist crush points of any human nature, then user is no exception for that. This is
the reason why Photo & Video gallery is designed so attractively so once the user sees the gallery he will
become the fond of that.

User Interface

24
Figure :Events Category

25
Figure: Photo Gallery

26
27
Figure : Video Gallery

28
Figure :Calendar

29
Figure: Administrator Login

30
31
Figure : Photo Uploader

32
Figure: Upload Status

33
 Figure: Upload Event

System Testing
System testing of software or hardware is testing conducted on a complete, integrated system to evaluate
the system's compliance with its specified requirements. System testing falls within the scope of black
box testing, and as such, should require no knowledge of the inner design of the code or logic.

As a rule, system testing takes, as its input, all of the "integrated" software components that have
successfully passed integration testing and also the software system itself integrated with any applicable
hardware system(s).
The purpose of integration testing is to detect any inconsistencies between the software units that
are integrated together (called assemblages) or between any of the assemblages and the hardware.
System testing is a more limiting type of testing; it seeks to detect defects both within the "inter-
assemblages" and also within the system as a whole.
System testing is performed on the entire system in the context of a Functional Requirement
Specification(s) (FRS) and/or a System Requirement Specification (SRS). System testing is an
investigatory testing phase, where the focus is to have almost a destructive attitude and tests not only the

34
design, but also the behavior and even the believed expectations of the customer. It is also intended to
test up to and beyond the bounds defined in the software/hardware requirements specification(s).

1. Performance Testing

Performance Testing covers a broad range of engineering or functional evaluations where a

material, product, system, or person is not specified by detailed material or component specifications:
rather, emphasis is on the final measurable performance characteristics.

Performance testing can refer to the assessment of the performance of a human examinee. For
example, a behind-the-wheel driving test is a performance test of whether a person is able to perform the
functions of a competent driver of an automobile.

In the computer industry, software performance testing is used to determine the speed or
effectiveness of a computer, network, software program or device. This process can involve quantitative
tests done in a lab, such as measuring the response time or the number of MIPS (millions of instructions
per second) at which a system functions. Qualitative attributes such as reliability, scalability and
interoperability may also be evaluated. Performance testing is often done in conjunction with stress
testing.

2. Stress Testing

Stress testing is a form of testing that is used to determine the stability of a given system or
entity. It involves testing beyond normal operational capacity, often to a breaking point, in order to
observe the results. Stress testing may have a more specific meaning in certain industries, such as fatigue
testing for materials.

In software testing, "System stress test" refers to tests that put a greater emphasis on robustness,
availability, and error handling under a heavy load, rather than on what would be considered correct
behavior under normal circumstances. In particular, the goals of such tests may be to ensure the software
does not crash in conditions of insufficient computational resources (such as memory or disk space),
unusually high concurrency, or denial of service attacks.

35
 Black Box Testing

Black-box testing, also called behavioral testing, focuses on the functional requirements of the
software. That is, black-box testing enables the software engineer to derive sets of input conditions that
will fully exercise all functional requirements for a program. Black-box testing is not an alternative to
white-box techniques. Rather, it is a complementary approach that is likely to uncover a different class
of errors than white-box methods.
Black-box testing attempts to find errors in the following categories: (1) incorrect or missing
functions, (2) interface errors, (3) errors in data structures or external data base access, (4) behavior or
performance errors, and (5) initialization and termination errors.

Unlike white-box testing, which is performed early in the testing process, black box testing tends
to be applied during later stages of testing. Because black-box testing purposely disregards control
structure, attention is focused on the information domain. Tests are designed to answer the following
questions:

36
• How is functional validity tested?
• How is system behavior and performance tested?
• What classes of input will make good test cases?
• Is the system particularly sensitive to certain input values?
• How are the boundaries of a data class isolated?
• What data rates and data volume can the system tolerate?
• What effect will specific combinations of data have on system operation?
By applying black-box techniques, we derive a set of test cases that satisfy the following
criteria [MYE79]: (1) test cases that reduce, by a count that is greater than one,
the number of additional test cases that must be designed to achieve reasonable testing
and (2) test cases that tell us something about the presence or absence of classes
of errors, rather than an error associated only with the specific test at hand.

Software Testing Strategies

Software testing must be planned carefully to avoid wasting development time and resources.
Testing begins "in the small" and progresses "to the large". Initially individual components are tested
using white box and black box techniques. After the individual components have been tested and added
to the system, integration testing takes place. Once the full software product is completed, system testing
is performed. The Test Specification document should be reviewed like all other software engineering
work products.

Strategic Approach to Software Testing:

 Testing begins at the component level and works outward toward the integration of the entire
computer-basedsystem.
 Different testing techniques are appropriate at different points in time.
 The developer of the software conducts testing and may be assisted by independent test groups
for large projects.

37
  The role of the independent tester is to remove the conflict of interest inherent when the builder
is testing his or herown product.
 Testing and debugging are different activities.
 Debugging must be accommodated in any testing strategy.
 Make a distinction between verification (are we building the product right?) and validation (are
we building the rightproduct?)

Strategic Testing Issues:

 Specify product requirements in a quantifiable manner before testing starts.
 Specify testing objectives explicitly.
 Identify the user classes of the software and develop a profile for each.
 Develop a test plan that emphasizes rapid cycle testing.
 Build robust software that is designed to test itself (e.g. uses anitbugging).
 Use effective formal reviews as a filter prior to testing.
 Conduct formal technical reviews to assess the test strategy and test cases.

38
 Conclusion

As the detail study of the software product is done I really feel that the webpage user wanted to be
developed I just developed the same, because, event management webpage module is the example of the
fact that how the website will help any organization can spread globally.

Event management will help the people outside the school like parents of the students and the
other school members to know about the things happening in the school, for this calendar is made
available in that webpage to check events listed for the whole educational year.

According to me and the study I performed on this webpage it is quite good to have the website
for the schools now a days, because in today’s e-world it e-world

Finally I just want to tell that it is always better to use the computerized system than the manual
one, because it computerized system can save the Time, Efforts used, and most importantly the major
factor money by doing work faster and accurate.

39
 User Training

Use training is one of the important step in the software development, which actually starts after
the completion of the development process. In user training at start user is provided with the hard copy
of user manual, then told them to study it to the extent that they will get the proper idea about the
software system they are going to work on.

User is then given training in the actual working environment so get them in to the situasysttion
in which they have to work for hours. While giving the training to the user it is kept in mind that, the
training provided is very much important because it will help them lifelong for using the same
computerized system or other updated systems like this.

So keeping in mind training is given very carefully and correctly, most importantly practical
base, i.e. based on live examples, which is more helpful because working in offline is very much
different than working directly with the real life examples.

User provided with the online help option to have more flexibility in work due to which user can
take the required help whenever he needs the help for any problem occurred while using the software.
With that offline user manual is also being provided to the user to have understanding of the software
system which will make user more friendly with the system.

40
 Bibliography

 FOR .NET INSTALLATION

www.support.mircosoft.com

 FOR DEPLOYMENT AND PACKING ON SERVER

www.developer.com

www.15seconds.com

 FOR SQL
www.msdn.microsoft.com

 FOR ASP.NET
www.msdn.microsoft.com/net/quickstart/aspplus/default.com

www.asp.net

www.asptoday.com

www.aspfree.com

 Software Engineering Concepts

Robert Pressman

41