Inventory Management System Project Report 1v65s

tag—if you don‘t, the HtmlInputFile control won‘t work. Declaring the File control is easy. It doesn‘t expose any new properties or events that you can use through the control tag.

C# example :protected void btn_Click(Object sender, System.EventArgs e) {_ String path = @‖C:\temp\‖ + File1.FileName; File1.PostedFile.SaveAs(path); }

Some few other quirks of the File control that are good to know: ●

You can check the size of the ed file using the PostedFile. ContentLength property. This lets you put a size limit on s. Just don‘t call the SaveAs method if the file exceeds the maximum length.

●

The ASP.NET must have access rights to the location to which you save the file. Galgotias Institute Of Management & Technology, Gr. Noida | Project Report

58

INVENTORY MANAGEMENT SYSTEM

●

Master of Computer Applications

The SaveAs method isn‘t what copies the file from the ‘s computer to the server. Instead, the file is copied to the server when the posts the page by clicking the button. The SaveAs method merely directs the File control to save the file that has been copied to the server. If you don‘t call the SaveAs method, the ed file is discarded.

Galgotias Institute Of Management & Technology, Gr. Noida | Project Report

59




60



MASTER PAGE A Master Pageis simply a template — a page that provides elements that appear consistently on each page, as well as contentplaceholdersthat specify where the variable content for each page should appear. A page that actually holds the content that a Master Page displays in its content area is called acontent page. The ContentPlaceHolder is a portion of the page where the content page can insert content. We can use a master page to ensure that every web page in your application has the same header, footer, and navigation controls. Master pages are an ASP.NET feature that‘s designed specifically for standardizing web-page layout.

Master Page Basics


61



●

To provide a practical, flexible solution for page templating, a number of requirements must be met:

●

The ability to define a portion of a page separately and reuse it on multiple pages.

●

The ability to create a locked-in layout that defines editable regions. Pages that reuse this template are then constrained to adding or modifying content in the allowed regions.

●

The ability to allow some customization of the elements you reuse on each page.

●

The ability to bind a page to a page template declaratively (with no code) or to bind to a page dynamically at runtime.

●

The ability to design a page that uses a page template with a tool such as Visual Studio. Master pages meet all of these requirements.

How to create a Master Page ? To create a master page in Visual Studio, select Website. Add New Item from the menu. Select Master Page, give it a filename (such as SiteTemplate.master), and click Add. A master page is similar to an ordinary ASP.NET web form. Like a web form, the master page can include HTML, web controls, and code (either in an inline script block or in a separate file). One difference is that while web forms start with the Page directive, a master page starts with a Master directive that specifies the same information, as shown here:

<%@ Master Language="C#" AutoEventWireup="true" CodeFile="SiteTemplate.master.cs" Inherits="SiteTemplate" %>

Another difference between master pages and ordinary web forms is that master pages can use the ContentPlaceHolder control, which isn‘t allowed in ordinary pages. The ContentPlaceHolder is a portion of the page where the content page can insert content.

Creating a content pages Galgotias Institute Of Management & Technology, Gr. Noida | Project Report

62



There are two ways to create a content page:

●

Use the Website➪Add New Item command, select Web Page as the template, check the Select Master Page option, and then choose the Master Page you want the content page applied to.

●

Select a Master Page either in the Solution Explorer or the Web Designer window, then choose the Website➪Add Content Page command.

When we create a content page in this manner, initially the page contains just the following markup: <%@ Page Language=‖C#‖ MasterPageFile=‖~/MasterPage.master‖ AutoEventWireup=‖true

CodeFile=‖Default.aspx.cs‖Inherits=‖_Default‖

Title=‖Untitled Page‖ %>


63




64



WEB CONFIG Web.config acts as a central location for storing the information to be accessed by web pages. This information could be a Connection String stored at a centralized location so that it can be accessed in a data-driven page. If the connection string changes it‘s just a matter of changing it at one place. In classic ASP such global information was typically stored as an application variable. In the sample we'll read the information from web.config using ASP.NET and ASP as there could be a possibility of project having ASP and ASP.NET pages.

What is Web.ConfigFile ?

Web.config file, as it sounds like is a

configuration file

for the Asp .net web

application. An Asp .net application has one web.config file which keeps the configurations required for the corresponding application. Web.config file is written in XML with specific tags having specific meanings.


65



What is Machine.configFile ? As web.config file is used to configure one asp.net web application, same way Machine.config file is used to configure the application according to a particular machine. That is, configuration done in machine.config file is affected on any application that runs on a particular machine. Usually, this file is not altered and only web.config is used which configuring applications.

What can be stored in Web.config file ? There are number of important settings that can be stored in the configuration file. Here are some of the most frequently used configurations, stored conveniently inside Web.config file..

●

1.

Database connections

2.

Session States

3.

Error Handling

4.

Security

Database Connections : The most important configuration data that can be stored inside the web.config file is the database connection string. Storing the connection string in the web.config file makes sense, since any modifications to the database configurations can be maintained at a single location. As otherwise we'll have to keep it either as a class level variable in all the associated source files or probably keep it in another class as a public static variable. But it this is stored in the Web.config file, it can be read and used anywhere in the program. This will certainly save us a lot of alteration in different files where we used the old connection.

●

Session States :


66



Session in Asp .net web application is very important. As we know that HTTP is a stateless protocol and we need session to keep the state alive. Asp .net stores the sessions in different ways. By default the session is stored in the asp .net process. ●

Error Handling : Error handling is one of the most important part of any web application. Each error has to be caught and suitable action has to be taken to resolve that problem. Asp.net web.config file lets us configure, what to do when an error occurs in our application.

●

Security : The most critical aspect of any application is the security. Asp.net offers many different types of security method which can be used depending upon the condition and type of security you need.

1.) No Authentication: No Authentication means "No Authentication" :) , meaning that Asp.net will not implement any type of security.

2.) Windows Authentication: The Windows authentication allows us to use the windows s. This provider uses

IIS to perform the actual authentication, and then es the authenticated identity to your code. If we like to see that what windows is using the Asp.net application we can use: .Identity.Name; This returns theDOMAIN\Nameof the current of the local machine.

3.) port Authentication: port Authentication provider uses Microsoft's port service to authenticate s. You need to purchase this service in order to use it.


67



4.) Forms Authentication: Forms Authentication uses HTML forms to collect the information and than it takes required actions on those HTML collected values.

web.config: Contains a key-value pair. web.config


68




69



ADO.NET ADO.NET consists of managed classes that allow .NET applications to connect to data sources (usually relational databases), execute commands, and manage disconnected data.

The ADO.NET Architecture ADO.NET uses a multilayered architecture that revolves around a few key concepts, such as Connection, Command, and DataSet objects.

1. ADO.NET Data Providers A data provideris a set of ADO.NET classes that allows you to access a specific database, execute SQL commands, and retrieve data. Essentially, a data provider is a bridge between your application and a data source.

The classes that make up a data provider include the following : ●

Connection: You use this object to establish a connection to a data source.

●

Command: You use this object to execute SQL commands and stored procedures.

●

DataReader: This object provides fast read-only, forward-only access to the data retrieved from a query.

●

DataAdapter: This object performs two tasks. First, you can use it to fill a DataSet (a disconnected collection of tables and relationships) with information extracted from a datasource.Second, you can use it to apply changes to a data source, according to the modifications


70



The .NET Framework is bundled with a small set of four providers: ●

SQL Server provider: Provides optimized access to a SQL Server database (version 7.0 or later).

●

OLE DB provider: Provides access to any data source that has an OLE DB driver. This includes SQL Server databases prior to version 7.0.

●

Oracle provider: Provides optimized access to an Oracle database (version 8i or later).

●

ODBC provider: Provides access to any data source that has an ODBC driver.

The ADO.NET Namespaces 1. System.Data :

Contains the key data container classes that model columns, relations,

tables, datasets, rows, views, and constraints. In addition,contains the key interfaces that are implemented by the connection based data objects.

2. System.Data.Common: Contains base, mostly abstract classes that implement some of the interfaces from System.Data and define the core ADO.NET functionality. Data providers inherit from these classes (such as DbConnection, DbCommand, and so on) to create their own Specialized versions.

3. System.Data.OleDb :Contains the classes used to connect to an OLE DB provider, Including OleDbCommand, OleDbConnection, OleDbDataReader and OleDbDataAdapter. These classes most OLE DB providers,but not those that require OLE DB version 2.5 interfaces.


71



4. System.Data.SqlClient : Contains the classes you use to connect to a Microsoft SQL Server database, including SqlDbCommand, SqlDbConnection, SqlDataReader, and SqlDBDataAdapter. These classes are Optimized to use the TDS interface to SQL Server. 5. System.Data.OracleClient : database

including

Contains the classes required to connect to an Oracle

OracleCommand,

OracleConnection,

OracleDataReader,

and

OracleDataAdapter. These classes are using the optimized Oracle Call Interface (OCI).

6. System.Data.Odbc: Contains the classes required to connect to most ODBC drivers.These classes include OdbcCommand, OdbcConnection, OdbcDataReader, and OdbcDataAdapter. ODBC drivers are included for all kinds of data sources and are configured through the Data Sources icon in the Control .

7. System.Data.SqlTypes : Contains structures that match the native data types in SQL Server.These classes aren‘t required but provide an alternative to using standard .NET data types, which require automatic conversion.

The Connection Class The Connection class allow us to establish a connection to the data source that you want to interact with. Before you can do anything else (including retrieving, deleting, inserting, or updating data), you need to establish a connection. When we create a Connection object, we need to supply a connection string. The connection string is a series of name/value settings separated by semicolons (;).

The Command and DataReader Classes The Command class allow us to execute any type of SQL statement. Although we can use a Command class to perform data definitiontasks (such as creating and altering databases, tables,and indexes), we‘re much more likely to perform data manipulationtasks (such as retrieving and updating the records in a table).The provider-specific Command classes Galgotias Institute Of Management & Technology, Gr. Noida | Project Report

72



implement standard functionality, just like the Connection classes. In this case, the IDbCommand interface defines a few key properties and the core set of methods that are used to execute a command over an open connection.

Command Basics Before we can use a command, we need to choose the command type, set the command text, and bind the command to a connection. We can perform this work by setting the corresponding properties (CommandType, CommandText, and Connection), or we can the information we need as constructor arguments.

Method Description 1. ExecuteNonQuery() Executes non-SELECT commands, such as SQL commands that insert, delete, or update records. The returned value indicates the number of rows affected by the command. You can also use ExecuteNonQuery() to execute data-definition commands that create, alter, or delete database objects (such as tables, indexes, constraints, and so on).

2. ExecuteScalar() Executes a SELECT query and returns the value of the first field of the first row from the rowset generated by the command. This method is usually used when executing an aggregate SELECT command that uses functions such as COUNT() or SUM() to calculate a single value.

3. ExecuteReader() Executes a SELECT query and returns a DataReader object that wraps a read-only, forward-only cursor.


73



The DataReader Class A DataReader allow us to read the data returned by a SELECT command one record at a time, in a forward-only, read-only stream. This is sometimes called a firehose cursor. Using a DataReader is the simplest way to get to your data, but it lacks the sorting and relational abilities of the disconnected DataSet.

Method Description 1. Read() Advances the row cursor to the next row in the stream. This method must also be called before reading the first row of data. (When the DataReader is first created, the row cursor is positioned just before the first row.) The Read() method returns true if there‘s another row to be read, or false if it‘s on the last row.

2. GetValue() Returns the value stored in the field with the specified index, within the currently selected row. The type of the returned value is the closest .NET match to the native value stored in the data source. If you access the field by index and inadvertently an invalid index that refers to a nonexistent field, you will get an IndexOutOfRangeException exception.

3. GetValues() Saves the values of the current row into an array. The number of fields that are saved depends on the size of the array you to this method. You can use the DataReader.FieldCount property to determine the number of fields in a row, and you can use that information to create an array of the right size if you want to save all the fields.

4. NextResult() If the command that generated the DataReader returned more than one rowset, this method moves the pointer to the next rowset (just before the first row).


74



5. Close() Closes the reader. If the originator command ran a stored procedure that returned an output value, that value can be read only from the respective parameter after the reader has been closed.

The DataAdapter Class To extract records from a database and use them to fill a table in a DataSet, we need to use another ADO.NET object : a DataAdapter. The DataAdapter comes in a provider-specific object, so there is a separate DataAdapter class for each provider (such as SqlDataAdapter, OracleDataAdapter, and so on).

The DataAdapter serves as a bridge between a single DataTable in the DataSet and the data source. It contains all the available commands for querying and updating the data source. To enable the DataAdapter to edit, delete, and add rows, you need to specify Command objects for the UpdateCommand, DeleteCommand, and InsertCommand properties of the DataAdapter. To use the DataAdapter to fill a DataSet, you must set the SelectCommand. .

Method Description 1. Fill() Adds a DataTable to a DataSet by executing the query in the SelectCommand. If our query returns multiple result sets, this method will add multiple DataTable objects at once. You can also use this method to add data to an existing DataTable.

2. FillSchema() Adds a DataTable to a DataSet by executing the query in the SelectCommand and retrieving schema information only. This method doesn‘t add any data to the DataTable. Instead, it simply preconfigures the DataTable with detailed information about column names, data types, primary keys, and unique constraints.


75



3. Update() Examines all the changes in a single DataTable and applies this batch of changes to the data source by executing the appropriate InsertCommand, UpdateCommand, and DeleteCommand operations.


76




77



Testing Testing is the major control measure used during software development. Its basic function is to detect errors in the software. During requirement analysis and design, the output is a document that is usually textual and no executable. After the coding phase, computer programs are available that can be executed for testing purpose. This implies that testing not only has to uncover errors introduced during coding, but also errors introduced during previous phase. Thus the goal of testing is to uncover the requirements, design and coding errors in the programs.

Objectives of testing First of all objectives should be clear. 

Testing as a process of executing a program with the intent of finding errors.



To perform testing, test cases are designed. A test case is a particular made up of artificial situation upon which a program is exposed so as to find errors. So a good test case is one that finds undiscovered errors.



If testing is done properly, it uncovers errors and after fixing those errors we have software that is being developed according to specifications.

The above objective implies a dramatic change in viewpoint .The move counter to the commonly held view than a successful test is one in which no errors are found. In fact, our objective is to design tests that a systematically uncover different classes of errors and do so with a minimum amount of time and effort.


78



Testing principles Before applying methods to design effective test cases, software engineer must understand the basic principles that guide the software testing process. Some of the most commonly followed principles are: All test should be traceable to requirements as the objective of testing is to uncover errors, it follows that the most severe defects (from the s point of view) are those that causes the program to fail to meet its requirements.

Tests should be planned long before the testing begins. Test planning can begin as soon as the requirement model is complete. Detailed definition of test cases can begin as soon as the design model has been solidated. Therefore, all tests can be planned and designed before any code can be generated.

The Pareto principle applies to software testing stated simply the Pareto principle implies that 80 percent of all errors uncovered during testing will likely be traceable to 20 percent of all program modules. The problem of course, is to isolate these suspects‘ modules and to thoroughly test them. Testing should begin ―in the small‖ and progress towards testing ―in large‖. The first tests planned and executed generally focus on individual modules. As testing progresses, testing shifts focus in an attempt to find errors in integrated clusters of modules and ultimately in the entire system. Exhaustive testing is not possible. The number of paths permutations for impossible to execute every combination of paths during testing. It is possible however to adequately cover program logic and to ensure that all conditions in the procedural design have been exercised. To be most effective, an independent third party should conduct testing. By ―most effective‖, we mean testing that has the highest probability of finding errors (the primary objective of testing).


79



Test information flow Testing is a complete process. For testing we need two types of inputs: ●

Software configuration It includes software requirement specification, design specification and source code of program. Software configuration is required so that testers know what is to be expected and tested.

●

Test configuration It is basically test plan and procedure. Test configuration is testing plan that is, the way how the testing will be conducted on the system. It specifies the test cases and their expected value. It also specifies if any tools for testing are to be used. Test cases are required to know what specific situations need to be tested. When tests are evaluated, test results are compared with actual results and if there is some error, then debugging is done to correct the error. Testing is a way to know about quality and reliability. Error rate that is the occurrence of errors is evaluated. This data can be used to predict the occurrence of errors in future.

A software product can be tested in two ways :-

In first approach, only overall functioning of the product is tested. Inputs are given and outputs are checked. This approach is called black box testing. It does not care about the internal functioning of the product.

The other approach is called white box testing. Here the internal functioning of the product is tested. Each procedure is tested for its accuracy. It is more intensive than black box testing. But for the overall product both these techniques are crucial. There should be sufficient number of tests in both categories to test the overall product.


80



Basic methods of Testing White box testing White box testing is performed to reveal problems with the internal structure of a program. This requires the tester to have detailed knowledge of the internal structure. A common goal of white box testing is to ensure a test case exercises every path through a program. A fundamental strength that all white box strategies share is that the entire software implementation is taken into during testing, which facilitates error detection even when software specification is vague or incomplete. The effectiveness or thoroughness of white box testing is commonly expressed in of test or code coverage metrics, which measure the fraction of code exercised by test cases.

Basic Path Testing It is a white box technique. It was proposed by Tom McCabe. These tests guarantee to execute every statement in the program at least one time during testing. Basic set is the set of all execution paths of a procedure.

Black Box Testing Black box tests are performed to access how well a program meets its requirements, looking for incorrect or missing functionality. Functional tests typically exercise code with valid or nearly valid input for which the expected output is known. This includes concepts such as ‗boundary values‘.

Performance tests evaluate response time, memory usage, throughput, device utilization and execution time. Stress tests push the system to or beyond its specified limits to evaluate its


81



robustness and error handling capabilities. Reliability tests monitor system response to representative input, counting failures over time to measure or certify reliability.

Black box testing uncovers the following types of errors 4. Incorrect or missing functions 5. Interface errors 6. External database access 7. Performance errors 8. Initialization and termination errors

What is a Black Box Testing Strategy? Black Box Testing is not a type of testing; it instead is a testing strategy, which does not need any knowledge of internal design or code etc. As the name "black box" suggests, no knowledge of internal logic or code structure is required. The types of testing under this strategy are totally based/focused on the testing for requirements and functionality of the work product/software application. Black box testing is sometimes also called as "Opaque Testing", "Functional/Behavioral Testing" and "Closed Box Testing".

The base of the Black box testing strategy lies in the selection of appropriate data as per functionality and testing it against the functional specifications in order to check for normal and abnormal behavior of the system. Now a days, it is becoming common to route the Testing work to a third party as the developer of the system knows too much of the internal logic and coding of the system, which makes it unfit to test the application by the developer. In order to implement Black Box Testing Strategy, the tester is needed to be thorough with the requirement specifications of the system and as a , should know, how the system should behave in response to the particular action.


82



Various testing types that fall under the Black Box Testing strategy are: functional testing, stress testing, recovery testing, volume testing, Acceptance Testing (also known as UAT), system testing, Sanity or Smoke testing, load testing, Usability testing, Exploratory testing, ad-hoc testing, alpha testing, beta testing etc.

These testing types are again divided in two groups: a) Testing in which plays a role of tester b) is not required.

Testing method where is not required:-

Functional Testing :In this type of testing, the software is tested for the functional requirements. The tests are written in order to check if the application behaves as expected.

Stress Testing :The application is tested against heavy load such as complex numerical values, large number of inputs, large number of queries etc. which checks for the stress/load the applications can withstand.

Load Testing :The application is tested against heavy loads or inputs such as testing of web sites in order to find out at what point the web-site/application fails or at what point its performance degrades.


83



Ad-hoc Testing :This type of testing is done without any formal Test Plan or Test Case creation. Ad-hoc testing helps in deciding the scope and duration of the various other testing and it also helps testers in learning the application prior starting with any other testing.

Exploratory Testing :This testing is similar to the ad-hoc testing and is done in order to learn/explore the application.

Usability Testing :This testing is also called as ‗Testing for -Friendliness‘. This testing is done if Interface of the application stands an important consideration and needs to be specific for the specific type of .

Smoke Testing :This type of testing is also called sanity testing and is done in order to check if the application is ready for further major testing and is working properly without failing up to least expected level.

Recovery Testing :Recovery testing is basically done in order to check how fast and better the application can recover against any type of crash or hardware failure etc. Type or extent of recovery is specified in the requirement specifications.

Volume Testing :Volume testing is done against the efficiency of the application. Huge amount of data is processed through the application (which is being tested) in order to check the extreme limitations of the system.


84



Testing where plays a role/ is required:

Acceptance Testing :In this type of testing, the software is handed over to the in order to find out if the software meets the expectations and works as it is expected to.

Alpha Testing :In this type of testing, the s are invited at the development center where they use the application and the developers note every particular input or action carried out by the . Any type of abnormal behavior of the system is noted and rectified by the developers.

Beta Testing :In this type of testing, the software is distributed as a beta version to the s and s test the application at their sites. As the s explore the software, in case if any exception/defect occurs that is reported to the developers.

Advantages of Black Box Testing ●

More effective on larger units of code than glass box testing

●

Tester needs no knowledge of implementation, including specific programming languages

●

Tester and programmer are independent of each other

●

tests are done from a 's point of view

●

will help to expose any ambiguities or inconsistencies in the specifications

●

test cases can be designed as soon as the specifications are complete


85



Disadvantages of Black Box Testing  Only a small number of possible inputs can actually be tested, to test every possible input stream would take nearly forever  Without clear and concise specifications, test cases are hard to design  There may be unnecessary repetition of test inputs if the tester is not informed of test cases the programmer has already tried  May leave many program paths untested  Cannot be directed toward specific segments of code which may be very complex (and therefore more error prone)

Test cases We know, test cases are integral part of testing. So we need to know more about test cases and how these test cases are designed. The most desired or obvious expectation from the test cases is that it should be able to find most errors with the least amount of time and effort.

Test Case for Block Brand – Open Product Brand Master from Left Menu under Forms

Test case Test Objective Test Procedure ID

Test Data

Expected Results

Brand_1 To Check all Mandatory Fields

Click Submit Button without entering data.

1.Without enter any brand code. 2. Without enter any brand name.

Message “Enter brand ed name” and “enter brand code”

Brand_2 To Submit Block

Enter character values in Brand Category code and submit.

1. HCL 2. #$$$$

“Date Inserted Successfully.”

ed/ Failed

ed

“Must insert character value


86

Comment s

Change duplicate category message “Already exist”



Test case Test Objective Test Procedure ID

Test Data

Expected Results

Brand_3 To check Block Submitted or not

All data will be Visible.

All records are visible ed in below window

Click on View/Modify in Block link

ed/ Failed

Comment s

Test Case for Product Category Master Village– Open Village from Left Menu under Masters Test case Test Objective Test Procedure ID

Test Data

Expected Results

ed/ Failed

Category To Check all Click Submit _1 Mandatory Button without Fields entering data.

1.Without enter Product Category code, Product Category Name, and Parent Category Name.

Message “Please enter Product Category Code, Product Category Name.

ed

“Date Inserted Successfully.”

ed

Category To Submit _2 Category

Enter mandatory Product Category Fields and press Code : LPT, submit button Product Category Name : Laptop


87

Comment s




88



CONCLUSION The goals accomplished in deg/developing of this system:

Friendliness The system has totally -friendly in sense as only has to interact with GUI pages and almost everywhere whenever any kind of task is going to perform.

Duplicate As data is entered in different modules so consideration is made so No duplicate entry exists in the system.

Menu Driven The system is made totally menu driven for the best results.

Query To see all the information regarding a single Report, a Report view page has been provided.

Security A high level security at different levels has been incorporated into the system on the basis of requirements.

Fast As far as possible slow responses are avoided and, thus, the system is fast enough.

Future Plans The development of modules are made such that can trace back and update the error entry.


89



MERITS OF THE PROJECT The project is identified by the merits of the system offered to the . The merits of this project are as follows:  This project offers to enter the data through simple & interactive web-page. This is very helpful for the client to enter the desired information through so much simplicity.  The is mainly more concerned about the validity of the data, whatever he is entering. There are checks in every stage of any new creation, data entry or updating. So that the cannot enter the invalid data, which can cause problems further?  Sometimes the find in the later stages of using the project that he need to update some of those information that he entered earlier. There are options for him by which he can update the records. Moreover there is restriction for him that he cannot change the primary

data

field. This keeps the validity of the data to longer extent.  is provided the option of monitoring the records he entered earlier He can see the desired records with the variety of options provided for him.  From every part of the project the is provided with the links through framing so that he can go from one option of the project to other one as per as desire and requirement. This is bound to be simple and very friendly as per the is concerned. That is, we can say that the project is friendly which is one of the primary concerns of any good project.  Data storage and Retrieval will become faster and easier to maintain because data is stored in a systematic manner and in a single database.  Decision making process would be greatly enhanced because of faster processing of information since data collection from information available on computer takes much less time then manual system.  Through these features it will increase the efficiency, accuracy and transparency.


90



LIMITATION OF THE PROJECT As nothing is perfect in this world, we also not claim that our software is perfect. As all other, our project also has some limitations. Those limitations are as follows – 

Due to the requirements of the of the data of not only of current year but also of last few years, the size of the database becomes too bulky. Due to which the processing speed of any request from the client becomes a little bit slow.



Since this is the On-Line Project, if the network will be down or not.



Working properly, then report will not be submitted or accepted. To overcome this problem, the report will be submitted through soft copies (Floppies, CD etc.) or written documents.

SCOPE OF FUTURE APPLICATION The objective of this application is to present the secure graphical interface much friendly to the authorized only, performing all the working of above mentioned procedure efficiently.It is aimed at making department affairs getting rid off all the bottlenecks that are there in the manual system and enabling them to focus on the core activities of the istration, thus helping them strengthen the overall quality standards.

Further Enhancement This is the pilot project, if needed, can be further modified according to requirement.


91




92



REFERENCES TEXT REFERENCES 1. Pro ASP.NET 3.5 in C# 2008, Second Edition by Matthew MacDonald and Mario Szpuszta,Apress. 2. Oreilly.Learning.Web.Design.3rd.Edition.Jun.2007. 3. Sams Asp Net 3.5 Unleashed Jun 2006 4. Wrox.Professional.ADO.dot.NET.2.Programming.with.SQL.Server.2005.Oracle.and.MySQ L.Dec.2005.eBook. 5. Addison Wesley - The Gurus Guide to Transact SQL

WEB REFERENCES

1. www.w3schools.com 2. http://msdn.microsoft.com/enus/library/system.web.httpcontext.session.aspx 3. www.dotnetspider.com 4. http://www.edrawsoft.com/Flowchart-tutorial.php 5. http://www.codeproject.com/KB/database/DatabaseWithAd oNet1.aspx 6. http://quickstarts.asp.net/QuickStartv20/aspnet/doc/pages/pages. aspx 7. http://www.bigresource.com/MS_SQL-data-bindingd4UHaJPz.html 8. http://www.sql-server-performance.com 9. http://www.sgsy.in


93




94




95



Purpose If you wants to avail all the facilities of Inventory Management System properly, you need to be ed through this Page and then you will be authorised of this site Innventory Management System. This registration process requires your basic knowledge such as Name, and Organisation etc.

Snapshot View This shows the page view for authorised s of Inventory Management System. Here you can to your if you are already ed. This will provide you with a name and .

is failed when the credentials are not entered correctly.


96



DESCRIPTION OF PAGE control of asp.net: 

This control forms authentication, an ASP.NET model for authenticating s against a database and tracking their status. Rather than writing your own interfaces to work with forms authentication, you can use these controls to get pre built, customizable pages, recovery, and -creation wizards.



When we open the project the first page opened will be page where we enter the credentials of name and . When the entries are entered correctly the page will be redirected to default.aspx page. Otherwise error will be displayed on the screen.


97




98



PRODUCT BRAND :This is the first page of Inventory Management System (product Brand master). The page is concerned with the following functionalities :(1) There are two input values on the on the form.  Brand Category Code (For entering the brand code).  Brand Category Name (For entering the name of the brand). (2) There is a Submit Button on the form.  For submitting the input values. (3) There is a Grid view on the form.



The Grid view show all input values on the form randomly after pressing the Submit Button.


99




100



PRODUCT CATEGORY :The second page of Inventory Management System (Add product Category).The page is concerned with the following functionalities :(1) There are two textboxes on the form : Product Category Code (For entering the product category code).  Product Category Name (For entering the name of the product category). (2) There is dropdown list on the form : Parent Category Name (For selecting the parent category of the product) (4) There is a Submit Button on the form.  Submit Button ( For submitting the input value) (3) There is a Grid view on the form.  Grid view (For showing all input values on the form randomly after pressing the Submit Button)


101




102



PRODUCT :The third page of Inventory Management System (Add product).The page is concerned with the following functionalities :(1) There are three textboxes on the form : Product Name (For entering the product name)  Product Detail (For entering the product detail)  Purchase date (For entering the purchase date of product)  Serial Number (For entering the serial number of product)  Search 1,2 (For searching the product) (2) There are three dropdown lists on the form : Brand Name (For selecting the brand of the product)  Category Name(For selecting the category of the product)  Office (For selecting the particular where to transfer the product) (3) There is a search textbox on the form There is a Submit Button on the form : Submit Button ( For submitting the input value) (4) There is a Grid view on the form : Grid view (For showing all input values on the form randomly after pressing the Submit Button)

Continue….


103




104




105



Product Issue & Receive :The third page of Inventory Management System (Active product in stock).The page is concerned with the following functionalities :(1) There is a Grid view on the form : Grid view (Grid view showing all the active products of company) (2) There are Check Boxes on the Grid View of the form : Check Boxes (Check Boxes for selecting the ready to use products from the list of the products, after selecting the particular row the product is transfer to Product Form) (3) There is a Submit Button on the form : Submit Button ( For submitting selecting check box values to Product Form)


106




107



Purpose This module provides you the facility to View all data entries :-


108

Inventory Management System Project Report 1v65s

Overview 3e4r5l

More details w3441

Related Documents 3m3m1z

Inventory Management System Project Report 1v65s

Project Report Inventory Management y6j5s

Hospital Management System Project Report 2z2m5e

Event Management System Project Report 5n2i6f

Leave Management System Project Report 9429

Library Management System Project Report 2d2d4

More Documents from "Alankar Sharma" 5d4r63

Inventory Management System Project Report 1v65s

The Congress Party System - Rajni Kothari 2i5p2j

Cite Hr Mgr Hr Jd 6b3z1u

Advt For Consultants Dypt And Contract Jalswarajya Ii 535j1p

Oct 2014 145b17

Hwidgen Activator.txt 4e61