Documente Academic
Documente Profesional
Documente Cultură
1.1 SYNOPSIS
The Objective of this document is to study and analyze the automation of Central
Excise operations of manufacturing unit in general. CENEX is the Central Excise
Software that aims to take care of all the statutory registers and returns required under the
Central Excise Act and Rules.
The materials purchased by the Manufacturer from his supplier are referred as
Inputs. A document is prepared namely GRN. (Goods Receipt Note) This document
contains all the details of the suppliers invoice and allows the materials in i.e. to the
stores. From stores these materials are directed for production. This GRN is shown to the
Excise authorities. Since it is the receipt of material for production the duty paid against
those materials are treated as material credit
The major change as far as service tax is concerned is that the Supreme Court
Judgment has now been over ruled by amending the law with retrospective effect. The
Central Excise Department can now recover service-tax collected by the users of the
services.
With the result no refund of service-tax paid on the services of goods transport
operators and clearing and forwarding agent would be granted.
A document is prepared namely GRN. (Goods Receipt Note) This document
contains all the details of the suppliers invoice and allows the materials in i.e. to the
stores. From stores these materials are directed for production. This GRN is shown to the
Excise authorities. Since it is the receipt of material for production the duty paid against
those materials are treated as material credit
2 ORGANIZATION PROFILE
SRM SOFTSOLUTIONS AND SOFTWARE is a company committed to provide
support to small, medium and large corporations in the development and management of
software essential to their needs over the entire life cycle of a project or system. All
corporations, regardless of size, need to process enormous amounts of data in support of
the day-to-day operation of the company and the dependence on a corporate information
system and up-grade the existing ones. In seeking efficient and cost-effective approaches
to manage change, many companies have found outsourcing to be particularly attractive.
SRM SOFTSOLUTIONS AND SOFTWARE Private Limited has been
established in 1998 with the objective of providing software solutions to the Domestic
and Export markets as well as for developing highly skilled manpower in specialized
areas of Information Technology promoted by a group of highly qualified Engineering
Managers. SRM has its offices at Austin, Boston, Chennai, and in Delhi. Equipped with
the latest Computing Hardware and Software backed by skilled manpower.
SRM provides comprehensive solutions for the industry software development
needs on turnkey basis. The accent of SRM is not merely on new and emerging
technologies. IT professional are more concerned with providing its clients reliable,
flexible and maintainable solutions to their business problem. SRM realizes that the
watchwords of yesterday Leading Edge Technology need to be tempered in favor of
cost containment.
SRM SOFTSOLUTIONS AND SOFTWARE is here to provide expert services
and support for change management in software systems allowing your organization to
focus on its core business. SRM Systems and Software offers the expertise of
experienced individual software consultants, as well as an off - shore facility with a stateof-the-art information technology infrastructure and a well trained and committed staff.
2
We at SRM provide our clients the potential for significant savings without
compromises in quality or schedule.
guarantees that the software services will be delivered to the customer on time, within
budge, in complete conformance means that at SRM, we are indeed Determined to
Make a Difference.
Services Offered
SRM SOFTSOLUTIONS AND SOFTWARE through its Strategic Business Units
offers the following services.
Consultancy Services
Product Development:
Pentium IV
RAM
512MB
Monitor size
17SVGA
Extra Device
CD-ROM 52x
Operating System
Windows XP
Keyboard
SOFTWARE CONFIGURATION:
Operating System
Windows XP Professional
Environment
.Net Framework
Version 2.0
Language
C#.Net
Web Technology
Web Server
Back End
The ability to group the taskbar buttons of the windows of one application into
one button
The ability to lock the taskbar and other toolbars to prevent accidental changes
Shadows under menus (Windows 2000 had shadows under mouse pointers, but
not menus)
graphics subsystem
and improvements
The ability to discard a newer in favor of the previous one (known as driver
rollback), should a driver upgrade not produce desirable results.
which allows a user to save the current state and open applications of their
desktop and allow another user to log on without losing that information
Support for most modems and connections, as well as networking over, and.
Editions
Main article:
and
implemented by Intel as "" (formerly known as IA-32e and EM64T), found in Intel's and
later chips.
Windows XP Tablet PC Edition was produced for a class of specially designed
notebook/laptop computers called. It is compatible with a pen-sensitive screen,
supporting handwritten notes and portrait-oriented screens.
12
accelerators, connected to one or more servers via a high-speed channel, are also used in
large volume transaction processing environments. DBMS are found at the heart of most.
13
collection of with each table consisting of a set of rows and columns, can satisfy
this property)
The first systems that were relatively faithful implementations of the relational model
were from the University of Michigan; (1969) and from IBM UK Scientific Centre at
Pete lee; (197072) and its follow on (197379). The first system sold as an RDBMS
was, first sold in 1978. Others have been and.
The most popular definition of an RDBMS is a product that presents a view of
data as a collection of rows and columns, even if it is not based strictly upon. By this
definition, RDBMS products typically implement some but not all of Codd's 12 rules.
14
15
17
Microsoft .NET
At the base is the common language runtime, often abbreviated to CLR. This is
the heart of the .NET Framework it is the engine that drives key functionality. It includes,
for example, a common system of data types. These common types, plus a standard
interface convention, make cross-language inheritance possible. In addition to allocation
and management of memory, the CLR also does reference tracking for objects and
handles garbage collection.
The middle layer includes the next generation of standard system Services such as
classes that manage data and Extensible Markup Language (XML). These services are
brought under control of the Framework, making them universally available and making
their usage consistent across languages.
The top layer includes user and program interfaces. Windows Forms is a new and
more advanced way to do standard Win32 screens (often referred to as smart clients).
Web Forms provides a new Web-based user interface. Perhaps the most revolutionary is
Web Services, which provide a mechanism for programs to communicate over the
Internet, using SOAP. Web Services provide an analog of COM and DCOM for object
brokering and interfacing, but based on Internet technologies so that allowance is made
even for integration to non-Microsoft platforms. Web Forms and Web Services, which
constitute the Internet interface portion of .NET, are implemented by a part of the .NET
Framework referred to as ASP.NET.
FEATURES OF ASP.NET
ASP.NET is the next version of Active Server Pages (ASP); it is a unified Web
development platform that provides the services necessary for developers to build
18
21
SECURITY:
The runtime enforces code access security. The security features of the runtime
thus enable legitimate Internet-deployed software to be exceptionally featuring rich. With
regards to security, managed components are awarded varying degrees of trust,
depending on a number of factors that include their origin to perform file-access
operations, registry-access operations, or other sensitive functions.
ROBUSTNESS:
The runtime also enforces code robustness by implementing a strict type- and
code-verification infrastructure called the common type system(CTS). The CTS ensures
that all managed code is self-describing. The managed environment of the runtime
eliminates many common software issues.
23
PRODUCTIVITY:
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.
PERFORMANCE:
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. Finally, the runtime can be
hosted by high-performance, server-side applications, such as Microsoft SQL Server
and Internet Information Services (IIS).
INTEROPERABILITY:
ADO.NET applications can take advantage of the flexibility and broad acceptance
of XML. Because XML is the format for transmitting datasets across the network, any
24
MAINTAINABILITY:
In the life of a deployed system, modest changes are possible, but substantial,
Architectural changes are rarely attempted because they are so difficult. As the
performance load on a deployed application server grows, system resources can become
scarce and response time or throughput can suffer. Faced with this problem, software
architects can choose to divide the server's business-logic processing and user-interface
processing onto separate tiers on separate machines.
In effect, the application server tier is replaced with two tiers, alleviating the
shortage of system resources. If the original application is implemented in ADO.NET
using datasets, this transformation is made easier.
ADO.NET data components in Visual Studio encapsulate data access
functionality in various ways that help you program more quickly and with fewer
mistakes.
PERFORMANCE:
ADO.NET datasets offer performance advantages over ADO disconnected record
sets. In ADO.NET data-type conversion is not necessary.
25
SCALABILITY:
ADO.NET accommodates scalability by encouraging programmers to conserve
limited resources. Any ADO.NET application employs disconnected access to data; it
does not retain database locks or active database connections for long durations.
XML SUPPORT
Extensible Markup Language (XML) provides a method for describing structured
data. XML is a subset of SGML that is optimized for delivery over the Web. The World
Wide Web Consortium (W3C) defines XML standards so that structured data will be
uniform and independent of applications. Visual Studio .NET fully supports XML,
providing the XML Designer to make it easier to edit XML and create XML schemas.
IMPLEMENTATION INHERITANCE
Visual Basic.NET supports implementation inheritance. This means that, while
creating applications in Visual Basic.NET, we can drive from another class, which is
know as the base class that derived class inherits all the methods and properties of the
base class. In the derived class, we can either use the existing code of the base class or
override the existing code. Therefore, with help of the implementation inheritance, code
can be reused.
GARBAGE COLLECTION
Garbage Collection is another new feature in Visual Basic.NET. The .NET
Framework monitors allocated resources, such as objects and variables. In addition,
the .NET Framework automatically releases memory for reuse by destroying objects that
are no longer in use. In Visual Basic.NET, the garbage collector checks for the objects
that are not currently in use by applications. When the garbage collector comes across an
object that is marked for garbage collection, it releases the memory occupied by the
object.
OVERLOADING
Overloading is another feature in Visual Basic.NET. Overloading enables us to
define multiple procedures with the same name, where each procedure has a different set
of arguments. Besides using overloading for procedures, we can use it for constructors
and properties in a class.
MULTITHREADING
Visual Basic.NET also supports multithreading. An application that supports
multithreading can handle multiple tasks simultaneously, we can use multithreading to
decrease the time taken by an application to respond to user interaction. To decrease the
time taken by an application to respond to user interaction, we must ensure that a separate
thread in the application handles user interaction.
28
Tables
In relational database systems (DBS) data are represented using tables (relations).
A query issued against the DBS also results in a table. A table has the following structure:
Column 1 Column 2 . . . Column n
..
A table is uniquely identified by its name and consists of rows that contain the
stored information, each row containing exactly one tuple (or record). A table can have
one or more columns.
A column is made up of a column name and a data type, and it describes an
attribute of the tuples. The structure of a table, also called relation schema, thus is defined
by its attributes.
29
VIEWS OF TABLE:
We can work with a table in two types,
1. Design View
2. Datasheet View
Design View
To build or modify the structure of a table we work in the table design view. We
can specify what kind of data will be hold.
Datasheet View
To add, edit or analyses the data itself we work in tables datasheet view mode.
QUERY:
A query is a question that has to be asked the data. Access gathers data that
answers the question from one or more table. The data that make up the answer is either
dynast (if you edit it) or a snapshot (it cannot be edited).Each time we run query, we get
latest information in the dynast. Access either displays the dynast or snapshot for us to
view or perform an action on it, such as deleting or updating.
FORMS:
A form is used to view and edit information in the database record by record .A
form displays only the information we want to see in the way we want to see it. Forms
use the familiar controls such as textboxes and checkboxes. This makes viewing and
entering data easy.
31
Views of Form:
We can work with forms in several primarily there are two views,
They are,
1. Design View
2. Form View
Design View
To build or modify the structure of a form, we work in forms design view. We can
add control to the form that are bound to fields in a table or query, includes textboxes,
option buttons, graphs and pictures.
Form View
The form view which display the whole design of the form.
EXISTING SYSTEM
The normal existing system in the auctioning is manual system. It is a difficult
and ridiculous one to maintain them without using of online system. In the existing
system for every action, lot of records has been needed for updating.
Disadvantages in the existing system
Enormous amount of time consumption for recording all the activities, added and
updated record is very slow.
This is very much error and more complex
This system is not user friendly
35
36
Tariff master
Product master
Scrap master
Data Base
Goods Receipt Note Details
GRN supplier
Sales master
37
BED
AED
DATA BASE
SED
CESS
Product master:
Product
Product name
Unit of measurement
DATA BASE
Tariff code
38
Scrap master:
Scrap
Product name
Unit of measurement
DATA BASE
Tariff code
Supplier Name
Supplier Date
Invoice No
Tariff code
Description
Reject
Approved
Accept
39
Challan No
Challan Date
Consumed qty
Received qty
40
Name
Data type
Size( Description
Tar_Code
Varchar
30
Tariff code
Tar_Type
Varchar
30
Tariff type
Tar_Desc
text
16
Tariff description
Tar_BED
int
Tar_BED Type
Varchar
30
Tar_SED
int
Tar_SED Type
Varchar
30
Tar_AED
int
Tar_AED Type
Varchar
30
10
Tar_CESS
int
CESS
11
Tar_CESS Type
Varchar
30
CESS in % or amount
12
Tar_Status
text
16
Tariff status
13
Tar_Date
Varchar
30
Tariff date
14
Tar_userName
Varchar
30
User name
41
Product Master:
S.No
Name
Data type
Size(
Description
Pro_Code
Varchar
30
Product Code
Pro_Name
Varchar
30
Product name
Pro_Desc
Varchar
30
Product description
Pro_Tariff_Code
Varchar
30
Tariff code
Pro_Status
text
16
Product status
Pro_Date
Varchar
30
Product date
Scrap Master:
S.No
Name
Data type
Size(
Description
Scrap_Code
Varchar
30
Scrap code
Scrap_Name
Varchar
30
Scrap name
UOM
Varchar
30
Unit of measurement
Tariff_Code
Varchar
30
Tariff code
Tariff_Desc
Varchar
30
Tariff description
Opening_Stock
Varchar
30
Opening stock
Company_Name
Varchar
30
Company name
42
GRN Details:
S.No
Filed Name
Data type
Size(
Description
GRN_NO
Varchar
30
GRN number
GRN_Date
Varchar
30
GRN Date
GRN_item_code
Varchar
30
GRN code
GRN_UOM
Varchar
30
GRN_Tariff
Varchar
30
Tariff head
GRN_Received_Qty
Int
Received Qty
GRN_Rej _Qty
Int
Reject Qty
GRN_App_ Qty
Int
Approved Qty
GRN_Ret_Qty
Int
Return Qty
GRN supplier:
S.No
Name
Data type
Size(
Description
GRN_NO
Varchar
30
GRN number
GRN_Date
Varchar
30
GRN Date
3
4
GRN_type
Sup_no
Varchar
Varchar
30
30
GRN type
Supplier No
Sup_name
Varchar
30
Supplier name
Sup_DC_No
int
Supplier DC No
Sup_DC_Date
Varchar
30
Supplier DC date
Invoice_no
int
Supplier invoice No
Invoice_Date
Varchar
30
43
Sales Master:
S.No
Name
Data type
Size(
Description
Sales_ret_no
int
Sales no
Sales_ret_date
Varchar
30
Sales date
Party_code
Varchar
30
Party code
Tariff_Head
Varchar
30
Tariff code
Description
Varchar
30
Description
Prod_Code
Varchar
30
Product code
Prod_Name
Varchar
30
Product name
UOM
Varchar
30
Unit of measurement
Rate
int
Rate
10
Sales_Qty
int
Sales Qty
11
Prod_Value
int
Product value
12
Ret_ Qty
int
Return Qty
13
Shortage_
int
Shortage
14
Net_Qty
int
Net Qty
15
Total_Valid
int
Total valid
16
BED
int
17
SED
int
18
AED
int
19
CESS
int
CESS
20
Total_SR_Value
int
Total value
Modules:
Tariff Master
UOM Master
Product Master
Supplier Report
Scrap Register
Sales Register
Tariff Master:
Tariff master report displays the list of Tariff heads and corresponding percentages
available for each heads. These data are recorded through the tariff master. This is a direct
report.
UOM Master:
UOM master report displays the list of unit of measurement that is commonly
used for your business. These data are recorded through the UOM master. This is a direct
report.
Product Master:
Party master report displays the list of Party names of those who are linked to
your company for establishing business operations. These data are recorded through the
party master. This is a direct report.
Supplier Report:
Supplier master report displays the details and list of suppliers belongs to your
45
Scrap Register:
Scrap Register report display the details of accumulated stock as scrap on a given
period.
The issued quantity and closing stock are also displayed in the output. This is parameter
based report. The main parameter is date range.
Start Date: The scraps issued and accrued details on or after this starting date are listed.
Allowed input is date in the format of DD/MM/YYYY. The start date must be greater
than the financial year start date.
End Date: The scrap issued or accrued on or before this end date are listed. Allowed input
is date in the format of DD/MM/YYYY. The end date must be greater than the start
date.
meets the business and technical requirements that guided its design and
development;
Scope
A primary purpose of testing is to detect software failures so that defects may be
discovered and corrected. This is a non-trivial pursuit. Testing cannot establish that a
product functions properly under all conditions but can only establish that it does not
function properly under specific conditions. The scope of software testing often includes
examination of code as well as execution of that code in various environments and
conditions as well as examining the aspects of code: does it do what it is supposed to do
47
Unit Testing
48
System Testing
System testing of software or hardware is testing conducted on a complete,
integrated system to evaluate the system's compliance with its specified requirements.
System testing falls within the scope of black box testing, and as such, should require no
knowledge of the inner design of the code or logic.
As a rule, system testing takes, as its input, all of the "integrated" software
components that have successfully passed integration testing and also the software
system itself integrated with any applicable hardware system(s). The purpose of
integration testing is to detect any inconsistencies between the software units that are
integrated together (called assemblages) or between any of the assemblages and the
hardware. System testing is a more limited type of testing; it seeks to detect defects both
within the "inter-assemblages" and also within the system as a whole.
Acceptance Testing
49
Testing artifacts
51
Test plan
A test specification is called a test plan. The developers are well aware what test
plans will be executed and this information is made available to management and the
developers. The idea is to make them more cautious when developing their code or
making additional changes. Some companies have a higher-level document called a test
strategy.
Traceability matrix
A traceability matrix is a table that correlates requirements or design documents to
test documents. It is used to change tests when the source documents are changed, or to
verify that the test results are correct.
Test case
A test case normally consists of a unique identifier, requirement references from a
design specification, preconditions, events, a series of steps (also known as actions) to
follow, input, output, expected result, and actual result. Clinically defined a test case is an
input and an expected result. This can be as pragmatic as 'for condition x your derived
result is y', whereas other test cases described in more detail the input scenario and what
results might be expected. The optional fields are a test case ID, test step, or order of
execution number, related requirement(s), depth, test category, author, and check boxes
for whether the test is automatable and has been automated. A test case should also
contain a place for the actual result. These steps can be stored in a word processor
document, spreadsheet, database, or other common repository. In a database system, you
may also be able to see past test results, which generated the results, and what system
configuration was used to generate those results. These past results would usually be
stored in a separate table.
Test script
52
Test suite
The most common term for a collection of test cases is a test suite. The test suite
often also contains more detailed instructions or goals for each collection of test cases. It
definitely contains a section where the tester identifies the system configuration used
during testing. A group of test cases may also contain prerequisite states or steps, and
descriptions of the following tests.
Test data
In most cases, multiple sets of values or data are used to test the same
functionality of a particular feature. All the test values and changeable environmental
components are collected in separate files and stored as test data. It is also useful to
provide this data to the client and with the product or a project.
Test harness
The software, tools, samples of data input and output, and configurations are all
referred to collectively as a test harness.
Maintenance:
Software maintenance in software engineering is the modification of a software
product after delivery to correct faults, to improve performance or other attributes.
A common perception of maintenance is that it is merely fixing bugs. However,
studies and surveys over the years have indicated that the majority, over 80%, of the
maintenance effort is used for non-corrective actions (Pigosky 1997). This perception is
perpetuated by users submitting problem reports that in reality are functionality
enhancements to the system.
Software maintenance and evolution of systems was first addressed by Meir M.
Lehman in 1969. Over a period of twenty years, his research led to the formulation of
53
Tariff master:
using
using
using
using
using
System;
System.Data;
System.Configuration;
System.Collections;
System.Web;
55
System.Web.Security;
System.Web.UI;
System.Web.UI.WebControls;
System.Web.UI.WebControls.WebParts;
System.Web.UI.HtmlControls;
System.Data.SqlClient;
}
}
protected void txtRejectedQty_TextChanged(object sender, EventArgs e)
{
int App = Convert.ToInt32(txtReceiveQty.Text) Convert.ToInt32(txtRejectedQty.Text);
txtAppQty.Text = App.ToString();
}
protected void ImageButton1_Click(object sender, ImageClickEventArgs
e)
{
string Query = "insert into GRN_Detail values('" + txtGRNNo.Text
+ "','" + txtGRNDate.Text + "','" + txtGRNItemCode.Text + "','" +
txtUOM.Text + "','" + ddlTariff.SelectedItem + "','" +
txtReceiveQty.Text + "','" + txtRejectedQty.Text + "','" +
txtAppQty.Text + "','" + txtRetQty.Text + "')";
int i = _objDb.Insert(Query);
if (i != -1)
{
Response.Write("Saved Sucessfully");
}
else
{
Response.Write("Not Saved");
}
}
}
56
Product master:
using
using
using
using
using
System;
System.Data;
System.Configuration;
System.Collections;
System.Web;
57
System.Web.Security;
System.Web.UI;
System.Web.UI.WebControls;
System.Web.UI.WebControls.WebParts;
System.Web.UI.HtmlControls;
System.Data.SqlClient;
}
}
protected void ImageButton1_Click(object sender, ImageClickEventArgs
e)
Scrap master:
using
using
using
using
using
System;
System.Data;
System.Configuration;
System.Collections;
System.Web;
58
System.Web.Security;
System.Web.UI;
System.Web.UI.WebControls;
System.Web.UI.WebControls.WebParts;
System.Web.UI.HtmlControls;
System.Data.SqlClient;
59
Response.Write("Not Saved");
GRN suppliers:
using
using
using
using
using
using
using
using
using
using
using
System;
System.Data;
System.Configuration;
System.Collections;
System.Web;
System.Web.Security;
System.Web.UI;
System.Web.UI.WebControls;
System.Web.UI.WebControls.WebParts;
System.Web.UI.HtmlControls;
System.Data.SqlClient;
e)
}
protected void ImageButton1_Click(object sender, ImageClickEventArgs
{
60
System.Collections;
System.Web;
System.Web.Security;
System.Web.UI;
System.Web.UI.WebControls;
System.Web.UI.WebControls.WebParts;
System.Web.UI.HtmlControls;
System.Data.SqlClient;
e)
}
protected void ImageButton1_Click(object sender, ImageClickEventArgs
{
Sales master:
using System;
using System.Data;
61
System.Configuration;
System.Collections;
System.Web;
System.Web.Security;
System.Web.UI;
System.Web.UI.WebControls;
System.Web.UI.WebControls.WebParts;
System.Web.UI.HtmlControls;
System.Data.SqlClient;
62
TextBox16.Text = dr[3].ToString();
TextBox17.Text = dr[4].ToString();
}
}
protected void DropDownList2_SelectedIndexChanged(object sender,
EventArgs e)
{
string Query = "select Pro_Name from ProductMaster where
Pro_Code like '" + DropDownList2.SelectedItem + "'";
dr = _objDb.Select(Query);
if (dr.Read())
{
TextBox5.Text = dr[0].ToString();
}
}
protected void ImageButton1_Click(object sender, ImageClickEventArgs
e)
{
string Query = "insert into Sales values('" + TextBox1.Text +
"','" + TextBox2.Text + "','" + TextBox3.Text + "','" +
DropDownList1.SelectedItem + "','" + TextBox4.Text + "','" +
DropDownList2.SelectedItem + "','" + TextBox5.Text + "','" +
TextBox6.Text + "','" + TextBox7.Text + "','" + TextBox8.Text + "','" +
TextBox9.Text + "','" + TextBox10.Text + "','" + TextBox11.Text + "','"
+ TextBox12.Text + "','" + TextBox13.Text + "','" + TextBox14.Text +
"','" + TextBox15.Text + "','" + TextBox16.Text + "','" + TextBox17.Text
+ "','" + TextBox18.Text + "')";
int i = _objDb.Insert(Query);
if (i != -1)
{
Response.Write("Saved");
}
else
{
Response.Write("Not saved");
}
}
protected void TextBox8_TextChanged(object sender, EventArgs e)
{
int a = Convert.ToInt16(TextBox7.Text) *
Convert.ToInt16(TextBox8.Text);
TextBox9.Text = a.ToString();
}
protected void TextBox11_TextChanged(object sender, EventArgs e)
{
int b = Convert.ToInt16(TextBox10.Text) Convert.ToInt16(TextBox11.Text);
TextBox12.Text = b.ToString();
}
protected void TextBox12_TextChanged(object sender, EventArgs e)
{
}
protected void Button1_Click(object sender, EventArgs e)
{
63
using System;
using System.Data;
using System.Configuration;
64
System.Collections;
System.Web;
System.Web.Security;
System.Web.UI;
System.Web.UI.WebControls;
System.Web.UI.WebControls.WebParts;
System.Web.UI.HtmlControls;
System.Data.SqlClient;
Admin Login
65
System;
System.Data;
System.Configuration;
System.Collections;
System.Web;
System.Web.Security;
System.Web.UI;
System.Web.UI.WebControls;
System.Web.UI.WebControls.WebParts;
System.Web.UI.HtmlControls;
User Login:
66
System;
System.Data;
System.Configuration;
System.Collections;
System.Web;
System.Web.Security;
System.Web.UI;
System.Web.UI.WebControls;
System.Web.UI.WebControls.WebParts;
System.Web.UI.HtmlControls;
67
Home Page:
68
Admin Login:
69
Admin Page:
70
Tariff Mater:
71
User Login:
72
User Page:
Product Master:
73
Scrap Master:
74
GRN Details:
75
GRN Supplier:
76
77
Sales Master:
78
Tariff Master:
79
80
Product Master:
81
Scrap Master
82
GRN Details
83
84
Sales
85
86
GRN Supplier
Conclusion:
87
The project is fully menu driven one. So, any one with little knowledge of
computer can handle the software and the requirements for the user are fully completed.
The project is simple and suitably designed for end users.
BIBLIOGRAPHY
88
89
90