SOA For Middleware

1.
0 INTRODUCTION
1.1ORGANIZATION PROFILE
RNC Data Com Software Solutions is an IT solution provider for a dynamic

environment where business and technology strategies converge. Their approach focuses
on new ways of business combining IT innovation and adoption while also leveraging an
organizations current IT assets. Their work is with large global corporations and new
products or services and to implement prudent business and technology strategies in
todays environment.
RNC Data Coms range of expertise includes :
Software Development Services

Engineering Services
Systems Integration
Customer Relationship Management
Product Development
Electronic Commerce
Consulting
IT Outsourcing
We apply technology with innovation and responsibility to achieve two broad objectives:
Effectively address the business issues our customers face today.

Generate new opportunities that will help them stay ahead in the future.
This approach rests on :
A strategy where we architect, integrate and manage technology services and solutions -
we call it AIM for success.
A robust offshore development methodology and reduced demand on customer resources.
A focus on the use of reusable frameworks to provide cost and times benefits.
1
They combine the best people, processes and technology to achieve excellent results -
consistency. We offer customers the advantages of:
Speed:
They understand the importance of timing, of getting there before the competition. A rich
portfolio of reusable, modular frameworks helps jump-start projects. Tried and tested
methodology ensures that we follow a predictable, low - risk path to achieve results. Our track
record is testimony to complex projects delivered within and evens before schedule.
Expertise:
Our teams combine cutting edge technology skills with rich domain expertise. Whats
equally important - they share a strong customer orientation that means they actually start by
listening to the customer. Theyre focused on coming up with solutions that serve customer
requirements today and anticipate future needs.
A full service portfolio:
They offer customers the advantage of being able to architect, integrate and manage
technology services. This means that they can rely on one, fully accountable source instead of
trying to integrate disparate multi vendor solutions.
Services:
RNC Data Com is providing its services to companies which are in the field of
production, quality control etc with their rich expertise and experience and information
technology they are in best position to provide software solutions to distinct business
requirements.
2
1.2 OBJECTIVE AND SCOPE OF THE PROJECT
The main purpose for preparing this document is to give a general insight into the
analysis and requirements of the existing system or situation and for determining the operating
characteristics of the system.
Scope:
This Document plays a vital role in the development life cycle (SDLC). As it describes
the complete requirement of the system. It is meant for use by the developers and will be the
basic during testing phase. Any changes made to the requirements in the future will have to go
through formal change approval process.
Developers Responsibilities Overview:
The developer is responsible for:
1) Developing the system, which meets the SRS and solving all the requirements of the system?
2) Demonstrating the system and installing the system at client's location after the acceptance
testing is successful.
3) Submitting the required user manual describing the system interfaces to work on it and also
the documents of the system.
4) Conducting any user training that might be needed for using the system.
5) Maintaining the system for a period of one year after installation.
3
2.0 OPERATING ENVIRONMENT
2.1 SOFTWARE REQUIREMENTS:
Operating System : Windows NT/ Windows XP with IIS Server.
Language : ASP.NET, C#.
Front End : Microsoft Visual Studio.Net 2008.
Backend : SQL Server 2005
2.2 HARDWARE REQUIREMENTS:
Processor : Intel P-III Processor or later

Hard Disk : 300 GB
RAM : 256 MB RAM
4
3.0 SYSTEM ANALYSIS
3.1 Existing system
The Certificate Issuing Agencies are maintaining the information manually with the help of
Simple Applications
The Applications are MS Office or Ms Excel to carry on their day to day activities of recording
the information related to different companies which are approaching for various certificates
issued by the agency.
3.2 Proposed system
The development of the new system contains the following activities, which try to automate the
entire process keeping in view of the database integration approach.
User friendliness is provided in the application with various controls.
The system makes the overall project management much easier and flexible with security.
It can be accessed over the internet.
Data can be maintained in the centralized web server so that it can be shared with other agencies
binded with the ISO .
There is no risk of data mismanagement at any level while the project development is under
process.
Relationship between the Agency and Company can be maintained very easily.
It provides high level of security using different protocols like https etc.
5
3.3 System Requirements and Specifications
The software, ISO Visualizer is designed for management and issuance of certificates for
Industrial Standardization and Quality.
Functional Requirements:
Output Design:
Outputs from computer systems are required primarily to communicate the results
of processing to users. They are also used to provides a permanent copy of the results for later
consultation. The various types of outputs in general are:
. External Outputs, whose destination is outside the organization,.

. Internal Outputs whose destination is with in organization and they are
The users main interface with the computer.
. operational outputs whose use is purely with in the computer department.
. Interface outputs, which involve the user in communicating directly with Output
Definition .
The outputs should be defined in terms of the following points:

. Type of the output
. Content of the output
. Format of the output
.Location of the output
.Frequency of the output
.Volume of the output
.Sequence of the output
It is not always desirable to print or display data as it is held on a computer. It should be

decided as which form of the output is the most suitable.
6
For Example
. Will decimal points need to be inserted
. should leading zeros be suppressed.
Output Media:
In the next stage it is to be decided that which medium is the most appropriate for the
output. The main considerations when decideing about the output media are:
The suitability for the device to the particular application.

The need for a hard copy.
The response time required.
The location of the users
The software and hardware available.
Keeping in view the above description the project is to have outputs mainly
coming under the category of internal outputs. The main outputs desired according to the
requirement specification are:
The outputs were needed to be generated as a hot copy and as well as queries to be viewed on the
screen. Keeping in view these outputs, the format for the output is taken from the outputs, which
are currently being obtained after manual processing. The standard printer is to be used as output
media for hard copies.
Input design:
Input design is a part of overall system design. The main objective during the input desings is as
given below:
To produce a cost-effective method of input.

To achieve the highest possible level of accuracy.
To ensure that the input is acceptable and understood by the user.
7
Input Stages:
The main input stages can be listed as below:
Data recording
Data transcription
Data conversion
Data verification
Data control
Data transmission
Data validation
Data correction
Input Types:
It is necessary to determine the various types of inputs. Inputs can be categorized as

follows:
External inputs, which are prime inputs for the system.

Internal inputs, which are user communications with the system.
Operational, which are computer departments communications to the system?
Interactive, which are inputs entered during a dialogue.
Input Media:
At this stage choice has to be made about the input media. To conclude about the input
media consideration has to be given to:
Type of input
Flexibility of format
Speed
8
Accuracy
Verification methods
Rejection rates
Ease of correction
Storage and handling requirements
Security
Easy to use
Portabilility
Keeping in view the above description of the input types and input media, it can be said
that most of the inputs are of the form of internal and interactive. As
Input data is to be the directly keyed in by the user, the keyboard can be considered to be the
most suitable input device.
Error Avoidance:
At this stage care is to be taken to ensure that input data remains accurate form the stage
at which it is recorded upto the stage in which the data is accepted by the system. This can be
achieved only by means of careful control each time the data is handled.
Error Detection:
Even though every effort is make to avoid the occurrence of errors, still a small
proportion of errors is always likely to occur, these types of errors can be discovered by using
validations to check the input data.
Data Validation:
Procedures are designed to detect errors in data at a lower level of detail. Data
validations have been included in the system in almost every area where there is a possibility for
the user to commit errors. The system will not accept invalid data. Whenever an invalid data is
keyed in, the system immediately prompts the user and the user has to again key in the data and
9
the system will accept the data only if the data is correct. Validations have been included where
necessary.
The system is designed to be a user friendly one. In other words the system has been
designed to communicate effectively with the user. The system has been designed with popup
menus.
User Interface design:
It is essential to consult the system users and discuss their needs while designing the user
interface:
User Interface systems can be classified as:
1. User initiated interface the user is in charge, controlling the progress of the
user/computer dialogue. In the computer-initiated interface, the computer selects the next
stage in the interaction.
2. Computer initiated interfaces. In the computer initiated interfaces the computer
guides the progress of the user/computer dialogue. Information is displayed and the user
response of the computer takes action or displays further information.
User Initiated Interfaces:
User initiated interfaces fall into tow approximate classes:
1. Command driven interfaces: In this type of interface the user inputs

commands or queries which are interpreted by the computer.
2. Forms oriented interface: The user calls up an image of the form to his/her
screen and fills in the form. The forms oriented interface is chosen because it is
the best choice.
Computer Initiated Interfaces:
The following computer initiated interfaces were used:
1. The menu system for the user is presented with a list of alternatives and the
user chooses one; of alternatives.
10
2. Questions answer type dialog system where the computer asks question and
takes action based on the basis of the users reply.
Right from the start the system is going to be menu driven, the opening menu displays the
available options. Choosing one option gives another popup menu with more options. In this
way every option leads the users to data entry form where the user can key in the data.
Error Message Design:
The design of error messages is an important part of the user interface design. As user is
bound to commit some errors or other while designing a system the system should be designed to
be helpful by providing the user with information regarding the error he/she has committed.
This application must be able to produce output at different modules for different inputs.
Performance Requirements:
Performance is measured in terms of the output provided by the application.
Requirement specification plays an important part in the analysis of a system. Only when
the requirement specifications are properly given, it is possible to design a system, which will fit
into required environment. It rests largely in the part of the users of the existing system to give
the requirement specifications because they are the people who finally use the system. This is
because the requirements have to be known during the initial stages so that the system can be
designed according to those requirements. It is very difficult to change the system once it has
been designed and on the other hand designing a system, which does not cater to the
requirements of the user, is of no use.
The requirement specification for any system can be broadly stated as given below:
The system should be able to interface with the existing system

The system should be accurate
The system should be better than the existing system
The existing system is completely dependent on the user to perform all the duties.
11
3.4 Feasibility Study
Feasibility study is conducted once the problem is clearly understood. Feasibility study is
a high level capsule version of the entire system analysis and design process. The
objective is to determine quickly at a minimum expense how to solve a problem. The
purpose of feasibility is not to solve the problem but to determine if the problem is worth
solving.
The system has been tested for feasibility in the following points.
1. Technical Feasibility
2. Economical Feasibility
3. Operational Feasibility.
1. Technical Feasibility:
The proposed system can be developed using existing technology or not. It

is planned to implement the proposed system using ASP.NET with C# and
databases are SQL Server 2005.
The organization already possesses Windows XP & Windows 2000 server with
Internet information Server (IIS) & Data bases. It is evident that the necessary
hardware and software are available for development and implementation of the
proposed system.
2. Economical Feasibility:
It is an evaluation of development cost weighed against the ultimate

income or benefit derived from the developed system. Economic justification
includes a broad range of concerns that includes cost-benefit analysis, long-term
corporate income strategies, cost of resources needed for development.
The Organization has in place, the required Hardware for implementing

the proposed system. The Organization has already satellite link, and a host of
servers so it need not invest newly for the Internet connection. So the
12
Organization need not incur any additional expenditure.
3. Operational Feasibility:
This test of feasibility asks if the system will work with least difficulties
when it is developed and installed. The technical staff has sufficient knowledge of
the tools being used and the users need just to know how to access and browse the
site. Hence it is concluded that the system is operationally feasible.
3.5 Modules of the project

The entire project is divided into six main modules. They are as follows
1 Enquiry
2. Quotation
3. Audit info/surveillance
4. Auditors
5. Reports
6. Administrator
FUNCTIONALITY OF EACH MODULE
1. ENQUIRY:Enquiry Module is the initial module in the SOA FOR MIDDLEWARE where the
user is provided with three possible options. They are Browse, Create and Modify.
1.1. Browse :
Once the user clicks the Browse option he will be able to view all the
information of the registered enquiries with all the details like Enquiry No,
Company Name, SIC Code and with a small button Details. Once we click the
button details then the detailed information of that enquiry is been displayed.
1.2 Create:
When he clicks the option Create then he will be provided with a form
with the following options New / Re-registration / Scope Enhancement / up
gradation. When the user selects the option New then the user will be provided
13
with a registration form with all the details, once he fills the details and says
update a new record of enquiry is created. When the user wants to Re-
registration / Scope Enhancement / Up gradation the existing enquiry then he has
the select the respective option along with the existing Certificate No / File No /
Enquiry No then the Detailed Enquiry form of that particular corresponding
Certificate No / File No / Enquiry No is displayed then that particular option Re-
registration /Scope Enhancement / Up gradation is changed according to the
requirement and updated into the database with an button Update. If we want to
cancel the transaction then click on the other button Cancel.
1.3 Modify:
When he clicks the option Modify he will be provided with a form

provided with the options Enquiry No / Organization Name /SIC code and two
buttons Search and Cancel. Once the user provides with any one of the following
options and say Search then the Enquiry No / Organization Name / SIC Code of
that particular option is retrieved from the database and displayed with the buttons
Modify and Add Address. Once we say Modify then that particular record is
modified, and if we say Add address then he can add the address to that particular
option selected by him.
2. QUOTATION: This Quotation module strictly deals with the quotation involved with the
enquiry. This module has mainly four options in the form; they are Browse / Create / Modify /
Approve.
2.1 Browse:
When the user clicks on the Quotation Module the default option which is
selected is Browse. It generally displays all the Quotations of the Enquiries with the
following fields as Quotation No / Quotation Date /Enquiry No / Organization Name and
a button named Details. Once the user clicks on the button details then the detailed
information of that Quotation number is being displayed with all the fee structure
involved with it.
14
2.2 Create:
When the user clicks on the Create Option then the information required to define
a new quotation includes an enquiry number for which the quotation is being given,
quotation no, date and fee charges (in rupees, dollars) for the various services is being
filled and updated with the button update to the data base.
2.3 Modify:
When the user clicks on the Modify Option then the form with Enquiry No /
Organization Name / Quotation No is viewed .Once the user fills in Company Name /
quotation no / quotation date , the system will search for the quotation on the search
criteria and the details of that quotation is displayed along with a button Modify , once
the Modify is clicked by the User then the detailed information of that quotation with its
approval status and fee is displayed , so the user can make necessary changes and say
update to Modify the changes and reflect them back into the database.
2.4 Approve:
When the user clicks on the Approve Option then the form with Enquiry No /
Organization Name is displayed along with the buttons Search and Cancel. Once the user
fills the Enquiry No / Organization Name and say search then the detailed information of
that quotation is being displayed along with its approval status is viewed. When the Is
Approved status is not Approved then a button named Approve is displayed once the user
clicks on it the status changes to Approved and the changes are reflected to the data base.
3. AUDITS : Audits is the module which deals with the Auditing details of the Enquiries.
Once the user clicks the Module Audits a form with Enquiry No / Company Name / Quotation
No / Certificate No with the buttons Search and cancel is displayed. Once the user fills Enquiry
No / Company Name /Quotation No / Certificate No then search Enquiries will be displayed
according to the search criteria with a button File Info. Once the User clicks the button File Info
then the complete filed Information of that Enquiry is being displayed with a button Audit Info.
Once the user clicks the Audit Info. Button then the complete audit Information regarding that
Enquiry is displayed with the following options in that Form and buttons Follow Ups, Update,
Reset. They are as follows:
15
3.1 Document Review.
3.2 Pre-Assessment.
3.3. Conformance.
3.4. Surveillance.
3.1. Document Review :
Document Review is the default option selected when the user clicks on
the Audit Info. Button with this Option the User is able to Review the Complete
Information of the Companies File regarding the Auditing and also the Status of the
Certificate Standards. In this Form the user is also provided with the buttons Follow Ups ,
Update and Reset. With the Update / Reset buttons he can manipulate the data
accordingly and reset the data if not necessary. Once he clicks on the Follow Ups then he
will be drive to the Screen where he will be provided the information of the Follow Ups
and with two possible buttons New Follow Ups and Cancel. When the User want to
create New Follow Ups he will click on New Follow Ups button , and Press Cancel if he
needs to cancel the data.
3.2. Pre-Assessment :
When the User clicks on the option Pre-Assessment then the user will be
provided with all the detailed Information of the Company with the Enquiry No,
Quotation No, Fee Details, Certificate Details , Audit Information and the Auditors
involved in this aspect is being Displayed on the Screen. Here the main theme of this Pre-
Assessment module is to Review the Audit Information of the Company before going to
the Final Audit of the company for the conformance of the Certification. The user have
options to add the Auditors according to the requirement and delete the Auditors with the
provided buttons Add Auditor / Add Prov. Auditors / Add Tech Auditors / Delete Auditors
/ Delete Prov. Auditors , once the entire Audit Information is reviewed by the team of the
Auditors and
make necessary changes then the user is provided with an button Update to
reflected the changes in the database and Reset button to set the changes to the old data.
The Pre-Assessment Module is so Flexible that it even provides Flexible Options
like Feed Back / Follow Ups / Communications.
16
3.2.1 Feed Back :
The user is provided with an option Feedback to give the feed back on the
Audit Information . Once he clicks on the button Feed Back then user is being displayed
with the entire Audit Information and the Feed Types like Lead Auditors On Auditors /
Auditors on Company / Company on Auditors / Lead Auditor Feedback on company /
Company on AQA. Hence from these different types we can get the Feed Back on
different level of Hierarchies involved in the Audit on different aspects. Once he Selects
the Feed Back Type and say Go he will be driven to the screen with detailed Feed backs ,
he is also provided with an Button New Entry to give his fresh Feed Back and save to the
data base.
3.2.2 Follow Ups :
Once the user clicks on the button Follow Ups then he will be driven to the
Screen viewed with all the detailed Follow ups made earlier and with two option buttons
New Follow Ups / Cancel.
Once the user clicks on the New Follow Ups he is allowed to give the necessary
Follow ups and Update the database, and say Cancel if he wants to cancel the present
Follow Up.
3.2.3 Communication :
Once the user clicks on the button Communication then the user will be driven to
the Complete Audit Information of the Company with different of Communication Types
like AQA(I) to Auditors / AQA(I) to Company / AQA(I) to AQA(I)-USA.
i) AQA(I) to Auditors : Communication is made from AQA(I) to the Auditors
involved in the Audit of the Company.
ii) AQA(I) to Company : Communication is made from AQA(I) to Company for
which the Audit is being done.
iii) AQA(I) to AQA(I)-USA.: Communication is made from AQA in India to AQA
in U.S.A.
Once the user selects the following Communication Type and say Go he will be
provided with all the details of that Communication Type with a button New Entry. Once
he clicks on that Button he will able to create a new Communication Entry and save it to
the database.
17
3.3. Comformance:
Once the User Clicks on the Conformance of the Audits Module then he
will be displayed with all the detailed information of the Audit Information with all the
Conformance details of the Certificate, Fee details with the following buttons . They are
Feed Backs / Communication / Follow Ups / Update / Reset.
The Feed Back / communication / Follow Ups buttons performs the same
functions as performed in the Pre-Assessment sub module. Hence once all the Audit
Information is confirmed and the Certificate details are correct or if he wants can make
necessary changes and say Update then the entire data is reflected and saved into the
database, when he says Reset then the Changed data will be reset to the old one.
3.4.Surveillance :
Surveillance is a Audit Check report for the certification , Surveillance check is
done to every company within a specified periods like for 3 months / 6 months / 9
months. Surveillance is left to the company for how many months the check should be
carried for the Certificate. Hence depending upon how many times the surveillance check
carried for the company , that would be reflected for that Enquiry as Surveillance I /
Surveillance II and son on.
4.AUDITORS : Auditors Module is the fourth module in the SOA FOR MIDDLEWARE
where the user is provided with three possible options . They are Browse, Create and Modify.
4.1. Browse :
Once the user clicks the Browse option he will be able to view all the
information of the registered Auditors with all the details like Auditor Type,
Auditor Name , Auditor SIC Code and with a small button Details. Once we click
the button details then the detailed information of that Auditor is been displayed.
4.2. Create:
When the user clicks the option Create then he will be provided with a
form with the following Auditor Information fields like Auditor Type , Auditor
Name , Qualification ,Experience , IRCA No , LACourseDate , Lacerate and the
complete personal information of that particular Auditor. Once he fills the details
18
and says Update, a new record of that Auditor is created. If we want to cancel the
transaction then click on the other button Cancel.
4.3. Modify:
When he clicks the option Modify he will be provided with a form

provided with the options Auditor Type / Auditor Name /SIS code / IsActive and
two buttons Search and Cancel. Once the user provides with any one of the
following options and say Search then the Auditor Type / Auditor Name / SIS
Code of that particular option is retrieved from the database and displayed with
the buttons Modify and Add Address. Once we say Modify then that particular
record is modified, and if we says Add address then he can add the address to that
particular option selected by him.
5. ADMINISTRATOR: Once the User clicks on the Admin Module, then the module is being
displayed with all the registered users in this Project with two buttons Modify /Delete, to modify
the required record or delete it. The Entire Module Administration is provided with 8 options.
They are:
5.1 Users
5.2 Accre Body
5.3 Certificate
5.4 Audit Frequency
5.5 Auditor
5.6 Communication
5.7 Feedback
5.8 Audit
5.1 Users :
Once the user clicks on the Administration module he will see the
User sub module as default. The user is provided with all the details of
the Users involved in this project like User Name / User Type. They also
have an option to Modify the changes by providing button Modify and
New Entry button to create a new User with all the information and save
it to the database.
19
5.2 Accreditation Body :
Once the user clicks on this option then he will driven to the screen
with all the information of the Accreditation with the following fields
Accreditation Type / Description. They are also provided with buttons
Modify , to modify the changes in any required record and New Entry
to create new Accreditation with all the information and save it to the
database.
5.3 Certificate :
Once the use clicks on this option then he will driven to the screen
with all the information of the Certificate with the following fields
Certificate Type / Description . They are also provided with buttons
Modify , to modify the changes in any required record and New Entry
to create new Certificate with all the information and save it to the
database.
5.4 Audit Frequency :
with all the information of the Audit Frequency with the following fields
Audit Frequency Type / Description (whether the audit is done once
3/6/9 months). They are also provided with buttons Modify, to modify
the changes in any required record and New Entry to create new Audit
Frequency with all the information and save it to the database.
5.4 Auditor :
with all the information of the Auditor with the following fields Auditor
Type / Description. They are also provided with buttons Modify, to
modify the changes in any required record and New Entry to create new
Auditor with all the information and save it to the database.
5.5 Communications :
with all the information of the Communications with the following fields
Communication Type / Description. This Option will be able to explain
20
the user with all the possible communications whether the
communications are from AQA(I) to Auditors or AQA(I) to Company or
AQA(I) to AQA(U.S.A). Hence this is the key option for the
communication in the company.
5.6 Feed Back :
with all the information of the Feed Back with the following fields Feed
Back Type / Description. This Option will be able to explain the user
with all the possible Feed Back whether the Feed Back is from Lead
Auditor on Auditor , Auditors on Company , Company on Auditors ,
Lead Auditor Feed back on Company, Company on AQA. Hence this is
the key option for the communication in the company.
5.7 Audit :
with all the information of the Audit with the following fields Audit
Type / Description. This Option will be able to explain the user with all
the possible Audits like Documentation review , Pre-Assessment ,
Conformance , Surveillance, Special Audit information.
6. REPORTS: This Module includes the complete information about the database. The
information is displayed in the specified format based on the requirement. In this we are generate
the reports in the following manner
Company wise reports
Communication reports
Feedback reports
Certification wise reports
File no wise report
Audit report
Auditor report
Between date wise report and Available auditors Reports
21
4.0 SYSTEM DEVELOPMENT ENVIRONMENT
Microsoft.NET Framework
The .NET Framework is a new computing platform that simplifies application development in
the highly distributed environment of the Internet. The .NET Framework is designed to fulfill the
following objectives:
To provide a consistent object-oriented programming environment whether object code is

stored and executed locally, executed locally but Internet-distributed, or executed
remotely.
To provide a code-execution environment that minimizes software deployment and
versioning conflicts.
To provide a code-execution environment that guarantees safe execution of code,

including code created by an unknown or semi-trusted third party.
To provide a code-execution environment that eliminates the performance problems of

scripted or interpreted environments.
To make the developer experience consistent across widely varying types of applications,
such as Windows-based applications and Web-based applications.
To build all communication on industry standards to ensure that code based on the .NET
Framework can integrate with any other code.
The .NET Framework has two main components: the common language runtime and the .NET
Framework class library. The common language runtime is the foundation of the .NET
Framework. You can think of the runtime as an agent that manages code at execution time,
providing core services such as memory management, thread management, and remoting, while
also enforcing strict type safety and other forms of code accuracy that ensure security and
robustness. In fact, the concept of code management is a fundamental principle of the runtime.
Code that targets the runtime is known as managed code, while code that does not target the
runtime is known as unmanaged code. The class library, the other main component of the .NET
22
Framework, is a comprehensive, object-oriented collection of reusable types that you can use to
develop applications ranging from traditional command-line or graphical user interface (GUI)
applications to applications based on the latest innovations provided by ASP.NET, such as Web
Forms and XML Web services.
The .NET Framework can be hosted by unmanaged components that load the common language
runtime into their processes and initiate the execution of managed code, thereby creating a
software environment that can exploit both managed and unmanaged features. The .NET
Framework not only provides several runtime hosts, but also supports the development of third-
party runtime hosts.
For example, ASP.NET hosts the runtime to provide a scalable, server-side environment for
managed code. ASP.NET works directly with the runtime to enable Web Forms applications and
XML Web services, both of which are discussed later in this topic.
Internet Explorer is an example of an unmanaged application that hosts the runtime (in the form
of a MIME type extension). Using Internet Explorer to host the runtime enables you to embed
managed components or Windows Forms controls in HTML documents. Hosting the runtime in
this way makes managed mobile code (similar to Microsoft ActiveX controls) possible, but
with significant improvements that only managed code can offer, such as semi-trusted execution
and secure isolated file storage.
The following illustration shows the relationship of the common language runtime and the class
library to your applications and to the overall system. The illustration also shows how managed
code operates within a larger architecture.
Features of the Common Language Runtime
The common language runtime manages memory, thread execution, code execution, code safety
verification, compilation, and other system services. These features are intrinsic to the managed
code that runs on the common language runtime.
23
With regards to security, managed components are awarded varying degrees of trust, depending
on a number of factors that include their origin (such as the Internet, enterprise network, or local
computer). This means that a managed component might or might not be able to perform file-
access operations, registry-access operations, or other sensitive functions, even if it is being used
in the same active application.
The runtime enforces code access security. For example, users can trust that an executable
embedded in a Web page can play an animation on screen or sing a song, but cannot access their
personal data, file system, or network. The security features of the runtime thus enable legitimate
Internet-deployed software to be exceptionally feature rich.
The runtime also enforces code robustness by implementing a strict type- and code-verification
infrastructure called the common type system (CTS). The CTS ensures that all managed code is
self-describing. The various Microsoft and third-party language compilers
Generate managed code that conforms to the CTS. This means that managed code can consume
other managed types and instances, while strictly enforcing type fidelity and type safety.
In addition, the managed environment of the runtime eliminates many common software issues.
For example, the runtime automatically handles object layout and manages references to objects,
releasing them when they are no longer being used. This automatic memory management
resolves the two most common application errors, memory leaks and invalid memory references.
The runtime also accelerates developer productivity. For example, programmers can write
applications in their development language of choice, yet take full advantage of the runtime, the
class library, and components written in other languages by other developers. Any compiler
vendor who chooses to target the runtime can do so. Language compilers that target the .NET
Framework make the features of the .NET Framework available to existing code written in that
language, greatly easing the migration process for existing applications.
While the runtime is designed for the software of the future, it also supports software of today
and yesterday. Interoperability between managed and unmanaged code enables developers to
continue to use necessary COM components and DLLs.
24
The runtime is designed to enhance performance. Although the common language runtime
provides many standard runtime services, managed code is never interpreted. A feature called
just-in-time (JIT) compiling enables all managed code to run in the native machine language of
the system on which it is executing. Meanwhile, the memory manager removes the possibilities
of fragmented memory and increases memory locality-of-reference to further increase
performance.
Finally, the runtime can be hosted by high-performance, server-side applications, such as

Microsoft SQL Server and Internet Information Services (IIS). This infrastructure enables
you to use managed code to write your business logic, while still enjoying the superior
performance of the industry's best enterprise servers that support runtime hosting.
.NET Framework Class Library

The .NET Framework class library is a collection of reusable types that tightly integrate with the
common language runtime. The class library is object oriented, providing types from which your
own managed code can derive functionality. This not only makes the .NET Framework types
easy to use, but also reduces the time associated with learning new
features of the .NET Framework. In addition, third-party components can integrate seamlessly
with classes in the .NET Framework.
For example, the .NET Framework collection classes implement a set of interfaces that you can
use to develop your own collection classes. Your collection classes will blend seamlessly with
the classes in the .NET Framework.
As you would expect from an object-oriented class library, the .NET Framework types enable
you to accomplish a range of common programming tasks, including tasks such as string
management, data collection, database connectivity, and file access. In addition to these common
tasks, the class library includes types that support a variety of specialized development scenarios.
For example, you can use the .NET Framework to develop the following types of applications
and services:
Console applications.
25
Scripted or hosted applications.
Windows GUI applications (Windows Forms).
ASP.NET applications.
XML Web services.
Windows services.
For example, the Windows Forms classes are a comprehensive set of reusable types that vastly
simplify Windows GUI development. If you write an ASP.NET Web Form application, you can
use the Web Forms classes.
Client Application Development
Client applications are the closest to a traditional style of application in Windows-based

programming. These are the types of applications that display windows or forms on the desktop,
enabling a user to perform a task. Client applications include applications such as word
processors and spreadsheets, as well as custom business applications such as data-entry tools,
reporting tools, and so on. Client applications usually employ windows, menus, buttons, and
other GUI elements, and they likely access local resources such as the file system and peripherals
such as printers.
Another kind of client application is the traditional ActiveX control (now replaced by the
managed Windows Forms control) deployed over the Internet as a Web page. This application is
much like other client applications: it is executed natively, has access to local resources, and
includes graphical elements.
In the past, developers created such applications using C/C++ in conjunction with the Microsoft
Foundation Classes (MFC) or with a rapid application development (RAD) environment such as
Microsoft Visual Basic. The .NET Framework incorporates aspects of these existing products
into a single, consistent development environment that drastically simplifies the development of
client applications.
26
The Windows Forms classes contained in the .NET Framework are designed to be used for GUI
development. You can easily create command windows, buttons, menus, toolbars, and other
screen elements with the flexibility necessary to accommodate shifting business needs.
For example, the .NET Framework provides simple properties to adjust visual attributes
associated with forms. In some cases the underlying operating system does not support changing
these attributes directly, and in these cases the .NET Framework automatically recreates the
forms. This is one of many ways in which the .NET Framework integrates the developer
interface, making coding simpler and more consistent.
Unlike ActiveX controls, Windows Forms controls have semi-trusted access to a user's computer.
This means that binary or natively executing code can access some of the resources on the user's
system (such as GUI elements and limited file access) without being able to access or
compromise other resources. Because of code access security, many applications that once
needed to be installed on a user's system can now be safely deployed through the Web. Your
applications can implement the features of a local application while being deployed like a Web
page.
C#.NET
Introduction
ACTIVE X DATA OBJECTS.NET:
ADO.NET Overview:
ADO.NET is an evolution of the ADO data access model that directly addresses user
requirements for developing scalable applications. It was designed specifically for the web with
scalability, statelessness, and XML in mind.
ADO.NET uses some ADO objects, such as the Connection and Command objects, and also
introduces new objects. Key new ADO.NET objects include the DataSet, DataReader, and
DataAdapter.
27
The important distinction between this evolved stage of ADO.NET and previous data
architectures is that there exists an object -- the DataSet -- that is separate and distinct from any
data stores. Because of that, the DataSet functions as a standalone entity. You can think of the
DataSet as an always disconnected recordset that knows nothing about the source or destination
of the data it contains. Inside a DataSet, much like in a database, there are tables, columns,
relationships, constraints, views, and so forth.
A DataAdapter is the object that connects to the database to fill the DataSet. Then, it connects
back to the database to update the data there, based on operations performed while the DataSet
held the data. In the past, data processing has been primarily connection-based. Now, in an effort
to make multi-tiered apps more efficient, data processing is turning to a message-based approach
that revolves around chunks of information. At the center of this approach is the DataAdapter,
which provides a bridge to retrieve and save data between a DataSet and its source data store. It
accomplishes this by means of requests to the appropriate SQL commands made against the data
store.
The XML-based DataSet object provides a consistent programming model that works with all
models of data storage: flat, relational, and hierarchical. It does this by having no 'knowledge' of
the source of its data, and by representing the data that it holds as collections and data types. No
matter what the source of the data within the DataSet is, it is manipulated through the same set
of standard APIs exposed through the DataSet and its subordinate objects.
While the DataSet has no knowledge of the source of its data, the managed provider has detailed
and specific information. The role of the managed provider is to connect, fill, and persist the
DataSet to and from data stores. The OLE DB and SQL Server .NET Data Providers
(System.Data.OleDb and System.Data.SqlClient) that are part of the .Net Framework provide
four basic objects: the Command, Connection, DataReader and DataAdapter. In the
remaining sections of this document, we'll walk through each part of the DataSet and the OLE
DB/SQL Server .NET Data Providers explaining what they are, and how to program against
them.
28
The following sections will introduce you to some objects that have evolved, and some that are
new. These objects are:
Connections. For connection to and managing transactions against a database.

Commands. For issuing SQL commands against a database.
DataReaders. For reading a forward-only stream of data records from a SQL Server
data source.
DataSets. For storing, remoting and programming against flat data, XML data and
relational data.
DataAdapters. For pushing data into a DataSet, and reconciling data against a
database.
When dealing with connections to a database, there are two different options: SQL Server .NET
Data Provider (System.Data.SqlClient) and OLE DB .NET Data Provider (System.Data.OleDb).
In these samples we will use the SQL Server .NET Data Provider. These are written to talk
directly to Microsoft SQL Server. The OLE DB .NET Data Provider is used to talk to any OLE
DB provider (as it uses OLE DB underneath).
Connections
Connections are used to 'talk to' databases, and are respresented by provider-specific classes such
as SQLConnection. Commands travel over connections and resultsets are returned in the form
of streams which can be read by a DataReader object, or pushed into a DataSet object.
Commands
Commands contain the information that is submitted to a database, and are represented by
provider-specific classes such as SQLCommand. A command can be a stored procedure call, an
UPDATE statement, or a statement that returns results. You can also use input and output
parameters, and return values as part of your command syntax. The example below shows how to
issue an INSERT statement against the Northwind database.
29
DataReaders
The DataReader object is somewhat synonymous with a read-only/forward-only cursor over

data. The DataReader API supports flat as well as hierarchical data. A DataReader object is
returned after executing a command against a database. The format of the returned DataReader
object is different from a recordset. For example, you might use the DataReader to show the
results of a search list in a web page.
DataSets and DataAdapters
DataSets
The DataSet object is similar to the ADO Recordset object, but more powerful, and with one
other important distinction: the DataSet is always disconnected. The DataSet object represents a
cache of data, with database-like structures such as tables, columns, relationships, and
constraints. However, though a DataSet can and does behave much like a database, it is
important to remember that DataSet objects do not interact directly with databases, or other
source data. This allows the developer to work with a programming model that is always
consistent, regardless of where the source data resides. Data coming from a database, an XML
file, from code, or user input can all be placed into DataSet objects. Then, as changes are made
to the DataSet they can be tracked and verified before updating the source data. The
GetChanges method of the DataSet object actually creates a second DatSet that contains only
the changes to the data. This DataSet is then used by a DataAdapter (or other objects) to update
the original data source.
The DataSet has many XML characteristics, including the ability to produce and consume XML
data and XML schemas. XML schemas can be used to describe schemas interchanged via
WebServices. In fact, a DataSet with a schema can actually be compiled for type safety and
statement completion.
DataAdapters (OLEDB/SQL)
The DataAdapter object works as a bridge between the DataSet and the source data. Using the
provider-specific SqlDataAdapter (along with its associated SqlCommand and
30
SqlConnection) can increase overall performance when working with a Microsoft SQL Server
databases. For other OLE DB-supported databases, you would use the OleDbDataAdapter
object and its associated OleDbCommand and OleDbConnection objects.
The DataAdapter object uses commands to update the data source after changes have been
made to the DataSet. Using the Fill method of the DataAdapter calls the SELECT command;
using the Update method calls the INSERT, UPDATE or DELETE command for each changed
row. You can explicitly set these commands in order to control the statements used at runtime to
resolve changes, including the use of stored procedures. For ad-hoc scenarios, a
CommandBuilder object can generate these at run-time based upon a select statement.
However, this run-time generation requires an extra round-trip to the server in order to gather
required metadata, so explicitly providing the INSERT, UPDATE, and DELETE commands at
design time will result in better run-time performance.
1. ADO.NET is the next evolution of ADO for the .Net Framework.

2. ADO.NET was created with n-Tier, statelessness and XML in the forefront. Two new
objects, the DataSet and DataAdapter, are provided for these scenarios.
3. ADO.NET can be used to get data from a stream, or to store data in a cache for
updates.
4. There is a lot more information about ADO.NET in the documentation.
5. Remember, you can execute a command directly against the database in order to do
inserts, updates, and deletes. You don't need to first put data into a DataSet in order to
insert, update, or delete it.
6. Also, you can use a DataSet to bind to the data, move through the data, and navigate
data relationships
ASP.Net
31
Server Application Development
Server-side applications in the managed world are implemented through runtime hosts.
Unmanaged applications host the common language runtime, which allows your custom
managed code to control the behavior of the server. This model provides you with all the features
of the common language runtime and class library while gaining the performance and scalability
of the host server.
The following illustration shows a basic network schema with managed code running in different
server environments. Servers such as IIS and SQL Server can perform standard operations while
your application logic executes through the managed code.
Server-side managed code
ASP.NET is the hosting environment that enables developers to use the .NET Framework to
target Web-based applications. However, ASP.NET is more than just a runtime host; it is a
complete architecture for developing Web sites and Internet-distributed objects using managed
code. Both Web Forms and XML Web services use IIS and ASP.NET as the publishing
mechanism for applications, and both have a collection of supporting classes in the .NET
Framework.
XML Web services, an important evolution in Web-based technology, are distributed, server-side
application components similar to common Web sites. However, unlike Web-based applications,
XML Web services components have no UI and are not targeted for browsers such as Internet
Explorer and Netscape Navigator. Instead, XML Web services consist of reusable software
components designed to be consumed by other applications, such as traditional client
applications, Web-based applications, or even other XML Web services. As a result, XML Web
services technology is rapidly moving application development and deployment into the highly
distributed environment of the Internet.
If you have used earlier versions of ASP technology, you will immediately notice the
improvements that ASP.NET and Web Forms offers. For example, you can develop Web Forms
pages in any language that supports the .NET Framework. In addition, your code no longer needs
32
to share the same file with your HTTP text (although it can continue to do so if you prefer). Web
Forms pages execute in native machine language because, like any other managed application,
they take full advantage of the runtime. In contrast, unmanaged ASP pages are always scripted
and interpreted. ASP.NET pages are faster, more functional, and easier to develop than
unmanaged ASP pages because they interact with the runtime like any managed application.
The .NET Framework also provides a collection of classes and tools to aid in development and
consumption of XML Web services applications. XML Web services are built on standards such
as SOAP (a remote procedure-call protocol), XML (an extensible data format), and WSDL ( the
Web Services Description Language). The .NET Framework is built on these standards to
promote interoperability with non-Microsoft solutions.
For example, the Web Services Description Language tool included with the .NET Framework
SDK can query an XML Web service published on the Web, parse its WSDL description, and
produce C# or Visual Basic source code that your application can use to become a client of the
XML Web service. The source code can create classes derived from classes in the class library
that handle all the underlying communication using SOAP and XML parsing. Although you can
use the class library to consume XML Web services directly, the Web Services Description
Language tool and the other tools contained in the SDK facilitate your development efforts with
the .NET Framework.
If you develop and publish your own XML Web service, the .NET Framework provides a set of
classes that conform to all the underlying communication standards, such as SOAP, WSDL, and
XML. Using those classes enables you to focus on the logic of your service, without concerning
yourself with the communications infrastructure required by distributed software development.
Finally, like Web Forms pages in the managed environment, your XML Web service will run
with the speed of native machine language using the scalable communication of IIS.
Active Server Pages.NET
33
ASP.NET is a programming framework built on the common language runtime that can
be used on a server to build powerful Web applications. ASP.NET offers several important
advantages over previous Web development models:
Enhanced Performance. ASP.NET is compiled common language runtime code

running on the server. Unlike its interpreted predecessors, ASP.NET can take advantage of early
binding, just-in-time compilation, native optimization, and caching services right out of the box.
This amounts to dramatically better performance before you ever write a line of code.
World-Class Tool Support. The ASP.NET framework is complemented by a rich

toolbox and designer in the Visual Studio integrated development environment. WYSIWYG
editing, drag-and-drop server controls, and automatic deployment are just a few of the features
this powerful tool provides.
Power and Flexibility. Because ASP.NET is based on the common language

runtime, the power and flexibility of that entire platform is available to Web application
developers. The .NET Framework class library, Messaging, and Data Access solutions are all
seamlessly accessible from the Web. ASP.NET is also language-independent, so you can choose
the language that best applies to your application or partition your application across many
languages. Further, common language runtime interoperability guarantees that your existing
investment in COM-based development is preserved when migrating to ASP.NET.
Simplicity. ASP.NET makes it easy to perform common tasks, from simple form
submission and client authentication to deployment and site configuration. For example, the
ASP.NET page framework allows you to build user interfaces that cleanly separate application
logic from presentation code and to handle events in a simple, Visual Basic - like forms
processing model. Additionally, the common language runtime simplifies development, with
managed code services such as automatic reference counting and garbage collection.
Manageability. ASP.NET employs a text-based, hierarchical configuration

system, which simplifies applying settings to your server environment and Web applications.
Because configuration information is stored as plain text, new settings may be applied without
the aid of local administration tools. This "zero local administration" philosophy extends to
34
deploying ASP.NET Framework applications as well. An ASP.NET Framework application is
deployed to a server simply by copying the necessary files to the server. No server restart is
required, even to deploy or replace running compiled code.
Scalability and Availability. ASP.NET has been designed with scalability in

mind, with features specifically tailored to improve performance in clustered and multiprocessor
environments. Further, processes are closely monitored and managed by the ASP.NET runtime,
so that if one misbehaves (leaks, deadlocks), a new process can be created in its place, which
helps keep your application constantly available to handle requests.
Customizability and Extensibility. ASP.NET delivers a well-factored

architecture that allows developers to "plug-in" their code at the appropriate level. In fact, it is
possible to extend or replace any subcomponent of the ASP.NET runtime with your own custom-
written component. Implementing custom authentication or state services has never been easier.
Security. With built in Windows authentication and per-application configuration,

you can be assured that your applications are secure.
Language Support
The Microsoft .NET Platform currently offers built-in support for three languages: C#,
Visual Basic, and JScript.
What is ASP.NET Web Forms?
The ASP.NET Web Forms page framework is a scalable common language runtime
programming model that can be used on the server to dynamically generate Web pages.
Intended as a logical evolution of ASP (ASP.NET provides syntax compatibility with

existing pages), the ASP.NET Web Forms framework has been specifically designed to address a
number of key deficiencies in the previous model. In particular, it provides:
The ability to create and use reusable UI controls that can encapsulate common
functionality and thus reduce the amount of code that a page developer has to write.
The ability for developers to cleanly structure their page logic in an orderly
fashion (not "spaghetti code").
35
The ability for development tools to provide strong WYSIWYG design support
for pages (existing ASP code is opaque to tools).
ASP.NET Web Forms pages are text files with an .aspx file name extension. They can be
deployed throughout an IIS virtual root directory tree. When a browser client requests .aspx
resources, the ASP.NET runtime parses and compiles the target file into a .NET Framework
class. This class can then be used to dynamically process incoming requests. (Note that the .aspx
file is compiled only the first time it is accessed; the compiled type instance is then reused across
multiple requests).
An ASP.NET page can be created simply by taking an existing HTML file and changing
its file name extension to .aspx (no modification of code is required). For example, the following
sample demonstrates a simple HTML page that collects a user's name and category preference
and then performs a form postback to the originating page when a button is clicked:
ASP.NET provides syntax compatibility with existing ASP pages. This includes support
for <% %> code render blocks that can be intermixed with HTML content within an .aspx file.
These code blocks execute in a top-down manner at page render time.
Code-Behind Web Forms
ASP.NET supports two methods of authoring dynamic pages. The first is the method
shown in the preceding samples, where the page code is physically declared within the
originating .aspx file. An alternative approach--known as the code-behind method--enables the
page code to be more cleanly separated from the HTML content into an entirely separate file.
Introduction to ASP.NET Server Controls
In addition to (or instead of) using <% %> code blocks to program dynamic content,
ASP.NET page developers can use ASP.NET server controls to program Web pages. Server
controls are declared within an .aspx file using custom tags or intrinsic HTML tags that contain a
runat="server" attribute value. Intrinsic HTML tags are handled by one of the controls in the
36
System.Web.UI.HtmlControls namespace. Any tag that doesn't explicitly map to one of the
controls is assigned the type of System.Web.UI.HtmlControls.HtmlGenericControl.
Server controls automatically maintain any client-entered values between round trips to
the server. This control state is not stored on the server (it is instead stored within an <input
type="hidden"> form field that is round-tripped between requests). Note also that no client-side
script is required.
In addition to supporting standard HTML input controls, ASP.NET enables developers to

utilize richer custom controls on their pages. For example, the following sample demonstrates
how the <asp:adrotator> control can be used to dynamically display rotating ads on a page.
1. ASP.NET Web Forms provide an easy and powerful way to build dynamic Web
UI.
2. ASP.NET Web Forms pages can target any browser client (there are no script
library or cookie requirements).
3. ASP.NET Web Forms pages provide syntax compatibility with existing ASP
pages.
4. ASP.NET server controls provide an easy way to encapsulate common

functionality.
5. ASP.NET ships with 45 built-in server controls. Developers can also use controls
built by third parties.
6. ASP.NET server controls can automatically project both uplevel and downlevel
HTML.
7. ASP.NET templates provide an easy way to customize the look and feel of list
server controls.
8. ASP.NET validation controls provide an easy way to do declarative client or

server data validation.
37
SQL SERVER
DATABASE
A database management, or DBMS, gives the user access to their data and helps them
transform the data into information. Such database management systems include dBase, paradox,
IMS, SQL Server and SQL Server. These systems allow users to create, update and extract
information from their database.
A database is a structured collection of data. Data refers to the characteristics of people,

things and events. SQL Server stores each data item in its own fields. In SQL Server, the fields
relating to a particular person, thing or event are bundled together to form a single complete unit
of data, called a record (it can also be referred to as raw or an occurrence). Each record is made
up of a number of fields. No two fields in a record can have the same field name.
During an SQL Server Database design project, the analysis of your business needs
identifies all the fields or attributes of interest. If your business needs change over time, you
define any additional fields or change the definition of existing fields.
SQL Server Tables
SQL Server stores records relating to each other in a table. Different tables are created
for the various groups of information. Related tables are grouped together to form a database.
Primary Key
Every table in SQL Server has a field or a combination of fields that uniquely identifies
each record in the table. The Unique identifier is called the Primary Key, or simply the Key. The
primary key provides the means to distinguish one record from all other in a table. It allows the
user and the database system to identify, locate and refer to one particular record in the database.
Relational Database
Sometimes all the information of interest to a business operation can be stored in one
table. SQL Server makes it very easy to link the data in multiple tables. Matching an employee
38
to the department in which they work is one example. This is what makes SQL Server a
relational database management system, or RDBMS. It stores data in two or more tables and
enables you to define relationships between the table and enables you to define relationships
between the tables.
Foreign Key
When a field is one table matches the primary key of another field is referred to as a
foreign key. A foreign key is a field or a group of fields in one table whose values match those of
the primary key of another table.
Referentialntegrity
Not only does SQL Server allow you to link multiple tables, it also maintains
consistency between them. Ensuring that the data among related tables is correctly matched is
referred to as maintaining referential integrity.
Data Abstraction
A major purpose of a database system is to provide users with an abstract view of the
data. This system hides certain details of how the data is stored and maintained. Data abstraction
is divided into three levels.
Physical level: This is the lowest level of abstraction at which one describes how the data are
actually stored.
Conceptual Level: At this level of database abstraction all the attributed and what data are
actually stored is described and entries and relationship among them.
View level: This is the highest level of abstraction at which one describes only part of the
database.
Advantages of RDBMS
Redundancy can be avoided

Inconsistency can be eliminated
Data can be Shared
39
Standards can be enforced
Security restrictions ca be applied
Integrity can be maintained
Conflicting requirements can be balanced
Data independence can be achieved.
Disadvantages of DBMS
A significant disadvantage of the DBMS system is cost. In addition to the cost of

purchasing of developing the software, the hardware has to be upgraded to allow for the
extensive programs and the workspace required for their execution and storage. While
centralization reduces duplication, the lack of duplication requires that the database be
adequately backed up so that in case of failure the data can be recovered.
FEATURES OF SQL SERVER (RDBMS)
SQL SERVER is one of the leading database management systems (DBMS) because it is
the only Database that meets the uncompromising requirements of todays most demanding
information systems. From complex decision support systems (DSS) to the most rigorous online
transaction processing (OLTP) application, even application that require simultaneous DSS and
OLTP access to the same critical data, SQL Server leads the industry in both performance and
capability.
SQL SERVER is a truly portable, distributed, and open DBMS that delivers unmatched
performance, continuous operation and support for every database.
SQL SERVER RDBMS is high performance fault tolerant DBMS which is specially designed for
online transactions processing and for handling large database application.
SQL SERVER with transactions processing option offers two features which contribute to very
high level of transaction processing throughput, which are
The row level lock manager

Enterprise wide Data Sharing
40
The unrivaled portability and connectivity of the SQL SERVER DBMS enables all the
systems in the organization to be linked into a singular, integrated computing resource.
Portability
SQL SERVER is fully portable to more than 80 distinct hardware and operating systems
platforms, including UNIX, MSDOS, OS/2, Macintosh and dozens of proprietary platforms.
This portability gives complete freedom to choose the database sever platform that meets the
system requirements.
Open Systems
SQL SERVER offers a leading implementation of industry standard SQL. SQL Servers
open architecture integrates SQL SERVER and non SQL SERVER DBMS with industries most
comprehensive collection of tools, application, and third party software products SQL Servers
Open architecture provides transparent access to data from other relational database and even
non-relational database.
Distributed Data Sharing
SQL Servers networking and distributed database capabilities to access data stored on
remote server with the same ease as if the information was stored on a single local computer. A
single SQL statement can access data at multiple sites. You can store data where system
requirements such as performance, security or availability dictate.
Unmatched Performance
The most advanced architecture in the industry allows the SQL SERVER DBMS to
deliver unmatched performance.
Sophisticated Concurrency Control
Real World applications demand access to critical data.With most database Systems
application becomes contention bound which performance is limited not by the CPU power or
by disk I/O, but user waiting on one another for data access. SQL Server employs full,
41
unrestricted row-level locking and contention free queries to minimize and in many cases
entirely eliminates contention wait times.
No I/O Bottlenecks
SQL Servers fast commit groups commit and deferred write technologies dramatically
reduce disk I/O bottlenecks. While some database write whole data block to disk at commit time,
SQL Server commits transactions with at most sequential log file on disk at commit time, On
high throughput systems, one sequential writes typically group commit multiple transactions.
Data read by the transaction remains as shared memory so that other transactions may access that
data without reading it again from disk. Since fast commits write all data necessary to the
recovery to the log file, modified blocks are written back to the database independently of the
transaction commit, when written from memory to disk.
5.0 DESIGN ANALYSIS AND DATA DICTIONARY

UML DIAGRAMS
Unified Modeling Language (UML) is a standard language for specifying, visualizing,

constructing, and documenting the artifacts of software systems, as well as for business modeling
and other non-software systems. The UML represents a collection of best engineering practices
that have proven successful in the modeling of large and complex systems. The UML is a very
important part of developing objects oriented software and the software development process.
The UML uses mostly graphical notations to express the design of software projects. Using the
UML helps project teams communicate, explore potential designs, and validate the architectural
design of the software.
Use Case Diagram
Displays the relationship among actors and use cases. A use case is a set of scenarios that
describing an interaction between a user and a system. A use case diagram displays the
relationship among actors and use cases. The two main components of a use case diagram are
use cases and actors.
42
Class Diagram: Class diagrams used to describe the structure of the system. Classes are
abstractions that specify the common structure and behavior of a set of objects. Objects are
instances of classes that are created , modified, and destroyed during the execution of the system.
Sequence Diagram: Sequence diagrams are used to formalize the behavior of the system and to
visualize the communication among objects. They are useful for identifying additional objects
that participate in the use cases.
State chart Diagram: State chart diagrams describe the behavior of an individual object as a
number of states and transitions between the states. A state represents a particular set of value for
an object.
USECASE DIAGRAM
43
SEQUENCE DIAGRAM
44
Login Admin Enquiry
Transactions
username,password
New Enquiry
invalid
Modify Enquiry
Delete Enquiry
Reregistration
Scope Enhancement
Upgradation
45
Login Admin Quotation
Transactions
username,password
Invalid
Enter EnquiryNo
Invalid
New Quotation
Modify Quotation
Delete Quotation
Approve
STATE CHART DIAGRAM
46
SOA For Middleware
Enquiry ISO Agency
Receive Enquiry Request

<<test Begin At>>
Company User
[]
Insert Enquiry Info
Approach ISO Agency
Registration
No Yes
Insert to
Display Error Message
Database
Enter Enquiry Details
Update Enquiry
Notify User
Info
47
SOA For Middleware
ENQUIRY ISO Agency

<<test Begin At>>
Company User
[]
SEARCH ENQUIRY NO
Approach ISO Agency
No Yes
MODIFY
SEARCH IN
Database
Enter Enquiry NO
Update Enquiry
Notify User
Info
48
SOA For Middleware
ENQUIRY ISO Agency

<<test Begin At>>
Company User
[]
GET ALL ENQUIRIES
Approach ISO Agency
No Yes
BROWSE
SEARCH IN
Database
DISPLAY
REGISTRATION
DISAPLY
ENQUIRY Notify User
DETAILS
49
SOA For Middleware
QUOTATION ISO Agency
Receive QUOTATION Request

<<test Begin At>>
Company User
[]
SEARCH Enquiry Info
Approach ISO Agency
CREATE
No Yes
Insert Quotation to
Database
Enter Enquiry NO
Quotation inserted
Notify User
50
SOA For Middleware

<<test Begin At>>
Company User
[]
SEARCH QUOTATION NO
Approach ISO Agency
No Yes
MODIFY
SEARCH IN
Database
Enter QUOTATION NO
Update QUOTATION
Notify User
Info
51
SOA For Middleware

<<test Begin At>>
Company User
[]
GET ALL QUOTATION
Approach ISO Agency
No Yes
BROWSE
SEARCH IN
Database
DISPLAY
QUOTATION
DISAPLY
QUOTATIONY Notify User
DETAILS
52
SOA For Middleware
AUDITORS ISO Agency
Receive AUDITORS Request

<<test Begin At>>
Company User
[]
SEARCH AUDITOR TYPE
Approach ISO Agency
CREATE
No Yes
Insert AUDITORS
Database
Enter AUDITOR TYPE
AUDITORS
Notify User
DETAILS inserted
53
SOA For Middleware
AUDITORS ISO Agency

<<test Begin At>>
Company User
[]
SEARCH AUDITOR NO
Approach ISO Agency
No Yes
MODIFY
SEARCH IN
Database
Enter AUDITOR NO
Update AUDITORS
Notify User
Info
54
SOA For Middleware
AUDITORS ISO Agency

<<test Begin At>>
Company User
[]
GET ALL AUDITORS
Approach ISO Agency
No Yes
BROWSE
SEARCH IN
Database
DISPLAY
AUDITORS
DISAPLY
AUDITOR Notify User
DETAILS
55
SOA For Middleware
AUDITING ISO Agency
Receive AUDITNG Request

<<test Begin At>>
Company User
[]
SEARCH INPUT DATA
Approach ISO Agency
No Yes
PREASSESSMENT/D
OCUMENTREVIEW
CONFORMANCE/ SEARCH IN
Database
SERVIVELENCE
ENTER QUOTATION NO
/ENQUIRY NO/ COMP NAME
DISAPLY
AUDITING Notify User
DETAILS
56
SOA For Middleware
REPORTS ISO Agency
Receive TYPE OF REPORT Request

<<test Begin At>>
Company User
[]
SEARCH INPUT DATA
Approach ISO Agency
No Yes
ENQUIRY/QUOTATIO
N/AUDITOR/AUDITS
SEARCH IN
Database
ENTER QUOTATION NO
/ENQUIRY NO/ COMP NAME
DISAPLY
REPORT Notify User
DETAILS
57
DATA DICTIONARY
After carefully understanding the requirements of the client the the entire data storage
requirements are divided into tables. The below tables are normalized to avoid any anomalies
during the course of data entry.
TABLE DESCRIPTIONS:
1. TB_ACCRBODY_TYPE:
Sno ColumnName DataType Length AllowNulls Constraints
1 ACCRBODY_TYPE_ID NUMERIC 9 P
2 ACCRBODY_TYPE Varchar 50
3 ACCRBODY_TYPE_DESC Varchar 50
2.TB_ADDRESS_AUDITOR:
1 ADDRESSID NUMERIC 9 P
2 AUDITORID NUMERIC 5
3 ADDRESS1 Varchar 30
5 CITY Varchar 20
6 STATE Varchar 20
7 COUNTRY Varchar 20
8 EMAIL Varchar 50
9 FAX Varchar 20
10 MOBILE Varchar 20
11 IS_ACTIVE Char 1
58
3.TB_ADDRESS_COMPANY:
1 ADDRESSID NUMERIC 9 P
2 COMPANY_ID NUMERIC 5
5 CITY Varchar 20
6 STATE Varchar 20
7 COUNTRY Varchar 20
8 EMAIL Varchar 50
9 FAX Varchar 20
10 MOBILE Varchar 20
11 IS_ACTIVE Char 1
4.TB_AUDIT_TYPE:
1 AUDIT_TYPE_ID NUMERIC 5 P
2 AUDIT_TYPE Varchar 50
3 AUDIT_TYPE_DESC Varchar 20
5.TB_AUDITFREQ_TYPE:
59
1 AUDITFREQ_TYPE_ID NUMERIC 9 P
2 AUDITFREQ_TYPE Varchar 50
3 AUDITFREQ_TYPE_DESC Varchar 50
6.TB_AUDITOR:
1 AUDITORID NUMERIC 5 P
2 AUDITOR_TYPE_ID Numeric 5
3 AUDITORNAME Varchar 30
4 QUALIFICATION Varchar 100
5 MGRLEXP10YRS Varchar 1000
6 ICRAREGDTLS Varchar 1000
7 LACERTNO Varchar 20
8 LACOURSEDT DateTime 8
9 IS_ACTIVE Char 1
7.TB_AUDITOR_SCODE:
1 AUDITORID NUMERIC 5
2 SICCODE Varchar 20
8.TB_AUDITOR_TYPE:
1 AUDITOR_TYPE_ID NUMERIC 5 P
2 AUDITOR_TYPE Varchar 15
60
3 AUDITOR_TYPE_DESC Varchar 50
9.TB_CERTIFICATE_INFO:
1 CERTIFICATE_NO Varchar 50 P
2 REG_NO Numeric 9
3 CERTDATE DateTime 8
4 CERTVALIDITY DateTime 8
5 IS_WITHDRAWN Char 1
6 IS_PROBATION Char 1
10.TB_CERTIFICATE_TYPE:
1 CERT_TYPE_ID Numeric 9 P
2 CERT_TYPE Varchar 50
3 CERT_TYPE_DESC Varchar 50
11.TB_COMM_TYPE:
1 COMMTYPEID Numeric 5 P
2 COMMTYPE Varchar 50
3 COMMDESC Varchar 50
12.TB_COMMUNICATION:
61
1 COMMUNICATIONID Numeric 9 P
2 AUDITNO Numeric 9
3 COMMTYPEID Numeric 5
4 COMMTOWHOME Varchar 10
5 COMMTOID Numeric 5
6 MODEOFCOMM Varchar 50
7 MESSAGE Varchar 1000
8 REMARKS Vatchar 1000
13.TB_COMP_SHIFT:
1 COMPANY_ID Numeric 9
2 SHIFTID Numeric 5
3 SHIFTTIME Varchar 20
4 TOTALEMP Numeric 5
14.TB_COMPANY_DETAILS:
1 COMPANY_ID Numeric 9 P
2 COMPANYNAME Varchar 100
3 ENQUIRY_NO Varchar 30
4 MAILINGADDRESS1 Varchar 100
5 MAILINGADDRESS2 Varchar 100
6 CONTACTPERSON Varchar 50
62
7 TITLE Varchar 50
8 SICCODE Varchar 100
9 IAFCODE Varchar 30
10 INDUSTRYTYPE Varchar 50
11 AUDITLOCATION Varchar 30
12 COMPANYLOG_ID Numeric 9
15.TB_ENQUIRY:
1 ENQUIRY_NO Varchar 30 P
2 REGISTRATIONSCOPE Varchar 1000
3 AUDITFREQ_TYPE_ID Numeric 9
4 HEARABTAQA Varchar 100
5 CONSENGDEARLIER Varchar 100
6 COMPLETEDBY Varchar 50
7 DESIGNATION Varchar 50
8 ENQUIRYDT DateTime 8
9 ENQUIRYTYPE Varchar 20
10 CERT_TYPE_ID Numeric 9
11 ACCRBODY_TYPE_ID Numeric 9
12 CONF_MANDAYS Varchar 30
13 SURVE_MANDAYS Varchar 30
14 Flag Bit 1
16.TB_FEEDBACK:
63
1 FEEDBACKID Numeric 5 P
2 AUDITNO Numeric 9
3 FEEDBACK_TYPE_ID Numeric 5
4 FEEDBACKBY Numeric 5
5 FEEDBACKON Numeric 5
6 FEEDBACKDESC Varchar 1000
7 REMARKS Varchar 1000
8 MODEOFFEEDBACK Varchar 50
9 AQARESPONSE Varchar 1000
17.TB_FEEDBACK_TYPE:
1 FEEDBACK_TYPE_ID Numeric 9 P
2 FEEDBACKTYPE Varchar 50
3 FEEDBACKDESC Varchar 50
18.TB_FEES:
1 AUDITNO Numeric 9
2 FEESRS Numeric 9
3 FEESDLR Numeric 9
4 INVNO Varchar 10
5 INVDT DateTime 8
64
6 FEEPAIDRS Numeric 9
7 FEEPAIDDLR Numeric 9
8 FEEPAIDDT DateTime 8
19.TB_QUOT_LOG_FEES:
1 QUOTATIONNO Varchar 30
2 AUDIT_TYPE_ID Numeric 5
3 AUDITFEESRS Numeric 9
4 AUDITFEESDLR Numeric 9
20.TB_QUOTATION:
1 QUOTATIONNO Varchar 30 P
2 ENQUIRY_NO Varchar 30
3 QUOTATIONDT DateTime 8
4 IS_APPROVED Char 1
5 APPROVEDDATE DateTime 8
21.TB_REG_AUDIT:
1 AUDITNO Numeric 9 P
2 AUDIT_TYPE_ID Numeric 5
3 REG_NO Numeric 9
4 FILE_NO Varchar 30
65
5 REQUESTDT DateTime 8
6 SCHEDULEDDT DateTime 8
7 CONDUCTEDDT DateTime 8
8 REPORTDT DateTime 8
9 RCVDFROMLA DateTime 8
10 RCVDATAQAINDIABY Varchar 50
11 RCVDATAQAINDIADT DateTime 8
12 SENTTOAQAUSA DateTime 8
13 COMMENTSFROMAQAUSA Varchar 2000
14 RCVDFROMAQAUSADT DateTime 8
15 FOLLOW_TO Numeric 9
16 RECOLETTDT DateTime 8
22.TB_REG_AUDITORS:
1 AUDITNO Numeric 9
2 AUDITORID Numeric 5
3 MANDAYS Numeric 5
4 IS_LA Varchar 2
23.TB_REGISTRATION:
1 REG_NO Numeric 9 P
2 FILE_NO Varchar 30
3 FILEDATE DateTime 8
66
4 FILESTORAGE Varchar 30
5 QUOTATIONNO Varchar 30
6 COMPANY_ID Numeric 9
7 APPLICATION_FEEPAID Char 1
24.TB_USER:
1 USERID Numeric 9
2 USERTYPE Varchar 20
3 USERNAME Varchar 20
4 PASSWORD Varchar 20
6.0 CODING
Login Page:
using System;
using System.Collections;
using System.ComponentModel;
67
using System.Data;
using System.Drawing;
using System.Web;
using System.Web.SessionState;
using System.Web.UI;
using System.Web.UI.WebControls;
using System.Web.UI.HtmlControls;
namespace ESEC
{
/// <summary>
/// Summary description for Login.
/// </summary>
public partial class Login : System.Web.UI.Page
{
protected localhost.ESECWebService ESECws=new localhost.ESECWebService();
public Login()
{
Page.Init += new System.EventHandler(Page_Init);
}
protected void Page_Load(object sender, System.EventArgs e)

{
protected void Page_Init(object sender, EventArgs e)

{
//
// CODEGEN: This call is required by the ASP.NET Web Form Designer.
//
InitializeComponent();
}
#region Web Form Designer generated code

/// <summary>
/// Required method for Designer support - do not modify
/// the contents of this method with the code editor.
/// </summary>
private void InitializeComponent()
{
}
#endregion
68
protected void btnlogin_click(object sender,ImageClickEventArgs args)
{
string strUsername=username.Text;
string strPassword=password.Text;
string len=strPassword.Length.ToString();
username.Text=len;
localhost.LoginInfo loginData;
if (Page.IsValid)
{
try
{
loginData =
ESECws.LoginUser(strUsername,strPassword);
if
(loginData.LoginResult==localhost.LoginStatus.LoginSuccessful)
{
Session["USERNAME"]=strUsername;
try
{
DataSet userDetails =
ESECws.GetUserID(strUsername);
Session["USERDETAILS"]=userDetails;
Response.Redirect("~/HomePage.aspx", false);
}
catch(Exception e){
LogFileClass.writeToLogFile(e,"Login.aspc.cs","btnlogin_click INNER TRY");

}
}
else if
(loginData.LoginResult==localhost.LoginStatus.LoginInvalidPassword)
{
invalidlbl.Text="Invalid UserName or Password" ;
username.Text="";
password.Text="";
}
else
{
invalidlbl.Text="Invalid User Name";
}
}
catch (Exception ex)
69
{
LogFileClass.writeToLogFile(ex,"Login.aspc.cs","btnlogin_click OUTER TRY");

}
}
}
}
}
Admin Page:
using System;
using System.Collections;
using System.ComponentModel;
using System.Data;
using System.Drawing;
using System.Web;
using System.Web.SessionState;
using System.Web.UI;
using System.Web.UI.WebControls;
using System.Web.UI.HtmlControls;
namespace ESEC
{
/// <summary>
/// Summary description for AdminUser.
/// </summary>
public partial class AdminUser : System.Web.UI.Page
{
protected int _totalPages = 1;
protected int _currentPageNumber = 1;
protected localhost.ESECWebService ESECws=new

localhost.ESECWebService();
protected System.Web.UI.WebControls.PlaceHolder Group1;
public Hashtable UserType;
protected void Page_Load(object sender, System.EventArgs e)

{
if (!Page.IsPostBack )
{
BindData();
UserType=new Hashtable();
70
UserType["Admin"]=1;
UserType["Manager"]=2;
UserType["Guest"]=3;
}
}
protected void NavigationLink_Click ( Object sender, EventArgs e )

{
_currentPageNumber = Int32.Parse( ddl.SelectedItem.Value);
try
{
_currentPageNumber = Int32.Parse(ddl.SelectedItem.Value);
}
catch
{
_currentPageNumber=1;
}
BindData();
}
public int Getusertype(string strUsertype)

{
if (UserType[strUsertype] != null)
return (int)UserType[strUsertype];
else
return 0;
}
private void BindData()

{
MyDataGrid.Visible=true;
ddl.Visible=true;
page1.Visible=true;
of1.Visible=true;
TotalPages.Visible=true;
object[] records=ESECws.getAllUsers(_currentPageNumber);
localhost.DataRecords myAL=(localhost.DataRecords) records[0];
DataSet myData = (DataSet)myAL.ds;
MyDataGrid.DataSource=myData.Tables["AllUsers"].DefaultView;
MyDataGrid.DataBind();
Int32 _totalRecords = myAL.TotalRecords;

Int32 recsperpage=myAL.RecordsPerPage;
_totalPages = _totalRecords / recsperpage;
71
if(_totalRecords>recsperpage)
{
_totalPages = _totalRecords / recsperpage;
if((_totalRecords % recsperpage)==0)
{
TotalPages.Text = ( (double) ( _totalPages ) ).ToString();
}
else
{
if(_totalRecords>recsperpage)
{
TotalPages.Text = ((double)(_totalPages) + 1).ToString();
}
_totalPages = Int32.Parse ( TotalPages.Text );
}
}
else
{
_totalPages=1;
}
if(_totalPages==0)
{
_totalPages=1;
}
TotalPages.Text=_totalPages.ToString();
ddl.Items.Clear();
for(int i=1;i<=_totalPages;i++)
{
System.Web.UI.WebControls.ListItem list1= new
System.Web.UI.WebControls.ListItem(i.ToString(),i.ToString());
if(_currentPageNumber==i)
{
list1.Selected=true;
}
ddl.Items.Add(list1);
}
if(_totalRecords<=0)
{
MyDataGrid.Visible=false;
ddl.Visible=false;
page1.Visible=false;
of1.Visible=false;
TotalPages.Visible=false;
Message.Text ="No DataRecords Found Matching Your
Criteria. ";
72
Message.Style["color"] = "red";
}
}
public void MyDataGrid_Modify(Object sender, DataGridCommandEventArgs e)
{
object Username=MyDataGrid.DataKeys[(int)e.Item.ItemIndex];
DataSet ds=ESECws.getSelectedUser(Username.ToString());
DataRowCollection collection =
(DataRowCollection)ds.Tables["SelectedUser"].Rows;
DataRow datarow=(DataRow)collection[0];
ArrayList arraylist = new ArrayList();

arraylist.Add(new
AssignData(Int32.Parse(datarow[0].ToString()),datarow[1].ToString(),datarow[2].ToString(),data
row[3].ToString()));
DataGrid1.DataSource = arraylist;
DataGrid1.DataBind();
DataGrid1.Visible=true;
Message.Style["color"] = "black";
Message.Text = "Modify The Values ";
public void AddNewUser(object sender, System.Web.UI.ImageClickEventArgs e)
ArrayList arraylist = new ArrayList();

arraylist.Add(new AssignData(1,"",null,""));
DataGrid1.DataSource = arraylist;
Message.Style["color"] = "black";
Message.Text = "Enter The Values ";
}
public class AssignData
73
{
private int strUserId;
private string strUserType;
private string strUserName;
private string strPassword;
public AssignData()
{
}
public AssignData(int strUserId,string strUserType,string
strUserName,string strPassword)
{
this.strUserId=strUserId;
this.strUserType=strUserType;
this.strUserName=strUserName;
this.strPassword=strPassword;
}
public int userid

{
get
{
return strUserId;
}
}
public string usertype
{
get
{
return strUserType;
}
}
public string Getusername
{
get
{
return strUserName;
}
}
public string Getpassword
{
get
{
return strPassword;
}
}
74
}
public void MyDataGrid_Delete(object sender, DataGridCommandEventArgs e)
{
object strUsername=MyDataGrid.DataKeys[(int)e.Item.ItemIndex];
string i = ESECws.deleteUser(strUsername.ToString());
if(i=="deleted")
{
Message.Text = "Record Deleted ";
}
else
{
Message.Text = "ERROR: Could not delete record";
}
BindData();
}
public void MyDataGrid_ItemCreated(object Sender,DataGridItemEventArgs e)
{
switch(e.Item.ItemType)
{
case ListItemType.Item:
ImageButton myDeleteButton;
myDeleteButton
=(System.Web.UI.WebControls.ImageButton) e.Item.FindControl("btnDelete");
myDeleteButton.Attributes.Add("onclick","return
confirm('Are You Sure You Want To Delete This Audit Type ?');");
break;
case ListItemType.AlternatingItem:
myDeleteButton
=(System.Web.UI.WebControls.ImageButton) e.Item.FindControl("btnDelete");
myDeleteButton.Attributes.Add("onclick","return
confirm('Are You Sure You Want To Delete This Audit Type ?');");
break;
}
}
protected void DataGrid1_OnUpdateCommand(object sender,
DataGridCommandEventArgs e)
{
string
strUserId=(((DropDownList)e.Item.FindControl("usertype")).SelectedItem.Value).ToString();
string
strUserType=(((DropDownList)e.Item.FindControl("usertype")).SelectedItem.Text).ToString();
string
strUserName=(((TextBox)e.Item.FindControl("username")).Text).ToString();
string
strPassword=(((TextBox)e.Item.FindControl("passwords")).Text).ToString();
75
if ((strUserName!="")&& (strPassword!=""))
{
if(Message.Text.StartsWith("Modify"))
{
int
i=ESECws.modifyUser(strUserId,strUserType,strUserName,strPassword);
if(i==1)
{
DataGrid1.Visible=false;
Message.Text = "Record Modified ";
}
else
{
Message.Text = "ERROR: Record Not Modified";
}
}
else
{
string
status=ESECws.insertUser(strUserId,strUserType,strUserName,strPassword);
if(status.Equals("Inserted"))
{
Message.Text = "Record Inserted
Successfully. ";
}
else
{
Message.Text = "ERROR: Record Not Inserted";
}
}
BindData();
}
else
{
Message.Text="User Name And Password Cannot be null";
}
}
protected void DataGrid1_OnCancelCommand(object sender,
DataGridCommandEventArgs e)
{
76
Message.Text = "";
#region Web Form Designer generated code

override protected void OnInit(EventArgs e)
{
//
// CODEGEN: This call is required by the ASP.NET Web Form Designer.
//
InitializeComponent();
base.OnInit(e);
}
/// <summary>
/// Required method for Designer support - do not modify
/// the contents of this method with the code editor.
/// </summary>
private void InitializeComponent()
{
}
#endregion
}
}
7.0 TESTING
SOFTWARE TESTING
77
The important of software testing and its implication with respect to software quality cannot
be overemphasized.
The development of the software system involves a series of production activities where
opportunities for injection of human fallibilitys are enormous. Errors may be to occur at the very
inception of the process where the objectives may be erroneously or imperfectly specified, as
well as [in] later design and development stages. Because of human inability to perform and
communicate with perfection, a software development is accompanied by quality assurance
activity.
Software test is a critical element of software quality assurance and represents the ultimate
review of specification, design and coding.
1. Testing objectives :
Glen Myers [MYE79] states a number of rules that can serve well as testing objectives:
a. Testing is process of executing a program with the intent of finding an error.
b. A good test case is one that has a high probability of finding an as-yet
undiscovered error.
c. A successful test is one that uncovers an as-yet undiscovered error.
Testing cannot show the absence of defects, it can only show that software errors are
present. It is important to keep this statement in mind as testing is being conducted.
2. Testing Principles:
Before applying methods to design effective test cases, software engineer must
understand the basic principles that guide software testing. Davis [DAV95] suggests some of the
testing principles which are as follows:
a. All tests should be traceable to customer requirements.
b b. Tests should be planned long before testing begins.
c. Testing should begin in the small and progress toward testing in the large.
c d. Exhaustive testing is not possible.
e. To be most effective, testing should be conducted by an independent third party.
3. Testability:
78
In ideal circumstances, a software engineer designs a computer program, a system, or a
product with testability in mind. This enables the individuals charged with testing to design
effective test cases more easily. But what is
testability James Bach describes testability in the following manner:
Software testability is simply how easily a computer program can be tested. Since testing
is so profoundly difficult, it pays to know what can be done to streamline it. Sometimes
programmers are willing to do things that will help the testing process, and a checklist of
possible design points, features and so on can be useful in negotiating with them.
Object oriented software testing differs from procedural oriented software. Although this
fundamental objective remains unchanged for object oriented software, the nature of object
oriented programs changes both testing strategy and testing tactics.
TESTING TYPES:
Testing is a process in which we create a series of test cases that are intended to demolish
the software that has built.
The system can be tested in two ways.
White-box Testing:
This is performed knowing the internal workings of a product, tests are
conducted to ensure that all gears mesh, that is, that internal operation performs according to
specification and all internal components have been adequately exercise. This can be done on
close examination of procedural detail. Providing test cases that exercise specific set of
conditions and /or loops tests logical paths through the software.
Using the white-box testing we can derive test cases that
Guarantee that all independent paths within a module have been exercised at least once.
Exercise all logical decisions on their true and false sides.
Execute all loops at their boundaries and within their operational bounds and
Exercise internal data structures to assure their validity.
Black-Box Testing:
Knowing the specified function that a product has been designed to perform,
79
tests can be conducted that demonstrate each function is fully operational, at the same time
searching for errors in each function . It enables us to derive sets of input conditions that will
fully exercise all functional requirements for a program.
It attempts to find errors in the following categories:
1.1.1.1. Incorrect or missing functions.
1.1.1.2. Interface errors.
1.1.1.3. Errors in data structures or external
database access.
1.1.1.4. Performance errors.
1.1.1.5. Initialization and termination errors.
All the functions in the system are tested one after another and the desired tasks are fulfilled.
Input values should lie in the data values size and these must check before processing. All the
boundary values are tested.
System testing strategies have the following generic characteristics:
Testing begins at the module level and works outward toward the integration of the entire
computer-based system.
Different testing techniques are appropriate at different points in time.
The developer of the software and an independent test group conducts testing.
Testing and debugging are different activities, but debugging must be accommodated in a
test strategy.
The different test strategies are:
1. UNIT TESTING: It focuses verification effort on the smallest unit of system design the
module. Using the procedural design description as a guide, important control paths are tested to
uncover error within the boundary of module. In the choice software all the small units are
tested for errors.
2. INTEGRATION TESTING: Integration testing is a systematic technique for construction of

the program structure while conducting test to uncover errors associated with interfacing. The
objective is to take unit tested modules and build a program structure that has been dictated by
80
design. In this system top-down integration is followed, that is modules are integrated by moving
downward through the control hierarchy, beginning with the main control.
3.VALIDATION TESTING: Validation succeeds when system functions in a manner that can
be reasonably expected by the end user. This achieved through a series of black- box that
demonstrate with requirements. There are two tests conducted for the system validation.
ALPHA TEST: A customer conducts it at the developers site. The software is used in a
natural setting with the developer looking over the shoulder of the user and recording errors
and usage problems.
BETA TEST: This test is conducted at one or more users sites by the end user(s) of the
software. Here the developer is generally not present. Therefore, the beta test is a live
application of the software in an environment that cannot be controlled by the developer. The
customer records all problems that are encountered during beta testing and reports these to the
developer at regular intervals.
4.SYSTEM TESTING : System testing is actually a series of different test whose primary
purpose is to fully exercise the computer-based system. Although each test has a different
purpose, all work to verify that all system elements have been properly integrated and perform
allocated functions. During this process recovery testing is done which is a system test that
forces the software to fail in a variety of ways and verifies that recovery is properly performed.
Security testing attempts to verify that protection mechanisms built into systems will in fact
protect it from improper penetration.
8.0 OUTPUT SCREENS
81
After login
After click on details Button
82
New enquiry
83
Enter enquiry details
84
Enquiry browse
85
Enquiry modify
86
After click on modify
Quotation browse
87
Create quotation
88
89
90
91
92
93
94
95
New user
96
97
98
99
User login
100
Change password
101
Help
9.0 SCOPE FOR FUTURE DEVELOPMENT
The application although an open website Provide some security restriction for the
user to register ISO certification before user login. Here we are not provided any registration for
users directly. Administrator will provide username and password after Finish the preassessment.
Here we are not providing direct enquiry we will be send a link to the customers in online. If we
will provide separate registration, it is one more enhancement. Here we are provided reports for
verify the types of company details the current system being small on volume is currently hosted
only in the LAN environment of a company with little modification and general website hosting
requirements it can be made as a public website.
The application can be converted into a Mobile based using ASP.net with which the
deployment of application will be done only on enterprises server and is accessible to all other
departments of the organization. The current application is confined to only one enterprise.
When the agency will issue the certificate, that date we will send to their mobile devices.
102
10.0 CONCLUSION
The project has been appreciated by all the users in the organization.
It is easy to use, since it uses the GUI provided in the user dialog.
User friendly screens are provided.
The usage of software increases the efficiency, decreases the effort.
It has been efficiently employed as a Site management mechanism.
It has been thoroughly tested and implemented.
103
11.0 BIBLIOGRAPHY
SOFTWARE ENGINEERING
By Rogers. Pressman
SQL FOR PROFESSIONALS
By Jain
C#.NET
By Wrox Publications
ASP.Net Professional
By Wrox Publications
104
MSDN 2008
By Microsoft
105

SOA For Middleware

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

SOA For Middleware

Загружено:

Авторское право:

Доступные форматы

1.

RNC Data Com Software Solutions is an IT solution provider for a dynamic

RNC Data Coms range of expertise includes :

Software Development Services

Effectively address the business issues our customers face today.

This approach rests on :

A full service portfolio:

Developers Responsibilities Overview:

The developer is responsible for:

5) Maintaining the system for a period of one year after installation.

2.1 SOFTWARE REQUIREMENTS:

Operating System : Windows NT/ Windows XP with IIS Server.

Language : ASP.NET, C#.

Front End : Microsoft Visual Studio.Net 2008.

Backend : SQL Server 2005

2.2 HARDWARE REQUIREMENTS:

Processor : Intel P-III Processor or later

RAM : 256 MB RAM

3.2 Proposed system

User friendliness is provided in the application with various controls.

It can be accessed over the internet.

. External Outputs, whose destination is outside the organization,.

The outputs should be defined in terms of the following points:

It is not always desirable to print or display data as it is held on a computer. It should be

. Will decimal points need to be inserted

. should leading zeros be suppressed.

The suitability for the device to the particular application.

To produce a cost-effective method of input.

The main input stages can be listed as below:

It is necessary to determine the various types of inputs. Inputs can be categorized as

External inputs, which are prime inputs for the system.

User Interface design:

User Interface systems can be classified as:

User initiated interfaces fall into tow approximate classes:

1. Command driven interfaces: In this type of interface the user inputs

The following computer initiated interfaces were used:

Error Message Design:

Performance is measured in terms of the output provided by the application.

The system should be able to interface with the existing system

The proposed system can be developed using existing technology or not. It

It is an evaluation of development cost weighed against the ultimate

The Organization has in place, the required Hardware for implementing

3.5 Modules of the project

FUNCTIONALITY OF EACH MODULE

When he clicks the option Modify he will be provided with a form

When he clicks the option Modify he will be provided with a form

Certification wise reports

File no wise report

Between date wise report and Available auditors Reports

To provide a consistent object-oriented programming environment whether object code is

To provide a code-execution environment that guarantees safe execution of code,

To provide a code-execution environment that eliminates the performance problems of

Features of the Common Language Runtime

Finally, the runtime can be hosted by high-performance, server-side applications, such as

.NET Framework Class Library

Windows GUI applications (Windows Forms).

XML Web services.

Client Application Development

Client applications are the closest to a traditional style of application in Windows-based

Connections. For connection to and managing transactions against a database.

The DataReader object is somewhat synonymous with a read-only/forward-only cursor over

DataSets and DataAdapters

1. ADO.NET is the next evolution of ADO for the .Net Framework.