Download as docx, pdf, or txt
Download as docx, pdf, or txt
You are on page 1of 66

WOMEN SMALL SCALE INDUSTRIES USING ASP.

NET AND MSSQL

Project Report Submitted to the

MADURAI KAMARAJ UNIVERSITY, MADURAI

In partial fulfillment of the requirement for the award of the degree of

BACHELOR OF INFORMATION TECHNOLOGY

SUBMITTED BY

M.DHARANI (Reg.No:C1S22953)

G.SIVA RANJANI (Reg.No:C1S22959)

UNDER THE GUIDANCE OF


G.VENKATESWARAN MCA., MPhil.,

DEPARTMENT OF INFORMATION TECHNOLOGY


NPR ARTS & SCIENCE COLLEGE
NATHAM
2023-2024
NPR ARTS & SCIENCE COLLEGE
NATHAM

DEPARTMENT OF INFORMATION TECHNOLOGY

BONAFIDE CERTIFICATE

Certified that this project report “WOMEN SMALL SCALE INDUSTRIES USING
ASP.NET AND MSSQL” is the bonafide work of M. DHARANI (C1S22953) & G.SIVA
RANJANI (C1S22959) in Bachelor of Information Technology who carried out the project
work under my supervision.

Internal Guide Head of the Department

Mr. G. VENKATESWARAN MCA., M.Phil., Mrs. S. SHARMILA JEYARANI MCA., M.Phil., ME.,

Submitted for the viva-voice held at NPR Arts and Science College, Natham on ________

INTERNAL EXAMINER EXTERNAL EXAMINER


DECLARATION

We hereby declare that this project work entitled “WOMEN SMALL SCAALE
INDUSTRIES USING ASP.NET AND MSSQL” is a record of original work done by us under
the guidance of Mr. G. VENKATESWARAN MCA., M.Phil., Department of Information
Technology, NPR ARTS & SCIENCE COLLEGE, NATHAM and this project work has not
formed the basis for the award of any degree or similar to candidate in any university.

M.DHARANI (C1S22953)

Place:

Date: G.SIVA RANJANI (C1S22959)


ACKNOWLEDGEMENT

We Praise GOD almighty for his blessings and grace showered to us during our project
work and to finish this project in a successful way. Our Sincere efforts have made us to
accomplish the task of completing this project

1. We express our heartfelt thanks to our beloved principal Dr. S.


THABASU KANNAN, MCA, M.Phil., M.Tech., Ph.D., MBA, M.Phil., D.Litt.,
FIE for giving us for an opportunity to undergo this project work.

We Extend our profound gratitude reference to Mrs. S. SHARMILA JEYARANI MCA.,


M.Phil., M.E., Head of the Department, Department of Information Technology, NPR Arts &
Science College Natham, for giving an opportunity to undergo this project work and timely help.

Our Heartfelt to express our deep sense of gratitude to our guide


Mr.G. VENKATESWARAN MCA., M.Phil., Assistant Professor, Department of Information
Technology, NPR Arts & Science College, Natham for her guidance and supervision throughout
the period of our project work.

Our Profound thanks go to all respondents who have rendered full co-operation during the
time of data collection.

We express my high thankfulness to my parents and my friends for their help and

encouragement throughout the successful completion of my project work.


TABLE OF CONTENTS

S.No CONTENTS PAGENO


1 INTRODUCTION 1

1.1 About the project

2 SYSTEM STUDY AND ANALYSIS 3

2.1 Feasibility Study

2.2 Existing System

2.3 Proposed System

3 SYSTEM ENVIRONMENT 7

3.1 Hardware Requirement

3.2 Software Requirement

3.3 Software Specification

4 SYSTEM DESIGN 18

4.1 Input Design

4.2 Output Design

4.3 Data Flow Diagram

4.4 Data Dictionary

5 SYSTEM SPECIFATION 24

5.1 Module Description

6 ER DIAGRAM 27
7 SYSTEM IMPLEMENTATION 29

8 SYSTEM TESTING 31

9 CONCLUSION 33

10 FUTURE ENHANCEMENT 29

11 BIBLIOGRAPHY 35

12 APPENDIX 36

I. Screen Shots
II. Sample Coding

II.
III.
IV.
V.
VI.
VII.
VIII.
IX.
X.
XI.
XII.
XIII.
XIV.
XV.
XVI.
XVII.
XVIII.
XIX. INTRODUCTION
1.1 ABOUT THE PROJECT

Abstract:
Nowadays women power forms an important segment of the labor force
and the economic role played by them cannot be isolated from the framework of development.
Due to rapid advancement in e-technology various monitoring systems are developed for
performing various activities. The monitoring systems are mainly used in industries for
controlling of equipment and also used in house hold purposes and in offices for controlling the
appliances. This system is developed for women who can be as a guide for their personal growth.
The term women’s rights refer to freedom and entitlements of women and girls of all age. This
system is give idea for the women to start the business. The admin is maintain the small industries
details like business name, common description about the business, the amount expenses details,
number of employee details. The user has no restriction to register into the system. It guide the
user to select the correct and accurate information. The loan details are also available so user no
needs worry about the amount.
SYSTEM ANALYSIS
2.1 Feasibility Study
Preliminary investigation examine project feasibility, the likelihood the
system will be useful to the organization. The main objective of the feasibility study is to test the
Technical, Operational and Economical feasibility for adding new modules and debugging old
running system. All system is feasible if they are unlimited resources and infinite time. There are
aspects in the feasibility study portion of the preliminary investigation:
 Technical Feasibility
 Operational Feasibility
 Economical Feasibility

TECHNICAL FEASIBILITY
The technical issue usually raised during the feasibility stage of the investigation
includes the following:

 Does the necessary technology exist to do what is suggested?


 Do the proposed equipment have the technical capacity to hold the data required to use the
new system?
 Will the proposed system provide adequate response to inquiries, regardless of the number or
location of users?
 Can the system be upgraded if developed?
 Are there technical guarantees of accuracy, reliability, ease of access and data security?

Earlier no system existed to cater to the needs of ‘Secure Infrastructure


Implementation System’. The current system developed is technically feasible. It is a web based
user interface for audit workflow at NIC-CSD. Thus it provides an easy access to the users. The
database’s purpose is to create, establish and maintain a workflow among various entities in order
to facilitate all concerned users in their various capacities or roles. Permission to the users would
be granted based on the roles specified. Therefore, it provides the technical guarantee of accuracy,
reliability and security. The software and hard requirements for the development of this project
are not many and are already available in-house at NIC or are available as free as open source.
The work for the project is done with the current equipment and existing software technology.
Necessary bandwidth exists for providing a fast feedback to the users irrespective of the number
of users using the system.

OPERATIONAL FEASIBILITY

Proposed projects are beneficial only if they can be turned out into
information system. That will meet the organization’s operating requirements. Operational
feasibility aspects of the project are to be taken as an important part of the project implementation.
Some of the important issues raised are to test the operational feasibility of a project includes the
following: -

 Is there sufficient support for the management from the users?


 Will the system be used and work properly if it is being developed and implemented?
 Will there be any resistance from the user that will undermine the possible application
benefits?

This system is targeted to be in accordance with the above-mentioned


issues. Beforehand, the management issues and user requirements have been taken into
consideration. So there is no question of resistance from the users that can undermine the possible
application benefits.
The well-planned design would ensure the optimal utilization of the computer resources and
would help in the improvement of performance status.

ECONOMICAL FEASIBILITY

A system can be developed technically and that will be used if


installed must still be a good investment for the organization. In the economical feasibility, the
development cost in creating the system is evaluated against the ultimate benefit derived from the
new systems. Financial benefits must equal or exceed the costs.
The system is economically feasible. It does not require any addition
hardware or software. Since the interface for this system is developed using the existing resources
and technologies available at NIC, There is nominal expenditure and economical feasibility for
certain.

2.2 Existing System


The present system is semi-automated system. Maintaining critical
information in the files and manuals is full of risk and a tedious process .The existing system
needs to save his information in the form of excel sheets or Disk Drives. The system gives us very
less security for saving data; some data may be lost due to mismanagement. It is a manual system
or semi-automated system.

Disadvantages
 It is very critical to search the information.
 There is no interface to show the details
 It doesn’t have any possibility to sending regular newsletter.
 If the user wants to send the complaint, then the user needs to prepare it manually on the paper.

2.3 PROPOSED SYSTEM

The development of this new system contains the following


activities, which try to automate the entire process keeping in the view of database integration
approach. User Friendliness is provided in the application with various controls provided by
system Rich User Interface. The system makes the overall project management much easier and
flexible. It can be accessed over the Intranet. The user information files can be stored in
centralized database which can be maintained by the system. There is no risk of data management
at any level while the project development is under process.

Advantages
 It gives good security for user information
 Authentication is provided for this application and It is easier and flexible data management.

SYSTEM ENVIRONMENT
3.1 Hardware Requirement :

The hardware used for the development of the project is:

 Processor Type : Pentium®DualCore


 Speed : 2.4GHZ
 RAM : 2GB
 Hard Disk : 500GB
 Monitor : LCD
 Kit : Keyboard, Mouse

3.2 Software Requirement :

The software used for the development of the project is:

 Operating System : Windows 7


 Front End : Asp.net
 Back End : Ms Sql
3.3 Software Specification
3.3.1 DESCRIPTION OF SOFTWARE ENVIRONMENT
Asp.NET

ASP.NET is a new way to program dynamic and interactive Web applications.


ASP.NET is a compiled environment that makes extensive use of the Microsoft® .NET Framework, and
the entire .NET platform is available to any ASP.NET application.

(1)
What is ASP?

Microsoft Active Server Pages (ASP) is a server-side scripting technology. Any


scripting or programming language that is compliant with the Component Object Model (COM)
can be used to create Web server applications.

Take a pure HTML file and add scripting code to it, so that one file contains both
HTML and, for example, Microsoft Visual Basic Scripting Edition (VBScript). That file has the
file extension .asp (instead of .html) and is accessed via HTTP requests.

In the browser, a user enters the URL for the file. When the server receives the
request, it recognizes the extension; Microsoft Internet Information Service (IIS) treats the .asp
file differently from an .html file. A COM component (asp.dll) parses the file for the scripting
code and processes it from the top of the file to bottom. The scripting code inside the .asp file is
interpreted each time the file is requested.

Normally, a standard HTML document will be generated and sent to the browser
as a response; but other data, such as images or binary data, can be returned.

What can I do with ASP?

Fortunately we are not limited to dynamically generating and presenting date and
time information in the client browser or performing computations. We can also access COM
components to extend the functionality of our Web site.
With ASP we can use client-side scripts as well as server-side scripts. Maybe
we want to validate user input or access a database. ASP provides solutions for transaction
processing and managing session state.

While ASP should not be used for implementing business logic, we can easily
and quickly create simple Web applications.

What’s wrong with that?

There are many problems with ASP if we think of today’s need for powerful
Web applications. Some of these “restrictions” are listed here:

 Mixes layout (HTML) and logic (scripting code)


Mixing HTML code and scripting code may not cause problems when
implementing and editing one file the first time. You will begin to have problems when a
programmer and a designer have to update the functionality and the layout, because having both
HTML and scripting code in one file complicates the update process.

 Interpreting ASP code leads to performance loss


As mentioned earlier, the scripting code in an ASP file is interpreted
each time the file is requested. The .asp file name extension alerts IIS that the file contains
scripting code. IIS then parses the file for the code and processes it.

On Web servers where hundreds of client requests per minute are


expected, this time consuming processing leads to a performance loss.

 Uses JScript and VBScript


Microsoft JScript® and VBScript are common scripting languages and
currently supported by the ASP scripting engine. Because both JScript and VBScript are not
strongly typed, this leads to another performance loss.

You can use other scripting languages, but custom scripting engines are
hard to find.
 Browser compatibility

Another restriction is that you have to be sure that the user’s browser
can make use of the scripting language your ASP code is written in.

b)

c)

Architecture

In this section you will get an overview of the .NET Framework


architecture, the Web application model, and the configuration system.

 The .NET Framework Architecture

To really understand what makes ASP.NET more than just “ASP 4.0”
we need to have a look at the underlying .NET Framework architecture.
The .NET Framework architecture is built on top of the operating
system services. This framework contains different layers.

In the .NET Framework common language runtime, this resides on


top of the operating system services. The common language runtime loads and executes code that
targets the runtime. This code is therefore called managed code. The runtime gives you, for
example, the ability for cross-language integration. For that matter it makes use of the common
type system, which defines a standard set of types and rules to create new types.

As mentioned earlier, the .NET Framework provides a rich set of


class libraries. These include base classes, like networking and input/output classes, a data class
library for data access, and classes for use by programming tools, such as debugging services. All
of them are brought together by the Services Framework, which sits on top of the common
language runtime.

The top layer of the .NET framework consists of the Windows


application model and, in parallel, the Web application model.

Use the Windows application model—Windows Forms—to develop


more traditional Windows applications and take advantage of new Windows 2000 features. You
can include existing COM components, but also make use of Web Services (which are explained
later).

The Web application model—in the slide presented as ASP.NET—


includes Web Forms and Web Services.

ASP.NET comes with built-in Web Forms controls, which are


responsible for generating the user interface. They mirror typical HTML widgets like text boxes
or buttons. If these controls do not fit your needs, you are free to create your own user controls.

Web Services brings you a model to bind different applications


over the Internet. This model is based on existing infrastructure and applications and is therefore
standard-based, simple, and adaptable.

A Web Service can be understood as a contract between server


and client. Those contracts are described by the XML-based Web Services Description Language
(WSDL). Doing so, Web Services are defined as endpoints that communicate via XML-based
messages.

 Web Application Model

But now we will show you in more detail how ASP.NET requests are
handled.

As with earlier versions of ASP, a client can access your Web application
using URLs. So, a Web application is a set of URLs related to one or more virtual directories on
the Web server.

Each request is processed by the HTTP runtime, which is the core of the
ASP.NET Web application model. Processing consists of resolving the URL of the request to the
corresponding application, and dispatching the request to the application for further processing.

Requests are led through a pipeline of HTTP modules. With each module
a developer can catch and modify requests. One of those modules could be, for example, a
security module.

At the end of the module pipeline, there are request handlers. They enable
the processing of individual URLs within an application.

From the developer’s point of view there is easy access to a clean and
well-structured object model. Beside those aspects mentioned above, there is an object
encapsulating all information about an individual HTTP request within ASP.NET. This object is
called Http Context. HTTP modules and request handlers access ASP.NET intrinsic via Http
Context.

 HTTP Runtime

Now in more detail:


(1) Managed code
While the HTTP runtime is managed code—because it targets the common language
runtime—it runs within an unmanaged host process that could be, for example, Microsoft IIS.

So, for ASP.NET the .NET Framework uses IIS as a more or less “dump” gateway
for its own HTTP infrastructure.

Objectives

This module covers basic concepts and principles of .NET and an overview of
the .NET Framework.

Challenges for the Development Organization

 Development

The developer and/or development organization have historically attacked the


production of a solution by first asking, “What is the target platform?” The answer may be one of
several possibilities: Microsoft Windows® 95, Windows 98, Windows Millennium Edition,
Windows NT®, or Windows 2000; the Apple Macintosh; UNIX (any given flavor); or even a
Web browser. With the answer in hand, the development team chooses a language or tool—
sometimes the choice of target and development platform is the same! Often the decision is based
not on what is best to create the solution but on what is available for the target platform. As you
may have experienced for yourself, once you choose the platform and development begins, there
is little hope for changing the platform decision at a later date.

 Delivery

The traditional delivery method for software solutions is predominantly via CD or


even floppy disk. Although it is true that electronic delivery of software solutions is an option
today, the current means of doing so has drawbacks.
The CD and floppy disk methods require the delivery of a physical medium to the
customer. What is wrong with that? To begin with, it costs both the producer and consumer
money in several obvious ways: the medium itself, creation of the deliverable, packaging, postage
or personal delivery, and so on.

The electronic delivery method is superior in that there are no costs involved in
the packaging of the deliverable. There are no CDs to burn and no CD packaging to design and
print, no physical distribution is involved, and printed manuals are optional. However, the process
of ordering and downloading software with today’s Internet-based systems requires user
intervention, as well as vigilance against malicious code.

 Stability

If you are a computer user, you have certainly experienced DLL compatibility
issues, known colloquially as “DLL Hell.” This often happens when the vendor’s software
requires certain functionality normally found in a component shipped with the operating system
(OS), known as a dynamic-link library (DLL), but the available functionality is not exactly what is
required. The current system and development models require the vendor to solve the problem by
creating a customized version, which it ships with the software. During installation, the vendor’s
version replaces the original DLL.

The problem is that previously installed, running software may not work with the
newly installed version. This “bug,” which can be quite an event to fix if the operating system is
the software that gets broken, happens all too frequently. Unfortunately, a good solution to this
problem, using today’s systems and shared by both developers and consumers, does not exist.
DLL compatibility issues also exist outside of the OS area.

 Maintenance

Maintenance has proven itself the Achilles’ heel of software, often requiring
significant updates to the existing version. Given the current development, production, and
delivery methods, a maintenance update to a software solution often requires that nearly an entire
version be delivered to the customer. As you may well know, maintenance also reintroduces all
the aforementioned headaches.

MS SQL SERVER

DATABASE:

Database is an organized list of data (information) that can be queried to find information
quickly
and easily based chosen reference point.

Such a last name of security number. In database terminology, the columns are called fields
and the rows are called records.

The kind of organization in a database is called a table.

SQL SERVER:

SQL Server is a RDBMS that you can store and manipulate large amount of information. A

relational database is a database, which consists of tables of that related information that are linked

together on key fields.

The tools of SQL Server are user friendly and provide a powerful development environment,

making it equally appropriate for novices and MIS professionals. For example we can access quickly

and easily create a database of mailing list information that we can merge with other document.

SQL Server commands are related to Oracle, So that the oracle users can easily operate the SQL

Server, One of the main advantage is it can easily execute set of queries at a time.
MAIN ELEMENTS OF SQL SERVER:

SQL Server is an Object Oriented program. Objects are modules, which is used to provide

information and programs, which any of user can directly apply to create application. Each Object has

properties that defines how the looks and perform. It has the following Objects

o Tables

o Queries

o Forms

o Reports

o Module

o Relationships

TABLE:

Tables are primary building blocks of SQL SERVER database. All data is stored in tables.

Every table in the database focus on one subject. We can combine specific fields from multiple tables

into one data sheet. The datasheet that a query written is called a record set.

QUERIES:

Queries are used to perform some operation for retrieve the data from the table and to store the
data to the table.
SYSTEM DESIGN
4.1 Input Design

Input design is the process of converting user-oriented input into computer-based


format. The goal of designing input data is to make data entry as easy as possible and free from
errors. Errors in the input are handled in the input design. The input data is the lifeblood of a
system and have to be analyzed and designed with utmost case and consideration. The decisions
made during the input design are:

 To provide cost effective method of input


 To achieve the highest possible level of accuracy
 To ensure that input is understand by the user

In this project various resources like textboxes, dropdown list, link buttons etc., are
used for accepting user inputs. The main type of inputs to this project are files which can be a text
file or image file. The other inputs to this project include file names, destination user name,
integer values for splitting files into packets. The file name is nothing but the file that is to be
splitted into packets and transferred to the specified destination. Destination user name is the user
who is going to reassemble the splitted packets.

Taking into account, all the above needs of the input designing, the new process
designing could have the following features. In all cases processing should be automatic and
manual work should be kept minimum. Similarly, the user input should also be kept minimum or
least extend possible. By giving the above input calculations should be automatic. The auto
calculation is the motto of this new process, while providing the auto calculation the results with
minimum time operation, should be accurate and free from errors.

4.2 Output Design

Output design generally refers to the results and information’s that are
generated by the system for many end-users; output is the main reason for developing the system
and the basis on which they evaluate the usefulness of the application. The basic requirements of
output are that it should be accurate, timely and appropriate, in terms of content, medium and
layout for its intended purpose.

The important task of any system lies in the capability of producing high
quality output and reports. Computer output is the most important and direct source of information
to the user. A good output design contains all required information and well formatted for the
better visualization and avoid the complexity in displaying the data this system was developed by
keeping in mind and proper output is displayed for the users accurately.

In this project the output is the reassembled file that was received by the user
at the destination and the messages found in the client’s inbox and the report that was generated
which shows the number of packets transferred along with acknowledgement. These outputs are
obtained in a new page on the browser.
4.3 Data Flow Diagram

DFD

database
database

Data manager login Add business details

View user registration details Based on business loan details is


added
Search history
Visitors count database

user register

login Search business


database

View business details and loan


details
System Flow Diagram

View user details

admin login
Manage visitors count

Manage search count


database Add women business details

Add loan details


database
It shows business and loan
database
details

User Search business


login
register
4.4 Data Dictionary:

ADMIN

COLUMN NAME DATA TYPE

username varchar(50)

password varchar(50)

dbo.branchdetails

COLUMN NAME DATA TYPE

Id int(autoincrement)

Branch name varchar(50)

address varchar(500)

Manager name varchar(50)

Number workers varchar(50)

29
Transport

COLUMN NAME DATA TYPE

Id int(autoincrement)

Transport name INT

Employee name varchar(50)

Source root varchar(50)

Destination root varchar(50)

Data of transport varchar(50)

others varchar(50)

Quotation

COLUMN NAME DATA TYPE

Id int(autoincrement)

User type varchar(50)

Quotation type varchar(50)

dateofpurchase varchar(50)

importitems varchar(50)

totalamount varchar(50)

billstatus varchar(50)

billby varchar(50)

30
SYSTEM SPECIFATION

31
5.1 Module Description

Modules

The Modules involved are

Data Manager

Web Registration

Business details

Loan details

Report

Modules Description

Data Manager

In this system, Data Manager is tread as an administrator. The administrator has all the
privileges in this system. The administrator can monitor the user registration and add/update the new
business details in this system. He/she can insert necessary data into the system using his administrative
user interface.

Web Registration

The system has a process of registration. Every citizen needs to submit his complete details in
the form of registration. Whenever a user registration completed automatically user will get a user id and
password. By using that user id and password member can log into the system. If registration process is
completed successfully an email reminder is generated and sends to the citizen.

Business details

The admin will save the news business information into the website. The business information
contains details like business name, business type, number of employees, expenses, income details.

Loan Details

32
In the product software, the admin will enter the loan amount possibility details according to
their business. The user search module is designed as the open interface through which user can search and
they will get the various available loan schemes for the business.

Loan Calculation

From this module user automatically calculate their own loan calculation values like
amount ,interest, duration etc. calculation maintained by Emi calculation wise.

Reports

Different kind of reports is generated by the system.

 The user registration reports by date wise


 It shows the visitors counts and generate the overall business information reports.

33
ER DIAGRAM

34
status

loanrequest username Phone no


Mail id

address

anknam
Admin amount pwd user
cusname

request status
login

interest

Loan amount monthlydate

requestid Loan calculation


loan

35
SYSTEM IMPLEMENTATION

36
SYSTEM IMPLEMENTATION

Provision must be made for environmental change which may affect either the computer
or other parts of computer based system, such activity is normally called maintenance. It included both
improvement of the system functions and the correction of the faults which arise during the operation of
the system.

Maintenance activity may require the continuing involvement of a large proportion of


computer department resources.

Responsibility for the maintenance of a particular system must be allocated before any
requirement for change arises. The maintenance team should be allowed to influence the original design of
the system programs in so far as if will affect their maintainability.

37
SYSTEM TESTING

38
SYSTEM TESTING

Software testing is an important element of software quality assurance and represents the ultimate
review of specification, design and coding. It increasing visibility of software as a system element and the
costs associates with a software failure are motivating forces for all well planned through testing .The
system is tested with giving wrong information. Cascade deletion and, the software developer checks
updating. Testing and debugging are different activities, but debugging must be accommodated in any
testing strategy.

Unit Testing

The first step in testing is Unit testing. Individual testing are tested to ensure that they
operate correctly. Each component is tested independently, without other system components. The module
interface is tested to ensure that information properly flow into and out of the program. These are tested
that the module operates at boundary established to limit or restrict processing. Unit testing is normally
considered as an adjunct to the coding step. After the coding has been developed, received and verified for
correct syntax, unit testing begins. Here each module is tested to provide its correctness, validity and
determine any missing operations and to verify whether the objectives have been met, errors are noted
down and corrected immediately.

Unit testing is the important and major part of the project. So errors can be rectified easily in
each module and program clarity can be increased. In this project, the entire system is divided into several
modules and is developed individually. Hence, unit testing is conducted to individual modules.

Integration Testing

The second step in the testing process is the Integration testing. Integration testing is the
systematic technique for constructing the program structure while conducting tests to uncover errors
associated with integrating. After the unit test, each module is gradually integrated to form one final
system.

39
All the modules when unit tested will work properly but after integrating the data can cause
error one module can have an inadvertent, adverse effect on another; sub functions when combined may
not produce the desired major function; global data structures can cause problems, etc.

Hence, the objective of integration testing is to take unit tested modules and build a final
program structure. In this project, modules are combined to find the overall performance of the system.

VERIFICATION & VALIDATION

Client Side Validation

Various client side validations are used to ensure on the client side that only valid
data is entered. Client side validation saves server time and load to handle invalid data. Some checks
imposed are:

 VBScript in used to ensure those required fields are filled with suitable data only. Maximum lengths of
the fields of the forms are appropriately defined.
 Forms cannot be submitted without filling up the mandatory data so that manual mistakes of
submitting empty fields that are mandatory can be sorted out at the client side to save the server time
and load.
 Tab-indexes are set according to the need and taking into account the ease of user while working with
the system.

Server Side Validation

Some checks cannot be applied at client side. Server side checks are necessary to save the
system from failing and intimating the user that some invalid operation has been performed or the
performed operation is restricted. Some of the server side checks imposed is:

 Server side constraint has been imposed to check for the validity of primary key and foreign key. A
primary key value cannot be duplicated. Any attempt to duplicate the primary value results into a
message intimating the user about those values through the forms using foreign key can be updated
only of the existing foreign key values.

40
 User is intimating through appropriate messages about the successful operations or exceptions
occurring at server side.

 Various Access Control Mechanisms have been built so that one user may not agitate upon another.
Access permissions to various types of users are controlled according to the organizational structure.
Only permitted users can log on to the system and can have access according to their category. User-
name, passwords and permissions are controlled o the server side.

 Using server side validation, constraints on several restricted operations are imposed.

41
CONCLUSION

42
CONCLUSION

The small scale industries of women have a distinct advantage


of low investment with a high potential for employment generation. Small scale industries have a
unique role to play in the industrial development of the country. Small scale industries are one of
the most cost-effective ways in creating employment spreading industry. In this system user can
search business details and finance details very efficiently. It reduces searching time of the users.

43
FUTURE ENHANCEMENT

44
FUTURE ENHANCEMENT

The project has been viewed using distributed architecture, with centralized storage
of the database. In present system, the MSSQL connection is used. The standards security and data
protective mechanism have been used.

In this system, we can some features to make it more reliable. These are as follows

 The searching procedure should be stronger for student and search as fast as possible.
 Modify approach can better with some graphics effects.
 The backup procedure is incorporated to make sure of the database integrity.

45
BIBLIOGRAPHY
B.

46
BIBILIOGRAPHY

i) Books referred:

 ASP.NET

(i) The Complete Reference by Matthew MacDonald.

 ASP.NET

(i) Developers Guide by Buczek

 Software Engineering

(i) Roger S. Pressman.

 ASP.NET

(i) ASP.NET Professional by Wrox

 C#

(i) ASP.NET Professional by Wrox

ii) Websites:
www.c-sharpcorner.com
www.asp.net
www.microsoft.com

47
APPENDIX

48
SCREEN SHOTS:

49
50
51
52
53
SAMPLE CODING:

Admin login

<%@ Page Language="C#" MasterPageFile="./home.master" AutoEventWireup="true"


CodeFile="admin.aspx.cs" Inherits="admin" Title="Untitled Page" %>

<asp:Content ID="Content1" ContentPlaceHolderID="head" runat="Server">

<style type="text/css">

.form-style-6{

font: 95% Arial, Helvetica, sans-serif;

54
max-width: 400px;

margin: 10px auto;

padding: 16px;

background: #F7F7F7;

.form-style-6 h1{

background:brown;

padding: 20px 0;

font-size: 140%;

font-weight: 300;

text-align: center;

color: #fff;

margin: -16px -16px 16px -16px;

.form-style-6 input[type="text"],

.form-style-6 input[type="password"],

.form-style-6 input[type="date"],

.form-style-6 input[type="date time"],

.form-style-6 input[type="email"],

.form-style-6 input[type="number"],

.form-style-6 input[type="search"],

.form-style-6 input[type="time"],

.form-style-6 input[type="url"],

.form-style-6 textarea,

55
.form-style-6 select

-webkit-transition: all 0.30s ease-in-out;

-moz-transition: all 0.30s ease-in-out;

-ms-transition: all 0.30s ease-in-out;

-o-transition: all 0.30s ease-in-out;

outline: none;

box-sizing: border-box;

-webkit-box-sizing: border-box;

-moz-box-sizing: border-box;

width: 100%;

background: #fff;

margin-bottom: 4%;

border: 1px solid #ccc;

padding: 3%;

color: #555;

font: 95% Arial, Helvetica, sans-serif;

.form-style-6 input[type="text"]:focus,

.form-style-6 input[type="password"]:focus,

.form-style-6 input[type="date"]:focus,

.form-style-6 input[type="datetime"]:focus,

.form-style-6 input[type="email"]:focus,

.form-style-6 input[type="number"]:focus,

56
.form-style-6 input[type="search"]:focus,

.form-style-6 input[type="time"]:focus,

.form-style-6 input[type="url"]:focus,

.form-style-6 textarea:focus,

.form-style-6 select:focus

box-shadow: 0 0 5px #87A96B;

padding: 3%;

border: 1px solid #43D1AF;

.form-style-6 input[type="submit"],

.form-style-6 input[type="button"]{

box-sizing: border-box;

-webkit-box-sizing: border-box;

-moz-box-sizing: border-box;

width: 100%;

padding: 3%;

background:brown;

border-bottom: 2px solid #30C29E;

border-top-style: none;

border-right-style: none;

border-left-style: none;

color: #fff;

57
.form-style-6 input[type="submit"]:hover,

.form-style-6 input[type="button"]:hover{

background:brown;

</style>

</asp:Content>

<asp:Content ID="Content2" ContentPlaceHolderID="ContentPlaceHolder1" runat="Server">

<div>

<img src="admin-login.jpg" width="100%" height="268"/>

<div class="form-style-6">

<h1>Admin Login</h1>

<form>

<asp:TextBox ID="TextBox1" runat="server" placeholder="Username"></asp:TextBox>

<asp:RegularExpressionValidator runat="server"

id="regexpSSN" ControlToValidate="TextBox1"

ValidationExpression="[a-z]*"

ErrorMessage = "*"

Display="Dynamic" />

<asp:TextBox ID="TextBox2" runat="server" placeholder="Password"


TextMode="Password"></asp:TextBox>

<asp:RegularExpressionValidator runat="server"

id="RegularExpressionValidator1" ControlToValidate="TextBox2"

ValidationExpression="[a-z]*"

ErrorMessage = "*"

Display="Dynamic" />
58
<asp:Button ID="Button1" runat="server" Text="Submit" OnClick="Button1_Click"/>

</form>

</div>

</div>

</asp:Content>

using System;

using System.Collections;

using System.Configuration;

using System.Data;

using System.Linq;

using System.Web;

using System.Web.Security;

using System.Web.UI;

using System.Web.UI.HtmlControls;

using System.Web.UI.WebControls;

using System.Web.UI.WebControls.WebParts;

using System.Xml.Linq;

using System.Data.SqlClient;

using womenclasslib;

public partial class admin : System.Web.UI.Page

protected void Page_Load(object sender, EventArgs e)

59
{

protected void Button1_Click(object sender, EventArgs e)

Class1 getcon = new Class1();

SqlConnection con = getcon.connect();

SqlCommand cmd = new SqlCommand("select * from admin where username='" +


TextBox1.Text + "' and password='" + TextBox2.Text + "'", con);

SqlDataReader dr = cmd.ExecuteReader();

if (dr.Read())

Session["username"] = TextBox1.Text;

TextBox2.Text = dr["password"].ToString();

Response.Redirect("adminhome.aspx");

else

ClientScript.RegisterStartupScript(this.GetType(), "ele", "<script>alert('Invalid Username


and Password');</script>");

60
<%@ Page Language="C#" MasterPageFile="./adminhome.master" AutoEventWireup="true"
CodeFile="businessdetails.aspx.cs" Inherits="businessdetails" Title="Untitled Page" %>

<asp:Content ID="Content1" ContentPlaceHolderID="head" Runat="Server">

<style type="text/css">

.form-style-6{

font: 95% Arial, Helvetica, sans-serif;

max-width: 400px;

margin: 10px auto;

padding: 16px;

background: #F7F7F7;

.form-style-6 h1{

background:brown;

padding: 20px 0;

font-size: 140%;

font-weight: 300;

text-align: center;

color: #fff;

margin: -16px -16px 16px -16px;

.form-style-6 input[type="text"],

.form-style-6 input[type="password"],

.form-style-6 input[type="date"],
61
.form-style-6 input[type="datetime"],

.form-style-6 input[type="email"],

.form-style-6 input[type="number"],

.form-style-6 input[type="search"],

.form-style-6 input[type="time"],

.form-style-6 input[type="url"],

.form-style-6 textarea,

.form-style-6 select

-webkit-transition: all 0.30s ease-in-out;

-moz-transition: all 0.30s ease-in-out;

-ms-transition: all 0.30s ease-in-out;

-o-transition: all 0.30s ease-in-out;

outline: none;

box-sizing: border-box;

-webkit-box-sizing: border-box;

-moz-box-sizing: border-box;

width: 100%;

background: #fff;

margin-bottom: 4%;

border: 1px solid #ccc;

padding: 3%;

color: #555;

font: 95% Arial, Helvetica, sans-serif;

62
}

.form-style-6 input[type="text"]:focus,

.form-style-6 input[type="password"]:focus,

.form-style-6 input[type="date"]:focus,

.form-style-6 input[type="datetime"]:focus,

.form-style-6 input[type="email"]:focus,

.form-style-6 input[type="number"]:focus,

.form-style-6 input[type="search"]:focus,

.form-style-6 input[type="time"]:focus,

.form-style-6 input[type="url"]:focus,

.form-style-6 textarea:focus,

.form-style-6 select:focus

box-shadow: 0 0 5px #87A96B;

padding: 3%;

border: 1px solid #43D1AF;

.form-style-6 input[type="submit"],

.form-style-6 input[type="button"]{

box-sizing: border-box;

-webkit-box-sizing: border-box;

-moz-box-sizing: border-box;

width: 100%;

padding: 3%;

63
background:brown;

border-bottom: 2px solid #30C29E;

border-top-style: none;

border-right-style: none;

border-left-style: none;

color: #fff;

.form-style-6 input[type="submit"]:hover,

.form-style-6 input[type="button"]:hover{

background:brown;

</style>

</asp:Content>

<asp:Content ID="Content2" ContentPlaceHolderID="ContentPlaceHolder1" runat="Server">

<div>

<div class="form-style-6">

<h1>Business Details</h1>

<form>

<asp:TextBox ID="TextBox1" runat="server" placeholder="Business Name"></asp:TextBox>

<asp:RegularExpressionValidator runat="server"

id="regexpSSN" ControlToValidate="TextBox1"

ValidationExpression="[a-zA-Z ]*"

ErrorMessage = "*"

Display="Dynamic" />

64
<asp:TextBox ID="TextBox2" runat="server" placeholder="Business Type"></asp:TextBox>

<asp:RegularExpressionValidator runat="server"

id="RegularExpressionValidator3" ControlToValidate="TextBox2"

ValidationExpression="[a-zA-Z ]*"

ErrorMessage = "*"

Display="Dynamic" />

<asp:TextBox ID="TextBox3" runat="server" placeholder="Investment"></asp:TextBox>

<asp:RegularExpressionValidator runat="server"

id="RegularExpressionValidator1" ControlToValidate="TextBox3"

ValidationExpression="[0-9]*"

ErrorMessage = "*"

Display="Dynamic" />

<asp:TextBox ID="TextBox4" runat="server" placeholder="Number of


Workers"></asp:TextBox>

<asp:RegularExpressionValidator runat="server"

id="RegularExpressionValidator2" ControlToValidate="TextBox4"

ValidationExpression="[0-9]*"

ErrorMessage = "*"

Display="Dynamic" />

<asp:Button ID="Button1" runat="server" Text="Save" OnClick="Button1_Click"/>

<asp:Button ID="Button2" runat="server" Text="Update" OnClick="Button2_Click"/><%--

<asp:Button ID="Button3" runat="server" Text="View" OnClick="Button3_Click"/>--%>

</form>

65
</div>

</div>

</asp:Content>

66

You might also like