DBAO

CONTENTS
Peg. No

1) INTRODUCTION 2-5
 INTRODUCTION TO IQMS
 PURPOSE OF THE PROJECT
 PROBLEM IN EXISTING SYSTEM
 SOLUTION OF THESE PROBLEMS

2) PROJECT ANALYSIS 6-15

 STUDY OF THE SYSTEM
 HARDWARE & SOFTWARE SPECIFICATIONS
 INPUT & OUTPUT
 PROCESS MODELS USED WITH JUSTIFICATION

3) SOFTWARE REQUIRMENT SPECIFICATION 16-24

 FUNCIONAL REQUIREMENTS
 PERFORMANCE REQUIREMENTS

4) SELECTED SOFTWARE 25-45

5) PROJECT DESIGN 46-65

 DATA DICTIONARY
 E-R DIAGRAM
 DATA FLOW DIAGRAMS

6) SCREENS 66-70

7) PROJECT TESTING 71-72

 COMPILING TEST
 EXECUTION TEST
 OUTPUT TEST

9) CONCLUSION 73-74

10) BIBLOGRAPHY 75-76

1
 DBAO

2
 DBAO

INTRODUCITON

IQMS project designed to automate the work process (from client making an
enquiry to maintaining ISO certificates information) in an ISO certificate issuing
agency. This is an Intranet Project developed for the Quality Assessors India Pvt.
Ltd. This organization is involved in auditing Organizations going in for ISO
certifications. The project keeps track of various activities, like the auditors
associated, their affiliations, organizational data, certification information, and
surveillance information. Various reports are generated monthly/yearly wise,
auditor wise, organization wise, surveillance wise, Quotation wise etc.

KAP TECHNOLOGIES

KAP TECHNOLOGIES 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 organization’s current IT assets. Their work with large global
corporations and new products or services and to implement prudent business and
technology strategies in today’s environment.
KAP TECHNOLOGIES’s range of expertise includes:

 Software Development Services

 Engineering Services
 Systems Integration
 Customer Relationship Management
 Product Development
 Electronic Commerce

3
 DBAO

 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.

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 -

4
 DBAO

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. What’s equally important - they share a strong customer orientation that
means they actually start by listening to the customer. They’re 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:

KAP TECHNOLOGIES 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.

5
 DBAO

6
 DBAO

PROJECT ANALYSIS

STUDY OF THE SYSTEM

INTRODUCTION

IQMS is a project designed to automate the work process (from client

making an enquiry to maintaining ISO 9000 certificate information) in a ISO
9000 certificate issuing agency. This is an Intranet Project developed for the
XYZ Quality Assessors India Pvt. Ltd. This organization is involved in
auditing Organizations going in for ISO certifications. The project keeps track
of various activities, like the auditors associated, their affiliations,
organizational data, certification information, and surveillance information.
Various reports are generated monthly/yearly wise, auditor wise, organization
wise, surveillance wise, Quotation wise etc.

The entire project is divided into five main modules. They are as follows

1 Enquiry
2. Quotation
3. Audit info/surveillance
4. Auditors
5. Reports
6. Administrator

7
 DBAO

FUNCTIONALITY OF EACH MODULE

1. ENQUIRY:

Enquiry Module is the initial module in the IQMS where the user is
provided with three possible options. They are Browse, Create and Modify.

1.1Browse:
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.2Create:
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 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.

8
 DBAO

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.

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

9
 DBAO

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 are 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.

10
 DBAO

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:

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.

11
 DBAO

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 them 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.

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

12
 DBAO

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.

13
 DBAO

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.

3.3. CONFORMANCE:
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…

14
 DBAO

4. AUDITORS:
Auditors Module is the fourth module in the IQMS 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,
and 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, Lacert and the complete
personal information of that particular Auditor. Once he fills the details 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 / Is Active and two buttons
Search and Cancel. Once the users 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.

15
 DBAO

16
 DBAO

SOFTWARE REQUIREMENT SPECIFICATION

REQUIREMENT SPECIFICATION:

The software, ISO Visualizer is designed for management and issuance of

certificates for Industrial Standardization and Quality.

INTRODUCTION

Purpose: 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.

17
 DBAO

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.

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
 User’s 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

18
 DBAO

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.
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 deciding about the
output media are:
o The suitability for the device to the particular application.
o The need for a hard copy.
o The response time required.
o The location of the users
o The software and hardware available.
o The cost.

19
 DBAO

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 objectives during
the input desing 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.

INPUT STAGES:

The main input stages can be listed as below:

 Data recording
 Data transcription
 Data conversion
 Data verification
 Data control

20
 DBAO

 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 department’s 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
 Accuracy
 Verification methods
 Rejection rates

21
 DBAO

 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 up to 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.

22
 DBAO

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 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 pop up menus.

USERINTERFACE DESIGN

It is essential to consult the system users and discuss their needs while
designing the user interface:

USER INTERFACE SYSTEMS CAN BE BROADLY CLASIFIED

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

23
 DBAO

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.
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.

24
 DBAO

25
 DBAO

SELECTED SOFTWARE

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

26
 DBAO

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 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

27
 DBAO

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.

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

28
 DBAO

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.

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.

29
 DBAO

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

30
 DBAO

example, you can use the .NET Framework to develop the following types of
applications and services:

 Console applications.

 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

31
 DBAO

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.

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

32
 DBAO

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, Data Reader, and Data Adapter.

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
record set 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 Data Adapter 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

33
 DBAO

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 Data
Adapter, 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, Data Reader and Data Adapter. 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.

The following sections will introduce you to some objects that have evolved,
and some that are new. These objects are:

34
 DBAO

 Connections. For connection to and managing transactions against a

database.

 Commands. For issuing SQL commands against a database.

 Data Readers. 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.

 Data Adapters. 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 represented by provider-
specific classes such as SQLConnection. Commands travel over connections and
result sets are returned in the form of streams which can be read by a Data Reader
object, or pushed into a Dataset object.

35
 DBAO

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 North wind database.

Data Readers

The Data Reader object is somewhat synonymous with a read-

only/forward-only cursor over data. The Data Reader API supports flat as well as
hierarchical data. A Data Reader object is returned after executing a command
against a database. The format of the returned Data Reader object is different
from a record set. For example, you might use the Data Reader to show the results
of a search list in a web page.

Datasets and Data Adapters

Datasets

The Dataset object is similar to the ADO Record set object, but more
powerful, and with one other important distinction: the Dataset is always

36
 DBAO

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 Get Changes method of the Dataset object
actually creates a second Dataset that contains only the changes to the data. This
Dataset is then used by a Data Adapter (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 Web Services. In fact, a Dataset with a schema can
actually be compiled for type safety and statement completion.

Data Adapters (OLEDB/SQL)

The Data Adapter object works as a bridge between the Dataset and the
source data. Using the provider-specific SqlDataAdapter (along with its
associated SqlCommand and 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 Data Adapter object uses commands to update the data source after
changes have been made to the Dataset. Using the Fill method of the Data

37
 DBAO

Adapter calls the SELECT command; using the Update method calls the
INSERT, UPDATE or DELETES 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
Command Builder 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 Data Adapter, 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

38
 DBAO

ASP.Net

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

39
 DBAO

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 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

40
 DBAO

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.

41
 DBAO

Active Server Pages.NET

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.

42
 DBAO

 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 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

43
 DBAO

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.

44
 DBAO

 The ability for developers to cleanly structure their page logic in an orderly
fashion (not "spaghetti code").

 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 post back 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.

45
 DBAO

46
 DBAO

PROJECT DESIGN

SOFTWARE ENGINEERING PARADIGM APPLIED- (RAD-

MODEL)

The two design objectives continuously sought by developers are reliability

and maintenance.

Reliable System

There are two levels of reliability. The first is meeting the right
requirements. A careful and through systems study is needed to satisfy this aspect
of reliability. The second level of systems reliability involves the actual working
delivered to the user. At this level, the systems reliability is interwoven with
software engineering and development. There are three approaches to reliability.

1. Error avoidance: Prevents errors from occurring in software.

2. Error detection and correction: In this approach errors are recognized
whenever they are encountered and correcting the error by effect of error, of the
system does not fail.
3. Error tolerance: In this approach errors are recognized whenever they occur,
but enable the system to keep running through degraded perform or by applying
values that instruct the system to continue process.

47
 DBAO

Maintenance:

The key to reducing need for maintenance, while working, if possible to do

essential tasks.
1. More accurately defining user requirement during system development.
2. Assembling better systems documentation.
3. Using more effective methods for designing, processing, login and
communicating information with project team members.
4. Making better use of existing tools and techniques.
5. Managing system engineering process effectively.

Output Design:

One of the most important factors of an information system for the user is
the output the system produces. Without the quality of the output, the entire system
may appear unnecessary that will make us avoid using it possibly causing it to fail.
Designing the output should process the in an organized well throughout the
manner. The right output must be developed while ensuring that each output
element is designed so that people will find the system easy to use effectively.
The term output applying to information produced by an information system
whether printed or displayed while designing the output we should identify the
specific output that is needed to information requirements select a method to
present the formation and create a document report or other formats that contains
produced by the system.

48
 DBAO

Types of output:

Whether the output is formatted report or a simple listing of the contents of a

file, a computer process will produce the output.

 A Document
 A Message
 Retrieval from a data store
 Transmission from a process or system activity
 Directly from an output sources

Layout Design:

It is an arrangement of items on the output medium. The layouts are building

a mock up of the actual reports or document, as it will appear after the system is in
operation. The output layout has been designated to cover information. The outputs
are presented in the appendix.

Input design and control:

Input specifications describe the manner in which data enter the system for
processing. Input design features will ensure the reliability of the systems and
produce results from accurate data, or thus can be result in the production of
erroneous information. The input design also determines whenever the user can
interact efficiently with this system.

49
 DBAO

Objectives of input design:

Input design consists of developing specifications and procedures for data

preparation, the steps necessary to put transaction data into a usable from for
processing and data entry, the activity of data into the computer processing. The
five objectives of input design are:

 Controlling the amount of input

 Avoiding delay
 Avoiding error in data
 Avoiding extra steps
 Keeping the process simple

Controlling the amount of input:

Data preparation and data entry operation depend on people, because labour
costs are high, the cost of preparing and entering data is also high. Reducing
data requirement expense. By reducing input requirement the speed of entire
process from data capturing to processing to provide results to users.

Avoiding delay:

The processing delay resulting from data preparation or data entry operations is
called bottlenecks. Avoiding bottlenecks should be one objective of input.

Avoiding errors:

Through input validation we control the errors in the input data.

50
 DBAO

Avoiding extra steps:

The designer should avoid the input design that cause extra steps in processing
saving or adding a single step in large number of transactions saves a lot of
processing time or takes more time to process.

Keeping process simple:

If controls are more people may feel difficult in using the systems. The best-
designed system fits the people who use it in a way that is comfortable for
them.

NORMALIZATION

It is a process of converting a relation to a standard form. The process is

used to handle the problems that can arise due to data redundancy i.e. repetition of
data in the database, maintain data integrity as well as handling problems that can
arise due to insertion, updating, deletion anomalies.

Decomposing is the process of splitting relations into multiple relations to

eliminate anomalies and maintain anomalies and maintain data integrity. To do
this we use normal forms or rules for structuring relation.

Insertion anomaly: Inability to add data to the database due to absence of other
data.

Deletion anomaly: Unintended loss of data due to deletion of other data.

51
 DBAO

Update anomaly: Data inconsistency resulting from data redundancy and partial
update

Normal Forms: These are the rules for structuring relations that eliminate
anomalies.

First Normal Form:

A relation is said to be in first normal form if the values in the relation are
atomic for every attribute in the relation. By this we mean simply that no attribute
value can be a set of values or, as it is sometimes expressed, a repeating group.

Second Normal Form:

A relation is said to be in second Normal form is it is in first normal form

and it should satisfy any one of the following rules.

1) Primary key is a not a composite primary key

2) No non key attributes are present
3) Every non key attribute is fully functionally dependent on full set of primary
key.

Third Normal Form:

A relation is said to be in third normal form if their exits no transitive

dependencies.

52
 DBAO

Transitive Dependency: If two non key attributes depend on each other as well as
on the primary key then they are said to be transitively dependent.

The above normalization principles were applied to decompose the data in

multiple tables thereby making the data to be maintained in a consistent state.

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

Database:

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 

53
 DBAO

2. TB_ADDRESS_AUDITOR:

Sno ColumnName DataType Length AllowNulls Constraints

1 ADDRESSID NUMERIC 9 P
2 AUDITORID NUMERIC 5 
3 ADDRESS1 Varchar 30 
4 ADDRESS2 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 

54
 DBAO

3. TB_ADDRESS_COMPANY:

Sno ColumnName DataType Length AllowNulls Constraints

1 ADDRESSID NUMERIC 9 P
2 COMPANY_ID NUMERIC 5 
3 ADDRESS1 Varchar 100 
4 ADDRESS2 Varchar 100 
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:

Sno ColumnName DataType Length AllowNulls Constraints

1 AUDIT_TYPE_ID NUMERIC 5 P
2 AUDIT_TYPE Varchar 50 
3 AUDIT_TYPE_DESC Varchar 20 

55
 DBAO

5. TB_AUDITFREQ_TYPE:

Sno ColumnName DataType Length AllowNulls Constraints

1 AUDITFREQ_TYPE_ID NUMERIC 9 P
2 AUDITFREQ_TYPE Varchar 50 
3 AUDITFREQ_TYPE_DESC Varchar 50 

6. TB_AUDITOR:

Sno ColumnName DataType Length AllowNulls Constraints

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 

56
 DBAO

7. TB_AUDITOR_SCODE:

Sno ColumnName DataType Length AllowNulls Constraints

1 AUDITORID NUMERIC 5
2 SICCODE Varchar 20 

8. TB_AUDITOR_TYPE:

Sno ColumnName DataType Length AllowNulls Constraints

1 AUDITOR_TYPE_ID NUMERIC 5 P
2 AUDITOR_TYPE Varchar 15 
3 AUDITOR_TYPE_DESC Varchar 50 

9. TB_CERTIFICATE_INFO:

Sno ColumnName DataType Length AllowNulls Constraints

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 

57
 DBAO

10. TB_CERTIFICATE_TYPE:

Sno ColumnName DataType Length AllowNulls Constraints

1 CERT_TYPE_ID Numeric 9 P
2 CERT_TYPE Varchar 50 
3 CERT_TYPE_DESC Varchar 50 

11. TB_COMM_TYPE:

Sno ColumnName DataType Length AllowNulls Constraints

1 COMMTYPEID Numeric 5 P
2 COMMTYPE Varchar 50 
3 COMMDESC Varchar 50 

12. TB_COMMUNICATION:

Sno ColumnName DataType Length AllowNulls Constraints

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 

58
 DBAO

13. TB_COMP_SHIFT:

Sno ColumnName DataType Length AllowNulls Constraints

1 COMPANY_ID Numeric 9 
2 SHIFTID Numeric 5 
3 SHIFTTIME Varchar 20 
4 TOTALEMP Numeric 5 

14. TB_COMPANY_DETAILS:

Sno ColumnName DataType Length AllowNulls Constraints

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 
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 

59
 DBAO

15. TB_ENQUIRY:

Sno ColumnName DataType Length AllowNulls Constraints

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:

Sno ColumnName DataType Length AllowNulls Constraints

1 FEEDBACKID Numeric 5 P
2 AUDITNO Numeric 9 
3 FEEDBACK_TYPE_ID Numeric 5 

60
 DBAO

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:

Sno ColumnName DataType Length AllowNulls Constraints

1 FEEDBACK_TYPE_ID Numeric 9 P
2 FEEDBACKTYPE Varchar 50 
3 FEEDBACKDESC Varchar 50 

18. TB_FEES:

Sno ColumnName DataType Length AllowNulls Constraints

1 AUDITNO Numeric 9 
2 FEESRS Numeric 9 
3 FEESDLR Numeric 9 
4 INVNO Varchar 10 
5 INVDT DateTime 8 
6 FEEPAIDRS Numeric 9 
7 FEEPAIDDLR Numeric 9 
8 FEEPAIDDT DateTime 8 

61
 DBAO

19. TB_QUOT_LOG_FEES:

Sno ColumnName DataType Length AllowNulls Constraints

1 QUOTATIONNO Varchar 30 
2 AUDIT_TYPE_ID Numeric 5 
3 AUDITFEESRS Numeric 9 
4 AUDITFEESDLR Numeric 9 

20. TB_QUOTATION:

Sno ColumnName DataType Length AllowNulls Constraints

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:

Sno ColumnName DataType Length AllowNulls Constraints

1 AUDITNO Numeric 9 P
2 AUDIT_TYPE_ID Numeric 5 
3 REG_NO Numeric 9 
4 FILE_NO Varchar 30 
5 REQUESTDT DateTime 8 
6 SCHEDULEDDT DateTime 8 

62
 DBAO

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:

Sno ColumnName DataType Length AllowNulls Constraints

1 AUDITNO Numeric 9 
2 AUDITORID Numeric 5 
3 MANDAYS Numeric 5 
4 IS_LA Varchar 2 

23. TB_REGISTRATION:

Sno ColumnName DataType Length AllowNulls Constraints

1 REG_NO Numeric 9 P
2 FILE_NO Varchar 30
3 FILEDATE DateTime 8 

63
 DBAO

4 FILESTORAGE Varchar 30 
5 QUOTATIONNO Varchar 30 
6 COMPANY_ID Numeric 9 
7 APPLICATION_FEEPAID Char 1 

24. TB_USER:

Sno ColumnName DataType Length AllowNulls Constraints

1 USERID Numeric 9
2 USERTYPE Varchar 20 
3 USERNAME Varchar 20 
4 PASSWORD Varchar 20 

64
 DBAO

E- R DIAGRAM

65
 DBAO

66
 DBAO

SCREENS

67
 DBAO

68
 DBAO

69
 DBAO

70
 DBAO

71
 DBAO

PROJECT TESTING

COMPILATION TEST:

 It was a good idea to do our stress testing early on, because it gave us time to
fix some of the unexpected deadlocks and stability problems that only
occurred when components were exposed to very high transaction volumes.

EXECUTION TEST:

 This program was successfully loaded and executed. Because of good

programming there were no execution errors.

OUTPUT TEST:

 The successful output screens are placed in the output screens section.

72
 DBAO

73
 DBAO

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.

74
 DBAO

75
 DBAO

BIBLIOGRAPHY

SOFTWARE ENGINEERING

By Roger.S. Pressman

SQL FOR PROFESSIONALS

By Jain

C#.NET

By Wrox Publications

ASP.Net Professional

By Wrox Publications

MSDN 2002

By Microsoft

76