1.

Introduction
1.1 Introduction to project The main idea behind making an Hardware Management System for Essar Oil Ltd was mainly to provide a standard method to manage all the IT Asset of the various departments of the company. The real problem is keeping a record of more than 24 IT Assets every day and storing it in record file that contains all information of every Asset is very tedious. Handling all the requests and than giving appropriate response while keeping that response also into a record file becomes a very tedious and time consuming method. When any employee request for any Asset the admin of IT Help Desk has to search all the record file to know that whether the requested Asset is available or not. So they observed that there was a problem of keeping a track of all the Assets through a well defined effective and efficient system 1.2 Use of the project Hardware Management System is a system to maintain all the essential assets that are required by various departments in the company. Various Assets are assigned to the employees of various departments on the temporarily or permanent basis. It also supports online asset allotment which consists of features like transfer of assets within departments, return of various Assets etc. The main objective of this system is to provide a facility which allows the assigning of Asset to all Vadinar base users including admin & engineer and keeping a track of the records of various Asset Allotments. 1.3 Objectives: To provide facility which allows assigning the Asset to all Vadinar base users including admin & engineer To provide facility to transfer the assets between various users based upon their requirements. To provide facility to return the assets back to the admin when the requirement of assets is no longer needed by the users. To provide facility to update the database whenever transfer or return transaction takes place.

pg. 1

To provide facility to search for a particular asset allotted to a particular department of the company. To provide facility to either donate the asset to some charity or sale the asset after a particular period of its usage. To provide a user friendly system. It enables easy management of all above information.

1.4 Expected Outcome:In new computerized Asset Management System I have tried to give these facilities. Manually system changes into computerized system. Friendly user interface. Time saving. Save paper work. Connecting to database so we use different type of queries, data report. Formatted data.

According to technical terms, Hardware Management System will have: Secure login with encrypted password protection Unlimited number of concurrent users. Set permissions for each user (Client) to request for available Asset Manage an online account Confirmation of Assets Use for security. Maximum Asset availability

pg. 2

2. Technology Study and Literature Reviews

2.1 Front Ends .Net was developed To provide a code-execution environment that minimizes software deployment and versioning conflicts. To provide a code-execution environment that promotes safe execution of code, including code created by an unknown or semi-trusted third party. To provide a code-execution environment that eliminates the performance. To build all communication on industry standards to ensure that code based on the .NET Framework can integrate with any other code.

Fig 2.1 Net Frameworks

pg. 3

The .NET Framework has two main components: the common language runtime and the .NET Framework class library.

2.1.1 The Common Language Runtime: - (CLR) is the foundation of the .NET Framework. You can think of the runtime as an agent that manages code at execution time, providing core services such as memory management, thread management and remote, while also enforcing strict type safety and other forms of code accuracy that promote security and robustness. We are all familiar with runtimesthey go back further than DOS languages. However, the

common language runtime (CLR) is as advanced over traditional runtimes as a machine gun is over a musket. Figure 1-2 shows a quick diagrammatic summary of the major pieces of the CLR. In fact, the concept of code management is a fundamental principle of the runtime. Code that targets the runtime is known as managed code, while code that does not target the runtime is known as unmanaged code. The class library, the other main component of the .NET Framework, is a comprehensive, objectoriented collection of reusable types that you can use to develop applications ranging from traditional command-line or graphical user interface (GUI) applications to applications based on the latest innovations provided by ASP.NET, such as Web Forms and XML Web services. The .NET Framework can be hosted by unmanaged components that load the common language runtime into their processes and initiate the execution of managed code, thereby creating a software environment that can exploit both managed and unmanaged features. The .NET Framework not only provides several runtime hosts, but also supports the development of third-party runtime hosts. For example, ASP.NET hosts the runtime to provide a scalable, server-side environment for managed code. ASP.NET works directly with the runtime to enable ASP.NET applications and XML Web services, both of which are discussed later in this topic. Internet Explorer is an example of an unmanaged application that hosts the runtime (in the form of a MIME type extension). Using Internet Explorer to host the runtime enables you to embed managed components or Windows Forms controls in HTML documents.

pg. 4

2.1.1 Language Compilations in. NET

Hosting the runtime in this way makes managed mobile code (similar to Microsoft ActiveX controls) possible, but with significant improvements that only managed code can offer, such as semi-trusted execution and isolated file storage.

2.1.2. NET Framework Class Library The .Net Framework class library is a collection of reusable types that tightly integrate with the common language runtime. The class library is object oriented, providing types from which your own managed code can derive functionality. This not only makes the .NET Framework types easy to use, but also reduces the time associated with learning new features of the .NET Framework. In addition, third-party components can integrate seamlessly with classes in the .NET Framework. For example, the .NET Framework collection classes implement a set of interfaces that you can use to develop your own collection classes. Your collection classes will blend seamlessly with the classes in the .NET Framework. As you would expect from an objectoriented class library, the .NET Framework types enable you to accomplish a range of common programming tasks, including tasks such as string management, data collection, database connectivity, and file access. In addition to these common tasks, the class library includes types that support a variety of specialized development scenarios.

pg. 5

NET Class Libraries

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

Console applications. Windows GUI applications (Windows Forms). ASP.NET applications. XML Web services. For example, the Windows Forms classes are a comprehensive set of reusable

types that vastly simplify Windows GUI development. If you write an ASP.NET Web Form application, you can use the Web Forms classes.

2.1.3 Features of Asp.Net

1. Data Controls: - Data access in ASP.NET 2.0 can be accomplished completely

declaratively (no code) using the new data-bound and data source controls. There are new data source controls to represent different data back ends such as SQL database, business objects, and XML, and there are new data-bound controls for rendering common UI for data, such as grid view, details view, and form view.

pg. 6

2. Navigation Controls: - Navigation controls provide common UI for navigating between

pages in your site, such as tree view, menu, and sitemap path. These controls use the site navigation service in ASP.NET 2.0 to retrieve the custom structure you have defined for your site.

3. Login Controls:-The new login controls provide the building blocks to add
authentication and authorization-based UI to your site, such as login forms, create user forms, password retrieval, and custom UI for logged in users or roles. These controls use the built-in membership and role services in ASP.NET 2.0 to interact with the user and role information defined for your site.

4. Web Part Controls: - Web parts are an exciting new family of controls that enable you
to add rich, personalized content and layout to your site, as well as the ability to edit that content and layout direct from your application pages. These controls rely on the personalization services in ASP.NET 2.0 to provide a unique experience for each user in your application.

5. Master Pages: - This feature provides the ability to define common structure and
interface elements for your site, such as a page header, footer, or navigation bar, in a common location called a "master page", to be shared by many pages in your site. In one simple place you can control the look, feel, and much of functionality for an entire Web site. This improves the maintainability of your site and avoids unnecessary duplication of code for shared site structure or behavior.

6. Themes and Skins: - The themes and skins features in ASP.NET 2.0 allow for easy
customization of your site's look-and-feel. You can define style information in a common location called a "theme", and apply that style information globally to pages or controls in your site. Master Pages improves the maintainability of your site and avoid unnecessary duplication of code for shared styles.

7. Personalization: - Using the new personalization services in ASP.NET 2.0 you can
easily create customized experiences within Web applications. The Profile object enables developers to easily build strongly-typed, sticky data stores for user accounts and build highly customized, relationship based experiences. At the same time, a developer can leverage Web Parts and the personalization service to enable Website visitors to completely control the layout and behavior of the site, with the knowledge

pg. 7

that the site is completely customized for them. Personalization scenarios are now easier to build than ever before and require significantly less code and effort to implement.

8. Localization: - Enabling globalization and localization in Web sites today is difficult,

requiring large amounts of custom code and resources.ASP.NET 2.0 and Visual Studio 2005 provide tools and infrastructure to easily build Localizable sites including the ability to auto-detect incoming locale's and display the appropriate locale based UI. Visual Studio 2008 includes built-in tools to dynamically generate resource files and localization references. Together, building localized applications becomes a simple and integrated part of the development experience. HTML: - HTML stands for Hyper Text Markup Language. HTML is based on SGML (Standard Generalized Markup Language), a much bigger document-processing system. To write HTML pages, you won't need to know a whole lot about SGML, but it does help to know that you of the main features of SGML are that it describes the general structure of the content inside documents, not that content's actual appearance on the page or on the screen. HTML defines a set of common styles for Web pages: headings, paragraphs, lists, and tables. It also defines character styles such as boldface and code examples. Each element has a name and is contained in what's called a tag. When you write a Web page in HTML, you label the different elements of your page with these tags that say "this is a heading" or "this is a list item." It's like if you were working for a newspaper or a magazine where you do the writing but someone else does the layout; you might explain to the layout person that this line is the title, this line is a figure caption, or this line is a heading. It's the same way with HTML.

CSS: - CSS (cascading style sheets), style sheets when attached to documents describe how the document is displayed or printed e.g. a CSS sheet is attached to an HTML document, to influence its layout when accessed via a browser. CSS supports cascading, i.e. a single document may use two or more style sheets that are then applied according to specified priorities. CSS is a specification for the presentation of HTML marked documents. CSS work like a template, allowing web developers to define style for an HTML element and they apply it to as many web pages they would like. With CSS, when you want to make a change, you simply change the

pg. 8

style, and that element is updated automatically whenever it appears within the site. Both Navigator 4.0 and Internet Explorer 6.0 support cascading style sheets. What is CSS? CSS stands for Cascading Style Sheets. Styles define how to display HTML elements. Styles are normally stored in style sheets. External Style Sheets can save you a lot of work. Multiple style definitions will cascade into one.

2.2 Back End - Microsoft SQL Server 2005 SQL Server 2005 provides vast range of new features and a lot of improvements, which SQL Server 2000 aspirants were always looking for. With SQL Server 2005, users and information technology (IT) professionals across your organization will benefit from reduced application downtime, increased scalability and performance, and tight yet flexible security controls. SQL Server 2005 also includes many new and improved capabilities to help make your IT staff more productive.

Manageability: - SQL Server 2005 makes it simpler and easier to deploy, manage, and
optimize enterprise data and analytical applications. As an enterprise data management platform, it provides a single management console that enables data administrators anywhere in your organization to monitor, manage, and tune all of the databases and associated services across your enterprise. It provides an extensible management infrastructure that can be easily programmed using SQL Management Objects, enabling users to customize and extend their management environment and independent software vendors (ISVs) to build additional tools and functionality to further extend the capabilities that come out of the box.

Fast Recovery: - SQL Server 2005 improves the availability of SQL Server databases
with a new and faster recovery option. Users can reconnect to a recovering database after the transaction log has been rolled forward. Earlier versions of SQL Server required users

pg. 9

to wait until incomplete transactions had rolled back, even if the users did not need to access the affected parts of the database. Replication: - Replication is designed to increase data availability by distributing the data across multiple database servers. Availability is increased by allowing applications to scale out the SQL Server read workload across databases. SQL Server 2005 offers enhanced replication using a new peer-to-peer model that provides a new topology in which databases can be synchronized transitionally with any identical peer database.

Scalability: - Scalability advancements such as table partitioning, snapshot isolation and

64-bit support will enable you to build and deploy your most demanding applications using SQL Server 2005. The partitioning of large tables and indexes significantly enhances query performance against very large databases. Table and Index Partitioning: - Table and index partitioning eases the management of large databases by facilitating the management of the database in smaller, more manageable chunks. While the concept of partitioning data across tables, databases, and servers is not new to the world of databases, SQL Server 2005 provides a new capability for the partitioning of tables across file groups in a database. Horizontal partitioning allows for the division of a table into smaller groupings based on a partitioning scheme. Table partitioning is designed for very large databases, from hundreds of gigabytes to terabytes and beyond. Security: - SQL Server 2005 makes significant enhancements to the security model of the database platform, with the intention of providing more precise and flexible control to enable tighter security of the data. A considerable investment has been made in a number of features to provide a high level of security for your enterprise data including the following: Enforcing policies for SQL Server login passwords in the authentication space. Providing for more granularities in terms of specifying permissions at various scopes in the authorization space.

pg. 10

 Allowing for the separation of owners and schemas in the security management Space. Authorization: - A new security model in SQL Server 2005 allows administrators to manage permissions at a granular level and at a designated scope, making management of permissions easier as well as ensuring that the principle of least privileges is upheld. SQL Server 2005 lets you specify a context under which statements in a module execute. This feature also acts as an excellent mechanism for granular permission management. Authentication: - SQL Server 2005 clustering supports Kerberos authentication against a SQL Server 2005 virtual server. Administrators can specify Microsoft Windows-style policies on standard logins so that a consistent policy is applied across all accounts in the domain. Expanded Language Support: - Because the common language runtime (CLR) is hosted in the database engine, developers can choose from a variety of familiar languages to develop database applications, including Transact-SQL, Microsoft Visual Basic .NET, and Microsoft Visual C# .NET. Additionally, CLR hosting provides developers with increased flexibility with user-defined types and functions. The CLR also provides opportunities to use non-Microsoft code for rapid database application development. XML Support: - Advancements such as the native XML data type and XQuery help organizations seamlessly connect internal and external systems. SQL Server 2005 supports both relational and XML data natively, so enterprises can store, manage, and analyze data in the format that best suits their needs. Support for existing and emerging open standards such as Hypertext Transfer Protocol (HTTP), XML, Simple Object Access Protocol (SOAP), XQuery, and XML Schema definition language (XSD) also facilitate communication across extended enterprise systems. 2.2.1 Microsoft Visio The Visio Professional drawing helps us to efficiently design and document information systems and business processes. With Visio Professional, we can

pg. 11

Design and diagram networks. Plan and map intranet and World Wide Web sites. Describe and re-engineer business processes. Map and create databases. Model software systems and design interface elements, and more.

In addition to solutions, templates, stencils, shapes and wizards, Visio Professional includes features common to all Visio products that make it the program of choice for visualizing and communicating ideas. Those features include: Easy-to-use drag and drop drawing. Smart Shapes technologyshapes programmed to behave the way we expect. Compatibility and consistency with Microsoft Windows XP, Windows NT 4.0, and Office 2003. A quick and easy process for publishing drawings as Web pages. A built-in development tool, Visual Basic for Applications (VBA) that we can use to customize the Visio interface and create custom solutions.

pg. 12

3. Analysis and Design

3.1 System Analysis: Hardware Requirements Client Configuration Server Configuration Software Requirements Hardware Requirements Client Configuration o Pentium IV, 750 MHz, 20GB HDD o Operating System : Windows XP/NT o RAM :128MB minimum o 1 GB Minimum Free Space on Drive Server Configuration o Intel Pentium IV processor or its equivalent o Operating System: Win XP / NT o RAM : 1024 MB Minimum o 10 GB Minimum Free Space on Drive o 750MHz Software Requirements Development Requirements o Web Application and Services : ASP.Net, VB.NET, AJAX, HTML, JavaScript o Development Tool o Database Server o Operating System o Package : Visual Studio 2005 (Framework 2.0) : SQL Server 2005 : Windows XP : Office XP

pg. 13

Roles and Responsibilities There are two types of users who are dealing with the system. Admin Engineer

Figure 3.1 Main Module

pg. 14

3.2 Analysis and Design Diagrams Use Case Diagram

Figure 3.2

pg. 15

Sequence Diagram

Figure- 3.2

pg. 16

Collaboration Diagram

Figure- 3.2

pg. 17

Activity Diagram

pg. 18

Figure- 3.2

pg. 19

System Flow Chart

Figure- 3.2

pg. 20

Structure Chart

pg. 21

3.3 Data Dictionary Sr.No 1 2 3 4 Table Name Desktop_LaptopMaster Mouse_KeyboardMaster Server_Storage Master Blackberry_DataCard_Entrust Table Description Store Desktop, Laptop Inventory Details Store Mouse, Keyboard Inventory Details Store Server,Storage Inventory Details Store Blackberry,DataCard,Entrust Inventory Details Store Monitor Inventory Details Store other Assets Inventory Details Store Transaction Details Store Delete information of asset Store AMS Engineer detail Store populate data used to bound dropdown, list box etc at runtime. Store all usersDetails

5 6 7 8 9 10 11

Monitor_Master Asset_Master Movement_Master Delete_Master Engineer_Details Helps User_Details

Table Name : Desktop_LaptopMaster Table Description : Store Desktop, Laptop Inventory Details Field Name TagNo EntryDate CPUSrno CPUPrNo LaptopBatteryNo LaptopChargeNo AssetCompany AssetType Givenby Make Model WarrantyDateFrom WarrantyDateTo PONumber RAM HDD ProcessorType Data Type varchar datetime varchar varchar Varchar Varchar varchar Varchar Varchar varchar Varchar datetime datetime Varchar varchar varchar Varchar Size 10 30 30 30 30 30 30 30 10 20 30 10 10 20 Constraints Primary Key Not null Allow null Allow null Allow null Allow null Not null Not null Not null Not null Not null Not null Not null Not null Not null Not null Not null Description Unique Asset no Asset Entry Date CPU serial no CPU Product no Laptop battery no Requester Asset company Asset Type Requester name Asset Makecompany name Asset Model Warranty start date Warranty end date Product Order No Ram Hard disk Processor Type

pg. 22

SAPAssetNo CurrentUser Status Remark

Varchar Varchar Varchar Varchar

30 30 50 50

Not null Not null Not null Allow null

SAPAssetNo AssetUser AssetStatus Remarks

Table Name : Mouse_KeyboardMaster Table Description : Store Mouse, Keyboard Inventory Details Field Name SerialNo EntryDate AssetCompany AssetType GivenBy Make Model SAPAssetNo WarrantyDateFrom WarrantyDateTo PONumber CurrentUser Status Remark Data Type Varchar datetime Varchar Varchar Varchar Varchar Varchar Varchar datetime datetime Varchar Varchar Varchar Varchar Size 10 30 20 30 10 20 30 Constraints Primary Key Not null Not null Not Null Not null Not null Not null Not null Not null Not null Not null Not null Not null Allow null Description UniqueSerialNo Transaction Date AssetCompany AssetType RequesterName AssetMake AssetModel SAPAssetNo StartDate EndingDate Product Order No. Current User Status Remark

20 20 50 30

Table Name : Server_Master Table Description : Store Server Storage Inventory Details Field Name TagNo EntryDate AssetCompany AssetType GivenBy Make Type WarrantyDateFrom WarrantyDateTo SAPAssetNo Data Type Varchar datetime Varchar Varchar Varchar Varchar Varchar datetime datetime Varchar Size 10 30 20 30 10 15 Constraints Primary Key Not null Not null Not null Not null Not null Not null Not null Not null Not null Description UniqueAssetNo EntryDate AssetCompany AssetType RequesterName AssetMake AssetType Starting Date Ending Date SAPAssetNo

20

pg. 23

PONumber SerialNo PIDNo IPAddress Application ServerName RackNo ProcessorType NoOfProcessor

Varchar Varchar Varchar Nchar Varchar Varchar Varchar Varchar numeric(3, 0) RAM Varchar HDD Varchar NoOfHdd Numeric Os Varchar SecurityHardeningStatus Varchar SymantecBSRStatus Varchar CurrentUser Varchar Status Varchar Remark Varchar

20 20 10 15 30 30 10 15 3 10 10 3 10 10 5 20 50 30

Not null Not null Not null Not null Not null Not null Not null Not null Not null Not null Not null Not null Not null Not null Not null Not null Not null Allow null

PONumber SerialNo PIDNo IPAddress Application ServerName Rack No ProcessorType NoOfProcessor RAM HDD NoOfHDD OS Status BSRStatus CurrentUser Status Remark

Table Name : Blackberry_DataCard_Entrust Table Description : Store Blackberry, DataCard, Entrust Inventory Details Field Name Rid SerialNo TagNo PO_No AssetType GivenBy Make Model WarrantyDateFrom WarrantyDateTo PONumber SAPAssetNo IMEINo PINNo BTMAC MobNo BNNo ZFGNo Data Type Numeric Varchar Varchar Varchar Varchar Varchar Varchar Varchar Datetime Datetime Varchar varchar numeric Numeric Varchar Numeric Varchar Varchar Size 18 50 50 50 20 30 30 30 Constraints Primary Key Not null Null Not null Not null Not null Not null Not null Not null Not null Not null Not null Allow null Allow null Allow null Allow null Allow null Allow null Description UniqueRecordNo. SerialNo. TagNo. AssetCompany AssetType RequesterName AssetMake AssetModel Starting Date Ending Date ProductOrderNo SAPAssetNo. IMEINo PINNo BTMAC MobNo BNNo ZFGNo

20 30 18 18 30 13 20 20

pg. 24

DocketNo CurrentUser Status Remark

Varchar Varchar Varchar Varchar

15 20 50 30

Allow null Not null Not null Allow null

DocketNo Current User Status Remark

Table Name : Monitor_Master Table Description : Store Monitor Inventory Details Field Name TagNo EntryDate AssetCompany AssetType GivenBy Make Model WarrantyDateFrom WarrantyDateTo PONumber SerialNo ProductNo SAPAssetNo CurrentUser Status Remark Data Type Varchar Datetime Varchar Varchar Varchar Varchar Varchar datetime datetime Varchar Varchar Varchar Varchar Varchar Varchar Varchar Size 10 30 20 30 10 20 Constraints Primary Key Not null Not null Not null Not null Not null Not null Not null Not null Not null Not null Not null Not null Not null Not null Allow null Description Unique Asset No. EntryDate AssetCompany AssetType RequesterName AssetMake AssetModel Starting Date Ending Date PONumber SerialNo ProductNo SAPAssetNo Current User Status Remark

20 20 20 30 20 50 30

Table Name : Engineer Detail Table Description : Store Engineer Detail Details Field Name EmployeeID EmployeeCode EmployeeName MailID MobileNo Department ExtensionNo Location Data Type Varchar Varchar Varchar Varchar Varchar Varchar Varchar Varchar Size 50 50 50 50 15 50 50 50 Constraints Not null Not null Not null Not null Not null Not null Not null Not null Description EmployeeID EmployeeCode EmployeeName` MailID MobileNo Department ExtensionNo Location

pg. 25

SubLocation Shift Rights Status Type

Varchar Varchar Varchar Varchar Varchar

50 50 50 10 10

Not null Not null Not null Not null Not null

SubLocation Shifts Rights Status Type

Table Name : Helps Table Description : Store populate data used to bound dropdown, list box etc at Runtime. Field Name Data Type Size Constraints Description RID lNames fldNames fldText fldValues ProjId Numeric Varchar Varchar Varchar Varchar Varchar 5 250 250 250 250 250 Unique Key Not null Not null Not null Not null Not null Record No List Name Field Name fieldText fieldValues ProjectID

Table Name : UserDetail Table Description : Store all usersDetails Field Name RID UserID UserType Rights Data Type Numeric Varchar Varchar Varchar Size 5 200 50 50 Constraints Unique Key Not null Not null Not null Description Record No User ID User Type Rights

3.4 Pseudo Code (Structured English) Pseudo code is a compact and informal high-level description of a computer programming algorithm that uses the structural conventions of a programming language, but is intended for human reading rather than machine reading. Pseudo code typically omits details that are not essential for human understanding of the algorithm, such as variable declarations, systemspecific code.

pg. 26

1) LOGIN
1. IF LoginId is authenticated in Active Directory THEN 2. IF userid is EQUAL UserID of UserDetailMaster a. IF UserID=ADMIN THEN i. Allow to view Menu-Asset Entry, Inventory, Engineer Setting, ii. EditHelps, Reports b. ENDIF c. IF UserID=ENGINEER THEN i. Allow to view Menu-Asset Entry, Inventory d. ENDIF 3. ENDIF 4. ELSE 5. Message->Please Enter OUTLOOK userid, Password 6. ENDIF

2) ASSET ASSIGN
1. Select Asset 2. Enter Tag no 3. Select Choice for assigning asset a. IF Choice EQUAL Temporary THEN i. Enter Start date and End date b. ENDIF

4. Click Confirm after gathering Asset for assign 5. Enter User Code a. IF User Code not Available THEN i. Enter User name b. ENDIF 6. Click->Assign

pg. 27

3) RETURN
1. IF Enter User Id THEN 2. Display all Assets which are assigning to that user a. 3. ENDIF 4. IF Enter Tag no THEN a. Display detail of that asset only - (Tag no, Make, Model, User Id, Location etc.) 5. ENDIF 6. Click->Return (Tag no, Make, Model)

4) TRANSFER
1. Select Asset 2. Enter Tag no 3. IF Click-> Replace THEN a. Enter new Tag no 4. ENDIF 5. Click->Submit 6. IF Click ->Transfer THEN a. Enter new employee Id b. IF employee Id not available THEN i. Enter employee name c. ENDIF d. Select Choice for transferring asset e. IF Choice EQUAL Temporary THEN i. Enter Start date and End date f. ENDIF 7. ENDIF 8. Click->Submit

pg. 28

Referential Integrity Referential integrity is a database concept that ensures that relationships between tables remain consistent. When one table has a foreign key to another table, the concept of referential integrity states that you may not add a record to the table that contains the foreign key unless there is a corresponding record in the linked table. It also includes the techniques known as cascading update and cascading delete, which ensure that changes made to the linked table are reflected in the primary table. Referential integrity prevents inconsistent data from being created in the database by ensuring that any data shared between tables remains consistent. To put it another way, it ensures that the soundness of the relationships remains intact. The following table includes the important elements of Referential Integrity: Term Definition A table, where the referential constraints are defined. A child table is synonymous with the referencing table. The table being referenced by a Child table. A Parent table is synonymous with the referenced table. A primary key uniquely identifies a row of a table. A foreign key refers to columns in the Child table. A foreign key may consist of up to 16 columns. Referencing columns are within a referencing table that are foreign keys for columns in some other referenced table. Referenced column are defined as either primary key columns or unique columns in a referenced table.

Child Table

Parent Table

Primary Key

Foreign Key

Referencing columns Referenced columns

pg. 29

4. Implementation and Results

4.1 Appendix or Variables Use Meaningful, descriptive words to name variables. Variable names shall describe their use, shall be in mixed case with an initial upper

case character for each word, and shall have 'Hungarian' prefixes that describe their type and scope. Use Camel Casing: First character of all words, except the first word is Upper Case and other characters are lower case. Variables shall be explicitly declared. For VB use Option Explicit at the top of all modules. Variables shall have a focused use. They shall not be declared once and used for several different purposes. Global variables must be declared in a code module. Local variables shall be declared at the top of a procedure. Meaning for variable Connection DataAdapter Dataset Report Grid view Array List Active Directory Data Table Data Row

Class name SqlConnection SqlDataAdapter Dataset ReportDocument GridView ArrayList LDAPClassLibrary.ESSAR.srActiveDirectory DataTable DataRow

Variable con da dset report gd ar ADL dt dr

Functions:

Function Name/Class Name

Private Function GetConnection()

Task
Open SQL connection

pg. 30

Partial Class Assign Partial Class EditHelps Partial Class Tag_Generation Partial Class Return Partial Class EngineerSetting

Assign Asset to the Requester Add new Item at Run time Create new Tag Return Add Engineer , change rights

Control Names Control Label Textbox Button ListBox DropDownList Radio Button Panel Gridview CrystalReportViewer Menu Prefix lbl txt btn lst dd rd panel gd crv Menu Example lblSelectAsset txtEcode btnSubmit lstRights ddLocation rdChoiceforReport Panel1 gdAssetDetail crvReport1 Menu1

pg. 31

4.2 Screen Shots

1. Login Page:-

This is a login page which allows user authentication. User will only be able to log into the VadHelpdesk system only if he is authenticated. Otherwise error message Login Failed will be displayed.

pg. 32

2. Main Page

The asset is assigned to the user by entering its employee code which calls the web service.

pg. 33

3. Assign Asset

After the user is selected all the previous assets that belongs to the user is displayed in the form of grid view.

pg. 34

4. New Asset Assign

On click of Assign New Asset the various textbox are shown that are to be filled by the admin such as asset name, assign type, etc.

pg. 35

5. Return of Asset

While returning the asset back from user to the admin the information is to be filled so that necessary database can be updated.

pg. 36

6. Transfer of Asset

We can directly transfer the asset from one user to another user and the necessary database is directly updated while selecting the transfer button.

pg. 37

7. Update Asset Information

Asset may problem so while solving it may possible its value to be changed hence an update existing asset value is designed to facilitate this service.

pg. 38

8. Search of Asset

A particular asset values can be found by search asset option which reveals all the details regarding that asset.

pg. 39

4.3 Testing
Test Plan Generally, it has been specified thought for the Testing that: Testing is the critical element of any software quality assurance & represents the ultimate review of specification, design & code generation. Software Testing has a dual function; it is used to establish the presence of defects in program and it is used to help judge whether or not the program is usable in practice. Thus software testing is used for validation and verification, which ensure that software conforms to its specification and meets the need of the software customer. Developer resorted Alpha testing, which usually comes in after the basic design of the program has been completed. The project leader will look over the program and give suggestions and ideas to improve or to correct the design. They also report and give ideas to get rid of around any major problems. There is bound to be a number of bugs after a program have been created.

Software Inspection Analyze and check system representations such as the requirements document, design diagrams and the program source code. They may be applied at all stages of the process. Regardless of which strategies the analysts follow, there are preferred practices to ensure that the testing is useful. The levels of tests and types of test data, combined with testing libraries are important aspects of test process. Among the various testing practices or strategies that are followed by analysts, the two important ones are unit testing and system testing. Software testing is crucial step in determining whether a software application is viable, ready for market and free of bugs. No software will be completely free of glitches but through software testing can and will make sure that it is as error free as humanly possible.

pg. 40

Unit Testing Module Testing Sub-system Testing

System Testing Acceptance Testing

Test Strategy The test strategy consists of a series of different tests that will fully exercise the AMS@ Vadinar on Intranet. The primary purpose of these tests is to uncover the systems limitations and measure its full capabilities. A list of the various planned tests and a brief explanation follow below. Unit Testing In each of this, functionality is tested rigorously. Functionality like Rights Settings, Generation of Different Reports, Exporting Different Reports in Excel Sheet, Adding & Editing the data for various Forms. This all functionality is tested individually and independently under unit testing. Integration Testing In this take the unit-tested component, build the program that has been dictated by design test a specific feature. E.g. changing the rights of engineer, accordingly he is able to access the different menus in system. Regression Testing

pg. 41

Each time a new module is added as part of integration testing, the software changes. New data flow paths are established, new I/O may occur and new control logic is invoked. It is the re-execution of some forms that are tested to ensure that changes have not propagated unintended side effects. Acceptance Testing This type of testing is done when the system is being deployed. The testing data are supplied by the system procurer. The acceptance testing was carried out in the company in the Essar Oil Limited itself. If they think it capable and only after a series of systematic testing the system will be ready to use by the company. Control Testing Control is a management tool to that processing is performed in accordance to what management desire or intents of management. The objectives of doing so are accurate and complete data. Software Testing Involves executing an implementation of the software with test data and examining the outputs of the software and its operational behavior to check that it is performing as required. Statistical Testing Used to test the programs performance and reliability and to check how to works under operational conditions. Tests are designed to reflect the actual user inputs and their frequency. The stages involved in the static analysis for this system are follows. Control flow analysis Unreachable code Unconditional branches into loops Data use analysis Variable used before initialization

pg. 42

Variable declared but never used Variable assigned twice but never used between assignments Possible array bound violations Declare variables Interface analysis Parameter type mismatches Non-usage of results of functions Uncalled function and procedures

Defect Testing Intended to find inconsistencies between a program and its specification. inconsistencies are usually due to program faults or defects. Structural Testing We have done path testing to exercise every independent execution path through a component or program. If every independent path is executed then all statements in the components must have been executed at least once. We checked graphics module and database access module, which have independent execution path. They are not related to each other. The structure of our program is also checked. Performance Testing Performance testing is designed to test the runtime performance of the system within the context of the system. These tests were performed as module level as well as system level. Individual modules were tested for required performance. In Performance testing we counted the processing time and response from the server with respect to request. We also checked out the total-execution time. On the click of the mouse we get the result. Condition Testing Coding testing is a test case design method that exercises the logical conditions in a program module .If the condition is incorrect then at least one component of the condition is incorrect. These

pg. 43

 This test will test the appearance of various forms and user interface. Various Levels for Testing: Field Level Check weather hot keys are defined for that item for key board navigation Testing. Check for all the validation as mentioned in the program specifications. Check for boundary condition, if apply. Check for field for format mask. Checking for possibility of under or overflow for every variable/expression. Check the calculated field with 3-4 different values or combination of values. Check whether the inserted record reaches the destination table. Check weather all the fields are stored properly if filled with maximum possible characters. Form Level Check each and every integrity constraints. Check for inter module table updates Query Level

First execute the query without defining any criteria. This should fetch all the transaction of base table. Program Level Understandability: Program should not contain cryptic codes and cryptic data names. Comments used should he simple and precise.

Readability: The code should have proper indentation. There should be blank line at the end of a logical block of code. Too many condition or statements should not be placed on in one line.

Maintainability: Comments should be present at the beginning of every logical block of code. And comments should to describe logic.

pg. 44

4.4 Test Cases and Test Results The purpose of the test cases is to test the various input and see the output produce any error or not. There are different test cases according to the system. It is tested with different types of value like single value multiple value and see it can generate expected output.

Valid Input

SYSTEM

Valid output

[Figure Test Cases Block Diagram] 1. Login Process

Test Case Number Name Description

1 Valid User Test This test will check whether user ID and Password valid or not. If not then it will not allow the user to use Helpdesk system. 1) Valid ID and Password which is already defined. 2) Valid ID but wrong Password 3) Wrong ID wrong password

Input Data

Expected Output

1) System allow login 2) System prompts error message that user is not valid. 3) System prompts error message that user is not valid.

Actual Output Test Status:

System allow login PASS

pg. 45

2. Asset Entry Process Test Case Number Name Description Input Data Expected Output 2 Insertion of new asset details. (Unique Tag No) This test will check whether the Tag no is unique or no and in proper format. Fill the various field of selected asset. 1) Field must not be blank 2) Tag no must unique and in proper format like -Desktop DT30002 -Laptop LT30005 3) Data should be added in database Data Add in Database PASS

Actual Output Test Status:

3.

Modifying Asset Process 3 Edit the details selected Asset. Tag no which want to Modified. Data should be edited in database Data edited Pass

Test Case Number Description Input Data Expected Output Actual Output Pass / Fail?

4. Delete Asset Process Test Case Number Description Input Data Expected Output Actual Output Pass / Fail? 4 Delete selected asset as per selected choice- Scrap, Sale, Donation Tag no which want to Deleted. Status should be change in database. Status change. Pass

pg. 46

5. Assign Asset Process

Test Case Number Description Input Data Expected Output Actual Output Pass / Fail?

5 Asset assign as per employee request. Enter employee Id or Name. Employee information added into database and status change of Asset in database. Employee information added into database and status change of Asset in database. Pass

6. Return Asset Process Test Case Number Description Input Data Expected Output Actual Output Pass / Fail? 6 Asset return as per employee request. Enter employee Id or Name. Status change of Asset in database. Status change of Asset in database. Pass

7.

Replacement Process 7 Asset replaced as per employee request. Enter new Tag no. Status change of Asset in database. Status change of Asset in database. Pass

Test Case Number Description Input Data Expected Output Actual Output Pass / Fail?

pg. 47

8. Transfer Asset Process Test Case Number Description Input Data Expected Output Actual Output Pass / Fail? 8 Asset transfer as per employee request. Enter employee Id or Name. Employee information added into database and Status change of Asset in database. Employee information added into database and Status change of Asset in database. Pass

9. Search Asset Process 9 Test Case Number This test will check whether the search asset result is correct based Description on the selected criteria. Search results found should displayed correctly in grid based on Expected the selected criteria. Output Search results found is displayed correctly in grid based on the Actual Output selected criteria. Pass Pass / Fail?

pg. 48

5. Conclusion
Hardware Management System is a system to maintain all the essential assets that are required in the company. Various Assets are assigned to the employee of various departments on the temporarily or permanent basis. It also supports online asset allotment which consists of features like update, transfer, return of various Assets etc.

New computerized Hardware Management System gives these facilities. Manually system changes into computerized system. Friendly user interface. Time saving. Save paper work. Connecting to database so we use different type of queries, data report. Give facility of different type of inquiry. Formatted data.

According to Technical terms, Hardware Management System provides these facilities: Secure login with encrypted password protection Unlimited number of concurrent users. Set permissions for each user (Client) to request for available Asset Manage an online account Confirmation of Assets Use for security. Maximum Asset availability

Limitations: The Grid View which has been used to display all the assets belonging to particular Employee in this project is the pirated one and has been downloaded from internet. Deactivate entries of Asset were also shown in grid along with the active one. On click of button the dropdown menu was moving along the page thus problem in designing

pg. 49

6. References
BOOKS:

ASP.NET 2.0 Unleashed By Stephen Walther ASP.NET 2.0 in VB 2005 by Mathew Macdonald and Mario Szpuszta Complete Reference ix Crystal Report By George E Peck Professional Vb.Net2005 by Mathew Macdonald Roger S. Pressman, Software Engineering: A Practitioners approach, McGrawHill, Fifth Edition Visual Basic .Net Programming Black Book by Steven Holzner

WEBSITES:

http://www.w3schools.com/ http://www.aspalliance.com http://www.dotnetspider.com/ http://www.freevbcode.com/ http://www.dotnetheaven.com/ http://www.1keydata.com/sql/

pg. 50

pg. 51