Table of Contents

5,229 views
5,090 views

Published on

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
5,229
On SlideShare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
39
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Table of Contents

  1. 1. PROJECT REPORT ON ENTERPRISE ASSET MANAGEMENT SYSTEM FOR DEPARTMENT OF INFORMATION TECHNOLOGY NEW DELHI-110011 SUBMITTED IN PARTIAL FULFILLMENT OF THE REQUIREMENT FOR AWARD OF THE DEGREE MASTER OF COMPUTER APPLICATION OF U.P TECHNICAL UNIVERSITY, LUCKNOW SESSION: 2004-2007 UNDER THE GUIDANCE OF Ms. Rakhi Sharma Mr. C.S. Jairath Head of Department Senior Technical Director Department of Computer Application NIC, C.G.O.Complex R.C.C.V Girls Degree College New Delhi Ghaziabad SUBMITTED BY Priyanka Bhatt th 6 Semester M.C.A DEPARTMENT OF COMPUTER APPLICATIONS R.C.C.V GIRLS DEGREE COLLEGE GHAZIABAD-201003 Affiliated To U.P Technical University, Lucknow
  2. 2. GOVERNMENT OF INDIA MINISTRY OF COMMUNICATIONS & INFORMATION TECHNOLOGY DEPARTMENT OF INFORMATION TECHNOLOGY National Informatics Centre This is to certify that Miss. Priyanka Bhatt ID.N0 9153 a student of Master of Computer Applications (M.C.A) from R.C.C.V Girls Degree College, Ghaziabad /U.P Technical Univ., Lucknow has done his full-semester project training at NIC-DIT Division, NIC, New Delhi, from 9thFeb, 2007 to 9thJune, 2007. The project work entitled “ Enterprise Asset Management System ( Technical Store )” embodies the original work done by Priyanka Bhatt during her above full semester project training period. Project Guide/HOD Head, Training Division 2
  3. 3. R.C.C.V Girls Degree College Department of Computer Applications Ghaziabad, U.P-201003 CERTIFICATE This is to certify that Miss. Priyanka Bhatt, a student of 6th semester, Master of Computer Application, R.C.C.V Girls Degree College, Ghaziabad has carried out the project on “Enterprise Asset Management System” for Technical Store, Department of Information and Technology, New Delhi. This project work has been prepared as a fulfillment of the requirement for the degree of Master of Computer Applications (M.C.A) to be awarded by U.P Technical University, Lucknow. This work has not been presented earlier for any other academic activity. I wish her all success in life. (Rakhi Sharma) HOD Department of Computer Applications R.C.C.V Girls Degree College Ghaziabad 3
  4. 4. Declarations I do, hereby, declare that the Project work entitled “Enterprise Asset Management System (Technical Store)” is an authentic work developed by me at NIC-DIT Division, Electronics Niketan, New Delhi, under the guidance of Mr. Niraj Goswami (SA) and Mrs. Rakhi Sharma (HOD) and submitted as a partial fulfillment of the degree of M.C.A of U.P Technical University, Lucknow. I also declare that, any or all contents incorporated in this report have not been submitted in any form for the award of any degree or diploma of any other institution or university. Priyanka Bhatt 6th semester, M.C.A R.C.C.V Girls Degree College Ghaziabad 4
  5. 5. Acknowledgement I take this opportunity to express my profound sense of gratitude and respect to all those who helped me throughout the duration of this project. I express my sincere gratitude and thankfulness towards Ms. Rakhi Sharma, Department of Computer Applications, of R.C.C.V Girls Degree College, Ghaziabad for her valuable time and guidance throughout the M.C.A. I feel privileged to offer my sincere thanks and deep sense of gratitude to Mrs. Rachna Srivastava (Technical Director), Training Division, NIC Headquarters and Mr. C. S. Jairath (Senior Technical Director) and Mr. Niraj Goswami (‘SA’) at NIC-DIT, C.G.O. Complex, New Delhi, for expressing their confidence in me by letting me work on a project of this magnitude and using latest technologies and providing their support, help & encouragement in completing this project. I am grateful for the co-operation & valuable suggestions rendered by all the staff members of the NIC-DIT, C.G.O.Complex, New Delhi. I am grateful to all our friends for providing critical feedback & support whenever required. I regret any inadvertent omissions. Priyanka Bhatt R.C.C.V Girls Degree College 6th semester, M.C.A Ghaziabad 5
  6. 6. Abstract ProjectTitle: Enterprise Asset Management System Technical Store, DIT developed in C#.Net. Abstract: Module assigned: Requisition/Issue/SMG Module The project has been developed to fulfill the requirements of the Technical Store of Department of Information Technology. This system provide the online access to DIT’s employee by which they can apply for the issue of the hardware items like pendrive,printer,laptop,scanner etc. . Every part has been done online. With the help of this system DIT’s employee can apply for the item according to their requirement. Each application will be sent to their concerned authority and then it will sanction after checked the record of the employee. After getting sanctioned from authority the employee gets their item from their concerned authority. They can apply for the hardware items like (printer, pen drive, laptop, and keyboard). As we know that our records information is traditionally paper based; they are maintained on paper. And because of that paper based record authority face lots of problem and if record will misplaced then humble of problem has been occurred. So this inventory control system will make the work of authorities bit easy. The Enterprise management System includes the primary data such as employee code and employee name to which the item is provided. The system requires only a few information about the user, which also can be easily submit by the employee and rest of the work is self generated by the system. 6
  7. 7. Tools & Technologies used: • C#.Net • Sql Server 2000 • HTML • ASP.Net • Java Script • Microsoft Windows XP Keywords: C#.Net, Sql Server 2000, HTML, ASP.Net. NIC Division: NIC-DIT. 7
  8. 8. Table of Contents Contents Page NO. 1.About NIC 9-10 2.About Ministry of Communication and information 11 Technology 3.Project Overview 12-16 3.1 Introduction to Enterprise Asset Management System 3.2. Problem Statement 3.3 Project Description 3.4 Component Assigned 4.Technology Used 17-27 4.1 System Architecture: 4.2 Hardware 4.3 Software 4.4 Software Description 5.System Study and Analysis 28-33 5.1 Existing System 5.2 Proposed System 5.2.1 Objective of proposed system 5.2.2 Advantages of the proposed system 5.2.3 Scope of the proposed system 5.3 Feasibility Study 5.3.1 Economic Feasibility 5.3.2 Technical Feasibility 5.3.3 Behavioral Feasibility 6.SRS 34-50 7.Design of the Component 51-89 7.1 Functional Decomposition Diagram(FDD) 7.2 DFD 7.3 Entity Relationship Diagram 7.5 Database Design 7.6 Physical Design(Physical files and their description) 8.Conclusion 90 9.Bibliography 91 8
  9. 9. 1. About NIC National Informatics Centre (NIC) of the Department of Information Technology is providing network backbone and e-Governance support to Central Government, State Governments, UT Administrations, Districts and other Government bodies. It offers a wide range of ICT services including Nationwide Communication Network for decentralized planning, improvement in Government services and wider transparency of national and local Governments. NIC assists in implementing Information Technology Projects, in close collaboration with Central and State Governments, in the areas of (a) Centrally sponsored schemes and Central sector schemes, (b) State sector and State sponsored projects, and (c) District Administration sponsored projects. NIC endeavors to ensure that the latest technology in all areas of IT is available to its users. NIC Headquarters is based in New Delhi. At NIC Headquarters, a large number of Application Divisions exist which provide total Informatics Support to the Ministries and Departments of the Central Government. NIC computer cells are located in almost all the Ministry Bhawans of the Central Government and Apex Offices including the Prime Minister’s Office, the Rashtrapati Bhawan and the Parliament House. Apart from this, NIC has various Resource Divisions at the Headquarters which specialize into different areas of IT and facilitate the Application Divisions as well as other NIC Centers in providing state-of-the-art services to the Govt. At the State level, NICs State/UTs Units provide informatics support to their respective State Government and at the District level lie the NIC District Informatics Offices. NIC has conceptualized, developed and implemented a very large number of projects for various Central and State Government Ministries, Departments and Organizations. Many of these projects are continuing projects being carried out by various divisions of NIC at New Delhi Headquarters and State/District centers throughout the country. Some of the most important note worthy projects, which offer a glimpse of the multifaceted, diverse activities of NIC, touching upon all spheres of 9
  10. 10. e-governance and thereby influencing the lives of millions of citizens of India is given below: Agricultural Marketing Information Network (AGMARKNET) Central Passport System Community Information Centers (CICs) Computerized Rural Information Systems Project (CRISP) Court Information System (COURTIS) Department of Agriculture Network (DACNET) Examination Results Portal India Image Land Records Information System (LRIS) National Hazardous Waste Information System (NHWIS) Public Grievance Redress and Monitoring System (PGRAMS) Spatial Data Infrastructure (SDI) Training Video Conferencing Web Site of NIC http://indiaimage.nic.in/ 10
  11. 11. 2. About Ministry of Communication and Information Technology:- The Ministry of Communication and Information Technology, through the mass communication media consisting of radio, television, films, the press, publications, advertising and traditional mode of dance and drama plays a significant part in helping the people to have access to free flow of information. It also caters to the dissemination of knowledge and entertainment to all sections of society, striking a careful balance between public interest and commercial needs, in its delivery of services. Ministry of Information & Broadcasting is the apex body for formulation and administration of the rules and regulations and laws relating to information, broadcasting, the press and films. This Ministry is responsible for international co- operation in the field of mass media, films and broadcasting and interacts with its foreign counterparts on behalf of Government of India. 11
  12. 12. 3. Project Overview 3.1 Introduction to Enterprise Asset Management System Enterprise Asset Management system is the system for the DIT. The Authority of the Technical store of the DIT will be used this system for the better performance of the work. This system will provide the online facilities for the employees of the DIT and also for the Administrator. Features of the systems are:- • Online request form for the issue of items (Printer/laptop/Scanner). • Issue of the items (Printer/laptop/Scanner). • Employees can check their application (request) status. • Generation of the Inventory Item issue report. 3.2. Problem Statement The problem definition for the system is to launching the online system for the inventory of Technical store of NIC-DIT at C.G.O. Complex, New Delhi. The objective of the project is to setting up of an on-line enquiry system about the status of the availability of the hardware items (Printer/laptop/Scanner) along with the facility to apply online and also to automate the issuing procedure. 12
  13. 13. 3.3 Project Description Managing the entire applying request for the Hardware items (Printer, desktp, mouse, pendrive) at the Technical store of Department of Information Technology (DIT) at C.G.O. Complex, New Delhi. The retrieval of the status of various request at various times is technically a cumbersome process and not very desirable. The user i.e. the employee who wants to apply the item must complete all the formalities which are a very time consuming process. Also maintaining all the records of the details on paper or traditional diaries is incompatible with this age of machines and computers. It is proposed that a software system "Enterprise Asset Management System for Technical store (DIT)" may be developed to nurture the needs of an individual employee so that he can easily access to the system and check for availability of the items and also apply while sitting at his office. This software is also developed to nurture the needs of the management of the Technical store for managing the details of the request and the transaction occurs against the respective details .The concentration will be on highlighting the events starting from the Filing of the Application form by the employee (user), Approval of the application by the administrator, Providing the information about the status to the employee (user) so he/she can fulfill the necessary requirement for the item, resulting in a final issue of items. This software system will help in automating all the processes required for item issuing. These processes are like filling the application form and submitting it, Checking the application form by the administrator for it’s validity for approval, Retrieval of all the approved request to check if all the formalities are fulfilled for final process and also the process required for the report generation of the item issued. 13
  14. 14. They can apply for the issue of the item according to their requirement. Each application will be sent to their concerned authority (HOD) and then it will sanction after checked the record of the employee. After getting sanctioned from authority the employee gets their item from their concerned authority. They can apply for the Hardware items (printer, pendrive, desktop, and laptop). As we know that our records information is traditionally paper based; they are maintained on paper. And because of that paper based record authority face lots of problem and if record will misplaced then humble of problem has been occurred. So this inventory control system will make the work of authorities bit easy. The current website is hosted at http:/intradit.nic.in as intradit content. The Enterprise Asset Management System includes the primary data such as employee code and employee name to which the item is provided. The system requires only a few information about the user, which also can be easily submit by the employee and rest of the work is self generated by the system. 14
  15. 15. 3.4 Component Assigned There are six modules in “Enterprise Management System” and the component assigned to me is “System Manager (SMG) Module” which is part of “Requisition/Issue Module”. 15
  16. 16. SMG Module: The System Manager (SMG) works like an administrator of the system. He has assigned a unique ID and password. There can be only one System Manager. He manages all the activities. Main functions of SMG module are: - • Creation of New LoginID. • Creation of New Category for the hardware. • Change Password for the existing LoginID. • Creation of New Employee. • Entry of details of holiday data. 16
  17. 17. 4. Technology Used 4.1 System Architecture: The system we have developed is mainly a web based system. The three-tier architecture is followed in the development of the system. Three tier architecture has three separate components: a client, an application server and a database server. In implementing three tier architecture the number of choices is more than the traditional client server architecture. The communication protocol used to communicate between the client and the application server can be different from that used to communicate between the application server and the database server. The workload distribution among the three components can vary widely across applications. Most web-enabled database relies on a three-tier model. Typically, an existing database server is made available for web-based access. To make the database available, the server must be accessible via an external network. To provide this network access, a second server is commonly used as a firewall, restricting the kinds of commands that can be passed to the database server. The application server can act as a firewall. Request Command APPLICATION DATABASE CLIENT SERVER SERVER Reply Result The above figure shows one possible configuration for a web enabled system. The client is a computer with access to the Internet, running a browser. The client communicates with the application server via the Hypertext Transfer Protocol (HTTP). The application server in turn executes commands against the database, formats the result in Hypertext Markup Language (HTML), and returns the result to the client. In this configuration, the application server provides authentication services (to make sure the client is allowed to initiate the request), database connection service, and application processing service. The client’s role is to initiate the request and display the result returned, while the database serves as the repository for the data. 17
  18. 18. 4.2 Hardware:- Processor : 1.70 GHz and Above Main Memory : 256 MB. Hard Disk : 40 GB. Disk Space : 100 MB. Floppy Disk Drive : 1.44 MB. Keyboard : HP Mouse : Compaq Monitor : hp7500 CD ROM Drive : 52x Samsung CD ROM 4.3 Software:- Operating System : Windows Software : C#.Net, Asp.Net, JAVASCRIPT, HTML Data Base : SQLServer2000 18
  19. 19. 4.4 Software Description:- .Net Introduction: What is Visual Studio .NET .NET is the result of a complete make-over of Microsoft’s software development products, and forms part of the company’s new strategy for delivering software as a service. The key features that .NET offers include: .NET Platform: The .NET platform includes the .NET Framework and tools to build and operate services, clients, and so on. ASP.NET, the focus of this book, is a part of the .NET Framework. .NET FRAMEWORK: THE CONCEPTUAL OVERVIEW The .NET Framework is an integral Windows component that supports building and running the next generation of applications and XML Web services. The .NET Framework is designed to fulfill the following objectives: • To provide a consistent object-oriented programming environment whether object code is stored and executed locally, executed locally but Internet-distributed, or executed remotely. • To provide a code-execution environment that minimizes software deployment and versioning conflicts. 19
  20. 20. • 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 problems of scripted or interpreted environments. • To make the developer experience consistent across widely varying types of applications, such as Windows-based applications and Web-based applications. • To build all communication on industry standards to ensure that code based on the .NET Framework can integrate with any other code. The .NET Framework has two main components: the common language runtime and the .NET Framework class library. The common language runtime is the foundation of the .NET Framework. We can think of the runtime as an agent that manages code at execution time, providing core services such as memory management, thread management, and remoting, while also enforcing strict type safety and other forms of code accuracy that promote security and robustness. In fact, the concept of code management is a fundamental principle of the runtime. Code that targets the runtime is known as managed code, while code that does not target the runtime is known as unmanaged code. The class library, the other main component of the .NET Framework, is a comprehensive, object-oriented collection of reusable types that you can use to develop applications ranging from traditional command-line or graphical user interface (GUI) applications to applications based on the latest innovations provided by ASP.NET, such as Web Forms and XML Web services. The .NET Framework can be hosted by unmanaged components that load the common language runtime into their processes and initiate the execution of managed code, thereby creating a software environment that can exploit both managed and unmanaged features. The .NET Framework not only provides several runtime hosts, but also supports the development of third-party runtime hosts. For example, ASP.NET hosts the runtime to provide a scalable, server-side environment for managed code. ASP.NET works directly with the runtime to enable 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 20
  21. 21. documents. 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. The following illustration shows the relationship of the common language runtime and the class library to your applications and to the overall system. The illustration also shows how managed code operates within a larger architecture. .NET Framework in context 21
  22. 22. What is ASP.NET For years now, Active Server Pages (ASP) has been arguably the leading choice for Web developers building dynamic Websites on Windows Web servers. ASP has gained popularity by offering the simplicity of flexible scripting via several languages. That combined with the fact that it’s built into every Microsoft Windows-based Web server, has made ASP a difficult act to follow. Early in 2002, Microsoft released its new technology for Internet development. Originally called ASP+, it was finally released as ASP.NET, and represents a leap forward from ASP both in sophistication and productivity for the developer. It continues to offer flexibility in terms of the languages it supports, but instead of a range of simple scripting languages, developers can now choose between several fully-fledged programming languages. Development in ASP.NET requires not only an understanding of HTML and Web design, but also a firm grasp of the concepts of object-oriented programming and development. ASP.NET is a server-side technology for developing Web applications based on the Microsoft .NET Framework. ASP.NET is server-side; that is, it runs on the Web server. Most Web designers start by learning client-side technologies like HTML, JavaScript, and Cascading Style Sheets (CSS). When a Web browser requests a Web page created with client-side technologies, the Web server simply grabs the files that the browser (the client) requests and sends them down the line. The client is entirely responsible for reading the code in the files and interpreting it to display the page on the screen. Server-side technologies, like ASP.NET, are different. Instead of being interpreted by the client, server-side code (for example, the code in an ASP.NET page) is interpreted by the Web server. In the case of ASP.NET, the code in the page is read by the server and used dynamically to generate standard HTML/JavaScript/CSS that is then sent to the browser. As all processing of ASP.NET code occurs on the server, it’s called a server-side technology. As Figure shows, the user (client) only sees the HTML, JavaScript, and CSS within the browser. The server (and server-side technology) is entirely responsible for processing the dynamic portions of the page. The Web server is responsible for processing the server-side code and presenting the output to the user (client). 22
  23. 23. ASP.NET is a technology for developing Web applications. A Web application is just a fancy name for a dynamic Website. Web applications usually (but not always) store information in a database on the Web server, and allow visitors to the site to access and change that information. Many different programming technologies and supported languages have been developed to create Web applications; PHP, JSP (using Java), CGI (using Perl), and Cold Fusion (using CFML) are just a few of the more popular ones. Rather than tying you to a specific technology and language, however, ASP.NET lets you write Web applications using a variety of familiar programming languages. Finally, ASP.NET is based on the Microsoft .NET Framework. Why and When Would I Use ASP.NET? New projects starting development should use ASP.NET for the following reasons: • Reduced development time • Increased performance • Increased application stability • Increased scalability • New ASP.NET features In addition to the above factors, ASP.NET, like ASP, is available for free. The only costs associated with ASP.NET development are the costs of the operating system on which you wish to run your application (Windows 2000, Windows XP, or the upcoming Windows .NET Server) and the cost of any development environment you choose to use. Of course, as with classic ASP, you can use free or inexpensive text 23
  24. 24. editors to create your applications. Given that the .NET Framework is a free add-on to Windows (and will be installed by default in the Windows .NET Server line), it is possible to create ASP.NET applications without spending a penny beyond the cost of the operating system and hardware on which it will run. Integrated Development Environments, such as Microsoft Visual Studio .NET, are also available at higher cost. C#.NET As the definition of C# evolved, the goals used in its design were as follows: C# is intended to be a simple, modern, general-purpose, object-oriented programming language. The language, and implementations thereof, should provide support for software engineering principles such as strong type checking, array bounds checking, detection of attempts to use uninitialized variables, and automatic garbage collection. Software robustness, durability, and programmer productivity are important. The language is intended for use in developing software components suitable for deployment in distributed environments. Source code portability is very important, as is programmer portability, especially for those programmers already familiar with C and C++. Support for internationalization is very important. C# is intended to be suitable for writing applications for both hosted and embedded systems, ranging from the very large that use sophisticated operating systems, down to the very small having dedicate functions. Although C# applications are intended to be economical with regards to memory and processing power requirements, the language was not intended to compete directly on performance and size with C or assembly language. The development of this standard started in November 2000.It is expected there will be future revisions to this standard, primarily to add new functionality. 24
  25. 25. JavaScript Introduction: JavaScript is a technique for manipulating HTML documents in the browser. This is often called client-side scripting. It allows the page author to incorporate facilities such as buttons that change in appearance when you move the mouse over them and menus that expand. It also provides facilities to manipulate the browser window in various interesting ways. It is used by incorporating programmes in parts of HTML pages known as scripts. Browsers must include JavaScript interpreters. It should be noted that JavaScript has nothing whatsoever to do with the Java programming language. Microsoft SQLServer 2000 Features of SQL Server 2000: Microsoft SQL Server 2000 features include: ♦ Internet Integration. The SQL Server 2000 database engine includes integrated XML support. It also has the scalability, availability, and security features required to operate as the data storage component of the largest Web sites. The SQL Server 2000 programming model is integrated with the Windows DNA architecture for developing Web applications, and SQL Server 2000 supports features such as English Query and the Microsoft Search Service to incorporate user-friendly queries and powerful search capabilities in Web applications. The same database engine can be used across platforms ranging from laptop computers running Microsoft Windows® 98 through large, multiprocessor servers running Microsoft Windows 2000 Data Center Edition. SQL Server 2000 Enterprise Edition supports features such as federated servers, indexed views, and large memory support that allow it to scale to the performance levels required by the largest Web sites. ♦ Enterprise-Level Database Features. The SQL Server 2000 relational database engine supports the features required to support demanding data processing environments. The database engine protects data integrity while minimizing the overhead of managing thousands of users 25
  26. 26. concurrently modifying the database. SQL Server 2000 distributed queries allow you to reference data from multiple sources as if it were a part of a SQL Server 2000 database, while at the same time, the distributed transaction support protects the integrity of any updates of the distributed data. Replication allows you to also maintain multiple copies of data, while ensuring that the separate copies remain synchronized. You can replicate a set of data to multiple, mobile, disconnected users, have them work autonomously, and then merge their modifications back to the publisher. ♦Ease of installation, deployment, and use. SQL Server 2000 includes a set of administrative and development tools that improve upon the process of installing, deploying, managing, and using SQL Server across several sites. SQL Server 2000 also supports a standards-based programming model integrated with the Windows DNA, making the use of SQL Server databases and data warehouses a seamless part of building powerful and scalable systems. These features allow you to rapidly deliver SQL Server applications that customers can implement with a minimum of installation and administrative overhead. ♦Data warehousing. SQL Server 2000 includes tools for extracting and analyzing summary data for online analytical processing. SQL Server also includes tools for visually designing databases and analyzing data using English-based questions. 26
  27. 27. SQL Server Enterprise Manager Microsoft Management Console (MMC) is a tool that presents a common interface for managing different server applications in a Microsoft Windows network. Server applications provide a component called an MMC snap-in that presents MMC users with a user interface for managing the server application. SQL Server Enterprise Manager is the Microsoft SQL Server™ MMC snap-in. SQL Server Enterprise Manager is the primary administrative tool for SQL Server and provides an MMC-compliant user interface that allows users to: • Define groups of SQL Server instances. • Register individual servers in a group. • Configure all SQL Server options for each registered server. • Create and administer all SQL Server databases, objects, logins, users, and permissions in each registered server. • Define and execute all SQL Server administrative tasks on each registered server. • Design and test SQL statements, batches, and scripts interactively by invoking SQL Query Analyzer. • Invoke the various wizards defined for SQL Server. Overview of the SQL Server Tools Microsoft SQL Server 2000 includes many graphical and command prompt utilities that allow users, programmers, and administrators to: • Administer and configure SQL Server. • Determine the catalog information in a copy of SQL Server. • Design and test queries for retrieving data. • Copy, import, export, and transform data. • Provide diagnostic information. • Start and stop SQL Server. In addition to these utilities, SQL Server contains several wizards to walk administrators and programmers through the steps needed to perform more complex administrative tasks. 27
  28. 28. 5. System Study and Analysis 5.1 Existing System: The management of the Enterprise Asset system of Technical store of DIT is currently following a manual procedure. The user has to check the availability of the required item by querying to the management. The management has to check the availability from the register manually. After getting the availability status the user has to fill up the application form manually. The management then checks the validity of the application form and after checking it books the item against the respective request. The information about the item is kept in a temporary register. When the user submits the entire necessary document, the administrator enters the details of the request in the main register of item details. Drawbacks of the existing system The whole process is carried out in a manual order. Since it’s a manual system it has the drawbacks such as time consumption, inefficient resource utilization. Some of the drawbacks of the current system are: • The Employee has to collect the request form by hand from the Technical store. • This consumes a valuable amount of time of the employee. • Every time an employee queries about the availability of the item the Management checks their register, which is also time consuming. 5.2 Proposed System: From earlier system the employees have to keep in touch with the Technical store’s management about the availability of the items .Now this system is the part of intradit website .The proposed system is a web based online system. The user can apply online from any place and also at any time. The main base of the proposed system is the database, which keeps all the information about the availability status of the items i.e. desktop, plotter, printer, laptop. Based on this information the user can easily get the availability status at any time without coming to the Technical store. 28
  29. 29. The software also allows user to fill up the application form and submit it online which will save a lot of user’s valuable time. Along with the availability status the database also keeps the information of the Issue details and the transaction details against the respective request .This database also keeps the information of user’s personal details, based on which the administrator can check the validity of the user and it’s request. Based on all the above information the administrator can efficiently respond all the user queries. The main activities will de performed by the system are: • Online submission of the application form by the employees. • Automation of the procedure performed by the administrator. • Report generation. 5.2.1 Objective of proposed system The main objective of the proposed system is to overcome the drawbacks of the existing system. The prime benefits are: • To create a comprehensive database that provides the information on the availability details and the issue details along with the transaction details related to item. • Development and implement of information retrieval system for the employees and the management of the Technical store. • To automate the entire range of activities or processes that needs to be performed by the administrator before a request. • To put the information on Intranet for easy access not only for the administrator but also for the employees. • To make the system more user friendly and easy to use. • Utilize the IT to increase the efficiency/productivity. 29
  30. 30. 5.2.2 Advantages of the proposed system The proposed system is a computerized system. This system has lots of advantages over the existing system. Some of them are • The user can log onto the intradit website from anywhere to check the availability status and issue the item. • This saves a valuable amount of employee time. • All the data relevant to item information are stored in the database. So the management can get rid of the tedious job like manually searching for an available and issue date. The database contains the cost information of the various items offered by Technical Store of DIT. So, the management can get help from the proposed system as most of the cost calculations are done in a computerized manner and the results are again in the database at it helps in the generation of bills. 5.2.3 Scope of the proposed system The “Enterprise Asset Management System of Technical store” software is being developed as accurate and efficient online software for the user such as the employees and also the administrator i.e. the management of the Technical store of DIT. In this system the record of the each request details are preserved along with their status and transaction related to them. The system is also made secured as all the updation of the item and transaction can be done by the authorized person i.e. the administrator only. 30
  31. 31. 5.3 FEASIBILITY STUDY The feasibility report of the project holds the advantages and flexibility of the project. This is divided into three sections: • Economical Feasibility • Technical Feasibility • Operational Feasibility 5.3.1 ECONOMIC FEASIBILITY A system’s financial benefit must exceed the cost of developing that system. i.e. a new system being developed should be a good investment for the organization. Economic feasibility considers the following: • The cost to conduct a full system investigation. • The cost of hardware and software for the class of application. • The benefits in the form of reduced cost or fewer costly errors. • The cost if nothing changes (i.e. the proposed system is not developed). The proposed “Enterprise Asset Management system” of Technical store of DIT is economically feasible because • The system requires very less time factors. • The system will provide fast and efficient automated environment instead of slow and error prone manual system, thus reducing both time and manpower spent in running the system. • The system will have GUI interface and very less user-training is required to learn it. • The system will provide service to view various information for proper managerial decision making. 31
  32. 32. 5.3.2 TECHNICAL FEASIBILITY Technical feasibility centers around the existing computer system (H/W and S/ W) whether it can support the addition of proposed system, if not, to what extent it can support and the organization’s capacity to acquire additional components. Our proposed system is technically feasible because: • The H/W and S/W required are easy to install and handle • The necessary H/W configuration and software platform is already there. • The system supports interactivity with the user through GUI Technical feasibility centers around the existing computer system (hardware and software) whether it can support the addition of proposed system, if not to what extend it can support the organization’s capacity to acquire required additional components. Proposed system is technically feasible because of the following reasons:- • The site will be hosted by Intradit website of DIT on behalf of Technical store of DIT , where all the H/W and S/W tools are available that are needed to run the application. So it doesn’t require extra investment to run the proposed application. • Expandability will be maintained in the new system. New modules can be added later on the application, if required in the future. • The application will have User-friendly Forms and Screens, all validation checks. So the new system guarantees accuracy, reliability, ease of access and data security. 32
  33. 33. 5.3.3 BEHAVIOURAL FEASIBILITY Behavioural feasibility determines how much effort will go in the proposed information system, and in educating and training the employees on the new system, along with the new ways of conducting the business. Behavioural study strives on ensuring that the equilibrium of the organization and status quo in the organization are not disturbed and changes are readily accepted by the users. The proposed system is behaviorally feasible because of the following: • The employees of Technical store of DIT will accept it because they are already acquainted with computers. • This system is also meant for the Technical user i.e. employees of DIT. Nowadays the Internet is almost familiar to everyone. So, it is not difficult for the user to use the system, in fact they feel comfortable in using this system. • Most of the employees are familiar with the web browser and the process of booking the auditorium will be simplified for the employees. The organization is definitely ready to welcome the computerized system. 33
  34. 34. 6. Software Requirement Specification (SRS) 1. Introduction 1.1. Version Version 0.01 1.2. Purpose The purpose of this document is to specify the requirements of the Enterprise Asset Management System of Technical Stores (EAMSTS). Every function, feature, and constraint that is required for this system is documented here. 1.3. Scope This document describes the requirements for all functions, features, and constraints for EAMSTS. 1.4. Definitions, Abbreviations, and Acronyms 1.4.1. Approval: Approval by the competent authority for the procurement/issue of a product. It may be in the form of a note sheet or in the form of an authenticated e- mail or through the ensuing web-enabled system. 1.4.2. Approved Configuration: Details of the configuration of a product approved by the competent authority for procurement. It must contain the empanelment letter, name of the empanelled vendor, and configuration of the product, price of the product and the relevant terms and conditions. 1.4.3. BCT: Bill Certification-Technical: Certification of the product given on the invoice/bill by the concerned authorized unit. 1.4.4. BCF: Bill Certification-Financial: Certification of the product given on the invoice/bill by TS that the product has been taken into the stock. 1.4.5. Chillan: Prepared by the supplier and sent along with the products for delivery to TS. 1.4.6. Clients: Departments who are availing DIT Services. 1.4.7. End-users: All the officers and staff of DIT availing Technical Stores services. 1.4.8. Expert Group: The group whose opinion is sought for either before procuring a product or before issuing a product to the end-user. 1.4.9. Field: All location other than Hqrs. 1.4.10. GFR 17: Generated by TS based on the ODF 1.4.11. GFR 18: Generated by Auction Committee and submitted to TS for deletion of inventory recorded in the individual’s name. 34
  35. 35. 1.4.12. HOD: Head of Division 1.4.13. Indent: A structured document prepared by Technical Stores based on the approval. 1.4.14. Invoice/Bill: Document raised by the supplier based on the PO. 1.4.15. IRC: Inspection-cum-Receiving Centre: In case of bulk procurement, NIC centre in the field nearest to the manufacturer site. 1.4.16. ODF: Obsolete Declaration Form: It is filled up the end-user who is having physical custody of the product in case of hardware. 1.4.17. PO: Purchase Order placed by the Technical Purchase onto the vendor based on the Indent received from the Technical Stores 1.4.18. POD: Proof of Delivery. Document raised by the supplier and signed by the receiver of the goods in the field 1.4.19. Product: Any IT product whether hardware or software. 1.4.20. Requisition: Document submitted by the end-user to get the product issued from TS. 1.4.21. Requestor: The officer who initiates the request for getting a product procured. 1.4.22 STV: Stock Transfer Voucher. It is prepared by the IRC. 1.4.23. TP: Technical Purchase 1.4.24. TS: Technical Stores 1.5 Overview of the System EAMSTS deals with obtaining approval for procurement of product from competent authority, raising of indents for procurement, receiving the products along with the relevant document, recoding the receipt, and issue of hardware to the authorized persons, getting the Annual Physical Verification of stock, preparing GFR 17 and finally deleting the inventory entries based on GFR 18 form. 35
  36. 36. 2. Description 2.1. General Description Technical Stores role starts when a user/employee sends in the requisition for a product. TS take the approval of the Competent Authority. After approval, TS checks whether the product is available in the store or not. If it is not available, then Indent is raised and product is procured and issued to the user. TS records receipt, issue, ensures annual physical verification of stock, declaring the products obsolete and deleting the entry from the individual after the product has been auctioned off. 2.2. Product Function Overview 2.2.1. Master data: 2.2.1.1. Database of all employees except Class IV, locations/departments under their control along with the name of their controlling officer. 2.2.1.2. Database of all the products. 2.2.1.3. Database of all the vendors 2.2.2. Inventory data. 2.2.2.1. Database of all Receipt of products 2.2.2.2. Database of all issue of products 2.2.2.3. Database of all products declared obsolete. 2.2.2.4. Database of all products finally disposed off 2.3. User Characteristics & Authentication (roles) 2.3.1. TS HOD: HOD Technical Store will: 2.3.1.1. Put up the entire request raised by the end-user to the competent authority for approval. 2.3.1.2. Inform the requestor about the status of the request. 2.3.1.3. Seek expert opinion, whenever needed from the expert group. 2.3.1.4. Get the Indent for procurement raised. 23.1.5. Record the receipt into receipt books/database 2.3.1.6. Certify the bills 2.3.1.7. Acknowledge STV and send it back to the IRCs 2.3.1.8. Inform the requestor that product is ready for issue 2.3.1.9. Record the issue into the issue books/database 2.3.1.10. Issue Gate pass and other necessary document required for product transportation to the field. 2.3.1.11. Get the Physical Verification Done 36
  37. 37. 2.3.1.12. Inform the end-users regarding the life span of the products. 2.3.1.13. Generate GFR 17 form 2.3.1.14. Update the final disposal. 2.3.2. HOD/SIO: HOD/SIO will: 2.3.2.1. Initiate the procurement and send it to TS 2.3.2.2. Signing proof of Delivery 2.3.2.3. Sending signed STV to IRCs/TS 2.3.2.4. Get the product issued. 2.3.2.5. Annual Physical Verification of Stock 2.3.2.6. Getting the GFR 17 issued from TS 2.3.2.7. Depositing obsolete product for Auctioning 2.4. General Constraints: 2.4.1. General Assumptions and Dependencies 2.4.1.1. It is assumed that the Approval System, Technical Stores, Purchase, Testing, IRCs and Auction Committee departments are computerized and database is available for sharing information. 2.4.1.2. It is also assumed the all the procedures are duly approved by the competent authority and are followed by the each and every one using the system. 2.4.1.3. It is also assumed that in the final phase, the manual recording of products in receipt and issue books will be completely eliminated. 2.4.1.4. As TS does not expect large volume of data in terms of number of records, duplicity of some data elements has been kept. 3. Functional Requirements 3.1. Approval from Competent Authority This is the starting point. Here in this phase the un-structured information in the form of note sheet / e- mail will be transformed into structured format. The input for this activity is generated by the end-users. After gone through the business process, it generates an output in the form of an authenticated approval from the competent authority, which is given as input to the next activity of Indent Raising/Issue Procedure. 37
  38. 38. 3.1.1. Overview: 3.1.1.1. HOD will raise a request for a product in the request form 3.1.1.2. The request form shall have provision to mention the essential details 3.1.1.3. The request form will be put up/transmitted to Technical Stores or updated on Technical Store website. 3.1.1.4. Technical stores will take advise from the expert group/Division wherever necessary 3.1.1.5. Technical stores shall put up the request for approval from the Competent Authority with the background information on the availability of the product/comments of the expert group/availability of the product in the approved panel list. 3.1.1.6. Provision to monitor the status of the request form will be made available to the requestor 3.1.1.7. Any further clarifications sought during approval phase shall be updated on the request form by Technical stores. 3.1.1.8. Alert to the requestor will be generated for clarifications if required 3.1.1.9. The requestor would fill in explanations by the user. 3.1.1.10. In the last stage, once the approval is obtained, a printout is taken and kept in the file to meet the audit requirement. 38
  39. 39. 3.1.2. Work Flow 39
  40. 40. 3.1.3. Data Files and linkages therein 3.2 Processing of Approval This is the next point from TS. Here in this phase the product approved by the competent authority for the end-user is either issue or its indent is raised for procurement. 3.2.1. System overview: The input for this activity is generated by the output of the previous activity. After having gone through the business process, it will generate an output in the form of an authenticated approval from the competent authority, which is communication to the requestor so that product can be issued or it will initiate the process for raising of indent. 40
  41. 41. 3.2.2. Work Flow 3.2.3. Data Files and linkages therein No new data file will be generated in this phase. Only approval data file created in the first phase will be updated with the appropriate message for the requestor and requestor will be alerted. 41
  42. 42. 3.3. Raising of Indent 3.3.1. System overview On the receipt of the approval and in case product cannot be issued from the current stock, TS will raise the indent for procurement and submits it to Technical Purchase (TP). The only pre-requisite for raising an indent is that there must be an empanelled vendor to supply the product. In case the required vendor is not in place, competent authority is informed as well as the end-user. TS will raise the indent in the prescribed format. Once indent has been raised and submitted to TP, end- user is informed and an alert message is generated. All indents raised will be shown as pending till the time TP places a PO and copy of PO is received in TS. A monthly / fortnightly report for all the pending indents is generated and sent to TP. 3.3.2. Work Flow 42
  43. 43. 3.3.3. Data Files and linkages therein 3.4 Recording of Issue of products As soon as the product is received in TS and has been stock entered, it will be ready for issue. Here end- user will submit the requisition form duly signed by the authorized person and TS will update the stock book and product will be physically handed over to the end-user. It is end- user’s responsibility to get the product transported from the racks of TS to its respective destination. TS will only assist in the paper work. 43
  44. 44. 3.4.2. Work Flow 3.4.2.1. Work flow for the end-user 44
  45. 45. 3.4.2.2. Work Flow for TS 45
  46. 46. 3.4.3. Data Files and linkages therein Product Master and issue data file will be updated. 46
  47. 47. 3.5. Physical Verification of Stock 3.5.1. System overview As per Government’s rules the stock procured and issued to the end-users has to be annually verified and a certificate is to be provided by the end-users to TS that everything is in order and there is no storage or excess of stock available with them. At present this is a fully paper-based exercise. Printout of the stock mainly h/w is taken-out by TS and dispatched to the end-users along with the necessary directions to conduct physical verification. End users after conducting the physical verification send the report back to TS. 3.5.2. Work Flow 3.5.3. Data Files and linkages therein Only Daybook and Location master is used to take printout. 47
  48. 48. 4. External Interface Requirements 4.1. User Interface / Brief features of the Interface 4.1.1. The user interface of TS will be GUI. 4.1.2. The application will be web enabled and menu driven. 4.1.3. A menu containing the options provided by the system depending on the user authentication will appear on the computer screen. 4.1.4. The system will be accessed by the entire DIT employee except class IV. 4.1.5. Any individual should be able to view and to update (on selective base) the inventory record available in his/her custody. 4.1.6. Any supervisory level officer should be able to view the entire inventory available with the staff posted under him/her. 4.1.7. Access the system from only one pre-designated machine. 4.1.8. Concerned official ensures that their e-mail address is up-to date in the employee master. 4.2. Hardware and Software platform 4.2.1. Hardware: SAN Server 4.2.2. Software: C#.Net, Asp.Net, JAVASCRIPT, HTML, SQLServer2000 4.2.3. Printer: Color Laser Printer A3 size for TS 4.2.4. Scanner: A4 size 4.2.5. CD-writer: One External CD-Writer 4.3. Hardware & Software Interface (Horizontal Integration) TS will be linked to Purchase Information System, Testing Information system of DIT and at IRCs. 4.4. Hardware & Software Interface (Vertical Integration) TS will interface vertically with User Departments applications depending on the need. 48
  49. 49. 5 Coding Structure 5.1. Employee Code: The existing directory of codes as followed by DIT will do the job. 5.2. Item Code 5.2.1.1.Definition: Here we define the scheme for encoding /decoding the products procured by DIT. There must be some logical in designing this scheme. For the code it should be possible to group the products into major and minor categories. Some the important categories are listed below and the list is not exhaustive 5.2.1.2. Hardware 5.2.1.2.1. Communication 5.2.1.2.1.1.VSAT 5.2.1.2.1.2. Modems 5.2.1.2.1.3.Hub/Switches 5.2.1.2.1.4.Routers 5.2.1.2.2. Computers 5.2.1.2.2.1.Desktop 5.2.1.2.2.2.Workstation 5.2.1.2.2.3.Server 5.2.1.2.3. Printers 5.2.1.2.3.1.Inkjet 5.2.1.2.3.2.laserjet 5.2.1.2.3.3.Dot matrix 5.2.1.2.3.4.Line matrix 5.2.1.2.4. Perpherals 5.2.1.2.4.1.CD-writers 5.2.1.2.4.2.Web Camera 5.2.1.2.4.3.Scanners 5.2.1.3. Software 5.2.1.3.1. Operating System 5.2.1.3.2. Development Tools 5.2.1.3.3. Office Automation Tools 49
  50. 50. 6 Non-functional Requirements: 6.1 Security Requirement: The “Enterprise Asset Management System” is a secured system as no one can access the system and tamper the data without an authorized account. The authorized administrator handles all the data i.e. only the administrator can access the system. 6.2Maintainability Requirement: A regular maintenance is needed for smooth and efficient performance of the software. To do this, the software should be monitored at regular interval of time. If any fault will be noticed it should be reported immediately. 50
  51. 51. 7. Design of the Component 7.1 Functional Decomposition Diagram (FDD) 51
  52. 52. 52
  53. 53. 7.2 DFD 53
  54. 54. Level 1 DFD 54
  55. 55. Level 2 DFD Level 3 DFD 55
  56. 56. 7.3. Entity Relationship Diagram EMP_COD HOD_ID NAME EmployeeI Passwor E D d Employee_InformationMS Login_MS EncrptPWD 1 1 Role Verificatio Admin_Roles EmployeeI D 1 Admin_RolesMS 1 Requisitio n Approval_ID Approval_ID Request_ID EmployeeI Request_ID EmployeeI D D M Employee_RequisitionTR M Employee_RequisitionApprovedAR EmployeeI Approval_I D D Request_ID IssueProce ProductItem_IssuedTR ss Issue_Date ProductItem_IssuedAR Receipt_DateTim e ProductItem_ReceivedAR ProductItem_ReceivedTR 56
  57. 57. 7.4 Database Design 1. Admin_RolesMS FIELD NAME FIELD TYPE SIZE EmployeeID Nvarchar 255 Admin_Roles Nvarchar 255 2. Designation FIELD NAME FIELD TYPE SIZE DesignationCode float 8 Designation Nvarchar 255 3. Desktop FIELD NAME FIELD TYPE SIZE Category_Code Nvarchar 255 Category Nvarchar 255 Type_Code Nvarchar 255 Type Nvarchar 255 Configuration_Code Nvarchar 255 Item_Code Nvarchar 255 Item_Description Nvarchar 255 Reserved_Quantity Nvarchar 255 Make Nvarchar 255 Model Nvarchar 255 SupplierCode Nvarchar 255 57
  58. 58. 4. Employee_InformationMS FIELD NAME FIELD TYPE SIZE HOD_ID Nvarchar 255 HOD_NAME Nvarchar 255 HOD_DESIGNATION Nvarchar 255 HIREDATE Nvarchar 255 SCODE Nvarchar 255 SITECODE Nvarchar 255 HOD_YN Nvarchar 255 Group_Code Nvarchar 255 Group_Name Nvarchar 255 Block Nvarchar 255 Bay Nvarchar 255 HOD_Email Nvarchar 255 HOD_Mobile Nvarchar 255 5. Item_MainCategoryMS FIELD NAME FIELD TYPE SIZE Code Nvarchar 255 Name Nvarchar 1500 6. Login_MS FIELD NAME FIELD TYPE SIZE EmployeeID Nvarchar 50 Password Nvarchar 50 EncrptPWD Nvarchar 50 58
  59. 59. 7. Employee_Profile FIELD NAME FIELD TYPE SIZE EMP_CODE Nvarchar 255 FIRSTNAME Nvarchar 255 MIDDLENAME Nvarchar 255 LASTNAME Nvarchar 255 DESIGNATION Nvarchar 255 EMAIL Nvarchar 255 OFF_PHONE Nvarchar 255 EXT_NO Nvarchar 255 RESI_PHONE Nvarchar 255 MOBILENO Nvarchar 255 HOUSENO Nvarchar 255 STREETNO Nvarchar 255 CITY Nvarchar 255 STATE Nvarchar 255 PIN_CODE Nvarchar 255 L_CODE Nvarchar 255 SITE_NAME Nvarchar 255 DIVISION Nvarchar 255 BUILDING_NAME Nvarchar 255 FLOOR Nvarchar 255 ROOM_NO Nvarchar 255 HOD_ID Nvarchar 255 HOD_NAME Nvarchar 255 HOD_DESIGNATION Nvarchar 255 HIREDATE Nvarchar 255 SCODE Nvarchar 255 SITECODE Nvarchar 255 HOD_YN Nvarchar 255 Group_Code Nvarchar 255 Group_Name Nvarchar 255 Block Nvarchar 255 Bay Nvarchar 255 HOD_Email Nvarchar 255 HOD_Mobile Nvarchar 255 8. Employee_RequisitionTR 59
  60. 60. FIELD NAME FIELD TYPE SIZE Approval_ID Int 4 Request_ID Int 4 EmployeeID Nvarchar 255 Name Nvarchar 100 Designation Nvarchar 50 Division Nvarchar 200 MDSD Nvarchar 100 Email Nvarchar 50 PhoneNo Nvarchar 20 Extension Nvarchar 20 Products_RequiredFor Nvarchar 50 Item_Description Nvarchar 500 Item_Code Nvarchar 255 Configuration_code Nvarchar 255 Quantity Int 4 Delivery_address Nvarchar 500 Date_Issue/Receive Nvarchar 50 Justification Nvarchar 600 Reference Nvarchar 255 Remarks Nvarchar 255 Req_DateTime Nvarchar 50 HOD_ID Nvarchar 255 HOD_Sanction Nvarchar 255 HOD_SancDateTime Nvarchar 255 HOD_Remarks Nvarchar 255 ExpGrp_Sanction Nvarchar 255 ExpGrp_SancDateTime Nvarchar 255 ExpGrp_Remarks Nvarchar 255 TS_Sanction Nvarchar 255 TS_SancDateTime Nvarchar 255 CA_Sanction Nvarchar 255 CA_SancDateTime Datetime 8 CA_Remarks Nvarchar 255 HOD_Reject_Remark Nvarchar 250 HOD_Name Nvarchar 100 60
  61. 61. 9. ProductItem_ReceivedTR FIELD NAME FIELD TYPE SIZE Item_Code Nvarchar 255 Configuration_Code Nvarchar 255 Item_Description Nvarchar 255 Serial_No Nvarchar 255 Request_ID Int 4 Receipt_DateTime Nvarchar 50 Indent_No Int 4 Indent_DateTime Datetime 8 PO_No Nvarchar 255 PO_DateTime Datetime 8 Bill_No Nvarchar 255 Bill_DateTime Datetime 8 POD_No Nvarchar 255 POD_DateTime Datetime 8 Supplier_Code Nvarchar 255 Installation_DateTime Datetime 8 Quantities Int 4 Category_Code Nvarchar 255 Reserved_Value Int 4 Codename Char 10 ReqForReqID Int 4 Book_Value Nvarchar 50 obs_Status Nvarchar 255 Final_Status Nvarchar 255 ReceiveType Nvarchar 10 ReceiveStatus Nvarchar 50 Approval_ID Int 4 10. ProductItem_ReceivedAR 61
  62. 62. FIELD NAME FIELD TYPE SIZE Item_Code Nvarchar 255 Configuration_Code Nvarchar 255 Item_Description Nvarchar 255 Serial_No Nvarchar 255 Request_ID Int 4 Receipt_DateTime Nvarchar 50 Indent_No Int 4 Indent_DateTime Datetime 8 PO_No Nvarchar 255 PO_DateTime Datetime 8 Bill_No Nvarchar 255 Bill_DateTime Datetime 8 POD_No Nvarchar 255 POD_DateTime Datetime 8 Supplier_Code Nvarchar 255 Installation_DateTime Datetime 8 Quantities Int 4 Category_Code Nvarchar 255 Reserved_Value Int 4 Codename Char 10 ReqForReqID Int 4 Book_Value Nvarchar 50 obs_Status Nvarchar 255 Final_Status Nvarchar 255 ReceiveType Nvarchar 10 ReceiveStatus Nvarchar 50 Approval_ID Int 4 PO_Date Datetime 8 Bill_Date datetime 8 62
  63. 63. 11. ProductItem_IssuedTR FIELD NAME FIELD TYPE SIZE Rno Nvarchar 255 EmployeeID Nvarchar 255 Employee_Name Nvarchar 255 PO_No Nvarchar 255 POD_No Nvarchar 255 Category_Code Nvarchar 255 RoomNo Nvarchar 255 LRNO Nvarchar 255 CLASS_CODE Nvarchar 255 Voucherno Nvarchar 255 Configuration_Code Nvarchar 255 POD_DateTime Datetime 8 Item_Description Nvarchar 400 Supplier_Code Nvarchar 255 BILL_No Nvarchar 255 Bill_DateTime Datetime 8 Item_Code Nvarchar 255 Item_Code1 Nvarchar 255 Quantities Nvarchar 255 Issue_Date Nvarchar 50 DivName Nvarchar 255 Book_Value Nvarchar 255 Amount Nvarchar 255 Item_Code_old Nvarchar 255 Serial_No Nvarchar 255 Receiver_Name Nvarchar 255 Req_DateTime Nvarchar 50 HOD_Name Nvarchar 255 Request_ID Nvarchar 255 Final_Status Nvarchar 255 Receipt_DateTime Nvarchar 50 Approval_ID Nvarchar 255 Indent_No Nvarchar 255 HOD_ID Nvarchar 255 Division Nvarchar 255 FinalIssueStatus Nvarchar 50 63
  64. 64. 12. ProductItem_IssuedAR FIELD NAME FIELD TYPE SIZE Item_code Nvarchar 255 Configuration_Code Nvarchar 255 Item_Description Nvarchar 255 Serial_No Nvarchar 255 Approval_ID Int 4 Request_ID Int 4 Voucherno Nvarchar 255 Req_DateTime Nvarchar 50 Receipt_DateTime Nvarchar 50 Indent_No Nvarchar 255 Indent_DateTime Datetime 8 PO_No Nvarchar 255 PO_DateTime Datetime 8 Bill_No Nvarchar 255 Bill_DateTime Datetime 8 POD_No Nvarchar 255 POD_DateTime Datetime 8 Supplier_Code Nvarchar 255 Installation_DateTime Datetime 8 Issue_Date Nvarchar 50 EmployeeID Nvarchar 50 Employee_Name Nvarchar 255 Quantities Int 4 Delivery_Address Nvarchar 500 Final_Status Nvarchar 255 HOD_ID Nvarchar 100 HOD_Name Nvarchar 100 Division Nvarchar 255 DivName Varchar 50 Category_Code Nvarchar 255 Site_Code Nvarchar 255 Location Nvarchar 50 Receiver_Name Nvarchar 50 Receiver_Desig Nvarchar 50 FinalIssueStatus Nvarchar 50 64
  65. 65. 7.5 Physical Design (Physical files and their descriptions) 1. Login Page : Description : This is the login screen. Here the user (i.e. the authorized official) will login by using their right userID and Password 65
  66. 66. 2. IntraDIT Home Page after Login: 66
  67. 67. 3. Employee Page: Description: When employee login ,Employee Page will appear. This screen will show all the functionalities in menus that the application can perform. 67
  68. 68. 4.Requisition Page: Description : In this Page Employee gives the Requistion for hardware/Software Items. 68
  69. 69. 5. HOD Requisition Approval Reminder Page: Description : After Clicking on submit button in requisition page employee’s request for hardware/Software goes to HOD for approval. 69
  70. 70. 6. My Requisition Status: Description: This page shows the status (Pending/Forwarded/Approved) of Employee’s request for Hardware/Software. 70
  71. 71. 7. Employee Details: Description : This page shows the Employee’s official details as the name selected in the dropdownlist. 71
  72. 72. 8. Technical store page: Description :This is the technical store page. It appears when role is TS. . This screen will show all the functionalities in menus that the application can perform.After approval by HOD,Employee’s request finally goes to technical store for approval. 72
  73. 73. 9. RecieveItem in store: Description:This page shows the Items in stock. 73
  74. 74. 10. Issue page: Description : In this page TS will issue the requested item after checking the items already issued to the employee and availability of the requested item In the stock register. 74
  75. 75. 11. System Manager (SMG) page: Description: This is the System Manager page. It appears when role is SMG. He performs all the managerial activities. 75
  76. 76. 12. Create New EmployeeID Page: Description: In this page SMG will create a new employeeID. 76
  77. 77. 13. Change Password Page: Description: This page is for the change of the password for the employee against the id.after clicking on submit button a popup window will appear for confirmation. 77
  78. 78. 14. Create New Category: Description: This page adds a new item in a particular category which is selected in dropdown list on clicking the submit button entry for new item will stored in database. 78
  79. 79. 15. Get Employee Detail Page: Description: This page shows the Employee details whose EmployeeID will be generated on clicking the GetEmpCode button. 16.PopUp Window to get Employee Code: 79
  80. 80. 17. Add Holiday page: Description: In this page SMG adds new holiday data for selected state. 80
  81. 81. 18. View Gazzeted Holiday List: Description: This page displays the Gazzeted Holiday List. 81
  82. 82. 19. Logged Out: Description: This page displays the Logout Window on clicking “Logout” button. 82
  83. 83. Report: 1. Employee Inventory Description: This report shows the Employee Inventory when login. 83
  84. 84. 2. View Inventory by TS: Description: This report shows the Items Issued to the employee when selected in the dropdown list. 84
  85. 85. 3. Issue Detail Between Dates Description: This page show the quantities issued for the required period as entered by the user. 85
  86. 86. 4. Technical Store Item Inventory Report: Description: This report shows the received items detail in Technical Store. 86
  87. 87. 5. Employee Info by Employee ID: Description: This page displays the Employee’s details against the Employee code as entered by user on clicking the “Details “button. 87
  88. 88. 6. Item Description by serial NO. Description: This page show the quantities issued against the particular item’s Serial No. as entered by the TS. 88
  89. 89. 7. View Inventory: Description: This page displays the inventory report and Total no. of Items issued to the employee. 89
  90. 90. 8. Conclusion The web enabled system “Enterprise Asset Management System” on successful completion will provide the facility to the employees of DIT so that they can send their request online. The Authority of the Technical Store, IT will be also benefited by the proposed system, as it will automate the whole issuing procedure, which will reduce the workload for the Authority Any work may not be always perfect. There may be some errors or defects in the work. I have taken enough care to make my web application more users friendly, more interactive and attractive. I hope that “Enterprise Asset Management system” will be useful to the organization. I am heartedly thankful to all the teachers who have helped us directly or indirectly to make this project work complete. Any suggestion to make this project more useful is always welcome. I would like to thank Mr. C.S Jairath (senior technical director, NIC New Delhi) and Mr. Niraj Goswami (SA, NIC New Delhi), for sharing their idea with me. I would like to thank them for their constant encouragement, suggestions and moral support through out the duration of our project. 90
  91. 91. 9. Bibliography  Reference Books: o ASP. Net Unleashed 2.0 By Stephen Walther o ASP. Net 2.0 Guide By Wrox Publication o SQL Server 2000 By Microsoft Publication o Software Engineering By Pressman o MSDN Help January-2006 o System Analysis and Design By Elias M.Awad (Galgotia Publications)  Reference Sites: o www.dotnetspider.com o www.highdots.com o www.devsource.com o www.c-sharpcorner.com o www.dotnetjunkies.com o www.google.co.in o www.codersource.net 91

×