This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
INTEGRATED SOFTWARE SOLUTION is a rapidly growing software services
company. We specialize in the development of custom software applications and offshoresoftware outsourcing services. Specifically, our company carries out customized softwaredevelopment, database design, client-server and internet/intranetapplicationdevelopment.
Over the years we have managed to build a solid team of software professionals that come
from various backgrounds and expand the creative potential of the company. The expertise
that they posses embraces a wide range of programming skills involving the latest and mosteffective development technologies, such as .NET (ASP.NET, C#, VB.NET), PHP, Javaand many more. This to a great extent defines the quality and reliability of the applications
that we develop.We deliver customized application services to the end customers and also provide offshoresoftware outsourcing services to other IT companies. Our competence and experience ensurethat we deliver excellent services and products to our customers. At every stage of the
development process, from conceptual design to product release, the highest qualitystandards are maintained. Our extensive communication facilities allow us to keep in touch
with our customer 24 hours. INTEGRATED SOFRTWARE SOLUTION creates ExpertSystems designed with one goal in mind- to greatly contribute to the client's bottom line
through the implementation of technology solutions strategically designed to expand marketshare.
INTEGRATED SOFRTWARE SOLUTION premier product, the I NTEGRATED ExpertSystem, accomplishes this by providing valuable customer service that gives retailers a
distinct edge over their competition. In turn, Financial Institutions and other entities participating in the retail business model benefit greatly by making INTEGRATED
SOFRTWARE SOLUTION available to their clients.
Where previously market saturation once stymied the growth of these institutions,
INTEGRATED SOFRTWARE SOLUTION creates the capability for them to compete intheir markets in an exciting new way: by leveraging valuable customer service and the promise of increased market share as the catalyst for success.
As we know that for company to grow it is one of the vital parts because it helps to set up a
target to achieve. Not only the I NTEGRATED SOFRTWAR E SOLUTION has decided to
fulfill the requirement of the customer but also it has proven it time to time.
INTEGRATED SOFTWARE services are a software services company. We offer services
in two areas: Information Technology and business integration. We are a services-oriented
company. We offer services in two areas; Information Technology and Business Integration.
Information Technology services can be anything from analyzing an environment (in an
effort to improve effectiveness), to develop an application or interface (to improve the
performance of an environment.) I NTEGRATED SOFRTWAR E SOLUTION provides a
variety of services to help clients solve problems in the most effective and economical
possible way. For customized Software development services, We have professionals from
diverse backgrounds. I NTEGRATED SOFRTWAR E SOLUTION is a software services and
outsourcing company. We have worked with companies like MDI Security Systems to name
a few. Click here for more details.
VISION
I NTEGRATED SOFRTWAR E SOLUTION is a group of dedicated software professionals..
DEDICATED in everything we do. Throughout our website you will be exposed to the
different parts of our world. Hopefully... something we do... can help you do... what you do..a little better.
I NTEGRATED SOFRTWAR E SOLUTION provides software development solutions and
services for all types of businesses. We furnish digital solutions at economical prices by performing the majority of the development work at our development center in Kolkata, the
new IT hub of India. Our clients work face-to-face with an executive through the projectdefinition, testing, and installation phases. The executive also assists clients with variousoptions regarding ongoing product support.
I NTEGRATED SOFTWAR E SOLUTION employs are talented software development professionals who have experience in solving real world problems in industries as diverse assecurity systems, DVR , NVR , IP Cameras, manufacturing, wholesale, retail sales, healthcare, accounting, government, education, and document imaging. Consequently, we are well
qualified to solve a wide range of problems involving application development or re-engineering, legacy web integration, web solutions and e-business.
y Microsoft Project Server y Share Point Portal Server
y MS Exchange Server
y Microsoft BizTalk Server
y Microsoft Transaction Server
y Commerce Server 2000
y Site Server
Design, Testing, Configuration, Software Engineering and other
Tools
y Rational R OSE y Developer 2000, Designer 2000
y Visual SourceSafe
y Win Runner , Load runner
y Microsoft . NET
y Install Shield
Objectives:-
The main objective of our company is to provide the confidentiality regardingto the software. Company recognizes that your investment in software, web and business
processes represent a very valuable and confidential aspect of your business. Consequently, access to all sensitive information regarding our clients is restricted on a need-to-know basis.
Our client contracts as well as employment agreements include confidentiallyclauses that are strictly enforced. Your success is important to us and we will protect your
A software life cycle model is a descriptive and diagrammatic representation of the software life cycle.
Life cycle model represents all the activities required to make a software product transit through its life
cycle phases. It also captures the order in which these activities are to be undertaken.
Various Life cycle models are:--
1. Water fall Model.
2. Prototyping Model.
3. EvolutionaryModel.
4. Spiral Model.
Waterfall Model
This is the most common and classic type of life cycle models,
also referred to as a linear-sequential life cycle model. It is very simple to understand and use. In a waterfall model,
each phase must be completed in its entirety before the next phase can begin. At the end of each phase, a review takes place to determine if the project is on the right path and whether or not to continue or discard the project. Unlike what I mentioned in the general model,
The Internet began in the late 1960s as an experiment. Its goal was to create a truly resilient
information network²one that could withstand the loss of several computers without
preventing the others from communicating. Driven by potential disaster scenarios (such asnuclear attack), the U.S. Department of Defense provided the initial funding. The early
Internet was mostly limited to educational institutions and defense contractors. It flourishedas a tool for academic collaboration, allowing researchers across the globe to share
information. In the early 1990s, modems were created that could work over existing phonelines, and the Internet began to open up to commercial users. In 1993, the first HTML browser was created, and the Internet revolution began.
HTML and HTML Forms
HTML forms allow web application developers to design standard input pages. When theuser clicks the Submit button on the page shown in Figure 1-2, all the data in the input
controls (in this case, the two check boxes) is patched together into one long string of textand sent to the web server. On the server side, a custom application receives and processes
the data. Amazingly enough, the controls that were created for HTML forms more than tenyears ago are still the basic foundation that you¶ll use to build dynamic ASP. NET pages! Thedifference
is the type of application that runs on the server side. In the past, when the user clicked button on a form page, the information might have been e-mailed to a set account or sent to
an application on the server that used the challenging Common Gateway Interface (CGI)standard. Today, you¶ll work with the much more capable and elegant ASP. NET platform.
Server-Side Programming
To understand why ASP. NET was created, it helps to understand the problems of early web
development technologies. With the original CGI standard, for example, the web server mustlaunch a completely separate instance of the application for each web request. If the websiteis popular , the web server struggles under the weight of hundreds of separate copies of theapplication, eventually becoming a victim of its own success. Furthermore, technologies
such as CGI provide a bare-bones programming environment. If you want higher-levelfeatures, like the ability to authenticate users, store personalized information, or display
records you¶veretrieved from a database, you need to write pages of code from scratch. Building a web
application this way is tedious and error-prone. To counter these problems, Microsoft createdhigher-level development platforms, such as ASP and ASP. NET. Both of these technologies
allow developers to program dynamic web pages without worrying about the low-levelimplementation details. For that reason, both latforms have been incredibly successful. Theoriginal ASP platform garnered a huge audience of nearly one million developers, becoming
far more popular than even Microsoft anticipated. It wasn¶t long before it was being wedgedinto all sorts of unusual places, including mission-critical business applications and highly
trafficked e-commerce sites. Because ASP wasn¶t designed with these uses in mind,
performance, security, and configuration problems soon appeared. That¶s where ASP. NETcomes into the picture. ASP. NET was developed as an industrial strength web application
framework that could address the limitations of ASP. Compared to classic ASP, ASP. NET
offers better performance, better design tools, and a rich set of readymade features.ASP. NET was wildly popular from the moment it was released²in fact, it was put to work
in dozens of large-scale commercial websites while still in beta form. Client-Side ProgrammingAt the same time that server-side web development was moving through an alphabet soup of
technologies, a new type of programming was gaining popularity. Developers began toexperiment with the different ways they could enhance web pages by embedding miniatureapplets built with JavaScript, ActiveX, Java, and Flash into web pages. These client-side
technologiesdon¶t involve any server processing. Instead, the complete application is downloaded to the
client browser , which executes it locally. The greatest problem with client-side technologies
is that they aren¶t supported equally by all browsers and operating systems. One of thereasons that web development is so popular
in the first place is because web applications don¶t require setup CDs, downloads, and othertedious (and error-prone) deployment steps. Instead, a web application can be used on any
computer that has Internet access. But when developers use client-side technologies, theyencounter a few familiar headaches. Suddenly, cross-browser compatibility becomes a problem. Developers are forced to test their websites with different operating systems and
browsers, and they might even need to distribute browser updates to their clients. In otherwords, the client-side model sacrifices some of the most important benefits of web
development. For that reason, ASP. NET is designed as a server-side technology. AllASP. NET code executes on the server. When the code is finished executing, the user
receives an ordinary HTML page, which can be viewed in any browser. Figure 1-3 showsthe difference between the server-side and the client-side model. These are some other
reasons for avoiding client-side programming:
Isolation: Client-side code can¶t access server-side resources. For example, a client-sideapplication has no easy way to read a file or interact with a database on the server (at leastnot without running into problems with security and browser compatibility).
Security: End users can view client-side code. And once malicious users understand how anapplication works, they can often tamper with it.Thin client s: As the Internet continues to evolve, web-enabled devices such as mobile phones, palmtop computers, and PDAs (personal digital assistants) are appearing. These
devices can communicate with web servers, but they don¶t support all the features of atraditional browser. Thin clients can use server-based web applications, but they won¶tsupport client-side features such as JavaScript.
However , client-side programming isn¶t truly dead. In many cases, ASP. NET allows you tocombine the best of client-side programming with server-side programming. For example
the best ASP. NET controls can intelligently detect the features of the client browser. If the
browser supports JavaScript, these controls will return a web page that incorporatesJavaScript for a richer , more responsive user interface. And in Chapter 25, you¶ll learn howyou can superchargeordinary ASP. NET pages with Ajax features, which use even more client-side JavaScript
However , no matter what the capabilities of the browser , your code is always executed onthe server. The client-side frills are just the icing on the cake. CHARACTERISTICS OF .NET
The .NET Framework As you¶ve already learned, the . NET Framework is really a cluster of several technologies.These include the following:
The .NE T languag es: These include Visual Basic, C#, JScript . NET (a server-side version ofJavaScript), J# (a Java clone), and C++. The Common Languag e Runtime (CLR): This is the
engine that executes all . NET programs and provides automatic services for theseapplications, such as security checking, memory management, and optimization. The .NE T
Framework cla ss library: The class library collects thousands of pieces of prebuilt
functionality that you can ³snap in´ to your applications. These features are sometimesorganized into technology sets, such as ADO. NET (the technology for creating database
applications) and Windows Forms (the technology for creating desktop user interfaces).
A SP.NET :- This is the engine that hosts the web applications you create with . NET, and supports almost
any feature from the . NET class library. ASP. NET also includes a set of web-specificservices, like secure authentication and data storage.V i sual Studio:-This optional development tool contains a rich set of productivity and debugging features.The Visual Studio setup DVD includes the complete . NET Framework , so you won¶t need to
download it separately. Sometimes the division between these components isn¶t clear. Forexample, the term ASP .NE T is sometimes used in a narrow sense to refer to the portion of the
. NET class libraryused to design web pages. On the other hand, ASP. NET also refers to the whole topic of
. NET web applications, which includes . NET languages and many fundamental pieces of theclass library that aren¶t web-specific. exhaustive examination of ASP. NET includes . NET
basics, the C# language, and topics that any . NET developer could use, such as component-
based programming and database access.)
THE MANY FACES OF ASP.NET
With ASP. NET 3.5, Microsoft aims to continue its success by refining and enhancingASP. NET. The good news is that Microsoft hasn¶t removed features, replaced functionality,
or reversed direction. Instead, almost all the changes add higher-level features that can make
your programming more productive.All in all, there have been four major releases ofASP. NET:
ASP .NE T 1.0: This first release created the core ASP. NET platform and introduced a widerange of essential features.
ASP .NE T 1.1: This second release added performance tune-ups and bug fixes, but no new
features. ASP .NE T 2.0: This third release piled on a huge set of new features, all of which were builton top of the existing ASP. NET plumbing. The overall emphasis was to supply developerswith prebuilt goodies that
they could use without writing much (if any) code. Some of the new features included built-in support for website navigation, a theming feature for standardizing web page design, and
ASP .NE T 3.5: This fourth release keeps the same basic engine asASP. NET 2.0, but adds a few frills and two more dramatic changes. The most significant
enhancement is the ASP. NET AJAX toolkit, which gives web developers better tools forcreating highly responsive web pages that incorporate richeffects usually seen in desktopapplications (such as drag-and-drop and autocomplete). The otherinnovation is support forLI NQ, a set of language enhancements included with . NET 3.5 that allows you to search in-memory data in the same way that you query a database.
If you¶re wondering what happened to ASP. NET 3.0²well, it doesn¶t exist! Somewhat
confusingly, Microsoft used the . NET 3.0 name to release a set of new technologies,
including Windows Presentation Foundation (WPF), a platform for building slick Windows
applications; Windows Workflow Foundation (WF), a platform for modeling applicationlogic using flowchart-style diagrams; and Windows Communication Foundation (WCF), a
platform for designing services that can be called from other computers. However , . NET 3.0
did not include an updated version of ASP. NET.
C#,VB, and the .NET Languages
C#, Microsoft¶s . NET language of preference. C# is a new language that was
designed for . NET 1.0. It resembles Java and C++ in syntax, but no direct migration pathexists from Java or C++. Interestingly, VB and C# are actually quite similar. Though thesyntax is different, both VB and C# use the . NET class library and are supported by the CLR
In fact, almost any block of C# code can be translated, line by line, into an equivalent block
of VB code (and vice versa). Anoccasional language difference pops up (for example, VB supports a language feature called
optional paramet er s, while C# doesn¶t), but for the most part, a developer who has learnedone . NET language can move quickly and efficiently to another.In short, both VB and C# are
elegant, modern languages that are ideal for creating the next generation of web applications.. NET 1.0 introduced completely new languages. However , the changes in subsequent versions of . NET
have been more subtle. Although the version of VB and C# in . NET 3.5 adds a few new features,
most parts of these languages remain unchanged. In Chapter 2 and Chapter 3, you¶ll sort through the syntax
of C#
and learn the basics of object-oriented programming
.
Intermediate Language:-All the . NET languages are compiled into another lower-level language before the code isexecuted. This lower-level language is the Common Intermediate Language (CIL, or just IL)
The CLR , the engine of . NET, uses only IL code. Because all . NET languages are designed based on IL, they all have profound similarities. This is the reason that the VB and C#languages provide essentially the same features and performance. In fact, the languages are
so compatible that a web page written with C# can use a VB component in the same way ituses a C# component,
and vice versa. The . NET Framework formalizes this compatibility with something called theCommon Language Specification (CLS). Essentially, the CLS is a contract that, if respected
guarantees that a component written in one . NET language can be used in all the others. One part of the CLS is the common type system (CTS), which defines the rules for data types
such as strings, numbers, and arrays that are shared in all . NET languages. The CLS also
ingredients such as classes, methods, events, and quite a bit more. For the most part, . NETdevelopers don¶t need to think about how the CLS works, even though they rely on it every
day. the . NET languages are compiled to IL. Every EXE or DLL file that you build with a. NET language contains IL code. This is the file you deploy to other computers. In the caseof a web application, you deploy your compiled code to a live web server. The CLR runs
only IL code, which means it has no idea which . NET language you originally used. Notice,
however , that the CLR actually performs another compilation step²it takes the IL code and
transforms it to native machine language code that¶s appropriate for the
current platform. This step occurs when the application is launched , just before the code isactually executed. In an ASP. NET application, these machine-specific files are cached while
the web application is running so they can be reused, ensuring optimum performance. You
might wonder why . NET compilers don¶t compile straight to machine code. The reason is that
the machine code depends on several factors, including the CPU. For example, if you create
machine codefor a computer with an Intel processor , the compiler may be able to use Hyper-Threading to
produce enhanced code. This machine-specific version isn¶t suitable for deployment to othe
computers, because no guarantee exists that they¶re using the same processor.
Other .NET Languages:-VB and C# aren¶t the only choices for ASP. NET development. Developers can also use J# (alanguage with Java-like syntax). You can even use a . NET language provided by a third- party developer , such as a . NET version of Eiffel or even COBOL. This increasing range of
language choices is possible thanks to the CLS and CTS, which define basic requirementsand standards that allow other companies to write languages that can be compiled to IL.
Although you can use any . NET language to create an ASP. NET web application, some ofthem do not provide the same level of design support in Visual Studio, and virtually allASP. NET developers use VB and C#. For more information about third-party . NET
languages.
The Common Language Runtime:-The CLR is the engine that supports all the . NET languages. Many modern languages use
runtimes. In VB 6, the runtime logic is contained in a DLL file named msvbvm60.dll. InC++, many applications link to a file named mscrt40.dll to gain common functionality.
These runtimes may provide libraries used by the language, or they may have the additionalresponsibility of executing the code (as with Java). Runtimes are nothing new, but the CLR
is Microsoft¶s most ambitious runtime to date. Not only does the CLR execute code, it also
provides a whole set of related services such as code verification, optimization, and objectmanagement.The CLR is the reason that some developers have accused . NET of being a Java clone. The
claim is fairly silly. It¶s true that . NET is quite similar to Java in key respects (both use a specialmanaged environment and provide features through a rich class library) , but it¶s also true thatevery programming language ³steals´ from and improves on previous programming languages.This includes Java, which adopted parts of the C/C++ language and syntax when it was createdOf course, in many other aspects . NET differs just as
All . NET code runs inside the CLR. This is true whether you¶re running a Windowsapplication or a web service. For example, when a client requests an ASP. NET web page, the
ASP. NET service runs inside the CLR environment, executes your code, and creates a finalHTML page to send to the client.The implications of the CLR are wide-ranging:
Deep language integration :- VB and C#, like all . NET languages, compile to IL. In other
words, the CLR makes no distinction between different languages²in fact, it has no way of
knowing what language was used to create an executable. This is far more than merelanguage compatibility; it¶s language int e gration.
Side-by- side execution :- The CLR also has the ability to load more than one version of a
component at a time. In other words, you can update a component many times, and the
correct version will be loaded and used for each application. As a side effect , multipleversions of the . NET Framework can be installed, meaning that you¶re able to upgrade to
new versions of ASP. NET without replacing the current version or needing to rewrite yourapplications. Fewer error s :- Whole categories of errors are impossible with the CLR. For example, the
CLR prevents many memory mistakes that are possible with lower-level languages such asC++. Along with these truly revolutionary benefits, the CLR has some potential drawbacks.
Here are three issues that are often raised by new developers but aren¶t always answered
Performance :- A typical ASP. NET application is much faster than a comparable ASP
application, because ASP. NET code is compiled to machine code before it¶s executed.
However , processor-crunching algorithms still can¶t match the blinding speed of well-writtenC++ code, because the CLR imposes some additional overhead. Generally, this is a factor
only in a few performance-critical high-workload applications (such as real-time games).With high-volume web applications, the potential bottlenecks are rarely processor-related but
are usually tied to the speed of an external resource such as a database or the web server¶sfile system. With ASP. NET caching and some well-written database code, you can ensure
excellent performance for any web application.
C ode tran s parency :- IL is much easier to disassemble, meaning that if you distribute acompiled application or component, other programmers may have an easier time determining
how your code works. This isn¶t much of an issue for ASP. NET applications, which aren¶tdistributed but are hosted on a secure web server
Que stionable cro ss-platform support :-
No one is entirely sure whether . NET will ever be adopted for use on other operating systemsand platforms. Ambitious projects such as Mono (a free implementation of . NET on LinuxUNIX, and Windows) are currently underway However; . NET will probably never have the
wide reach of a language such as Java because it incorporates too many different platform-specific and operating system±specific technologies and features. Although implementationsof . NET are available for other platforms, they aren¶t supported by Microsoft, and they
provide only a subset of the total range of features. The general consensus is that theseimplementations aren¶t ideal for mission-critical business systems.
The .NET Class Library :-The . NET class library is a giant repository of classes that provide prefabricated functionalityfor everything from reading an XML file to sending an e-mail message. If you¶ve had any
exposure to Java, you may already be familiar with the idea of a class library. However , the. NET class library is more ambitious and comprehensive than just about any other
programming framework. Any . NET language can use the . NET class library¶s features byinteracting with the right objects. This helps encourage consistency among different . NETlanguages and removes the need to install numerous components on your computer or web
server. Some parts of the class library include features you¶ll never need to use in webapplications other parts of the class library are targeted directly at web development. Still
more classes can be used in various programming scenarios and aren¶t specific to web or
Windows development. These include the base set of classes that define common variabletypes and the classes for data access, to name just a few. You¶ll explore the . NETFramework throughout this book.You can think of the class library as a well-stocked programmer¶s toolkit. Microsoft¶s
philosophy is that it will provide the tedious infrastructure so that application developersneed only to write business-specific code. For example, the . NET Framework deals withthorny issues like database transactions and concurrency, making sure that hundreds or
thousands of simultaneous users can request the same web page at once. You just add thelogic needed for your specific application.
Visual Studio:-The last part of . NET is the Visual Studio development tool, which provides a rich
environment where you can rapidly create advanced applications. Although in theory youcould create an ASP. NET application without Visual Studio (for example, by writing all the
source code in a text editor and compiling it with . NET¶s command-line compilers), this taskwould be tedious, painful, and prone to error. For that reason, all professional ASP. NET
developers use a design tool like Visual Studio. Some of the features of Visual Studioinclude the following: Page de sign :- You can create an attractive page with drag-and-drop ease using Visual
Studio¶s integrated web form designer. You don¶t need to understand HTML. Automatic error detection :-You could save hours of work when Visual Studio detects andreports an error before you run your application. Potential problems are underlined, just like
the ³spell-as-you-go´ feature found in many word processors. Debugging tool s :-Visual Studio retains its legendary debugging tools, which allow you to
watch your code in action and track the contents of variables. And you can test webapplications just as easily as any other application type, because Visual Studio has a built-in
web server that works just for debugging. I ntelliSen se: :-Visual Studio provides statement completion for recognized objects andautomatically lists information such as function parameters in helpful tool tips.
You don¶t need to use Visual Studio to create web applications. In fact, you might betempted to use the freely downloadable . NET Framework and a simple text editor to createASP. NET web pages and web services. However , in doing so you¶ll multiply your work , and
you¶ll have a much harder time debugging, organizing, and maintaining your code.Introduces the latest version of Visual Studio. Visual Studio is available in several editions.
The Standard Edition has all the features you need to build any type of application (Windows
or web). The Professional Edition and the Team Edition increase the cost and pile on moretools and frills. For example, they incorporate features for managing source code that¶s
edited by multiple people on a development team and running automated tests.The scaled-down Visual Web Developer Express Edition is a completely free
version of Visual Studio that¶s surprising capable, but it has a few significant limitations.Visual Web Developer Express Edition gives you full support for developing webapplications, but it doesn¶t support any other type of application. This means you can¶t use it
to develop separate components for use in your applications or to develop Windows
applications. However , rest assured that Visual Web Developer Express Edition is still a bona fide version of Visual Studio, with a similar set of features and development interface.
C# Language :-Before you can create an ASP. NET application, you need to choose a . NET language inwhich to program it. If you¶re an ASP or VB developer , the natural choice is VB 2008. If
you¶re a longtime Java programmer or old-hand C coder , or you just want to learn theofficial language of . NET, C# will suit you best.
This chapter presents an overview of the C# language. You¶ll learn about the data types youcan use, the operations you can perform, and the code you¶ll need to define functions loopsand conditional logic. This chapter assumes you¶ve programmed before and you¶re already
familiar with most of these concepts²you just need to see how they¶re implemented in C#.If you¶ve programmed with a similar language such as Java, you might find that the most
beneficial way to use this chapter is to browse through it without reading every section. Thisapproach will give you a general overview of the C# language. You can then return to this
chapter later as a reference when needed. But remember , though you can program anASP. NET application without mastering all the language details, this deep knowledge is
often what separates the casual programmer from the legendary programming guru.
<div class="loginbg1"><div style="width:210px; margin-left:13px; margin-right:4px; float:left;text-align:justify;">Remember that no authoring tool can automate the developmentprocess. Designing accessible websites requires you to understand accessibility </div>
</div></div></div>
</div>
<!------ left panel end ------>
<div style="width:715px; float:left; height:237px; margin-top:5px;"><div class="aboutheader"><h1>Welcome To Our Web Site</h1></div>
<div class="aboutbg3"><div class="arialblack12">
<div class="arialnprmal" style="padding:8px 8px 8px 8px;">TheBaranwal family was started by King Ahivarn, whose ancestors had moved to a placecalled Ahar in North India. Ahivaran renamed the Ahar kingdom after himself and foundedits capital as "Varn-sahar" (identified with modern Bulandshahar in present day WesternUP). His children were christened as Varnwal, a term that distorted to Barnwal over theyears.Book:Statistical, descriptive and historical account of the North-westernProvinces; page no:125; Edwin Thomas Atkinson.<br />
<br />King Ahivarn/Ahibaran has been said to be a king of the Tomar
caste.Although his dynasty was succeeded by Dors after hundreds of years, his familyadopted his name, continued his lineage and were called Baranwals. It is conjecturedthat by marital alliances the Dors also were assimilated in the family.</div>
<div class="arialnprmal" style="padding:8px 8px 8px 8px;">This guidecontains links to third-party websites that are not under the control of Macromedia,and Macromedia is not responsible for the content on any linked site. If you access athird-party website mentioned in this guide, then you do so at your own risk.
Macromedia provides these links only as a convenience.</div><div style="width:120px; float:right; margin-right:5px;"><ahref="#">Read more..</a> </div> <br />
to third-party websites that are not under the control of Macromedia, and Macromedia isnot responsible for the content on any linked site. If you access a third-party websitementioned in this guide, then you do so at your own risk. Macromedia provides theselinks only as a convenience.</div>
using System;using System.Collections;using System.Configuration;using System.Data;using System.Linq;using System.Web;using System.Web.Security;
using System.Web.UI;using System.Web.UI.HtmlControls;using System.Web.UI.WebControls;using System.Web.UI.WebControls.WebParts;using System.Xml.Linq;using System.Net.Mail;using System.Data.SqlClient;
public partial class forgot_pass : System.Web.UI.Page{
string subBody = "";SqlConnection con = new SqlConnection("Integrated Security=SSPI;Persist Security
Info=False;Initial Catalog=Bernawal;Data Source=VMKVEC-55E02648");SqlCommand com = new SqlCommand();SqlDataAdapter da = new SqlDataAdapter();DataSet ds = new DataSet();protected void Page_Load(object sender, EventArgs e){
ErrorMessage="re enter password" ControlToValidate="TextBox3" Display="Dynamic"SetFocusOnError="True"></asp:RequiredFieldValidator>
<asp:CompareValidator ID="CompareValidator1" runat="server"ErrorMessage="password did not match" ControlToCompare="TextBox2"ControlToValidate="TextBox3" SetFocusOnError="True"></asp:CompareValidator>
<tr><td align="center" valign="middle"><table><tr><td>The Baranwal family was started by King Ahivarn, whose ancestors had moved to a placecalled Ahar in North India. Ahivaran renamed the Ahar kingdom after himself and foundedits capital as "Varn-sahar" (identified with modern Bulandshahar in present day WesternUP). His children were christened as Varnwal, a term that distorted to Barnwal over theyears.Book:Statistical, descriptive and historical account of the North-westernProvinces; page no:125; Edwin Thomas Atkinson.
King Ahivarn/Ahibaran has been said to be a king of the Tomar caste.Although hisdynasty was succeeded by Dors after hundreds of years, his family adopted his name,
continued his lineage and were called Baranwals. It is conjectured that by maritalalliances the Dors also were assimilated in the family.
con.Open();da = new SqlDataAdapter("select id from Member_login where
mem_id='"+TextBox8.Text+"',status='grant'",con);
ds.Clear();
da.Fill(ds);
da = new SqlDataAdapter("select * from registration");Image2.ImageUrl = ds.Tables[0].Rows[0]["img"].ToString();Response.Write("<script>alert('authorised person')</script>");
intended to operate. Software Testing also provides an objective, independent view of the softwareto allow the business to appreciate and understand the risks at implementation of the software. Testtechniques include, but are not limited to, the process of executing a program or application with the
intent of finding software bugs.
Software Testing can also be stated as the process of validating and verifying that a software program/application/product:
1. meets the business and technical requirements that guided its design and development;
2. works as expected; and
3.
Can be implemented with the same characteristics.Software Testing, depending on the testing method employed, can be implemented at any time inthe development process. However , most of the test effort occurs after the requirements have been
defined and the coding process has been completed. Different software development models willfocus the test effort at different points in the development process. In a more traditional model, mostof the test effort occurs after the requirements have been defined and the coding process has been
completed. Newer development models, such as Agile or XP, often employ test driven development
and place an increased portion of the testing up front in thedevelopment process, in the hands of the developer.
Software testing topics
Scope:-
A primary purpose for testing is to detect software failures so that defects may be uncovered andcorrected. This is a non-trivial pursuit. Testing cannot establish that a product functions properly
under all conditions but can only establish that it does not function properly under specificconditions. The scope of software testing often includes examination of code as well as execution of
that code in various environments and conditions as well as examining the aspects of code: does itdo what it is supposed to do and do what it needs to do. In the current culture of software
development, a testing organization may be separate from the development team. There are various
roles for testing team members. Information derived from software testing may be used to correctthe process by which software is developed
Functional vs non-functional testingFunctional testing refers to tests that verify a specific action or function of the code. These are
usually found in the code requirements documentation, although some development methodologieswork from use cases or user stories. Functional tests tend to answer the question of "can the user do
this" or "does this particular feature
Non-functional testing refers to aspects of the software that may not be related to a specific functionor user action, such as scalability or security. Non-functional testing tends to answer such questionsas "how many people can log in at once", or "how easy is it to hack this software".
Defects and failures:-
Not all software defects are caused by coding errors. One common source of expensive defects iscaused by requirement gaps, e.g., unrecognized requirements, that result work".in errors of omission
by the program designer. A common source of requirements gaps is non-functional requirement
such as testability, scalability, maintainability, usability, performance, and security.
Software faults occur through the following processes. A programmer makes an error (mistake),which results in a defect (fault, bug) in the software source code. If this defect isexecuted, in certain situations the system will produce wrong results, causing a failure. Not all
defects will necessarily result in failures. For example, defects in dead code will never result infailures. A defect can turn into a failure when the environment is changed. Examples of thesechanges in environment include the software being run on a new hardware platform, alterations in
source data or interacting with different software. A single defect may result in a wide range of
A frequent cause of software failure is compatibility with another application, a new operatingsystem, or , increasingly, web browser version. In the case of lack of backward compatibility, this
can occur because the programmers have only considered coding their programs for , or testing the
software upon, "the lat est version of" this-or-that operating system. The unintended consequence ofthis fact is that: their latest work might not be fully compatible with earlier mixtures ofsoftware/hardware, or it might not be fully compatible with anot her important operating system. In
any case, these differences, whatever they might be, may have resulted in (unintended...) software
failures,
as witnessed by some significant population of computer users.This could be considered a "prevention oriented strategy" that fits well with the latest testing phasesuggested by Dave Gelperin and William C. Hetzel, as cited below.
Input combinations and preconditions:-
A very fundamental problem with software testing is that testing under all combinations of inputs
and preconditions (initial state) is not feasible, even with a simple product.[12][18] This means that the
number of defects in a software product can be very large and defects that occur infrequently aredifficult to find in testing. More significantly, non-functional dimensions of quality (how it issupposed to be versus what it is supposed to d o)²usability, scalability, performance, compatibility,
reliability²can be highly subjective; something that constitutes sufficient value to one person may
be intolerable to another.Static vs. dynamic testing:-
There are many approaches to software testing. Reviews, walkthroughs, or inspections are
considered as static testing, whereas actually executing programmed code with a given set of testcases is referred to as dynamic testing. Static testing can be (and unfortunately in practice often is)omitted. Dynamic testing takes place when the program itself is used for the first time (which is
generally considered the beginning of the testing stage). Dynamic testing may begin before the
program is 100% complete in order to test particular sections of code (modules or discretfunctions). Typical techniques for this are either using stubs/drivers or execution from a debugger
environment. For example, Spreadsheet programs are, by their very nature, tested to a large extentinteractively ("on the fly"), with results displayed immediately after each calculation or text
manipulation.Software verification and validation:-
Software testing is used in association with verification and validation:
y Verification: Have we built the software right? (i.e., does it match the specification).
y Validation: Have we built the right software? (i.e., is this what the customer wants).
The terms verification and validation are commonly used interchangeably in the industry; it is alsocommon to see these two terms incorrectly defined. According to the IEEE Standard Glossary of
Software Engineering Terminology:
Verification is the process of evaluating a system or component to determine whether the productsof a given development phase satisfy the conditions imposed at the start of that phase.Validation is the process of evaluating a system or component during or at the end of the
development process to determine whether it satisfies specified requirements.Software Quality Assurance (SQA):-
Though controversial, software testing may be viewed as an important part of the software qualityassurance (SQA) process.[12] In SQA, software process specialists and auditors take a broader
view on software and its development. They examine and change the software engineering processitself to reduce the amount of faults that end up in the delivered software: the so-called defect rat e. What constitutes an "acceptable defect rate" depends on the nature of the software. For example, anarcade video game designed to simulat e flying an airplane would presumably have a much higher
tolerance for defects than mission critical software such as that used to control the functions of anairliner that r eally i s flying!Although there are close links with SQA, testing departments often exist independently, and there
may be no SQA function in some companies.
Software Testing is a task intended to detect defects in software by contrasting a computer program's expected results with its actual results for a given set of inputs. By contrast, QA (QualityAssurance) is the implementation of policies and procedures intended to prevent defects from
occurring in the first place.
Testing methods:-
The box approach:-
Software testing methods are traditionally divided into black box testing and white box testing.These two approaches are used to describe the point of view that a test engineer takes whendesigning test cases.
Black box testing:-
Black box testing treats the software as a "black box"²without any knowledge of internalimplementation. Black box testing methods include: equivalence partitioning, boundary value
and specification-based testing.Specification-based testing:-Specification-based testing aims to test the functionality of software according to the applicable
requirements.[21] Thus, the tester inputs data into, and only sees the output from, the test object. This
level of testing usually requires thorough test cases to be provided to the tester , who then can simplyverify that for a given input, the output value (or behavior), either "is" or "is not" the same as the
expected value specified in the test case. Specification-based testing is necessary, but it isinsufficient to guard against certain risks.
Advantages and disadvantages:-The black box tester has no "bonds" with the code, and a tester's perception is very simple: a code
mu st have bugs. Using the principle, "Ask and you shall receive," black box testers find bugs where programmers do not. But, on the other hand, black box testing has been said to be "like a walk in a
dark labyrinth without a flashlight," because the tester doesn't know how the software being tested
was actually constructed. As a result, there are situations when (1) a tester writes many test cases tocheck something that could have been tested by only one test case , and/or (2) some parts of the
back-end are not tested at all.
Therefore, black box testing has the advantage of "an unaffiliated opinion," on the one hand, and the
disadvantage of "blind exploring," on the other.White box testing:-
White box testing is when the tester has access to the internal data structures and algorithmsincluding the code that implement these.Types of white box testingThe following types of white box testing exist:
y API testing (application programming interface) - Testing of the application using Public and
Private APIsy Code coverage - creating tests to satisfy some criteria of code coverage (e.g. , the test designer
can create tests to cause all statements in the program to be executed at least once)
y Fault injection methods - improving the coverage of a test by introducing faults to test code paths
y Mutation testing methodsy Static testing - White box testing includes all static testing
Test coverage:-
White box testing methods can also be used to evaluate the completeness of a test suite that was
created with black box testing methods. This allows the software team to examine parts of a systemthat are rarely tested and ensures that the most important function points have been tested.Two common forms of code coverage are:
y Function coverag e, which reports on functions executed
y S tat ement coverag e
,
which reports on the number of lines executed to complete the testThey both return a code coverage metric, measured as a percentage.Grey Box Testing:-
Grey box testing involves having access to internal data structures and algorithms for purposes ofdesigning the test cases, but testing at the user , or black-box level. Manipulating input data andformatting output do not qualify as grey box, because the input and output are clearly outside of the
"black-box" that we are calling the system under test. This distinction is particularly important when
conducting integration testing between two modules of code written by two different developerswhere only the interfaces are exposed for test. However , modifying a data repository does qualify asgrey box, as the user would not normally be able to change the data outside of the system under test.
Grey box testing may also include reverse engineering to determine, for instance, boundary values
or error messages.
Testing Levels:-
Tests are frequently grouped by where they are added in the software development process, or bythe level of specificity of the test.Unit Testing:-
Unit testing refers to tests that verify the functionality of a specific section of code, usually at the
function level. In an object-oriented environment, this is usually at the class level, and the minimalunit tests include the constructors and destructors.
[25]
These type of tests are usually written by developers as they work on code (white-box style) , toensure that the specific function is working as expected. One function might have multiple tests, to
catch corner cases or other branches in the code. Unit testing alone cannot verify the functionality ofa piece of software, but rather is used to assure that the building blocks the software uses work
independently of each other.
Integration Testing:-
Integration testing is any type of software testing that seeks to verify the interfaces between
components against a software design. Software components may be integrated in an iterative wayor all together ("big bang"). Normally the former is considered a better practice since it allowsinterface issues to be localised more quickly and fixed.Integration testing works to expose defects in the interfaces and interaction between integrated
components (modules). Progressively larger groups of tested software components corresponding to
elements of the architectural design are integrated and tested until the software works as asystem.[26] System Testing:-
System testing tests a completely integrated system to verify that it meets its requirements.[27]
System integration testing verifies that a system is integrated to any external or third party systemsdefined in the system requirements.Regression Testing:-
Regression testing focuses on finding defaults after a major code change has occurred. Specifically,
it seeks to uncover software regressions, or old bugs that have come back. Such regressions occurwhenever software functionality that was previously working correctly stops working as intended.Typically, regressions occur as an unintended consequence of program changes, when the newly
developed part of the software collides with the previously existing code. Common methods of
regression testing include re-running previously run tests and checking whether previously fixedfaults have re-emerged. The depth of testing depends on the phase in the release process and the riskof the added features. They can either be complete, for changes added late in the release or deemed
to be risky, to very shallow, consisting of positive tests on each feature, if the changes are early inthe release or deemed to be of low risk.
Acceptance testing:-
Acceptance testing can mean one of two things:1. A smoke test is used as an acceptance test prior to introducing a new build to the main testing
process, i.e. before integration or regression.
2. Acceptance testing performed by the customer ,
often in their lab environment on their ownHW, is known as user acceptance testing (UAT). Acceptance testing may be performed as
part of the hand-off process between any two phases of development.[citation needed ]
Alpha testing:-
Alpha t esting is simulated or actual operational testing by potential users/customers or an
independent test team at the developers' site. Alpha testing is often employed for off-the-shelf
software as a form of internal acceptance testing, before the software goes to beta testing.Beta testing:-
Beta t esting comes after alpha testing. Versions of the software, known as beta versions, arereleased to a limited audience outside of the programming team. The software is released to groups
of people so that further testing can ensure the product has few faults or bugs. Sometimes,
betaversions are made available to the open public to increase the feedback field to a maximal number
of future users.Non Functional Software Testing:-
Special methods exist to test non-functional aspects of software. In contrast to functional testing ,
which establishes the correct operation of the software (correct in that it matches the expected behavior defined in the design requirements), non-functional testing verifies that the softwarefunctions properly even when it receives invalid or unexpected inputs. Software fault injection, in
the form of fuzzing, is an example of non-functional testing. Non-functional testing, especially for
software, is designed to establish whether the device under test can tolerate invalid or unexpectedinputs, thereby establishing the robustness of input
validation routines as well as error-handling routines. Various commercial non-functional testingtools are linked from the Software fault injection page; there are also numerous open-source andfree software tools available that perform non-functional testing.Software performance testing, including Load testing:-
Performance testing, or Load testing checks to see if the software can handle large quantities of data
or users. This is generally referred to as software scalability. This activity of Non FunctionalSoftware Testing is often referred to as Endurance Testing.Stability testing:-
Stability testing checks to see if the software can continuously function well in or above anacceptable period. This activity of Non Functional Software Testing is oftentimes referred to as load(or endurance) testing.
Usability testing:-
Usability testing is needed to check if the user interface is easy to use and understand.Security testing:-
Security testing is essential for software that processes confidential data to prevent system intrusion
by hackers.
Internationalization and localization:-Internationalization and localization is needed to test these aspects of software, for which a pseudolocalization method can be used. It will verify that the application still works, even after it
has been translated into a new language or adapted for a new culture (such as different currencies ortime zones).Destructive testing:-
Destructive testing attempts to cause the software or a sub-system to fail, in order to test its
robustness.The testing process:-
Traditional CMMI or waterfall development model:-
A common practice of software testing is that testing is performed by an independent group of
testers after the functionality is developed,
before it is shipped to the customer.[28]
This practiceoften results in the testing phase being used as a project buffer to compensate for project delays ,
thereby compromising the time devoted to testing.
Another practice is to start software testing at the same moment the project starts and it is acontinuous process until the project finishes.Agile or Extreme development model:-
In counterpoint, some emerging software disciplines such as extreme programming and the agile
software development movement, adhere to a "test-driven software development" model. In this process, unit tests are written first, by the software engineers (often with pair programming in the
extreme programming methodology). Of course these tests fail initially; as they are expected toThen as code is written it passes incrementally larger portions of the test suites. The test suites are
continuously updated as new failure conditions and corner cases are discovered,
and they areintegrated with any regression tests that are developed. Unit tests are maintained along with the rest
of the software source code and generally integrated into the build process (with inherentlyinteractive tests being relegated to a partially manual build acceptance process).
A sample testing cycle:-
Although variations exist between organizations, there is a typical cycle for testing. The sample below is common among organizations employing the Waterfall development model.
y Requirements analysis: Testing should begin in the requirements phase of the software
development life cycle. During the design phase, testers work with developers in determining
what aspects of a design are testable and with what parameters those tests work.y Test planning: Test strategy, test plan, testbed creation. Since many activities will be carried
out during testing, a plan is needed.y Test development: Test procedures, test scenarios, test cases, test datasets, test scripts to use
in testing software.y Test execution: Testers execute the software based on the plans and tests and report any
errors found to the development team.
y Test reporting: Once testing is completed, testers generate metrics and make final reports ontheir test effort and whether or not the software tested is ready for release.
y Test result analysis: Or Defect Analysis, is done by the development team usually alongwith the client, in order to decide what defects should be treated, fixed, rejected (i.e. found
software working properly) or deferred to be dealt with later.
y Defect Retesting: Once a defect has been dealt with by the development team, it is retested by the testing team. AKA Resolution testing
y Regression testing: It is common to have a small test program built of a subset of tests , for
each integration of new, modified, or fixed software, in order to ensure that the latest delivery
has not ruined anything, and that the software product as a whole is still working correctly.y Test Closure: Once the test meets the exit criteria, the activities such as capturing the key
outputs, lessons learned, results, logs, documents related to the project are archived and used
as a reference for future projects.
Automated testing:-
Many programming groups are relying more and more on automated testing, especially groups thatuse Test-driven development. There are many frameworks to write tests in, and ContinuousIntegration software will run tests automatically every time code is checked into a version control
system.
While automation cannot reproduce everything that a human can do (and all the strange ways theythink of to do it), it can be very useful for regression testing. However , it does require a well-developed test suite of testing scripts in order to be truly useful.
Testing Tools:-
Program testing and fault detection can be aided significantly by testing tools and debuggers.Testing/debug tools include features such as:
y Program monitors, permitting full or partial monitoring of program code including:o Instruction Set Simulator , permitting complete instruction level monitoring and trace
facilitieso Program animation, permitting step-by-step execution and conditional breakpoint at
source level or in machine codeo Code coverage reports
y Formatted dump or Symbolic debugging, tools allowing inspection of program variables onerror or at chosen points
y Automated functional GUI testing tools are used to repeat system-level tests through the GUI
y Benchmarks, allowing run-time performance comparisons to be madey Performance analysis (or profiling tools) that can help to highlight hot spots and resource
usageSome of these features may be incorporated into an Integrated Development Environment (IDE).Measuring software testing:-
Usually, quality is constrained to such topics as correctness, completeness, security,
[citation needed ]but
can also include more technical requirements as described under the ISO standard ISO 9126, suchas capability, reliability, efficiency, portability, maintainability, compatibility, and usability.
There are a number of common software measures, often called "metrics", which are used to
measure the state of the software or the adequacy of the testing.
Bibliography:-
Reference Website:-
Here is a preliminary list of websites you may like to visit to keep up-to-date with
developments in PHP, Apache and MySQL. A fuller reference list is included in the